[Touch-packages] [Bug 2002098] [NEW] Seems like my GPU isn't supported

2023-01-06 Thread Walid D
Public bug reported:

(base) walid@len:~$ lspci | grep VGA
:00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01)
(base) walid@len:~$ sudo lshw -C video
[sudo] password for walid: 
  *-display 
   description: VGA compatible controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   logical name: /dev/fb0
   version: 01
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
   configuration: depth=32 driver=i915 latency=0 mode=1920x1080 
resolution=1920,1080 visual=truecolor xres=1920 yres=1080
   resources: iomemory:600-5ff iomemory:400-3ff irq:158 
memory:600200-6002ff memory:40-400fff ioport:3000(size=64) 
memory:c-d memory:401000-4016ff memory:402000-40
(base) walid@len:~$ lspci -nn |egrep "VGA|Display"
:00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9a78] (rev 01)
(base) walid@len:~$ sudo apt-get install xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
xserver-xorg-video-intel is already the newest version 
(2:2.99.917+git20210115-1).
xserver-xorg-video-intel set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
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: Fri Jan  6 11:30:53 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3f89]
MachineType: LENOVO 82FG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=f5b7aa1d-e67f-4b72-8621-88ab6b130991 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2021
dmi.bios.release: 1.59
dmi.bios.vendor: LENOVO
dmi.bios.version: FHCN59WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32866 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 15ITL05
dmi.ec.firmware.release: 1.59
dmi.modalias: 
dmi:bvnLENOVO:bvrFHCN59WW:bd08/26/2021:br1.59:efr1.59:svnLENOVO:pn82FG:pvrIdeaPad515ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad515ITL05:skuLENOVO_MT_82FG_BU_idea_FM_IdeaPad515ITL05:
dmi.product.family: IdeaPad 5 15ITL05
dmi.product.name: 82FG
dmi.product.sku: LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05
dmi.product.version: IdeaPad 5 15ITL05
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.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy 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/2002098

Title:
  Seems like my GPU isn't supported

Status in xorg package in Ubuntu:
  New

Bug description:
  (base) walid@len:~$ lspci | grep VGA
  :00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01)
  (base) walid@len:~$ sudo lshw -C video
  [sudo] password for walid: 
*-display 
 description: VGA compatible controller
 product: Intel Corporation
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 logical name: /dev/fb0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list rom 
fb
 configuration: depth=32 driver=i915 latency=0 mode=1920x1080 
resolution=1920,1080 visual=truecolor xres=1920 yres=1080
 resources: iomemory:600-5ff iomemory:400-3ff irq:158 
memory:600200-6002ff memory:40-400fff ioport:3000(size=64) 
memory:c0

[Touch-packages] [Bug 2002098] Re: Intel PCI ID 8086:9a78 missing in pci.ids

2023-01-06 Thread Daniel van Vugt
It is supported, just the name of the GPU is unknown in 22.04. This has
been fixed already in later Ubuntu versions and should not affect
performance at all.

** Summary changed:

- Seems like my GPU isn't supported
+ Intel PCI ID 8086:9a78 missing in pci.ids

** Package changed: xorg (Ubuntu) => pci.ids (Ubuntu)

** Changed in: pci.ids (Ubuntu)
   Importance: Undecided => Low

** Changed in: pci.ids (Ubuntu)
   Status: New => Fix Released

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

Title:
  Intel PCI ID 8086:9a78 missing in pci.ids

Status in pci.ids package in Ubuntu:
  Fix Released

Bug description:
  (base) walid@len:~$ lspci | grep VGA
  :00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01)
  (base) walid@len:~$ sudo lshw -C video
  [sudo] password for walid: 
*-display 
 description: VGA compatible controller
 product: Intel Corporation
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 logical name: /dev/fb0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list rom 
fb
 configuration: depth=32 driver=i915 latency=0 mode=1920x1080 
resolution=1920,1080 visual=truecolor xres=1920 yres=1080
 resources: iomemory:600-5ff iomemory:400-3ff irq:158 
memory:600200-6002ff memory:40-400fff ioport:3000(size=64) 
memory:c-d memory:401000-4016ff memory:402000-40
  (base) walid@len:~$ lspci -nn |egrep "VGA|Display"
  :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9a78] (rev 01)
  (base) walid@len:~$ sudo apt-get install xserver-xorg-video-intel
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  xserver-xorg-video-intel is already the newest version 
(2:2.99.917+git20210115-1).
  xserver-xorg-video-intel set to manually installed.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  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: Fri Jan  6 11:30:53 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3f89]
  MachineType: LENOVO 82FG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=f5b7aa1d-e67f-4b72-8621-88ab6b130991 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2021
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FHCN59WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32866 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15ITL05
  dmi.ec.firmware.release: 1.59
  dmi.modalias: 
dmi:bvnLENOVO:bvrFHCN59WW:bd08/26/2021:br1.59:efr1.59:svnLENOVO:pn82FG:pvrIdeaPad515ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad515ITL05:skuLENOVO_MT_82FG_BU_idea_FM_IdeaPad515ITL05:
  dmi.product.family: IdeaPad 5 15ITL05
  dmi.product.name: 82FG
  dmi.product.sku: LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05
  dmi.product.version: IdeaPad 5 15ITL05
  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.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  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/pci.ids/+bug/2002098/+subscriptions


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


[Touch-packages] [Bug 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound

2023-01-06 Thread Luis Alberto Pabón
*** This bug is a duplicate of bug 1783689 ***
https://bugs.launchpad.net/bugs/1783689

That does sound like it could be an issue for sure.

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

Title:
  [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers
  but no sound

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Every now and then, after boot, I get no sounds at all coming from the
  speakers. Everything seems normal - the control center reports the
  output as active, and if I play anything with sound I can see the VU
  meter going back and forth. I've attached a screenshot showing as
  much.

  The internal microphone does not pick up any sounds either when this
  happens.

  If I connect my Bose NC700 bluetooth headset, I get sound out of it
  just fine, and the mike on it also works.

  Sometimes the internal sound will start working after a few times of
  switching back and forth internal audio / bluetooth headset.

  Restarting the systemd pipewire and pipewire-pulse user services
  doesn't help. Nor does killing & respawning wireplumber.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire-pulse 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Tue Jan  3 11:25:23 2023
  InstallationDate: Installed on 2023-01-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago)

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


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


[Touch-packages] [Bug 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound

2023-01-06 Thread Luis Alberto Pabón
*** This bug is a duplicate of bug 1783689 ***
https://bugs.launchpad.net/bugs/1783689

Ah my apologies, I didn't realise I had already reported this a few
months back when updating to jammy here
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750

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

Title:
  [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers
  but no sound

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Every now and then, after boot, I get no sounds at all coming from the
  speakers. Everything seems normal - the control center reports the
  output as active, and if I play anything with sound I can see the VU
  meter going back and forth. I've attached a screenshot showing as
  much.

  The internal microphone does not pick up any sounds either when this
  happens.

  If I connect my Bose NC700 bluetooth headset, I get sound out of it
  just fine, and the mike on it also works.

  Sometimes the internal sound will start working after a few times of
  switching back and forth internal audio / bluetooth headset.

  Restarting the systemd pipewire and pipewire-pulse user services
  doesn't help. Nor does killing & respawning wireplumber.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire-pulse 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Tue Jan  3 11:25:23 2023
  InstallationDate: Installed on 2023-01-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago)

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


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


[Touch-packages] [Bug 2002120] [NEW] Apport cli cant open Lubuntu browser

2023-01-06 Thread Jānis Kangarooo
Public bug reported:

Apport cli cant open Lubuntu browser

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
99%

*** To continue, you must visit the following URL:

https://bugs.launchpad.net/ubuntu/+source/calamares/+filebug/1d54234c-8dc5-11ed-99a1-40a8f0305cb4?

You can launch a browser now, or copy this URL into a browser on another
computer.


Choices:
  1: Launch a browser now
  C: Cancel
Please choose (1/C): 1
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: firefox: not found
xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/calamares/+filebug/1d54234c-8dc5-11ed-99a1-40a8f0305cb4?'

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.1
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
CasperMD5CheckResult: pass
CasperVersion: 1.470
CurrentDesktop: LXQt
Date: Fri Jan  6 15:16:16 2023
LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  Apport cli cant open Lubuntu browser

Status in apport package in Ubuntu:
  New

Bug description:
  Apport cli cant open Lubuntu browser

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  99%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/calamares/+filebug/1d54234c-8dc5-11ed-99a1-40a8f0305cb4?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/calamares/+filebug/1d54234c-8dc5-11ed-99a1-40a8f0305cb4?'

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  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
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Fri Jan  6 15:16:16 2023
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2002119] [NEW] Apport works, but ubuntu-bug shows internet error 500

2023-01-06 Thread Jānis Kangarooo
Public bug reported:

Apport works, but ubuntu-bug shows internet error 500

The collected information is being sent to the bug tracking system.
This might take a few minutes.
99%
*** Error: Network problem  
 

 
Cannot connect to crash database, please check your Internet connection.
 

 
HTTP Error 500: Internal Server Error   
 

 
Press any key to continue...

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.1
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
CasperMD5CheckResult: pass
CasperVersion: 1.470
CurrentDesktop: LXQt
Date: Fri Jan  6 15:18:00 2023
LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  Apport works, but ubuntu-bug shows internet error 500

Status in apport package in Ubuntu:
  New

Bug description:
  Apport works, but ubuntu-bug shows internet error 500

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  99%
  *** Error: Network problem
   

   
  Cannot connect to crash database, please check your Internet connection.  
   

   
  HTTP Error 500: Internal Server Error 
   

   
  Press any key to continue...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  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
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Fri Jan  6 15:18:00 2023
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2002119] Re: ubuntu-bug shows internet error 500, but Apport works

2023-01-06 Thread Jānis Kangarooo
** Summary changed:

- Apport works, but ubuntu-bug shows internet error 500
+ ubuntu-bug shows internet error 500, but Apport works

** Description changed:

- Apport works, but ubuntu-bug shows internet error 500
+ ubuntu-bug shows internet error 500, but Apport works
  
  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  99%
- *** Error: Network problem
   
-   
   
- Cannot connect to crash database, please check your Internet connection.  
   
-   
   
- HTTP Error 500: Internal Server Error 
   
-   
   
+ *** Error: Network problem
+ 
+ Cannot connect to crash database, please check your Internet connection.
+ 
+ HTTP Error 500: Internal Server Error
+ 
  Press any key to continue...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  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
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Fri Jan  6 15:18:00 2023
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ubuntu-bug shows internet error 500, but Apport works

Status in apport package in Ubuntu:
  New

Bug description:
  ubuntu-bug shows internet error 500, but Apport works

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  99%
  *** Error: Network problem

  Cannot connect to crash database, please check your Internet
  connection.

  HTTP Error 500: Internal Server Error

  Press any key to continue...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  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
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Fri Jan  6 15:18:00 2023
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2002146] [NEW] Second Display not detected after software update

2023-01-06 Thread Bhavin Patel
Public bug reported:

Update required restart, before restart the display was working as
expected. After restart the system does not even detect the display,
even after unplugging and plugging back the HDMI.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  6 19:39:38 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback/0.12.5, 5.15.0-56-generic, x86_64: installed
 v4l2loopback/0.12.5, 5.15.0-57-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c2) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1]
InstallationDate: Installed on 2022-06-12 (208 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
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-57-generic 
root=UUID=0efa9695-6ef2-4b6e-b3c8-b0702c8a9b8a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/28/2021
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX505DT.316
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX505DT
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: 16.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.316:bd01/28/2021:br5.14:efr16.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: TUF Gaming
dmi.product.name: TUF Gaming FX505DT_FX505DT
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 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  Second Display not detected after software update

Status in xorg package in Ubuntu:
  New

Bug description:
  Update required restart, before restart the display was working as
  expected. After restart the system does not even detect the display,
  even after unplugging and plugging back the HDMI.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  6 19:39:38 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.5, 5.15.0-56-generic, x86_64: installed
   v4l2loopback/0.12.5, 5.15.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c2) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1]
  InstallationDate: Installed on 2022-06-12 (208 days ago)
  InstallationMedia: Ubuntu

[Touch-packages] [Bug 2002120] Re: Apport cli cant open Lubuntu browser

2023-01-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1973470 ***
https://bugs.launchpad.net/bugs/1973470

** This bug has been marked a duplicate of bug 1973470
   Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

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

Title:
  Apport cli cant open Lubuntu browser

Status in apport package in Ubuntu:
  New

Bug description:
  Apport cli cant open Lubuntu browser

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  99%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/calamares/+filebug/1d54234c-8dc5-11ed-99a1-40a8f0305cb4?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/calamares/+filebug/1d54234c-8dc5-11ed-99a1-40a8f0305cb4?'

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  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
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Fri Jan  6 15:16:16 2023
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2002119] Re: ubuntu-bug shows internet error 500, but Apport works

2023-01-06 Thread Benjamin Drung
** Package changed: apport (Ubuntu) => launchpad

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

Title:
  ubuntu-bug shows internet error 500, but Apport works

Status in Launchpad itself:
  New

Bug description:
  ubuntu-bug shows internet error 500, but Apport works

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  99%
  *** Error: Network problem

  Cannot connect to crash database, please check your Internet
  connection.

  HTTP Error 500: Internal Server Error

  Press any key to continue...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  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
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Fri Jan  6 15:18:00 2023
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

2023-01-06 Thread Benjamin Drung
** Tags added: jammy

** Also affects: apport (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: xdg-utils (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Invalid
Status in apport source package in Jammy:
  New
Status in xdg-utils source package in Jammy:
  New

Bug description:
  Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  While reporting Bug #1973469, I discovered that ubuntu-bug was unable
  to open Firefox at the very end of the process. Sadly, I closed the
  terminal window that contained the initial error, but I was able to
  easily reproduce it reporting this bug. The full console output of
  "ubuntu-bug apport" on Lubuntu Kinetic is:

  
  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  94%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

  I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
  just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
  is due to the Snap version of Firefox, but I don't know for sure.
  Since ubuntu-bug is what gave me the error, I'm filing this against
  Apport.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:41:07 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2023-01-06 Thread Aaron Honeycutt
I second backporting this to jammy at least as it is an LTS.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory region starvation in <1G
  addresses:

  Type   StartEnd  # Pages  Attributes
  Available  -00086FFF 0087 000F
  BS_Data00087000-00087FFF 0001 000F
  Available  00088000-0009EFFF 0017 000F
  Reserved   0009F000-0009 0001 000F
  Available  0010-00FF 0F00 000F
  LoaderCode 0100-01021FFF 0022 000F
  Available  01022000-238A7FFF 00022886 000F
  BS_Data238A8000-23927FFF 0080 000F
  Available  23928000-28860FFF 4F39 000F
  BS_Data28861000-2AB09FFF 22A9 000F
  LoaderCode 2AB0A000-2ACF8FFF 01EF 000F
  BS_Data2ACF9000-2B2FAFFF 0602 000F
  Available  2B2FB000-2B611FFF 0317 000F
  BS_Data2B612000-2B630FFF 001F 000F
  Available  2B631000-2B632FFF 0002 000F
  BS_Data2B633000-2B63CFFF 000A 000F
  Available  2B63D000-2B649FFF 000D 000F
  BS_Data2B64A000-2B64EFFF 0005 000F
  Available  2B64F000-2B666FFF 0018 000F
  BS_Data2B667000-2D8D5FFF 226F 000F
  LoaderCode 2D8D6000-2D8E9FFF 0014 000F
  BS_Data2D8EA000-2D925FFF 003C 000F
  LoaderCode 2D926000-2D932FFF 000D 000F
  BS_Data2D933000-2D969FFF 0037 000F
  BS_Code2D96A000-2D973FFF 000A 000F
  BS_Data2D974000-2E377FFF 0A04 000F
  Available  2E378000-2E37AFFF 0003 000F
  ...
  Reserved   3C08B000-4192 58A5 000F
  ACPI_NVS   4193-41B2 0200 000F
  ACPI_Recl  41B3-41BFEFFF 00CF 000F
  BS_Data41BFF000-41BF 0001 000F
  Available  0001-0002AB7F 001AB800 000F
  Reserved   000A-000F 0060 
  Reserved   41C0-43FF 2400 
  Reserved   4400-47FF 4000 

[Touch-packages] [Bug 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

2023-01-06 Thread Jānis Kangarooo
@guiverc i just tried latest iso lubuntu-22.04.1-desktop-amd64.iso and reported 
Bug 2002120 that now is a duplicate of this. So its not fixed.
My bug is about Apport. Is this about ubuntu-bug? So then mine is not 
duplicate, or why its the same package?
Ubuntu-bug doesnt work for me at all because of Bug #2002119

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

Title:
  Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Invalid
Status in apport source package in Jammy:
  New
Status in xdg-utils source package in Jammy:
  New

Bug description:
  Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  While reporting Bug #1973469, I discovered that ubuntu-bug was unable
  to open Firefox at the very end of the process. Sadly, I closed the
  terminal window that contained the initial error, but I was able to
  easily reproduce it reporting this bug. The full console output of
  "ubuntu-bug apport" on Lubuntu Kinetic is:

  
  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  94%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

  I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
  just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
  is due to the Snap version of Firefox, but I don't know for sure.
  Since ubuntu-bug is what gave me the error, I'm filing this against
  Apport.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:41:07 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2023-01-06 Thread iMac
Backporting to LTS is a good idea IMHO.  A few additional use cases to
consider

- Users on the threshold who experience slight initrd image growth due
to any module update

- Users who thought they might be able to continue just using older
images may fail to recognize grub will eventually remove those older
images during regular updates.

- Users that take their laptops on the road, but then plug them into
their dock with larger displays to get the real work done only to have a
boot failure. And yet when they take it into Best Buy it just works
somehow.

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory region starvation in <1G
  addresses:

  Type   StartEnd  # Pages  Attributes
  Available  -00086FFF 0087 000F
  BS_Data00087000-00087FFF 0001 000F
  Available  00088000-0009EFFF 0017 000F
  Reserved   0009F000-0009 0001 000F
  Available  0010-00FF 0F00 000F
  LoaderCode 0100-01021FFF 0022 000F
  Available  01022000-238A7FFF 00022886 000F
  BS_Data238A8000-23927FFF 0080 000F
  Available  23928000-28860FFF 4F39 000F
  BS_Data28861000-2AB09FFF 22A9 000F
  LoaderCode 2AB0A000-2ACF8FFF 01EF 000F
  BS_Data2ACF9000-2B2FAFFF 0602 000F
  Available  2B2FB000-2B611FFF 0317 000F
  BS_Data2B612000-2B630FFF 001F 000F
  Available  2B631000-2B632FFF 0002 000F
  BS_Data2B633000-2B63CFFF 000A 000F
  Available  2B63D000-2B649FFF 000D 000F
  BS_Data2B64A000-2B64EFFF 0005 000F
  Available  2B64F000-2B666FFF 0018 000F
  BS_Data2B667000-2D8D5FFF 226F 000F
  LoaderCode 2D8D6000-2D8E9FFF 0014 000F
  BS_Data2D8EA000-2D925FFF 003C 000F
  LoaderCode 2D926000-2D932FFF 000D 000F
  BS_Data2D933000-2D969FFF 0037 000F
  BS_Code2D96A000-2D973FFF 000A 000F
  BS_Data2D974000-2E377FFF 0A04 000F
  Available  2E378000-2E37AFFF 0003 000F
  ...
  Reserved   3C08B000-4192 58A5 000F
  ACPI_NVS   4193-41B2 00

[Touch-packages] [Bug 2002153] Re: Guitarix not starting, fontconfig errors

2023-01-06 Thread Erich Eickmeyer
Cannot reproduce on Lunar. I'm suspecting this is an issue with
fontconfig as there were some changes between Jammy and Lunar.

** Also affects: guitarix (Ubuntu Lunar)
   Importance: Undecided
   Status: Incomplete

** Also affects: guitarix (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: guitarix (Ubuntu Lunar)
   Status: Incomplete => Invalid

** Also affects: fontconfig (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** No longer affects: guitarix (Ubuntu)

** No longer affects: guitarix (Ubuntu Jammy)

** No longer affects: guitarix (Ubuntu Lunar)

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

Title:
  Guitarix not starting, fontconfig errors

Status in fontconfig package in Ubuntu:
  Invalid
Status in fontconfig source package in Jammy:
  New
Status in fontconfig source package in Lunar:
  Invalid

Bug description:
  There is a problem with starting guitarix cause fontconfig errors for ex:
  Fontconfig error: "/etc/fonts/conf.d/66-lohit-tamil-classical.conf", line 22: 
out of memory
  Fontconfig warning: "/etc/fonts/conf.d/66-lohit-tamil-classical.conf", line 
23: No  nor  elements in 
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-05 (214 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: guitarix 0.42.1+dfsg1-3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Tags: third-party-packages jammy
  Uname: Linux 5.15.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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


[Touch-packages] [Bug 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

2023-01-06 Thread Benjamin Drung
ubuntu-bug is a command from Apport. This bug is fixed in Ubuntu >=
22.10 (kinetic) but not in 22.04 (jammy) – yet.

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

Title:
  Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Invalid
Status in apport source package in Jammy:
  New
Status in xdg-utils source package in Jammy:
  New

Bug description:
  Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  While reporting Bug #1973469, I discovered that ubuntu-bug was unable
  to open Firefox at the very end of the process. Sadly, I closed the
  terminal window that contained the initial error, but I was able to
  easily reproduce it reporting this bug. The full console output of
  "ubuntu-bug apport" on Lubuntu Kinetic is:

  
  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  94%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

  I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
  just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
  is due to the Snap version of Firefox, but I don't know for sure.
  Since ubuntu-bug is what gave me the error, I'm filing this against
  Apport.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:41:07 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1998950] Re: GPU hang on Alder Lake laptop

2023-01-06 Thread brian m. carlson
Since there appears to be upstream patches in kernel 6.0 and Mesa 22.3.1
which fix this, perhaps it would be possible to backport those to the
versions in Ubuntu 22.10?  If not, would it at least be possible to
upload such packages to Lunar so that there's an option which doesn't
involve reinstalling the machine to go back to 22.04?

Right now my machine is freezing multiple times per day and it would be
really valuable to get those backports applied.  I'm pretty sure this
affects all Alder Lake-P GPUs on Kinetic, since the upstream bug report
mentions multiple different hardware variants.

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

Title:
  GPU hang on Alder Lake laptop

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1
  Carbon Gen 10.  When this occurs, part of the image tears away and X
  becomes unusable.  Sometimes the cursor continues to move for a short
  time after the fact.  In order to recover, I must SSH into the machine
  and run `sudo killall -9 Xorg`, which drops me back to the lightdm
  login screen and then things work again.

  I've also seen this on Debian sid on a nearly identical machine, and
  there when upgrading to kernel 6.0 and Mesa 22.3, the problem
  disappears.  However, those are not available in Kinetic.

  I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot
  parameters and this does not affect anything.  The problem has been
  occurring since I installed Ubuntu on this machine when I got it on
  November 17.

  I believe the upstream bug report is this:
  https://gitlab.freedesktop.org/drm/intel/-/issues/6757.

  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: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Tue Dec  6 16:42:04 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7]
  InstallationDate: Installed on 2022-11-17 (18 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 21CBCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash 
i915.enable_dc=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2022
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3AET65W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
  dmi.product.family: ThinkPad X1 Carbon Gen 10
  dmi.product.name: 21CBCTO1WW
  dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
  dmi.product.version: ThinkPad X1 Carbon Gen 10
  dmi.sys.vendor: LENOVO
  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.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-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/linux/+bug/1998950/+subscriptions


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


[Touch-packages] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q

2023-01-06 Thread Andreas Hasenack
Hello errors.ubuntu.com, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-failed-jammy
** Tags added: verification-needed-jammy

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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


[Touch-packages] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q

2023-01-06 Thread Andreas Hasenack
I accepted 22.0.5-0ubuntu0.3 which does NOT fix this bug, so I'm
reopening it.

** Changed in: mesa (Ubuntu Jammy)
   Status: Fix Committed => Confirmed

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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


[Touch-packages] [Bug 1998893] Re: NV reverse prime HDMI has no output

2023-01-06 Thread Andreas Hasenack
Hello Kai-Chuan, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-jammy
** Tags added: verification-needed verification-needed-jammy

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

Title:
  NV reverse prime HDMI has no output

Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The X failed to load glamoregl module on Dell's new platforms, the module is 
needed by NV dGPU.

  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading 
/usr/lib/xorg/modules/libglamoregl.so
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: 
vendor="X.Org Foundation"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 
1.21.1.3, module version = 1.0.1
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org 
ANSI C Emulation, version 0.4
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does 
not support the 0xa78b PCI ID.
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to 
try glamor on llvmpipe
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor 
initialization failed

  [Fix]

  The upstream PR added missing ID for the platforms.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/

  After creating the test build to include the PR above, ODM verified
  passed on those platform.

  [Test case]
  Install fixed package on the systems, check that display works.

  [Where things could go wrong]
  Although one commit drops a couple of pci-id's, they were synced from the 
kernel and such id's should not be in the wild. Other than that these just add 
id's and modify some vendor branding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions


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


[Touch-packages] [Bug 1998893] Re: NV reverse prime HDMI has no output

2023-01-06 Thread Andreas Hasenack
I ran update-maintainer on the mesa source and uploaded again.

Give the removal of PCI IDs, and the vague statement in the "Where
things could go wrong" section of the bug description, I'd like to see a
more clear statement saying that these IDs are already not available in
the jammy kernel, and as such there is an even lesser risk of regression
due to that.

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

Title:
  NV reverse prime HDMI has no output

Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The X failed to load glamoregl module on Dell's new platforms, the module is 
needed by NV dGPU.

  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading 
/usr/lib/xorg/modules/libglamoregl.so
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: 
vendor="X.Org Foundation"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 
1.21.1.3, module version = 1.0.1
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org 
ANSI C Emulation, version 0.4
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does 
not support the 0xa78b PCI ID.
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to 
try glamor on llvmpipe
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor 
initialization failed

  [Fix]

  The upstream PR added missing ID for the platforms.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/

  After creating the test build to include the PR above, ODM verified
  passed on those platform.

  [Test case]
  Install fixed package on the systems, check that display works.

  [Where things could go wrong]
  Although one commit drops a couple of pci-id's, they were synced from the 
kernel and such id's should not be in the wild. Other than that these just add 
id's and modify some vendor branding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions


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


[Touch-packages] [Bug 1997124] Re: Netplan/Systemd/Cloud-init/Dbus Race

2023-01-06 Thread James Falcon
** Changed in: cloud-init
 Assignee: (unassigned) => James Falcon (falcojr)

** Changed in: cloud-init
   Status: Triaged => In Progress

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

Title:
  Netplan/Systemd/Cloud-init/Dbus Race

Status in cloud-init:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Cloud-init is seeing intermittent failures while running `netplan
  apply`, which appears to be caused by a missing resource at the time
  of call.

  The symptom in cloud-init logs looks like:

  Running ['netplan', 'apply'] resulted in stderr output: Failed to
  connect system bus: No such file or directory

  I think that this error[1] is likely caused by cloud-init running
  netplan apply too early in boot process (before dbus is active).

  Today I stumbled upon this error which was hit in MAAS[2]. We have
  also hit it intermittently during tests (we didn't have a reproducer).

  Realizing that this may not be a cloud-init error, but possibly a
  dependency bug between dbus/systemd we decided to file this bug for
  broader visibility to other projects.

  I will follow up this initial report with some comments from our
  discussion earlier.

  [1] https://github.com/canonical/netplan/blob/main/src/dbus.c#L801
  [2] 
https://discourse.maas.io/t/latest-ubuntu-20-04-image-causing-netplan-error/5970

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1997124/+subscriptions


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


[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2023-01-06 Thread Julian Andres Klode
The entire upload will be uploaded to all older releases but we do have
a security upload already in the unapproved queues that should go out
first, but that needs approving those first, them passing the SRU
verification, a resigning against the new signing key the new shim
needs, and finally someone to release them. So that the security update
can be released to security pocket.

This won't be ready before Monday the week after next week at the
earliest (7 day testing period in proposed).

People that can approve are still out and only return next week, so I
don't think that's entirely realistic we get the existing uploads into
proposed on Monday.

If we could get them in by Thursday they could go out Monday the 23rd
and we may be able to then upload this fix and release it on like 31st
or so.

We're strictly limited by the point release - it needs to be ready for
that.

** Changed in: grub2-signed (Ubuntu)
Milestone: None => ubuntu-22.04.2

** Changed in: grub2-unsigned (Ubuntu)
Milestone: None => ubuntu-22.04.2

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory region starvation in <1G
  addresses:

  Type   StartEnd  # Pages  Attributes
  Available  -00086FFF 0087 000F
  BS_Data00087000-00087FFF 0001 000F
  Available  00088000-0009EFFF 0017 000F
  Reserved   0009F000-0009 0001 000F
  Available  0010-00FF 0F00 000F
  LoaderCode 0100-01021FFF 0022 000F
  Available  01022000-238A7FFF 00022886 000F
  BS_Data238A8000-23927FFF 0080 000F
  Available  23928000-28860FFF 4F39 000F
  BS_Data28861000-2AB09FFF 22A9 000F
  LoaderCode 2AB0A000-2ACF8FFF 01EF 000F
  BS_Data2ACF9000-2B2FAFFF 0602 000F
  Available  2B2FB000-2B611FFF 0317 000F
  BS_Data2B612000-2B630FFF 001F 000F
  Available  2B631000-2B632FFF 0002 000F
  BS_Data2B633000-2B63CFFF 000A 000F
  Available  2B63D000-2B649FFF 000D 000F
  BS_Data2B64A000-2B64EFFF 0005 000F
  Available  2B64F000-2B666FFF 0018 000F
  BS_Data2B667000-2D8D5FFF 226F 000F
  LoaderCode 2D8D6000-2D8E9FFF 0014 000F
  BS_Data2D8EA000-2D925FFF 003C 000F
  LoaderCode 2D926000-2D932FFF 000D 0

[Touch-packages] [Bug 2002187] [NEW] package libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1 failed to install/upgrade: package libcryptsetup12:amd64 is already installed and configured

2023-01-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

by wanting to change the language in the parameters it displays these
errors to me.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
AptdaemonVersion: 1.1.1+bzr982-0ubuntu39
Architecture: amd64
CasperMD5CheckResult: pass
CrashReports:
 600:0:124:384169:2023-01-06 22:11:58.452482461 +0100:2023-01-06 
22:11:59.452482461 +0100:/var/crash/systemd.0.crash
 600:0:124:384090:2023-01-06 22:11:58.436482667 +0100:2023-01-06 
22:11:59.436482667 +0100:/var/crash/libcryptsetup12:amd64.0.crash
Date: Fri Jan  6 22:11:59 2023
ErrorMessage: package libcryptsetup12:amd64 is already installed and configured
InstallationDate: Installed on 2023-01-06 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
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: cryptsetup
Title: package libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1 failed to 
install/upgrade: package libcryptsetup12:amd64 is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed amd64 apport-package jammy
-- 
package libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1 failed to install/upgrade: 
package libcryptsetup12:amd64 is already installed and configured
https://bugs.launchpad.net/bugs/2002187
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt in Ubuntu.

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


[Touch-packages] [Bug 2002187] Re: package libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1 failed to install/upgrade: package libcryptsetup12:amd64 is already installed and configured

2023-01-06 Thread Steve Langasek
** Package changed: cryptsetup (Ubuntu) => apt (Ubuntu)

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

Title:
  package libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1 failed to
  install/upgrade: package libcryptsetup12:amd64 is already installed
  and configured

Status in apt package in Ubuntu:
  New

Bug description:
  by wanting to change the language in the parameters it displays these
  errors to me.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu39
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   600:0:124:384169:2023-01-06 22:11:58.452482461 +0100:2023-01-06 
22:11:59.452482461 +0100:/var/crash/systemd.0.crash
   600:0:124:384090:2023-01-06 22:11:58.436482667 +0100:2023-01-06 
22:11:59.436482667 +0100:/var/crash/libcryptsetup12:amd64.0.crash
  Date: Fri Jan  6 22:11:59 2023
  ErrorMessage: package libcryptsetup12:amd64 is already installed and 
configured
  InstallationDate: Installed on 2023-01-06 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  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: cryptsetup
  Title: package libcryptsetup12:amd64 2:2.4.3-1ubuntu1.1 failed to 
install/upgrade: package libcryptsetup12:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 990632] Re: Add IDs for new AMD Evergreen/Fusion SKUs

2023-01-06 Thread Narrow Security
These calm and quite cute little toys are the perfect alternatives as they are 
the fluffiest, the cutest, and simply do not make any noises.
cow squishmallows:https://cowsquishmallow.com/

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

Title:
  Add IDs for new AMD Evergreen/Fusion SKUs

Status in libdrm package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-ati package in Ubuntu:
  Incomplete

Bug description:
  This graphics driver has no compiz or Unity 3d support. I understand
  that this is a new laptop, but please, do include support for this
  graphics card soon.This graphics driver has no compiz or Unity 3d
  support. I understand that this is a new laptop, but please, do
  include support for this graphics card soon, that is, if you can
  cherry-pick a patch to make 3d work on this thing. If not now, please
  try for the next Ubuntu release. Running Precise Pangolin with the
  latest patches.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-video-radeon 1:6.14.99~git20111219.aacbd629-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.315
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  Date: Sat Apr 28 17:09:12 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Device [1002:9649] (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:3566]
  LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3568
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 21.39
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.46:bd02/22/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn3568:rvr21.39:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g7 Notebook PC
  dmi.product.version: 06901320461620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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


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


[Touch-packages] [Bug 1993870] Re: WiFi setting has no visible networks (Intel Wireless-AC 9560)

2023-01-06 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  WiFi setting has no visible networks (Intel Wireless-AC 9560)

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  With ubuntu 22.10, I can not see any AP in WiFi setting. It's ok on
  previous versions. The driver is okay since I can scan with iwlist
  tool. Below are more details.

  $ sudo lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.10
  Release:  22.10
  Codename: kinetic

  $ ifconfig
  enx5e80011fa4e9: flags=4163  mtu 1500
  inet 192.168.42.116  netmask 255.255.255.0  broadcast 192.168.42.255
  inet6 fe80::cd60:eccc:f8d7:21e6  prefixlen 64  scopeid 0x20
  ether 5e:80:01:1f:a4:e9  txqueuelen 1000  (Ethernet)
  RX packets 432320  bytes 621981996 (621.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 186680  bytes 22769110 (22.7 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 11354  bytes 24889535 (24.8 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 11354  bytes 24889535 (24.8 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  wlp0s20f3: flags=4099  mtu 1500
  ether 18:1d:ea:ed:34:16  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  $ sudo iwlist wlp0s20f3 scan
  wlp0s20f3  Scan completed :
    Cell 01 - Address: D0:79:80:DA:4F:F3
  Channel:1
  Frequency:2.412 GHz (Channel 1)
  Quality=29/70  Signal level=-81 dBm
  Encryption key:on
  ESSID:"CMCC-7S6H"
  Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s
  Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
  Mode:Master
  Extra:tsf=00e793b8a899
  Extra: Last beacon: 2164ms ago
  IE: Unknown: 0009434D43432D37533648
  IE: Unknown: 010882848B962430486C
  IE: Unknown: 030101
  IE: Unknown: 23021100
  IE: Unknown: 2A0104
  IE: Unknown: 32040C121860
  IE: IEEE 802.11i/WPA2 Version 1
  Group Cipher : CCMP
  Pairwise Ciphers (1) : CCMP
  Authentication Suites (1) : PSK
  IE: Unknown: 0B0539
  IE: Unknown: 7F0804000840
  IE: Unknown: 
DD7E0050F204104A0001101044000102103B000103104700105D2DBCBB9D644948047E083B1A419A72102100094669626572686F6D65102300094669626572686F6D651024000631323334353610420004313233341054000800060050F20400011011000B4669626572686F6D6541501008000220081049000600372A000120
  IE: Unknown: DD0A001018020C01
  IE: WPA Version 1
  Group Cipher : CCMP
  Pairwise Ciphers (1) : CCMP
  Authentication Suites (1) : PSK
  IE: Unknown: 
DD180050F20201018C0003A227A442435E0062322F00
    Cell 02 - Address: FC:DD:65:2B:6B:52
  

  $ sudo dmesg | grep iwl
  [2.816274] iwlwifi :00:14.3: WRT: Overriding region id 0
  [2.816285] iwlwifi :00:14.3: WRT: Overriding region id 1
  [2.816289] iwlwifi :00:14.3: WRT: Overriding region id 2
  [2.816293] iwlwifi :00:14.3: WRT: Overriding region id 3
  [2.816297] iwlwifi :00:14.3: WRT: Overriding region id 4
  [2.816300] iwlwifi :00:14.3: WRT: Overriding region id 6
  [2.816304] iwlwifi :00:14.3: WRT: Overriding region id 8
  [2.816307] iwlwifi :00:14.3: WRT: Overriding region id 9
  [2.816311] iwlwifi :00:14.3: WRT: Overriding region id 10
  [2.816314] iwlwifi :00:14.3: WRT: Overriding region id 11
  [2.816318] iwlwifi :00:14.3: WRT: Overriding region id 15
  [2.816322] iwlwifi :00:14.3: WRT: Overriding region id 16
  [2.816326] iwlwifi :00:14.3: WRT: Overriding region id 18
  [2.816330] iwlwifi :00:14.3: WRT: Overriding region id 19
  [

[Touch-packages] [Bug 2001568] Re: unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

2023-01-06 Thread Steve Langasek
Have you forwarded this patch to Debian?  Debian doesn't *currently*
have any flavors that are a substring of another, but that is not a
policy in Debian, so the patch is also applicable there.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Fix Committed

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

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  Fix Committed

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

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


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


[Touch-packages] [Bug 1886714] Re: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect

2023-01-06 Thread John Erling Blad
The bug is still present in Ubuntu 22.10 on a Gigabyte Technology Co.,
Ltd. GA-990FXA-UD3, when attached to an HK Onyx Studio 6.

Usually a work around is to restart the Bluetooth stack twice.

My wild guess is that a (ring) buffer in the Bluetooth stack is filled,
and isn't reset because the sound system can't catch up. It then goes on
until it crashes.

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

Title:
  [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on
  reconnect

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP fi