[Touch-packages] [Bug 1998444] [NEW] Backport security fix for CVE-2022-3970
Public bug reported: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped) make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: /<>/workdir/CppunitTest/vcl_filters_test.test] Error 134 For the log of the failed amd64 kinetic archive build, see https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181 For the log of the successful amd64 kinetic PPA build with the updated tiff present, see https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/24886085 Lunar already includes this fix with the last merge from debian https://launchpad.net/ubuntu/+source/tiff/4.4.0-6ubuntu1 Presumably this fix is required for all supported stable releases. ** Affects: tiff (Ubuntu) Importance: Critical Status: New ** Affects: tiff (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: tiff (Ubuntu Focal) Importance: Undecided Status: New ** Affects: tiff (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: tiff (Ubuntu Kinetic) Importance: Critical Status: New ** Patch added: "tiff_4.4.0-4ubuntu3.2.debdiff" https://bugs.launchpad.net/bugs/1998444/+attachment/5633646/+files/diff ** Also affects: tiff (Ubuntu Bionic)
[Touch-packages] [Bug 1998321] Autopkgtest regression report (tzdata/2022g-0ubuntu0.20.04.0)
All autopkgtests for the newly accepted tzdata (2022g-0ubuntu0.20.04.0) for focal have finished running. The following regressions have been reported in tests triggered by the package: libical3/3.0.8-1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#tzdata [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Autopkgtest regression report (tzdata/2022g-0ubuntu0.22.04.0)
All autopkgtests for the newly accepted tzdata (2022g-0ubuntu0.22.04.0) for jammy have finished running. The following regressions have been reported in tests triggered by the package: chrony/4.2-2ubuntu2 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#tzdata [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1648890] Re: X Diagnostics
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1648890 Title: X Diagnostics Status in xorg package in Ubuntu: Expired Bug description: After running X Diagnostics I ran in to some reported bugs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.2 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: Fri Dec 9 22:34:13 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:0212] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:0212] InstallationDate: Installed on 2016-11-18 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: eMachines eMachines E525 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=d610160c-133b-4da2-b1f5-7fbdfda6271e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2009 dmi.bios.vendor: eMachines dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: eMachines E525 dmi.board.vendor: eMachines dmi.board.version: V2.06 dmi.chassis.type: 10 dmi.chassis.vendor: eMachines dmi.chassis.version: V2.06 dmi.modalias: dmi:bvneMachines:bvrV2.06:bd08/03/2009:svneMachines:pneMachinesE525:pvrV2.06:rvneMachines:rneMachinesE525:rvrV2.06:cvneMachines:ct10:cvrV2.06: dmi.product.name: eMachines E525 dmi.product.version: V2.06 dmi.sys.vendor: eMachines version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Dec 9 21:51:50 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4332 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1648890/+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 1444895] Re: xrandr --brightness resets gamma ratio
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1444895 Title: xrandr --brightness resets gamma ratio Status in xorg package in Ubuntu: Expired Bug description: $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 $ xrandr --output VGA1 --brightness .75 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.0 Brightness: 0.75 As can be seen in the above command output, changing the brightness with xrandr resets the gamma ratio to 1/1/1/ instead of 1/1/.6 (values in xrandr --verbose output are inverted...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444895/+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 1639017] Re: Unable to have Higher Resolution on Ubuntu 16.04
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1639017 Title: Unable to have Higher Resolution on Ubuntu 16.04 Status in xorg package in Ubuntu: Expired Bug description: Hi, I am only able to view the screen in 1024x768 resolution here is my output for lshw -c Video *-display description: VGA compatible controller product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:25 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) I think the xorg driver is fully updated but still I am unable to run in higher resolution on ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 CurrentDesktop: Unity Date: Fri Nov 4 00:33:25 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1458:d000] InstallationDate: Installed on 2016-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=361b7ddd-636c-40e8-98a4-6f7c6ceb1f69 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61MS dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd06/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61MS:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Nov 4 00:10:15 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639017/+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 1586787] Re: Wrong colors on external TV
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1586787 Title: Wrong colors on external TV Status in xorg package in Ubuntu: Expired Bug description: Hi, On a Lenovo Thinkpad T420, with an Intel Core i5-2520M CPU and integrated graphics, when using a Samsung UE40J5200AW 40in TV with a DisplayPort to HDMI adapter and an HDMI cable, the colors are very wrong on the TV. This happens on a brand new Ubuntu 16.04 installation made from scratch, and it does not happen when I boot from a Linux Mint 17.3 "Rosa" Cinnamon 64-bit live DVD. So same laptop, same adapter, same cable, same TV, and the colors are fine on the TV in this case (Mint live DVD). Also, when switching the laptop with a Dell running Windows 8.1 (so the same adapter, cable, and TV are used), the colors are again fine. I have attached a picture that shows the laptop screen in front of the TV screen with the display mirrored. So both screens should look the same in the picture. But it looks like only the white color is the same, while the rest of the colors are very different. Thanks for your help, Alin. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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: Sun May 29 17:47:11 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21ce] InstallationDate: Installed on 2016-05-06 (22 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 4236BH1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236BH1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236BH1:pvrThinkPadT420:rvnLENOVO:rn4236BH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236BH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun May 29 17:45:29 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 738 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586787/+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 1623518] Re: problemi accensione pc
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1623518 Title: problemi accensione pc Status in xorg package in Ubuntu: Expired Bug description: problemi scheda radeon Google translation: radeon card problems ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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: Wed Sep 14 15:48:44 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:184a] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2015-07-20 (422 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=c2b360dd-7125-486f-911b-14f23fa0bc6b ro plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 184A dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd02/21/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn184A:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Sep 14 15:47:08 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623518/+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 1635872] Re: xorg freezes for long time after using virtual terminal
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
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/1635872
Title:
xorg freezes for long time after using virtual terminal
Status in xorg package in Ubuntu:
Expired
Bug description:
Ubuntu: 16.04
xorg 1:7.7+13ubuntu3
Always reproducible, steps:
a) start computer
b) verify that Xorg is using some 0.7% CPU
c) f1+ctrl+shift #go to virtual terminal
d) f7+ctrl #back to the xorg
Maybe 60 seconds mouse cursor can be barely moved, but keyboard and clicks
are not responding after all. After that run script for monitoring CPU usage of
Xorg.
e)
while [ 1 ] ; do top -b -n 1 | grep Xorg | awk {'print $9'} ; sleep 1; done
CPU usage is almost 100% for 12...71 minutes and then calms down.
Not sure if this relates display controllers (lspci | grep VGA):
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M
Mac Edition] (rev a1)
Or drivers (lsmod | grep video):
video 40960 3 i915,nouveau,apple_gmux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635872/+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 1667881] Re: hdmi
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1667881 Title: hdmi Status in xorg package in Ubuntu: Expired Bug description: o sistema não reconhece a tyv, através da entrada/saída HDMI Google translation: the system does not recognize the tyv, through the hdmi input/output ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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: Sat Feb 25 01:16:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed i915-4.6.3-4.4.0, 1, 4.4.0-64-generic, x86_64: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2017-02-21 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NV55C ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=UUID=beab8c72-b619-44a3-a386-7c39ccfb2730 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: Gateway dmi.bios.version: V1.27 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NV55C dmi.board.vendor: Gateway dmi.board.version: V1.27 dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: V1.27 dmi.modalias: dmi:bvnGateway:bvrV1.27:bd11/09/2011:svnGateway:pnNV55C:pvrV1.27:rvnGateway:rnNV55C:rvrV1.27:cvnGateway:ct10:cvrV1.27: dmi.product.name: NV55C dmi.product.version: V1.27 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75+git1702140630.f6499b~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 17.1~git1702241930.983348~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1~git1702241930.983348~gd~x version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.99+git1702221933.244d4b~gd~x version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1702161933.860c36~gd~x version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13+git1701262001.1516d3~gd~x xserver.bootTime: Sat Feb 25 01:05:52 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 732 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1667881/+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 1667133] Re: touch is constantly jumping around (ghost touching)
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1667133 Title: touch is constantly jumping around (ghost touching) Status in xorg package in Ubuntu: Expired Bug description: The issue I am having is very similar to this bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667 Depending on what applications are running the apparently random behavior may increase. Sometimes it is really bad and several times in one second the system detects random touches around the screen. As a result Ubuntu automatically zooms in or out or moves the content of screen around or the focus is stolen. Right now as I am typing this bug I am getting very dizzy because the UI is constantly zooming in and out. I have noticed this happens a lot (A LOT!) more frequently when chrome is opened. I have tried removing a few xorg input packages as a desperate attempt to stop this: ``` sudo apt-get remove --purge xserver-xorg-input-libinput sudo apt-get remove --purge xserver-xorg-input-synaptics sudo apt-get remove --purge xserver-xorg-input-wacom ``` Right now my touch screen is not working and my touchpad never worked. I have plugged in an external mouse and it works, up until the focus gets stolen from it by random touches around the screen. Before I removed libinput mouse pointer was also jumping constantly to a random location. But since I remove libinput, mouse cursor stays where it is but random touches seems to be happening anyway. This is extremely annoying behavious and is rendering my laptop useless. I am using Acer Spin 5 ``` $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 0bda:57f3 Realtek Semiconductor Corp. Bus 001 Device 005: ID 2386:3111 Bus 001 Device 004: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 009: ID 05b8:3279 Agiler, Inc. Bus 001 Device 008: ID 17ef:6019 Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` ``` $ dmesg |grep touch [2.558494] hid-multitouch 0018:04F3:3018.0001: Ignoring the extra HID_DG_INPUTMODE [2.558662] hid-multitouch 0018:04F3:3018.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN0501:00 04F3:3018] on i2c-ELAN0501:00 [3.294025] hid-multitouch 0003:2386:3111.0006: input,hiddev0,hidraw1: USB HID v1.10 Device [Raydium Corporation Raydium Touch System] on usb-:00:14.0-6/input0 ``` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 CurrentDesktop: Unity Date: Wed Feb 22 13:35:35 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1139] InstallationDate: Installed on 2016-07-26 (211 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Spin SP513-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic.efi.signed root=UUID=45f1b204-27f6-467d-97ee-0d12b3b14388 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.name: Drift_SK dmi.board.vendor: KBL dmi.board.version: V1.02 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd10/20/2016:svnAcer:pnSpinSP513-51:pvrV1.02:rvnKBL:rnDrift_SK:rvrV1.02:cvnAcer:ct31:cvrV1.02: dmi.product.name: Spin SP513-51 dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
[Touch-packages] [Bug 1701349] Re: Nvidia display is slow
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1701349 Title: Nvidia display is slow Status in xorg package in Ubuntu: Expired Bug description: Applications display is slow, mouse movement is delayed and movies cannot be played smoothly but frame by frame. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 29 21:53:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated Graphics [1462:116b] Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 960M] [1462:116b] InstallationDate: Installed on 2017-04-12 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1770:ff00 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS60 6QC ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-56-generic root=UUID=4742493d-f9c1-4072-9d91-f07611aac5da ro nomodeset quiet splash vt.handoff=7 SourcePackage: xorg UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: Error: GLX is not available on the system UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H8IMS.111 dmi.board.asset.tag: Default string dmi.board.name: MS-16H8 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H8IMS.111:bd11/21/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS606QC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H8:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.name: GS60 6QC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jun 29 21:20:46 2017 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for (null): -22 Screen 0 deleted because of no matching config section. Failed to initialize GLX extension (Compatible NVIDIA X driver not found) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1701349/+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 1675680] Re: My graphic is not running well anymore
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1675680 Title: My graphic is not running well anymore Status in xorg package in Ubuntu: Expired Bug description: After trying to install Sonos i couldn't shut down the usual way anymore so i restarted after deleting successfully Xorg says hardware doesn't use grapic support correctly! Thanks for helping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 09:24:42 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller [17aa:3047] Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller [17aa:3047] InstallationDate: Installed on 2017-03-21 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 7628AE3 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=0f2ed734-4a52-4f76-89cf-87d23eac183e ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT46AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.asset.tag: S4AH163 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT46AUS:bd03/20/2009:svnLENOVO:pn7628AE3:pvrThinkCentreM58:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 7628AE3 dmi.product.version: ThinkCentre M58 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 24 09:20:40 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675680/+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 1696903] Re: 3d hardware problem
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1696903 Title: 3d hardware problem Status in xorg package in Ubuntu: Expired Bug description: Requested size (3200, 1080) exceeds 3D hardware limit (2048, 2048). You must either rearrange the displays so that they fit within a (2048, 2048) square. GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code3: Requested size (3200, 1080) exceeds 3D hardware limit (2048, 2048). You must either rearrange the displays so that they fit within a (2048, 2048) square. this is showing when trying to connect to tv ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 CurrentDesktop: Unity Date: Thu Jun 8 21:55:17 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [103c:30bb] Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [103c:30bb] InstallationDate: Installed on 2017-06-07 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP Pavilion dv6000 (RU696UA#ABL) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=01be26e4-ea37-4e70-9440-06c51957e7bb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.2E dmi.board.name: 30BB dmi.board.vendor: Quanta dmi.board.version: 66.42 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.2E:bd03/22/2010:svnHewlett-Packard:pnHPPaviliondv6000(RU696UA#ABL):pvrRev1:rvnQuanta:rn30BB:rvr66.42:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6000 (RU696UA#ABL) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jun 8 21:19:32 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13125 vendor SEC xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1696903/+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 1711231] Re: xdiagnose me trajo hasta aqui por algun problema de xorg (xdiagnose brought me here because of some xorg problem)
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1711231 Title: xdiagnose me trajo hasta aqui por algun problema de xorg (xdiagnose brought me here because of some xorg problem) Status in xorg package in Ubuntu: Expired Bug description: no se darles mas detalles Google translation: I don't know how to give you more details ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Wed Aug 16 19:15:53 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics [1043:196d] InstallationDate: Installed on 2017-06-12 (65 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 001 Device 003: ID 0bda:57bc Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X751LAB ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=c128aeae-24fb-4403-b895-02ae42e88920 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X751LAB.507 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X751LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX751LAB.507:bd12/07/2015:svnASUSTeKCOMPUTERINC.:pnX751LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X751LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 16 16:06:01 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1711231/+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 1993834] Re: Update evolution-data-server to 3.46.1
This bug was fixed in the package evolution-data-server - 3.46.1-1 --- evolution-data-server (3.46.1-1) unstable; urgency=medium * New upstream release (LP: #1993834) -- Jeremy Bicha Fri, 21 Oct 2022 11:32:50 -0400 ** Changed in: evolution-data-server (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1993834 Title: Update evolution-data-server to 3.46.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Kinetic: Fix Released Bug description: Impact -- This is a new stable release in the 3.46 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.46.1/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1993834/+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 1986521] Re: ssh client spins if output fd closed
** Description changed:
[Impact]
- In certain edge cases where the terminal goes away while an ssh process is
running, ssh can be left consuming 100% CPU. This increases processing costs
for cloud users and wastes energy.
+ In certain edge cases where the terminal goes away while an ssh process is
running, ssh can be left consuming 100% CPU. This increases processing costs
for cloud users and wastes energy. While this is an uncommon error, googling
indicates many people have run into it in several different ways. It seems
important to get this fixed in stable releases.
This is a regression in jammy presumably due to change from select() to
poll() (see OpennSSH 8.9 Release Announcement [1] ), fixed by upstream
commit d6556de1db0822c76ba2745cf5c097d9472adf7c "upstream: fix poll()
spin when a channel's output fd closes..." [2].
1: https://lwn.net/Articles/885886/
2.
https://github.com/openssh/openssh-portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c
[Test Case]
$ lxc launch ubuntu-daily:jammy ssh-cpu
$ lxc shell ssh-cpu
# passwd -d root
# ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa
# cat << EOF >>/etc/ssh/ssh_config
StrictHostKeyChecking accept-new
EOF
# sed -ri 's/^PasswordAuthentication/#PasswordAuthentication/'
/etc/ssh/sshd_config
# cat << EOF >>/etc/ssh/sshd_config
PermitRootLogin yes
PubkeyAuthentication yes
PermitEmptyPasswords yes
PasswordAuthentication yes
ChallengeResponseAuthentication no
UsePAM no
EOF
# systemctl restart sshd
# ssh localhost 2> >({exec 1>&2})
You can shell into the container from a second terminal and use "htop"
to verify that ssh is using 100% of one of the CPU cores:
$ lxc shell ssh-cpu
# htop
This should show one CPU pegged at 100% due to the 'ssh localhost'
process
Next, return to the first terminal, exit out of the sub-ssh session and
install the fix:
# logout
# add-apt-repository -yus ppa:bryce/openssh-sru-lp1986521
# apt-get full-upgrade -y
Now repeat the test in the first terminal window, while viewing htop in
the second terminal:
# ssh localhost 2> >({exec 1>&2})
[Where Problems Could Occur]
While the patch in question is well tested upstream, it has a relatively
high line count and as such is difficult to assure correctness by visual
code checking. However, it's not clear that the line count could be
significantly reduced without risking loss of correctness. Thus this
relies more on testing to assure robustness, than on code review.
The code involves polling behavior, so issues to watch for would more
likely involve process handling, i.e. problems with socket polling.
Beyond that, the usual generic issues to watch for - build issues,
dependency issues during build or on upgrade, and service restarting.
-
[Original Report]
The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the
bug described at
https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and
https://bugzilla.mindrot.org/show_bug.cgi?id=3405
A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
an xterm, ask for whatever authentication is needed, close the xterm,
and leave the ssh client spinning consuming CPU time for 60 seconds
before it exits. It should leave the ssh client idle for 60 seconds.
Many uses of ssh to launch graphical applications will be caught by this
bug.
This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its release
notes at https://www.openssh.com/txt/release-9.0
--
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/1986521
Title:
ssh client spins if output fd closed
Status in portable OpenSSH:
Unknown
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Jammy:
Triaged
Bug description:
[Impact]
In certain edge cases where the terminal goes away while an ssh process is
running, ssh can be left consuming 100% CPU. This increases processing costs
for cloud users and wastes energy. While this is an uncommon error, googling
indicates many people have run into it in several different ways. It seems
important to get this fixed in stable releases.
This is a regression in jammy presumably due to change from select()
to poll() (see OpennSSH 8.9 Release Announcement [1] ), fixed by
upstream commit d6556de1db0822c76ba2745cf5c097d9472adf7c "upstream:
fix poll() spin when a channel's output fd closes..." [2].
1: https://lwn.net/Articles/885886/
2.
https://github.com/openssh/openssh-portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c
[Test Case]
$ lxc launch ubuntu-daily:jammy ssh-cpu
$ lxc shell ssh-cpu
# passwd -d root
# ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa
# cat << EOF >>/etc/ssh/ssh_config
StrictHostKeyChecking accept-new
EOF
#
[Touch-packages] [Bug 1986521] Re: ssh client spins if output fd closed
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/openssh/+git/openssh/+merge/433911
--
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/1986521
Title:
ssh client spins if output fd closed
Status in portable OpenSSH:
Unknown
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Jammy:
Triaged
Bug description:
[Impact]
In certain edge cases where the terminal goes away while an ssh process is
running, ssh can be left consuming 100% CPU. This increases processing costs
for cloud users and wastes energy. While this is an uncommon error, googling
indicates many people have run into it in several different ways. It seems
important to get this fixed in stable releases.
This is a regression in jammy presumably due to change from select()
to poll() (see OpennSSH 8.9 Release Announcement [1] ), fixed by
upstream commit d6556de1db0822c76ba2745cf5c097d9472adf7c "upstream:
fix poll() spin when a channel's output fd closes..." [2].
1: https://lwn.net/Articles/885886/
2.
https://github.com/openssh/openssh-portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c
[Test Case]
$ lxc launch ubuntu-daily:jammy ssh-cpu
$ lxc shell ssh-cpu
# passwd -d root
# ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa
# cat << EOF >>/etc/ssh/ssh_config
StrictHostKeyChecking accept-new
EOF
# sed -ri 's/^PasswordAuthentication/#PasswordAuthentication/'
/etc/ssh/sshd_config
# cat << EOF >>/etc/ssh/sshd_config
PermitRootLogin yes
PubkeyAuthentication yes
PermitEmptyPasswords yes
PasswordAuthentication yes
ChallengeResponseAuthentication no
UsePAM no
EOF
# systemctl restart sshd
# ssh localhost 2> >({exec 1>&2})
You can shell into the container from a second terminal and use "htop"
to verify that ssh is using 100% of one of the CPU cores:
$ lxc shell ssh-cpu
# htop
This should show one CPU pegged at 100% due to the 'ssh localhost'
process
Next, return to the first terminal, exit out of the sub-ssh session and
install the fix:
# logout
# add-apt-repository -yus ppa:bryce/openssh-sru-lp1986521
# apt-get full-upgrade -y
Now repeat the test in the first terminal window, while viewing htop in
the second terminal:
# ssh localhost 2> >({exec 1>&2})
[Where Problems Could Occur]
While the patch in question is well tested upstream, it has a
relatively high line count and as such is difficult to assure
correctness by visual code checking. However, it's not clear that the
line count could be significantly reduced without risking loss of
correctness. Thus this relies more on testing to assure robustness,
than on code review.
The code involves polling behavior, so issues to watch for would more
likely involve process handling, i.e. problems with socket polling.
Beyond that, the usual generic issues to watch for - build issues,
dependency issues during build or on upgrade, and service restarting.
[Original Report]
The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the
bug described at
https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and
https://bugzilla.mindrot.org/show_bug.cgi?id=3405
A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
an xterm, ask for whatever authentication is needed, close the xterm,
and leave the ssh client spinning consuming CPU time for 60 seconds
before it exits. It should leave the ssh client idle for 60 seconds.
Many uses of ssh to launch graphical applications will be caught by
this bug.
This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its
release notes at https://www.openssh.com/txt/release-9.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1986521/+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 1986521] Re: ssh client spins if output fd closed
** Description changed:
+ [Impact]
+ In certain edge cases where the terminal goes away while an ssh process is
running, ssh can be left consuming 100% CPU. This increases processing costs
for cloud users and wastes energy.
+
+ This is a regression in jammy presumably due to change from select() to
+ poll() (see OpennSSH 8.9 Release Announcement [1] ), fixed by upstream
+ commit d6556de1db0822c76ba2745cf5c097d9472adf7c "upstream: fix poll()
+ spin when a channel's output fd closes..." [2].
+
+ 1: https://lwn.net/Articles/885886/
+ 2.
https://github.com/openssh/openssh-portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c
+
[Test Case]
$ lxc launch ubuntu-daily:jammy ssh-cpu
$ lxc shell ssh-cpu
# passwd -d root
# ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa
# cat << EOF >>/etc/ssh/ssh_config
StrictHostKeyChecking accept-new
EOF
# sed -ri 's/^PasswordAuthentication/#PasswordAuthentication/'
/etc/ssh/sshd_config
# cat << EOF >>/etc/ssh/sshd_config
PermitRootLogin yes
PubkeyAuthentication yes
PermitEmptyPasswords yes
PasswordAuthentication yes
ChallengeResponseAuthentication no
UsePAM no
EOF
# systemctl restart sshd
# ssh localhost 2> >({exec 1>&2})
-
You can shell into the container from a second terminal and use "htop"
to verify that ssh is using 100% of one of the CPU cores:
$ lxc shell ssh-cpu
# htop
This should show one CPU pegged at 100% due to the 'ssh localhost'
process
Next, return to the first terminal, exit out of the sub-ssh session and
install the fix:
# logout
# add-apt-repository -yus ppa:bryce/openssh-sru-lp1986521
# apt-get full-upgrade -y
Now repeat the test in the first terminal window, while viewing htop in
the second terminal:
# ssh localhost 2> >({exec 1>&2})
+ [Where Problems Could Occur]
+
+ While the patch in question is well tested upstream, it has a relatively
+ high line count and as such is difficult to assure correctness by visual
+ code checking. However, it's not clear that the line count could be
+ significantly reduced without risking loss of correctness. Thus this
+ relies more on testing to assure robustness, than on code review.
+
+ The code involves polling behavior, so issues to watch for would more
+ likely involve process handling, i.e. problems with socket polling.
+
+ Beyond that, the usual generic issues to watch for - build issues,
+ dependency issues during build or on upgrade, and service restarting.
+
+
[Original Report]
The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the
bug described at
https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and
https://bugzilla.mindrot.org/show_bug.cgi?id=3405
A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
an xterm, ask for whatever authentication is needed, close the xterm,
and leave the ssh client spinning consuming CPU time for 60 seconds
before it exits. It should leave the ssh client idle for 60 seconds.
Many uses of ssh to launch graphical applications will be caught by this
bug.
This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its release
notes at https://www.openssh.com/txt/release-9.0
--
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/1986521
Title:
ssh client spins if output fd closed
Status in portable OpenSSH:
Unknown
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Jammy:
Triaged
Bug description:
[Impact]
In certain edge cases where the terminal goes away while an ssh process is
running, ssh can be left consuming 100% CPU. This increases processing costs
for cloud users and wastes energy. While this is an uncommon error, googling
indicates many people have run into it in several different ways. It seems
important to get this fixed in stable releases.
This is a regression in jammy presumably due to change from select()
to poll() (see OpennSSH 8.9 Release Announcement [1] ), fixed by
upstream commit d6556de1db0822c76ba2745cf5c097d9472adf7c "upstream:
fix poll() spin when a channel's output fd closes..." [2].
1: https://lwn.net/Articles/885886/
2.
https://github.com/openssh/openssh-portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c
[Test Case]
$ lxc launch ubuntu-daily:jammy ssh-cpu
$ lxc shell ssh-cpu
# passwd -d root
# ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa
# cat << EOF >>/etc/ssh/ssh_config
StrictHostKeyChecking accept-new
EOF
# sed -ri 's/^PasswordAuthentication/#PasswordAuthentication/'
/etc/ssh/sshd_config
# cat << EOF >>/etc/ssh/sshd_config
PermitRootLogin yes
PubkeyAuthentication yes
PermitEmptyPasswords yes
PasswordAuthentication yes
ChallengeResponseAuthentication no
UsePAM no
EOF
# systemctl restart sshd
# ssh localhost 2> >({exec 1>&2})
You can
[Touch-packages] [Bug 1996937] Re: "install vim failed"package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller ava
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1996937 Title: "install vim failed"package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. Status in tzdata package in Ubuntu: New Bug description: trying to install vim but i occured an error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2022f-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: vim-runtime:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Nov 17 20:00:11 2022 ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2022-11-12 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tzdata Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1996937/+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 1986521] Re: ssh client spins if output fd closed
I've reproduced the issue and confirmed the PPA fixes it, as expected.
** Description changed:
+ [Test Case]
+ $ lxc launch ubuntu-daily:jammy ssh-cpu
+ $ lxc shell ssh-cpu
+
+ # passwd -d root
+ # ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa
+
+ # cat << EOF >>/etc/ssh/ssh_config
+ StrictHostKeyChecking accept-new
+ EOF
+
+ # sed -ri 's/^PasswordAuthentication/#PasswordAuthentication/'
/etc/ssh/sshd_config
+ # cat << EOF >>/etc/ssh/sshd_config
+ PermitRootLogin yes
+ PubkeyAuthentication yes
+ PermitEmptyPasswords yes
+ PasswordAuthentication yes
+ ChallengeResponseAuthentication no
+ UsePAM no
+ EOF
+
+ # systemctl restart sshd
+
+ # ssh localhost 2> >({exec 1>&2})
+
+
+ You can shell into the container from a second terminal and use "htop"
+ to verify that ssh is using 100% of one of the CPU cores:
+
+ $ lxc shell ssh-cpu
+ # htop
+
+ This should show one CPU pegged at 100% due to the 'ssh localhost'
+ process
+
+ Next, return to the first terminal, exit out of the sub-ssh session and
+ install the fix:
+
+ # logout
+ # add-apt-repository -yus ppa:bryce/openssh-sru-lp1986521
+ # apt-get full-upgrade -y
+
+ Now repeat the test in the first terminal window, while viewing htop in
+ the second terminal:
+
+ # ssh localhost 2> >({exec 1>&2})
+
+ [Original Report]
The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the
bug described at
https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and
https://bugzilla.mindrot.org/show_bug.cgi?id=3405
A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
an xterm, ask for whatever authentication is needed, close the xterm,
and leave the ssh client spinning consuming CPU time for 60 seconds
before it exits. It should leave the ssh client idle for 60 seconds.
Many uses of ssh to launch graphical applications will be caught by this
bug.
This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its release
notes at https://www.openssh.com/txt/release-9.0
--
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/1986521
Title:
ssh client spins if output fd closed
Status in portable OpenSSH:
Unknown
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Jammy:
Triaged
Bug description:
[Test Case]
$ lxc launch ubuntu-daily:jammy ssh-cpu
$ lxc shell ssh-cpu
# passwd -d root
# ssh-keygen -t rsa -N '' -f /root/.ssh/id_rsa
# cat << EOF >>/etc/ssh/ssh_config
StrictHostKeyChecking accept-new
EOF
# sed -ri 's/^PasswordAuthentication/#PasswordAuthentication/'
/etc/ssh/sshd_config
# cat << EOF >>/etc/ssh/sshd_config
PermitRootLogin yes
PubkeyAuthentication yes
PermitEmptyPasswords yes
PasswordAuthentication yes
ChallengeResponseAuthentication no
UsePAM no
EOF
# systemctl restart sshd
# ssh localhost 2> >({exec 1>&2})
You can shell into the container from a second terminal and use "htop"
to verify that ssh is using 100% of one of the CPU cores:
$ lxc shell ssh-cpu
# htop
This should show one CPU pegged at 100% due to the 'ssh localhost'
process
Next, return to the first terminal, exit out of the sub-ssh session and
install the fix:
# logout
# add-apt-repository -yus ppa:bryce/openssh-sru-lp1986521
# apt-get full-upgrade -y
Now repeat the test in the first terminal window, while viewing htop in
the second terminal:
# ssh localhost 2> >({exec 1>&2})
[Original Report]
The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the
bug described at
https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and
https://bugzilla.mindrot.org/show_bug.cgi?id=3405
A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
an xterm, ask for whatever authentication is needed, close the xterm,
and leave the ssh client spinning consuming CPU time for 60 seconds
before it exits. It should leave the ssh client idle for 60 seconds.
Many uses of ssh to launch graphical applications will be caught by
this bug.
This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its
release notes at https://www.openssh.com/txt/release-9.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1986521/+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 1998414] Re: libdrm-dev missing man pages
Debian also is missing the same pages: https://manpages.debian.org/bullseye/libdrm- dev/drmModeGetResources.3.en.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998414 Title: libdrm-dev missing man pages Status in libdrm package in Ubuntu: New Bug description: When I access the man-page for drmModeGetResources I am referred to other pages in "SEE ALSO" ``` SEE ALSO drm(7), drm-kms(7), drmModeGetFB(3), drmModeAddFB(3), drmMod‐ eAddFB2(3), drmModeRmFB(3),drmModeDirtyFB(3),drmMod‐ eGetCrtc(3), drmModeSetCrtc (3), drmModeGetEncoder (3), drm‐ ModeGetConnector(3) ``` However, almost none of these other man-pages exist: ``` $ man drmModeGetEncoder No manual entry for drmModeGetEncoder ``` libdrm-dev is installed: 2.4.113-2 OS: Ubuntu 22.10 ``` $ dpkg -L libdrm-dev /. /usr /usr/include /usr/include/libdrm /usr/include/libdrm/amdgpu.h /usr/include/libdrm/amdgpu_drm.h /usr/include/libdrm/drm.h /usr/include/libdrm/drm_fourcc.h /usr/include/libdrm/drm_mode.h /usr/include/libdrm/drm_sarea.h /usr/include/libdrm/i915_drm.h /usr/include/libdrm/intel_aub.h /usr/include/libdrm/intel_bufmgr.h /usr/include/libdrm/intel_debug.h /usr/include/libdrm/mach64_drm.h /usr/include/libdrm/mga_drm.h /usr/include/libdrm/msm_drm.h /usr/include/libdrm/nouveau /usr/include/libdrm/nouveau/nouveau.h /usr/include/libdrm/nouveau/nvif /usr/include/libdrm/nouveau/nvif/cl0080.h /usr/include/libdrm/nouveau/nvif/cl9097.h /usr/include/libdrm/nouveau/nvif/class.h /usr/include/libdrm/nouveau/nvif/if0002.h /usr/include/libdrm/nouveau/nvif/if0003.h /usr/include/libdrm/nouveau/nvif/ioctl.h /usr/include/libdrm/nouveau/nvif/unpack.h /usr/include/libdrm/nouveau_drm.h /usr/include/libdrm/qxl_drm.h /usr/include/libdrm/r128_drm.h /usr/include/libdrm/r600_pci_ids.h /usr/include/libdrm/radeon_bo.h /usr/include/libdrm/radeon_bo_gem.h /usr/include/libdrm/radeon_bo_int.h /usr/include/libdrm/radeon_cs.h /usr/include/libdrm/radeon_cs_gem.h /usr/include/libdrm/radeon_cs_int.h /usr/include/libdrm/radeon_drm.h /usr/include/libdrm/radeon_surface.h /usr/include/libdrm/savage_drm.h /usr/include/libdrm/sis_drm.h /usr/include/libdrm/tegra_drm.h /usr/include/libdrm/vc4_drm.h /usr/include/libdrm/via_drm.h /usr/include/libdrm/virtgpu_drm.h /usr/include/libdrm/vmwgfx_drm.h /usr/include/libsync.h /usr/include/xf86drm.h /usr/include/xf86drmMode.h /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libdrm.a /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.a /usr/lib/x86_64-linux-gnu/libdrm_intel.a /usr/lib/x86_64-linux-gnu/libdrm_nouveau.a /usr/lib/x86_64-linux-gnu/libdrm_radeon.a /usr/lib/x86_64-linux-gnu/pkgconfig /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_amdgpu.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_intel.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_nouveau.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_radeon.pc /usr/share /usr/share/doc /usr/share/doc/libdrm-dev /usr/share/doc/libdrm-dev/copyright /usr/share/man /usr/share/man/man3 /usr/share/man/man3/drmAvailable.3.gz /usr/share/man/man3/drmHandleEvent.3.gz /usr/share/man/man3/drmModeGetResources.3.gz /usr/share/man/man7 /usr/share/man/man7/drm-kms.7.gz /usr/share/man/man7/drm-memory.7.gz /usr/share/man/man7/drm.7.gz /usr/lib/x86_64-linux-gnu/libdrm.so /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.so /usr/lib/x86_64-linux-gnu/libdrm_intel.so /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so /usr/lib/x86_64-linux-gnu/libdrm_radeon.so /usr/share/doc/libdrm-dev/changelog.Debian.gz ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1998414/+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 1998414] [NEW] libdrm-dev missing man pages
Public bug reported: When I access the man-page for drmModeGetResources I am referred to other pages in "SEE ALSO" ``` SEE ALSO drm(7), drm-kms(7), drmModeGetFB(3), drmModeAddFB(3), drmMod‐ eAddFB2(3), drmModeRmFB(3),drmModeDirtyFB(3),drmMod‐ eGetCrtc(3), drmModeSetCrtc (3), drmModeGetEncoder (3), drm‐ ModeGetConnector(3) ``` However, almost none of these other man-pages exist: ``` $ man drmModeGetEncoder No manual entry for drmModeGetEncoder ``` libdrm-dev is installed: 2.4.113-2 OS: Ubuntu 22.10 ``` $ dpkg -L libdrm-dev /. /usr /usr/include /usr/include/libdrm /usr/include/libdrm/amdgpu.h /usr/include/libdrm/amdgpu_drm.h /usr/include/libdrm/drm.h /usr/include/libdrm/drm_fourcc.h /usr/include/libdrm/drm_mode.h /usr/include/libdrm/drm_sarea.h /usr/include/libdrm/i915_drm.h /usr/include/libdrm/intel_aub.h /usr/include/libdrm/intel_bufmgr.h /usr/include/libdrm/intel_debug.h /usr/include/libdrm/mach64_drm.h /usr/include/libdrm/mga_drm.h /usr/include/libdrm/msm_drm.h /usr/include/libdrm/nouveau /usr/include/libdrm/nouveau/nouveau.h /usr/include/libdrm/nouveau/nvif /usr/include/libdrm/nouveau/nvif/cl0080.h /usr/include/libdrm/nouveau/nvif/cl9097.h /usr/include/libdrm/nouveau/nvif/class.h /usr/include/libdrm/nouveau/nvif/if0002.h /usr/include/libdrm/nouveau/nvif/if0003.h /usr/include/libdrm/nouveau/nvif/ioctl.h /usr/include/libdrm/nouveau/nvif/unpack.h /usr/include/libdrm/nouveau_drm.h /usr/include/libdrm/qxl_drm.h /usr/include/libdrm/r128_drm.h /usr/include/libdrm/r600_pci_ids.h /usr/include/libdrm/radeon_bo.h /usr/include/libdrm/radeon_bo_gem.h /usr/include/libdrm/radeon_bo_int.h /usr/include/libdrm/radeon_cs.h /usr/include/libdrm/radeon_cs_gem.h /usr/include/libdrm/radeon_cs_int.h /usr/include/libdrm/radeon_drm.h /usr/include/libdrm/radeon_surface.h /usr/include/libdrm/savage_drm.h /usr/include/libdrm/sis_drm.h /usr/include/libdrm/tegra_drm.h /usr/include/libdrm/vc4_drm.h /usr/include/libdrm/via_drm.h /usr/include/libdrm/virtgpu_drm.h /usr/include/libdrm/vmwgfx_drm.h /usr/include/libsync.h /usr/include/xf86drm.h /usr/include/xf86drmMode.h /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libdrm.a /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.a /usr/lib/x86_64-linux-gnu/libdrm_intel.a /usr/lib/x86_64-linux-gnu/libdrm_nouveau.a /usr/lib/x86_64-linux-gnu/libdrm_radeon.a /usr/lib/x86_64-linux-gnu/pkgconfig /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_amdgpu.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_intel.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_nouveau.pc /usr/lib/x86_64-linux-gnu/pkgconfig/libdrm_radeon.pc /usr/share /usr/share/doc /usr/share/doc/libdrm-dev /usr/share/doc/libdrm-dev/copyright /usr/share/man /usr/share/man/man3 /usr/share/man/man3/drmAvailable.3.gz /usr/share/man/man3/drmHandleEvent.3.gz /usr/share/man/man3/drmModeGetResources.3.gz /usr/share/man/man7 /usr/share/man/man7/drm-kms.7.gz /usr/share/man/man7/drm-memory.7.gz /usr/share/man/man7/drm.7.gz /usr/lib/x86_64-linux-gnu/libdrm.so /usr/lib/x86_64-linux-gnu/libdrm_amdgpu.so /usr/lib/x86_64-linux-gnu/libdrm_intel.so /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so /usr/lib/x86_64-linux-gnu/libdrm_radeon.so /usr/share/doc/libdrm-dev/changelog.Debian.gz ``` ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1998414 Title: libdrm-dev missing man pages Status in libdrm package in Ubuntu: New Bug description: When I access the man-page for drmModeGetResources I am referred to other pages in "SEE ALSO" ``` SEE ALSO drm(7), drm-kms(7), drmModeGetFB(3), drmModeAddFB(3), drmMod‐ eAddFB2(3), drmModeRmFB(3),drmModeDirtyFB(3),drmMod‐ eGetCrtc(3), drmModeSetCrtc (3), drmModeGetEncoder (3), drm‐ ModeGetConnector(3) ``` However, almost none of these other man-pages exist: ``` $ man drmModeGetEncoder No manual entry for drmModeGetEncoder ``` libdrm-dev is installed: 2.4.113-2 OS: Ubuntu 22.10 ``` $ dpkg -L libdrm-dev /. /usr /usr/include /usr/include/libdrm /usr/include/libdrm/amdgpu.h /usr/include/libdrm/amdgpu_drm.h /usr/include/libdrm/drm.h /usr/include/libdrm/drm_fourcc.h /usr/include/libdrm/drm_mode.h /usr/include/libdrm/drm_sarea.h /usr/include/libdrm/i915_drm.h /usr/include/libdrm/intel_aub.h /usr/include/libdrm/intel_bufmgr.h /usr/include/libdrm/intel_debug.h /usr/include/libdrm/mach64_drm.h /usr/include/libdrm/mga_drm.h /usr/include/libdrm/msm_drm.h /usr/include/libdrm/nouveau /usr/include/libdrm/nouveau/nouveau.h /usr/include/libdrm/nouveau/nvif /usr/include/libdrm/nouveau/nvif/cl0080.h /usr/include/libdrm/nouveau/nvif/cl9097.h /usr/include/libdrm/nouveau/nvif/class.h
[Touch-packages] [Bug 1998407] [NEW] package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with l
Public bug reported: Did not install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_48_54_generic_90 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Nov 16 16:41:22 2022 DuplicateSignature: package:libnih-dbus1:1.0.3-6ubuntu2 Unpacking libnfsidmap1:amd64 (1:2.6.1-1ubuntu1.1) over (1:2.6.1-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-5AFDRm/154-libnih-dbus1_1.0.3-12build1_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances InstallationDate: Installed on 2014-09-14 (2999 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances UpgradeStatus: Upgraded to jammy on 2022-08-23 (99 days ago) ** Affects: libnih (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1998407 Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances Status in libnih package in Ubuntu: New Bug description: Did not install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_48_54_generic_90 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Nov 16 16:41:22 2022 DuplicateSignature: package:libnih-dbus1:1.0.3-6ubuntu2 Unpacking libnfsidmap1:amd64 (1:2.6.1-1ubuntu1.1) over (1:2.6.1-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-5AFDRm/154-libnih-dbus1_1.0.3-12build1_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances InstallationDate: Installed on 2014-09-14 (2999 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances UpgradeStatus: Upgraded to jammy on 2022-08-23 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1998407/+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 1998408] [NEW] package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with l
Public bug reported: Did not install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_48_54_generic_90 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Nov 16 16:41:22 2022 DuplicateSignature: package:libnih-dbus1:1.0.3-6ubuntu2 Unpacking libnfsidmap1:amd64 (1:2.6.1-1ubuntu1.1) over (1:2.6.1-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-5AFDRm/154-libnih-dbus1_1.0.3-12build1_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances InstallationDate: Installed on 2014-09-14 (2999 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances UpgradeStatus: Upgraded to jammy on 2022-08-23 (99 days ago) ** Affects: libnih (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1998408 Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances Status in libnih package in Ubuntu: New Bug description: Did not install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_48_54_generic_90 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Nov 16 16:41:22 2022 DuplicateSignature: package:libnih-dbus1:1.0.3-6ubuntu2 Unpacking libnfsidmap1:amd64 (1:2.6.1-1ubuntu1.1) over (1:2.6.1-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-5AFDRm/154-libnih-dbus1_1.0.3-12build1_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances InstallationDate: Installed on 2014-09-14 (2999 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances UpgradeStatus: Upgraded to jammy on 2022-08-23 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1998408/+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 1998321] Please test proposed package
Hello Benjamin, or anyone else affected, Accepted tzdata into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2022g-0ubuntu0.18.04 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, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Please test proposed package
Hello Benjamin, or anyone else affected, Accepted tzdata into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2022g-0ubuntu0.20.04.0 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, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: tzdata (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Re: tzdata 2022g release
Hello Benjamin, or anyone else affected, Accepted tzdata into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2022g-0ubuntu0.22.04.0 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, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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: tzdata (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy ** Changed in: tzdata (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Re: tzdata 2022g release
Hello Benjamin, or anyone else affected, Accepted tzdata into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2022g-0ubuntu0.22.10.0 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, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: tzdata (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: Fix Committed Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1983185] Re: Recent commit breaks /etc/X11/Xsession
The problem is a change in the file
/etc/X11/Xsession.d/20x11-common_process-args
Replacing line 36:
STARTUP_FULL_PATH=$(command -v "${1%% *}" || true)
with this:
STARTUP_FULL_PATH=$(/usr/bin/which "${1%% *}" || true)
removes the error.
The question is now: WHY was there a change from "which" to "command
-v"?
Andy
--
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/1983185
Title:
Recent commit breaks /etc/X11/Xsession
Status in xorg package in Ubuntu:
Confirmed
Status in xorg package in Debian:
New
Bug description:
The following command:
$/etc/X11/Xsession true
opens a dialog with the following error message:
"Xsession: unable to launch "true" X session --- "true" not found;
falling back to default session."
There is a "Okay" button on this message, and clicking it does bad
things if one happens to be running Ubuntu 22.04 on Xorg (or running
Gnome on Xorg, which is seemingly a different option for the the low
latency installation I am running: 5.15.0-43-generic #46-Ubuntu SMP
Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux).
See Brendan O'Dea's related comment about this behavior on debian-
bugs-dist: https://www.mail-archive.com/debian-bugs-
d...@lists.debian.org/msg1857023.html
This has consequences in my use of xpra. For example, if I use xpra
via the run_scaled-master script to magnify a single application's
interface for a 4K display I get the error dialog mentioned above,
often with resulting system instability.
This behavior cropped up last month.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon
znvpair
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7
05:30:26 UTC 2022
GCC version:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Sat Jul 30 10:14:43 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
virtualbox/6.1.34, 5.15.0-41-lowlatency, x86_64: installed
virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:2269]
NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269]
InstallationDate: Installed on 2022-07-13 (16 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: LENOVO 20MBCTO1WW
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_aze0rg@/vmlinuz-5.15.0-43-generic
root=ZFS=rpool/ROOT/ubuntu_aze0rg ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2022
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: N2CET64W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.16
dmi.modalias:
dmi:bvnLENOVO:bvrN2CET64W(1.47):bd06/10/2022:br1.47:efr1.16:svnLENOVO:pn20MBCTO1WW:pvrThinkPadP72:rvnLENOVO:rn20MBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20MB_BU_Think_FM_ThinkPadP72:
dmi.product.family: ThinkPad P72
dmi.product.name: 20MBCTO1WW
dmi.product.sku: LENOVO_MT_20MB_BU_Think_FM_ThinkPad P72
dmi.product.version: ThinkPad P72
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel:
[Touch-packages] [Bug 1993834] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package is now being 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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1993834 Title: Update evolution-data-server to 3.46.1 Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Kinetic: Fix Released Bug description: Impact -- This is a new stable release in the 3.46 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.46.1/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1993834/+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 1993834] Re: Update evolution-data-server to 3.46.1
This bug was fixed in the package evolution-data-server - 3.46.1-0ubuntu1 --- evolution-data-server (3.46.1-0ubuntu1) kinetic; urgency=medium * New upstream release (LP: #1993834) -- Jeremy Bicha Fri, 21 Oct 2022 11:32:50 -0400 ** Changed in: evolution-data-server (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1993834 Title: Update evolution-data-server to 3.46.1 Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Kinetic: Fix Released Bug description: Impact -- This is a new stable release in the 3.46 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.46.1/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1993834/+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 1998321] Re: tzdata 2022g release
** Description changed: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 + + Verification is done with 'zdump'. The first timezone that gets changed + in the updated package is dumped with 'zdump -v + $region/$timezone_that_changed' (this needs to be greped for in + /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is + compared to the same output after the updated package got installed. If + those are different the verification is considered done. + + [ Test Case for all releases ] + 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail + -> should have output, last dates should be in 2499 + + [Test Case for releases <= 20.04 LTS] + + Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: + diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) To manage notifications about this bug go to:
[Touch-packages] [Bug 1997189] Re: [BPO] elfutils/0.188-1 from Lunar
Thanks, Dan. I'll ping you when elfutils migrates on lunar, then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1997189 Title: [BPO] elfutils/0.188-1 from Lunar Status in elfutils package in Ubuntu: Fix Released Status in elfutils source package in Jammy: New Bug description: [Impact] * elfutils ships many ELF/DWARF related tools that are interesting for users and developers of low level code. * More specifically, elfutils ships the debuginfod library and server. The latest upstream version (0.188) introduces many interesting features that should make the life of debuginfod users easier; one of those features is the ability to serve sections of DWARF, instead of the whole file. I intend to update Ubuntu's debuginfod instance to use this new package in the near future. [Scope] * I will backport elfutils/0.188 from Lunar. * I will backport elfutils/0.188 to Jammy. [Other Info] * None so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1997189/+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 1998321] Re: tzdata 2022g release
** Patch added: "tzdata_2022g-0ubuntu0.18.04.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+attachment/5633556/+files/tzdata_2022g-0ubuntu0.18.04.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com
** Changed in: network-manager
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1998082
Title:
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
Status in NetworkManager:
Fix Released
Status in gnome-shell package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
Original Report
---
Hotspot Login window [gnome-shell-portal-helper] randomly opens with
https://help.ubuntu.com
I'm not even using wifi. I don't care about hotspots.
Workaround
--
sudo apt install network-manager-config-connectivity-debian
sudo apt remove network-manager-config-connectivity-ubuntu
sudo systemctl restart NetworkManager
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 43.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 16:40:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-portal-helper
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-11-28 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
RelatedPackageVersions: mutter-common 43.0-1ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1998082/+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 1998321] Re: tzdata 2022g release
** Patch added: "tzdata_2022g-0ubuntu0.20.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+attachment/5633547/+files/tzdata_2022g-0ubuntu0.20.04.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1997189] Re: [BPO] elfutils/0.188-1 from Lunar
we briefly discussed this in the backporters mtg and it looks good to us, however it's backported from 0.188-1 which is currently in lunar- proposed, so that needs to migrate to lunar-release before we can accept this backport; feel free to ping us once that's happened. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1997189 Title: [BPO] elfutils/0.188-1 from Lunar Status in elfutils package in Ubuntu: Fix Released Status in elfutils source package in Jammy: New Bug description: [Impact] * elfutils ships many ELF/DWARF related tools that are interesting for users and developers of low level code. * More specifically, elfutils ships the debuginfod library and server. The latest upstream version (0.188) introduces many interesting features that should make the life of debuginfod users easier; one of those features is the ability to serve sections of DWARF, instead of the whole file. I intend to update Ubuntu's debuginfod instance to use this new package in the near future. [Scope] * I will backport elfutils/0.188 from Lunar. * I will backport elfutils/0.188 to Jammy. [Other Info] * None so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1997189/+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 1980408] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package is now being 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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+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 1980408] Re: Update glib to 2.72.4
This bug was fixed in the package glib2.0 - 2.72.4-0ubuntu1 --- glib2.0 (2.72.4-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1980408) * Update testfilemonitor-Skip-if-we-are-avoiding-flaky-tests.patch for new testfilemonitor test. -- Jeremy Bicha Wed, 12 Oct 2022 14:59:04 -0400 ** Changed in: glib2.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+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 1997036] Re: python-apt: FTBFS with Python 3.11 as a supported version
** Changed in: python-apt (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1997036 Title: python-apt: FTBFS with Python 3.11 as a supported version Status in python-apt package in Ubuntu: Fix Committed Bug description: python-apt FTBFS with Python 3.11 as a supported version: https://launchpad.net/ubuntu/+source/python-apt/2.3.0ubuntu3 I've copied what I hope is the relevant part of the log below. I: pybuild base:240: env PYTHONPATH=/<>/.pybuild/cpython3_3.11_dbg_apt/build python3.11-dbg tests/test_all.py [tests] Running on 3.11.0+ (main, Nov 4 2022, 09:23:33) [GCC 12.2.0] Using pybuild supplied build dir s...gc:0: ResourceWarning: Object of type apt_pkg.Package is not untracked before destruction gc:0: ResourceWarning: Object of type apt_pkg.Package is not untracked before destruction gc:0: ResourceWarning: Object of type apt_pkg.Package is not untracked before destruction gc:0: ResourceWarning: Object of type apt_pkg.Package is not untracked before destruction ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1997036/+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 1998321] Re: tzdata 2022g release
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1992454] Re: iptables: segfault when renaming a chain
Hello, Sorry for the late response. It is most probably a mistake from my part. Let me know if you want me to upload a corrected debdiff. Regarding focal, since it was added by upstream, I thought that it would be better to add it as well. Kind regards, ...Louis -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: In Progress Status in iptables source package in Bionic: In Progress Status in iptables source package in Focal: In Progress Status in iptables source package in Jammy: In Progress Status in iptables source package in Kinetic: In Progress Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1997979] Re: Merge grilo-plugins 0.3.15-1 from Debian unstable
** Changed in: grilo-plugins (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1997979 Title: Merge grilo-plugins 0.3.15-1 from Debian unstable Status in grilo-plugins package in Ubuntu: Fix Committed Bug description: Built successfully locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1997979/+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 1986936] Re: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages
This may be the wrong place to confirm this, and I don't know what package the link libQt5Core.so is supposed to be a part of, but I can confirm that this particular symlink was missing immediately after upgrading to 22.04 from 20.04. No others were missing on my system. -- 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/1986936 Title: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages Status in qtbase-opensource-src package in Ubuntu: New Bug description: While trying to link against corresponding libraries to get i386 executable like that: > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ... I get the following errors: > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so when searching for -lQt5Gui > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so when searching for -lQt5Gui > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so when searching for -lQt5Core > /usr/bin/ld: cannot find -lQt5Core: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so when searching for -lQt5Core despite corresponging packages are installed (libqt5gui5:i386 and same for widgets and core). Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no symlinks named exactly libQt5Core.so (and same for two other libs). Adding those symlinks by hand completely solves the problem. I believe however that those symlinks must be installed by corresponding .debs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1986936/+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 1998321] Re: tzdata 2022g release
** Patch added: "tzdata_2022g-0ubuntu0.22.04.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+attachment/5633471/+files/tzdata_2022g-0ubuntu0.22.04.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1118485] Re: software sources settings do not load
Unsure if this bug report was reported against the correct package. This issue was never confirmed by another user. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. Bug description seems rather vague when using a recent Ubuntu release so may be Unity related? Please feel free to re-open this bug report if this is still an issue when using a currently supported release of Ubuntu. Please make sure you tell us with which release you still experience this issue and which desktop environment you are using. Thank you for your understanding. ** Changed in: ubuntu-settings (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1118485 Title: software sources settings do not load Status in ubuntu-settings package in Ubuntu: Invalid Bug description: Clicking on "software sources" produces no results Can't launch its icon directly either. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubuntu-settings 12.10.3 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Thu Feb 7 07:56:42 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to quantal on 2012-10-19 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1118485/+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 1998321] Re: tzdata 2022g release
** Patch added: "tzdata_2022g-0ubuntu0.22.10.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+attachment/5633398/+files/tzdata_2022g-0ubuntu0.22.10.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Re: tzdata 2022g release
** Also affects: tzdata (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Kinetic: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 243105] Re: When Wubi is installed from CD, ubiquity crashes at the end of the installation
Further to comment #7, bug report did not expire due to WUBI task. Closing all taks as 'Invalid' as WUBI no longer part of Ubuntu . ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Invalid ** Changed in: wubi Status: Confirmed => Invalid ** Changed in: apt (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/243105 Title: When Wubi is installed from CD, ubiquity crashes at the end of the installation Status in Wubi: Invalid Status in apt package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Bug description: Because of bug #207137 Wubi now copies the CD content as opposed to extract an ISO. This was implemented via bug #230716 which allows casper to boot off a directory. That directory is bindmounted to /cdrom in the initrd. But that makes ubiquity/install.py > install_extras > do_install > cache.commit fail, since apt/python-apt does not work correctly when /cdrom is bind-mounted. That in turn can be tracked down to fetcher.Run() in apt/cache.py cache.py > Cache.commit > Cache._fetchArchives > self._runFetcher(fetcher) > fetcher.Run() Where fetcher = apt_pkg.GetAcquire(fetchProgress) -> Acquire instance When installing Wubi from an ISO (no bindmount) or when setting up /cdrom via a symlink in casper, the installation proceeds correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/243105/+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 1997201] Re: BlueZ 5.66 release
I've uploaded this for you. I did notice that the "original" tarball you provided and is compatible with the Launchpad git tree doesn't match the original tarball used by Debian for 5.66. Not a problem here, but if we ever did get the bluez packaging closer in sync with Debian, it might be nice to use the same tarballs. ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+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 1998321] Re: tzdata 2022g release
** Description changed: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) + + ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 + CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998325] Re: Please merge sysvinit 3.05-7 (main) from Debian unstable (main)
** Changed in: sysvinit (Ubuntu) Assignee: Olivier Gayot (ogayot) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998325 Title: Please merge sysvinit 3.05-7 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: New Bug description: Debian moved to a new upstream version 3.04 => 3.05. Since bionic, we only build sysvinit-utils because it is the only package marked [essential]. sysvinit-utils will surely gain more reverse depends because scripts that used to be provided by lsb-base are now provided by sysvinit-utils. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1958019]
(In reply to Cameron Berkenpas from comment #711) > It does not, which is unfortunate, as the 6th gen model recently finally > got support. > > The gen 7 uses the CSC3551 and the gen 7 is missing the properties in > the _DSD tables. > > Do you already have the Gen 7? No, I just have a Gen 6 and it's still working fine on a patched 5.17 kernel. > Try submitting a Lenovo support ticket > asking them to add the properties. I have a ticket they haven't follow > up on yet so I added a comment to the ticket I think less than an hour ago. I wish the kernel guys weren't so dead set against loadable DSDTs. There's still so many reasons why we need to be able to patch these ourselves and there's no good reason to have to rebuild an entire kernel just to add missing table entries. > On 10/24/22 09:55, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > --- Comment #710 from Howard Chu (h...@highlandsun.com) --- > > Hi, I might've missed this but - do we know for certain that the 7th gen > > Legion > > 7 (2022 model) uses the same amplifier chip as the 6th gen (2021 model)? > > -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Blake Lee from comment #719)
> Hi Cameron,
>
> I got my Legion Slim 7 Gen 7 AMD version yesterday and when I excitedly
> installed Fedora, I found the audio did not work. I would like to throw my
> weight behind this to get it fixed, but I don't know what to say to support
> exactly in my ticket. What do I need to ask them for?
>
> I would really prefer not to have to send this laptop back. Is there
> anything else I can do to help?
I don't really have a plan of attack on this as I'm pretty busy
generally. I haven't had time to follow up with Lenovo support yet. I'm
just hoping if they get enough feedback, they'll do something.
Otherwise, maybe we can try a petition?
But you might try explaining that all you need is for Lenovo to add the
requisite info to the DSD table in a BIOS update. Linux doesn't need to
be touched at all. Just a BIOS update. Here's a working example (that I
got from https://bugzilla.kernel.org/show_bug.cgi?id=216194):
Name (_DSD, Package (0x02) // _DSD: Device-Specific Data
{
ToUUID ("daffd814-6eba-4d8c-8a91-bc9bbf4aa301") /* Device
Properties for _DSD */,
Package (0x05)
{
Package (0x02)
{
"cirrus,dev-index",
Package (0x02)
{
0x40,
0x42
}
},
Package (0x02)
{
"reset-gpios",
Package (0x08)
{
SPKR,
One,
Zero,
Zero,
SPKR,
One,
Zero,
Zero
}
},
Package (0x02)
{
"cirrus,speaker-position",
Package (0x02)
{
One,
Zero
}
},
Package (0x02)
{
"cirrus,gpio1-func",
Package (0x02)
{
Zero,
One
}
},
Package (0x02)
{
"cirrus,gpio2-func",
Package (0x02)
{
0x02,
0x02
}
}
}
})
This information appears to be hard-coded in the drivers or related
files somehow. If this information could be determined, perhaps there
could be a kernel look up table with static values for supported
laptops?
Lenovo could easily add this information (that is specific to the given
model of laptop) in a BIOS update.
Some (many?) laptops with the CSC3551 amplifier chips have this
information in the BIOS. Not to support Linux, but because it seems
their drivers for Windows expect it to be there as well... Which leads
me to believe this is probably the approach that Cirrus Logic wants to
take (at least going forward). Perhaps models of laptop without this
info are older. Maybe not necessarily in terms of the launch date, but
design started earlier than the laptops that do have this information in
their DSDT's.
--
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/1958019
Title:
[Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
sound at all
Status in sound-2.6 (alsa-kernel):
Confirmed
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
internal speakers, but it work by headphones connected to standard
jack aux.
uname -r
5.11.0-44-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: i3draven 1266 F pulseaudio
/dev/snd/controlC0: i3draven 1266 F pulseaudio
[Touch-packages] [Bug 1998265] Re: OverFlow error when using cnf-extractor
** Changed in: python-apt (Ubuntu) Status: New => In Progress ** Changed in: python-apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: In Progress Status in python-apt source package in Bionic: New Bug description: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1998265] Re: OverFlow error when using cnf-extractor
>>> acq=apt.apt_pkg.Acquire() >>> apt.apt_pkg.AcquireFile(acq,"http://foo;, "foo", size=2875204834) Traceback (most recent call last): File "", line 1, in OverflowError: signed integer is greater than maximum -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: New Status in python-apt source package in Bionic: New Bug description: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1998324] Re: Missing changelog.Debian.gz from sysvinit-utils
I submitted a debdiff that addresses the issue in lunar as part of the 3.05-7 merge: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325 ** Changed in: sysvinit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998324 Title: Missing changelog.Debian.gz from sysvinit-utils Status in sysvinit package in Ubuntu: In Progress Bug description: The binary package sysvinit-utils does not include the changelog.Debian.gz file. Lintian reports it as an error: E: sysvinit-utils: no-changelog usr/share/doc/sysvinit- utils/changelog.Debian.gz (non-native package) I looked in the sysvinit-utils package in all releases of Ubuntu >= Bionic [1] and could not file anywhere ; whereas it's present in Debian [2]: It strongly suggests that our Delta from Debian is faulty. [1] https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324/+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 1998325] Re: Please merge sysvinit 3.05-7 (main) from Debian unstable (main)
Adding debdiff from Ubuntu ** Patch added: "1-3.04-1ubuntu1__3.05-7ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+attachment/5633389/+files/1-3.04-1ubuntu1__3.05-7ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998325 Title: Please merge sysvinit 3.05-7 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: New Bug description: Debian moved to a new upstream version 3.04 => 3.05. Since bionic, we only build sysvinit-utils because it is the only package marked [essential]. sysvinit-utils will surely gain more reverse depends because scripts that used to be provided by lsb-base are now provided by sysvinit-utils. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998325] Re: Please merge sysvinit 3.05-7 (main) from Debian unstable (main)
Adding debdiff from Debian. During the merge, I noticed that the changelog.Debian.gz file is absent from sysvinit-utils in Ubuntu since we introduced our delta from Debian. I created https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324 and fixed it as part of the debdiff. Successful build in PPA on amd64: https://launchpad.net/~ogayot/+archive/ubuntu/lunar-proposed/+build/24885473 ** Description changed: - TODO + Debian moved to a new upstream version 3.04 => 3.05. + Since bionic, we only build sysvinit-utils because it is the only package marked [essential]. + sysvinit-utils will surely gain more reverse depends because scripts that used to be provided by lsb-base are now provided by sysvinit-utils. ** Patch added: "1-3.05-7__3.05-7ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+attachment/5633388/+files/1-3.05-7__3.05-7ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998325 Title: Please merge sysvinit 3.05-7 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: New Bug description: Debian moved to a new upstream version 3.04 => 3.05. Since bionic, we only build sysvinit-utils because it is the only package marked [essential]. sysvinit-utils will surely gain more reverse depends because scripts that used to be provided by lsb-base are now provided by sysvinit-utils. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998326] [NEW] bug display
Public bug reported: hello. I ran into such a problem. I lost all the icons on the taskbar and above. I don’t know why it happened. please fix this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.85.02 Tue Jul 12 16:51:23 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 30 21:11:02 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology TU116 [GeForce GTX 1660 SUPER] [174b:a538] InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro N50-620 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=97aad5b7-d730-47af-9a09-cfdfeec41490 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2021 dmi.bios.release: 10.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A2 dmi.board.name: Nitro N50-620 dmi.board.vendor: Acer dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A2:bd07/02/2021:br10.2:efr1.2:svnAcer:pnNitroN50-620:pvr1.0:rvnAcer:rnNitroN50-620:rvr1.0:cvnAcer:ct3:cvr:sku: dmi.product.family: Nitro N dmi.product.name: Nitro N50-620 dmi.product.sku: dmi.product.version: 1.0 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 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:21.1.3-2ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu ** Attachment added: "image.png" https://bugs.launchpad.net/bugs/1998326/+attachment/5633359/+files/image.png -- 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/1998326 Title: bug display Status in xorg package in Ubuntu: New Bug description: hello. I ran into such a problem. I lost all the icons on the taskbar and above. I don’t know why it happened. please fix this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.85.02 Tue Jul 12 16:51:23 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 30 21:11:02 2022 DistUpgraded:
[Touch-packages] [Bug 1998325] [NEW] Please merge sysvinit 3.05-7 (main) from Debian unstable (main)
Public bug reported: TODO ** Affects: sysvinit (Ubuntu) Importance: Undecided Assignee: Olivier Gayot (ogayot) Status: New ** Changed in: sysvinit (Ubuntu) Assignee: (unassigned) => Olivier Gayot (ogayot) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998325 Title: Please merge sysvinit 3.05-7 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: New Bug description: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998324] Re: Missing changelog.Debian.gz from sysvinit-utils
** Changed in: sysvinit (Ubuntu) Assignee: (unassigned) => Olivier Gayot (ogayot) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998324 Title: Missing changelog.Debian.gz from sysvinit-utils Status in sysvinit package in Ubuntu: New Bug description: The binary package sysvinit-utils does not include the changelog.Debian.gz file. Lintian reports it as an error: E: sysvinit-utils: no-changelog usr/share/doc/sysvinit- utils/changelog.Debian.gz (non-native package) I looked in the sysvinit-utils package in all releases of Ubuntu >= Bionic [1] and could not file anywhere ; whereas it's present in Debian [2]: It strongly suggests that our Delta from Debian is faulty. [1] https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324/+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 1998324] [NEW] Missing changelog.Debian.gz from sysvinit-utils
Public bug reported: The binary package sysvinit-utils does not include the changelog.Debian.gz file. Lintian reports it as an error: E: sysvinit-utils: no-changelog usr/share/doc/sysvinit- utils/changelog.Debian.gz (non-native package) I looked in the sysvinit-utils package in all releases of Ubuntu >= Bionic [1] and could not file anywhere ; whereas it's present in Debian [2]: It strongly suggests that our Delta from Debian is faulty. [1] https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998324 Title: Missing changelog.Debian.gz from sysvinit-utils Status in sysvinit package in Ubuntu: New Bug description: The binary package sysvinit-utils does not include the changelog.Debian.gz file. Lintian reports it as an error: E: sysvinit-utils: no-changelog usr/share/doc/sysvinit- utils/changelog.Debian.gz (non-native package) I looked in the sysvinit-utils package in all releases of Ubuntu >= Bionic [1] and could not file anywhere ; whereas it's present in Debian [2]: It strongly suggests that our Delta from Debian is faulty. [1] https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324/+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 1998321] [NEW] tzdata 2022g release
Public bug reported: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ** Affects: tzdata (Ubuntu) Importance: Critical Assignee: Benjamin Drung (bdrung) Status: New ** Description changed: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows + + Changes to future timestamps: + + In the Mexican state of Chihuahua, the border strip near the US will + change to agree with nearby US locations on 2022-11-30. The strip's + western part, represented by Ciudad Juárez, switches from -06 all year + to -07/-06 with US DST rules, like El Paso, TX. The eastern part, + represented by Ojinaga, will observe US DST next year, like Presidio, + TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez + splits from America/Ojinaga. + + Much of Greenland, represented by America/Nuuk, stops observing winter + time after March 2023, so its daylight saving time becomes standard + time. (Thanks to Jonas Nyrup and Jürgen Appel.) ** Changed in: tzdata (Ubuntu) Importance: Undecided => Critical ** Changed in: tzdata (Ubuntu) Assignee: (unassigned) => Benjamin Drung (bdrung) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998309] Re: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Sadly the attached logs do not contain the crash information. Do you have an apport crash file in /var/crash? If not, can you run ubuntu-bug in a terminal to capture the crash there? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1998309 Title: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo. Status in apport package in Ubuntu: Incomplete Bug description: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 -0500:2022-11-30 02:13:35.548841973 -0500:/var/crash/_usr_bin_avplayer.1000.crash CurrentDesktop: KDE Date: Wed Nov 30 03:11:50 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+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 1997201] Re: BlueZ 5.66 release
Tarballs are above, and the source code is in: https://git.launchpad.net/~bluetooth/bluez -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: In Progress Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+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 1997201] Re: BlueZ 5.66 release
** Attachment added: "bluez_5.66-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+attachment/5633346/+files/bluez_5.66-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: In Progress Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+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 1997201] Re: BlueZ 5.66 release
** Changed in: bluez (Ubuntu) Milestone: None => ubuntu-23.04-feature-freeze ** Attachment added: "bluez_5.66.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+attachment/5633345/+files/bluez_5.66.orig.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: In Progress Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+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 1998309] [NEW] attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
Public bug reported: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 -0500:2022-11-30 02:13:35.548841973 -0500:/var/crash/_usr_bin_avplayer.1000.crash CurrentDesktop: KDE Date: Wed Nov 30 03:11:50 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1998309 Title: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo. Status in apport package in Ubuntu: New Bug description: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 -0500:2022-11-30 02:13:35.548841973 -0500:/var/crash/_usr_bin_avplayer.1000.crash CurrentDesktop: KDE Date: Wed Nov 30 03:11:50 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+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 1997201] Re: BlueZ 5.66 release
** Changed in: bluez (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: In Progress Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+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
