[Touch-packages] [Bug 1975400] [NEW] Unable to change Display resolution to its full capacity

2022-05-21 Thread Anuj Sain
Public bug reported:

It's showing 'unknown display'.
Running this 'ubuntu-drivers devices' showed no output.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 22 11:22:50 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor Family 
Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2022-05-21 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Gigabyte Technology Co., Ltd. H81M-S
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=963a4763-1838-41e9-ab01-dff1efefa136 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-S
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/19/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H81M-S
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  Unable to change Display resolution to its full capacity

Status in xorg package in Ubuntu:
  New

Bug description:
  It's showing 'unknown display'.
  Running this 'ubuntu-drivers devices' showed no output.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 11:22:50 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor 
Family Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2022-05-21 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Gigabyte Technology Co., Ltd. H81M-S
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=963a4763-1838-41e9-ab01-dff1efefa136 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-S
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/19/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd

[Touch-packages] [Bug 1972123] Re: Online accounts crashes on sign in

2022-05-21 Thread DuckDuckWhale
Thanks, I can confirm this workaround works and my to-dos are syncing
now.

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

Title:
  Online accounts crashes on sign in

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my to-dos weren't syncing, so I checked online accounts
  and there's this triangle warning icon.  I click into it and it says
  "Credentials have expired", "Sign in to enable this account."  Now
  when I click "Sign in", the pop up changes to a frozen progress bar on
  top and with empty content, then crashes after a few seconds.  Now I
  can't sync anything and can't fix it.

  Ubuntu 22.04 LTS, Wayland on Nvidia 510

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


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


[Touch-packages] [Bug 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04

2022-05-21 Thread Muhammad Hafidz Pratama
I'm kind of getting this bug but not sure if it's the same situation
since I still able to connect using QR code.

Basically the difference from my case is :

...
- connect another device to the wifi created
- fail to connect after input password (already tried change password many time 
but still not working)
- success connecting after scan QR code (I'm using mobile device obviously)

Maybe there are some problem with the password security since Security
type of the wi-fi hotspot can not be change and stuck at WPA (if I'm not
wrong, the last config of my wi-fi hotspot security type before upgrade
to 22.04 is WPA2-PSK).

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

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


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


[Touch-packages] [Bug 1972123] Re: Online accounts crashes on sign in

2022-05-21 Thread Jouko Karvonen
I had the same problem, and I had just switched to Wayland when this
happened, so I thought it might be the culprit. I tried logging out
without Wayland and indeed "Sign in" worked. Seems that the webkit view
crashes on Wayland. I'm also on 22.04, Nvidia 510.

Logging back in on Wayland after having signed in, things keep working,
so this would be a temporary workaround.

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

Title:
  Online accounts crashes on sign in

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my to-dos weren't syncing, so I checked online accounts
  and there's this triangle warning icon.  I click into it and it says
  "Credentials have expired", "Sign in to enable this account."  Now
  when I click "Sign in", the pop up changes to a frozen progress bar on
  top and with empty content, then crashes after a few seconds.  Now I
  can't sync anything and can't fix it.

  Ubuntu 22.04 LTS, Wayland on Nvidia 510

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


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


[Touch-packages] [Bug 1975383] [NEW] Please enable vmci support

2022-05-21 Thread Oliver Kurth
Public bug reported:

zmq supports vsock for communication between virtual machines and hosts.
For example, to listen on a vsock port you can specify vmci://*: for
the socket. This feature is enabled with the option '--with-vmci' for
the configure script. I have made that change in the debian/rules file
and the resulting package works fine.

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

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

Title:
  Please enable vmci support

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  zmq supports vsock for communication between virtual machines and
  hosts. For example, to listen on a vsock port you can specify
  vmci://*: for the socket. This feature is enabled with the option
  '--with-vmci' for the configure script. I have made that change in the
  debian/rules file and the resulting package works fine.

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


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


[Touch-packages] [Bug 1972721] Re: Include gtk3 changes needed for mutter 42.1

2022-05-21 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.33-2ubuntu1

---
gtk+3.0 (3.24.33-2ubuntu1) kinetic; urgency=medium

  * Resynchronize with Debian, remaining changes
+ Install a settings.ini file to set our themes
+ Update debian/libgtk-3-0.symbols
+ debian/control.in and debian/tests/control (installed-tests):
  - Build-depend on adwaita-icon-theme-full for icon name check test
+ debian/control.in: Build-Depend on dh-sequence-translations
+ Ubuntu-specific patches:
  - 073_treeview_almost_fixed.patch
  - bzg_gtkcellrenderer_grabbing_modifier.patch
  - ubuntu_gtk_custom_menu_items.patch
  - print-dialog-show-options-of-remote-dnssd-printers.patch
  - uimanager-guard-against-nested-node-updates.patch
  - x-canonical-accel.patch
  - message-dialog-restore-traditional-look-on-unity.patch
  - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
  - restore_filechooser_typeaheadfind.patch
  - 0001-calendar-always-emit-day-selected-once.patch
  - 0001-gtkwindow-set-transparent-background-color.patch
  - unity-border-radius.patch
  - unity-headerbar-maximized-mode.patch

gtk+3.0 (3.24.33-2) unstable; urgency=medium

  * Cherry-pick gtk-3-24 commits needed for mutter 42.1 (LP: #1972721)

 -- Jeremy Bicha   Mon, 09 May 2022 16:12:01 -0400

** Changed in: gtk+3.0 (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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1972721

Title:
  Include gtk3 changes needed for mutter 42.1

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  We need to update gtk3 before updating mutter to 42.1. Otherwise, in gtk3 
apps like gedit, it's not possible to scroll past the cursor position.

  The mutter issue with more details is
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2261

  We need to update mutter 42.1 since it includes a lot of bug fixes.

  GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and
  gtk4) will better comply with the Wayland specifications.

  The gtk4 bug is LP: #1972722

  Test Case
  -
  Install the updated gtk3 packages.
  Use gedit to open a long text file.
  Scroll down past the page break.
  The document should scroll normally.

  What Could Go Wrong
  ---
  Ideally, GNOME would have done a new GTK3 release for this issue. They will 
eventually, but it seems better for Ubuntu to be proactive and not further 
delay the mutter/gnome-shell 42.1 releases.

  These commits are cherry-picks from the stable branch
  https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-3-24/

  NOTE
  
  To avoid a temporary mismatch related to phased updates, we want this update 
to be 100% phased before releasing mutter 42.1 to jammy-updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1972721/+subscriptions


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


[Touch-packages] [Bug 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial

2022-05-21 Thread A. Denton
Solved it for me by editing /etc/apparmor.d/usr.bin.firefox on XSE
(Debian- & Xubutnu 18.04 LTS-based distro):

  # per-user firefox configuration
  #...
  owner @{HOME}/.{firefox,mozilla}/**/gmp-widevinecdm/*/lib*so m,


That solved the problem when using Mz Firefox 100.0 (64-bit) and widevine 
4.10.2449.0

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

Title:
  firefox plugin libwidevinecdm.so crashes due to apparmor denial

Status in apparmor package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04, Firefox 60.0.1+build2-0ubuntu0.18.04.1

  Running firefix, then going to netflix.com and attempting to play a
  movie.  The widevinecdm plugin crashes, the following is found in
  syslog:

  
  Jun 15 19:13:22 xplt kernel: [301351.553043] audit: type=1400 
audit(1529046802.585:246): apparmor="DENIED" operation="file_mmap" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
 pid=16118 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000
  Jun 15 19:13:22 xplt kernel: [301351.553236] audit: type=1400 
audit(1529046802.585:247): apparmor="DENIED" operation="ptrace" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox" 
requested_mask="trace" denied_mask="trace" 
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
  Jun 15 19:13:22 xplt kernel: [301351.553259] plugin-containe[16118]: segfault 
at 0 ip 7fcdfdaa76af sp 7ffc1ff03e28 error 6 in 
libxul.so[7fcdfb77a000+6111000]
  Jun 15 19:13:22 xplt snmpd[2334]: error on subcontainer 'ia_addr' insert (-1)
  Jun 15 19:13:22 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!! 
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
  Jun 15 19:13:24 xplt kernel: [301353.960182] audit: type=1400 
audit(1529046804.994:248): apparmor="DENIED" operation="file_mmap" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
 pid=16135 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000
  Jun 15 19:13:24 xplt kernel: [301353.960373] audit: type=1400 
audit(1529046804.994:249): apparmor="DENIED" operation="ptrace" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox" 
requested_mask="trace" denied_mask="trace" 
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
  Jun 15 19:13:24 xplt kernel: [301353.960398] plugin-containe[16135]: segfault 
at 0 ip 7fe3b57f46af sp 7ffe6dc0b488 error 6 in 
libxul.so[7fe3b34c7000+6111000]
  Jun 15 19:13:28 xplt kernel: [301357.859177] audit: type=1400 
audit(1529046808.895:250): apparmor="DENIED" operation="file_mmap" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
 pid=16139 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000
  Jun 15 19:13:28 xplt kernel: [301357.859328] audit: type=1400 
audit(1529046808.895:251): apparmor="DENIED" operation="ptrace" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox" 
requested_mask="trace" denied_mask="trace" 
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
  Jun 15 19:13:28 xplt kernel: [301357.859349] plugin-containe[16139]: segfault 
at 0 ip 7fcf32ae06af sp 7ffeb8a136c8 error 6 in 
libxul.so[7fcf307b3000+6111000]
  Jun 15 19:13:25 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!! 
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
  Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ERROR block_reap:328: 
[hamster] bad exit code 1
  Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!! 
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
  Jun 15 19:13:29 xplt kernel: [301358.227635] audit: type=1400 
audit(1529046809.263:252): apparmor="DENIED" operation="file_mmap" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
 pid=16188 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000 
ouid=1000
  Jun 15 19:13:29 xplt kernel: [301358.227811] audit: type=1400 
audit(1529046809.263:253): apparmor="DENIED" operation="ptrace" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox" 
requested_mask="trace" denied_mask="trace" 
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
  Jun 15 19:13:29 xplt kernel: [301358.227844] plugin-containe[16188]: segfault 
at 0 ip 7fe5667c66af sp 7fffe8cc0da8 error 6 in 
libxul.so[7fe564499000+6111000]
  Jun 15 19:13:31 xplt kernel: [301360.574177] audit: type=1400 
audit(1529046811.608:254): apparmor="DENIED" operation="file_mmap" 
profile="

[Touch-packages] [Bug 1975369] [NEW] conky is not visible - Ubuntu 22.04

2022-05-21 Thread mpetit987
Public bug reported:

conky is running from terminal but does not show on the desktop:

conky: desktop window (800015) is subwindow of root window (96)
conky: window type - dock
conky: drawing to create window (0xa02)
conky: drawing to double buffer

This is only happening in Ubuntu 22.04!

conky is visible in Ubuntu 18.04 20.04, Kubuntu 20.04, Kubuntu 22.04,
and KDE Neon

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 21 03:27:48 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell OptiPlex 755 [1028:0211]
   Subsystem: Dell OptiPlex 755 [1028:0211]
InstallationDate: Installed on 2022-04-22 (28 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Dell Inc. OptiPlex 755
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=5c6021ec-5923-467d-b2f9-d0a62f8823b2 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2011
dmi.bios.release: 18.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A21
dmi.board.name: 0PU052
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd12/07/2011:br18.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:sku:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  conky is not visible - Ubuntu 22.04

Status in xorg package in Ubuntu:
  New

Bug description:
  conky is running from terminal but does not show on the desktop:

  conky: desktop window (800015) is subwindow of root window (96)
  conky: window type - dock
  conky: drawing to create window (0xa02)
  conky: drawing to double buffer

  This is only happening in Ubuntu 22.04!

  conky is visible in Ubuntu 18.04 20.04, Kubuntu 20.04, Kubuntu 22.04,
  and KDE Neon

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 21 03:27:48 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2022-04-22 (28 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=5c6021ec-5923-467d-b2f9-d0a62f8823b2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2011
  dmi.bios.release: 18.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd12/07/2011:br18.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:sku:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  

[Touch-packages] [Bug 1971901] Re: dlltool uses non-unique temp filenames

2022-05-21 Thread Bug Watch Updater
Launchpad has imported 16 comments from the remote bug at
https://bugs.winehq.org/show_bug.cgi?id=52770.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2022-04-04T17:19:02+00:00 Bernhard Rosenkraenzer wrote:

Building wine 7.5 (with wine-staging patches, but they shouldn't be
relevant to this) with "make -j64" fails with

tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/rpcrt4/librpcrt4.delay.a --export \
  /home/bero/abf/wine/BUILD/wine-7.5/dlls/rpcrt4/rpcrt4.spec
/usr/bin/x86_64-w64-mingw32-dlltool: bfd_open failed reopen stub file: 
rpcrt4_dll_s00176.o: No such file or directory
winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
make: *** [Makefile:297034: dlls/rpcrt4/librpcrt4.delay.a] Error 1

Probably the library is assembled before all object files belonging to
it are built.

Building with make (without SMP) works.

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/11


On 2022-04-04T19:28:51+00:00 Cybermax wrote:

Is there a change if you build with lesser threads? Eg. make -j8 or
something assuming you have a threadripper with 32 cores/64 threads?

And possibly also interesting - distro, gcc and mingw-w64 version.

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/12


On 2022-04-04T19:36:49+00:00 Alexandre Julliard wrote:

These objects file are not created from the makefile. It sounds more
like it's running into some kind of resource limit.

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/13


On 2022-04-04T19:50:11+00:00 Cybermax wrote:

(In reply to Alexandre Julliard from comment #2)
> These objects file are not created from the makefile. It sounds more like
> it's running into some kind of resource limit.

tmpfs maybe? Just wondering since i got that exact error when building
wine on OBS.. Also got a couple of other very strange errors that failed
building on OBS with files that was not found, but could not find a
error message from the actual compile..

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/14


On 2022-04-08T13:04:47+00:00 Eric-pouech wrote:

I've run into a similar issue

looking at the compile traces lets me believe that the issue arises when two 
instances of mingw dlltool run at the same time, and thrashing each other 
temporary files

indeed, this ugly hack lets the compilation succeeds (it was failing almost 
always; sometimes on a different DLL)
---
diff --git a/tools/winebuild/import.c b/tools/winebuild/import.c
index c876d51f8e6..8049530a7e5 100644
--- a/tools/winebuild/import.c
+++ b/tools/winebuild/import.c
@@ -1595,7 +1595,11 @@ static void build_windows_import_lib( const char *lib_na>
 strarray_add( &args, lib_name );
 strarray_add( &args, "-d" );
 strarray_add( &args, def_file );
-
+strarray_add( &args, "-t" );
+{
+   char tmp[128]; sprintf(tmp, "%u\n", getpid());
+   strarray_add( &args, tmp );
+}
 switch (target.cpu)
 {
 case CPU_i386:
--
Bernhard, can you test this on your side?

I don't see a simple way to fix it...

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/15


On 2022-04-08T15:03:19+00:00 Eric-pouech wrote:

hmmm thinking about it, doesn't look quite right (or sufficient)

in the dlltool source code, if no -t prefix is given, will generate its own 
prefix based on pid...
need more investigation

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/16


On 2022-04-08T15:31:06+00:00 Eric-pouech wrote:

I'm testing on two environments:
E1) with dlltool 2.38-1
E2) with dlltool 2.37-3

I see the error in E1 only 

on all env, I run 
> strace winebuild...  -v -v >& log
> grep exec log

results:

E2) 
pid 12272] execve("/usr/bin/x86_64-w64-mingw32-dlltool", 
["/usr/bin/x86_64-w64-mingw32-dllt"..., "-k", "-y", 
"dlls/iphlpapi/libiphlpapi.delay."..., "-d", "libiphlpapi.delay-625082dd.def", 
"-m", "i386:x86-64", "--as-flags=--64"], 0x7ffc19487b48 /* 56 vars */) = 0
[pid 12273] execve("/usr/bin/x86_64-w64-mingw32-as", 
["/usr/bin/x86_64-w64-mingw32-as", "--64", "-o", "daesh.o", "daesh.s"], 
0x7fffa1e12cf

[Touch-packages] [Bug 1956603] Re: > Internal error: Could not resolve keysym ...

2022-05-21 Thread Bug Watch Updater
** Changed in: libx11-xcb-perl (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  > Internal error:   Could not resolve keysym ...

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11-xcb-perl package in Ubuntu:
  Fix Released
Status in x11-xkb-utils package in Ubuntu:
  Invalid

Bug description:
  Get lot of such warnings into Jammy logged;
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard: