date:20220330

Thanks for the bug report.

You seem to be using graphics packages that are not from Ubuntu, but
from the "oibaf" PPA. That's unsupported and known to cause bugs like
this.

Please remove the PPA from your system and then open new bugs if you
encounter further problems.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  the laptop is slowing down I suspect the graphics

Status in Ubuntu:
  Invalid

Bug description:
  I am sure that the video driver does not work because it is very
  stupid

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-36.41~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 14 01:26:27 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:081b]
  InstallationDate: Installed on 2022-03-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Acer Aspire V5-132P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-36-generic 
root=UUID=3ed9b8cd-2125-43f4-af3a-b14a5314ae6e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 07/19/2013
  dmi.bios.release: 2.4
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.04
  dmi.board.name: Angel_CY
  dmi.board.vendor: Acer
  dmi.board.version: V2.04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.04
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04:bd07/19/2013:br2.4:efr1.5:svnAcer:pnAspireV5-132P:pvrV2.04:rvnAcer:rnAngel_CY:rvrV2.04:cvnAcer:ct9:cvrV2.04:skuAspireV5-132P_081B_2.04:
  dmi.product.family: Aspire V5-132P
  dmi.product.name: Aspire V5-132P
  dmi.product.sku: Aspire V5-132P_081B_2.04
  dmi.product.version: V2.04
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110+git2203100500.7c28f5~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1~git2203130600.177805~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket

2022-03-30 Thread Pengpeng Sun

VMware internal bug for this is 2928681.

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

Title:
  Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to
  adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-
  networkd.socket

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Problem:
  Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to  
adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket

  Analysis
  Compared with Ubuntu 21.04 desktop image, there is a difference in 
/usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to 
Before and Conflicts options.

  Ubuntu 22.04
[Unit]
Description=Network Service Netlink Socket
Documentation=man:systemd-networkd.service(8) man:rtnetlink(7)
ConditionCapability=CAP_NET_ADMIN
DefaultDependencies=no
Before=sockets.target shutdown.target
Conflicts=shutdown.target
  Ubuntu 21.04
[Unit]
Description=Network Service Netlink Socket
Documentation=man:systemd-networkd.service(8) man:rtnetlink(7)
ConditionCapability=CAP_NET_ADMIN
DefaultDependencies=no
Before=sockets.target

  After removed "shutdown.target" from /usr/lib/systemd/system/systemd-
  networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce
  since systemd-networkd.service starts much earlier

  So the root cause of the issue is that adding 'shutdown.target' leads
  systemd-networkd.service starts late which makes customization command
  '/usr/sbin/netplan apply' fail.

  Not sure why adding 'shutdown.target' to file
  /usr/lib/systemd/system/systemd-networkd.socket ?

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


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

[Touch-packages] [Bug 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice

I never narrowed down the test case to reproduce this -- it just
happened once in every few attempts to valgrind gnome-shell.

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

Title:
  Valgrind memory errors in gnome-shell 42 from accountsservice

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511== 
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun

[Touch-packages] [Bug 1965563] Re: gnome-extensions-app fails to start (Protocol error)

So this is GTK only? GTK4 only?

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

Title:
  gnome-extensions-app fails to start (Protocol error)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

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


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

[Touch-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

We should confirm whether gnome-chess has the same stack trace (hence
comment #3). According to comment #4, the original reporter is only
confirmed to have encountered bug 1965897. So the gnome-chess issue
might be off-topic here.

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in Mesa:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio

2022-03-30 Thread Matheus Reich

The issue goes away when speech-dispatcher is uninstalled, meaning that
this package is related to the bug in question, and is resolved once it
is removed.

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

Title:
  [AMD Ellesmere] Crackling sound on Pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  While playing back any sounds, a certain crackling sound (static) will
  play with a fixed delay of the sound being played. The amount and
  volume of the static will depend on the sound/music that is being
  played, and this only starts occurring after a somewhat long time (30
  minutes or more). What is interesting to see is that while playing
  back music from Spotify (Snap) the static will only start after a
  second or so, but when playing YouTube videos on Firefox, it will be
  immediate and output that static while the video is playing.

  I've added two sound recordings, one while playing back a song from
  Spotify and the other while playing a song from YouTube. This issue
  goes away when restarting the PulseAudio service, but it comes back
  after a random amount of time.

  1) Description:   Ubuntu 21.04
  Release:  21.04

  2) pulseaudio:
Installed: 1:14.2-1ubuntu1
Candidate: 1:14.2-1ubuntu1
Version table:
   1:14.2-1ubuntu1.1 1 (phased 10%)
  500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:14.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matheus   18662 F pulseaudio
   /dev/snd/controlC2:  matheus   18662 F pulseaudio
   /dev/snd/controlC0:  matheus   18662 F pulseaudio
   /dev/snd/pcmC0D8p:   matheus   18662 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 16:58:43 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-05-03 (41 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Touch-packages] [Bug 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio

2022-03-30 Thread Matheus Reich

@ppq

I've actually been able to determine what the issue was. The speech-
dispatcher package is the one causing issues. It is possible to
uninstall it from any Ubuntu installation (or Ubuntu-based distros). But
to make sure that indeed this is what is causing the issue in your case,
try to run this command on your Terminal:

speech-dispatcher -K

And check if the crackling noise will go away. If it does, uninstall it
using apt:

sudo apt remove speech-dispatcher (or replace remove with autoremove if
you want to also uninstall any packages related to speech-dispatcher).

It seems that this package will stop behaving correctly after some time
with the system running, and will interfere with everything that
pulseaudio will output.

** Also affects: speech-dispatcher (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [AMD Ellesmere] Crackling sound on Pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  While playing back any sounds, a certain crackling sound (static) will
  play with a fixed delay of the sound being played. The amount and
  volume of the static will depend on the sound/music that is being
  played, and this only starts occurring after a somewhat long time (30
  minutes or more). What is interesting to see is that while playing
  back music from Spotify (Snap) the static will only start after a
  second or so, but when playing YouTube videos on Firefox, it will be
  immediate and output that static while the video is playing.

  I've added two sound recordings, one while playing back a song from
  Spotify and the other while playing a song from YouTube. This issue
  goes away when restarting the PulseAudio service, but it comes back
  after a random amount of time.

  1) Description:   Ubuntu 21.04
  Release:  21.04

  2) pulseaudio:
Installed: 1:14.2-1ubuntu1
Candidate: 1:14.2-1ubuntu1
Version table:
   1:14.2-1ubuntu1.1 1 (phased 10%)
  500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:14.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matheus   18662 F pulseaudio
   /dev/snd/controlC2:  matheus   18662 F pulseaudio
   /dev/snd/controlC0:  matheus   18662 F pulseaudio
   /dev/snd/pcmC0D8p:   matheus   18662 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 16:58:43 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-05-03 (41 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Touch-packages] [Bug 1931902] Re: [AMD Ellesmere] Crackling sound on Pulseaudio

2022-03-30 Thread ppq

I am experiencing this issue in Xubuntu 22.04, pulseaudio 
1:15.99.1+dfsg1-1ubuntu1, with this Hardware: 
GIGABYTE B550I AORUS Pro AX (BIOS F15 with AGESA ComboV2 1.2.0.5); 
Ryzen 7 5700G (Cezanne) with integrated graphics; 
audio output via HDMI (mainboard).

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

Title:
  [AMD Ellesmere] Crackling sound on Pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  While playing back any sounds, a certain crackling sound (static) will
  play with a fixed delay of the sound being played. The amount and
  volume of the static will depend on the sound/music that is being
  played, and this only starts occurring after a somewhat long time (30
  minutes or more). What is interesting to see is that while playing
  back music from Spotify (Snap) the static will only start after a
  second or so, but when playing YouTube videos on Firefox, it will be
  immediate and output that static while the video is playing.

  I've added two sound recordings, one while playing back a song from
  Spotify and the other while playing a song from YouTube. This issue
  goes away when restarting the PulseAudio service, but it comes back
  after a random amount of time.

  1) Description:   Ubuntu 21.04
  Release:  21.04

  2) pulseaudio:
Installed: 1:14.2-1ubuntu1
Candidate: 1:14.2-1ubuntu1
Version table:
   1:14.2-1ubuntu1.1 1 (phased 10%)
  500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:14.2-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matheus   18662 F pulseaudio
   /dev/snd/controlC2:  matheus   18662 F pulseaudio
   /dev/snd/controlC0:  matheus   18662 F pulseaudio
   /dev/snd/pcmC0D8p:   matheus   18662 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 14 16:58:43 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-05-03 (41 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Touch-packages] [Bug 1965563] Re: gnome-extensions-app fails to start (Protocol error)

2022-03-30 Thread Gunnar Hjalmarsson

I see a similar error message when trying to start yelp:

$ yelp
Gdk-Message: 01:23:31.232: Error flushing display: Protocol error
$ gnome-extensions-app
Gdk-Message: 01:23:48.075: Error reading events from display: Protocol error

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

Title:
  gnome-extensions-app fails to start (Protocol error)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

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


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

[Touch-packages] [Bug 1931024] Re: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550]

2022-03-30 Thread Mauricio Salazar

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools

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

Title:
  BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550]

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I've been working with a user for the last 2 days on a failure to even
  start the kernel when installing 20.04 or 21.04 (possibly other
  releases) with a UEFI boot.

  System is Dell XPS 9550 amd64 with Ubuntu Budgie.

  The symptom is that after GRUB successfully loads the kernel into RAM,
  it fails to return from loading the initrd into RAM. This was proved
  by adding guard 'echo' and 'sleep' around each stage n grub.cfg.

  After much investigation since this seemed initially related to a LUKS
  install I noticed the initrd.img files generated with MODULES=most are
  105MB. Most of that is unneeded firmware and other files so I changed
  to MODULES=dep. Resulting initrd.img's are around 55MB.

  System then boots correctly.

  This looks like a possible issue with the UEFI on these XPS models but
  as initrd.img sizes get ridiculously large this is likely to hit more
  systems and users.

  For several years I carry optimisation patches to initramfs-tools that
  don't add most firmwares except those specifically required (certainly
  not adding AMD GPU firmware when system has only Intel or Nvidia GPUs
  - and visa versa)

  My initrd.img's are a hybrid of MODULES=dep and result in less than
  20MB.

  My recommendation is to add optimisations to initramfs-tools or adopt
  MODULES=dep.

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


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

[Touch-packages] [Bug 1966591] Re: ssh-keygen -R changes known_hosts file permissions (mode)

2022-03-30 Thread Sergio Durigan Junior

** Bug watch added: OpenSSH Portable Bugzilla #3146
   https://bugzilla.mindrot.org/show_bug.cgi?id=3146

** Also affects: openssh via
   https://bugzilla.mindrot.org/show_bug.cgi?id=3146
   Importance: Unknown
   Status: Unknown

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

Title:
  ssh-keygen -R changes known_hosts file permissions (mode)

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Confirmed
Status in openssh source package in Focal:
  Confirmed
Status in openssh source package in Impish:
  Fix Released
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  When I use ssh-keygen -R to remove a host from known_hosts it changes
  permissions on the file. This causes problems particularly when used
  on the global known hosts file (/etc/ssh/ssh_known_hosts), because
  then only root can read it. Programs running non-interactively as non-
  root users suddenly fail to SSH and it's not immediately obvious why.

  To reproduce:

  $ ssh-keyscan github.com >test_known_hosts
  $ chmod 741 test_known_hosts
  $ ssh-keygen -R github.com -f test_known_hosts
  $ stat test_known_hosts
  ...
  Access: (0600/-rw---) ...

  Expected behavior: file permissions remain unchanged (mode 0741 in
  this example).

  $ lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04

  $ apt-cache policy openssh-client
  openssh-client:
Installed: 1:7.6p1-4ubuntu0.6

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


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

[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2022-03-30 Thread Nick Rosbrook

These errors appear to be coming from the udev rules in
/lib/udev/rules.d/66-snapd-autoimport.rules. I also see the errors on my
system, but I have not experienced any other problems as a result.

Jimmy or Jiwei, can you please tell us how you came across these logs?
What other problem(s) did you experience that seem to be associated?

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


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

[Touch-packages] [Bug 1966418]

I reported this issue to Mesa also.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Touch-packages] [Bug 1966418]

The first 2 did not work for me but the 3rd did.

iris

$ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
Unsupported modifier, resource creation failed.
XXX: resource creation failed

zink

$ MESA_LOADER_DRIVER_OVERRIDE=zink yelp
MESA-INTEL: warning: Performance support disabled, consider sysctl 
dev.i915.perf_stream_paranoid=0

MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0

EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

i965

$ MESA_LOADER_DRIVER_OVERRIDE=i965 yelp
libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so: 
cannot open shared object file: No such file or directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

WaylandCompositor requires eglBindWaylandDisplayWL, eglUnbindWaylandDisplayWL 
and eglQueryWaylandBuffer.
Nested Wayland compositor could not initialize EGL
libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so: 
cannot open shared object file: No such file or directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Touch-packages] [Bug 1966418]

2022-03-30 Thread Adrian Perez

(In reply to Jeremy Bicha from comment #4)
> The first 2 did not work for me but the 3rd did.
> 
> iris
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
> Unsupported modifier, resource creation failed.
> XXX: resource creation failed
> 
> zink
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=zink yelp
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
> 
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
> 
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

Zink will use internally lower-level parts from the Iris driver to access
the hardware, so at least this indicates that the issue is *below* the
OpenGL/GLES implementation. Could be EGL or hardware access, I suppose.

> i965
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=i965 yelp
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
> 
> WaylandCompositor requires eglBindWaylandDisplayWL,
> eglUnbindWaylandDisplayWL and eglQueryWaylandBuffer.
> Nested Wayland compositor could not initialize EGL
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

When a driver that was set explicitly like this fails to load, Mesa falls
back to using software rendering. This means you ended up here using the
swrast/llvmpipe driver, most likely (you can load “webkit://gpu” in the
Minibrowser or Epiphany to check this). This means that WebKit is most
likely using the GLX/EGL/OpenGL/GLES APIs correctly and the issue lies
somewhere in the Intel driver.

But the version of Mesa I am using here is the same as you and it works.
My suspicion is that one of the following is happening:

 * Patches applied by Debian/Ubuntu on top of Mesa are breaking the Intel
   driver. Here I am using Arch Linux, which does not apply any patches.
 * The Intel driver is being miscompiled somehow by the compiler toolchain
   shipped by Ubuntu. In case it helps, here Arch stable has GCC 11.2.0 as
   the default system compiler, so that's what gets used to build packages.
 * The bug could be related to your particular GPU model (and the
   corresponding code inside Mesa for it).

I hope this helps :)

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)

2022-03-30 Thread Simon Déziel

When rsyncd cannot find the address it was told to bind to, it exits
with rc=10 and systemd doesn't even attempt a restart.

To make it restart on such condition, the systemd unit should have
`Restart=on-failure` added.

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

Title:
  Daemon won't start at boot up   (18LTS fully patched)

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Won't Fix

Bug description:
  By adding the 'address=' option to the /etc/rsyncd.conf file, the
  daemon fails at boot.

  Once the NIC(s) is/are up, it will start fine when executed via
  systemctl start rsync

  
  ● rsync.service - fast remote file copy program daemon
 Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 
52min ago
Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, 
status=10)
   Main PID: 851 (code=exited, status=10)

  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file 
copy program daemon.
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 
starting, listening on port 873
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot 
assign requested address (address-family 2)
  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main 
process exited, code=exited, status=10/n/a
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any 
inbound sockets on port 873
  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with 
result 'exit-code'.
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in 
socket IO (code 10) at socket.c(555) [Receiver=3.1.2]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jun  2 08:48:15 2018
  InstallationDate: Installed on 2018-06-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

2022-03-30 Thread Fabio Augusto Miranda Martins

I've setup a Lab with dnsmasq acting as DHCP Server, which I can use the
dhcp-reply-delay option to introduce a delay between the DHCPDISCOVER
and DHCPOFFER, as in the example below:

Mar 30 18:26:34 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPDISCOVER(ens3) 
52:54:00:d7:10:13 
Mar 30 18:26:34 focal-dhcpsrv dnsmasq-dhcp[2470]: 4195928115 reply delay: 3
Mar 30 18:26:37 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPOFFER(ens3) 
192.168.150.119 52:54:00:d7:10:13 

Just minor note that the delay only happens between DHCPDISCOVER and
DHCPOFFER, but not between DHCPREQUEST and DHCPACK:

Mar 30 18:22:13 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPREQUEST(ens3) 
192.168.150.119 52:54:00:d7:10:13 
Mar 30 18:22:13 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPACK(ens3) 192.168.150.119 
52:54:00:d7:10:13 ubuntu

So, if this is a new interface (new mac) looking for an IP, the delay
will be added, but if this is an interface which was previously
configured and is asking to re-use the same IP (DHCPREQUEST), there
won't be any delays.

I believe this Lab will help reproducing the issue with and without the
proposed patch.

1. In a ideal scenario, where no delays were added (dhcp-reply-delay is
commented out), ipconfig will take approximately to do its job: it sends
a DHCPREQUEST, then DHCPDISCOVER and then another DHCPREQUEST in this
process:

- From the ipconfig perspective:

root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig ens9; date
Wed Mar 30 19:25:44 UTC 2022
IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP
IP-Config: ens9 complete (dhcp from 192.168.150.2):
 address: 192.168.150.105  broadcast: 192.168.150.255  netmask: 255.255.255.0   
 gateway: 192.168.150.1dns0 : 192.168.150.2dns1   : 0.0.0.0 
 domain : sts.lab 
 rootserver: 192.168.150.2 rootpath: 
 filename  : 
Wed Mar 30 19:25:54 UTC 2022

- From the dhcp server perspective:

Mar 30 19:25:45 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:25:45 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e ubuntu
Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPDISCOVER(ens3) 
52:54:00:f3:4e:0e 
Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPOFFER(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e 


2. Adding a 5 seconds delay in dnsmasq (dhcp-reply-delay=5) and without 
enforcing a timeout in ipconfig:

- From ipconfig perspective:

root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig ens9; date
Wed Mar 30 19:34:09 UTC 2022
IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP
IP-Config: ens9 complete (dhcp from 192.168.150.2):
 address: 192.168.150.105  broadcast: 192.168.150.255  netmask: 255.255.255.0   
 gateway: 192.168.150.1dns0 : 192.168.150.2dns1   : 0.0.0.0 
 domain : sts.lab 
 rootserver: 192.168.150.2 rootpath: 
 filename  : 
Wed Mar 30 19:34:27 UTC 2022


- From the dhcpserver perspective:

Mar 30 19:34:10 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:10 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e ubuntu
Mar 30 19:34:19 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 
52:54:00:f3:4e:0e 
Mar 30 19:34:19 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5
Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 
52:54:00:f3:4e:0e 
Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5
Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 
52:54:00:f3:4e:0e 
Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e 
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 
192.168.150.105 52:54:00:f3:4e:0e 
Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 
52:54:00:f3:4e:0e 

It takes 18 seconds for the process to complete, as dnsmasq adds 3x 5
seconds delay in the process


3. Using the -t to specify a 15 seconds timeout (when the actual process takes 
18 seconds):

- From the ipconfig perspective:

root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig -t 15 ens9; date
Wed Mar 30 19:37:11 UTC

[Touch-packages] [Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)

2022-03-30 Thread Andreas Hasenack

This is a class[1] of bugs for which we cannot come up with a general
solution that will safely and sanely apply to all scenarios. For such
cases, local configuration changes should be made to accommodate the
intended behavior in each case.

We believe that, in this particular case, since the configuration was
explicitly changed to use a specific IP, you should continue with the
changes and adjust the systemd unit file for rsync to cope with that. Be
it adjust the target to be network-online, or something else that
explicitly waits for that very interface to come up. systemd offers
mechanisms for such overrides, and it's described in more detail in
comment #2.

Regarding the "systemctl start rsync" exit status, it's the way it work
with Type=simple systemd services. From the systemd.service manpage:

"""
If set to simple (the default if ExecStart= is specified but neither Type= nor 
BusName= are) the service manager will consider the unit started immediately 
after the main service process has been forked off. (...)
Note that this means systemctl start command lines for simple services will 
report success even if the service's binary cannot be invoked successfully
"""

I tried Type=exec, but it still behaved in the same way (as the error
happens after rsync starts up, i.e., the binary was executed).

With Type=forking I got a bit further, but the timeout needs tuning:

root@j1-rsyncd:~# time systemctl start rsync
Job for rsync.service failed because a timeout was exceeded.
See "systemctl status rsync.service" and "journalctl -xeu rsync.service" for 
details.

real1m30.246s


With TimeoutStartSec=5 in the unit file it's better:

root@j1-rsyncd:~# time systemctl start rsync
Job for rsync.service failed because a timeout was exceeded.
See "systemctl status rsync.service" and "journalctl -xeu rsync.service" for 
details.

real0m5.287s


I think the most reliably way would be Type=notify, but that requires rsync 
code changes to support systemd's notify mechanism.

In summary, for the specific case of this bug, we believe that systemd
overrides are the best answer for now. To detect startup errors
immediately, I'm willing to file a separate bug.


1. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=network-online-ordering

** Changed in: rsync (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Daemon won't start at boot up   (18LTS fully patched)

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Won't Fix

Bug description:
  By adding the 'address=' option to the /etc/rsyncd.conf file, the
  daemon fails at boot.

  Once the NIC(s) is/are up, it will start fine when executed via
  systemctl start rsync

  
  ● rsync.service - fast remote file copy program daemon
 Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 
52min ago
Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, 
status=10)
   Main PID: 851 (code=exited, status=10)

  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file 
copy program daemon.
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 
starting, listening on port 873
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot 
assign requested address (address-family 2)
  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main 
process exited, code=exited, status=10/n/a
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any 
inbound sockets on port 873
  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with 
result 'exit-code'.
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in 
socket IO (code 10) at socket.c(555) [Receiver=3.1.2]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jun  2 08:48:15 2018
  InstallationDate: Installed on 2018-06-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows

2022-03-30 Thread Dan Streetman

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/software-properties/+git/software-properties/+merge/417981

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

Title:
  apt-add-repository requires --login for private repos, breaking
  automated workflows

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Jammy:
  New

Bug description:
  On Focal, in an automated environment (such as a launchpad builder), a
  used can do the following workflow:

  curl
  "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
  --output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu focal main"

  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
  Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
  Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 
Packages [3288 B] 
  Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main 
Translation-en [1892 B]  

  However, on Jammy, I get the following:

  
  curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT}; 
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu jammy main"

  Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, 
in lpppa
  self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
592, in __call__
  response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
429, in _request
  raise error
  lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
  Response headers:
  ---
  -content-encoding: gzip
  content-length: 91
  content-type: text/plain;charset=utf-8
  date: Wed, 16 Mar 2022 19:54:16 GMT
  server: gunicorn/19.8.1
  status: 404
  vary: Accept-Encoding
  x-powered-by: Zope (www.zope.org), Python (www.python.org)
  x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
  x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
  ---
  Response body:
  ---
  b"Object: , 
name: '$REPO'"
  ---

  
  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
  self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
  if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, 
in description
  return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, 
in lpppa
  raise ShortcutException(msg)
  softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa 
'$REPO/proposed' not found (use --login if private)

  Impish similarly breaks. Digging through changelogs, I see various
  entries in Impish forward, starting with version 0.99.0 where a
  refactor was done.

  using `--login` is not possible in an automated setup (such as a
  builder) as it starts an OAuth dance, which requires human
  interaction. this will break existing automation utilizing apt-add-
  repository for users when migrating to Jammy

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


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

[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2022-03-30 Thread Sergio Durigan Junior

Thank you for taking the time to file a bug report.

I don't know if I fully understand the issue here.  I installed dropbear
inside a container, started it, and then ran ssh-copy-id on the host in
order to copy my public key to the dropbear server.  It got copied
successfully and I was able to login via SSH without issues later.

Could you please provide reproduction steps here?  Also, from your
description, it doesn't seem like this is an openssh bug.  But first we
need to verify whether this is really an issue or not.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: openssh (Ubuntu)
   Status: New => Incomplete

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

Title:
  ssh-copy-id and Dropbear Server

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  on Dropbear SSH Servers ssh-copy-id installs the key in
  /etc/dropbear/authorized_keys

  only the openwrt dropbear server uses that path
  
https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch

  the upstream dropbear server uses the normal path
  ~/.ssh/authorized_keys

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


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

[Touch-packages] [Bug 1967082] Re: SIGSEGV and out-of-bounds write during processing file via objdump

Thanks for reporting this. I don't see that attached reproducer. Could
you please attach it again?

** Changed in: binutils (Ubuntu)
   Status: New => Incomplete

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

Title:
  SIGSEGV and out-of-bounds write during processing file via objdump

Status in binutils package in Ubuntu:
  Incomplete

Bug description:
  SIGSEGV and out-of-bounds write during processing file via objdump

  # Description
  During processing of the attached elf file via
  ```
  objdump -S testcase
  ```
  an out-of-bounds write is triggered and causes a segmentation fault (SIGSEGV) 
This allows an attacker to perform a denial of service and possibly opens up 
other attack vectors if files from untrusted sources are processed.

  For reproduction of the crash, I attached the following script(s):
    - reproduce-ubuntu.sh : Reproduction on Ubuntu 20.04

  Since I was unable to reproduce the bug upstream, I report it here.

  If you need further assistance, please do not hesitate to ask.

  # Ubuntu version
  # apt show binutils
  Package: binutils
  Version: 2.34-6ubuntu1.3
  Priority: optional
  Build-Essential: yes
  Section: devel
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Matthias Klose 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 110 kB
  Provides: binutils-gold, elf-binutils
  Depends: binutils-common (= 2.34-6ubuntu1.3), libbinutils (= 
2.34-6ubuntu1.3), binutils-x86-64-linux-gnu (= 2.34-6ubuntu1.3)
  Suggests: binutils-doc (>= 2.34-6ubuntu1.3)
  Conflicts: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), binutils-multiarch (<< 
2.27-8), modutils (<< 2.4.19-1)
  Homepage: https://www.gnu.org/software/binutils/
  Task: ubuntustudio-video, ubuntu-mate-core, ubuntu-mate-desktop
  Download-Size: 3380 B
  APT-Manual-Installed: yes
  APT-Sources: http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  Description: GNU assembler, linker and binary utilities

  # Ubuntu valgrind
  ==1== Memcheck, a memory error detector
  ==1== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==1== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
  ==1== Command: objdump -S /testcase
  ==1==
  objdump: warning: /testcase has a corrupt section with a size (3c3b031b01) 
larger than the file size
  objdump: /testcase: warning: loop in section dependencies detected
  objdump: warning: /testcase has a corrupt section with a size (3c3b031b01) 
larger than the file size
  ==1== Invalid write of size 4
  ==1==at 0x4A40248: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A3BD4F: bfd_elf64_object_p (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A1AB01: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x111B3C: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x4B360B2: (below main) (libc-start.c:308)
  ==1==  Address 0x4d469f4 is 1,940 bytes inside a block of size 4,064 free'd
  ==1==at 0x483CA3F: free (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==1==by 0x4ABC85B: objalloc_free_block (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A1AABF: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x111B3C: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x4B360B2: (below main) (libc-start.c:308)
  ==1==  Block was alloc'd at
  ==1==at 0x483B7F3: malloc (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==1==by 0x4ABC65B: _objalloc_alloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A227D4: bfd_alloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A22CED: bfd_zalloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A41DE9: _bfd_elf_new_section_hook (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A2485E: ??? (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A40CEB: _bfd_elf_make_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A401DE: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A3BD4F: bfd_elf64_object_p (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A1AB01: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x116402: ??? (in

[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #6236
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236
   Importance: Unknown
   Status: Unknown

** Changed in: liferea (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Touch-packages] [Bug 1964724] Re: the laptop is slowing down I suspect the graphics

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  the laptop is slowing down I suspect the graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  I am sure that the video driver does not work because it is very
  stupid

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-36.41~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 14 01:26:27 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:081b]
  InstallationDate: Installed on 2022-03-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Acer Aspire V5-132P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-36-generic 
root=UUID=3ed9b8cd-2125-43f4-af3a-b14a5314ae6e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 07/19/2013
  dmi.bios.release: 2.4
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.04
  dmi.board.name: Angel_CY
  dmi.board.vendor: Acer
  dmi.board.version: V2.04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.04
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04:bd07/19/2013:br2.4:efr1.5:svnAcer:pnAspireV5-132P:pvrV2.04:rvnAcer:rnAngel_CY:rvrV2.04:cvnAcer:ct9:cvrV2.04:skuAspireV5-132P_081B_2.04:
  dmi.product.family: Aspire V5-132P
  dmi.product.name: Aspire V5-132P
  dmi.product.sku: Aspire V5-132P_081B_2.04
  dmi.product.version: V2.04
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110+git2203100500.7c28f5~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1~git2203130600.177805~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1965114] Re: computer errs

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  computer errs

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  OS  performs  errors

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar 16 15:41:52 2022
  DistUpgraded: 2022-02-14 15:26:03,689 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad X240 [17aa:2214]
  InstallationDate: Installed on 2021-01-14 (425 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20AMCTO1WW
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic 
root=UUID=fb3eedbf-03ca-48cd-b4f6-ab7e0a3a9af6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2022-02-14 (30 days ago)
  dmi.bios.date: 08/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET76WW (2.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:svnLENOVO:pn20AMCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20AMCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X240
  dmi.product.name: 20AMCTO1WW
  dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Thu Sep 30 14:17:53 2021
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6
  xserver.video_driver: modeset

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


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

[Touch-packages] [Bug 1966324] Re: package python3-problem-report 2.20.11-0ubuntu27.21 failed to install/upgrade: installed python3-problem-report package post-installation script subprocess returned

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package python3-problem-report 2.20.11-0ubuntu27.21 failed to
  install/upgrade: installed python3-problem-report package post-
  installation script subprocess returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  dgdfg

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-problem-report 2.20.11-0ubuntu27.21
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportLog: ERROR: apport (pid 43397) Thu Mar 24 23:44:05 2022: host pid 2669 
crashed in a separate mount namespace, ignoring
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Mar 24 23:42:18 2022
  Dependencies:
   
  ErrorMessage: installed python3-problem-report package post-installation 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-03-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: apport
  Title: package python3-problem-report 2.20.11-0ubuntu27.21 failed to 
install/upgrade: installed python3-problem-report package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483

** Merge proposal linked:
   
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/openssh/+git/openssh/+merge/417971

** Merge proposal linked:
   
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/openssh/+git/openssh/+merge/417972

** Merge proposal linked:
   
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/openssh/+git/openssh/+merge/417973

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

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Triaged
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Impish:
  Triaged
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
  ssh client to crash. This happens due to an integer overflow which was
  fixed upstream with the patch being proposed for this SRU, which caps
  the effective value for that option at INT_MAX/1000.

  While use cases triggering the bug may be uncommon, the patch is
  straightforward and the fix could be staged for the next time an
  upload is needed.

  
  [Test Plan]

  Running

  ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
  int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost

  triggers the error. In this case, the ssh client will crash and

  Aborted

  will be printed to stderr.

  By applying the proposed fix, running the same command should allow
  the ssh connection to proceed to the authentication steps.

  [Where problems could occur]

  Most problems would manifest due to rebuilding the package (e.g.,
  dependency changes). Since this proposal is to stage these SRUs, such
  risk is being deferred to be shared with the next, more critical,
  upload.

  [Other Info]
   
  All the SRUs proposed here should be staged due to the low priority nature of 
the bug.

  [Original bug report]

  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

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


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

[Touch-packages] [Bug 1967165] [NEW] package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-03-30 Thread Brian Hardenstein

Public bug reported:

automated update

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
Uname: Linux 5.4.0-104-generic x86_64
NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal 
falcon_lsm_pinned_13207 falcon_lsm_pinned_13109 nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar 30 06:47:50 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-02-10 (48 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  automated update

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  Uname: Linux 5.4.0-104-generic x86_64
  NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal 
falcon_lsm_pinned_13207 falcon_lsm_pinned_13109 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 30 06:47:50 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-02-10 (48 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

This bug was fixed in the package intel-media-driver-non-free -
22.2.1+ds1-1build1

---
intel-media-driver-non-free (22.2.1+ds1-1build1) jammy; urgency=medium

  * Rebuild with the current libva version (lp: #1966571)

 -- Sebastien Bacher   Wed, 30 Mar 2022 11:16:29
+0200

** Changed in: intel-media-driver-non-free (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in intel-media-driver package in Ubuntu:
  Fix Committed
Status in intel-media-driver-non-free package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage

[Touch-packages] [Bug 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected

2022-03-30 Thread Steve Dodd

The bug has been periodically tripping me up for years, but recently I
discovered that it has basically stopped my elderly uncle from using
Libreoffice (which defaults to GTK file picker on Xubuntu at least) on
bionic. Priority really needs to be higher, at least if the intent is
for Ubuntu to be usable by non-power users. To be honest, I felt
actually embarrassed when I realized that the standard process for
saving a file in a non-default folder ("Save As..", click folder, type
filename) is broken. Particularly as, as mentioned above, the highlight
in the text entry is misleading.

At the risk of sounding like I'm sulking, going to have to seriously
consider moving my - and all my family's - machines to a non-gtk based
desktop environment if upstream's attitude to a significant usability
bug like this is to just ignore it for years. An ubuntu-specific patch
would at least reduce the urgency somewhat! I'd settle for an option
(gtk.ini or whatever) to disable the search functionality if that would
help.

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

Title:
  GTK save-dialogs input-focus moves from filename to file search if a
  folder is selected

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  This bug is also reported on GNOME's GTK GitLab:
  https://gitlab.gnome.org/GNOME/gtk/issues/326

  ## Steps to reproduce
   1. Open any GTK app which uses save dialogs (e.g. gedit)
   2. Press save
   3. A save dialog appears and the filename is highlighted (if typing at this 
point you edit the file name)
   4. Click on a different folder (e.g. Downloads)
   5. The filename is still highlighted, hinting that the focus is still there
   6. Type and find yourself searching for a file in the selected folder 

  -- Current behavior --
  The higlighting (on the file name) hints a focus which is not the actual 
input focus, and the actual input focus (the search bar) is hidden until one 
starts to type, which I think to be confusing and unexpected. Also, clicking 
back on the highlighted filename you lose the highlighting, so you have to 
highlight again some already highlighted text; I think this to be confusing and 
counterintuitive.

  -- Expected outcome --
  Highlighting and focus need to match. If they don't that's a UX bug, and 
there are several options to solve it, some examples:
  - keep highlighting as is and keep focus on the filename, this whould require 
finding a different path for file search (I think this is the most productive 
option, because I assume a user wants to change the folder and eventually 
rename or name the file, which I consider more likely than a user wanting to 
search for a file within a save-file dialog);
  - keep filesearch as is, but show its bar before typing begins, and remove 
any highlighting from filename.

  For reference, Windows 10's native save-file dialogs disables the
  highlighting when clicking on a different folder. Typing does nothing
  at that point.

  Tested on gedit 3.36.1 on Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgtk-3-0 3.24.18-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon May 11 21:53:37 2020
  InstallationDate: Installed on 2020-04-03 (37 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768

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


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

[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2022-03-30 Thread Jeff Lane

** Also affects: snapd
   Importance: Undecided
   Status: New

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


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

[Touch-packages] [Bug 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"

2022-03-30 Thread EdwardO

Thanks for the support.

Indeed pipewire is part of the issue. Although installing kubuntu-
desktop does not force pipewire (according to
https://packages.ubuntu.com/jammy/kubuntu-desktop ), I may have enabled
it wrongly while getting Wayland screensharing to work with the
following:

sudo apt install xdg-desktop-portal-gnome gnome-remote-desktop  #
installs pipewire

systemctl --user enable pipewire-media-session
systemctl --user start pipewire-media-session
systemctl --user restart xdg-desktop-portal-gnome

This must have been what caused audio to break
(aside - I'd be happy to know the supported steps for xdg-portal sharing when 
upgrading to 22.04)

Thanks to your pointer I managed to fix it:
* recover the (wired) audio by installing wireplumber: this fixed half-setup 
pipewire situation.
* fix bluetooth by installing libspa-0.2-bluetooth (and restart bluetooth & 
wireplumber)
(see 
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1826833.html)
So, closing this, and if it is considered an unsupported solution, sorry for 
taking your time!

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

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

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

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

Title:
  Bluetooth fails to connect "br-connection-profile-unavailable"

Status in bluez package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:

  > bluetoothctl scan on
  Discovery started
  ...
  > bluetoothctl connect 94:DB:56:8E:0B:96
  Attempting to connect to 94:DB:56:8E:0B:96
  Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable

  > systemctl status bluetooth
  bluetooth.service - Bluetooth service
   Loaded: loaded
  ...
  mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: 
src/service.c:btd_service_connect() a2dp-sink profile connect failed for 
94:DB:56:8E:0B:96: Protocol not available

  Notes:
  kernel-5.15, bluez-5.64
  Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
  Dell Precision 3560
  Unfortunately I did not test before upgrade to 22.04.
  Tried installing pipewire-pulse, blueman, but this is lower-level.
  There are reports of similar errors popping up in Arch and Manjaro recently:
  https://bbs.archlinux.org/viewtopic.php?id=270465
  https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Mar 25 12:56:34 2022
  InstallationDate: Installed on 2022-03-04 (21 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Precision 3560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES 
nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago)
  dmi.bios.date: 09/13/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.2
  dmi.board.name: 095HH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22:
  dmi.product.family: Precision
  dmi.product.name: Precision 3560
  dmi.product.sku: 0A22
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 44:E5:17:BC:00:DD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:24189 acl:41 sco:0 events:519 errors:0
TX bytes:8252 acl:33 sco:0 commands:239 errors:0
  modified.conffile..etc.cron.daily.apport: [deleted]

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


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

[Touch-packages] [Bug 1967014] Re: Lenovo Ideapad 3 screen brightness F keys not working...

2022-03-30 Thread Brian Murray

** Package changed: ubuntu => systemd (Ubuntu)

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

Title:
  Lenovo Ideapad 3 screen brightness F keys not working...

Status in systemd package in Ubuntu:
  New

Bug description:
  As the title says, the F keys the control screen brightness (F11/F12
  on the Lenovo Ideapad 3 15ITL05 laptop I have) don't work on Ubuntu
  21.10. All other special function keys (volume up/down, lock screen,
  airplane mode, etc...) and the screen brightness slider in the top
  right-hand corner work; it's just the brightness keys that are not
  working.

  I know I can just use the slider, but it's more convenient to use the
  F keys. I hope you are working on this for a future 21.10 update.

  Also, I originally installed 20.04 and upgraded to 21.10, but even on
  20.04, those keys weren't working, either.

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


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

[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2022-03-30 Thread Jeff Lane

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


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

[Touch-packages] [Bug 1967014] [NEW] Lenovo Ideapad 3 screen brightness F keys not working...

You have been subscribed to a public bug:

As the title says, the F keys the control screen brightness (F11/F12 on
the Lenovo Ideapad 3 15ITL05 laptop I have) don't work on Ubuntu 21.10.
All other special function keys (volume up/down, lock screen, airplane
mode, etc...) and the screen brightness slider in the top right-hand
corner work; it's just the brightness keys that are not working.

I know I can just use the slider, but it's more convenient to use the F
keys. I hope you are working on this for a future 21.10 update.

Also, I originally installed 20.04 and upgraded to 21.10, but even on
20.04, those keys weren't working, either.

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


** Tags: bot-comment
-- 
Lenovo Ideapad 3 screen brightness F keys not working...
https://bugs.launchpad.net/bugs/1967014
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-03-30 Thread Alexander Browne

@seb128

Sorry if that sounded browbeating. My response is more like
"unfortunate, but understandable". Someone has to be first, even if
MS/Apple seem OK to leave it working.

Thanks for finding the Fedora info. I had just wondered about other
distros. Looks like the other bug they link to is a dupe of this?
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1961558

Can I suggest this be documented in the release notes, at least the
issue, but maybe even including the workaround? FWIW, I see now the file
suggested in the workaround above (/usr/lib/ssl/openssl.cnf) is a link
to /etc/ssl/openssl.cnf, so I think it shouldn't get overwritten as I
thought it might.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1967155] [NEW] Update gnome-online-accounts to 3.44

Public bug reported:

Minimal tracking bug if needed.

https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/master/NEWS

https://gitlab.gnome.org/GNOME/gnome-online-
accounts/-/compare/3.43.1...master?from_project_id=1666

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: In Progress


** Tags: jammy upgrade-software-version

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

Title:
  Update gnome-online-accounts to 3.44

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  Minimal tracking bug if needed.

  https://gitlab.gnome.org/GNOME/gnome-online-
  accounts/-/blob/master/NEWS

  https://gitlab.gnome.org/GNOME/gnome-online-
  accounts/-/compare/3.43.1...master?from_project_id=1666

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1967155/+subscriptions


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

[Touch-packages] [Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)

** Tags added: network-online-ordering

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

Title:
  Daemon won't start at boot up   (18LTS fully patched)

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Triaged

Bug description:
  By adding the 'address=' option to the /etc/rsyncd.conf file, the
  daemon fails at boot.

  Once the NIC(s) is/are up, it will start fine when executed via
  systemctl start rsync

  
  ● rsync.service - fast remote file copy program daemon
 Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 
52min ago
Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, 
status=10)
   Main PID: 851 (code=exited, status=10)

  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file 
copy program daemon.
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 
starting, listening on port 873
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot 
assign requested address (address-family 2)
  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main 
process exited, code=exited, status=10/n/a
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any 
inbound sockets on port 873
  Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with 
result 'exit-code'.
  Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in 
socket IO (code 10) at socket.c(555) [Receiver=3.1.2]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jun  2 08:48:15 2018
  InstallationDate: Installed on 2018-06-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice

Upstream gave some debugging hints

'So the only unref call has a matching ref call pair.  This means it
shouldn't lead to the object getting freed. But between those two calls
the property notify handlers get run, etc.  It's at least conceivable to
me that one of those handlers is accidentally unrefing the object when
it isn't supposed to.

If that is what's going on, how are we going to find out where the
handler is?  One idea,

You could try putting

g_object_unref (user);

and the top of on_new_user_loaded. This is wrong and adding a bug, but
it may also help valgrind to spot the aforementioned, theorized
preexisting extraneously unref too. This is because it will make the
user object get freed earlier, and valgrind should show where.'


Could you give it a try?

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

Title:
  Valgrind memory errors in gnome-shell 42 from accountsservice

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511== 
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08:

[Touch-packages] [Bug 1967145] Re: Keyboard keys are misfiring

2022-03-30 Thread Zhang

I have found that this is only an issue in Wayland sessions. In the Gdm3
interface, and in other ttys there is no such problem

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

Title:
  Keyboard keys are misfiring

Status in console-setup package in Ubuntu:
  New

Bug description:
  My keyboard is a standard 104 layout, but when I press ~, it will type into ¬.
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: keyboard-configuration 1.205ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 22:42:39 2022
  InstallationDate: Installed on 2022-02-09 (48 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Keyboard:
   BACKSPACE="guess"
   XKBLAYOUT="cn"
   XKBMODEL="pc104"
   XKBVARIANT="altgr-pinyin"
   XKBOPTIONS=""
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483

2022-03-30 Thread Athos Ribeiro

** Description changed:

+ [Impact]
+ 
+ Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
+ ssh client to crash. This happens due to an integer overflow which was
+ fixed upstream with the patch being proposed for this SRU, which caps
+ the effective value for that option at INT_MAX/1000.
+ 
+ While use cases triggering the bug may be uncommon, the patch is
+ straightforward and the fix could be staged for the next time an upload
+ is needed.
+ 
+ 
+ [Test Plan]
+ 
+ Running
+ 
+ ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
+ int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost
+ 
+ triggers the error. In this case, the ssh client will crash and
+ 
+ Aborted
+ 
+ will be printed to stderr.
+ 
+ By applying the proposed fix, running the same command should allow the
+ ssh connection to proceed to the authentication steps.
+ 
+ [Where problems could occur]
+ 
+ Most problems would manifest due to rebuilding the package (e.g.,
+ dependency changes). Since this proposal is to stage these SRUs, such
+ risk is being deferred to be shared with the next, more critical,
+ upload.
+ 
+ [Other Info]
+  
+ All the SRUs proposed here should be staged due to the low priority nature of 
the bug.
+ 
+ [Original bug report]
+ 
  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.
  
  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1
  
  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.
  
  What happened:
  
  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

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

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Triaged
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Impish:
  Triaged
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
  ssh client to crash. This happens due to an integer overflow which was
  fixed upstream with the patch being proposed for this SRU, which caps
  the effective value for that option at INT_MAX/1000.

  While use cases triggering the bug may be uncommon, the patch is
  straightforward and the fix could be staged for the next time an
  upload is needed.

  
  [Test Plan]

  Running

  ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
  int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost

  triggers the error. In this case, the ssh client will crash and

  Aborted

  will be printed to stderr.

  By applying the proposed fix, running the same command should allow
  the ssh connection to proceed to the authentication steps.

  [Where problems could occur]

  Most problems would manifest due to rebuilding the package (e.g.,
  dependency changes). Since this proposal is to stage these SRUs, such
  risk is being deferred to be shared with the next, more critical,
  upload.

  [Other Info]
   
  All the SRUs proposed here should be staged due to the low priority nature of 
the bug.

  [Original bug report]

  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

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


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

[Touch-packages] [Bug 1967145] [NEW] Keyboard keys are misfiring

2022-03-30 Thread Zhang

Public bug reported:

My keyboard is a standard 104 layout, but when I press ~, it will type into ¬.
Wayland

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: keyboard-configuration 1.205ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 22:42:39 2022
InstallationDate: Installed on 2022-02-09 (48 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Keyboard:
 BACKSPACE="guess"
 XKBLAYOUT="cn"
 XKBMODEL="pc104"
 XKBVARIANT="altgr-pinyin"
 XKBOPTIONS=""
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Keyboard keys are misfiring

Status in console-setup package in Ubuntu:
  New

Bug description:
  My keyboard is a standard 104 layout, but when I press ~, it will type into ¬.
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: keyboard-configuration 1.205ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 22:42:39 2022
  InstallationDate: Installed on 2022-02-09 (48 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Keyboard:
   BACKSPACE="guess"
   XKBLAYOUT="cn"
   XKBMODEL="pc104"
   XKBVARIANT="altgr-pinyin"
   XKBOPTIONS=""
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

Thank you for the detailed additional information. I think I understand
the situation properly now, together with the need for the fix.

> That means that if something is currently accepting DHCP offers after
the specified timeout has expired, then that is buggy behaviour.

We sometimes run into the case where we're concerned about users being
regressed by the very fix for the buggy behaviour itself. I think we
need to take a pragmatic view in these cases. But unless there's some
specific scenario we're concerned about, I think it's OK to not worry
about the general case. As you say, if there's a user who is specifying
a 2 second timeout but then relying on a DHCP reply coming after 3
seconds, then we will regress them but I think this is reasonable under
the circumstances. I think it's sufficient to have considered and
documented this case carefully, as you now have done (thanks!)

We also need to be careful to ensure that the code that we ship in the
archive isn't itself already making such an assumption. But I think
you've sufficiently covered that already.

It might be worth verifying that this is exactly the result of the
change being landed here though. During SRU verification, in addition to
the test plan you've already specified, would it be practical and/or
useful to verify that, with a timeout of 2s, a DHCP reply sent after
1.5s works, but a DHCP reply sent after 2.5s does not? This would help
us ensure that we are introducing the exact change we intend to
introduce.

I would also like you to verify your actual failing user story please -
that your boot time does actually speed up with that hardware.

With those two requests added to your Test Plan I am in principle fine
to proceed. I still need to review your patch in detail but I've
unfortunately run out of time for that today. I'd also like Łukasz's ack
please.

If another SRU team member looks again before I do, feel free to take
over and accept without my further input if you feel that's appropriate.

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  Incomplete

Bug description:
  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.

  [Test Plan]
  Any situation where ipconfig encounters an error sending the DHCP packet, it 
will automatically set a delay of 10 seconds, which could be longer than the 
user-specified timeout. It can be reproduced by creating a dummy interface and 
attempting to run ipconfig on it with a timeout value of less than 10:

  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021

  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.

  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).

  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.

  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&

[Touch-packages] [Bug 1967127] Re: [FFe] update libarchive to 3.6.0

** Description changed:

- .
+ I request a Feature Freeze Exception to update libarchive from 3.5.2 to
+ 3.6.0 and build evince with libarchive 3.6.
+
+ This will allow us to drop 2 revert commits we added to evince to build with
the older libarchive.
+ https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b
+
+ Changes
+ ---
+ https://github.com/libarchive/libarchive/releases/tag/v3.6.0
+ https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0
+
+ Other Changes
+ -
+ 1. I am cherry-picking a security fix for CVE-2022-26280
+ 2. debian/rules was only running dh_auto_test if 'check' was set in
DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set. That
way we run the build tests by default.
+
+ I'm forwarding both those changes to Debian soon.
+
+ Build logs
+ --
+
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra
+
+ https://buildd.debian.org/status/package.php?p=evince
+
+ Testing done
+
+ No errors in the install logs
+
+ Evince still works fine to open a variety of PDFs and a .cbz file I have.
+ File Roller still works fine to open a variety of compressed file types.

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

** Description changed:

I request a Feature Freeze Exception to update libarchive from 3.5.2 to
3.6.0 and build evince with libarchive 3.6.

This will allow us to drop 2 revert commits we added to evince to build with
the older libarchive.
https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b

Changes
---
https://github.com/libarchive/libarchive/releases/tag/v3.6.0
https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0

Other Changes
-
- 1. I am cherry-picking a security fix for CVE-2022-26280
- 2. debian/rules was only running dh_auto_test if 'check' was set in
DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set. That
way we run the build tests by default.
+ 1. libarchive: I am cherry-picking a security fix for CVE-2022-26280
+ 2. libarchive: debian/rules was only running dh_auto_test if 'check' was set
in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set.
That way we run the build tests by default.

I'm forwarding both those changes to Debian soon.

Build logs
--

https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra

https://buildd.debian.org/status/package.php?p=evince

Testing done

No errors in the install logs

Evince still works fine to open a variety of PDFs and a .cbz file I have.
File Roller still works fine to open a variety of compressed file types.

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

Title:
[FFe] update libarchive to 3.6.0

Status in evince package in Ubuntu:
New
Status in libarchive package in Ubuntu:
New

Bug description:
I request a Feature Freeze Exception to update libarchive from 3.5.2
to 3.6.0 and build evince with libarchive 3.6.

This will allow us to drop 2 revert commits we added to evince to build with
the older libarchive.
https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b

Changes
---
https://github.com/libarchive/libarchive/releases/tag/v3.6.0
https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0

Other Changes
-
1. libarchive: I am cherry-picking a security fix for CVE-2022-26280
2. libarchive: debian/rules was only running dh_auto_test if 'check' was set
in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set.
That way we run the build tests by default.

I'm forwarding both those changes to Debian soon.

Build logs
--

https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra

https://buildd.debian.org/status/package.php?p=evince

Testing done

No errors in the install logs

Evince still works fine to open a variety of PDFs and a .cbz file I have.
File Roller still works fine to open a variety of compressed file types.

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

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

[Touch-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland

** Tags removed: verification-done-focal verification-needed
** Tags added: verification-failed verification-failed-focal

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Impish:
  Fix Released
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  This bug makes it more difficult for Wayland users to report bugs with
  apport. When a Wayland user tries to use the -w,--window option,
  apport fails silently. We do not want users to face a high barrier to
  submitting bug reports.

  The patch for this bug adds a message explaining that the -w,--window
  option cannot be used on Wayland, and suggests a method for finding
  the window's PID instead.

  [Test Plan]

  * Log on to Ubuntu on Wayland. You can check that 
$XDG_SESSION_TYPE=="wayland" in your current session.
  * Open a terminal, and run `ubuntu-bug -w`.
  * Click on any other window, and observe that the apport UI will not respond.

  [Where problems could occur]

  The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to
  'wayland'. If either of these strings in the patch were wrong, or the
  environment variable was not used in the target release, the condition
  would likely never be true.

  [Original Description]

  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed

  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

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


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

[Touch-packages] [Bug 1966871] Re: Unable to play music in gnome but able to play in "speaker-test" after upgrade

2022-03-30 Thread Xavier Hsinyuan

Fixed after checking pipewire-media-session release note. Thanks for
your reply!

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

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

Title:
  Unable to play music in gnome but able to play in "speaker-test" after
  upgrade

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  ==
  pulseaudio:
Installed：1:15.99.1+dfsg1-1ubuntu1
  pipewire:
Installed：0.3.48-1ubuntu1
  ==

  After upgrade to 22.04 dev branch, it seems that gnome the desktop
  environment and applications can't detect sound output devices. But
  "speaker-test" and "aplay" works fine with root privileges.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 15:01:27 2022
  InstallationDate: Installed on 2021-05-01 (332 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to jammy on 2022-01-23 (64 days ago)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 106.117
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0E07
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0E07:bd09/11/2020:br106.117:efr0.7:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:skuTM1701-16773:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.product.sku: TM1701-16773
  dmi.sys.vendor: Timi

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


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

[Touch-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland

Sorry, the apport 2.20.11-0ubuntu27.22 to Focal is bad. It looks like
symlinks have inadvertently been expanded. So that one needs fixing
please with a replacement upload for Focal. Impish is fine, so I've
released that one.

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Impish:
  Fix Released
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  This bug makes it more difficult for Wayland users to report bugs with
  apport. When a Wayland user tries to use the -w,--window option,
  apport fails silently. We do not want users to face a high barrier to
  submitting bug reports.

  The patch for this bug adds a message explaining that the -w,--window
  option cannot be used on Wayland, and suggests a method for finding
  the window's PID instead.

  [Test Plan]

  * Log on to Ubuntu on Wayland. You can check that 
$XDG_SESSION_TYPE=="wayland" in your current session.
  * Open a terminal, and run `ubuntu-bug -w`.
  * Click on any other window, and observe that the apport UI will not respond.

  [Where problems could occur]

  The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to
  'wayland'. If either of these strings in the patch were wrong, or the
  environment variable was not used in the target release, the condition
  would likely never be true.

  [Original Description]

  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed

  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

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


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

[Touch-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland

This bug was fixed in the package apport - 2.20.11-0ubuntu71.1

---
apport (2.20.11-0ubuntu71.1) impish; urgency=medium

  * apport/ui.py: Error out when -w option is used on wayland (LP:
#1952947).

 -- Nick Rosbrook   Wed, 16 Feb 2022
12:16:27 -0500

** Changed in: apport (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Impish:
  Fix Released
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  This bug makes it more difficult for Wayland users to report bugs with
  apport. When a Wayland user tries to use the -w,--window option,
  apport fails silently. We do not want users to face a high barrier to
  submitting bug reports.

  The patch for this bug adds a message explaining that the -w,--window
  option cannot be used on Wayland, and suggests a method for finding
  the window's PID instead.

  [Test Plan]

  * Log on to Ubuntu on Wayland. You can check that 
$XDG_SESSION_TYPE=="wayland" in your current session.
  * Open a terminal, and run `ubuntu-bug -w`.
  * Click on any other window, and observe that the apport UI will not respond.

  [Where problems could occur]

  The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to
  'wayland'. If either of these strings in the patch were wrong, or the
  environment variable was not used in the target release, the condition
  would likely never be true.

  [Original Description]

  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed

  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

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


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

[Touch-packages] [Bug 1952947] Update Released

The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Impish:
  Fix Released
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  This bug makes it more difficult for Wayland users to report bugs with
  apport. When a Wayland user tries to use the -w,--window option,
  apport fails silently. We do not want users to face a high barrier to
  submitting bug reports.

  The patch for this bug adds a message explaining that the -w,--window
  option cannot be used on Wayland, and suggests a method for finding
  the window's PID instead.

  [Test Plan]

  * Log on to Ubuntu on Wayland. You can check that 
$XDG_SESSION_TYPE=="wayland" in your current session.
  * Open a terminal, and run `ubuntu-bug -w`.
  * Click on any other window, and observe that the apport UI will not respond.

  [Where problems could occur]

  The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to
  'wayland'. If either of these strings in the patch were wrong, or the
  environment variable was not used in the target release, the condition
  would likely never be true.

  [Original Description]

  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed

  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

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


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

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

2022-03-30 Thread jeremyszu

** Tags removed: verification-needed verification-needed-focal 
verification-needed-impish
** Tags added: verification-done verification-done-focal 
verification-done-impish

** Changed in: oem-priority
   Status: Triaged => Fix Committed

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

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


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

[Touch-packages] [Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/update-notifier/+git/update-notifier/+merge/417912

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/417913

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/landscape-client/+git/landscape-client/+merge/417914

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

Title:
  scripts in /etc/update-motd.d/ run even on login via non-interactive
  scp and sftp sessions

Status in landscape-client package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in update-motd package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  In Progress

Bug description:
  My client has 200+ devices automatically uploading information via
  sftp and scp to a server every few minutes. After a recent update, I
  noticed the load on their server spiking through the roof. Upon
  investigation, I discovered a horde of landscape-sysinfo and
  /usr/bin/lsb_release processes running that correlated with login
  session notifications in /var/log/syslog and the load spikes.

  It appears that even in non-interactive sessions where this
  information will never be seen, the configuration options below in
  /etc/pam.d/sshd cause these items to be launched (in fact, probably
  everything in /etc/update-motd.d). This only started on the system in
  question after a recent set of system updates were installed.

  The content of /etc/update-motd.d/* really, really, really shouldn't
  be executed if the session in question is not interactive, as it
  provides no value at all. Unfortunately, to disable it for these non-
  interactive sessions, we also have to disable it for the interactive
  ones as well where it has some value (though not enough to make
  spiking the load on this server through the roof an acceptable
  tradeoff).

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  #sessionoptional pam_motd.so  motd=/run/motd.dynamic
  #sessionoptional pam_motd.so noupdate

  Also, looking at the script 00-header in /etc/update-motd.d/,
  /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release
  does include the necessary information:

  [ -r /etc/lsb-release ] && . /etc/lsb-release

  if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
  # Fall back to using the very slow lsb_release utility
  DISTRIB_DESCRIPTION=$(lsb_release -s -d)
  fi

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"

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


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

[Touch-packages] [Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions

I re-installed the former package content, rebooted the system and gave
it some more memory to get rid of any concerns in that regard (from the
perf data).

The diff of the actual content before/after was all reasonable (new
times, different package counts, but otherwise the same)

Consumption wise we have:

# Before fixes
real1m11.731s
us  sy  id  wa  st
71  20   9   0   0

59.16%  landscape-sysin
14.23%  swapper
 6.16%  sshd   
 5.78%  lsb_release
 3.35%  apt-config 
 0.86%  dbus-daemon
 0.80%  systemd
 0.59%  gdbus  
 0.56%  dpkg   
 0.48%  systemd-logind


# After fixes

real0m21.257s
us  sy  id  wa  st
32  34  34   0   0

42.00%  swapper
22.45%  sshd   
 2.94%  dbus-daemon
 2.79%  systemd
 2.08%  gdbus  
 2.07%  grep   
 1.88%  run-parts  
 1.58%  systemd-logind 
 1.46%  find   
 1.23%  bash   
 1.22%  update-motd-fsc
 1.18%  systemd-journal
 1.13%  cat

That is good.
Ready to open MRs for this.

At a very high summary:
- delay cut down by 2/3 of the initial duration
- consumption reduced by 71% (duration) and by 26% (consumption while running).
  This is multiplicative so for the example we have an saving of ~81.27% of cpu 
cycles

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

Title:
  scripts in /etc/update-motd.d/ run even on login via non-interactive
  scp and sftp sessions

Status in landscape-client package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in update-motd package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  In Progress

Bug description:
  My client has 200+ devices automatically uploading information via
  sftp and scp to a server every few minutes. After a recent update, I
  noticed the load on their server spiking through the roof. Upon
  investigation, I discovered a horde of landscape-sysinfo and
  /usr/bin/lsb_release processes running that correlated with login
  session notifications in /var/log/syslog and the load spikes.

  It appears that even in non-interactive sessions where this
  information will never be seen, the configuration options below in
  /etc/pam.d/sshd cause these items to be launched (in fact, probably
  everything in /etc/update-motd.d). This only started on the system in
  question after a recent set of system updates were installed.

  The content of /etc/update-motd.d/* really, really, really shouldn't
  be executed if the session in question is not interactive, as it
  provides no value at all. Unfortunately, to disable it for these non-
  interactive sessions, we also have to disable it for the interactive
  ones as well where it has some value (though not enough to make
  spiking the load on this server through the roof an acceptable
  tradeoff).

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  #sessionoptional pam_motd.so  motd=/run/motd.dynamic
  #sessionoptional pam_motd.so noupdate

  Also, looking at the script 00-header in /etc/update-motd.d/,
  /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release
  does include the necessary information:

  [ -r /etc/lsb-release ] && . /etc/lsb-release

  if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
  # Fall back to using the very slow lsb_release utility
  DISTRIB_DESCRIPTION=$(lsb_release -s -d)
  fi

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"

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


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

[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

the issue is in the library there is no need to add every client
software

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

** Changed in: evolution (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: epiphany-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Touch-packages] [Bug 1967127] [NEW] [FFe] update libarchive to 3.6.0

Public bug reported:

.

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


** Tags: jammy upgrade-software-version

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

Title:
  [FFe] update libarchive to 3.6.0

Status in libarchive package in Ubuntu:
  New

Bug description:
  .

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


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

[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

2022-03-30 Thread Luis Alberto Pabón

Added `gnome-control-center` to affected - GNOME online accounts
requires a web browsing session to auth into some services.

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  New
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Touch-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-30 Thread Timo Aaltonen

the gnome-chess crash does

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in Mesa:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1967117] [NEW] package linux-image-5.15.0-23-generic 5.15.0-23.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-03-30 Thread Jannick

Public bug reported:

The upgrade from the LTS Version to ubuntu jammy has failed on ubuntu
server

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-23-generic 5.15.0-23.23
ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174
Uname: Linux 5.4.0-107-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 30 13:13 seq
 crw-rw 1 root audio 116, 33 Mar 30 13:13 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
CasperMD5CheckResult: unknown
Date: Wed Mar 30 13:16:30 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: innotek GmbH VirtualBox
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic 
root=UUID=c545d079-6483-492d-a078-e32869326a2a ro console=tty1 console=ttyS0
Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 
3.10.1-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-23-generic 5.15.0-23.23 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check uec-images

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The upgrade from the LTS Version to ubuntu jammy has failed on ubuntu
  server

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174
  Uname: Linux 5.4.0-107-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 30 13:13 seq
   crw-rw 1 root audio 116, 33 Mar 30 13:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: unknown
  Date: Wed Mar 30 13:16:30 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: innotek GmbH VirtualBox
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic 
root=UUID=c545d079-6483-492d-a078-e32869326a2a ro console=tty1 console=ttyS0
  Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 
3.10.1-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-23-generic 5.15.0-23.23 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version:

[Touch-packages] [Bug 1932305] Re: fstrim doesn't trim my /home separate partition

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  fstrim doesn't trim my /home separate partition

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  My system is Kubuntu 20.04

  I have 3 partitions in my nvme:
  NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  nvme0n1 259:00 465,8G  0 disk 
  ├─nvme0n1p1 259:10   251M  0 part /boot/efi
  ├─nvme0n1p2 259:20  53,7G  0 part /
  ├─nvme0n1p4 259:30   7,6G  0 part [SWAP]
  └─nvme0n1p5 259:40   357G  0 part /home


  I have activated fstrim.service and fstrim.timer:
  sudo systemctl list-timers
  ...
  Mon 2021-06-21 00:00:00 CEST 3 days left   Mon 2021-06-14 00:00:03 CEST 3 
days ago   fstrim.timer fstrim.service  


  But home partition is not trimmed:
  ...
  jun 14 00:00:10 moon fstrim[5137]: /: 29,1 GiB (31264600064 bytes) trimmed on 
/dev/nvme0n1p2
  jun 14 00:00:10 moon fstrim[5137]: /boot/efi: 239,1 MiB (250755584 bytes) 
trimmed on /dev/nvme0n1p1
  jun 14 00:00:10 moon systemd[1]: fstrim.service: Succeeded.
  ...


  The fstrim.service is Protected for home:
  sudo systemctl cat fstrim.service 
  # /lib/systemd/system/fstrim.service
  [Unit]
  Description=Discard unused blocks on filesystems from /etc/fstab
  Documentation=man:fstrim(8)
  ConditionVirtualization=!container

  [Service]
  Type=oneshot
  ExecStart=/sbin/fstrim --fstab --verbose --quiet
  ProtectSystem=strict
  ProtectHome=yes
  PrivateDevices=no
  PrivateNetwork=yes
  PrivateUsers=no
  ProtectKernelTunables=yes
  ProtectKernelModules=yes
  ProtectControlGroups=yes
  MemoryDenyWriteExecute=yes
  SystemCallFilter=@default @file-system @basic-io @system-service


  
  I think the problem is:
  
https://github.com/karelzak/util-linux/commit/61b384b36105fe682ddf16b9379f446d935603bc

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


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

[Touch-packages] [Bug 1932305] Re: fstrim doesn't trim my /home separate partition

2022-03-30 Thread Steve Dodd

This is due to "ProtectHome=yes" in the .service file; the workaround is
to add:

[Service]
ProtectHome=no

In e.g. /etc/systemd/system/fstrim.service.d/allow-home.conf

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

Title:
  fstrim doesn't trim my /home separate partition

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  My system is Kubuntu 20.04

  I have 3 partitions in my nvme:
  NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  nvme0n1 259:00 465,8G  0 disk 
  ├─nvme0n1p1 259:10   251M  0 part /boot/efi
  ├─nvme0n1p2 259:20  53,7G  0 part /
  ├─nvme0n1p4 259:30   7,6G  0 part [SWAP]
  └─nvme0n1p5 259:40   357G  0 part /home


  I have activated fstrim.service and fstrim.timer:
  sudo systemctl list-timers
  ...
  Mon 2021-06-21 00:00:00 CEST 3 days left   Mon 2021-06-14 00:00:03 CEST 3 
days ago   fstrim.timer fstrim.service  


  But home partition is not trimmed:
  ...
  jun 14 00:00:10 moon fstrim[5137]: /: 29,1 GiB (31264600064 bytes) trimmed on 
/dev/nvme0n1p2
  jun 14 00:00:10 moon fstrim[5137]: /boot/efi: 239,1 MiB (250755584 bytes) 
trimmed on /dev/nvme0n1p1
  jun 14 00:00:10 moon systemd[1]: fstrim.service: Succeeded.
  ...


  The fstrim.service is Protected for home:
  sudo systemctl cat fstrim.service 
  # /lib/systemd/system/fstrim.service
  [Unit]
  Description=Discard unused blocks on filesystems from /etc/fstab
  Documentation=man:fstrim(8)
  ConditionVirtualization=!container

  [Service]
  Type=oneshot
  ExecStart=/sbin/fstrim --fstab --verbose --quiet
  ProtectSystem=strict
  ProtectHome=yes
  PrivateDevices=no
  PrivateNetwork=yes
  PrivateUsers=no
  ProtectKernelTunables=yes
  ProtectKernelModules=yes
  ProtectControlGroups=yes
  MemoryDenyWriteExecute=yes
  SystemCallFilter=@default @file-system @basic-io @system-service


  
  I think the problem is:
  
https://github.com/karelzak/util-linux/commit/61b384b36105fe682ddf16b9379f446d935603bc

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


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

[Touch-packages] [Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions

With the three combined I get down to:

real0m20.900s
us  sy  id  wa  st
32  33  35   0   0

43.88%  swapper
21.48%  sshd   
 3.07%  dbus-daemon
 2.78%  systemd
 2.10%  gdbus  
 1.96%  grep   
 1.80%  run-parts  
 1.68%  systemd-logind 
 1.38%  find   
 1.24%  systemd-journal
 1.23%  bash   
 1.12%  update-motd-fsc
 1.10%  cat
 0.95%  awk
 0.85%  50-motd-news   
 0.76%  uname  
 0.70%  00-header  
 0.69%  91-release-upgr
 0.67%  97-overlayroot 
 0.67%  50-landscape-sy
 0.62%  date   
 0.61%  90-updates-avai
 0.56%  95-hwe-eol 
 0.54%  cut 

None of the remaining big contributions to consumption is from the MOTD
efforts (all <2%).

That is reasonable, nice time gain as well as reduced cpu consumption.

** Changed in: landscape-client (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => In Progress

** Changed in: update-notifier (Ubuntu)
   Status: New => In Progress

** Changed in: update-notifier (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

** Changed in: ubuntu-release-upgrader (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

** Changed in: landscape-client (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

** Changed in: landscape-client (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => High

** Changed in: update-notifier (Ubuntu)
   Importance: Undecided => High

** Changed in: update-motd (Ubuntu)
   Importance: High => Medium

** Changed in: pam (Ubuntu)
   Importance: High => Medium

** Changed in: update-motd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  scripts in /etc/update-motd.d/ run even on login via non-interactive
  scp and sftp sessions

Status in landscape-client package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in update-motd package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  In Progress

Bug description:
  My client has 200+ devices automatically uploading information via
  sftp and scp to a server every few minutes. After a recent update, I
  noticed the load on their server spiking through the roof. Upon
  investigation, I discovered a horde of landscape-sysinfo and
  /usr/bin/lsb_release processes running that correlated with login
  session notifications in /var/log/syslog and the load spikes.

  It appears that even in non-interactive sessions where this
  information will never be seen, the configuration options below in
  /etc/pam.d/sshd cause these items to be launched (in fact, probably
  everything in /etc/update-motd.d). This only started on the system in
  question after a recent set of system updates were installed.

  The content of /etc/update-motd.d/* really, really, really shouldn't
  be executed if the session in question is not interactive, as it
  provides no value at all. Unfortunately, to disable it for these non-
  interactive sessions, we also have to disable it for the interactive
  ones as well where it has some value (though not enough to make
  spiking the load on this server through the roof an acceptable
  tradeoff).

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  #sessionoptional pam_motd.so  motd=/run/motd.dynamic
  #sessionoptional pam_motd.so noupdate

  Also, looking at the script 00-header in /etc/update-motd.d/,
  /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release
  does include the necessary information:

  [ -r /etc/lsb-release ] && . /etc/lsb-release

  if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
  # Fall back to using the very slow lsb_release utility
  DISTRIB_DESCRIPTION=$(lsb_release -s -d)
  fi

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"

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


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

[Touch-packages] [Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions

#3 50-landscape-sysinfo

The landscape part already has a statement about "when it is from" as it
is not re-executed on high load. This is handy as it will also ensure
there is no confusion "from when" this info is if we skip for too
frequent invocations.

Since it has an alternate less useful output I've added checks to
replace this more often and not replace a good output with a bad one.

--- orig/50-landscape-sysinfo   2022-03-30 07:53:04.320551811 +
+++ /etc/update-motd.d/50-landscape-sysinfo 2022-03-30 10:04:00.536053398 
+
@@ -1,17 +1,39 @@
 #!/bin/sh
-# pam_motd does not carry the environment
-[ -f /etc/default/locale ] && . /etc/default/locale
-export LANG
-cores=$(grep -c ^processor /proc/cpuinfo 2>/dev/null)
-[ "$cores" -eq "0" ] && cores=1
-threshold="${cores:-1}.0"
-if [ $(echo "`cut -f1 -d ' ' /proc/loadavg` < $threshold" | bc) -eq 1 ]; then
-echo
-echo -n "  System information as of "
-/bin/date
-echo
-/usr/bin/landscape-sysinfo
-else
-echo
-echo " System information disabled due to load higher than $threshold"
+
+# do try refresh this more than once per minute
+# Due to cpu consumption and login delays (LP: #1893716)
+stamp="/var/lib/landscape/landscape-sysinfo.cache"
+NEED_UPDATE="FALSE"
+find $stamp -newermt 'now-1 minutes' 2> /dev/null | grep -q -m 1 '.' || 
NEED_UPDATE="TRUE"
+# If the last report in cache wasn't useful (load was too high) still wait at 
least 5 seconds
+if grep -q "System information disabled" $stamp 2> /dev/null; then
+find $stamp -newermt 'now-5 seconds' 2> /dev/null | grep -q -m 1 '.' || 
NEED_UPDATE="TRUE"
 fi
+
+if [ "$NEED_UPDATE" = "TRUE" ]; then
+# pam_motd does not carry the environment
+[ -f /etc/default/locale ] && . /etc/default/locale
+export LANG
+cores=$(grep -c ^processor /proc/cpuinfo 2>/dev/null)
+[ "$cores" -eq "0" ] && cores=1
+threshold="${cores:-1}.0"
+if [ $(echo "`cut -f1 -d ' ' /proc/loadavg` < $threshold" | bc) -eq 1 ]; 
then
+   (
+echo
+echo -n "  System information as of "
+/bin/date
+echo
+/usr/bin/landscape-sysinfo
+) > $stamp
+else
+   # do not replace a formerly good result due to load
+   if ! grep -q "System information as of" $stamp 2> /dev/null; then
+   (
+   echo
+   echo " System information disabled due to load higher than 
$threshold"
+   ) > $stamp
+   fi
+fi
+fi
+
+[ ! -r "$stamp" ] || cat "$stamp"

# Info:
It might be worth to note, the optimizations to 95-hwe-eol and 
91-release-upgrade save CPU cycles (which is good and worth on its own), but do 
not improve the delay much.
The optimization to 

P.S. I'll need some minor updates for style and avoiding errors (e.g.
the && exit 0 was working but could be bad)

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

Title:
  scripts in /etc/update-motd.d/ run even on login via non-interactive
  scp and sftp sessions

Status in landscape-client package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in update-motd package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  In Progress

Bug description:
  My client has 200+ devices automatically uploading information via
  sftp and scp to a server every few minutes. After a recent update, I
  noticed the load on their server spiking through the roof. Upon
  investigation, I discovered a horde of landscape-sysinfo and
  /usr/bin/lsb_release processes running that correlated with login
  session notifications in /var/log/syslog and the load spikes.

  It appears that even in non-interactive sessions where this
  information will never be seen, the configuration options below in
  /etc/pam.d/sshd cause these items to be launched (in fact, probably
  everything in /etc/update-motd.d). This only started on the system in
  question after a recent set of system updates were installed.

  The content of /etc/update-motd.d/* really, really, really shouldn't
  be executed if the session in question is not interactive, as it
  provides no value at all. Unfortunately, to disable it for these non-
  interactive sessions, we also have to disable it for the interactive
  ones as well where it has some value (though not enough to make
  spiking the load on this server through the roof an acceptable
  tradeoff).

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  #sessionoptional pam_motd.so  motd=/run/motd.dynamic
  #sessionoptional pam_motd.so noupdate

  Also, looking at the script 00-header in /etc/update-motd.d/,
  /usr/bin/lsb_release is being

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

Internet also suggests other recent distributions will have the same
issue, https://ask.fedoraproject.org/t/cannot-connect-to-
wpa2-enterprise-university-wifi-on-fedora-36 for example

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

@Hans, fair enough. Googling for that error the first result here is 
https://www.ibm.com/mysupport/s/question/0D50z62ktWGCAY/why-ssl-handshake-fails-with-unsafe-legacy-renegotiation-disabled
which states

'This error means that the SSL server does not support the Renegotiation
Indication Extension (RFC 5746) and therefore is vulnerable to man-in-
the-middle attacks (CVE-2009-3555).

You will need to make sure the server is upgraded to support RFC 5746'


maybe you should try to contact your sysadmin to ask if that's the case?

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2009-3555

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions

#2 95-hwe-eol / update-motd-hwe-eol

Sadly this already does some caching in update-motd-hwe-eol by checking
if the last of these checks is older than an update to the source lists.
But to do so it has already executed the - relatively - rather expensive
apt-config calls.

Since it comes down to checking new sources.lists there is no need to
update this more often than once every few minutes or hours. Could be
even slower without loosing most of its value, but we already achieve
most of what we need with a delay of ~1h.

We started with:
 5.37%  apt-config
Now:
 -- no more present


--- orig/95-hwe-eol 2022-03-30 07:53:18.396529018 +
+++ /etc/update-motd.d/95-hwe-eol   2022-03-30 09:13:16.160985148 +
@@ -1,5 +1,11 @@
 #!/bin/sh
 
+# this stamp is created and updated by 
/usr/lib/update-notifier/update-motd-hwe-eol
+stamp="/var/lib/update-notifier/hwe-eol"
+
+# do not try to refresh this more than once per hour
+find $stamp -newermt 'now-1 hours' 2> /dev/null | grep -m 1 '.' && exit 0
+
 if [ -x /usr/lib/update-notifier/update-motd-hwe-eol ]; then
 exec /usr/lib/update-notifier/update-motd-hwe-eol
 fi


No big need left to reduce the apt-config usage in update-motd-hwe-eol after 
this change.

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

Title:
  scripts in /etc/update-motd.d/ run even on login via non-interactive
  scp and sftp sessions

Status in landscape-client package in Ubuntu:
  New
Status in pam package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-motd package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  New

Bug description:
  My client has 200+ devices automatically uploading information via
  sftp and scp to a server every few minutes. After a recent update, I
  noticed the load on their server spiking through the roof. Upon
  investigation, I discovered a horde of landscape-sysinfo and
  /usr/bin/lsb_release processes running that correlated with login
  session notifications in /var/log/syslog and the load spikes.

  It appears that even in non-interactive sessions where this
  information will never be seen, the configuration options below in
  /etc/pam.d/sshd cause these items to be launched (in fact, probably
  everything in /etc/update-motd.d). This only started on the system in
  question after a recent set of system updates were installed.

  The content of /etc/update-motd.d/* really, really, really shouldn't
  be executed if the session in question is not interactive, as it
  provides no value at all. Unfortunately, to disable it for these non-
  interactive sessions, we also have to disable it for the interactive
  ones as well where it has some value (though not enough to make
  spiking the load on this server through the roof an acceptable
  tradeoff).

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  #sessionoptional pam_motd.so  motd=/run/motd.dynamic
  #sessionoptional pam_motd.so noupdate

  Also, looking at the script 00-header in /etc/update-motd.d/,
  /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release
  does include the necessary information:

  [ -r /etc/lsb-release ] && . /etc/lsb-release

  if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
  # Fall back to using the very slow lsb_release utility
  DISTRIB_DESCRIPTION=$(lsb_release -s -d)
  fi

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"

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


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

[Touch-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

** Changed in: intel-media-driver-non-free (Ubuntu)
   Status: New => Fix Committed

** Changed in: intel-media-driver-non-free (Ubuntu)
   Importance: Undecided => High

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in intel-media-driver package in Ubuntu:
  Fix Committed
Status in intel-media-driver-non-free package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-03-30 Thread Hans Schulz

I won't attach a full system log of my work machine. I can confirm
however that I get the same "wpa_supplicant[3600]: OpenSSL:
openssl_handshake - SSL_connect error:0A000152:SSL routines::unsafe
legacy renegotiation disabled" error, even without the -d flag.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1967082] Re: SIGSEGV and out-of-bounds write during processing file via objdump

2022-03-30 Thread Nils

** Description changed:

  SIGSEGV and out-of-bounds write during processing file via objdump
  
  # Description
  During processing of the attached elf file via
  ```
  objdump -S testcase
  ```
- an out-of-bounds write is triggered and causes a segmentation fault (SIGSEGV)
- This allows an attacker to perform a denial of service and possibly opens up
- other attack vectors if files from untrusted sources are processed.
+ an out-of-bounds write is triggered and causes a segmentation fault (SIGSEGV) 
This allows an attacker to perform a denial of service and possibly opens up 
other attack vectors if files from untrusted sources are processed.
  
  For reproduction of the crash, I attached the following script(s):
    - reproduce-ubuntu.sh : Reproduction on Ubuntu 20.04
  
  Since I was unable to reproduce the bug upstream, I report it here.
  
  If you need further assistance, please do not hesitate to ask.
  
  # Ubuntu version
  # apt show binutils
  Package: binutils
  Version: 2.34-6ubuntu1.3
  Priority: optional
  Build-Essential: yes
  Section: devel
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Matthias Klose 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 110 kB
  Provides: binutils-gold, elf-binutils
  Depends: binutils-common (= 2.34-6ubuntu1.3), libbinutils (= 
2.34-6ubuntu1.3), binutils-x86-64-linux-gnu (= 2.34-6ubuntu1.3)
  Suggests: binutils-doc (>= 2.34-6ubuntu1.3)
  Conflicts: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), binutils-multiarch (<< 
2.27-8), modutils (<< 2.4.19-1)
  Homepage: https://www.gnu.org/software/binutils/
  Task: ubuntustudio-video, ubuntu-mate-core, ubuntu-mate-desktop
  Download-Size: 3380 B
  APT-Manual-Installed: yes
  APT-Sources: http://archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  Description: GNU assembler, linker and binary utilities
  
  # Ubuntu valgrind
  ==1== Memcheck, a memory error detector
  ==1== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==1== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
  ==1== Command: objdump -S /testcase
  ==1==
  objdump: warning: /testcase has a corrupt section with a size (3c3b031b01) 
larger than the file size
  objdump: /testcase: warning: loop in section dependencies detected
  objdump: warning: /testcase has a corrupt section with a size (3c3b031b01) 
larger than the file size
  ==1== Invalid write of size 4
  ==1==at 0x4A40248: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A3BD4F: bfd_elf64_object_p (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A1AB01: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x111B3C: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x4B360B2: (below main) (libc-start.c:308)
  ==1==  Address 0x4d469f4 is 1,940 bytes inside a block of size 4,064 free'd
  ==1==at 0x483CA3F: free (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==1==by 0x4ABC85B: objalloc_free_block (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A1AABF: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x111B3C: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x4B360B2: (below main) (libc-start.c:308)
  ==1==  Block was alloc'd at
  ==1==at 0x483B7F3: malloc (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==1==by 0x4ABC65B: _objalloc_alloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A227D4: bfd_alloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A22CED: bfd_zalloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A41DE9: _bfd_elf_new_section_hook (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A2485E: ??? (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A40CEB: _bfd_elf_make_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A401DE: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A3BD4F: bfd_elf64_object_p (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x4A1AB01: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
  ==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
  ==1==
  ==1== Invalid write of size 4
  ==1==at 0x4A40248: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)

[Touch-packages] [Bug 1967082] [NEW] SIGSEGV and out-of-bounds write during processing file via objdump

2022-03-30 Thread Nils

*** This bug is a security vulnerability ***

Public security bug reported:

SIGSEGV and out-of-bounds write during processing file via objdump

# Description
During processing of the attached elf file via
```
objdump -S testcase
```
an out-of-bounds write is triggered and causes a segmentation fault (SIGSEGV)
This allows an attacker to perform a denial of service and possibly opens up
other attack vectors if files from untrusted sources are processed.

For reproduction of the crash, I attached the following script(s):
  - reproduce-ubuntu.sh : Reproduction on Ubuntu 20.04

Since I was unable to reproduce the bug upstream, I report it here.

If you need further assistance, please do not hesitate to ask.

# Ubuntu version
# apt show binutils
Package: binutils
Version: 2.34-6ubuntu1.3
Priority: optional
Build-Essential: yes
Section: devel
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Matthias Klose 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 110 kB
Provides: binutils-gold, elf-binutils
Depends: binutils-common (= 2.34-6ubuntu1.3), libbinutils (= 2.34-6ubuntu1.3), 
binutils-x86-64-linux-gnu (= 2.34-6ubuntu1.3)
Suggests: binutils-doc (>= 2.34-6ubuntu1.3)
Conflicts: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), binutils-multiarch (<< 
2.27-8), modutils (<< 2.4.19-1)
Homepage: https://www.gnu.org/software/binutils/
Task: ubuntustudio-video, ubuntu-mate-core, ubuntu-mate-desktop
Download-Size: 3380 B
APT-Manual-Installed: yes
APT-Sources: http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
Description: GNU assembler, linker and binary utilities

# Ubuntu valgrind
==1== Memcheck, a memory error detector
==1== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==1== Command: objdump -S /testcase
==1==
objdump: warning: /testcase has a corrupt section with a size (3c3b031b01) 
larger than the file size
objdump: /testcase: warning: loop in section dependencies detected
objdump: warning: /testcase has a corrupt section with a size (3c3b031b01) 
larger than the file size
==1== Invalid write of size 4
==1==at 0x4A40248: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A3BD4F: bfd_elf64_object_p (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A1AB01: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
==1==by 0x111B3C: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
==1==by 0x4B360B2: (below main) (libc-start.c:308)
==1==  Address 0x4d469f4 is 1,940 bytes inside a block of size 4,064 free'd
==1==at 0x483CA3F: free (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==1==by 0x4ABC85B: objalloc_free_block (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A1AABF: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
==1==by 0x111B3C: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
==1==by 0x4B360B2: (below main) (libc-start.c:308)
==1==  Block was alloc'd at
==1==at 0x483B7F3: malloc (in 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==1==by 0x4ABC65B: _objalloc_alloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A227D4: bfd_alloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A22CED: bfd_zalloc (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A41DE9: _bfd_elf_new_section_hook (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A2485E: ??? (in /usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A40CEB: _bfd_elf_make_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A401DE: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A3BD4F: bfd_elf64_object_p (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A1AB01: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x116402: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
==1==by 0x116532: ??? (in /usr/bin/x86_64-linux-gnu-objdump)
==1==
==1== Invalid write of size 4
==1==at 0x4A40248: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A4036B: bfd_section_from_shdr (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A3BD4F: bfd_elf64_object_p (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x4A1AB01: bfd_check_format_matches (in 
/usr/lib/x86_64-linux-gnu/libbfd-2.34-system.so)
==1==by 0x116402: ??? (in

[Touch-packages] [Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions

Collecting snippets:

This one worked, proven by eliminating lsb_release on the consumption
charts.

#1 Caching for 91-release-upgrade:

--- orig/91-release-upgrade 2022-03-30 07:53:26.560515795 +
+++ /etc/update-motd.d/91-release-upgrade   2022-03-30 07:59:05.819971148 
+
@@ -1,7 +1,12 @@
 #!/bin/sh
 
 # if the current release is under development there won't be a new one
-if [ "$(lsb_release -sd | cut -d' ' -f4)" = "(development" ]; then
+[ -r /etc/lsb-release ] && . /etc/lsb-release
+if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
+DISTRIB_DESCRIPTION=$(lsb_release -s -d)
+fi
+
+if [ "$(echo "$DISTRIB_DESCRIPTION" | cut -d' ' -f4)" = "(development" ]; then
 exit 0
 fi

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

Title:
  scripts in /etc/update-motd.d/ run even on login via non-interactive
  scp and sftp sessions

Status in landscape-client package in Ubuntu:
  New
Status in pam package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-motd package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  New

Bug description:
  My client has 200+ devices automatically uploading information via
  sftp and scp to a server every few minutes. After a recent update, I
  noticed the load on their server spiking through the roof. Upon
  investigation, I discovered a horde of landscape-sysinfo and
  /usr/bin/lsb_release processes running that correlated with login
  session notifications in /var/log/syslog and the load spikes.

  It appears that even in non-interactive sessions where this
  information will never be seen, the configuration options below in
  /etc/pam.d/sshd cause these items to be launched (in fact, probably
  everything in /etc/update-motd.d). This only started on the system in
  question after a recent set of system updates were installed.

  The content of /etc/update-motd.d/* really, really, really shouldn't
  be executed if the session in question is not interactive, as it
  provides no value at all. Unfortunately, to disable it for these non-
  interactive sessions, we also have to disable it for the interactive
  ones as well where it has some value (though not enough to make
  spiking the load on this server through the roof an acceptable
  tradeoff).

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  #sessionoptional pam_motd.so  motd=/run/motd.dynamic
  #sessionoptional pam_motd.so noupdate

  Also, looking at the script 00-header in /etc/update-motd.d/,
  /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release
  does include the necessary information:

  [ -r /etc/lsb-release ] && . /etc/lsb-release

  if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
  # Fall back to using the very slow lsb_release utility
  DISTRIB_DESCRIPTION=$(lsb_release -s -d)
  fi

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"

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


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

[Touch-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Oh the upstream tags 'crocus' and 'iris' suggest it affects old and new
Intel GPUs equally.

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in Mesa:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Report upstream as
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6229 and git bisected
to https://gitlab.freedesktop.org/mesa/mesa/-/commit/60d95c5d

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #6229
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6229

** Changed in: mesa (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6229
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in Mesa:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

@Hans, you should probably open a new bug with a debug log attach as
described in comment #6 so we can ensure it's the same issue you are
seeing

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-30 Thread Bug Watch Updater

** Changed in: ibus
   Status: Unknown => New

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus:
  New
Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here：https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1967064] xdpyinfo.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574630/+files/xdpyinfo.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] acpidump.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574628/+files/acpidump.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] nvidia-settings.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "nvidia-settings.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574629/+files/nvidia-settings.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] UdevDb.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1967064/+attachment/5574626/+files/UdevDb.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] Xrandr.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1967064/+attachment/5574627/+files/Xrandr.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] Re: wayland crash when plugging in external monitor

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1964037, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

** This bug has been marked a duplicate of bug 1964037
   gnome-shell crashes (fatal error logged in create_fallback_offscreen) when 
attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland 
session

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] ProcInterrupts.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574624/+files/ProcInterrupts.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] ProcModules.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574625/+files/ProcModules.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] ProcEnviron.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574623/+files/ProcEnviron.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] ProcCpuinfoMinimal.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574622/+files/ProcCpuinfoMinimal.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] ProcCpuinfo.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574621/+files/ProcCpuinfo.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] NvidiaBugReportLog.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "NvidiaBugReportLog.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574620/+files/NvidiaBugReportLog.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] Lsusb-t.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574618/+files/Lsusb-t.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] Lspci-vt.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574616/+files/Lspci-vt.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] CurrentDmesg.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574613/+files/CurrentDmesg.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] Lsusb-v.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574619/+files/Lsusb-v.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] Lspci.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1967064/+attachment/5574615/+files/Lspci.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] DpkgLog.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574614/+files/DpkgLog.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] Lsusb.txt

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1967064/+attachment/5574617/+files/Lsusb.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
  InstallationDate: Installed on 2022-03-26 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
  MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: wayland (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  wayland-session jammy ubuntu
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 2.2
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.02
  dmi.board.name: CH570
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
  dmi.product.family: 1A582018 Razer Blade
  dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
  dmi.product.sku: RZ09-0409CEC3
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1967064] Re: wayland crash when plugging in external monitor

*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037

apport information

** Tags added: apport-collected jammy ubuntu wayland-session

** Description changed:

- When I plug in an external monitor via usb-c thunderbolt port wayland
- crashes and returns to the login screen.
+ When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
+ --- 
+ ProblemType: Bug
+ .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
+ .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
+ .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
+ .proc.driver.nvidia.registry: Binary: ""
+ .proc.driver.nvidia.suspend: suspend hibernate resume
+ .proc.driver.nvidia.suspend_depth: default modeset uvm
+ .proc.driver.nvidia.version:
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
+  GCC version:
+ ApportVersion: 2.20.11-0ubuntu79
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CasperMD5CheckResult: pass
+ CompositorRunning: None
+ CurrentDesktop: ubuntu:GNOME
+ DistUpgraded: Fresh install
+ DistroCodename: jammy
+ DistroRelease: Ubuntu 22.04
+ DistroVariant: ubuntu
+ DkmsStatus: openrazer-driver/3.2.0, 5.15.0-23-generic, x86_64: installed
+ GraphicsCard:
+  Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) 
(prog-if 00 [VGA controller])
+Subsystem: Razer USA Ltd. TigerLake-H GT1 [UHD Graphics] [1a58:2018]
+  NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:249c] (rev a1) (prog-if 00 [VGA controller])
+Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 
8GB/16GB] [1a58:2018]
+ InstallationDate: Installed on 2022-03-26 (4 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
+ MachineType: Razer Blade 15 Advanced Model (Mid 2021) - RZ09-0409
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: wayland (not installed)
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=25b0f42f-f5d4-44af-bd85-c145039c9772 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
+ Tags:  wayland-session jammy ubuntu
+ Uname: Linux 5.15.0-23-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/12/2021
+ dmi.bios.release: 2.2
+ dmi.bios.vendor: Razer
+ dmi.bios.version: 2.02
+ dmi.board.name: CH570
+ dmi.board.vendor: Razer
+ dmi.board.version: 4
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Razer
+ dmi.ec.firmware.release: 1.2
+ dmi.modalias: 
dmi:bvnRazer:bvr2.02:bd11/12/2021:br2.2:efr1.2:svnRazer:pnBlade15AdvancedModel(Mid2021)-RZ09-0409:pvr7.04:rvnRazer:rnCH570:rvr4:cvnRazer:ct10:cvr:skuRZ09-0409CEC3:
+ dmi.product.family: 1A582018 Razer Blade
+ dmi.product.name: Blade 15 Advanced Model (Mid 2021) - RZ09-0409
+ dmi.product.sku: RZ09-0409CEC3
+ dmi.product.version: 7.04
+ dmi.sys.vendor: Razer
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.110-1ubuntu1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
+ version.libgl1-mesa-glx: libgl1-mesa-glx N/A
+ version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
+ version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

** Attachment added: ".proc.driver.nvidia.params.txt"
   
https://bugs.launchpad.net/bugs/1967064/+attachment/5574612/+files/.proc.driver.nvidia.params.txt

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

Title:
  wayland crash when plugging in external monitor

Status in mutter package in Ubuntu:
  New

Bug description:
  When I plug in an external monitor via usb-c thunderbolt port wayland crashes 
and returns to the login screen.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied:

[Touch-packages] [Bug 1967064] [NEW] wayland crash when plugging in external monitor