[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package hoel - 1.4.8-4ubuntu1 --- hoel (1.4.8-4ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Thu, 13 Feb 2020 13:11:18 -0300 ** Changed in: hoel (Ubuntu) Status: In Progress => Fix Released ** Changed in: gearmand (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 qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package gearmand - 1.1.18+ds-3.1ubuntu1 --- gearmand (1.1.18+ds-3.1ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Thu, 20 Feb 2020 20:02:18 -0300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857198] Re: alsa ALC285 Missing still, No Sound Lenovo Ideapad S740
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1857198 Title: alsa ALC285 Missing still, No Sound Lenovo Ideapad S740 Status in alsa-driver package in Ubuntu: Expired Bug description: cat /proc/asound/card0/codec* | grep Codec I tired all the possible trouble shooting and firmware and kernel, Current Kernel : 5.0.0-37-generic Problem : If I connect Headphone or any 3.5 Jack device it works perfectly but my laptop speakers are not working still. Please help. For more info below link has more info for my device http://alsa-project.org/db/?f=581ebad190e03c379ea87ce08d6b365e1cfe4580 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771041] Re: Remove gconf from Ubuntu
This bug was fixed in the package gyrus - 0.3.12-1 --- gyrus (0.3.12-1) unstable; urgency=medium * QA upload. * New upstream release. * debian/patches/643404.diff: Remove; fixed upstream. * debian/patches/713631.diff: Likewise. * debian/patches/deprecated-macros.patch: New; remove a deprecated gnome-common macro (Closes: #830014). * debian/patches/gsettings-port.patch: New; port to GSettings as GConf is about to be removed (Closes: #886065). * debian/patches/gtk3-port.patch: New; port to GTK 3. * debian/patches/glib-deprecations.patch: New; replace some deprecated GLib functions/macros. * debian/patches/compiler-warnings.patch: New; fix some warnings. * debian/patches/desktop.patch: New; remove deprecated Encoding entry in the .desktop file; add Keywords entry. * debian/patches/series: Update. * debian/compat: Bump to 12. * debian/control: Run wrap-and-sort -ast. (Build-Depends): Remove cdbs, libgconf2-dev, libglade2-dev (unused) and libxml-parser-perl (pulled in by intltool). Bump debhelper version requirement. Add autoconf-archive. Replace libgtk2.0-dev with libamtk-5-dev. Remove intltool version constraint. (Homepage): Set to the project page at wiki.gnome.org. (Rules-Requires-Root): Set to no. (Standards-Version): Compliant with 4.4.1 as of this release. * debian/rules: Rewrite for dh, enable hardening. * debian/dirs: Delete; useless. * debian/watch: Bump version, use https and .xz extension. * debian/gyrus.1: New file. * debian/manpages: Install it. * debian/copyright: Rewrite as machine-readable. * debian/NEWS: Warn users that all stored sessions are lost. * debian/changelog: Strip trailing whitespace. -- Yavor Doganov Mon, 28 Oct 2019 23:38:41 +0200 ** Changed in: gyrus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1771041 Title: Remove gconf from Ubuntu Status in desktopnova package in Ubuntu: New Status in evolution-indicator package in Ubuntu: New Status in gconf package in Ubuntu: New Status in gconf-editor package in Ubuntu: New Status in gkdebconf package in Ubuntu: New Status in gnome-mastermind package in Ubuntu: New Status in gnome-phone-manager package in Ubuntu: New Status in gnome-xcf-thumbnailer package in Ubuntu: New Status in gnomint package in Ubuntu: New Status in gtkwave package in Ubuntu: Fix Released Status in guake-indicator package in Ubuntu: New Status in gyrus package in Ubuntu: Fix Released Status in jack-mixer package in Ubuntu: New Status in jana package in Ubuntu: New Status in mssh package in Ubuntu: New Status in ogmrip package in Ubuntu: New Status in ooo-thumbnailer package in Ubuntu: New Status in planner package in Ubuntu: New Status in ogmrip package in Debian: Confirmed Bug description: gconf is being removed from Debian Testing. We should remove it from Ubuntu also. eclipse is troublesome. At a minimum, we can remove everything but eclipse and gconf. libgnome is sort of a blocker so do it first LP: #1771031 And remove libqt-gconf LP: #1740538 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktopnova/+bug/1771041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863724] Autopkgtest regression report (mesa/19.2.8-0ubuntu0~19.10.3)
All autopkgtests for the newly accepted mesa (19.2.8-0ubuntu0~19.10.3) for eoan have finished running. The following regressions have been reported in tests triggered by the package: mutter/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1863724 Title: Add missing pci-id's for Comet Lake (CML) Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Committed Bug description: [Impact] After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was updated but some parts of it got accidentally dropped, losing a couple of pci-id's for CML. They need to be restored. [Test case] Install the updates on an affected machine, check with glxinfo -B that the proper driver is loaded. [Regression potential] none, this just adds pci-id's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1863724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package gnokii - 0.6.31+dfsg-2ubuntu10 --- gnokii (0.6.31+dfsg-2ubuntu10) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Thu, 13 Feb 2020 11:31:25 -0300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package gnunet - 0.10.1-5.1ubuntu1 --- gnunet (0.10.1-5.1ubuntu1) focal; urgency=medium * d/control: request python2 explicitly, this doesn't work with py3 yet. * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Fri, 14 Feb 2020 19:49:34 -0300 ** Changed in: gnokii (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 qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package jabberd2 - 2.7.0-1ubuntu1 --- jabberd2 (2.7.0-1ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Thu, 13 Feb 2020 13:24:51 -0300 ** Changed in: jabberd2 (Ubuntu) Status: In Progress => Fix Released ** Changed in: gnunet (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 qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
Thanks for the analysis! >From it, I still wonder whether this is a pulseaudio bug, though. Why is pulseaudio ever binding to RFCOMM channel 3 *before* there is any need to do so? That is, until I am not connected to any device using channel 3, why is pulseaudio already using it up? In other words, it seems reasonable to me to have the laptop connected to the phone as a headset and in this case not to have the impress remote working. But in case I start impress before setting up a bluetooth connection to the phone, why should be the pulseaudio binding already there? -- 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/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798400]
This issue was annoying me for a while too. So I sat down and debugged bluez to see why the bind fails: LO is using the default channel (3) for the RFCOMM protocol as it should be. However, the bind call fails, because another process has already bound that channel via DBUS. Changing the default RFCOMM channel in the bluez source temporaliy to 2 (UDP, unused) and recompiling bluez made remote impress work immediately! So I inspected the DBUS users via the old mdbus tool from openmoko and it turned out that the other process is PulseAudio: The HS profile needs the RFCOMM for the AT Commands and registers channel 3. Stop PA and impress remote works again. So now we have two programs that need RFCOMM for the mobile phone. :-( One solution would be that LO explicitly requests channel 2 instead of the default one. Channel 2 is UDP and unused to my knowledge. This will work until another programm needs RFCOMM and chooses 2 as a free channel... Or, in the long run, there needs to be some kind of multipexing between the apps that use the RFCOMM protocol. -- 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/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1863370] Re: problem opening settings
Thank you for reporting this bug to Ubuntu. Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1863370 Title: problem opening settings Status in Ubuntu: Won't Fix Bug description: i Have problem opening settings in ubuntu disco 19 destop ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CompositorRunning: None Date: Fri Feb 14 14:05:32 2020 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Microsoft Corporation Haswell-ULT Integrated Graphics Controller [1414:0005] InstallationDate: Installed on 2020-02-11 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181115) MachineType: Microsoft Corporation Surface Pro 3 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=a63a3048-e668-4ab7-afe7-71e98c06872b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2650 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2650:bd04/30/2019:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.sku: Surface_Pro_3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1863370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864031] Re: system will not connect after opening browser
*** This bug is a duplicate of bug 1858280 *** https://bugs.launchpad.net/bugs/1858280 Please stop reporting the same bug as we already have bug 1858280 open. Please put any further comments in that one. ** This bug has been marked a duplicate of bug 1858280 Firefox reports "cannot connect to internet" message -- 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/1864031 Title: system will not connect after opening browser Status in xorg package in Ubuntu: Incomplete Bug description: Software glitch after summoning browser and selecting website, fail to connect. I run Diagnostic bug check and get bug summary and report connects finally and uploads report. Does this randomly and the clears out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 20 07:13:19 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1296 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (421 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package gerbera - 1.1.0+dfsg-3ubuntu1 --- gerbera (1.1.0+dfsg-3ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Wed, 12 Feb 2020 20:36:24 -0300 ** Changed in: gerbera (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 qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: In Progress Status in gnunet package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864061] Re: PCI/internal sound card not detected
This machine has dmic on it, so the legacy hda abort the probe: snd_hda_intel :00:1f.3: Digital mics found on Skylake+ platform, aborting probe And if want the legacy hda driver to work, please add options snd-hda- intel dmic_detect=0 in the /etc/modprobe.d/alsa-base.conf This is a machine which has dmic on it, so please blacklist snd_soc_skl driver through /etc/modporbe.d/balcklist.conf, then the sof driver will be loaded. And if there is some issue, I will fix it, I am working on the the sof driver for eoan kernel now. -- 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/1864061 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Feb 20 16:46:21 2020 InstallationDate: Installed on 2019-10-07 (136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET44W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET44W(1.27):bd01/15/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1864061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
*** This bug is a duplicate of bug 1576953 *** https://bugs.launchpad.net/bugs/1576953 I don't think that apport-collect will work while I am offline. Please let me know how I can run this command and send the data after I have done the restart. Remember, after restart the problem goes away. I can't run diagnostics on Internet access that requires Internet access to run. As it looks like I am talking to an automated script rather than a real person perhaps this is now a dead thread. -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same problem on 18.04 with Sony headset: s [WI-1000X]# info 38:18:4C:04:C7:2A Device 38:18:4C:04:C7:2A (public) Name: WI-1000X Alias: WI-1000X Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) >>>UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (7b265b0e-2232-4d45-bef4-bb8ae62f813d) UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351) UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7) UUID: Vendor specific (96cc203e-5068-46ad-b32d-e316f5e069ba) UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b) UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15) Modalias: usb:v054Cp0C63d0411 -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
aha, so: $ snap info --verbose git-ubuntu | grep contact contact: https://bugs.launchpad.net/usd-importer/+filebug I wonder, if we can improve apport to actually upload / start filing a bug report on launchpad, if it points to a launchpad +filebug url? Can we enforce for contact to be set to something sensible, for all Canonical published projects? Also does apport know how to open bug reports against launchpad "upstream" (not ubuntu distro-package) projects? And i guess also github issues? -- 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/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: New Status in Snap Store: New Status in apport package in Ubuntu: Incomplete Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package vtk7 - 7.1.1+dfsg2-2ubuntu1 --- vtk7 (7.1.1+dfsg2-2ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Gianfranco Costamagna Wed, 19 Feb 2020 21:46:28 +0100 ** Changed in: vtk7 (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 qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in gnunet package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864061] Re: PCI/internal sound card not detected
It seems there were some fixes in the new kernel for the intel sound system. Including some for the Lenovo X1 carbon 7th gen. https://launchpad.net/ubuntu/+source/linux/5.3.0-41.33 -- 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/1864061 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Feb 20 16:46:21 2020 InstallationDate: Installed on 2019-10-07 (136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET44W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET44W(1.27):bd01/15/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1864061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)
** Also affects: apport (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags removed: rls-ee-incoming -- 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/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) Status in apport package in Ubuntu: Confirmed Status in apport source package in Focal: Confirmed Bug description: https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: 5.0 -- 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
@slashd, thanks for uploading util-linux to Focal. I've added the SRU template and uploaded to Eoan. ** Description changed: + [Impact] + + * lsblk no longer prints a partition's parent +kernel device name (the wholedisk). +(i.e., 'lsblk -no PKNAME /dev/partition') + + * Another impact is the 'removable media' check +always return zero for partitions. +(i.e., 'lsblk -no RM /dev/partition') + + * The regression was introduced on v2.34, only +Eoan (v2.34) and later are affected. +Disco (v2.33) and earlier are not affected. + + * The regression is fixed in v2.35, in commit +e3bb9bfb76c1 ("lsblk: force to print PKNAME +for partition"); fixes RM for partition too. + + [Test Case] + + * lsblk -no PKNAME /dev/vda1 # partition + + * Expected output: vda # wholedisk + + * Current output: (nothing) + + [Regression Potential] + + * Columns that depend on a partition device's +parent device (i.e., seen as 'wholedisk') +could in theory show incorrect values if +another bug is present in v2.34 for that. + + * Other usages of 'parent' pointer in the +function have been examined and reported +(e.g. issue w/ removable media column), +and others found to not have issues +(e.g. --merge option, to group multiple +parents of a device, as in RAID.) + + [Other Info] + + * The impacts to the curtin source package +have been addressed in other way, it no +longer requires util-linux, comment #14. + + * util-linux github issue: +https://github.com/karelzak/util-linux/issues/813 + + [Original Bug Description] + During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: [Impact] * lsblk no longer prints a partition's parent kernel device name (the wholedisk). (i.e., 'lsblk -no PKNAME /dev/partition') * Another impact is the 'removable media' check always return zero for partitions. (i.e., 'lsblk -no RM /dev/partition') * The regression was introduced on v2.34, only Eoan (v2.34) and later are affected. Disco (v2.33) and earlier are not affected. * The regression is fixed in v2.35, in commit e3bb9bfb76c1 ("lsblk: force to print PKNAME for partition"); fixes RM for partition too. [Test Case] * lsblk -no PKNAME /dev/vda1 # partition * Expected output: vda # wholedisk * Current output: (nothing) [Regression Potential] * Columns that depend on a partition device's parent device (i.e., seen as 'wholedisk') could in theory show incorrect values if another bug is present in v2.34 for that. * Other usages of 'parent' pointer in the function have been examined and reported (e.g. issue w/ removable media column), and others found to not have issues (e.g. --merge option, to group multiple parents of a device, as in RAID.) [Other Info] * The impacts to the curtin source package have been addressed in other way, it no longer requires util-linux, comment #14. * util-linux github issue: https://github.com/karelzak/util-linux/issues/813 [Original Bug Description] During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698181] Re: Switch to netplan renderer in Artful
** Changed in: maas (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: Fix Released Status in openvswitch: New Status in cloud-init package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: Fix Released Status in resolvconf package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
util-linux uploaded in focal. Thanks Mauricio ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864062] Re: autopkgtest regressions with gmp 6.2.0
** Changed in: gmp (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gmp in Ubuntu. https://bugs.launchpad.net/bugs/1864062 Title: autopkgtest regressions with gmp 6.2.0 Status in gmp package in Ubuntu: New Status in libmath-gmp-perl package in Ubuntu: New Status in libmath-prime-util-gmp-perl package in Ubuntu: New Status in postgresql-pgmp package in Ubuntu: New Status in gmp package in Debian: Fix Released Bug description: Change in behaviour in GMP makes adjustments needed in reverse dependencies: postgresql-pgmp needs merging 1.0.4-1 from Debian unstable. Perl tests need to be fixed, see the linked Debian bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/1864062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I don't mean to sound rude, just want to understand how this is working. I gave it a week and now loginctl list-sessions have 1955 sessions like that and it keeps growing... How the bug reports are handled? Thanks -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: New Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
I think it's worth mentioning that 'ubuntu-bug git-ubuntu' does present a dialog telling you that "it is about a snap published by canonical. Contact them via https://bugs.launchpad.net/usd-importer/+filebug for help". So apport does try to point you in the right direction. You can see this code in apport/ui.py. -- 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/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: New Status in Snap Store: New Status in apport package in Ubuntu: Incomplete Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863195] Re: py3compile should not emit python runtime warnings during dist-upgrade
** Also affects: dh-python (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags removed: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1863195 Title: py3compile should not emit python runtime warnings during dist-upgrade Status in dh-python package in Ubuntu: Confirmed Status in dh-python source package in Focal: Confirmed Bug description: py3compile should compile without emitting python runtime warnings on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are emitted during apt upgrade, due to buffering=1 being deprecated. We will not fix all the packages, and these warnings are not helpful to the users, as they cannot and shouldn't need to do anything about them, as they come from packages that are maintained by the distro. Imho py3compile should execute python interpreter with -W ignore Or maybe set PYTHONWARNINGS=ignore in the environment during the upgrade? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1863195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
** Also affects: command-not-found (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: python3-defaults (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags removed: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Confirmed Status in python3-defaults package in Ubuntu: Confirmed Status in command-not-found source package in Focal: Confirmed Status in python3-defaults source package in Focal: Confirmed Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
So, snaps in the snapstore can declare a contact url, where one can file bug reports. I don't see these to be exposed on the system, but maybe I don't know the localhost APIs for that. I do wonder if there can be some standartesation done, for example, if the contact url is +filebug on a launchpad project, maybe apport should be able to file bugs against the launchpad project for that snap. Ie. ideally ubuntu-bug core20 subiquity git-ubuntu would all work. @snapd @snapcraft @snapstore - is there a standard for where to file bug reports, and how can apport query and use it? Can we start enforcing branced snaps to provide that? ** Also affects: snapd Importance: Undecided Status: New ** Also affects: snapcraft Importance: Undecided Status: New ** Also affects: snapstore Importance: Undecided Status: New ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: New Status in Snap Store: New Status in apport package in Ubuntu: Incomplete Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Tags removed: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864061] Re: PCI/internal sound card not detected
** Package changed: ubuntu => alsa-driver (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/1864061 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Feb 20 16:46:21 2020 InstallationDate: Installed on 2019-10-07 (136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET44W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET44W(1.27):bd01/15/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1864061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863195] Re: py3compile should not emit python runtime warnings during dist-upgrade
** Changed in: dh-python (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1863195 Title: py3compile should not emit python runtime warnings during dist-upgrade Status in dh-python package in Ubuntu: Confirmed Bug description: py3compile should compile without emitting python runtime warnings on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are emitted during apt upgrade, due to buffering=1 being deprecated. We will not fix all the packages, and these warnings are not helpful to the users, as they cannot and shouldn't need to do anything about them, as they come from packages that are maintained by the distro. Imho py3compile should execute python interpreter with -W ignore Or maybe set PYTHONWARNINGS=ignore in the environment during the upgrade? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1863195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864062] Re: autopkgtest regressions with gmp 6.2.0
** Also affects: libmath-gmp-perl (Ubuntu) Importance: Undecided Status: New ** Also affects: libmath-prime-util-gmp-perl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gmp in Ubuntu. https://bugs.launchpad.net/bugs/1864062 Title: autopkgtest regressions with gmp 6.2.0 Status in gmp package in Ubuntu: New Status in libmath-gmp-perl package in Ubuntu: New Status in libmath-prime-util-gmp-perl package in Ubuntu: New Status in postgresql-pgmp package in Ubuntu: New Status in gmp package in Debian: Unknown Bug description: Change in behaviour in GMP makes adjustments needed in reverse dependencies: postgresql-pgmp needs merging 1.0.4-1 from Debian unstable. Perl tests need to be fixed, see the linked Debian bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/1864062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864061] [NEW] PCI/internal sound card not detected
You have been subscribed to a public bug: Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Feb 20 16:46:21 2020 InstallationDate: Installed on 2019-10-07 (136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET44W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET44W(1.27):bd01/15/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- PCI/internal sound card not detected https://bugs.launchpad.net/bugs/1864061 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1864062] [NEW] autopkgtest regressions with gmp 6.2.0
Public bug reported: Change in behaviour in GMP makes adjustments needed in reverse dependencies: postgresql-pgmp needs merging 1.0.4-1 from Debian unstable. Perl tests need to be fixed, see the linked Debian bug report. ** Affects: gmp (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-pgmp (Ubuntu) Importance: Undecided Status: New ** Affects: gmp (Debian) Importance: Unknown Status: Unknown ** Tags: update-excuse ** Bug watch added: Debian Bug tracker #950608 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950608 ** Also affects: gmp (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950608 Importance: Unknown Status: Unknown ** Also affects: postgresql-pgmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gmp in Ubuntu. https://bugs.launchpad.net/bugs/1864062 Title: autopkgtest regressions with gmp 6.2.0 Status in gmp package in Ubuntu: New Status in postgresql-pgmp package in Ubuntu: New Status in gmp package in Debian: Unknown Bug description: Change in behaviour in GMP makes adjustments needed in reverse dependencies: postgresql-pgmp needs merging 1.0.4-1 from Debian unstable. Perl tests need to be fixed, see the linked Debian bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/1864062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: sru-20200217 ** Tags added: gcp -- 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
The problem is also present in privileged LXC containers. Example with full LXC configuration below, on a host with a custom 5.4.13 kernel. # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf # For Ubuntu 14.04 lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none bind,optional 0 0 lxc.mount.entry = /sys/kernel/security sys/kernel/security none bind,optional 0 0 lxc.mount.entry = /sys/fs/pstore sys/fs/pstore none bind,optional 0 0 lxc.mount.entry = mqueue dev/mqueue mqueue rw,relatime,create=dir,optional 0 0 lxc.include = /usr/share/lxc/config/userns.conf # For Ubuntu 14.04 lxc.mount.entry = /sys/firmware/efi/efivars sys/firmware/efi/efivars none bind,optional 0 0 lxc.mount.entry = /proc/sys/fs/binfmt_misc proc/sys/fs/binfmt_misc none bind,optional 0 0 lxc.arch = linux64 lxc.hook.pre-start = /usr/local/share/lxc/hooks/pre-start.sh vps526706 lxc.hook.post-stop = /usr/local/share/lxc/hooks/post-stop.sh vps526706 lxc.hook.destroy = /usr/local/share/lxc/hooks/destroy.sh vps526706 lxc.mount.fstab = /lxc/vps526706/fstab lxc.rootfs.path = dir:/lxc/vps526706/rootfs lxc.uts.name = vps526706 # Network configuration lxc.net.0.type = veth lxc.net.0.veth.pair = vps526706 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:67:06 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.171/32 -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. Hosts: Debian Buster custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd6
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Tags added: sts-sponsor-mfo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working
I would like to add that, as described here (https://askubuntu.com/questions/1208247/this-device-is-not-working- message-in-additional-drivers-in-asus-zenbook-ubu) this is affecting me in Ubuntu 18.04, not just 20.04 as reported here. -- 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/1859308 Title: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working Status in software-properties package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Patch added: "lp1862846_focal_util-linux.debdiff" https://bugs.launchpad.net/subiquity/+bug/1862846/+attachment/5329790/+files/lp1862846_focal_util-linux.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
@ltrager, Indeed, I see the refactor in curtin. :) Absolutely agree w/ you, it's a regression in util-linux, and after following up with you on IRC yesterday that it is OK for me to submit the fix to Ubuntu, I worked on it. I've tested the patch today, and it's currently building on all architectures in a test PPA. If all goes well, it should move forward to Focal and Eoan in the coming days. Providing test steps in the next comment. Attaching the debdiffs for reference. cheers, Mauricio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
util-linux / test steps === Bionic --- No regression: parent kernel device name $ dpkg -s util-linux | grep ^Version: Version: 2.31.1-0.4ubuntu3.5 $ lsblk -no pkname /dev/vda1 vda Eoan --- Before: empty string $ dpkg -s util-linux | grep ^Version: Version: 2.34-0.1ubuntu2.2 $ lsblk -no pkname /dev/vda1 $ After: parent kernel device name $ dpkg -s util-linux | grep ^Version: Version: 2.34-0.1ubuntu2.2+pkname1 $ lsblk -no pkname /dev/vda1 vda Focal --- Before: empty string $ dpkg -s util-linux | grep ^Version: Version: 2.34-0.1ubuntu6 $ lsblk -no pkname /dev/vda1 $ After: parent kernel device name $ dpkg -s util-linux | grep ^Version: Version: 2.34-0.1ubuntu6+pkname1 $ lsblk -no pkname /dev/vda1 vda -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Patch added: "lp1862846_eoan_util-linux.debdiff" https://bugs.launchpad.net/subiquity/+bug/1862846/+attachment/5329791/+files/lp1862846_eoan_util-linux.debdiff ** Changed in: util-linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: util-linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Eoan) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: util-linux (Ubuntu Focal) Status: New => In Progress ** Changed in: util-linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Focal) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: In Progress Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863724] Re: Add missing pci-id's for Comet Lake (CML)
and since it's an identical package in eoan which just added three pci- id's, I've marked it verified there too ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1863724 Title: Add missing pci-id's for Comet Lake (CML) Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Committed Bug description: [Impact] After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was updated but some parts of it got accidentally dropped, losing a couple of pci-id's for CML. They need to be restored. [Test case] Install the updates on an affected machine, check with glxinfo -B that the proper driver is loaded. [Regression potential] none, this just adds pci-id's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1863724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864048] [NEW] Bluetooth mic not working in ubuntu 14.04.4 LTS
Public bug reported: I have bluetooth headset(speaker & mic). It is working fine(speaker & mic) in Windows 7 but in Ubuntu 14.04.4 LTS only speaker work and mic not working. I have dual boot system, so I think it is not related to hardware issue. Profile selected is High fedelity Playback(A2DP Sink), HSP/HFP not working. ** Affects: alsa-driver (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-driver in Ubuntu. https://bugs.launchpad.net/bugs/1864048 Title: Bluetooth mic not working in ubuntu 14.04.4 LTS Status in alsa-driver package in Ubuntu: New Bug description: I have bluetooth headset(speaker & mic). It is working fine(speaker & mic) in Windows 7 but in Ubuntu 14.04.4 LTS only speaker work and mic not working. I have dual boot system, so I think it is not related to hardware issue. Profile selected is High fedelity Playback(A2DP Sink), HSP/HFP not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1864048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864031] Re: system will not connect after opening browser
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). You've reported this bug against Xorg so is it video/glitch-on-screen? but also have "system will not connect after opening browser" which makes me think of network issues, Currently I feel it's unclear what your issue is, so please clarify. I've marked this bug report as Incomplete, once you've provided the requested detail - please change status back to "New". If you believe I'm in error, leave a comment explaining why, and you can change it back to "New" too. Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1864031 Title: system will not connect after opening browser Status in xorg package in Ubuntu: Incomplete Bug description: Software glitch after summoning browser and selecting website, fail to connect. I run Diagnostic bug check and get bug summary and report connects finally and uploads report. Does this randomly and the clears out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 20 07:13:19 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1296 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (421 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** No longer affects: nautilus ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/gtk/issues/2457 Importance: Unknown Status: Unknown -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863988] Re: 49 unnecessary warnings about "configured multiple times"
You created a google.list file with duplicates so it's your fault. The Google packages will reinstall their sources.lomist files eventually. It's important for users to know that there are duplicates as that can easily lead to errors further down the road. ** Changed in: apt (Ubuntu) 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/1863988 Title: 49 unnecessary warnings about "configured multiple times" Status in apt package in Ubuntu: Invalid Bug description: Two duplicate entries in apt sources, that exist due to no fault of my own, generated 49 entirely unnecessary warnings every single time I ran apt-update or added a ppa today. apt-get update W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target Contents-deb (main/Contents-amd64) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target Contents-deb (main/Contents-all) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1 W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target Contents-deb (main/Contents-amd64) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target Contents-deb (main/Contents-all) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and /etc/apt/sources.list.d/google.list:2 N: Skipping acquire of configured file
[Touch-packages] [Bug 1864031] [NEW] system will not connect after opening browser
Public bug reported: Software glitch after summoning browser and selecting website, fail to connect. I run Diagnostic bug check and get bug summary and report connects finally and uploads report. Does this randomly and the clears out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 20 07:13:19 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1296 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (421 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1864031 Title: system will not connect after opening browser Status in xorg package in Ubuntu: New Bug description: Software glitch after summoning browser and selecting website, fail to connect. I run Diagnostic bug check and get bug summary and report connects finally and uploads report. Does this randomly and the clears out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 20 07:13:19 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1296 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (421 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7
[Touch-packages] [Bug 1864031] Re: system will not connect after opening browser
Please get this bug cleared out with some program you can send me. Thanks -- 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/1864031 Title: system will not connect after opening browser Status in xorg package in Ubuntu: New Bug description: Software glitch after summoning browser and selecting website, fail to connect. I run Diagnostic bug check and get bug summary and report connects finally and uploads report. Does this randomly and the clears out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 20 07:13:19 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1296 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (421 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
The bug manifests on v.19.10 too. I have experienced it also in past on v.^16 and v.^18. -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
Moved to: https://gitlab.gnome.org/GNOME/gtk/issues/2457 ** Description changed: - https://gitlab.gnome.org/GNOME/nautilus/issues/1190 + https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2457 https://gitlab.gnome.org/GNOME/gtk/issues/2457 -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
Did you do your test in an unprivileged LXC container? -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. Hosts: Debian Buster custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::ff:fe5
[Touch-packages] [Bug 1864008] Re: No hardware acceleration on i5-9600K (UHD630) with HWE kernel and Xorg
The issue is probably: [ 8.309] (WW) intel(0): Unknown chipset [ 8.374] (II) GLX: Initialized DRISWRAST GL provider for screen 0 But I wouldn't blame the intel driver. It's old and may not ever support newer Intel GPUs. You should instead use the newer "modesetting" driver. If you have a custom Xorg config file then replace "intel" with "modesetting". If you don't, then just uninstall the Intel driver: sudo apt remove xserver-xorg-video-intel ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1864008 Title: No hardware acceleration on i5-9600K (UHD630) with HWE kernel and Xorg Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: Hello! I've replaced CPU from i5-8600K to i5-9600K and found that compiz consuming circa 200% CPU all the time. I've searched X.org log and from what I see there are no hardware acceleration in my system: [ 8.308] (II) intel(0): SNA compiled: xserver-xorg-video-intel-hwe-16.04 2:2.99.917+git20171229-1~16.04.1 (Timo Aaltonen ) [ 8.308] (II) intel(0): SNA compiled for use with valgrind [ 8.309] (WW) intel(0): Unknown chipset [ 8.310] (II) intel(0): SNA initialized with disabled backend [ 8.311] (WW) intel(0): loading DRI2 whilst acceleration is disabled. [ 8.319] (EE) AIGLX error: Calling driver entry point failed [ 8.320] (EE) AIGLX: reverting to software rendering # lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 I've tried to load i195 with i915.alpha_support=1 but it didn't helps. Display performance is very poor, sometime even mice pointer moves with lags especially when browser-based applications like Skype or Slack are active. # apt show xserver-xorg-video-intel-hwe-16.04 Package: xserver-xorg-video-intel-hwe-16.04 Version: 2:2.99.917+git20171229-1~16.04.1 My previous CPU had UHD630 as well so I guess that intel driver just need some hint to understand that it is still the same hardware with minor changes in naming or so. Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 20 11:40:53 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2019-08-01 (202 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=e3b65cff-1991-4573-b276-1d072093f039 ro quiet splash i915.alpha_support=1 vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2604 dmi.board.asset.tag: Default string dmi.board.name: PRIME Q370M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2604:bd09/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEQ370M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xse
[Touch-packages] [Bug 1864008] [NEW] No hardware acceleration on i5-9600K (UHD630) with HWE kernel and Xorg
Public bug reported: Hello! I've replaced CPU from i5-8600K to i5-9600K and found that compiz consuming circa 200% CPU all the time. I've searched X.org log and from what I see there are no hardware acceleration in my system: [ 8.308] (II) intel(0): SNA compiled: xserver-xorg-video-intel-hwe-16.04 2:2.99.917+git20171229-1~16.04.1 (Timo Aaltonen ) [ 8.308] (II) intel(0): SNA compiled for use with valgrind [ 8.309] (WW) intel(0): Unknown chipset [ 8.310] (II) intel(0): SNA initialized with disabled backend [ 8.311] (WW) intel(0): loading DRI2 whilst acceleration is disabled. [ 8.319] (EE) AIGLX error: Calling driver entry point failed [ 8.320] (EE) AIGLX: reverting to software rendering # lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 I've tried to load i195 with i915.alpha_support=1 but it didn't helps. Display performance is very poor, sometime even mice pointer moves with lags especially when browser-based applications like Skype or Slack are active. # apt show xserver-xorg-video-intel-hwe-16.04 Package: xserver-xorg-video-intel-hwe-16.04 Version: 2:2.99.917+git20171229-1~16.04.1 My previous CPU had UHD630 as well so I guess that intel driver just need some hint to understand that it is still the same hardware with minor changes in naming or so. Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 20 11:40:53 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2019-08-01 (202 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=e3b65cff-1991-4573-b276-1d072093f039 ro quiet splash i915.alpha_support=1 vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2604 dmi.board.asset.tag: Default string dmi.board.name: PRIME Q370M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2604:bd09/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEQ370M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 20 11:39:21 2020 xserver.configfile: default xserver.errors: AIGLX error: Calling driver entry point failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 26167 vendor IVM xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 performance ubuntu xenial -- 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/1864008 Title: No hardware acceleration on i5-9600K (UHD630) with HWE kernel and Xorg Status in xorg package in Ubuntu: New Bug description: Hello! I've replaced CPU from i5-8600K to i5-9600K and found that compiz consuming circa 200% CPU all the time. I've searched X.org log and from what I see there are no hardware acceleration in my sys
[Touch-packages] [Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server
** Changed in: bind9 (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1862437 Title: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server Status in bind9 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: Starting Ubuntu 16.10 resolution of LAN addresses fails. This name resolution failure is evident in every post 16.0 Ubuntu & derivative that I have tested. See below - which shows 16.04 resolves, 18.04 and Pop!_OS 19.04 fail, and other distros - Fedora 31, openSUSE Leap 15.1, and Debian GNU/Linux 10 (buster) - all resolve as expected. == Test Case == $ name=$(hostnamectl | grep "Static hostname:" | cut -d: -f2 | xargs) $ echo "${name}" $ hostnamectl | grep System $ hostnamectl | grep Kernel $ nmcli dev show | grep DNS $ nslookup "${name}" == Additional Information == Operating System: Ubuntu 16.04.6 LTS Kernel: Linux 4.4.0-170-generic IP4.DNS[1]: 192.168.3.2 Server:127.0.1.1 Address: 127.0.1.1#53 Name: BGOWIKI01v Address: 192.168.3.60 Operating System: Ubuntu 18.04.3 LTS Kernel: Linux 4.15.0-72-generic IP4.DNS[1]: 192.168.3.2 Server:127.0.0.53 Address: 127.0.0.53#53 ** server can't find BGOWIKI01v: SERVFAIL Operating System: Pop!_OS 19.04 Kernel: Linux 5.0.0-21-generic IP4.DNS[1]: 192.168.3.2 Server:127.0.0.53 Address: 127.0.0.53#53 ** server can't find BGOWIKI01v: SERVFAIL Operating System: Fedora 31 (Workstation Edition) Kernel: Linux 5.3.7-301.fc31.x86_64 IP4.DNS[1]: 192.168.3.2 Server:192.168.3.2 Address: 192.168.3.2#53 Name: BGOWIKI01v Address: 192.168.3.60 Operating System: openSUSE Leap 15.1 Kernel: Linux 4.12.14-lp151.28.36-default IP4.DNS[1]: 192.168.3.2 Server:192.168.3.2 Address: 192.168.3.2#53 Name: BGOWIKI01v Address: 192.168.3.60 Operating System: Debian GNU/Linux 10 (buster) Kernel: Linux 4.19.0-6-amd64 IP4.DNS[1]: 192.168.3.2 Server:192.168.3.2 Address: 192.168.3.2#53 Name: BGOWIKI01v Address: 192.168.3.60 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsutils 1:9.11.3+dfsg-1ubuntu1.11 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: MATE Date: Sat Feb 8 17:36:28 2020 InstallationDate: Installed on 2019-12-22 (47 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: bind9 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1862437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp