[Touch-packages] [Bug 1998957] Re: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: pakket systemd is reeds geïnstalleerd en geconfigureerd

2022-12-06 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1998957

Title:
  package systemd 249.11-0ubuntu3.6 failed to install/upgrade: pakket
  systemd is reeds geïnstalleerd en geconfigureerd

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  I don't know what the problem is.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Dec  6 19:03:51 2022
  DpkgTerminalLog:
   dpkg: fout bij verwerken van pakket systemd (--configure):
pakket systemd is reeds geïnstalleerd en geconfigureerd
  ErrorMessage: pakket systemd is reeds geïnstalleerd en geconfigureerd
  InstallationDate: Installed on 2022-12-06 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7D22
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=761228fd-f419-4259-b184-f54c7d42d38b ro quiet splash
  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: systemd
  Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: pakket 
systemd is reeds geïnstalleerd en geconfigureerd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 3.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: H510M-A PRO (MS-7D22)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.B0:bd10/21/2022:br5.19:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D22:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH510M-APRO(MS-7D22):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D22
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1998957/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1998709] Re: Screen distorted when connecting via USB-C - HDMI adapter

2022-12-04 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1998709

Title:
  Screen distorted when connecting via USB-C - HDMI adapter

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using the internal laptop screen and 2 external monitors - the problem 
appears only with the one connected via an USB-C to HDMI adapter.
  - The setup works flawlessly on Windows (using the same resolution and 
refresh rate)
  - I've managed to get it working on Ubuntu only once by randomly switching 
(using Gnome settings & xrandr) screen resolutions, refresh rates, "Broadcast 
RGB"=Full setting - I cannot reproduce the exact sequence, it got broken again 
after a restart

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  4 18:09:40 2022
  DistUpgraded: 2022-10-23 18:19:23,869 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
  InstallationDate: Installed on 2018-07-27 (1590 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP EliteBook 840 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=c71c418c-5835-47e6-8b6e-ba75f32dc748 ro quiet splash 
resume=UUID=c31b8087-a480-47e0-b155-8fe5934eae37 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-23 (42 days ago)
  dmi.bios.date: 09/15/2022
  dmi.bios.release: 22.0
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.22.00
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.6D.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 4.109
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.22.00:bd09/15/2022:br22.0:efr4.109:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.6D.00:cvnHP:ct10:cvr:sku4RU25EC#AKD:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G5
  dmi.product.sku: 4RU25EC#AKD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.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-3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1998709/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1998673] Re: External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working

2022-12-03 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1998673

Title:
  External Display via Lenovo TB3 Dock on AMD Ryzen CPU not working

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Lenovo Yoga 7 Gen 7 (14ARB7) with AMD Ryzen 7 6800U CPU, with
  integrated AMD Radeon Graphics and USB4. I know this is quite new
  hardware, but I am astonished that many things work right out of the
  box.

  Ubuntu 22.04 with Mainline Kernel Linux 6.0.9-060009-generic 
#202211170559-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 17 06:06:21 UTC x86_64 x86_64 
x86_64 GNU/Linux
  Did some cross checks with Kernel 5.15.0-56 (stable)
  Monitor Samsung U32R592CWU UHD 4K (3.840 x 2.160 Pixel, VA-Panel, 16:9 
Format, 60 Hz, 4ms)

  What I have issues with (In this issue I'll only report on topic 1):

  1) External Monitor
  2) Touchscreen not working after suspend by closing lid; suspend only works 
once
  3) Integrated keyboard only works with Kernel 6 (Mainline) (kind of solved)

  I tested multiple ways connecting external monitors, each of them only 
working to some extent:
  i) directly via HDMI port of Notebook
  ii) via Lenovo Thinkpad Thunderbolt 3 Dock 40AC DisplayPort or HDMI 
(preferred solution)
  iii) via an Razer Core X eGPU with Radeon RX570 DisplayPort or HDMI

  Problems/Observations:
  1) DP/HDMI via Dock mostly not working (exception see point 3). USB via Dock 
works however.
  2) Booting with HDMI connected to Dock on Kernel 6 stalls. When unplugging 
the monitor the boot process immediately resumes successfully.
  3) Booting with HDMI connected to Dock on Kernel 5 brings up the screen, 
after that Hot Plug is also working, even DP
  4) Booting with DP connected to Dock on Kernel 5 does not bring up the 
screen, neither after Hot-Plug of HDMI or DP
  5) Booting without Monitor connected on Kernel 5 does not bring up the screen 
on Hot Plug, neither HDMI nor DP
  6) Hot Plugging the monitors (way i and iii) sometimes freezes the system, 
needs hard reset.
  7) Turning off or disconnecting TB cable of eGPU may also cause a freeze (as 
this also disconnects the monitor it may have the same cause as 2)

  So to sum it up: External Screens via this Docking Stations is only
  working on Kernel 5 when the monitor is connected via HDMI during
  boot, but not in any other case.

  Side observations:
  1) The USB devices connected to the TB3 Dock come up very slowly after hot 
plugging the TB3 connector to the Notebook.
  2) Mouse cursor (external mouse connected to Dock) hangs from time to time on 
Kernel 5.

  Please notify me if you need further logs. The automatically collected
  logs were captured in situation 2 above. You'll see the gap in the
  timestamps of th DMESG output.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  Uname: Linux 6.0.9-060009-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sat Dec  3 18:10:13 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev c1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2022-11-23 (9 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 82QF
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.9-060009-generic 
root=UUID=3031ba9e-0a88-4dc4-8cb6-65fab38e8fda ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2022
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: K5CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 7 14ARB7
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 
dmi:bvnLENOVO:bvrK5CN34WW:bd08/19/2022:br1.34:efr1.34:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7:
  dmi.product.family: Yoga 7 14ARB7
  dmi.product.name: 82QF
  dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7
  dmi.product.version: Yoga 7 14ARB7
  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.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.3
  

[Touch-packages] [Bug 1998444] Re: Backport security fix for CVE-2022-3970

2022-12-01 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tiff in Ubuntu.
https://bugs.launchpad.net/bugs/1998444

Title:
  Backport security fix for CVE-2022-3970

Status in tiff package in Ubuntu:
  New
Status in tiff source package in Bionic:
  New
Status in tiff source package in Focal:
  New
Status in tiff source package in Jammy:
  New
Status in tiff source package in Kinetic:
  New

Bug description:
  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 

[Touch-packages] [Bug 1998321] Re: tzdata 2022g release

2022-11-30 Thread Ubuntu Foundations Team Bug Bot
** 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 1998063] Re: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127

2022-11-27 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: tzdata (Ubuntu)
   Importance: Undecided => Low

** Changed in: tzdata (Ubuntu)
   Status: New => Invalid

-- 
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/1998063

Title:
  package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装
  tzdata 软件包 post-installation 脚本 子进程返回错误状态 127

Status in tzdata package in Ubuntu:
  Invalid

Bug description:

  hh

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: tzdata 2022f-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Nov 28 09:40:25 2022
  DpkgTerminalLog:
   正在设置 tzdata (2022f-0ubuntu0.22.04.1) ...
   /var/lib/dpkg/info/tzdata.config: 394: head: not found
   dpkg: 处理软件包 tzdata (--configure)时出错:
已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127
  ErrorMessage: 已安装 tzdata 软件包 post-installation 脚本 子进程返回错误状态 127
  InstallationDate: Installed on 2022-06-06 (174 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: tzdata
  Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: 已安装 
tzdata 软件包 post-installation 脚本 子进程返回错误状态 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998063/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1998042] Re: package python2-minimal 2.7.18-3 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1

2022-11-27 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => python-defaults (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1998042

Title:
  package python2-minimal 2.7.18-3 failed to install/upgrade: installed
  python2-minimal package post-installation script subprocess returned
  error exit status 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  when upgrading from 20.04 to 22.04 the updater throws an error
  relating to python2 (see report attached)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python2-minimal 2.7.18-3
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Nov 27 10:19:16 2022
  DuplicateSignature:
   package:python2-minimal:2.7.18-3
   Setting up python2-minimal (2.7.18-3) ...
   dpkg: error processing package python2-minimal (--configure):
installed python2-minimal package post-installation script subprocess 
returned error exit status 1
  ErrorMessage: installed python2-minimal package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-07-06 (509 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 3.3.3, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.0.9
  SourcePackage: python-defaults
  Title: package python2-minimal 2.7.18-3 failed to install/upgrade: installed 
python2-minimal package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2022-11-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1998042/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997615] Re: secondary display

2022-11-24 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1997615

Title:
  secondary display

Status in xorg package in Ubuntu:
  New

Bug description:
  I have connected an external display to my laptop through HDMI
  everything works fine but when I open chrome or teams on an external
  display it is too much zoomed which I don't encounter when I open
  nautilus or terminal or any other ubuntu native appps on my external
  display even the icons in the taskbar on the external display very
  large

  given that my

  laptop screen: 2880x1800 16:10

  external monitor: 1280x1024 5:4

  The way around that was to enable fractional scaling but then the text
  in my main laptop monitor is blurred

  I have attached a screen shot of the problem

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  Uname: Linux 5.19.5 x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 10:17:30 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1fd2]
  InstallationDate: Installed on 2022-09-30 (54 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop K3402ZA_S3402ZA
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.5 
root=UUID=b41a941c-21d0-4925-a5a8-3a8e402548b1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: K3402ZA.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K3402ZA
  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.ec.firmware.release: 208.31
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrK3402ZA.307:bd09/08/2022:br5.25:efr208.31:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopK3402ZA_S3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: VivoBook_ASUSLaptop K3402ZA_S3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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.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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1997615/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997278] Re: Merge tiff 4.4.0-5 (main) from Debian unstable (main)

2022-11-21 Thread Ubuntu Foundations Team Bug Bot
The attachment "tiff_4.4.0-5ubuntu1-kinetic-to-lunar.debdiff" seems to
be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tiff in Ubuntu.
https://bugs.launchpad.net/bugs/1997278

Title:
  Merge tiff 4.4.0-5 (main) from Debian unstable (main)

Status in tiff package in Ubuntu:
  In Progress

Bug description:
  Please merge tiff 4.4.0-5 (main) from Debian unstable (main)

  Changelog entries since current kinetic version 4.4.0-4ubuntu3:

  tiff (4.4.0-5) unstable; urgency=high

* Backport security fix for CVE-2022-3597, CVE-2022-3626 and CVE-2022-3627,
  out of bounds write and denial of service via a crafted TIFF file.
* Backport security fix for CVE-2022-3570, multiple heap buffer overflows
  via crafted TIFF file.
* Backport security fix for CVE-2022-3599, denial-of-service via a crafted
  TIFF file.
* Backport security fix for CVE-2022-3598, denial-of-service via a crafted
  TIFF file (closes: #1022555).

   -- Laszlo Boszormenyi (GCS)   Sun, 23 Oct 2022
  22:38:15 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1997224] Re: [NUC12WSKi5, Realtek ALC269VB, Green Headphone Out, Left] Playback problem with startup applications

2022-11-21 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1997224

Title:
  [NUC12WSKi5, Realtek ALC269VB, Green Headphone Out, Left] Playback
  problem with startup applications

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am starting an audio application (a.g. aplay, paplay, any media
  player) automatically after login (through the "Startup
  Applications"). I can see that the app is playing some audio through
  PulseAudio by checking pavucontrol. However, no sound is output to the
  speaker.

  When I delay the startup of the app a couple of seconds (e.g. via
  sleep 5), the sound is played as expected.

  We tried to analyze the issue here:
  https://answers.launchpad.net/ubuntu/+question/703840

  It seems that there is something wrong with the mixer when audio apps
  are launched very early after boot (or login?): The "Master Playback
  Volume" is set to 0 at the ALSA level, and it seems that PulseAudio is
  not able to raise it if audio playback is started so early. Attempts
  to automatically raise the "Master Playback Volume" through amixer
  also failed. The "Master Playback Volume" stays at 0. As mentioned
  above, when the start of the playback is delayed a bit, the "Master
  Playback Volume" is at 100 as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kiosk  1081 F pulseaudio
   /dev/snd/pcmC0D0c:   kiosk  1081 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kiosk  1081 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Nov 21 10:35:48 2022
  InstallationDate: Installed on 2022-11-21 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [NUC12WSKi5, Realtek ALC269VB, Green Headphone Out, Left] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2022
  dmi.bios.release: 5.26
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WSADL357.0085.2022.0718.1739
  dmi.board.name: NUC12WSBi5
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M46425-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWSADL357.0085.2022.0718.1739:bd07/18/2022:br5.26:svnIntel(R)ClientSystems:pnNUC12WSKi5:pvrM46708-302:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-302:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSKi5000:
  dmi.product.family: WS
  dmi.product.name: NUC12WSKi5
  dmi.product.sku: NUC12WSKi5000
  dmi.product.version: M46708-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1997224/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1996946] Re: Memory leak on every frame when reading GIF animations

2022-11-17 Thread Ubuntu Foundations Team Bug Bot
The attachment "Fix memory leak" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1996946

Title:
  Memory leak on every frame when reading GIF animations

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a big memory leak when reading GIF animations.

  The issue was identified and fixed in gdk-pixbuf two (2) years ago,
  but it was released in a version grater that the available in Ubuntu
  20.04.

  At first glance, the leak appears only when a static image is
  requested, but this function is used by pixbuf's upload functions and
  calls this function internally. So the leak happens every time a GIF
  is loaded.

  Here is the commit with the fix released in version 2.41:

  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

  A patch is attached to this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1996633] Re: Broken link in manpage for notify-send

2022-11-15 Thread Ubuntu Foundations Team Bug Bot
The attachment "libnotify-0.7.9.diff" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/1996633

Title:
  Broken link in manpage for notify-send

Status in libnotify package in Ubuntu:
  New

Bug description:
  Currently, the manpage for notify-send provides a see-also link to
  "http://www.galago-project.org/specs/notification/;, which returns a
  404 error when followed.

  User "Pablo A B" suggested
  "https://specifications.freedesktop.org/notification-
  spec/notification-spec-latest.html" as a replacement link on the
  Debian bug report logs. Original discussion is at
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869277#44


  Detailed info:

   Package: libnotify-bin
   Version: 0.7.9-3ubuntu5.22.04.1
   APT-Sources: https://nyc.mirrors.clouvider.net/ubuntu jammy-updates/main 
amd64 Packages

OS: Linux Mint 21
Kernel: Linux 5.15.0-53-generic
  Architecture: x86-64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1996633/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1995137] Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

2022-11-09 Thread Ubuntu Foundations Team Bug Bot
The attachment "mesa-build-lima-on-riscv64.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1995137

Title:
  "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

Status in mesa package in Ubuntu:
  New

Bug description:
  "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the
  Allwinner D1. This file is missing from the riscv64 packages, but
  present on others.  This affects (at least) 20.04 and 22.04.

  itrue@lxc-focal ~/tmp> dpkg -c 
libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so
  *snip*
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to 
./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so
  *snip*

  itrue@lxc-focal ~/tmp> dpkg -c 
libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so
  -rw-r--r-- root/root  16498024 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  -rw-r--r-- root/root   4692400 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1995897] Re: package dbus 1.12.16-2ubuntu2.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

2022-11-07 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => dbus (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1995897

Title:
  package dbus 1.12.16-2ubuntu2.1 failed to install/upgrade: dpkg-deb
  --control subprocess returned error exit status 2

Status in dbus package in Ubuntu:
  New

Bug description:
  I was just installing a update

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: dbus 1.12.16-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Nov  7 15:55:23 2022
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  InstallationDate: Installed on 2022-11-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.6
  SourcePackage: dbus
  Title: package dbus 1.12.16-2ubuntu2.1 failed to install/upgrade: dpkg-deb 
--control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1995897/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1995798] Re: MT7921K high latency when bluetooth headset is used

2022-11-06 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => bluez (Ubuntu)

-- 
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/1995798

Title:
  MT7921K high latency when bluetooth headset is used

Status in bluez package in Ubuntu:
  New

Bug description:
  When I use onboard WiFi and Bluetooth headset at the same time, the
  latency goes from ~30-50ms to 200-6500ms

  Motherboard: ASUS TUF GAMING X670E-PLUS WIFI
  BIOS: 0809

  Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream
  6.0.[135]

  $ lsb_release -rd
  Description:  Ubuntu 22.10
  Release:  22.10

  Also made upstream kernel bz:
  https://bugzilla.kernel.org/show_bug.cgi?id=216668

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: bluez 5.65-0ubuntu1
  Uname: Linux 6.0.5-060005-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 15:44:14 2022
  InstallationDate: Installed on 2022-10-15 (22 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic 
root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2022
  dmi.bios.release: 8.9
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X670E-PLUS WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 10:6F:D9:DD:4A:B0  ACL MTU: 1021:6  SCO MTU: 240:8
UP RUNNING PSCAN 
RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0
TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1995798/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

2022-11-04 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1842439

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0) from
  gtk_css_value_icon_theme_compute() from
  gtk_css_static_style_compute_value()

Status in apport package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Triaged
Status in gtk+3.0 source package in Focal:
  Confirmed

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1995015] Re: Logitech Brio LED doesn't light up with 22.10

2022-10-27 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1995015

Title:
  Logitech Brio LED doesn't light up with 22.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The LED light on my Logitech Brio webcam no longer lights up when the
  camera is active.

  When I exit an app that uses camera, the LED will illuminate for about
  a half second before turning off again.

  This behavior began after upgrading from Ubuntu 22.04 to 22.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brett  2437 F wireplumber
   /dev/snd/pcmC0D0c:   brett  2434 F...m pipewire
   /dev/snd/controlC1:  brett  2437 F wireplumber
   /dev/snd/seq:brett  2434 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 27 12:42:56 2022
  InstallationDate: Installed on 2021-12-16 (314 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-10-22 (5 days ago)
  dmi.bios.date: 09/13/2022
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0Y4GNJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd09/13/2022:br1.15:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA02:cvnDellInc.:ct10:cvr:sku096D:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1995015/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

2022-10-26 Thread Ubuntu Foundations Team Bug Bot
The attachment "openssh_9.0p1-1ubuntu8.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1993478

Title:
  package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade:
  postinstall script returned 1

Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Kinetic:
  Triaged

Bug description:
  [Impact]

  Users with /etc/ssh/sshd_config's that contain ListenAddress entries
  with the port specified will not be migrated to socket-activated ssh
  correctly, or may be migrated when they should not be (e.g. if
  ListenAddress, with a port number, is specified more than once). This
  leaves users with a broken sshd configuration.

  [Test Plan]

  There are 4 tests that should be used to verify the fix:

  1. Upgrade to Kinetic with just one ListenAddress entry, which
  specifies port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the 
following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * On an affected system, ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, ssh.socket will be active/listening, and
  /etc/systemd/system/ssh.socket.d/addresses.conf will contain the
  following:

  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234 

  2. Upgrade to Kinetic with multiple ListenAddress entries, each
  specifying port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the 
following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * On an affected system, migration will be attempted despite the multiple 
ListenAddress options, and ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, the ListenAddress option will be parsed
  correctly, and migration will not be attempted.

  3. On a Kinetic system which was migrated, but with errors (e.g. test
  case #1, prior to being patched), installing the new package should
  correct the ssh.socket configuration.

  
  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the 
following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.

  * The ssh.socket configuration should be fixed, and 
/etc/systemd/system/ssh.socket.d/addresses.conf should contain:
  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234 

  4. On a Kinetic system which was incorrectly migrated to ssh socket
  activation (e.g. test case #2, prior to being patched), installing the
  new package reverts to the previous behavior.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the 
following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable 

[Touch-packages] [Bug 1994144] Re: External display monitor not recognized

2022-10-25 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1994144

Title:
  External display monitor not recognized

Status in xorg package in Ubuntu:
  New

Bug description:
  xrandr lists four disconnected DPs (though my laptop has zero Display
  Ports) but does not list an HDMI, which is what I use to connect
  external monitor. Cable is sound b/c I have a dual boot setup and
  Windows recognizes the display without issue.

  Using Ubuntu 22.04.1 LTS
  I expected OS to recognize that I have a an HDMI port or alternatively that 
something is plugged into it
  OS does not seem to acknowledge same

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  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
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 25 08:45:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:899b]
  InstallationDate: Installed on 2022-10-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 30c9:0064 Luxvisions Innotech Limited HP TrueVision 
HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 17-cn2xxx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=ec82dd33-2985-40cd-a295-49463eb8e698 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2022
  dmi.bios.release: 15.2
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 899B
  dmi.board.vendor: HP
  dmi.board.version: 06.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 6.26
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd08/02/2022:br15.2:efr6.26:svnHP:pnHPLaptop17-cn2xxx:pvr:rvnHP:rn899B:rvr06.26:cvnHP:ct10:cvrChassisVersion:sku641G6UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 17-cn2xxx
  dmi.product.sku: 641G6UA#ABA
  dmi.sys.vendor: HP
  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.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1994144/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993892] Re: Window area is unusable

2022-10-22 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1993892

Title:
  Window area is unusable

Status in xorg package in Ubuntu:
  New

Bug description:
  The window area becomes unusable without warning and the same visual
  artefacts are seen (see attached). The system taskbar is still
  responsive, so I can logout/login, which resolves the issues
  temporarily.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 16:10:38 2022
  DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081]
  InstallationDate: Installed on 2022-10-14 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Intel(R) Client Systems NUC10i5FNH
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)
  dmi.bios.date: 04/09/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0052.2021.0409.1144
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i5FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M38063-307
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.9
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN:
  dmi.product.family: FN
  dmi.product.name: NUC10i5FNH
  dmi.product.sku: BXNUC10i5FNHN
  dmi.product.version: M38014-308
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1993892/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1993666] Re: Annoying constant background clinking noise

2022-10-20 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1993666

Title:
  Annoying constant background clinking noise

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Recently my laptop is producing a constant clinking noise. The noise
  is not load but it bothers after some time. However I noticed that
  noise stops while playing any youtube video. There is no noise even if
  the youtube sound is muted. However noise starts again after youtube
  video is stopped or the (Chrome) browser window is closed. My laptop
  is Lenovo Thinkpad X200 tablet.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mohan 16212 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 20 10:39:41 2022
  InstallationDate: Installed on 2019-09-15 (1131 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [7450BP8, Conexant CX20561 (Hermosa), Speaker, Internal] Playback 
problem
  UpgradeStatus: Upgraded to jammy on 2022-09-12 (38 days ago)
  dmi.bios.date: 11/29/2012
  dmi.bios.release: 3.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET71WW (3.21 )
  dmi.board.name: 7450BP8
  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.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:br3.33:efr1.6:svnLENOVO:pn7450BP8:pvrThinkPadX200Tablet:rvnLENOVO:rn7450BP8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X200 Tablet
  dmi.product.name: 7450BP8
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1993666/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2022-10-15 Thread Ubuntu Foundations Team Bug Bot
The attachment "FileChooser-Save_fix" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1949340

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1992707] Re: Extreme lag when switching to workspace overview

2022-10-12 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1992707

Title:
  Extreme lag when switching to workspace overview

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently updated from Ubuntu 20.04 to 22.04 and am experiencing
  significantly more lag. The most noticeable one is when entering and
  leaving the workspace overview. In 20.04 this was very fast (~0.5
  seconds?) and now it is taking ~2.8s after pressing Windows key before
  I can see the workspace overview and click to a different window or
  search for an application. The same in reverse; ~2.8s after pressing
  Esc or Windows key before I am returned control inside an application.

  I currently have some extensions installed but removed them all and
  was experiencing the same thing. This still occurs if I have no
  windows opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.14.0-1052.59-oem 5.14.21
  Uname: Linux 5.14.0-1052-oem 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..18.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  520.61.05  Thu Sep 29 
05:30:25 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 13 11:14:08 2022
  DistUpgraded: 2022-10-07 13:42:32,957 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/520.61.05, 5.14.0-1052-oem, x86_64: installed
   nvidia/520.61.05, 5.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107GL [Quadro P620] [10de:1cb6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GP107GL [Quadro P620] [10de:1264]
  InstallationDate: Installed on 2020-04-30 (895 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 30BBS6MG00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1052-oem 
root=UUID=124d9ac4-32b7-4679-a582-019a8f4235e0 ro quiet splash 
acpi_enfore_resources=lax vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-10-07 (5 days ago)
  dmi.bios.date: 07/21/2020
  dmi.bios.release: 1.48
  dmi.bios.vendor: LENOVO
  dmi.bios.version: S04KT48A
  dmi.board.name: 1037
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 19.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrS04KT48A:bd07/21/2020:br1.48:efr19.31:svnLENOVO:pn30BBS6MG00:pvrThinkStationP720:rvnLENOVO:rn1037:rvrNODPK:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30BB_BU_Think_FM_ThinkStationP720:
  dmi.product.family: ThinkStation P720
  dmi.product.name: 30BBS6MG00
  dmi.product.sku: LENOVO_MT_30BB_BU_Think_FM_ThinkStation P720
  dmi.product.version: ThinkStation P720
  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.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1992707/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1992563] Re: Boot freeze

2022-10-12 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1992563

Title:
  Boot freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  After recent update during boot Ubuntu freezes or I should wait a
  couple of minutes before gui starts.

  Laptop is Ubuntu certified (Thinkpad 17p gen1)

  Dmesg shows the following errors:
   [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-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  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 09:37:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/515.65.01, 5.15.0-48-generic, x86_64: installed
   nvidia/515.65.01, 5.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22bb]
   NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22bb]
  InstallationDate: Installed on 2020-11-20 (690 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20SN002WRT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=464ea21f-3e4f-4d24-97b2-deb2a870e063 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SN002WRT
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20SN002WRT:pvrThinkPadP17Gen1:rvnLENOVO:rn20SN002WRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SN002WRT
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  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.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.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1992563/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-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

2022-10-11 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
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:
  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.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  For Jammy and onward, iptables uses the new nft libraries so the
  problem does not appear unless the -legacy commands are used.

  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

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

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 1991857] Re: Web browser extensions bugs

2022-10-05 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1991857

Title:
  Web browser extensions bugs

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem seems to be from the Mozilla browser and the libre office
  word processor when I have been using google translate simultaneously.
  The screen has frozen several times and flickers reloading Facebook or
  whatever I seeing on the browser.

  I use extensions or plug-ins in the browser like Grammary to correct
  my texts and when I removed them my computer started to work better
  but still with some failures even in the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  5 18:45:12 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2022-09-30 (5 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. Inspiron 3442
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=2cd3ff22-e8b5-40a0-a450-10456d1ac17a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0878RH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd02/24/2014:br0.0:efr0.0:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0878RH:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:sku0651:
  dmi.product.name: Inspiron 3442
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  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.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1991857/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991494] Re: dark mode sometimes works

2022-10-02 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1991494

Title:
  dark mode sometimes works

Status in xorg package in Ubuntu:
  New

Bug description:
  the dark mode sometimes works and sometimes doesn't work. If i open
  Ubuntu Software store dark mode doesn't work and i have to go back to
  turn it back on again then it work's, its like it doesn't went to be
  in dark mode when i open Ubuntu Software store. it doesn't matter that
  must to me i just want you guys to know about it.

  this problem in on Ubuntu 22.10 Kinetic Kudu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-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  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  2 20:18:36 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e]
  InstallationDate: Installed on 2022-10-02 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  MachineType: ASUSTeK COMPUTER INC. X541UVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UVK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UVK
  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.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: X
  dmi.product.name: X541UVK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112-3ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1991494/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981794] Re: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

2022-09-29 Thread Ubuntu Foundations Team Bug Bot
The attachment "fix-dns-retry-confusion-jammy.patch" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1981794

Title:
  Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in dnsmasq source package in Jammy:
  Confirmed
Status in dnsmasq source package in Kinetic:
  Confirmed

Bug description:
  Duplicate or retried DNS queries will return REFUSED for one of the
  queries causing intermittent failures in clients.

  This probably breaks lots of things, but for me is causing 22.04's
  internet connection sharing to be unstable. It's particularly bad for
  my Xbox which seems to like sending duplicate queries.

  Here's an example capture:
  22:37:25.308212 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A? 
title.auth.xboxlive.com. (41)
  22:37:25.332711 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A? 
title.auth.xboxlive.com. (41)
  22:37:25.332740 IP 10.42.0.1.53 > 10.42.0.16.54248: 22442 Refused 0/0/0 (41)
  22:37:25.353003 IP 10.42.0.1.53 > 10.42.0.16.54248: 22442 2/0/0 CNAME 
title.auth.xboxlive.com.akadns.net., A 40.64.90.82 (105)

  This has been fixed in upstream as of Sept 2021 in the unreleased 2.87
  version. It's apparently a regression in version 2.86 (also released
  in Sept 2021). Ubuntu 22.04 and later all use the broken 2.86 version.

  Upstream fix:
  
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be1df48da1e2bd3d3feaa138c2

  Upstream bug thread:
  
https://www.mail-archive.com/search?l=dnsmasq-discuss%40lists.thekelleys.org.uk=subject:%22%5C%5BDnsmasq%5C-discuss%5C%5D+REFUSED+after+dropped+packets%22=oldest=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1981794/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1991067] Re: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls

2022-09-28 Thread Ubuntu Foundations Team Bug Bot
The attachment "lp-1991067-fix-gnutls-ftbfs.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1991067

Title:
  p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls

Status in p11-kit package in Ubuntu:
  In Progress

Bug description:
  Patches added in 0.24.1-1ubuntu1 prevent gnutls from building.
  Upstream has indicated that an additional change should have been
  included as mentioned at
  https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-09-28 Thread Ubuntu Foundations Team Bug Bot
The attachment "debdiffs.tgz" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379

Title:
  [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
  used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
 in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
 hardware and newer and impacts all JDK versions (8,11,17, etc.)
 that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
 platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
 Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
 on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
 of a small test program (in C) that makes use of the zlib1g library
 or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
 https://launchpadlibrarian.net/626003193/410-lp1990379.patch
 and there are not many issues to expect.

   * There could be a potential problem with the adler field
 in the strm struct.
 For example in case the struct is not as assumed or contains
 and unexpected value, which would then ripple through
 the other fields, too.

   * Structural changes could be identified with a test build that was done
 for all affected Ubuntu releases and for all major architectures:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]
   
   * The patch itself is the same for all zlib version in
 20.04, 22.04 and 22.10 - no further adjustments were needed.
  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

  ---
  External link: https://warthogs.atlassian.net/browse/PEI-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990824] Re: initramfs-tools: out-of-memory failures during autopkgtest

2022-09-26 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1990824

Title:
  initramfs-tools: out-of-memory failures during autopkgtest

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]

  Some autopkgtest tests are failing due to out-of-memory conditions,
  especially amd64-ata-only and net.

  It seems that we are creating a VM with 1GB only to run the amd64-ata-
  only test and even just 512MB for the net test.

  It probably makes sense to create larger VMs (at least 2GB) to run
  these tests with a more recent kernels (that will likely require a
  little more RAM).

  [Test case]

  sudo autopkgtest . -- null

  [Fix]

  Increase memory size of instances used to run the autopkgtests to 2GB.

  [Regression potential]

  We may experience regressions in small cloud instances, or systems
  with less than 2GB or RAM that are using a recent kernel (but this is
  more a generic potential regression, not strictly related to
  initramfs-tools).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990824/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1990736] Re: Xorg crash

2022-09-24 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1990736

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  J'ai des crash répétitif depuis longtemps. Et parfois l'écran se fige
  je ne peux plus rien faire. J'ai déjà réinstallé 3 x. Impossible de
  trouver le problème. Merci beaucoup.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 22:02:01 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2650]
  InstallationDate: Installed on 2022-09-08 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=fr_CH:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=30b5da29-5676-4f0b-bf23-d79eef14a3c5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1990736/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings

2022-09-15 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
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/1989807

Title:
  Move raspi cloud-init configuration to ubuntu-settings

Status in Ubuntu Seeds:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
  disable "real" cloud sources on the raspi images) is hacked into the
  images from livecd-rootfs. It would be preferable to have this in a
  server-specific variant of the ubuntu-raspi-settings package.

  To avoid dpkg conflicts, the file should be differently named
  (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to
  remove the old name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1079232] Re: OpenCV built without Qt support

2022-09-13 Thread Ubuntu Foundations Team Bug Bot
The attachment "4.5.4+dfsg-9ubuntu4.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1079232

Title:
  OpenCV built without Qt support

Status in opencv package in Ubuntu:
  Triaged
Status in opencv package in Debian:
  Unknown

Bug description:
  Is there any specific reason for openCV to be built without Qt
  support? The "new" Highgui Qt functions, already available in the
  version which ships with Ubuntu Precise, provide for much better user
  interfaces for simpler cases without having to build complete GUIs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1079232/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1989381] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script post-installation retor

2022-09-12 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => initramfs-tools (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1989381

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to
  install/upgrade: o subprocesso instalado, do pacote linux-firmware, o
  script post-installation retornou erro do status de saída 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Eu ainda não tenho conhecimento profundo no linux, mas sempre que faço
  o comando apt upgrade, ao termino recebo a notificação de erro, ou
  falha

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.5
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  emymatos   1701 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Sep 12 18:30:36 2022
  Dependencies: firmware-sof-signed 2.0-1ubuntu3
  ErrorMessage: o subprocesso instalado, do pacote linux-firmware, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2022-09-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Sony Corporation VPCEH40EB
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=UUID=8325b648-2499-45d2-b7d7-417a59c2beb8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to 
install/upgrade: o subprocesso instalado, do pacote linux-firmware, o script 
post-installation retornou erro do status de saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2012
  dmi.bios.release: 2.10
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0210Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 2.10
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0210Z9:bd06/21/2012:br2.10:efr2.10:svnSonyCorporation:pnVPCEH40EB:pvrC800BEL4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEH40EB
  dmi.product.sku: N/A
  dmi.product.version: C800BEL4
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989381/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1989246] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1

2022-09-10 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1989246

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 已安装
  initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  每次开机都会提示崩溃

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Sep 10 16:59:16 2022
  ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1
  InstallationDate: Installed on 2022-09-10 (0 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.7
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 已安装 
initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989246/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1989054] Re: Brightness bar not working properly

2022-09-08 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1989054

Title:
  Brightness bar not working properly on HP EliteBook 8460p

Status in linux package in Ubuntu:
  New

Bug description:
  My brightness doesn't change and stays at lowest brightness level till
  about 70% of the slider, after that the brightness starts increasing

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  8 10:47:44 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  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: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:161c]
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=f97ede9e-1a56-449e-81ae-d3b99491cdef ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2011
  dmi.bios.release: 15.8
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.08
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.45
  dmi.chassis.asset.tag: CNU147038F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.69
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:br15.8:efr151.69:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:skuSN119UC#ABA:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.sku: SN119UC#ABA
  dmi.product.version: A0001C02
  dmi.sys.vendor: Hewlett-Packard
  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.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989054/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1989003] Re: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-09-07 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1989003

Title:
  package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  i need to re-run the upgrade then it success updating the package

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-16-generic 5.19.0-16.16
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fenris72787 F wireplumber
   /dev/snd/seq:fenris72784 F pipewire
  CasperMD5CheckResult: unknown
  Date: Wed Sep  7 22:15:16 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-06-25 (803 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (134 days ago)
  dmi.bios.date: 07/12/2022
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0V2CCD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd07/12/2022:br1.18:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989003/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1989002] Re: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-09-07 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1989002

Title:
  package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  i need to re-run the upgrade then it success updating the package

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-16-generic 5.19.0-16.16
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fenris72787 F wireplumber
   /dev/snd/seq:fenris72784 F pipewire
  CasperMD5CheckResult: unknown
  Date: Wed Sep  7 22:15:16 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-06-25 (803 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (134 days ago)
  dmi.bios.date: 07/12/2022
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0V2CCD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd07/12/2022:br1.18:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989002/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2022-09-06 Thread Ubuntu Foundations Team Bug Bot
The attachment "1-0.38.4-0ubuntu2.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pixman in Ubuntu.
https://bugs.launchpad.net/bugs/1988796

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  New

Bug description:
  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1988790] Re: Pulse Audio 15.99.1 Simultaneous Output "Set as fallback" Not Working

2022-09-05 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1988790

Title:
  Pulse Audio 15.99.1 Simultaneous Output "Set as fallback" Not Working

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a new install of Ubuntu Studio 22.04 which came with Pulse
  Audio 15.99.1. Simultaneous Output "Set as fallback" will not stay.
  After selecting the button I then adjust the volume and the system
  adjusts the volume of my first sound card.

  There is a PA v16.1 out now that fixed a unstable combined-sink. Not
  sure if that will correct the fall back problem. Any guidance will be
  helpful. I do remember installing PA from scratch is a nightmare and
  wouldn't know where to start. I would consider without detailed
  instructions.

  Please keep me in the loop on this progress. Looking forward to trying
  KDE on 22.04 but I require whole house volume control.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-47.53-lowlatency 5.15.46
  Uname: Linux 5.15.0-47-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Sep  5 22:06:21 2022
  InstallationDate: Installed on 2022-09-05 (0 days ago)
  InstallationMedia: Ubuntu-Studio 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful
  Symptom_Card: Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] - HDA 
ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7704
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7704:bd12/16/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1988790/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims

2022-09-05 Thread Ubuntu Foundations Team Bug Bot
The attachment "Fix SCRAM support for SASL authentication" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1988730

Title:
  package libsasl2-modules provides only unsafe SASL bind mechanims

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  Current Cyrus libsasl2 packaging (Ubuntu Jammy) distributes SASL bind 
mechanims into different packages. Plained and shared secret mechanisms are 
provided by package libsasl2-modules:
  /usr/lib/x86_64-linux-gnu/sasl2/libanonymous.so
  /usr/lib/x86_64-linux-gnu/sasl2/libanonymous.so.2
  /usr/lib/x86_64-linux-gnu/sasl2/libanonymous.so.2.0.25
  /usr/lib/x86_64-linux-gnu/sasl2/libcrammd5.so
  /usr/lib/x86_64-linux-gnu/sasl2/libcrammd5.so.2
  /usr/lib/x86_64-linux-gnu/sasl2/libcrammd5.so.2.0.25
  /usr/lib/x86_64-linux-gnu/sasl2/libdigestmd5.so
  /usr/lib/x86_64-linux-gnu/sasl2/libdigestmd5.so.2
  /usr/lib/x86_64-linux-gnu/sasl2/libdigestmd5.so.2.0.25
  /usr/lib/x86_64-linux-gnu/sasl2/liblogin.so
  /usr/lib/x86_64-linux-gnu/sasl2/liblogin.so.2
  /usr/lib/x86_64-linux-gnu/sasl2/liblogin.so.2.0.25
  /usr/lib/x86_64-linux-gnu/sasl2/libntlm.so
  /usr/lib/x86_64-linux-gnu/sasl2/libntlm.so.2
  /usr/lib/x86_64-linux-gnu/sasl2/libntlm.so.2.0.25
  /usr/lib/x86_64-linux-gnu/sasl2/libplain.so
  /usr/lib/x86_64-linux-gnu/sasl2/libplain.so.2
  /usr/lib/x86_64-linux-gnu/sasl2/libplain.so.2.0.25

  The "safest" mechanism in this list is DIGEST-MD5, which is marked as
  obsolete by IANA and regarded as unsafe by IETF. Current safest
  standard mechanisms are SCRAM based (RFC7677).

  All SCRAM family SASL mechanisms of Cyrus SASL are provided by Ubuntu package 
libsasl2-modules-gssapi-mit:
  /usr/lib/x86_64-linux-gnu/sasl2/libscram.so
  /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2.0.25

  But the focus of this package is GSSAPI and GS2 SASL mechanism, which
  have nothing to do with SCRAM. In addition, this package conflicts
  with package libsasl2-modules-gssapi-heimdal. System administrators
  have to choose one package for support of GSSAPI or GSS-SPEGNO. If
  they prefer Heimdal there is no safe SASL shared secret mechanism
  available anymore on the server/workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1988730/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1988494] Re: ubuntu display error

2022-09-01 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1988494

Title:
  ubuntu display error

Status in xorg package in Ubuntu:
  New

Bug description:
  Booting from T7 Samsung SSD "trying Ubuntu" my display on Ubuntu seems
  to have a red/orange filter enabled.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  2 02:10:23 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Dell GA102 [GeForce RTX 3080 Lite Hash Rate] [1028:c890]
  LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Alienware Alienware Aurora Ryzen Edition
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2022
  dmi.bios.release: 2.3
  dmi.bios.vendor: Alienware
  dmi.bios.version: 2.3.1
  dmi.board.name: 0TYR0X
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr2.3.1:bd07/11/2022:br2.3:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.3.1:rvnAlienware:rn0TYR0X:rvrA01:cvnAlienware:ct3:cvrNotSpecified:sku0A8B:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora Ryzen Edition
  dmi.product.sku: 0A8B
  dmi.product.version: 2.3.1
  dmi.sys.vendor: Alienware
  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.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1988494/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1987711] Re: Ubuntu display get shifted after some time.

2022-08-25 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1987711

Title:
  Ubuntu display get shifted after some time.

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It is continuation of this bug:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583
  where advised fix was applied. 

  Summay: After ubuntu is turned on, after some time screen gets shifted
  to side. (and starts to overlap)

  I setup webcamera to record screen, and video below shows what it looked 
like. 
  after fix were applied.
  www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4
  (video was cropped, and slowed down 2x)

  before fix was applied shift looked somehow like this:
  www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4
  (video is also cropped, and slowed down 2x)

  During shift no one was present on computer.

  Is there any idea how to enable some more detailed log or something? I 
probably can pinpoint exact moment in time when shift happened. 
  i tried to read log journalctl, but I found nothing interesting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  Date: Fri Aug 26 02:31:10 2022
  DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015]
  InstallationDate: Installed on 2022-02-17 (189 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen
   Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Default string Default string
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago)
  dmi.bios.date: 10/07/2021
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GSKU0504.V54
  dmi.board.asset.tag: Default string
  dmi.board.name: SKYBAY
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  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.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: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1987711/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1987252] Re: "Beacon request: No valid channels" for 802.11k measurement (RRM) then frequent disconnections

2022-08-23 Thread Ubuntu Foundations Team Bug Bot
The attachment "rrm-include-passive-channels-in-active-beacon-report-
scan.patch" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1987252

Title:
  "Beacon request: No valid channels" for 802.11k measurement (RRM) then
  frequent disconnections

Status in wpa package in Ubuntu:
  New

Bug description:
  When running a laptop with a mesh WiFi network, frequent
  disconnections happen like 10 to 20 times per hour. And the issue has
  disappeared by applying the following patch.

  https://w1.fi/cgit/hostap/commit/?id=8e0ac53660aaa9691e140156c47fddb7cd8c62b6
  > RRM: Include passive channels in active beacon report scan
  > When receiving a beacon report request with the mode set to active,
  > channels that are marked as NO_IR were not added to the scan request.
  > However, active mode just mean that active scan is allowed, but not
  > that it is a must, so these channels should not be omitted.
  > Include channels that are marked as NO_IR in the scan request even
  > if the mode is set to active.

  So I'd like to request a backport of it.

  I believe the following combination of parameters is the key to
  trigger the "Beacon request: No valid channels" issue.

  - two or more access points as a mesh with 802.11k/v enabled
  - wpasupplicant 2.10 series or lower
- kinetic with wpasupplicant=2.10-9ubuntu1
- jammy and wpasupplicant=2:2.10-6ubuntu2
- or lower
  - Using 5GHz
  - and all of 5GHz channels are marked as:
- NO_IR (sudo wpa_cli get_capability freq)
- or PASSIVE-SCAN (iw reg get)

  
  The log has a sudden "Connection to AP lost" with "No beacon heard and the 
time event is over already" as follows:

  > kernel: [136930.972759] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost
  > kernel: [136931.217753] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz
  > kernel: [136931.229486] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3)
  > kernel: [136931.234536] wlp3s0: authenticated
  > kernel: [136931.239353] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3)
  > kernel: [136931.253596] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz 
(capab=0x1511 status=0 aid=2)
  > kernel: [136931.255411] wlp3s0: associated
  > kernel: [136931.843561] iwlwifi :03:00.0: No beacon heard and the time 
event is over already...
  > kernel: [136931.843650] wlp3s0: Connection to AP 6c:5a:b0:xx:yy:zz lost
  > kernel: [136932.067556] wlp3s0: authenticate with 6c:5a:b0:xx:yy:zz
  > kernel: [136932.078277] wlp3s0: send auth to 6c:5a:b0:xx:yy:zz (try 1/3)
  > kernel: [136932.085292] wlp3s0: authenticated
  > kernel: [136932.087341] wlp3s0: associate with 6c:5a:b0:xx:yy:zz (try 1/3)
  > kernel: [136932.100737] wlp3s0: RX AssocResp from 6c:5a:b0:xx:yy:zz 
(capab=0x1511 status=0 aid=2)
  > kernel: [136932.103238] wlp3s0: associated
  > kernel: [136932.392477] wlp3s0: Limiting TX power to 20 (23 - 3) dBm as 
advertised by 6c:5a:b0:xx:yy:zz

  And wpa_supplicant considers it in syslog as:
  wlp3s0: CTRL-EVENT-DISCONNECTED bssid=6c:5a:b0:xx:yy:zz reason=4 
locally_generated=1

  By enabling debug of wpa_supplicant with `sudo wpa_cli log_level
  DEBUG`, I found "Beacon request: No valid channels" message on the
  client (Ubuntu laptop) at the same timing as 11k measuremrent on the
  AP every 6 seconds.

  > Aug 21 14:01:06 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: 
Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 
255 ChanId 48  ESSId 0
  > Aug 21 14:01:06 deco daemon.err nrd[22822] 
estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ
  >
  > Aug 21 14:01:06 t480 wpa_supplicant[1613]: Beacon request: No valid channels
  >
  > Aug 21 14:01:12 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: 
Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 
255 ChanId 48  ESSId 0
  > Aug 21 14:01:12 deco daemon.err nrd[22822] 
estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ
  >
  > Aug 21 14:01:12 t480 wpa_supplicant[1613]: Beacon request: No valid channels
  >
  > Aug 21 14:01:18 deco daemon.notice nrd[22822]: estimatorPerformMeasurement: 
Do 11k measuremrent for D4:3B:04:XX:YY:ZZ on channel 48 from serving BSS APId 
255 ChanId 48  ESSId 0
  > Aug 21 14:01:18 deco daemon.err nrd[22822] 
estimatorCmnHandleBeaconReportEvent: Invalid beacon report for D4:3B:04:XX:YY:ZZ
  >
  > Aug 21 14:01:18 t480 wpa_supplicant[1613]: Beacon request: No valid channels

  This suggests that there is a clear disagreement around 11k between
  the client and the AP. And after 

[Touch-packages] [Bug 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.

2022-08-22 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1987340

Title:
  Please merge lvm2 2.03.16-1 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1987185] Re: mtds device is empty

2022-08-20 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1987185

Title:
  mtds device is empty

Status in xorg package in Ubuntu:
  New

Bug description:
  I am getting error when I start the laptop ACEPI error no pointer back
  to namespace and mtds device is empty

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 21 05:35:10 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
 Subsystem: Dell Radeon 530 [1028:0810]
  InstallationDate: Installed on 2022-08-04 (16 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=73d9eb29-2272-480e-b48a-93768b7bc792 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 05T59R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd03/25/2022:br1.9:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn05T59R:rvrA00:cvnDellInc.:ct10:cvr:sku0810:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112+git2208190500.46d1e9~oibaf~j
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3~git2208200600.1d521a~oibaf~j
  version.libgl1-mesa-glx: libgl1-mesa-glx 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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1987185/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1987126] Re: No audio devices are recognized

2022-08-19 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => pulseaudio (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1987126

Title:
  No audio devices are recognized

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No audio devices are recognized, both in and out. This worked on 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu1 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf]
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 19 11:35:58 2022
  InstallationDate: Installed on 2022-07-09 (41 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to kinetic on 2022-08-19 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0904
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H370M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Nobilis
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0904:bd09/14/2018:br5.13:svnEquusComputerSystems:pnNobilis:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH370M-PLUS:rvrRev1.xx:cvnNobilis:ct3:cvrDefaultstring:skuASUS_MB_CNL:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Nobilis
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: Equus Computer Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987126/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1987004] Re: Touchpad stops functioning after wakeup

2022-08-18 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1987004

Title:
  Touchpad stops functioning after wakeup

Status in xorg package in Ubuntu:
  New

Bug description:
  Although it happens randomly. The touchpad stops working where the
  cursor freezes after the system wakes up from suspension mode. The
  mouse, though, does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Aug 18 15:15:02 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Today
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=a0f3455c-f4c6-4dc2-a499-28f2f500c291 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  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 22.0.5-0ubuntu0.1
  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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1987004/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1983359] Re: hwrng drivers missing in initrd.img

2022-08-18 Thread Ubuntu Foundations Team Bug Bot
The attachment "initramfs-tools-0.140ubuntu14..0.140ubuntu15.debdiff"
seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff.  If the attachment isn't a patch, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are member
of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1983359

Title:
  hwrng drivers missing in initrd.img

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Jammy:
  New

Bug description:
  The initialization of the entropy buffer of the urandom device is
  critical for security.

  When booting Jammy 22.04.1 on QEMU riscv64 I see the following
  warnings:

  [   14.654546] random: lvm: uninitialized urandom read (4 bytes read)
  [   15.247995] random: lvm: uninitialized urandom read (2 bytes read)
  [   22.484719] random: lvm: uninitialized urandom read (4 bytes read)
  [   43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read)
  [   48.862281] random: lvm: uninitialized urandom read (4 bytes read)

  Module virtio-rng.ko is missing in initrd.img.
  Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings.

  Hardware RNG drivers should generally be included in the initrd to
  provide early entropy.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1986841] Re: canon pixma g2010 printer connected through usb, added in printer settings but unable to print through print command

2022-08-17 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => cups (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1986841

Title:
  canon pixma g2010 printer connected through usb, added in printer
  settings but unable to print through print command

Status in cups package in Ubuntu:
  New

Bug description:
  canon pixma g2010 printer connected through usb, added in printer
  settings when i searched for it but when i give print command to print
  a page it sends command and still no print out and also there is no
  pending jobs showing, and when i tried to print test page it is also
  not printing.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/main/l/linux-oem-5.17/linux-modules-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 17 21:37:30 2022
  InstallationDate: Installed on 2022-07-11 (36 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lpstat:
   device for CUPS-BRF-Printer: cups-brf:/
   device for G2010: usb://Canon/G2010%20series?serial=20B026=1
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RV411/RV511/E3511/S3511/RV711/E3411
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/G2010.ppd', 
'/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/G2010.ppd: Permission denied
   grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2011
  dmi.bios.release: 4.0
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 04PA.M006.20110615.XW
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: RV411/RV511/E3511/S3511/RV711/E3411
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr04PA.M006.20110615.XW:bd06/15/2011:br4.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnRV411/RV511/E3511/S3511/RV711/E3411:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRV411/RV511/E3511/S3511/RV711/E3411:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:sku:
  dmi.product.name: RV411/RV511/E3511/S3511/RV711/E3411
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1986606] Re: When locking computer with Win+L, screen goes black permanently

2022-08-15 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1986606

Title:
  When locking computer with Win+L, screen goes black permanently

Status in xorg package in Ubuntu:
  New

Bug description:
  I had a workaround for this in 20.04, press and hold Win+L so it types
  letters into the input field as you lock the computer. This kept the
  screen from going black, and I could manually dim the laptop screen
  (fn+brightness) and walk away. In 22.04 the screen now fades to black
  immediately when I press Win+L, even though I can see the first few
  characters being entered on the input field as the screen fades to
  black.

  Black screen (as in fade to black for inactivity) seems to be
  irreversible on this computer, no amount of mouse-wiggling, 3 finger
  salute (ctrl-alt-delete), or usb dongle removal and reattachment will
  cause the display to wake up. In 20.04 I could get around this on
  computer lock by continuing to press Win+L until the input box had
  lots of input. That seemed to stop the screen from dimming in 20.04.
  Not working in 22.04.

  The only way I have found out of this is to do a hard power down (7+
  seconds pressing power button). For obvious reasons I prefer not to do
  this often.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 15 22:03:08 2022
  DistUpgraded: 2022-08-15 15:36:20,169 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:121a]
  InstallationDate: Installed on 2022-03-14 (154 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. HD WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros 
QCA9377 Bluetooth
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-576
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (0 days ago)
  dmi.bios.date: 10/24/2017
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: KBL
  dmi.board.version: V1.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr1.10:svnAcer:pnAspireE5-576:pvrV1.32:rvnKBL:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:sku:
  dmi.product.family: Aspire E 15
  dmi.product.name: Aspire E5-576
  dmi.product.sku: 
  dmi.product.version: V1.32
  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 22.0.5-0ubuntu0.1
  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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1986606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1986451] Re: ubuntu dock bug

2022-08-14 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1986451

Title:
  ubuntu dock bug

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-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  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  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 22.0.5-0ubuntu0.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1986451/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1985983] Re: Horiontal nav flicks

2022-08-12 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1985983

Title:
  Horiontal nav flicks

Status in xorg package in Ubuntu:
  New

Bug description:
  When i hover my mouse on the left side horizontal navigation page and
  then use ALT+TAB to switch to a full-screen app, such as chrome or the
  terminal, the navigation page flicks between visible and hidden
  forever. Video descrpition in here:

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-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  470.141.03  Thu Jun 30 
18:45:31 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 12 09:44:19 2022
  DistUpgraded: 2022-08-12 08:59:18,023 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/470.141.03, 5.15.0-43-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!)
   nvidia/470.141.03, 5.15.0-46-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!)
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 
[8086:2086]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] 
[8086:2086]
  InstallationDate: Installed on 2021-06-12 (426 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Avell High Performance Avell A60 MUV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=bebf872e-8428-4ce7-8439-4f0eee074aae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QCCFL357.0122.2020.0911.1520
  dmi.board.name: Avell High Performance
  dmi.board.vendor: Avell High Performance
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnAvellA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV:
  dmi.product.family: QC
  dmi.product.name: Avell A60 MUV
  dmi.product.sku: A60 MUV
  dmi.sys.vendor: Avell High Performance
  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.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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1985983/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1984157] Re: [Lenovo Legion Y9000X IAH7 (82TF), Realtek ALC287, Speaker, Internal] No sound at all

2022-08-10 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1984157

Title:
  [Lenovo Legion Y9000X  IAH7 (82TF), Realtek ALC287, Speaker, Internal]
  No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Lenovo Legion Y9000X (or Legion S7) IAH7, model prefix 82TF.
  No sound output when unplug earphone jack;
  Output weirded sound like "pufpufpufpufpufpuf" in earphone after plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thelastline   2474 F pulseaudio
   /dev/snd/controlC0:  thelastline   2474 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 15:12:04 2022
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thelastline   2474 F pulseaudio
   /dev/snd/controlC0:  thelastline   2474 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82TF, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2022
  dmi.bios.release: 1.39
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JYCN39WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y9000X IAH7
  dmi.ec.firmware.release: 1.39
  dmi.modalias: 
dmi:bvnLENOVO:bvrJYCN39WW:bd06/16/2022:br1.39:efr1.39:svnLENOVO:pn82TF:pvrLegionY9000XIAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrLegionY9000XIAH7:skuLENOVO_MT_82TF_BU_idea_FM_LegionY9000XIAH7:
  dmi.product.family: Legion Y9000X IAH7
  dmi.product.name: 82TF
  dmi.product.sku: LENOVO_MT_82TF_BU_idea_FM_Legion Y9000X IAH7
  dmi.product.version: Legion Y9000X IAH7
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1984157/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1983998] Re: USB sound card not detected

2022-08-08 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1983998

Title:
  USB sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  usbc mics https://www.boya-mic.com/lavaliermicrophones/1430.html

  connects and immediately disconnects, ls usb hangs for a while, when usbc 
device is connected.
  it works on win laptop well.

  
  ```
  [10877.622942] usb 3-4: new full-speed USB device number 28 using xhci_hcd
  [10877.779590] usb 3-4: New USB device found, idVendor=0c76, idProduct=153f, 
bcdDevice= 1.00
  [10877.779596] usb 3-4: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [10877.779599] usb 3-4: Product: USB PnP Audio Device
  [10877.983589] usb 3-4: Warning! Unlikely big volume range (=496), cval->res 
is probably wrong.
  [10877.983593] usb 3-4: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16
  [10878.009593] usb 3-4: Warning! Unlikely big volume range (=1008), cval->res 
is probably wrong.
  [10878.009597] usb 3-4: [49] FU [Speaker Playback Volume] ch = 2, val = 
-16129/-1/16
  [10878.035587] usb 3-4: Warning! Unlikely big volume range (=496), cval->res 
is probably wrong.
  [10878.035591] usb 3-4: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16
  [10878.038757] input: USB PnP Audio Device as 
/devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-4/3-4:1.3/0003:0C76:153F.001B/input/input45
  [10878.095081] hid-generic 0003:0C76:153F.001B: input,hidraw6: USB HID v1.00 
Device [USB PnP Audio Device] on usb-:06:00.3-4/input3
  [10878.095179] usb 3-3: USB disconnect, device number 27
  [10878.426945] usb 3-3: new full-speed USB device number 29 using xhci_hcd
  [10878.587590] usb 3-3: New USB device found, idVendor=0c76, idProduct=153f, 
bcdDevice= 1.00
  [10878.587597] usb 3-3: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [10878.587599] usb 3-3: Product: USB PnP Audio Device
  [10878.783592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res 
is probably wrong.
  [10878.783597] usb 3-3: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16
  [10878.809597] usb 3-3: Warning! Unlikely big volume range (=1008), cval->res 
is probably wrong.
  [10878.809601] usb 3-3: [49] FU [Speaker Playback Volume] ch = 2, val = 
-16129/-1/16
  [10878.835592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res 
is probably wrong.
  [10878.835596] usb 3-3: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16
  [10878.838754] input: USB PnP Audio Device as 
/devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-3/3-3:1.3/0003:0C76:153F.001C/input/input46
  [10878.895092] hid-generic 0003:0C76:153F.001C: input,hidraw5: USB HID v1.00 
Device [USB PnP Audio Device] on usb-:06:00.3-3/input3
  [10878.895190] usb 3-4: USB disconnect, device number 28
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-45.48-generic 5.15.39
  Uname: Linux 5.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vany  12211 F pulseaudio
   /dev/snd/controlC0:  vany  12211 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 18:28:32 2022
  InstallationDate: Installed on 2020-11-26 (619 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: Upgraded to jammy on 2022-05-23 (76 days ago)
  dmi.bios.date: 04/01/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1407
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1407:bd04/01/2020:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1983998/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [Bug 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)

2022-08-04 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1958055

Title:
  sudo apport-kde is in a different design (stripped
  XDG_CURRENT_DESKTOP)

Status in sudo package in Ubuntu:
  Confirmed
Status in sudo source package in Jammy:
  New

Bug description:
  [Impact]

  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot). This
  applies to all Qt applications.

  [Test Plan]

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  Same result with KDE:

  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f

  [Analysis]

  Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
  but XDG_CURRENT_DESKTOP is not in the list of environment variables to
  preserve (and not in env_keep in /etc/sudoers).

  On other other hand, sudo preserves the DISPLAY environment variable:

  $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)'
  XAUTHORITY=/run/user/1000/gdm/Xauthority
  DISPLAY=:0
  MAIL=/var/mail/root
  LOGNAME=root
  USER=root
  HOME=/root
  SHELL=/bin/bash

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  [Other Info]

  This changes was accepted upstream: https://github.com/sudo-
  project/sudo/pull/165

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.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/sudo/+bug/1958055/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1983529] Re: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4)

2022-08-03 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1983529

Title:
  No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Not sure if it's relevant, but there are some errors in dmesg:

  $ sudo dmesg | grep audio

  [   14.290226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
  [   14.440430] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
  [   14.445129] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on 
Skylake+ platform, using SOF driver
  [   14.445811] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [   14.445861] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI 
codec failed
  [   14.448966] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
  [   15.467232] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, 
ret: -5
  [   15.467478] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1
  [   15.467479] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [   15.467484] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT 
tables: 2
  [   15.478062] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:1:1-3964a
  [   15.478066] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 
Kernel ABI 3:18:0
  [   15.478068] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more 
recent than kernel
  [   15.478073] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man 
header type 3 size 0x30
  [   15.584074] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:1:1-3964a
  [   15.584079] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 
Kernel ABI 3:18:0
  [   15.584080] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more 
recent than kernel
  [   15.591457] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 
Kernel ABI 3:18:0
  [   15.591461] sof-audio-pci-intel-tgl :00:1f.3: warn: topology ABI is 
more recent than kernel
  [   15.624250] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not 
yet available, widget card binding deferred
  [   15.643720] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
  [   15.643726] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   15.643727] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [   15.643728] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0
  [   15.643729] snd_hda_codec_realtek ehdaudio0D0:inputs:
  [   15.643730] snd_hda_codec_realtek ehdaudio0D0:  Mic=0x19

  
  Because of those ABI warnings, I tried building the latest mainline kernel 
from source, and the ABI warnings went away, but I still have no sound.

  $ sudo dmesg | grep audio # On latest upstream kernel

  [   17.519958] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
  [   17.804900] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
  [   17.805661] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on 
Skylake+ platform, using SOF driver
  [   17.806225] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [   17.806265] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI 
codec failed
  [   17.808071] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
  [   21.844005] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, 
ret: -5
  [   21.844263] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1
  [   21.844264] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [   21.844267] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT 
tables: 2
  [   21.853970] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:1:1-3964a
  [   21.853971] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 
Kernel ABI 3:21:0
  [   21.853979] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man 
header type 3 size 0x30
  [   21.961252] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:1:1-3964a
  [   21.961255] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 
Kernel ABI 3:21:0
  [   21.967719] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 
Kernel ABI 3:21:0
  [   21.979145] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
  [   21.979147] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   21.979148] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [   21.979149] snd_hda_codec_realtek ehdaudio0D0:   

[Touch-packages] [Bug 1983417] Re: Bluetooth volume low on reconnection

2022-08-02 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1983417

Title:
  Bluetooth volume low on reconnection

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  How to reproduce:

  So as to start from a fresh base setting, restart Bluetooth service by
  opening up a terminal and typing:

  sudo service bluetooth restart

  Connect Bluetooth audio device (I'm using Xbox Wireless Headset)

  Adjust volume to maximum (non amplified)

  Disconnect Bluetooth audio device by turning it off

  Reconnect Bluetooth audio device and adjust volume back up to maximum
  (non amplified) if it has lowered automatically (I believe this is a
  known hearing safety feature)

  Notice the volume is lower than before even though it is set to
  maximum.

  Again, restart the Bluetooth service like before.

  Reconnect Bluetooth audio device and adjust volume back up to maximum
  (non amplified).

  Notice the volume is as high as it originally was.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eodeluga   1600 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  2 23:19:08 2022
  InstallationDate: Installed on 2022-03-28 (127 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Xbox Wireless Headset
  Symptom_PulseAudioLog:
   Aug 02 23:15:03 tecra-z40-c-106 dbus-daemon[536]: [system] Rejected send 
message, 0 matched rules; type="error", sender=":1.80" (uid=1000 pid=1600 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") 
interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.14" (uid=0 pid=534 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
   Aug 02 23:15:03 tecra-z40-c-106 dbus-daemon[536]: [system] Rejected send 
message, 0 matched rules; type="error", sender=":1.80" (uid=1000 pid=1600 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") 
interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.14" (uid=0 pid=534 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
  Symptom_Type: Volume slider, or mixer problems
  Title: [Xbox Wireless Headset, playback] volume slider problem
  UpgradeStatus: Upgraded to jammy on 2022-07-31 (2 days ago)
  dmi.bios.date: 06/20/2016
  dmi.bios.release: 5.80
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.80
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z40-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.80:bd06/20/2016:br5.80:efr1.20:svnTOSHIBA:pnTECRAZ40-C:pvrPT465E-00301QEN:rvnTOSHIBA:rnTECRAZ40-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPT465E:
  dmi.product.family: 00
  dmi.product.name: TECRA Z40-C
  dmi.product.sku: PT465E
  dmi.product.version: PT465E-00301QEN
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1983417/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

2022-07-26 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1970449

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  [Test Plan]

  1. Launch software-properties-gtk
  2. Click on the "Authentication" tab
  3. At least one key should be listed

  [Where problems could occur]

  I fail to come up with possible problems. The failures was a
  regression and the fixed version has a test case.

  [Other Infos]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982693] Re: USB-Audio device UMC204HD disappears after suspend

2022-07-24 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1982693

Title:
  USB-Audio device UMC204HD disappears after suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Coming back from sleep, Behringer UMC204HD is not in the list of
  devices in Settings > Sound. It comes back if I unplug and plug back
  in.

  I tried with/without a USB hub in between, I tried setting
  "usbcore.autosuspend=-1". No help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 15:04:57 2022
  InstallationDate: Installed on 2022-04-21 (93 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful
  Symptom_Card: HD Webcam C525 - HD Webcam C525
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [USB-Audio - UMC204HD 192k, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.H0
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M PRO-VH (MS-7996)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.H0:bd06/16/2018:br5.12:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VH(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7996
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1982693/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982690] Re: screen flickering

2022-07-24 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1982690

Title:
  screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  sometimes screen is continuously flickering

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 17:06:28 2022
  DistUpgraded: 2022-04-25 11:41:26,744 INFO cache.commit()
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / 
Radeon 520 Mobile] [1028:06b2]
  InstallationDate: Installed on 2021-02-24 (515 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=e2bb84ca-dd6e-40ec-8b37-00f696fb958e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (90 days ago)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 04D1V1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd09/07/2020:br1.9:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct10:cvr:sku06B2:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5559
  dmi.product.sku: 06B2
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1982690/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982658] Re: 22.04 Input devices freeze when dock connects with monitor

2022-07-23 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1982658

Title:
  22.04 Input devices freeze when dock connects with monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  see here https://askubuntu.com/a/1404413 I have the same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 23 13:41:58 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0af3]
  InstallationDate: Installed on 2022-07-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 9320
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic 
root=/dev/mapper/lvm-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2022
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0KNXGD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/13/2022:br1.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0KNXGD:rvrA00:cvnDellInc.:ct10:cvr:sku0AF3:
  dmi.product.family: XPS
  dmi.product.name: XPS 9320
  dmi.product.sku: 0AF3
  dmi.sys.vendor: Dell Inc.
  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 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: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1982658/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982555] Re: core dump file empty inside container

2022-07-22 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
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/1982555

Title:
  core dump file empty inside container

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  New
Status in apport source package in Jammy:
  New

Bug description:
  [Impact]

  Apport will write an empty core dump file inside of containers.

  [Test plan]

  Run following testcase script inside a LXC container:

  ```
  rm -f /var/lib/apport/coredump/*
  ulimit -c 100
  sleep 86400 &
  killall -3 sleep
  ```

  Apport will write a core dump into /var/lib/apport/coredump, but this
  core dump is empty:

  ```
  $ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
File: 
/var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: fd00h/64768d  Inode: 120848663   Links: 1
  Access: (0400/-r)  Uid: (0/root)   Gid: (0/root)
  Access: 2022-07-22 07:54:48.838682067 +
  Modify: 2022-07-22 07:54:48.838682067 +
  Change: 2022-07-22 07:54:48.838682067 +
   Birth: 2022-07-22 07:54:48.838682067 +
  ```

  This file should not be empty.

  [Other Info]

  The autopkgtest for armhf are run inside a LXC container and the test
  case test_core_dump_packaged_sigquit triggers this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1982555/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982495] Re: distorted audio after update 5.15.0-42-lowlatency

2022-07-21 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => pulseaudio (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1982495

Title:
  distorted audio after update 5.15.0-42-lowlatency

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi.

  It is happening again updating 5.15.0-42 LOWLATENCY, as
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066

  Focusrite 2i2 2nd generation.

  Booting 5.13.0-52 LOWLATENCY solve, no distorted audio.

  Thx in advance, pleased to report more information about

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.15.0-42.45~20.04.1-lowlatency 5.15.39
  Uname: Linux 5.15.0-42-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alf1589 F jackdbus
   /dev/snd/pcmC1D0c:   alf1589 F...m jackdbus
   /dev/snd/pcmC1D0p:   alf1589 F...m jackdbus
   /dev/snd/seq:alf1717 F a2jmidid
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Jul 21 17:17:29 2022
  InstallationDate: Installed on 2021-02-05 (530 days ago)
  InstallationMedia: Ubuntu-Studio 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA NVidia
  Title: [USB-Audio - Scarlett 2i2 USB, playback] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2012
  dmi.bios.release: 30.240
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: EasyNote TK85
  dmi.board.vendor: Packard Bell
  dmi.board.version: V1.30
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.30
  dmi.modalias: 
dmi:bvnPackardBell:bvrV1.30:bd08/13/2012:br30.240:svnPackardBell:pnEasyNoteTK85:pvrV1.30:rvnPackardBell:rnEasyNoteTK85:rvrV1.30:cvnPackardBell:ct10:cvrV1.30:skuCalpella_CRB:
  dmi.product.family: Intel_Mobile
  dmi.product.name: EasyNote TK85
  dmi.product.sku: Calpella_CRB
  dmi.product.version: V1.30
  dmi.sys.vendor: Packard Bell
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2022-07-21T16:49:41.895417

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1982495/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982218] Re: wait-online does not correctly identify managed links

2022-07-19 Thread Ubuntu Foundations Team Bug Bot
The attachment "0001-wait-online-Check-if-links-are-in-the-configuring-
st.patch" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1982218

Title:
  wait-online does not correctly identify managed links

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu's packaging of systemd-networkd-wait-online includes a patch
  (UBUNTU-wait-online-exit-if-no-links-are-managed) intended to exit if
  none of the present links are managed by systemd-networkd.  However,
  the patch fails to identify links in the "configuring" state, which
  implies they are managed, but not yet fully online.  This undermines
  the purpose of systemd-networkd-wait-online with the --any option,
  since at the time the systemd-networkd-wait-online service is started,
  managed links are _likely_ in a configuring, but-not-yet-configured
  state.

  Please see the attached patch.  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1982213] Re: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] No sound at all

2022-07-19 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1982213

Title:
  [XPS 13 9370, Realtek ALC3271, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  playback sound off after lock/sleep. settings output shows audio
  detection from playback, but no sound from speakers. setting speaker
  test also does not (ever) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192
  Uname: Linux 5.4.0-122-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fmulvey2530 F pulseaudio
   /dev/snd/pcmC0D0c:   fmulvey2530 F...m pulseaudio
   /dev/snd/pcmC0D0p:   fmulvey2530 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 19 14:57:56 2022
  InstallationDate: Installed on 2018-11-24 (1332 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fmulvey2530 F pulseaudio
   /dev/snd/pcmC0D0c:   fmulvey2530 F...m pulseaudio
   /dev/snd/pcmC0D0p:   fmulvey2530 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-10-22 (634 days ago)
  dmi.bios.date: 06/06/2022
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd06/06/2022:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1982213/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-18 Thread Ubuntu Foundations Team Bug Bot
The attachment "debdiff_nettle_3.7.3-1build2_to_3.8-0ubuntu1.diff" seems
to be a debdiff.  The ubuntu-sponsors team has been subscribed to the
bug report so that they can review and hopefully sponsor the debdiff.
If the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in nettle package in Ubuntu:
  In Progress

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

2022-07-18 Thread Ubuntu Foundations Team Bug Bot
The attachment "openssl3_set_options.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1981807

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981707] Re: package linux-image-5.15.0-41-generic 5.15.0-41.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-07-14 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1981707

Title:
  package linux-image-5.15.0-41-generic 5.15.0-41.44~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  f

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jul 14 15:48:33 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-04-28 (441 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-41-generic 5.15.0-41.44~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981707/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1370953] Re: layout switch is delayed

2022-07-11 Thread Ubuntu Foundations Team Bug Bot
The attachment "keyboard-layout-switching-delay-workaround.patch" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1370953

Title:
  layout switch is delayed

Status in GNOME Shell:
  New
Status in console-setup package in Ubuntu:
  Incomplete
Status in gconf package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1370953/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981119] Re: The Desktop gets stuck when selecting Utilities

2022-07-09 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => ubuntu-meta (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1981119

Title:
  The Desktop gets stuck when selecting Utilities

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Click "Show Applications" on the bottom left.
  2. Click "All" at the bottom.
  3. Click Utilities.
  4. Click the Desktop to close Utilities.
  5. The system gets stuck. This might happen on the second or third try of 
step 3.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189
  Uname: Linux 5.4.0-121-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  9 13:05:32 2022
  InstallationDate: Installed on 2019-04-03 (1192 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-08-12 (695 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1981119/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1979144] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-06-19 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1979144

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  initramfs-tools failed up upgrade through the Ubuntu software updater
  Ubuntu 22.04 LTS - jammy

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   nautilus:amd64: Install
   nautilus-data:amd64: Install
   libnautilus-extension1a:amd64: Install
   intel-microcode:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Jun 19 09:57:14 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-06-11 (8 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1979144/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1940097] Re: A forgotten "space"

2022-06-18 Thread Ubuntu Foundations Team Bug Bot
The attachment "1-2.3.0ubuntu3.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1940097

Title:
  A forgotten "space"

Status in python-apt package in Ubuntu:
  In Progress

Bug description:
  Hi
  A "space" character has been forgotten in the "apt/package.py" file and line 
"592".
  I found this error while translating.
  
https://translations.launchpad.net/ubuntu/impish/+source/python-apt/+pots/python-apt/fa/36/+translate

  if not dsc:
  return _("Missing description for '%s'." <===
  "Please report.") % (self.package.name)

  This line should be like this

  if not dsc:
  return _("Missing description for '%s'. " <===
  "Please report.") % (self.package.name)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1940097/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1979096] Re: X.org or Gnome-shell

2022-06-17 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1979096

Title:
  X.org or Gnome-shell

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem happens, when I enable the dock to hide automatically.
  With this enabled, it is not possible to run the programs through the
  search. But when disabled, it is possible to search and run the
  programs. Here's the video of the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 17 18:21:45 2022
  DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed
   v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388]
  InstallationDate: Installed on 2021-04-15 (428 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago)
  dmi.bios.date: 03/04/2017
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX/BR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1979096/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1979066] Re: BUG: kernel NULL pointer dereference, address: 0000000000000300

2022-06-17 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1979066

Title:
  BUG: kernel NULL pointer dereference, address: 0300

Status in xorg package in Ubuntu:
  New

Bug description:
  Recently I experienced the issue that after dis- and reconnecting my monitor 
(Philips 346B1C) with USB-Hub, my laptop (Lenovo E480) did not accept any 
inputs (mouse or keyboard, neither), while the display looked OK.
  I was able to access the laptop using SSH and found following backtrace in 
dmesg:

  
  [18890.250253] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [18890.250286] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [18890.250293] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [18890.250300] pcieport :00:1d.2:[ 0] RxErr
  [18923.193928] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [18923.193941] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [18923.193944] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [18923.193948] pcieport :00:1d.2:[ 0] RxErr
  [18929.192524] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [18929.192547] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [18929.192554] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [18929.192561] pcieport :00:1d.2:[ 0] RxErr
  [18941.195429] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [18941.195440] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [18941.195446] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [18941.195450] pcieport :00:1d.2:[ 0] RxErr
  [18965.194123] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [18965.194132] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [18965.194134] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [18965.194136] pcieport :00:1d.2:[ 0] RxErr
  [18983.192431] pcieport :00:1d.2: AER: Multiple Corrected error received: 
:00:1d.2
  [18983.192471] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Transmitter ID)
  [18983.192478] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=1001/2000
  [18983.192487] pcieport :00:1d.2:[ 0] RxErr
  [18983.192494] pcieport :00:1d.2:[12] Timeout
  [18989.194543] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [18989.194574] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [18989.194581] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [18989.194588] pcieport :00:1d.2:[ 0] RxErr
  [19001.195887] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [19001.195914] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [19001.195919] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [19001.195926] pcieport :00:1d.2:[ 0] RxErr
  [19005.947848] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [19005.947872] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [19005.947878] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [19005.947886] pcieport :00:1d.2:[ 0] RxErr
  [19007.194477] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
  [19007.194505] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
  [19007.194509] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
  [19007.194514] pcieport :00:1d.2:[ 0] RxErr
  [19024.985336] usb 1-2: USB disconnect, device number 38
  [19024.985359] usb 1-2.1: USB disconnect, device number 39
  [19024.985370] usb 1-2.1.1: USB disconnect, device number 40
  [19025.030357] r8152 2-2.2:1.0 enx186571e521da: Stop submitting intr, status 
-71
  [19025.049481] usb 1-2.1.2: USB disconnect, device number 41
  [19025.151593] usb 1-2.1.4: USB disconnect, device number 42
  [19025.276446] usb 2-2.1: Port disable: can't disable remote wake
  [19025.555856] r8152 2-2.2:1.0 enx186571e521da: Tx status -71
  [19025.735918] usb 1-2: new high-speed USB device number 43 using xhci_hcd
  [19025.770499] usb 2-2: USB disconnect, device number 5
  [19025.770513] usb 2-2.1: USB disconnect, device number 6
  [19025.771766] usb 2-2.2: USB disconnect, device 

[Touch-packages] [Bug 1979053] Re: UI glitches in GTK application with AMDGPU

2022-06-17 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => cairo (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1979053

Title:
  UI glitches in GTK application with AMDGPU

Status in cairo package in Ubuntu:
  New

Bug description:
  After updating to (K)ubuntu 22.04, I see user interface glitches in
  GTK application.

  Most obviously affected is Gimp, but Evolution and Eclipse IDE are
  affected, too.

  The glitches don't appear on a notebook with Intel graphics, so maybe
  the problem is caused by a weird interaction between the AMDGPU X.Org
  driver (I use a Radeon RX5600XT) and GTK.

  But as the KDE desktop itself isn't affected and only GTK application
  show these glitches, I think it's not a general problem with AMDGPU.

  I also booted both Kubunutu and Ubuntu live images and installed Gimp:
  The effect show up there, too. So it's than a problem of my actual
  installation.

  I will upload some Gimp screenshots, so you can see what I mean...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libcairo2 1.16.0-5ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jun 17 12:36:26 2022
  InstallationDate: Installed on 2022-04-27 (50 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: cairo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1979053/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1978942] Re: Sound problem. The sound is a few minutes away. A buzzer signal then appears. The image is also bad.

2022-06-16 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => gst-plugins-good1.0 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-good1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1978942

Title:
  Sound problem. The sound is a few minutes away. A buzzer signal then
  appears. The image is also bad.

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  Sound problem. The sound is a few minutes away. A buzzer signal then
  appears. The image is also bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gstreamer1.0-plugins-good 1.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.21.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 16 15:17:35 2022
  InstallationDate: Installed on 2022-05-19 (27 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: Upgraded to kinetic on 2022-06-13 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1978942/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1978349] Re: Monitors sometimes permanently blanked after resume

2022-06-10 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1978349

Title:
  Monitors sometimes permanently blanked after resume

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes monitors don't wake up after resume. Happened couple times with 
Ubuntu 22.04 so far.
  Journalctl lists only one instance of this, might have failed to save the 
logs on other times.

  kernel BUG at
  drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039!

  1. (assumedly) occurs when resuming from ram
  2. suspend chosen from ui
  3. resume by clicking key on keyboard
  4.-11. not tested yet with mainline builds, since uncertain about how to 
reproduce reliably.
  12. openssh-server only installed after today's instance, so don't have much 
debug data beyond what was saved in logs before sysrq-sub.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 10 23:02:04 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2022-04-27 (44 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iheino 4966 F pulseaudio
   /dev/snd/controlC1:  iheino 4966 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-27 (44 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/16/2012
  

[Touch-packages] [Bug 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing

2022-06-08 Thread Ubuntu Foundations Team Bug Bot
The attachment "0001-Remove-pipewire-media-session.service-when-the-
packa.patch" seems to be a debdiff.  The ubuntu-sponsors team has been
subscribed to the bug report so that they can review and hopefully
sponsor the debdiff.  If the attachment isn't a patch, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1977564

Title:
  wireplumber conflicts with pipewire-media-session & needs fixing

Status in pipewire-media-session package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged
Status in wireplumber package in Ubuntu:
  Triaged
Status in pipewire-media-session package in Debian:
  Confirmed

Bug description:
  This issue was reported on IRC and we should probably fix it before
  installing wireplumber by default so I'm setting the block-proposed
  tag.

  https://i.imgur.com/L5VFZO8.png

  wireplumber is apparently too forceful in how it enables PipeWire.
  Both Arch Linux and Debian had to

  https://archlinux.org/news/undone-replacement-of-pipewire-media-
  session-with-wireplumber/

  Is it necessary for wireplumber to conflict with pipewire-media-
  session?

  Should we add Replaces?

  What files does pipewire-media-session need to clean up when it is
  removed?

  See https://salsa.debian.org/gnome-team/gnome-remote-
  desktop/-/commit/52799cfd for an example of how files that aren't
  technically conffiles can be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1977748] Re: apport-bug thinks it's running on Xorg

2022-06-06 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1977748

Title:
  apport-bug thinks it's running on Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Instructed by "ask a question" I tried to file a wayland-targeted bug,
  but apport-bug thinks I'm running Xorg.  See
  https://answers.launchpad.net/ubuntu/+question/702075

  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy

  $ ps -ef | grep Xwayland
  xx  24931685  0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 
-rootless -noreset -accessx -core -auth 
/run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 
-initfd 7

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  Uname: Linux 5.15.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/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: Mon Jun  6 06:40:48 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991]
  InstallationDate: Installed on 2021-10-02 (246 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic 
root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2022
  dmi.bios.release: 3.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.6.0
  dmi.board.name: 0MK6WC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1977748/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1977676] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-06-05 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1977676

Title:
  package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering:
   kmod:amd64: Install
   libkmod2:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jun  5 08:55:45 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-12-24 (527 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977676/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1977649] Re: my system is not showing me 1080p resolution

2022-06-04 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1977649

Title:
  my system is not showing me 1080p resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  After ubuntu 20 install I am not able to increase my screen
  resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  4 19:16:39 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor 
Family Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2022-06-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Gigabyte Technology Co., Ltd. H81M-S1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-44-generic 
root=UUID=fc58eb01-ce48-4d0e-ac05-443d37948ed0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-S1
  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.:bvrFC:bd01/17/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S1:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-S1
  dmi.product.sku: 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 N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1977649/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1977645] Re: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail

2022-06-04 Thread Ubuntu Foundations Team Bug Bot
The attachment "0001-avoid-identifying-as-beta-FIXED.patch" seems to be
a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1977645

Title:
  python3-gpg "1.16.0-unknown" version is incomparable -> dependencies
  always fail

Status in gpgme1.0 package in Ubuntu:
  New

Bug description:
  The python version of the gpgme version contains "unknown" and is
  therefore not PEP440 order compatible.

  See this example:

# pip3 freeze | grep gpg
gpg===1.16.0-unknown

# pip3 install pstore
...
Successfully installed gpg-1.10.0
Successfully installed pstore-2.0.0

# pip3 freeze | grep gpg
gpg==1.10.0

  
  Key takeways from that example:

  - pstore depends on gpg>=1.10

  - 1.16 SHOULD be higher than 1.10

  - pip installs 1.10 even though 1.16 exists

  - the triple-= (gpg===1.16.0-unknown) means that the version exists,
  but cannot be version compared:
  https://peps.python.org/pep-0440/#arbitrary-equality


  Suggested fix:

  - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with
  a '+'; that will compare as expected;

  - fix so "-unknown" isn't appended.

  
  Apparently, this is caused by insufficient fixes in 
0001-avoid-identifying-as-beta.patch

  I've attached a FIXED version, which should fix things.

  Before:

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown.

  After:

$ quilt push 
Applying patch 0001-avoid-identifying-as-beta-FIXED.patch

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0.

  
  Versions:

  $ lsb_release -a 2>/dev/null| grep Codename
  Codename: jammy

  $ apt-cache policy python3-gpg  | grep Installed
Installed: 1.16.0-1.2ubuntu4

  
  Cheers,
  Walter Doekes
  OSSO B.V.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1976607] Re: tests-in-lxd autopkgtest is skipped, due to missing 'lxd' deb

2022-06-02 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1976607

Title:
  tests-in-lxd autopkgtest is skipped, due to missing 'lxd' deb

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Triaged

Bug description:
  
  [Impact] 

   * The deb to snap transitional 'lxd' package was removed post feature-freeze 
in Jammy
   * this leads to systemd's 'tests-in-lxd' autopkgtest being skipped:
   * "tests-in-lxd SKIP installation fails and skip-not-installable set"
   * It reduces systemd's test coverage, which is bad.

  [Test Plan]

   * run systemd's autopkgtest
   * observe the logs
   * "tests-in-lxd SKIP installation fails and skip-not-installable 
set" should not be there
   * "tests-in-lxd PASS" should be there

  [Where problems could occur]

   * The change only affects systemd's 'test-in-lxd' autopkgtest
   * it does not have any impact outside the test suite

  [Other Info]
   
   * https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1964786

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1976607/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1975675] Re: GUI problem from {Online Accounts} Google Microsoft and {Ubuntu Desktop Guide}

2022-05-25 Thread Ubuntu Foundations Team Bug Bot
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251

** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1975675

Title:
  GUI problem from {Online Accounts} Google Microsoft and {Ubuntu
  Desktop Guide}

Status in Ubuntu:
  New

Bug description:
  raspberry pi 4 (8GB memory, USB SSD boot) ubuntu 64 with 2 monitors

  
  Description:  Ubuntu 22.04 LTS
  Release:  22.04


  Seems like the GUI for {Online Accounts} Google Microsoft and {Ubuntu Desktop 
Guide} can't render themselves correctly. Meanwhile, the Firefox can play 
YouTube on 2 monitors without any problem.
  Please refer to the attached snapshot.

  apt-cache policy 
  Package files:
   100 /var/lib/dpkg/status
   release a=now
   500 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64 
Packages
   release 
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64 
Packages
   release 
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages
   release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=arm64
   origin ports.ubuntu.com
   100 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64 
Packages
   release 
v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 
Packages
   release 
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64 
Packages
   release 
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
   release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages
   release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
   release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages
   release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=arm64
   origin ports.ubuntu.com
   500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
   release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=arm64
   origin ports.ubuntu.com
  Pinned packages:
   librados2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   crimson-osd -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   ec2-instance-connect -> 1.1.14-0ubuntu1.1 with priority 1
   python3-etcd3gw -> 0.2.5-1ubuntu1.22.04.1 with priority 1
   budgie-control-center-data -> 1.0.1-2ubuntu2 with priority 1
   xdg-desktop-portal-tests -> 1.14.3-0ubuntu2.22.04.1 with priority 1
   budgie-desktop -> 10.6.1-1ubuntu1~22.04 with priority 1
   python-etcd3gw-doc -> 0.2.5-1ubuntu1.22.04.1 with priority 1
   ceph-volume -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   evolution-dev -> 3.44.1-0ubuntu1 with priority 1
   libbudgietheme0 -> 10.6.1-1ubuntu1~22.04 with priority 1
   rbd-fuse -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   ceph-mgr-modules-core -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   libgtk-4-common -> 4.6.3+ds1-0ubuntu1 with priority 1
   ceph-grafana-dashboards -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   gir1.2-clutter-gst-3.0 -> 3.0.27-2ubuntu1 with priority 1
   libgail-3-dev -> 3.24.33-1ubuntu2 with priority 1
   libgail-3-doc -> 3.24.33-1ubuntu2 with priority 1
   ceph-resource-agents -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   ceph-base -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   libsqlite3-mod-ceph-dev -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   libjson-c-dev -> 0.15-3~ubuntu1.22.04.1 with priority 1
   libjson-c-doc -> 0.15-3~ubuntu1.22.04.1 with priority 1
   xdg-desktop-portal-dev -> 1.14.3-0ubuntu2.22.04.1 with priority 1
   gstreamer1.0-clutter-3.0 -> 3.0.27-2ubuntu1 with priority 1
   python3-ceph-common -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   librbd1 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   gir1.2-budgie-1.0 -> 10.6.1-1ubuntu1~22.04 with priority 1
   libraven0 -> 10.6.1-1ubuntu1~22.04 with priority 1
   librgw2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
   libusb-1.0-0-dev 

[Touch-packages] [Bug 1974037] Re: openssl: EVP_EC_gen() segfault without init

2022-05-24 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1974037

Title:
  openssl: EVP_EC_gen() segfault without init

Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  Confirmed
Status in openssl source package in Kinetic:
  In Progress
Status in openssl package in Debian:
  Fix Released

Bug description:
  [Impact]

  The fix for
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
  broken some code paths as the new string comparison functions now need
  initialization, triggering segafults.

  The provided debdiff fixes the immediate issue and also settles on a
  new implementation not requiring the initialization in the first
  place.

  [Test Plan]

  Since this is a regression fix, we first need to check that the
  original bug hasn't cropped up again:

  sudo locale-gen tr_TR.UTF-8
  LANG=C curl https://ubuntu.com/ > /dev/null # This work
  LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This should work as 
well

  For the regression itself:

  sudo apt install libssl-dev
  cat < openssl_test.c
  #include 
  int main()
  {
  EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
  }
  EOF
  gcc openssl_test.c -lcrypto -lssl -o openssl_test
  ./openssl_test

  
  [Where problems could occur]

  This new patch set is relatively massive, on top of another massive one.
  Some new regressions could crop up of a similar kind. Furthermore, the
  homegrown string comparison function could be buggy, leading to algorithm 
name mismatches.

  [Other info]

  The patches all come from upstream and have been merged on their 3.0
  maintenance branch.

  [Original report]

  Source: sscg
  Version: 3.0.2-1
  Severity: serious
  Tags: ftbfs

  https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1

  ...
   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal 11 
SIGSEGV
  04:32:21 MALLOC_PERTURB_=87 
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
  ...

  Summary of Failures:

   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal
  11 SIGSEGV

  Ok: 9
  Expected Fail:  0
  Fail:   1
  Unexpected Pass:0
  Skipped:0
  Timeout:0
  dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=4 ninja test returned exit code 1
  make: *** [debian/rules:6: binary-arch] Error 25

  This has also been reported on the openssl-users mailing list:

  https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal

2022-05-24 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1975587

Title:
  systemd: fix test-execute autotest failure with kernel 5.15 in focal

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New

Bug description:
  [Impact]

  test-execute autotest is failing in focal with kernel 5.15. This is
  because the following kernel commit changed the ABI for ioprio:

  e70344c05995 ("block: fix default IO priority handling")

  Previously setting IOPRIO_CLASS_NONE for a process would report
  IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
  IOPRIO_CLASS_BE instead.

  [Test case]

  Run systemd autopkgtest and check for the test-execute result.

  [Fix]

  Change test/test-execute/exec-ioschedulingclass-none.service to
  recognize both "none" and "best-effort" as valid returned strings from
  ionice.

  This change is already available in jammy and above.

  [Regression potential]

  We may see regressions in systemd autopkgtest, we won't introduce any
  potential regressions in systemd itself, because this is only
  affecting the specific unit test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974250] Re: ~/.pam_environment gets created as owned by root

2022-05-24 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1974250

Title:
  ~/.pam_environment gets created as owned by root

Status in accountsservice package in Ubuntu:
  Confirmed
Status in accountsservice source package in Jammy:
  Fix Released
Status in accountsservice source package in Kinetic:
  Confirmed

Bug description:
  Something has happened lately with accountsservice, which makes it act
  as root instead of the current user when creating ~/.pam_environment.
  The very old bug #904395 comes to mind, and this smells a security
  issue.

  The function which is supposed to prevent this behavior is here:

  https://salsa.debian.org/freedesktop-
  team/accountsservice/-/blob/ubuntu/debian/patches/0010-set-
  language.patch#L75

  Haven't investigated further yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1975561] Re: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-05-24 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1975561

Title:
  package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  it automatically cme up

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue May 24 06:39:36 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-05-13 (10 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1975561/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974261] Re: After updating to Ubuntu 22.04 I could not boot.

2022-05-19 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1974261

Title:
  After updating to Ubuntu 22.04 I could not boot.

Status in xorg package in Ubuntu:
  New

Bug description:
  Booting the laptop resulted in the splash screen. Then some text
  flashed very quickly but I couldn't read it. Then, the screen went
  black. The back light was on. I went to the TTY recovery mode and
  tried to fix the issue.

  I tried to fix the issue by deleting my nvidia drivers. 
  `apt remove --purge nvidia-*`
  Still would not boot.

  I ended up fixing the issue by going into recovery mode and changing
  the following line of `/etc/default/grub`:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor
  acpi_osi=linux"

  was changed to

  GRUB_CMDLINE_LINUX_DEFAULT=""

  I forgot to update the grub. After rebooting the issue was fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 19 19:24:34 2022
  DistUpgraded: 2022-05-19 18:29:07,954 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3a5d]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:3a5d]
  InstallationDate: Installed on 2021-10-28 (203 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 82K2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=3b1b44c9-cba0-4972-9d72-b1c58fe2f6f8 ro quiet splash 
acpi_backlight=vendor acpi_osi=linux vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-05-20 (0 days ago)
  XorgLog:
   
  dmi.bios.date: 06/28/2021
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H3CN30WW(V2.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Gaming 3 15ACH6
  dmi.ec.firmware.release: 1.30
  dmi.modalias: 
dmi:bvnLENOVO:bvrH3CN30WW(V2.00):bd06/28/2021:br1.30:efr1.30:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6:
  dmi.product.family: IdeaPad Gaming 3 15ACH6
  dmi.product.name: 82K2
  dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6
  dmi.product.version: IdeaPad Gaming 3 15ACH6
  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
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1974261/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974223] Re: FTBFS since changes in apt for automatic kernel removal

2022-05-19 Thread Ubuntu Foundations Team Bug Bot
The attachment "debdiff for bionic" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1974223

Title:
  FTBFS since changes in apt for automatic kernel removal

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  Since the following changes in apt have landed in focal-updates and
  bionic-updates, unattended-upgrades FTBFS on both series:

* Revert "Protect currently running kernel at run-time"
* Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  
  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974203] Re: NO IRQ HANDLER FOR VECTOR

2022-05-19 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1974203

Title:
  NO IRQ HANDLER FOR VECTOR

Status in xorg package in Ubuntu:
  New

Bug description:
  CANNOT UPDATE

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_84_94_generic_85
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu May 19 16:30:38 2022
  DistUpgraded: 2020-10-06 18:55:54,955 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Kabini [Radeon HD 8210] [17aa:3802]
  InstallationDate: Installed on 2018-11-18 (1277 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20240
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic 
root=UUID=1d6c2f9c-9ac1-47d3-8a0a-480bb5876f61 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-06 (589 days ago)
  dmi.bios.date: 12/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 82CN27WW(V3.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G505
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G505
  dmi.modalias: 
dmi:bvnLENOVO:bvr82CN27WW(V3.00):bd12/04/2013:svnLENOVO:pn20240:pvrLenovoG505:rvnLENOVO:rnLenovoG505:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG505:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20240
  dmi.product.sku: LENOVO_MT_20240
  dmi.product.version: Lenovo G505
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-31T16:07:37.548006
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Nov 18 18:23:05 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1974203/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974029] Re: vram memory leak under Wayland

2022-05-18 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1974029

Title:
  vram memory leak under Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  I use 3 monitors. When I turn two of then off and on, the "memory
  usage" shown by nvidia-smi grows by approximately 400 MB each cycle.
  When used video memory reaches maximum my card has (it ix GTX 970 with
  4GB) the graphical system sort of crashes (desktop is not shown, one
  of the monitor does not show image at all).

  This occurs only under Wayland.

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp 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..0c.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.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 18 14:50:11 2022
  DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit()
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
   nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 
libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on 
iommu=pt
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago)
  dmi.bios.date: 08/10/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5861
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1974029/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1974018] Re: dmesg

2022-05-18 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1974018

Title:
  dmesg

Status in xorg package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  [   29.170087] 

  [   29.170097] UBSAN: invalid-load in 
/build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21
  [   29.170102] load of value 255 is not a valid value for type '_Bool'
  [   29.170105] CPU: 3 PID: 549 Comm: in:imuxsock Tainted: P   OE 
5.15.0-30-generic #31-Ubuntu
  [   29.170110] Hardware name: ASUSTeK COMPUTER INC. X550CL/X550CL, BIOS 
X550CL.204 10/17/2013
  [   29.170113] Call Trace:
  [   29.170116]  
  [   29.170119]  show_stack+0x52/0x58
  [   29.170128]  dump_stack_lvl+0x4a/0x5f
  [   29.170136]  dump_stack+0x10/0x12
  [   29.170140]  ubsan_epilogue+0x9/0x45
  [   29.170144]  __ubsan_handle_load_invalid_value.cold+0x44/0x49
  [   29.170149]  ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211]
  [   29.170251]  ieee80211_tx_status+0x72/0xa0 [mac80211]
  [   29.170320]  ath_txq_unlock_complete+0x12d/0x160 [ath9k]
  [   29.170336]  ath_tx_edma_tasklet+0xef/0x4c0 [ath9k]
  [   29.170349]  ? del_timer_sync+0x6c/0xb0
  [   29.170355]  ath9k_tasklet+0x14e/0x290 [ath9k]
  [   29.170367]  tasklet_action_common.constprop.0+0xc0/0xf0
  [   29.170373]  tasklet_action+0x22/0x30
  [   29.170378]  __do_softirq+0xd9/0x2e3
  [   29.170385]  irq_exit_rcu+0x8c/0xb0
  [   29.170389]  common_interrupt+0x8a/0xa0
  [   29.170396]  
  [   29.170398]  
  [   29.170400]  asm_common_interrupt+0x1e/0x40
  [   29.170404] RIP: 0010:copy_user_generic_unrolled+0x89/0xc0
  [   29.170411] Code: 38 4c 89 47 20 4c 89 4f 28 4c 89 57 30 4c 89 5f 38 48 8d 
76 40 48 8d 7f 40 ff c9 75 b6 89 d1 83 e2 07 c1 e9 03 74 12 4c 8b 06 <4c> 89 07 
48 8d 76 08 48 8d 7f 08 ff c9 75 ee 21 d2 74 10 89 d1 8a
  [   29.170414] RSP: 0018:ae00c0b83c10 EFLAGS: 0202
  [   29.170419] RAX: 7f4885d52298 RBX: ae00c0b83c40 RCX: 
0007
  [   29.170422] RDX:  RSI: 7f4885d52260 RDI: 
ae00c0b83c40
  [   29.170424] RBP: ae00c0b83c30 R08:  R09: 
9a32e177e418
  [   29.170427] R10:  R11:  R12: 
0038
  [   29.170429] R13: ae00c0b83cd8 R14: ae00c0b83ce0 R15: 
0040
  [   29.170434]  ? _copy_from_user+0x2e/0x60
  [   29.170440]  __copy_msghdr_from_user+0x3d/0x130
  [   29.170446]  ___sys_recvmsg+0x68/0x110
  [   29.170450]  ? check_preempt_curr+0x5d/0x70
  [   29.170455]  ? ttwu_do_wakeup+0x1c/0x160
  [   29.170460]  ? rseq_get_rseq_cs.isra.0+0x1b/0x220
  [   29.170466]  ? ttwu_do_activate+0x72/0xf0
  [   29.170470]  ? __fget_files+0x86/0xc0
  [   29.170476]  ? __fget_light+0x32/0x80
  [   29.170481]  __sys_recvmsg+0x5f/0xb0
  [   29.170485]  ? switch_fpu_return+0x4e/0xc0
  [   29.170491]  ? exit_to_user_mode_prepare+0x92/0xb0
  [   29.170496]  ? syscall_exit_to_user_mode+0x27/0x50
  [   29.170501]  __x64_sys_recvmsg+0x1d/0x20
  [   29.170505]  do_syscall_64+0x5c/0xc0
  [   29.170510]  ? __x64_sys_futex+0x78/0x1e0
  [   29.170515]  ? exit_to_user_mode_prepare+0x37/0xb0
  [   29.170520]  ? syscall_exit_to_user_mode+0x27/0x50
  [   29.170524]  ? do_syscall_64+0x69/0xc0
  [   29.170528]  ? do_syscall_64+0x69/0xc0
  [   29.170533]  ? do_syscall_64+0x69/0xc0
  [   29.170537]  ? do_syscall_64+0x69/0xc0
  [   29.170541]  ? asm_common_interrupt+0x8/0x40
  [   29.170546]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   29.170550] RIP: 0033:0x7f48864179ef
  [   29.170554] Code: 44 00 00 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 97 90 f6 
ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2f 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 31 4c 63 e0 44 89 c7 e8 de 90 f6 ff 48 83 c4
  [   29.170557] RSP: 002b:7f4885d52140 EFLAGS: 0293 ORIG_RAX: 
002f
  [   29.170561] RAX: ffda RBX:  RCX: 
7f48864179ef
  [   29.170564] RDX: 0040 RSI: 7f4885d52260 RDI: 
0003
  [   29.170566] RBP:  R08:  R09: 
7f4878000bb0
  [   29.170568] R10: 7f4878002b50 R11: 0293 R12: 
55d6ce037580
  [   29.170570] R13: 55d6cc64e4cc R14: 1fa0 R15: 
7f4878000bb0
  [   29.170575]  
  [   29.170585] 


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Wed May 18 13:36:06 2022
  DistUpgraded: 2022-05-16 13:44:28,450 DEBUG 

[Touch-packages] [Bug 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks

2022-05-16 Thread Ubuntu Foundations Team Bug Bot
The attachment "8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

-- 
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/1973642

Title:
  [REGRESSION] Unable to connect to EAP-TLS networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 22.04, currently with network-manager
  1.36.4-2ubuntu1

  Attempting to connect to an EAP-TLS network fails with:

  NetworkManager[703]:   [1652732829.9142] device (wlp0s12f0): 
Activation: (wifi) connection 'AP' has security, and secrets exist.  No new 
secrets needed.
  NetworkManager[703]:   [1652732829.9143] Config: added 'ssid' value 'AP'
  NetworkManager[703]:   [1652732829.9143] Config: added 'scan_ssid' 
value '1'
  NetworkManager[703]:   [1652732829.9144] Config: added 'bgscan' value 
'simple:30:-65:300'
  NetworkManager[703]:   [1652732829.9144] Config: added 'key_mgmt' value 
'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
  NetworkManager[703]:   [1652732829.9144] Config: added 'eap' value 'TLS'
  NetworkManager[703]:   [1652732829.9144] Config: added 'fragment_size' 
value '1266'
  NetworkManager[703]:   [1652732829.9144] Config: added 'ca_cert' value 
''
  NetworkManager[703]:   [1652732829.9144] Config: added 
'domain_suffix_match' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'private_key' 
value '.key'
  NetworkManager[703]:   [1652732829.9145] Config: added 
'private_key_passwd' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'client_cert' 
value '.crt'
  NetworkManager[703]:   [1652732829.9145] Config: added 'identity' value 
''
  NetworkManager[703]:   [1652732829.9146] Config: added 
'proactive_key_caching' value '1'
  NetworkManager[703]:   [1652732829.9178] 
sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to 
add network: invalid message format
  NetworkManager[703]:   [1652732829.9179] device (wlp0s12f0): state 
change: config -> failed (reason 'supplicant-failed', sys-iface-state: 
'managed')

  
  Caused by NM providing an empty domain_suffix_match option

  Upstream commit fixing this (also attached): 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec
  Upstream bug report: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973642/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

2022-05-16 Thread Ubuntu Foundations Team Bug Bot
The attachment "debdiff_oldubuntu_newubuntu.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1973607

Title:
  Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

Status in logrotate package in Ubuntu:
  New

Bug description:
  Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1973475] Re: package klibc-utils 2.0.7-1ubuntu5.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2022-05-15 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => klibc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1973475

Title:
  package klibc-utils 2.0.7-1ubuntu5.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in klibc package in Ubuntu:
  New

Bug description:
  Unpacking libklibc:amd64 (2.0.7-1ubuntu5.1) over (2.0.7-1ubuntu5) ...
  Setting up libklibc:amd64 (2.0.7-1ubuntu5.1) ...
  dpkg: error processing package klibc-utils (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  Errors were encountered while processing:
   klibc-utils
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: klibc-utils 2.0.7-1ubuntu5.1
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   libklibc:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 15 16:31:01 2022
  Dependencies: libklibc 2.0.7-1ubuntu5.1
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2022-04-20 (24 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: klibc
  Title: package klibc-utils 2.0.7-1ubuntu5.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1973475/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1972749] Re: Multiple Xsessions doesn't work

2022-05-09 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1972749

Title:
  Multiple Xsessions doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  On my system with Nvidia 510 drivers I found that if I'm logged in and
  lock the session another user can't login.   I reset the 2nd user's
  account to verify that if I login and lock my session they can't
  login.

  I found this in permission error in the logs.

  May 09 21:58:20 x1 gnome-shell[17718]: Failed to start X Wayland:
  Wrong ownership for directory "/tmp/.X11-unix"

  I've confirmed that /tmp/.X11-unix is owned by the 1st user, so
  something seems to be causing the system to use the same tmp directory
  for both users.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-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.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 22:14:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
   nvidia/510.60.02, 5.17.6, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] 
[1458:401a]
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vg-root ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H270-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/11/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH270-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  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
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1972749/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1972005] Re: Unable to save or attach email attachments since upgrading to 22.04 from 20.04

2022-05-06 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => ubuntu-meta (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1972005

Title:
  Unable to save or attach email attachments since upgrading to 22.04
  from 20.04

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  This bug reporting process is very cumbersome. I tried using the
  update-bug application but none of the available options were
  relevant. If I selected other, I was forced to select a package. How
  am I supposed to know what package the bug is in? So I just picked one
  so I could get by this nonsensical barrier.

  As for the bug I am trying to report: since upgrading to 22.04 last
  week from 20.04, I have been unable to save attachments to my local
  disk from Gmail in Chrome or Firefox. Everything appears to work
  however the file is never actually saved to the file system.

  Also, when I drag files from the Files app to the browser, either to
  upload to Jira or attach to Gmail, it appears to work but the
  attachment is never actually uploaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-desktop 1.481
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  6 11:26:07 2022
  InstallationDate: Installed on 2021-07-31 (279 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1972005/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   3   4   5   6   7   8   9   10   >