[Touch-packages] [Bug 1834129] [NEW] Presence of sshd_config mandatory
Public bug reported: OpenSSH 7.9p1 Ubuntu 18..04.2 (LTS) If a sshd daemon is started with a "-f my_sshd_config" command-line specification the sshd process still requires the existence of the sshd_config. The bug is somewhere in one of the forked processes started when an external client attempts a connection. Since the sshd_config file does not exists, an external client connection cannot be started. Solution: If I "touch /etc/ssh/sshd_config" then the lock-up issue goes away and I am successfully able to login. Bug: If the sshd configuration file is specified in the command line execution of the daeomon, then this should be the only file that should be required. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834129 Title: Presence of sshd_config mandatory Status in openssh package in Ubuntu: New Bug description: OpenSSH 7.9p1 Ubuntu 18..04.2 (LTS) If a sshd daemon is started with a "-f my_sshd_config" command-line specification the sshd process still requires the existence of the sshd_config. The bug is somewhere in one of the forked processes started when an external client attempts a connection. Since the sshd_config file does not exists, an external client connection cannot be started. Solution: If I "touch /etc/ssh/sshd_config" then the lock-up issue goes away and I am successfully able to login. Bug: If the sshd configuration file is specified in the command line execution of the daeomon, then this should be the only file that should be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834128] [NEW] Multiple sshd services cannot be executed
Public bug reported: OpenSSH 7.6p1 Ubuntu 18.04.2 (LTS) (Bionic) See also Ticket #1831765, #1690485, and #1832110 regarding the path of the privilege separation directory (aka: /run/sshd). The current Debian installer sets the RuntimeDirectory=sshd (i.e. /run/sshd) in sshd.service (i.e. /lib/systemd/system/sshd.service) and sshd@.service (i.e. /lib/systemd/system/sshd@.service). This is not the best means of implementing this service. The problem is that the systemd deletes the RuntimeDirectory resource as soon as the service is stopped. When this happens, other sshd services will fault since the privileged separation directory is no longer there. We need to modify the configuration as follows: 1) Create /usr/lib/tmpfiles.d/sshd.conf that defines the /run/sshd directory with root:root as the owner and the protection of 0755. 2) Change the assignment of the RuntimeDirectory in sshd.service to something other than sshd (i.e. /run/sshd). 3) Change the assignment of the RuntimeDirectory in sshd@.service to something other than sshd (i.e. /run/sshd). Both OpenSSH and Ubuntu have declined to provision a means of adjusting the Privilege Separation directory. Since both teams do not want to address this, we need to have a means of implementing multiple instance sshd invocation using systemd and avoiding using the RuntimeDirectory assignment of /run/sshd. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834128 Title: Multiple sshd services cannot be executed Status in openssh package in Ubuntu: New Bug description: OpenSSH 7.6p1 Ubuntu 18.04.2 (LTS) (Bionic) See also Ticket #1831765, #1690485, and #1832110 regarding the path of the privilege separation directory (aka: /run/sshd). The current Debian installer sets the RuntimeDirectory=sshd (i.e. /run/sshd) in sshd.service (i.e. /lib/systemd/system/sshd.service) and sshd@.service (i.e. /lib/systemd/system/sshd@.service). This is not the best means of implementing this service. The problem is that the systemd deletes the RuntimeDirectory resource as soon as the service is stopped. When this happens, other sshd services will fault since the privileged separation directory is no longer there. We need to modify the configuration as follows: 1) Create /usr/lib/tmpfiles.d/sshd.conf that defines the /run/sshd directory with root:root as the owner and the protection of 0755. 2) Change the assignment of the RuntimeDirectory in sshd.service to something other than sshd (i.e. /run/sshd). 3) Change the assignment of the RuntimeDirectory in sshd@.service to something other than sshd (i.e. /run/sshd). Both OpenSSH and Ubuntu have declined to provision a means of adjusting the Privilege Separation directory. Since both teams do not want to address this, we need to have a means of implementing multiple instance sshd invocation using systemd and avoiding using the RuntimeDirectory assignment of /run/sshd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1237846] Re: OSK autopilot emulator isn't able to shift into CAPSLOCK state successfully.
I am pretty sure that veebers is not working on this bug. ** Changed in: ubuntu-keyboard (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1237846 Title: OSK autopilot emulator isn't able to shift into CAPSLOCK state successfully. Status in ubuntu-keyboard package in Ubuntu: Triaged Bug description: There is an issue with how the emulator handles changing states and currently can't handle changing into CAPSLOCK mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1237846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377169] Re: Top Crasher: /usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure
I am pretty sure that veebers is not working on this bug. ** Changed in: autopilot (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1377169 Title: Top Crasher: /usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure:addFailure:addFailure:addError:_convert:status:status:_gather_test:_fail:_details_to_str:as_text:_iter_text:decode Status in autopilot package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding autopilot. This problem was most recently seen with version 1.5.0+14.10.20140812-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/f293befd9513bb3f7a21b730cf9026f38d43e8e1 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1377169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1238662] Re: [autopilot] needs tests for deployment features
I am pretty sure that veebers is not working on this bug. ** Changed in: qtcreator-plugin-ubuntu (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1238662 Title: [autopilot] needs tests for deployment features Status in qtcreator-plugin-ubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: Opinion Bug description: so with the switch to mir/unity-mir we created this bug https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1238031 as that feature is fairly critical for app developers & permissions topics haven't fully settled - i would suggest we have some sort of test for this. its kind of weird cause its SDK, requiring both PC & devicemaybe they already have a test to harness ?? can you help us? (note if you want to put this in a blueprint that's ok too) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1238662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1204982] Re: refactored autopilot tests are fail prone for wrong environment setup
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1204982 Title: refactored autopilot tests are fail prone for wrong environment setup Status in Autopilot: Invalid Status in unity8 package in Ubuntu: Triaged Bug description: The old autopilot tests, when you would launch "autopilot run unity8" from within the source directory in tests/autopilot/, it would always try to run the local build. If there was no local build, it would fail, saying it can't find the binary. The new ones, don't. They fall back to the installed binary even though loading local tests. This fails in like 99% of the cases. Even worse, the error messages you get just totally don't match with the code you are examining for debugging. This issue is even worse now that the tests require a make install in the builddir (not telling so btw). If the install step really really needs to be kept (which I'm strongly voting against) then there should be a big fat debug output which binary is loaded, a big fat warning if the expected local installation is not found and in no way falling back to some other unity8 binary not having to do anything with the local test suite. To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/1204982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1229561] Re: Automated regression test for Bug #1227714 (OSK doesn't close after the application closes)
I am pretty sure that veebers is not working on this bug. ** Changed in: ubuntu-keyboard (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1229561 Title: Automated regression test for Bug #1227714 (OSK doesn't close after the application closes) Status in ubuntu-keyboard package in Ubuntu: Triaged Bug description: Automated regression test for Bug #1227714 (OSK doesn't close after the application closes). A test to show when this bug is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1229561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1202511] Re: Clean up unity8 indicator client test suite
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1202511 Title: Clean up unity8 indicator client test suite Status in unity8 package in Ubuntu: New Bug description: The unity8 indicators autopilot test suite needs a cleanup, similar to the unity8 shell tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1202511/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1260013] Re: [ap test] need to test click package app launching from dash
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1260013 Title: [ap test] need to test click package app launching from dash Status in unity8 package in Ubuntu: Triaged Bug description: this is related to an issue we found in the latest attempt to promote unity8 into the image. we do have an AP test in which core/resident apps are launched from the dash, but no click packages. We need to add a test specifically for click packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1260013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281688] Re: autopilot vis fails with: autopilot.introspection.dbus.StateNotFoundError
I am pretty sure that veebers is not working on this bug.
** Changed in: xpathselect
Assignee: Christopher Lee (veebers) => (unassigned)
** Changed in: xpathselect
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1281688
Title:
autopilot vis fails with:
autopilot.introspection.dbus.StateNotFoundError
Status in XPathSelect:
New
Status in autopilot package in Ubuntu:
New
Status in xpathselect package in Ubuntu:
Fix Released
Bug description:
When introspecting large application like qtcreator, autopilot vis
fails with:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/autopilot/vis/main_window.py", line
133, in tree_item_changed
self.detail_widget.tree_node_changed(proxy)
File "/usr/lib/python2.7/dist-packages/autopilot/vis/objectproperties.py",
line 64, in tree_node_changed
self.widget(i).new_node_selected(new_node)
File "/usr/lib/python2.7/dist-packages/autopilot/vis/objectproperties.py",
line 123, in new_node_selected
object_details = node.get_properties()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 246, in get_properties
self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 472, in refresh_state
_, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 562, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
autopilot.introspection.dbus.StateNotFoundError: State not found for class
'Core::Internal::MainWindow' and filters {'id': 3}.
TEST CASE
1. Install qtcreator
2. Run: autopilot launch qtcreator
3. Run: autopilot vis
4. In vis select qtcreator
5. Browser the widget tree
ACTUAL RESULT
Lot of widget can not be instrospected and fail with StateNotFound
EXPECTED RESULT
User can introspect the whole tree
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-autopilot 1.4+14.04.20140213-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 18 09:19:29 2014
InstallationDate: Installed on 2013-09-03 (167 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
PackageArchitecture: all
SourcePackage: autopilot
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xpathselect/+bug/1281688/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322199] Re: autopilot cannot fully introspect Qt applications
I am pretty sure that veebers is not working on this bug. ** Changed in: autopilot-qt Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1322199 Title: autopilot cannot fully introspect Qt applications Status in Autopilot Qt Support: Confirmed Status in autopilot-qt package in Ubuntu: Confirmed Bug description: Currently, for Qt apps, autopilot Qt introspection library is not taking into account non-QObject objects. Some widgets store visible elements in non-QObect data structures and are not visible from autopilot even if they are visible on the screen. This is for example the case for the content of QTableWidget, QListWidget, QTreeWidget etc. These objects store data in QTableWidgetItem, QListWidgetItem and QTreeWidgetItem respectively. These data structures do not inherit QObject. Autopilot should be improved to handle non-Qobject type datatypes for any UI element. To reproduce build the examples from the package qtbase5-examples and try to introspect applications in examples/widgets/ that contains any of the widget mentioned above e.g findfiles or spreadsheet. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libautopilot-qt 1.4+14.04.20140312-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 22 16:02:37 2014 InstallationDate: Installed on 2013-09-03 (260 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) SourcePackage: autopilot-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-qt/+bug/1322199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834053] Re: [Inspiron 3558] PCI/internal sound card not detected
*** This bug is a duplicate of bug 1820794 *** https://bugs.launchpad.net/bugs/1820794 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1820794, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - PCI/internal sound card not detected + [Inspiron 3558] PCI/internal sound card not detected ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1820794 [Dell Inspiron 3558] PCI/internal sound card not detected -- 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/1834053 Title: [Inspiron 3558] PCI/internal sound card not detected Status in linux package in Ubuntu: New Bug description: No sound as my pc does not detect sound hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 24 20:39:45 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-11-06 (960 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2019-06-24 (0 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834112] Re: the mouse stopped responding to commands
1. Which mouse is having the problem? You seem to have at least two mice connected. 2. Please remove these from your kernel command line options: drm.debug=0xe plymouth:debug and then reboot. 3. Wait for the problem to happen again and then please immediately run: dmesg > newdmesg.txt and send us the file 'newdmesg.txt'. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (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/1834112 Title: the mouse stopped responding to commands Status in linux package in Ubuntu: Incomplete Bug description: the mouse stopped responding to commands ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Mon Jun 24 21:21:31 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-24-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 24 21:29:22 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834047] Re: External monitor not recognised
> I have BenQ i do not know what number, but it is connected by HDMI to DVI cable. Does that mean you are trying to connect two monitors or only one? Because the system is recognising one 1920x1080 monitor on a DisplayPort. ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-418 (Ubuntu) ** Changed in: nvidia-graphics-drivers-418 (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/1834047 Title: External monitor not recognised Status in nvidia-graphics-drivers-418 package in Ubuntu: Incomplete Bug description: I have BenQ i do not know what number, but it is connected by HDMI to DVI cable. nvidia-driver-418 is version 418.56-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 24 16:20:03 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: als, master, 5.0.0-16-generic, x86_64: installed als, master, 5.0.0-17-generic, x86_64: installed nvidia, 418.56, 5.0.0-16-generic, x86_64: installed nvidia, 418.56, 5.0.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 [Zbook 17 G5 mobile workstation]) [103c:842f] MachineType: HP HP ZBook 17 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.00 dmi.board.name: 842D dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.00 dmi.chassis.asset.tag: 5CD8501DGX dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 17 dmi.product.name: HP ZBook 17 G5 dmi.product.sku: 4QH25EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/+source/nvidia-graphics-drivers-418/+bug/1834047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834032] Re: loosing wificontact
You say: * Often I receive the message : Problem in ubunt, do you want to send the messaage? * Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired by restarting the computer. But those are two separate issues. Please choose one issue you would like this bug to be about. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834032 Title: loosing wificontact Status in Ubuntu: Incomplete Bug description: Often I receive the message : Problem in ubunt, do you want to send the messaage? Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired by restarting the computer. This happens for all after changing a user and a moment of computersleep ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 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: Mon Jun 24 15:02:44 2019 DistUpgraded: 2019-05-03 22:15:55,047 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0492] InstallationDate: Installed on 2019-05-01 (53 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Latitude E6320 ProcEnviron: LANGUAGE=nl PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=cf82673b-3d94-436d-9879-0993332233ff ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-05-03 (51 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0GJF11 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn0GJF11:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6320 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1834032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834112] [NEW] the mouse stopped responding to commands
Public bug reported: the mouse stopped responding to commands ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Mon Jun 24 21:21:31 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-24-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 24 21:29:22 2019 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages 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/1834112 Title: the mouse stopped responding to commands Status in xorg package in Ubuntu: New Bug description: the mouse stopped responding to commands ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Mon Jun 24 21:21:31 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-24-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's
This bug was fixed in the package xorg-server - 2:1.19.6-1ubuntu4.3 --- xorg-server (2:1.19.6-1ubuntu4.3) bionic; urgency=medium * sync-i965-pciids.diff: Updated with Comet Lake id's. (LP: #1821863) -- Timo Aaltonen Fri, 31 May 2019 14:10:48 +0300 ** Changed in: xorg-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830859] Update Released
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1830859
Title:
new libseccomp 2.4 (in proposed) makes rebuilds need but not generate
a dependency to 2.4
Status in libseccomp package in Ubuntu:
Won't Fix
Status in qemu package in Ubuntu:
Triaged
Status in qemu source package in Disco:
Fix Released
Bug description:
[Impact]
* Just as of yesterday we have a new libseccomp in all releases.
This brings some new code and features which might impact packages.
For qemu being one of the few that is not so much a problem in many
cases. Prior to Disco we didn't have code in qemu using the new
libseccomp bits. In Eoan we can assume that libseccomp 2.4 (being
release level) will be installed.
But in Disco people might have installed and not updated libseccomp
but install/upgrade to a qemu that was built against that new
libseccomp. Due to that qemu will get a runtime dependency that is
not picked up automatically - this would break all qemu execution
being blocked by a failure to install seccomp filters.
* To fix that we will add an explicit versioned dependency to qemu to
make sure the rebuild will ensure that the right library version is
available.
* This is needed for qemu-system* which all depend on qemu-system-
common so to avoid too much noise changing all qemu-system* packages
the dependency it added there.
[Test Case]
* ensure that the qemu install will ensure that libseccomp2 (>= 2.4.1)
is also installed (not staying on 2.3)
* Then install qemu and run
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
which should not trigger this (when fixed)
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
[Regression Potential]
* Well, the regressions might be triggered by pushing the new
libseccomp, not by this dependency fixup. The security Team has
checked and this seems to be the only affected code in the archive.
So libseccomp was pushed to fix CVEs. I have thought if it is a
regression that users of qemu will now be forced to use the newer
libseccomp, but since it would be unusable without that is no
important argument. And it is strongly recommended to upgrade for
security reasons as well.
[Other Info]
* n/a
---
It started with some of my usual KVM checks and found them failing on Disco
with:
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
I realized it works on X/B/C/E but not in a D container
It worked ~4 weeks ago.
This test can be simplified to one command:
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
With strace I found different behavior:
Good:
[pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11>
[pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.44>
[pid 3487] 0.000250 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x55f2b7a5e2d0}) = 0 <0.000251>
Bad:
[pid 484] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.17>
[pid 484] 0.002680 seccomp(SECCOMP_GET_ACTION_AVAIL, 0,
[SECCOMP_RET_KILL_PROCESS]) = 0 <0.14>
[pid 484] 0.88 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.13>
The difference seems to come from being built against seccomp as in
Disco (2.3.3-3ubuntu2 = good) or Disco-proposed ( = bad).
The dependency on the built package stayed
libseccomp2 (>= 2.3.0)
It did not pick up 2.4 via e.g. shlibs.
If I install libseccomp2 2.4 from -proposed the issue is gone.
Strace now looks like:
[pid 1788]
[Touch-packages] [Bug 1821863] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Committed Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830859] Re: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4
This bug was fixed in the package qemu - 1:3.1+dfsg-2ubuntu3.2
---
qemu (1:3.1+dfsg-2ubuntu3.2) disco; urgency=medium
* d/p/ubuntu/define-ubuntu-machine-types.patch: fix wily machine type being
broken since 2.11 due to 2.3/2.4 version mismatch in its definition to
fix migrations from old machines (LP: #1829868).
* d/p/ubuntu/lp-1830704-s390x-cpumodel-ignore-csske-for-expansion.patch
toleration for future machines (LP: #1830704
* d/control-in, d/control: add versioned dependencies to libseccomp 2.4 as
any rebuild against 2.4 as it is in proposed right now will otherwise
crash (LP: #1830859).
-- Christian Ehrhardt Tue, 28 May
2019 10:52:47 +0200
** Changed in: qemu (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1830859
Title:
new libseccomp 2.4 (in proposed) makes rebuilds need but not generate
a dependency to 2.4
Status in libseccomp package in Ubuntu:
Won't Fix
Status in qemu package in Ubuntu:
Triaged
Status in qemu source package in Disco:
Fix Released
Bug description:
[Impact]
* Just as of yesterday we have a new libseccomp in all releases.
This brings some new code and features which might impact packages.
For qemu being one of the few that is not so much a problem in many
cases. Prior to Disco we didn't have code in qemu using the new
libseccomp bits. In Eoan we can assume that libseccomp 2.4 (being
release level) will be installed.
But in Disco people might have installed and not updated libseccomp
but install/upgrade to a qemu that was built against that new
libseccomp. Due to that qemu will get a runtime dependency that is
not picked up automatically - this would break all qemu execution
being blocked by a failure to install seccomp filters.
* To fix that we will add an explicit versioned dependency to qemu to
make sure the rebuild will ensure that the right library version is
available.
* This is needed for qemu-system* which all depend on qemu-system-
common so to avoid too much noise changing all qemu-system* packages
the dependency it added there.
[Test Case]
* ensure that the qemu install will ensure that libseccomp2 (>= 2.4.1)
is also installed (not staying on 2.3)
* Then install qemu and run
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
which should not trigger this (when fixed)
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
[Regression Potential]
* Well, the regressions might be triggered by pushing the new
libseccomp, not by this dependency fixup. The security Team has
checked and this seems to be the only affected code in the archive.
So libseccomp was pushed to fix CVEs. I have thought if it is a
regression that users of qemu will now be forced to use the newer
libseccomp, but since it would be unusable without that is no
important argument. And it is strongly recommended to upgrade for
security reasons as well.
[Other Info]
* n/a
---
It started with some of my usual KVM checks and found them failing on Disco
with:
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
I realized it works on X/B/C/E but not in a D container
It worked ~4 weeks ago.
This test can be simplified to one command:
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
With strace I found different behavior:
Good:
[pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11>
[pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.44>
[pid 3487] 0.000250 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x55f2b7a5e2d0}) = 0 <0.000251>
Bad:
[pid 484] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.17>
[pid 484] 0.002680 seccomp(SECCOMP_GET_ACTION_AVAIL, 0,
[SECCOMP_RET_KILL_PROCESS]) = 0 <0.14>
[pid 484] 0.88 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.13>
The difference seems to come from
[Touch-packages] [Bug 1820068] Re: specifying -O no-expr-simplify results in cache miss
FYI, I tested this and 2.13.2-9ubuntu6.1 fixes this bug. I also executed https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor (sans dbus optional bits) and everything passed. Lastly, I wanted to double check the performance impact of no-expr- simplify on amd64 especially as it pertains to cloud and found it was slightly faster for default cloud, lxd and server policy. (It was slower on desktop, as expected and in the expected way due to the somewhat pathological evince profile. This has been the historical acceptable tradeoff to help ARM devices (note that because no-expr- simplify is faster with snap policy, with a handful of additional snaps, desktop breaks even then eventually gets faster too). ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1820068 Title: specifying -O no-expr-simplify results in cache miss Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Disco: Fix Committed Status in apparmor source package in Eoan: Fix Released Bug description: [Impact] * AppArmor 2.13 unconditionally invalidates its cache when parser options are specified. To decrease compile times for ARM systems, -O no-expr-simplify has been used in Ubuntu for click and snap policy for many years, but was temporarily disabled during the disco development release with the 2.13 upload so caching properly worked everywhere. Now that a simple upstream workaround is available (and already in eoan), we'd like to apply the upstream patch and re-enable -O no-expr-simplify. * A condition of the AppArmor 2.13 feature freeze exception was to fix this bug in SRU to re-enable -O no-expr-simplify. This will help compile times for all architectures with default and typical AppArmor policy (ie, a mixture of (distro) system and snap policy), but especially ARM systems with snaps where the improvement could be in terms of minutes saved. * Specifically, the upstream patch workaround to no longer unconditionally skip reading the cache when parser options are specified. It also re-enables an existing quilt patch to update /etc/apparmor/parser.conf to use no-expr-simplify. [Test Case] # setup $ mkdir -p /tmp/aa/cache /tmp/aa/profiles $ cp /etc/apparmor.d/sbin.dhclient /tmp/aa/profiles/ # no options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # no options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache hit: /tmp/aa/cache/26b63962.0/sbin.dhclient # reset $ rm -rf /tmp/aa/cache/* # options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient # SHOULD BE A HIT Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient Same thing happens if omitting -O no-expr-simplify but add Optimize =no-expr-simplify to /etc/apparmor/parser.conf. [Regression Potential] The regression potential is considered low since the patch is simple and easily verifiable. If something went wrong, it would be around cache invalidation which the above test case will demonstrate it works correctly. # Original description With 2.13.2 and the most recent testsuite patches from the 2.13 branch, I find that the cache works correctly when no options are specified. Eg # setup $ mkdir -p /tmp/aa/cache /tmp/aa/profiles $ cp /etc/apparmor.d/sbin.dhclient /tmp/aa/profiles/ # no options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # no options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location
[Touch-packages] [Bug 1825001] Re: Allow archives to send a 4xx response to tell apt to try again later
** Tags removed: rls-ee-incoming ** Changed in: apt (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1825001 Title: Allow archives to send a 4xx response to tell apt to try again later Status in apt package in Ubuntu: Fix Released Bug description: As part of a broad plan to improve our ability to manage traffic to the archive servers, it would be useful if the archives could return a 4xx response to indicate to apt that they were over capacity and it should try again later, where later could be defined on the client side as several hours, the next day for unattended-upgrades runs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829077] Re: disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4
Hello, I didn't reach to start with this new 5.2 kernel ! I installed the 4 .deb packages for my amd64 computer without error message ; I updated Grub (and the kernel 5.2 is in the list) but when I start, in Grub, the kernel 5.2 doesn't appear ! I have uninstalled VirtualBox : no effect I'm not used to that at all and I don't understand what to do... Sorry. -- 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/1829077 Title: disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4 Status in systemd package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. When I choose "Power Off", it closes the session screen but then it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 645404] Re: Support Private PPAs
I changed the MP over to 'Needs Review' as I think the code is in a state ready for review. Note that I removed the --remote support from it; while that is definitely something that should be added, I believe it's separate and complex enough it should be done separately, later. -- 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/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Cosmic: In Progress Status in software-properties source package in Disco: In Progress Status in software-properties source package in Eoan: In Progress Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833237] Re: skiboot ftbfs in eoan
** Changed in: binutils Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1833237 Title: skiboot ftbfs in eoan Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Status in skiboot package in Ubuntu: Confirmed Status in binutils source package in Eoan: Confirmed Status in skiboot source package in Eoan: Confirmed Bug description: skiboot ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17038512/+files/buildlog_ubuntu-eoan- amd64.skiboot_6.2-1_BUILDING.txt.gz powerpc64-linux-gnu-gcc-I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -D__ASSEMBLY__ -mbig-endian -m64 -mabi=elfv1 -c asm/dummy_map.S -o asm/dummy_map.o powerpc64-linux-gnu-gcc -I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -P -E skiboot.lds.S -o skiboot.lds powerpc64-linux-gnu-ld -EB -m elf64ppc --no-multi-toc -N --build-id=none --whole-archive -static -nostdlib -pie -Ttext-segment=0x0 --oformat=elf64-powerpc -o skiboot.tmp.elf -T skiboot.lds skiboot.tmp.a asm/dummy_map.o powerpc64-linux-gnu-ld: BFD (GNU Binutils for Ubuntu) 2.32.51.20190614 internal error, aborting at ../../bfd/elf64-ppc.c:15381 in ppc64_elf_relocate_section powerpc64-linux-gnu-ld: Please report this bug. make[2]: *** [/<>/Makefile.main:262: skiboot.tmp.elf] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:19: override_dh_auto_build-indep] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1833237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833237]
Fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1833237 Title: skiboot ftbfs in eoan Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Status in skiboot package in Ubuntu: Confirmed Status in binutils source package in Eoan: Confirmed Status in skiboot source package in Eoan: Confirmed Bug description: skiboot ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17038512/+files/buildlog_ubuntu-eoan- amd64.skiboot_6.2-1_BUILDING.txt.gz powerpc64-linux-gnu-gcc-I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -D__ASSEMBLY__ -mbig-endian -m64 -mabi=elfv1 -c asm/dummy_map.S -o asm/dummy_map.o powerpc64-linux-gnu-gcc -I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -P -E skiboot.lds.S -o skiboot.lds powerpc64-linux-gnu-ld -EB -m elf64ppc --no-multi-toc -N --build-id=none --whole-archive -static -nostdlib -pie -Ttext-segment=0x0 --oformat=elf64-powerpc -o skiboot.tmp.elf -T skiboot.lds skiboot.tmp.a asm/dummy_map.o powerpc64-linux-gnu-ld: BFD (GNU Binutils for Ubuntu) 2.32.51.20190614 internal error, aborting at ../../bfd/elf64-ppc.c:15381 in ppc64_elf_relocate_section powerpc64-linux-gnu-ld: Please report this bug. make[2]: *** [/<>/Makefile.main:262: skiboot.tmp.elf] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:19: override_dh_auto_build-indep] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1833237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830914] Re: software-properties-gtk does not run at all!
The software-properties-gtk starts, but the last tab (which is a new
tab), captioned "Livepatch", does not work.
The text says "Checking availability...", then, after a while an
"internal error detected" dialog comes up.
So "livepatch" does not work (at least does not seem to).
--
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/1830914
Title:
software-properties-gtk does not run at all!
Status in software-properties package in Ubuntu:
New
Bug description:
software-properties-gtk does not even start!
$ software-properties-gtk --debug
ENABLED COMPS: {'universe', 'main'}
INTERNET COMPS: {'universe', 'main'}
MAIN SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
CHILD SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe', 'main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
CDROM SOURCES
SOURCE CODE SOURCES
DISABLED SOURCES
ISV
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 200, in __init__
self.init_livepatch()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1482, in init_livepatch
self.livepatch_page = LivepatchPage(self)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line
51, in __init__
self._lps = LivepatchService()
File
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line
93, in __init__
self._session = requests_unixsocket.Session()
NameError: name 'requests_unixsocket' is not defined
{Exited with code 1.}
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
$ dpkg-query -l software-properties-gtk python3-requests-unixsocket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===---===
ii python3-requests-unixsocket 0.1.5-3 all Use requests to
talk HTTP via a UNIX domain socket - Python 3.x
ii software-properties-gtk 0.97.11 all manage the
repositories that you install software from (gtk)
$ sudo apt-get update
{Works.}
$ sudo apt-get dist-upgrade
{Works.}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
I'm also running into this bug (or at least something that looks like it). Typically what happens for me is that I resume from suspend, get an unlock prompt (the system is locked on suspend) and when I log in, the unlock prompt stays visible (the password dots disappear, but I cannot type anything or click any buttons). When I then kill X to recover (ctrl-alt-backspace), I get a new login prompt. Sometimes, logging in again no longer works then, seeing such messages in the console: jun 21 17:01:50 grubby at-spi-bus-launcher[30649]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1024" jun 21 17:01:50 grubby at-spi-bus-launcher[30649]: after 21 requests (21 known processed) with 0 events remaining. jun 21 17:01:50 grubby gsd-power[30703]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-keyboard[30715]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-xsettings[30696]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-media-keys[30731]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby systemd-logind[1100]: Session c9 logged out. Waiting for processes to exit. jun 21 17:01:50 grubby gsd-clipboard[30695]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-color[30713]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gnome-shell[30633]: Connection to xwayland lost >From the messages, I suspect this might be the same problem as the original >poster. However, I'm not entirely sure if at-spi-bus-launcher is actually the culprit here. Could it be that that the xserver or xwayland (I'm not sure which - I'm using the GNOME xorg session since the wayland session doesn't work for me, but the log does talk about xwayland) crashes and that at-spi-bus-launcher is just the first process to find out (because it does so many requests maybe?). I've also seen some instances where at-spi-bus-launcher is not the first one in the log, and I've tried disabling at-spi-bus-launcher by masking it in systemd (not entirely sure if that really worked), but then I also think I saw a crash where at-spi-bus-launcher would not show up in the log at all. One additional observation: At some point during testing, while login would not work, I found a logged in session in some virtual terminal. After logging out that session, logins would work again as normal. I'm not entirely sure if there's a causal relationship there, nor where that logged in session came from (but I was testing with two different users to see if there was something in my homedir that triggered it, so perhaps it came from one of those tests...). Vague, but I wanted to mention this just in case it triggers an idea somewhere :-) As for reporting an upstream issue, that is probably a good idea, though I'm not entirely sure where the cause is. It's probably safe to say it is something in gnome, though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: Confirmed Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion:
[Touch-packages] [Bug 1833230] Re: aide ftbfs in eoan
both packages rebuilt. ** Changed in: e2fsprogs (Ubuntu) Status: New => Fix Released ** Changed in: aide (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1833230 Title: aide ftbfs in eoan Status in aide package in Ubuntu: Fix Released Status in e2fsprogs package in Ubuntu: Fix Released Bug description: aide ftbfs in eoan in a test rebuild: https://launchpadlibrarian.net/428245508/buildlog_ubuntu-eoan- amd64.aide_0.16.1-1_BUILDING.txt.gz gcc -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -W -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -static -o aide src/aide.o src/base64.o src/be.o src/commandconf.o src/compare_db.o src/conf_lex.o src/conf_yacc.o src/db.o src/db_disk.o src/db_file.o src/db_lex.o src/db_list.o src/db_sql.o src/do_md.o src/error.o src/gen_list.o src/getopt1.o src/getopt.o src/list.o src/md.o src/snprintf.o src/symboltable.o src/util.o -lm -lpcre -pthread -lmhash -lacl -lselinux -laudit -lcap-ng -lattr -le2p -lz /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libcap-ng.a(cap-ng.o): in function `capng_change_id': (.text+0x193e): warning: Using 'initgroups' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libacl.a(la-__acl_to_any_text.o): in function `__acl_to_any_text': (.text+0x909): warning: Using 'getgrgid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libaudit.a(libaudit.o): in function `audit_rule_fieldpair_data': (.text+0x2194): warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: (.text+0x25d4): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libacl.a(la-__acl_to_any_text.o): in function `__acl_to_any_text': (.text+0x693): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libaudit.a(audit_logging.o): in function `_resolve_addr': (.text+0x8f): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking lto1: fatal error: bytecode stream in file ‘/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libe2p.a’ generated with LTO version 7.1 instead of the expected 7.2 compilation terminated. lto-wrapper: fatal error: gcc returned 1 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status make[3]: *** [Makefile:595: aide] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1833230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834055] [NEW] Cannot run Update-Manager 1:18.04.11.10 + Segmentation fault
Public bug reported: Hi! I updated some packages + to kernel 4.15.0-52-generic in Ubuntu-Mate. After that I can't open the "Update-Manager + software-properties-gtk" anymore. Terminal Output: Segmentation fault Kern.log: Jun 24 17:29:35 user1 kernel: [ 3571.244993] update-manager[14392]: segfault at b0 ip 7f2f39904ac8 sp 7f2f0f64e880 error 4 in ld-2.27.so[7f2f398f8000+27000] "ld-2.27.so" I have started a post here, but anyone can't help me to fix that error. https://ubuntu-mate.community/t/cant-update-upgrade-anymore-um-18-04-v2-lts/19745/19 How can I fix that? Please help, thanks! ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: fault ld-2.27.so segmentation update-manager -- 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/1834055 Title: Cannot run Update-Manager 1:18.04.11.10 + Segmentation fault Status in update-manager package in Ubuntu: New Bug description: Hi! I updated some packages + to kernel 4.15.0-52-generic in Ubuntu-Mate. After that I can't open the "Update-Manager + software-properties-gtk" anymore. Terminal Output: Segmentation fault Kern.log: Jun 24 17:29:35 user1 kernel: [ 3571.244993] update-manager[14392]: segfault at b0 ip 7f2f39904ac8 sp 7f2f0f64e880 error 4 in ld-2.27.so[7f2f398f8000+27000] "ld-2.27.so" I have started a post here, but anyone can't help me to fix that error. https://ubuntu-mate.community/t/cant-update-upgrade-anymore-um-18-04-v2-lts/19745/19 How can I fix that? Please help, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1834055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834056] [NEW] Desktop background turns black/white on login after suspension
Public bug reported: It only happens on login after system has been suspended. Restarting X fixes it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-desktop 1.431 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 24 17:26:42 2019 InstallationDate: Installed on 2019-05-07 (47 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to disco on 2019-06-21 (2 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Bugged background is attached. The original background image is ubuntu default one" https://bugs.launchpad.net/bugs/1834056/+attachment/5272857/+files/bugged%20bg.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1834056 Title: Desktop background turns black/white on login after suspension Status in ubuntu-meta package in Ubuntu: New Bug description: It only happens on login after system has been suspended. Restarting X fixes it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-desktop 1.431 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 24 17:26:42 2019 InstallationDate: Installed on 2019-05-07 (47 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to disco on 2019-06-21 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1834056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834055] Re: Cannot run Update-Manager 1:18.04.11.10 + Segmentation fault
Here's is the Crash.log of Update-Manager. ** Attachment added: "crash.log" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1834055/+attachment/5272860/+files/crash.log ** Description changed: Hi! I updated some packages + to kernel 4.15.0-52-generic in Ubuntu-Mate. After that I can't open the "Update-Manager + software-properties-gtk" anymore. Terminal Output: Segmentation fault Kern.log: Jun 24 17:29:35 user1 kernel: [ 3571.244993] update-manager[14392]: segfault at b0 ip 7f2f39904ac8 sp 7f2f0f64e880 error 4 in ld-2.27.so[7f2f398f8000+27000] "ld-2.27.so" - Crash.log: - - I have started a post here, but anyone can't help me to fix that error. https://ubuntu-mate.community/t/cant-update-upgrade-anymore-um-18-04-v2-lts/19745/19 How can I fix that? Please help, thanks! ** Package changed: apt (Ubuntu) => update-manager (Ubuntu) -- 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/1834055 Title: Cannot run Update-Manager 1:18.04.11.10 + Segmentation fault Status in update-manager package in Ubuntu: New Bug description: Hi! I updated some packages + to kernel 4.15.0-52-generic in Ubuntu-Mate. After that I can't open the "Update-Manager + software-properties-gtk" anymore. Terminal Output: Segmentation fault Kern.log: Jun 24 17:29:35 user1 kernel: [ 3571.244993] update-manager[14392]: segfault at b0 ip 7f2f39904ac8 sp 7f2f0f64e880 error 4 in ld-2.27.so[7f2f398f8000+27000] "ld-2.27.so" I have started a post here, but anyone can't help me to fix that error. https://ubuntu-mate.community/t/cant-update-upgrade-anymore-um-18-04-v2-lts/19745/19 How can I fix that? Please help, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1834055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834053] [NEW] PCI/internal sound card not detected
Public bug reported: No sound as my pc does not detect sound hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 24 20:39:45 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-11-06 (960 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2019-06-24 (0 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834053 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No sound as my pc does not detect sound hardware ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 24 20:39:45 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-11-06 (960 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2019-06-24 (0 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812904] Re: [FTBFS] Doesn't compile with gtk-doc >=1.26 (Disco)
** Tags added: bionic cosmic eoan ** Summary changed: - [FTBFS] Doesn't compile with gtk-doc >=1.26 (Disco) + [FTBFS] Doesn't compile with gtk-doc >=1.26 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1812904 Title: [FTBFS] Doesn't compile with gtk-doc >=1.26 Status in hud package in Ubuntu: Confirmed Bug description: Gtkdoc-mktmpl was removed from gtk-doc 1.26. Instead use GtkDocConfig.cmake provided by gtk-doc-tools. See: https://github.com/GNOME/gtk- doc/commit/46df4354abed5724697fd5e39630c5bbc6637cc4#diff- 6023128f8e440b483f85968b0db7799e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1812904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834047] [NEW] External monitor not recognised
Public bug reported: I have BenQ i do not know what number, but it is connected by HDMI to DVI cable. nvidia-driver-418 is version 418.56-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 24 16:20:03 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: als, master, 5.0.0-16-generic, x86_64: installed als, master, 5.0.0-17-generic, x86_64: installed nvidia, 418.56, 5.0.0-16-generic, x86_64: installed nvidia, 418.56, 5.0.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 [Zbook 17 G5 mobile workstation]) [103c:842f] MachineType: HP HP ZBook 17 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q70 Ver. 01.07.00 dmi.board.name: 842D dmi.board.vendor: HP dmi.board.version: KBC Version 15.37.00 dmi.chassis.asset.tag: 5CD8501DGX dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 17 dmi.product.name: HP ZBook 17 G5 dmi.product.sku: 4QH25EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu ** Attachment added: "journalctl output" https://bugs.launchpad.net/bugs/1834047/+attachment/5272831/+files/jcl.txt -- 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/1834047 Title: External monitor not recognised Status in xorg package in Ubuntu: New Bug description: I have BenQ i do not know what number, but it is connected by HDMI to DVI cable. nvidia-driver-418 is version 418.56-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 24 16:20:03 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: als, master, 5.0.0-16-generic, x86_64: installed als, master, 5.0.0-17-generic, x86_64: installed nvidia, 418.56, 5.0.0-16-generic, x86_64: installed nvidia, 418.56, 5.0.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 [Zbook 17 G5 mobile workstation])
[Touch-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen flashes
*** This bug is a duplicate of bug 1826125 *** https://bugs.launchpad.net/bugs/1826125 I agree with mactyr that this should not be a duplicate of that bug. The flaw that I see is not what is shown in those videos. There is no glitching, it is the whole screen flashing brighter, and is why I used the word "flashes" in the title, as opposed to "flickers" or "glitches". -- 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/1827790 Title: Dell XPS 13 9380 - Screen flashes Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 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/+source/xorg/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
Following call with IBM, verification testing is in progress. Hoping to have test results posted in the next 24 hours (approx). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Cosmic: Fix Committed Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu
[Touch-packages] [Bug 1695876] Re: German Documentation file displays incorrect CUPS version
** Tags removed: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1695876 Title: German Documentation file displays incorrect CUPS version Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: In Progress Bug description: The /doc/de/index.html.in file in the package source has an incorrect version number written into a header instead of using '@CUPS_VERSION@' to populate this file as in the other languages' version of the same file, seemingly resulting in /usr/share/cups/doc-root/de/index.html having the wrong version once CUPS is installed: ... CUPS 2.0.2 ... instead of: ... CUPS @CUPS_VERSION@ ... resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1695876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834036] Re: [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded on TravelMate X514-51
** Attachment added: "Ubuntu bug #1834036 reproducing recording.ogg" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834036/+attachment/5272830/+files/Ubuntu%20bug%20%231834036%20reproducing%20recording.ogg -- 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/1834036 Title: [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded on TravelMate X514-51 Status in alsa-driver package in Ubuntu: New Bug description: On TravelMate X514-51 the microphone is detected but only staticky noises are recorded. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buo.ren.lin 7028 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 24 21:24:17 2019 InstallationDate: Installed on 2019-05-08 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: 內部音效 - HDA Intel PCH Symptom_Type: High background noise, or volume is too low Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.name: Crux_WL dmi.board.vendor: WL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd01/24/2019:svnAcer:pnTravelMateX514-51:pvrV1.04:rvnWL:rnCrux_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: TravelMate X5 dmi.product.name: TravelMate X514-51 dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834036] [NEW] [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded on TravelMate X514-51
Public bug reported: On TravelMate X514-51 the microphone is detected but only staticky noises are recorded. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buo.ren.lin 7028 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 24 21:24:17 2019 InstallationDate: Installed on 2019-05-08 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: 內部音效 - HDA Intel PCH Symptom_Type: High background noise, or volume is too low Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.name: Crux_WL dmi.board.vendor: WL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd01/24/2019:svnAcer:pnTravelMateX514-51:pvrV1.04:rvnWL:rnCrux_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: TravelMate X5 dmi.product.name: TravelMate X514-51 dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834036 Title: [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded on TravelMate X514-51 Status in alsa-driver package in Ubuntu: New Bug description: On TravelMate X514-51 the microphone is detected but only staticky noises are recorded. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buo.ren.lin 7028 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 24 21:24:17 2019 InstallationDate: Installed on 2019-05-08 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: 內部音效 - HDA Intel PCH Symptom_Type: High background noise, or volume is too low Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.name: Crux_WL dmi.board.vendor: WL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd01/24/2019:svnAcer:pnTravelMateX514-51:pvrV1.04:rvnWL:rnCrux_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: TravelMate X5 dmi.product.name: TravelMate X514-51 dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834032] [NEW] loosing wificontact
Public bug reported: Often I receive the message : Problem in ubunt, do you want to send the messaage? Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired by restarting the computer. This happens for all after changing a user and a moment of computersleep ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 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: Mon Jun 24 15:02:44 2019 DistUpgraded: 2019-05-03 22:15:55,047 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0492] InstallationDate: Installed on 2019-05-01 (53 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Latitude E6320 ProcEnviron: LANGUAGE=nl PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=cf82673b-3d94-436d-9879-0993332233ff ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-05-03 (51 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0GJF11 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn0GJF11:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6320 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 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/1834032 Title: loosing wificontact Status in xorg package in Ubuntu: New Bug description: Often I receive the message : Problem in ubunt, do you want to send the messaage? Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired by restarting the computer. This happens for all after changing a user and a moment of computersleep ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 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: Mon Jun 24 15:02:44 2019 DistUpgraded: 2019-05-03 22:15:55,047 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0492] InstallationDate: Installed on 2019-05-01 (53 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Latitude E6320 ProcEnviron: LANGUAGE=nl PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=cf82673b-3d94-436d-9879-0993332233ff ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-05-03 (51 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0GJF11 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1830914] Re: software-properties-gtk does not run at all!
I found that if I move a bit the "import requests_unixsocket" line (in file
LivepatchService.py), then the software-properties-gtk call *works*.
Please somebody either propagate this solution (if it is a true solution), or
tell me how to propagate.
(I do not know shat is exactly happening. Whether the try-clause partly
succeeds, then rolls back?..)
$ sudo -s
# cd /usr/lib/python3/dist-packages/softwareproperties
# diff -u4 LivepatchService.py.ORI LivepatchService.py.MY
--- LivepatchService.py.ORI 2019-06-24 14:46:07.0 +0200
+++ LivepatchService.py.MY 2019-06-24 14:54:31.0 +0200
@@ -23,13 +23,12 @@
import logging
import gi
from gi.repository import Gio, GLib, GObject
+import requests_unixsocket
try:
import dateutil.parser
-import requests_unixsocket
-
gi.require_version('Snapd', '1')
from gi.repository import Snapd
except(ImportError, ValueError):
pass
# cp LivepatchService.py.MY LivepatchService.py
$ software-properties-gtk
{OK, works! The dialog is popping up.}
--
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/1830914
Title:
software-properties-gtk does not run at all!
Status in software-properties package in Ubuntu:
New
Bug description:
software-properties-gtk does not even start!
$ software-properties-gtk --debug
ENABLED COMPS: {'universe', 'main'}
INTERNET COMPS: {'universe', 'main'}
MAIN SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
CHILD SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe', 'main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
CDROM SOURCES
SOURCE CODE SOURCES
DISABLED SOURCES
ISV
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 200, in __init__
self.init_livepatch()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1482, in init_livepatch
self.livepatch_page = LivepatchPage(self)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line
51, in __init__
self._lps = LivepatchService()
File
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line
93, in __init__
self._session = requests_unixsocket.Session()
NameError: name 'requests_unixsocket' is not defined
{Exited with code 1.}
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
$ dpkg-query -l software-properties-gtk python3-requests-unixsocket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===---===
ii python3-requests-unixsocket 0.1.5-3 all Use requests to
talk HTTP via a UNIX domain socket - Python 3.x
ii software-properties-gtk 0.97.11 all manage the
repositories that you install software from (gtk)
$ sudo apt-get update
{Works.}
$ sudo apt-get dist-upgrade
{Works.}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Dimitri John Ledkov (xnox) wrote on 2019-06-19:
> Have you tried openssl 1.1.1-1ubuntu2.1~18.04.3 from bionic proposed?
I can confirm that 1.1.1-1ubuntu2.1~18.04.3 (already released a couple
of days ago) fixes the issue. Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
Status in libwww-perl package in Ubuntu:
Fix Released
Status in openssl package in Ubuntu:
Fix Released
Status in libio-socket-ssl-perl source package in Bionic:
Fix Released
Status in libnet-ssleay-perl source package in Bionic:
Fix Released
Status in libwww-perl source package in Bionic:
Fix Released
Status in openssl source package in Bionic:
Fix Released
Status in python-cryptography source package in Bionic:
Fix Released
Status in python-tornado source package in Bionic:
Fix Released
Status in python2.7 source package in Bionic:
Fix Released
Status in python3.6 source package in Bionic:
Fix Released
Status in python3.7 source package in Bionic:
Fix Released
Status in r-cran-openssl source package in Bionic:
Fix Released
Status in ruby-openssl source package in Bionic:
Fix Released
Status in ruby2.5 source package in Bionic:
Fix Released
Bug description:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
be rapidly adopted due to increased set of supported hashes & algoes,
as well as improved handshake [re-]negotiation.
* OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
* OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
software is sensitive to the negotiation handshake and may either need
patches/improvements or clamp-down to maximum v1.2.
[Test Case]
* Rebuild all reverse dependencies
* Execute autopkg tests for all of them
* Clamp down to TLS v1.2 software that does not support TLS v1.3
(e.g. mongodb)
* Backport TLS v1.3 support patches, where applicable
[Test cases for the python updates]
python3.7 is a preview in bionic as a non-supported/non-default
version of python3. Passing it's own autopkgtests is sufficient
validation for python3.7. It includes a point release update, with
OpenSSL 1.1.1 compat and features.
python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
also includes a point release update to 3.6.8. It has been part of the
full-archive rebuild and regression analysis. Autopkgtests were
triggered for python3.6 and python3-defaults with regressions already
fixed in the individual packages as appropriate.
python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
compat only. It has been part of the full-archive rebuild and
regression analysis. Autopkgtests were triggered for python2.7 and
python-defaults with regressions already fixed in the individual
packages as appropriate.
The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1
and python point releases as seen in:
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html
And analyzed in
https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652
[ Test case libwww-perl (and deps) regression ]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034
1. apt install liblwp-protocol-https-perl
2. enable -proposed
3. apt install libio-socket-ssl-perl libnet-ssleay-perl
4. perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com;, { data => "foo" }) or die'
[Regression Potential]
* Connectivity interop is the biggest issues which will be
unavoidable with introducing TLS v1.3. However, tests on cosmic
demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
negotiate TLS v1.3 without issues.
* Mitigation of discovered connectivity issues will be possible by
clamping down to TLS v1.2 in either server-side or client-side
software or by backporting relevant support fixes
* Notable changes are listed here
https://wiki.openssl.org/index.php/TLS1.3
* Most common connectivity issues so far:
- client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname.
Solution is client change to set hostname, or to clamp down the client to
TLSv1.2.
- session negotiation is different in TLSv1.3, existing client code
may fail to create/negotiate/resume session. Clients need to learn how
to use session callback.
- non-application data records. TLSv1.3 sends more of these, when compared
with previous versions, and some applications may not handle this correctly.
Resulting in application data not
[Touch-packages] [Bug 857472] Re: net-update verifcation checking insecure
** Tags added: id-5d106c1d683546484e9cb04e -- 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/857472 Title: net-update verifcation checking insecure Status in apt package in Ubuntu: Fix Released Status in apt source package in Oneiric: Fix Released Bug description: From: http://seclists.org/fulldisclosure/2011/Sep/222 its easy to bypass the verification checking in apt-key net-update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/857472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820068] Re: specifying -O no-expr-simplify results in cache miss
Hello Jamie, or anyone else affected, Accepted apparmor into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/2.13.2-9ubuntu6.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apparmor (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1820068 Title: specifying -O no-expr-simplify results in cache miss Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Disco: Fix Committed Status in apparmor source package in Eoan: Fix Released Bug description: [Impact] * AppArmor 2.13 unconditionally invalidates its cache when parser options are specified. To decrease compile times for ARM systems, -O no-expr-simplify has been used in Ubuntu for click and snap policy for many years, but was temporarily disabled during the disco development release with the 2.13 upload so caching properly worked everywhere. Now that a simple upstream workaround is available (and already in eoan), we'd like to apply the upstream patch and re-enable -O no-expr-simplify. * A condition of the AppArmor 2.13 feature freeze exception was to fix this bug in SRU to re-enable -O no-expr-simplify. This will help compile times for all architectures with default and typical AppArmor policy (ie, a mixture of (distro) system and snap policy), but especially ARM systems with snaps where the improvement could be in terms of minutes saved. * Specifically, the upstream patch workaround to no longer unconditionally skip reading the cache when parser options are specified. It also re-enables an existing quilt patch to update /etc/apparmor/parser.conf to use no-expr-simplify. [Test Case] # setup $ mkdir -p /tmp/aa/cache /tmp/aa/profiles $ cp /etc/apparmor.d/sbin.dhclient /tmp/aa/profiles/ # no options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # no options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache hit: /tmp/aa/cache/26b63962.0/sbin.dhclient # reset $ rm -rf /tmp/aa/cache/* # options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient # SHOULD BE A HIT Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient Same thing happens if omitting -O no-expr-simplify but add Optimize =no-expr-simplify to /etc/apparmor/parser.conf. [Regression Potential] The regression potential is considered low since the patch is simple and easily verifiable. If something went wrong, it would be around cache invalidation which the above test case will demonstrate it works correctly. # Original description With 2.13.2 and the most recent testsuite patches from the 2.13 branch, I find that the cache works correctly when no options are specified. Eg # setup $ mkdir -p /tmp/aa/cache /tmp/aa/profiles $ cp /etc/apparmor.d/sbin.dhclient
[Touch-packages] [Bug 1833230] Re: aide ftbfs in eoan
** Also affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1833230 Title: aide ftbfs in eoan Status in aide package in Ubuntu: New Status in e2fsprogs package in Ubuntu: New Bug description: aide ftbfs in eoan in a test rebuild: https://launchpadlibrarian.net/428245508/buildlog_ubuntu-eoan- amd64.aide_0.16.1-1_BUILDING.txt.gz gcc -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -W -Wall -g -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -static -o aide src/aide.o src/base64.o src/be.o src/commandconf.o src/compare_db.o src/conf_lex.o src/conf_yacc.o src/db.o src/db_disk.o src/db_file.o src/db_lex.o src/db_list.o src/db_sql.o src/do_md.o src/error.o src/gen_list.o src/getopt1.o src/getopt.o src/list.o src/md.o src/snprintf.o src/symboltable.o src/util.o -lm -lpcre -pthread -lmhash -lacl -lselinux -laudit -lcap-ng -lattr -le2p -lz /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libcap-ng.a(cap-ng.o): in function `capng_change_id': (.text+0x193e): warning: Using 'initgroups' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libacl.a(la-__acl_to_any_text.o): in function `__acl_to_any_text': (.text+0x909): warning: Using 'getgrgid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libaudit.a(libaudit.o): in function `audit_rule_fieldpair_data': (.text+0x2194): warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: (.text+0x25d4): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libacl.a(la-__acl_to_any_text.o): in function `__acl_to_any_text': (.text+0x693): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libaudit.a(audit_logging.o): in function `_resolve_addr': (.text+0x8f): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking lto1: fatal error: bytecode stream in file ‘/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libe2p.a’ generated with LTO version 7.1 instead of the expected 7.2 compilation terminated. lto-wrapper: fatal error: gcc returned 1 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status make[3]: *** [Makefile:595: aide] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1833230/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: amd64 linux-kvm sru-20190603 ubuntu-ltp-syscalls -- 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: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete 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 1833719] Re: UFW 2nd interface incorrectly working
Hello i added `sudo ufw insert 1 allow in on ens192 to any from any` sudo ufw reload and then reloaded my webpage on port 80 and its blocked. looking at logs I can see that that the right ip address for adapter is used but the logs show the incorrect adapter at IN= Thanks for lookin at this. ps I have got round this now by adding the rule that says `sudo ufw allow to **.**.**.46 from any` ** Attachment added: "ufw status numberd.PNG" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+attachment/5272739/+files/ufw%20status%20numberd.PNG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1833719 Title: UFW 2nd interface incorrectly working Status in ufw package in Ubuntu: Incomplete Bug description: ufw --version = ufw 0.36 Server has two interfaces ens160 and ens192 looking at the logs to understand why ufw is blocking requests from an interface, the log show the correct ip address and the incorrect interface. ip address 192.168.1.4 is on ens160 ip address 192.168.1.46 is on ens192 Correct when visiting address 192.168.1.4 i am blocked an logs correctly identify that i am using IN=ens160 Incorrect when visiting address 192.168.1.46 i am also blocked even though rule has been added "sudo ufw allow in on ens192 to any from 192.168.0.0/16" Logs from /var/log/ufw.log show that DST=192.168.1.46 is blocked witn IN=ens160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833719] Re: UFW 2nd interface incorrectly working
** Attachment added: "ufw logs.PNG" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+attachment/5272740/+files/ufw%20logs.PNG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1833719 Title: UFW 2nd interface incorrectly working Status in ufw package in Ubuntu: Incomplete Bug description: ufw --version = ufw 0.36 Server has two interfaces ens160 and ens192 looking at the logs to understand why ufw is blocking requests from an interface, the log show the correct ip address and the incorrect interface. ip address 192.168.1.4 is on ens160 ip address 192.168.1.46 is on ens192 Correct when visiting address 192.168.1.4 i am blocked an logs correctly identify that i am using IN=ens160 Incorrect when visiting address 192.168.1.46 i am also blocked even though rule has been added "sudo ufw allow in on ens192 to any from 192.168.0.0/16" Logs from /var/log/ufw.log show that DST=192.168.1.46 is blocked witn IN=ens160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833719] Re: UFW 2nd interface incorrectly working
** Attachment added: "ip r.PNG" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+attachment/5272741/+files/ip%20r.PNG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1833719 Title: UFW 2nd interface incorrectly working Status in ufw package in Ubuntu: Incomplete Bug description: ufw --version = ufw 0.36 Server has two interfaces ens160 and ens192 looking at the logs to understand why ufw is blocking requests from an interface, the log show the correct ip address and the incorrect interface. ip address 192.168.1.4 is on ens160 ip address 192.168.1.46 is on ens192 Correct when visiting address 192.168.1.4 i am blocked an logs correctly identify that i am using IN=ens160 Incorrect when visiting address 192.168.1.46 i am also blocked even though rule has been added "sudo ufw allow in on ens192 to any from 192.168.0.0/16" Logs from /var/log/ufw.log show that DST=192.168.1.46 is blocked witn IN=ens160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792027] Re: evince denied access to mimeapps.list
I get this upstream on Debian Stretch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1792027 Title: evince denied access to mimeapps.list Status in apparmor package in Ubuntu: New Bug description: I am receiving the following message in my logs. It appears that the apparmor profile for evince is too strict. Sep 11 14:17:13 bbn-11838 kernel: [275098.499551] audit: type=1400 audit(1536693433.724:1007): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/etc/xdg/mimeapps.list" pid=11797 comm="evince" requested_mask="r" denied_mask="r" fsuid=1832001200 ouid=0 I'm using Ubuntu 18.04. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt show evince Package: evince Version: 3.28.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1792027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832108] Re: unmkinitramfs fails with lz4 compressed initrds
Reproduce the problem: # dpkg-query -W initramfs-tools lz4 initramfs-tools 0.131ubuntu19 lz4 1.8.3-1ubuntu1 # sed -i 's/gzip/lz4/' /etc/initramfs-tools/initramfs.conf # update-initramfs -c -k test # lsinitramfs /boot/initrd.img-test cpio: premature end of archive === # sed 's/-updates/-proposed/' -i /etc/apt/sources.list # apt update # dpkg-query -W initramfs-tools lz4 initramfs-tools 0.131ubuntu19.1 lz4 1.8.3-1ubuntu1 # lsinitramfs /boot/initrd.img-test ... all the files are listed ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832108 Title: unmkinitramfs fails with lz4 compressed initrds Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: Fix Committed Status in initramfs-tools package in Debian: New Bug description: [Impact] * Cannot unpack initrds compressed with lz4 due to changes in lz4 [Test Case] $ sudo apt install initramfs-tools lz4 file $ mkinitramfs -c lz4 -o foo.img $ lsinitramfs foo.img cpio: premature end of archive [Regression Potential] * New lz4cat is more strict w.r.t. enforcing file name extensions, thus the fix is to feed a stream to lz4cat instead of asking it to open a file. The performance impact should be similar between both methods of reading file contents during ls/unmk-initramfs time. [Other Info] Original bug report: unmkinitramfs fails with lz4 compressed initrds Note: $ lz4cat -t unmkinitramfs_Cz6Yl9 File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process file: unmkinitramfs_Cz6Yl9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
verification-needed-cosmic is blocking publishing the next initramfs- tools update in cosmic. Am I ok to trump the current initramfs-tools in cosmic-proposed with a new upload? Do we want to back out this change? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Cosmic: Fix Committed Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652]
[Touch-packages] [Bug 1833758] Re: lvm2: vgcfgbackup in postinst takes several minutes
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1833758 Title: lvm2: vgcfgbackup in postinst takes several minutes Status in lvm2 package in Ubuntu: New Bug description: The postinst for lvm2 includes a call to vgcfgbackup; in the version included in eoan 2.03.02-2ubuntu4 (and 2.03.02-2ubuntu3 before it), this command takes several minutes to run when invoked in an schroot as happens when a building a package with sbuild that ends up pulling lvm2 as part of its build dependency chain. An example package with lvm2 in its build depends is rsnapshot, but this behavior was seen with a build of glibc. Some notes: - this behavior is NOT seen with the version of lvm2 in disco. - this happens in bionic with a 4.15 kernel and disco with a 5.0 kernel (different hosts, so different sets of block devices) - this happens regardless of whether the host is currently using logical volumes or not Here's the time difference between running the disco version and the eoan version: (disco-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Failed to connect to lvmetad. Falling back to device scanning. real0m0.204s user0m0.014s sys 0m0.010s (eoan-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Device /dev/sda not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. real4m11.405s user0m0.470s sys 0m0.576s /proc/mounts in the schroot: (eoan-amd64)root@HOSTNAME:~# cat /proc/mounts eoan-amd64 / overlay rw,relatime,lowerdir=/var/lib/schroot/union/underlay/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34,upperdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/upper,workdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/work 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=10197712k,nr_inodes=2549428,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 /dev/sda2 /home ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/sda2 /tmp ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /run/shm tmpfs rw,relatime 0 0 /dev/sda2 /scratch ext4
[Touch-packages] [Bug 1833536] Re: QuiteRSS crashes intermittently
** Also affects: qtbase-opensource-src (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: qtbase-opensource-src (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1833536 Title: QuiteRSS crashes intermittently Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: In Progress Status in qtbase-opensource-src source package in Disco: In Progress Bug description: [Impact] This bug affects QuiteRSS and other Qt applications, like plasma-discover (see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 1814375). All they crash with similar stack traces. [Test Case] 1. Open QuiteRSS. 2. Leave it running for several hours. 3. It should not crash. [Proposed Fix] The proposed fix is a backport of the following commit from upstream 5.12 branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db [Regression Potential] This patch adds an additional check before re-sending the request. Regressions chance is minimal, but the potential regressions may be that the request is not re-sent where it was re-sent with the previous code. [Original Description] After opening QuiteRSS it will run until crash happens. This happens intermittently within the hour usually. (gdb) bt #0 QHttpNetworkConnectionChannel::sendRequest (this=) at access/qhttpnetworkconnectionchannel.cpp:238 #1 0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest ( this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 #2 0x72736122 in QObject::event (this=0x7fff48da89b0, e=) at kernel/qobject.cpp:1247 #3 0x76f2482c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x727069a8 in QCoreApplication::notifyInternal2 ( receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) at kernel/qcoreapplication.cpp:1024 #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x7fff60008e90) at kernel/qcoreapplication.cpp:1699 #8 0x727096a8 in QCoreApplication::sendPostedEvents ( receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1553 #9 0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10) at kernel/qeventdispatcher_glib.cpp:276 #10 0x7fffece96317 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffece96550 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffece965dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7275f8ef in QEventDispatcherGlib::processEvents ( this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7252322a in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20) at thread/qthread_unix.cpp:368 #17 0x722646db in start_thread (arg=0x7fff4700) at pthread_create.c:463 #18 0x719ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
