[Desktop-packages] [Bug 1986423] Re: Ubuntu logo overlapping a button.

2022-08-15 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- Ubuntu logo overlapping a button.
+ Ubuntu logo overlapping user selection widgets on the login screen

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986423

Title:
  Ubuntu logo overlapping user selection widgets on the login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Displaying the Ubuntu logo over "Not Listed" on the login screen.

  I'm using Ubuntu 22.04.1.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 13 11:23:28 2022
  DistUpgraded: 2022-08-11 21:55:03,477 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:161c]
  InstallationDate: Installed on 2021-03-26 (504 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=c83ab0ab-bcc6-4f8e-a43f-c872be521021 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-08-11 (1 days ago)
  dmi.bios.date: 02/13/2018
  dmi.bios.release: 15.103
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.67
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.asset.tag: CZC23633JQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.67:bd02/13/2018:br15.103:efr151.78:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuSN246UP#ABF:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.sku: SN246UP#ABF
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

2022-08-15 Thread Daniel van Vugt
I wonder if this is related to the extensions being restarted (panels
recreated) after unlocking. Mutter's window constraints code might
handle conflicts between panels and windows when the windows change
state, but not when a new panel suddenly appears.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1961508

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


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


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

2022-08-15 Thread Launchpad Bug Tracker
[Expired for gst-plugins-good1.0 (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Incomplete => Expired

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

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

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

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

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

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


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


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

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

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

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

Status in xorg package in Ubuntu:
  New

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

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

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

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

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


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


[Desktop-packages] [Bug 1986606] [NEW] When locking computer with Win+L, screen goes black permanently

2022-08-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

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

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

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

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

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
When locking computer with Win+L, screen goes black permanently
https://bugs.launchpad.net/bugs/1986606
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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


[Desktop-packages] [Bug 1986607] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-15 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1986607

Title:
  package firefox 103.0+build1-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  Not an expert in this field, I just want to report the problem to the
  developers.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 103.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
  Uname: Linux 5.4.0-124-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  farooq 1591 F pulseaudio
  BuildID: 20220718155818
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Tue Aug 16 06:48:51 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (1068 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.43.199 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.43.0/24 dev wlp3s0 proto kernel scope link src 192.168.43.99 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-16 (0 days ago)
  dmi.bios.date: 10/14/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M50Vm
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr212:bd10/14/2009:svnASUSTeKComputerInc.:pnM50Vm:pvr1.0:rvnASUSTeKComputerInc.:rnM50Vm:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M50Vm
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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


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


[Desktop-packages] [Bug 1986607] [NEW] package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-15 Thread Farooq Ali Khan
Public bug reported:

Not an expert in this field, I just want to report the problem to the
developers.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 103.0+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
Uname: Linux 5.4.0-124-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  farooq 1591 F pulseaudio
BuildID: 20220718155818
CasperMD5CheckResult: unknown
Channel: Unavailable
Date: Tue Aug 16 06:48:51 2022
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-09-12 (1068 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
IpRoute:
 default via 192.168.43.199 dev wlp3s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp3s0 scope link metric 1000 
 192.168.43.0/24 dev wlp3s0 proto kernel scope link src 192.168.43.99 metric 600
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: 
new firefox package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to jammy on 2022-08-16 (0 days ago)
dmi.bios.date: 10/14/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M50Vm
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr212:bd10/14/2009:svnASUSTeKComputerInc.:pnM50Vm:pvr1.0:rvnASUSTeKComputerInc.:rnM50Vm:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M50Vm
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1986607

Title:
  package firefox 103.0+build1-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  Not an expert in this field, I just want to report the problem to the
  developers.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 103.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
  Uname: Linux 5.4.0-124-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  farooq 1591 F pulseaudio
  BuildID: 20220718155818
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Tue Aug 16 06:48:51 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (1068 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.43.199 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.43.0/24 dev wlp3s0 proto kernel scope link src 192.168.43.99 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-16 (0 days ago)
  dmi.bios.date: 10/14/2009
  dmi.bios.vendor: American 

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

2022-08-15 Thread Daniel van Vugt
** No longer affects: gtk

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1949340

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

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

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

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

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

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


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


[Desktop-packages] [Bug 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

2022-08-15 Thread Launchpad Bug Tracker
This bug was fixed in the package tracker-miners -
2.3.3-2ubuntu0.20.04.1

---
tracker-miners (2.3.3-2ubuntu0.20.04.1) focal; urgency=medium

  * d/p/libtracker-miners-common-Add-newstatat-statat64-syscalls.patch:
cherry-picked from upstream to prevent seccomp crashes with newer glibc,
notably during dist-upgrade. (LP: #1983859)

 -- Simon Chopin   Wed, 10 Aug 2022 14:05:34 +0200

** Changed in: tracker-miners (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/1983859

Title:
  tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

Status in tracker-miners package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in tracker-miners source package in Focal:
  Fix Released
Status in ubuntu-release-upgrader source package in Focal:
  Invalid

Bug description:
  [Impact]
  The crash will prompt users during the ugprade, leaving a relatively bad user 
experience, compounded by the fact that the issue is marked by apport as 
"Unreportable" since the exec that crashed has usually been removed during the 
upgrade by the time the user tries to report it.

  [Fix]
  The crash is due to the Focal tracker-extract binary being triggered during 
the upgrade while its dependencies, including glibc have already been switched 
to their Jammy version, leading to new syscalls being used that the Focal 
seccomp filter didn't know about, notably fstatat64.

  There's an upstream commit addressing this specific issue that has been 
cherry-picked in both Hirsute and Debian, see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983637

  The fix is just backporting this patch further back to Focal, adding
  fstatat64 and newfstatat to the allowed-list of the seccomp filter. I
  consider those two syscalls fairly safe and legitimate.

  [Test plan]
  - Boot a pristine Focal VM
  - Install tracker-extract & tracker-miners from -proposed
  - run do-release-upgrade -d
    -> continue through the "do you want to continue" prompts
  => If all goes well the upgrade should finish and ask you to reboot
  => Otherwise you'd have a tracker-extract crash during the dist-upgrade phase 
of the upgrade

  [Regression potential]
  Messing with the seccomp filter could lead to the filter being made either 
too restrictive, making tracker-extract crash whenever called, or too 
permissive, weakening the sandboxing for this binary. That latter possibility 
is IMO more worrisome given the purpose of the package.

  [Original report]
  When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty much 
always) a crash from tracker-extract, as described in the following error 
report:

  https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0

  The crash occurs during the upgrade, which means it's fairly hard to
  investigate exactly what's going on as apport fails to extract a stack
  trace, the binaries being overwritten during the upgrade.

  However, the crash occurs because of a unhandled SIGSYS, meaning a
  seccomp filter issue. I've tried backporting this patch fixing a
  similar issue:

  https://gitlab.gnome.org/GNOME/tracker-
  miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef

  but it doesn't apply, likely due to the code having diverged too much
  since.

  My proposal is thus to disable tracker-extract during upgrade,
  including in all user sessions. I'm assuming that the new version will
  be enabled automatically as its unit file changed name anyway.

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


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


[Desktop-packages] [Bug 1986584] [NEW] nautilun crashes when i pluh-in iphone se

2022-08-15 Thread vbert
Public bug reported:

Stack trace: https://termbin.com/pd8x3

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


** Tags: iphone nautilus

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1986584

Title:
  nautilun crashes when i pluh-in iphone se

Status in nautilus package in Ubuntu:
  New

Bug description:
  Stack trace: https://termbin.com/pd8x3

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


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


[Desktop-packages] [Bug 1986583] [NEW] Screen after some time get shifted and starts to overlap

2022-08-15 Thread Ivan Krasicenko
Public bug reported:

problem resembles a lot this one:
https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right

"I am encountering a strange problem, my whole desktop has shifted to
right."

But different in a way, that when pc is started it shows everything just fine. 
But when computer is powered on a few days straight, display gets shifted. 
Some times just cca 1/4 of screen, sometimes it shifts over half of the screen. 
Computer should be used to run 8hours straight (it is intended for customer)
When i switch from graphic display to tty (ctrl+alt+num) and back, display gets 
"restarted" and
problem is fixed. But it is just temporary. Restart fixes it also.

Last time i encountered this behavior today between 17-18hour. But have
no idea what or where to look for.

yes, and when one connects to display over X11 or teamviewer screen
appears to be okay, so one will notice this problem if using pc remotely

1)
lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
2)
xorg:
  Installed: 1:7.7+23ubuntu2
  Candidate: 1:7.7+23ubuntu2
  Version table:
 *** 1:7.7+23ubuntu2 500
500 http://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
3) expect that display will stay where it is on the start of computer

4) display gets shifted to some distance from unknown reason (Maybe
x11vnc or teamviewer usage or something).

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

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


** Tags: amd64 apport-bug jammy ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1986583

Title:
  Screen after some time get shifted and starts to overlap

Status in xorg package in Ubuntu:
  New

Bug description:
  problem resembles a lot this one:
  https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right

  "I am encountering a strange problem, my whole desktop has shifted to
  right."

  But different in a way, that when pc is started it shows everything just 
fine. 
  But when computer is powered on a few days straight, display gets shifted. 
  Some times just cca 1/4 of screen, 

[Desktop-packages] [Bug 1986423] Re: Ubuntu logo overlapping a button.

2022-08-15 Thread Amin Hassaïni
I can't take screenshots from the login screen, but here is a photo from
my phone.

** Attachment added: "Photo of the bug"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986423/+attachment/5608868/+files/16605891387541662930868670564619.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986423

Title:
  Ubuntu logo overlapping a button.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Displaying the Ubuntu logo over "Not Listed" on the login screen.

  I'm using Ubuntu 22.04.1.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 13 11:23:28 2022
  DistUpgraded: 2022-08-11 21:55:03,477 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:161c]
  InstallationDate: Installed on 2021-03-26 (504 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=c83ab0ab-bcc6-4f8e-a43f-c872be521021 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-08-11 (1 days ago)
  dmi.bios.date: 02/13/2018
  dmi.bios.release: 15.103
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.67
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.asset.tag: CZC23633JQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.67:bd02/13/2018:br15.103:efr151.78:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuSN246UP#ABF:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.sku: SN246UP#ABF
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1986450] ShellJournal.txt

2022-08-15 Thread Tarmo Turunen
apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1986450/+attachment/5608864/+files/ShellJournal.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2018-04-27 (1570 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 42.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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


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


[Desktop-packages] [Bug 1986450] monitors.xml.txt

2022-08-15 Thread Tarmo Turunen
apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1986450/+attachment/5608865/+files/monitors.xml.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2018-04-27 (1570 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 42.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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


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


[Desktop-packages] [Bug 1986450] ProcEnviron.txt

2022-08-15 Thread Tarmo Turunen
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1986450/+attachment/5608863/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2018-04-27 (1570 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 42.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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


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


[Desktop-packages] [Bug 1986450] GsettingsChanges.txt

2022-08-15 Thread Tarmo Turunen
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1986450/+attachment/5608861/+files/GsettingsChanges.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2018-04-27 (1570 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 42.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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


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


[Desktop-packages] [Bug 1986450] ProcCpuinfoMinimal.txt

2022-08-15 Thread Tarmo Turunen
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1986450/+attachment/5608862/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2018-04-27 (1570 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 42.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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


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


[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper

2022-08-15 Thread Tarmo Turunen
apport information

** Tags added: apport-collected wayland-session

** Description changed:

  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there
  is a 1px wide vertical white line on the desktop that appears whenever
  an application has focus. It is on the right side of the monitor,
  covering the background wallpaper but not the menu.
  
- Workaround: in Displays, change scale to something else than 100% and
- then change back to 100%. That white vertical line will stay at the
- former 100% window size location until the Settings window is closed. It
- disappears when the Settings is closed.
+ Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2018-04-27 (1570 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: gnome-shell 42.2-0ubuntu0.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
+ RelatedPackageVersions: mutter-common 42.2-0ubuntu1
+ Tags:  wayland-session jammy
+ Uname: Linux 5.15.0-46-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1986450/+attachment/5608860/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2018-04-27 (1570 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 42.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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


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


[Desktop-packages] [Bug 1986454] ThreadStacktrace.txt

2022-08-15 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1986454/+attachment/5608840/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1986454/+attachment/5608569/+files/CoreDump.gz

** Changed in: gnome-disk-utility (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- gnome-disks crashed with SIGABRT in g_assertion_message_expr()
+ gnome-disks crashed with SIGABRT in g_assertion_message()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1986454

Title:
  gnome-disks crashed with SIGABRT in g_assertion_message()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  I deleted the single partition on a USB stick and after it was done (I
  checked with lsblk) gnome-disks still said "Deleting Partition (x)"
  and I clicked the circle with a cross and it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-disk-utility 43~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 14 11:50:16 2022
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2022-08-13 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220813)
  JournalErrors:
   aug 14 11:50:16 hostname org.gnome.DiskUtility[2343]: **
   aug 14 11:50:16 hostname org.gnome.DiskUtility[2343]: 
GNOME-Disks:ERROR:../src/disks/gduwindow.c:4270:on_job_cancel_button_clicked: 
assertion failed: (object != NULL)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  Signal: 6
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-disks crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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


[Desktop-packages] [Bug 1986454] gnome-disks crashed with SIGABRT in g_assertion_message_expr()

2022-08-15 Thread Apport retracing service
StacktraceTop:
 g_assertion_message (domain=, file=, 
line=, func=0x55bb5efa5390 <__func__.23> 
"on_job_cancel_button_clicked", message=) at 
../../../glib/gtestutils.c:3253
 g_assertion_message_expr (domain=domain@entry=0x55bb5ef9d058 "GNOME-Disks", 
file=file@entry=0x55bb5efa3db7 "../src/disks/gduwindow.c", 
line=line@entry=4270, func=func@entry=0x55bb5efa5390 <__func__.23> 
"on_job_cancel_button_clicked", expr=expr@entry=0x55bb5efa3e90 "object != 
NULL") at ../../../glib/gtestutils.c:3279
 on_job_cancel_button_clicked (button=, user_data=) at ../src/disks/gduwindow.c:4270
 _g_closure_invoke_va (param_types=0x0, n_params=0, args=0x7ffea8e1b570, 
instance=0x55bb5fc4adc0, return_value=, closure=) 
at ../../../gobject/gclosure.c:893
 g_signal_emit_valist (instance=0x55bb5fc4adc0, signal_id=291, 
detail=, var_args=var_args@entry=0x7ffea8e1b570) at 
../../../gobject/gsignal.c:3406

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1986454

Title:
  gnome-disks crashed with SIGABRT in g_assertion_message()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  I deleted the single partition on a USB stick and after it was done (I
  checked with lsblk) gnome-disks still said "Deleting Partition (x)"
  and I clicked the circle with a cross and it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-disk-utility 43~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 14 11:50:16 2022
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2022-08-13 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220813)
  JournalErrors:
   aug 14 11:50:16 hostname org.gnome.DiskUtility[2343]: **
   aug 14 11:50:16 hostname org.gnome.DiskUtility[2343]: 
GNOME-Disks:ERROR:../src/disks/gduwindow.c:4270:on_job_cancel_button_clicked: 
assertion failed: (object != NULL)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  Signal: 6
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-disks crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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


[Desktop-packages] [Bug 1986454] Stacktrace.txt

2022-08-15 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1986454/+attachment/5608838/+files/Stacktrace.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1986454

Title:
  gnome-disks crashed with SIGABRT in g_assertion_message()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  I deleted the single partition on a USB stick and after it was done (I
  checked with lsblk) gnome-disks still said "Deleting Partition (x)"
  and I clicked the circle with a cross and it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-disk-utility 43~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 14 11:50:16 2022
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2022-08-13 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220813)
  JournalErrors:
   aug 14 11:50:16 hostname org.gnome.DiskUtility[2343]: **
   aug 14 11:50:16 hostname org.gnome.DiskUtility[2343]: 
GNOME-Disks:ERROR:../src/disks/gduwindow.c:4270:on_job_cancel_button_clicked: 
assertion failed: (object != NULL)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  Signal: 6
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-disks crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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


[Desktop-packages] [Bug 1986454] StacktraceSource.txt

2022-08-15 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1986454/+attachment/5608839/+files/StacktraceSource.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1986454

Title:
  gnome-disks crashed with SIGABRT in g_assertion_message()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  I deleted the single partition on a USB stick and after it was done (I
  checked with lsblk) gnome-disks still said "Deleting Partition (x)"
  and I clicked the circle with a cross and it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-disk-utility 43~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 14 11:50:16 2022
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2022-08-13 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220813)
  JournalErrors:
   aug 14 11:50:16 hostname org.gnome.DiskUtility[2343]: **
   aug 14 11:50:16 hostname org.gnome.DiskUtility[2343]: 
GNOME-Disks:ERROR:../src/disks/gduwindow.c:4270:on_job_cancel_button_clicked: 
assertion failed: (object != NULL)
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  Signal: 6
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-disks crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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


[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

2022-08-15 Thread Felipe Espic
Hi, I'm experiencing the same bug in 22.04LTS. I have attached a pic for
reference.

** Attachment added: "Screenshot from 2022-08-10 10-20-51.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1961508/+attachment/5608831/+files/Screenshot%20from%202022-08-10%2010-20-51.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1961508

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


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


[Desktop-packages] [Bug 1986452] Re: Sound: ubuntu loses track of the selected output sink

2022-08-15 Thread Brian Murray
** Tags added: jammy

** Package changed: ubuntu => gnome-control-center (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1986452

Title:
  Sound: ubuntu loses track of the selected output sink

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Whenever I'm on Ubuntu the audio loses track of the selected output device 
(Line Out - Built-in Audio), and does not save the selected output when 
restarting (and perhaps re-logging, I have not tried this). Having several 
output options to choose from the system apparently chooses the first detected 
device (in my case, HyperX Cloud Flight S, an USB device).
  HyperX Cloud Flight S is appropriately selected as the input device.
  This was present in 20.04 LTS, as well, but not in 18.04 LTS.

  Workaround: open the Sound Settings, select the correct output device
  and keep the Settings window with the Sound settings selected
  minimized on the Favorites. If you select some other settings or close
  the Settings Ubuntu will lose track of the output device in a few
  seconds.

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


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


[Desktop-packages] [Bug 1986452] [NEW] Sound: ubuntu loses track of the selected output sink

2022-08-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Whenever I'm on Ubuntu the audio loses track of the selected output device 
(Line Out - Built-in Audio), and does not save the selected output when 
restarting (and perhaps re-logging, I have not tried this). Having several 
output options to choose from the system apparently chooses the first detected 
device (in my case, HyperX Cloud Flight S, an USB device).
HyperX Cloud Flight S is appropriately selected as the input device.
This was present in 20.04 LTS, as well, but not in 18.04 LTS.

Workaround: open the Sound Settings, select the correct output device
and keep the Settings window with the Sound settings selected minimized
on the Favorites. If you select some other settings or close the
Settings Ubuntu will lose track of the output device in a few seconds.

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


** Tags: bot-comment jammy
-- 
Sound: ubuntu loses track of the selected output sink
https://bugs.launchpad.net/bugs/1986452
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-control-center in Ubuntu.

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


[Desktop-packages] [Bug 1986542] [NEW] Issue building the debian source archive

2022-08-15 Thread Alistair
Public bug reported:

I cannot build the ubuntu source package gst-plugins-
good1.0_1.20.3-0ubuntu1.dsc. I am doing:

> dget -q 
> http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc
> cd gst-plugins-good1.0-1.20.3/
> DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b

and I receive the error:

../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown
variable "static_build".

I am testing inside of an ubuntu:jammy-20220801 container.

I have narrowed the issue down to a patch in the changelog on the 15th
Mar which states "Import plugins from -bad that are needed for main
applications". This patch imports some "bad" plugins into the source but
the meson file isn't setup correctly for this to work. Manually removing
the patches related to the bad plugins fixed the issue.

** Affects: gst-plugins-good1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Issue building the debian source archive

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

Bug description:
  I cannot build the ubuntu source package gst-plugins-
  good1.0_1.20.3-0ubuntu1.dsc. I am doing:

  > dget -q 
http://archive.ubuntu.com/ubuntu/pool/main/g/gst-plugins-good1.0/gst-plugins-good1.0_1.20.3-0ubuntu1.dsc
  > cd gst-plugins-good1.0-1.20.3/
  > DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -us -uc -d -nc -b

  and I receive the error:

  ../gst-libs/gst/basecamerabinsrc/meson.build:28:3: ERROR: Unknown
  variable "static_build".

  I am testing inside of an ubuntu:jammy-20220801 container.

  I have narrowed the issue down to a patch in the changelog on the 15th
  Mar which states "Import plugins from -bad that are needed for main
  applications". This patch imports some "bad" plugins into the source
  but the meson file isn't setup correctly for this to work. Manually
  removing the patches related to the bad plugins fixed the issue.

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


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


[Desktop-packages] [Bug 1979919] Re: package firefox 101.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso nuevo paquete firefox script pre-installation devolvió el código de salida

2022-08-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1979919

Title:
  package firefox 101.0.1+build1-0ubuntu0.20.04.1 failed to
  install/upgrade: el subproceso nuevo paquete firefox script pre-
  installation devolvió el código de salida de error 1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Package stopped installing when upgrading from 20.04 to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 101.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-51-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arturo 1425 F pulseaudio
   /dev/snd/controlC0:  arturo 1425 F pulseaudio
  BuildID: 20220608170832
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Sun Jun 26 15:24:06 2022
  ErrorMessage: el subproceso nuevo paquete firefox script pre-installation 
devolvió el código de salida de error 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-01-02 (174 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IpRoute:
   default via 192.168.0.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.104 metric 
100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 101.0.1+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: el subproceso nuevo paquete firefox script pre-installation 
devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to jammy on 2022-06-26 (0 days ago)
  dmi.bios.date: 12/04/2019
  dmi.bios.release: 1.16
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8UCN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15AST
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvr8UCN16WW:bd12/04/2019:br1.16:efr1.16:svnLENOVO:pn81D6:pvrLenovoideapad330-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15AST:skuLENOVO_MT_81D6_BU_idea_FM_ideapad330-15AST:
  dmi.product.family: ideapad 330-15AST
  dmi.product.name: 81D6
  dmi.product.sku: LENOVO_MT_81D6_BU_idea_FM_ideapad 330-15AST
  dmi.product.version: Lenovo ideapad 330-15AST
  dmi.sys.vendor: LENOVO

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


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


[Desktop-packages] [Bug 1986456] Re: Firefox fails to start after update

2022-08-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1986456

Title:
  Firefox fails to start after update

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After system Updates today (14.08.2022) firefox did not start anymore.
  It's Ubuntu 22.04

  Error Message:

  mikey@mikey-notebook:~$ firefox
  /snap/firefox/1670/snap/command-chain/desktop-launch: line 52: 
/home/mikey/.config/user-dirs.dirs: Permission denied
  sed: can't read /home/mikey/.config/user-dirs.dirs: Permission denied
  /snap/firefox/1670/snap/command-chain/desktop-launch: line 264: 
/home/mikey/.config/user-dirs.dirs: Permission denied
  cp: cannot open '/home/mikey/.config/user-dirs.locale' for reading: 
Permission denied
  /snap/firefox/1670/snap/command-chain/desktop-launch: line 269: 
/home/mikey/.config/user-dirs.locale: Permission denied
  /snap/firefox/1670/snap/command-chain/desktop-launch: line 20: 
/snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0:
 No such file or directory
  ERROR: 
/snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0
 exited abnormally with status 127
  XPCOMGlueLoad error for file /snap/firefox/1670/usr/lib/firefox/libmozgtk.so:
  libgtk-3.so.0: cannot open shared object file: No such file or directory
  Couldn't load XPCOM.

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


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


[Desktop-packages] [Bug 1956885] Re: Incorrect verify implementation, unable to verify on one finger

2022-08-15 Thread Andy Chi
** Changed in: libfprint-2-tod1-broadcom
   Status: New => Confirmed

** Changed in: libfprint-2-tod1-broadcom
   Importance: Undecided => Critical

** Changed in: libfprint-2-tod1-broadcom
 Assignee: (unassigned) => Andy Chi (andch)

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

** Tags added: oem-priority originate-from-1985872 somerville

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1956885

Title:
  Incorrect verify implementation, unable to verify on one finger

Status in libfprint-2-tod1-broadcom:
  Confirmed
Status in OEM Priority Project:
  New
Status in libfprint package in Ubuntu:
  Confirmed

Bug description:
  The closed-source library blocks on synchronous USB transfers in its "verify" 
method (at least, there might be others with the same issue).
  The "identify" one is correct (asynchronous).

  As a result :
  $ fprintd-verify
  Using device /net/reactivated/Fprint/Device/0
  Listing enrolled fingers:
   - #0: right-index-finger
  (finger pressed)
  Verify started!
  Verifying: right-index-finger
  (blocked)

  "Verify started!" should happen immediately, but the code libfprint code 
waits for fp_device_verify to return, which only happens when the finger is 
pressed with this driver.
  The verify success message is sent during the call, so it is ignored.

  "fprintd-verify -f any" and pam-fprintd use fp_device_identify, so they work 
correctly.
  But with https://gitlab.freedesktop.org/libfprint/fprintd/-/commit/fc65055279 
(so I suppose on jammy), the "verify" method will be used instead if only one 
finger is enrolled.

  TL,DR: the fingerprint reader appears to mostly work on focal, but
  starting with jammy it won't unless at least two fingers are enrolled.

  Note that this is tested on a Dell Latitude 5521, but the issue should
  be the same with all Broadcom fingerprint readers using this library.

  Duplicate bug #1981974

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1956885/+subscriptions


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


[Desktop-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

2022-08-15 Thread Dustin Utecht
Tested it with another nuc (hp elitedesk 800 G1 Business PC) and have still the 
same issues..
Can't connect with any device, but i also get "nl80211" error.
It's quite weired that i get the same error on 2 different nuc's (from 2 
different brands).
Also i'm not sure how i can check if the "nl80211" error is the cause of my 
hotspot problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1972790

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.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/1972790/+subscriptions


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


[Desktop-packages] [Bug 1986522] [NEW] Using a Gio.DesktopAppinfo().launch with context freezes GJS

2022-08-15 Thread Sundeep
Public bug reported:

Creating a Gio.DesktopAppInfo for a desktopfile, then launching with an
app_launch context freezes GJS. Launching with context set to null
works. There is no debug information on the console.

Using Gtk4

Here is the relevant code-

let desktopFile = Gio.DesktopAppInfo.new('gnome-background-panel.desktop');
const context = Gdk.Display.get_default().get_app_launch_context();
context.set_timestamp(Gdk.CURRENT_TIME);
// Fix me, context in the following causes a crash;
desktopFile.launch([], context)

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1986522

Title:
  Using a Gio.DesktopAppinfo().launch with context freezes GJS

Status in gjs package in Ubuntu:
  New

Bug description:
  Creating a Gio.DesktopAppInfo for a desktopfile, then launching with
  an app_launch context freezes GJS. Launching with context set to null
  works. There is no debug information on the console.

  Using Gtk4

  Here is the relevant code-

  let desktopFile = Gio.DesktopAppInfo.new('gnome-background-panel.desktop');
  const context = Gdk.Display.get_default().get_app_launch_context();
  context.set_timestamp(Gdk.CURRENT_TIME);
  // Fix me, context in the following causes a crash;
  desktopFile.launch([], context)

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


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


[Desktop-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2022-08-15 Thread Dave Jones
** Description changed:

- On the hirsute Pi desktop, under a wayland session with the "full" KMS
- overlay enabled, and "kms-modifiers" present in the
- org.gnome.mutter/experimental-features, the body of a window containing
- an HTML renderer (e.g. help text or a login page) displays corruption.
+ On the jammy Pi desktop, under a wayland session, the body of a window
+ containing an HTML renderer (e.g. help text or a login page) displays
+ corruption.
  
  These reproduction cases may not be entirely reliable given that *some*
  pages appear to render correctly, but I'll include a couple in the hopes
  of making it reliably reproducible:
  
  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link
  
  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.
  
  Another reproduction case:
  
  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me
  
  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).
  
  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in the
  body of the window; the window decorations are unaffected. I'll attach a
  screenshot of the corrupted help window to illustrate.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1924251

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

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


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


[Desktop-packages] [Bug 1981927] Re: correct password occassionally not accepted on start up. Will usually work after several attempts and/or reboot.

2022-08-15 Thread Daniel van Vugt
Thanks. I can see the password failures in the log, with a few possible
causes:

Aug 11 22:12:19 fantome gdm-password][4421]: pam_unix(gdm-password:auth): check 
pass; user unknown
Aug 11 22:12:19 fantome gdm-password][4421]: pam_unix(gdm-password:auth): 
authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost=
Aug 11 22:12:21 fantome gnome-shell[2766]: JS WARNING: 
[resource:///org/gnome/shell/gdm/util.js 285]: reference to undefined property 
"_currentMessageExtraInterval"
Aug 11 22:12:23 fantome gdm-password][5711]: Unable to load file 
'/etc/gdm3/custom.conf': Key file contains line “O# GDM configuration 
storage” which is not a key-value pair, group, or comment

Mostly it sounds like /etc/gdm3/custom.conf contains an error?



** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1981927

Title:
  correct password occassionally not accepted on start up.  Will usually
  work after several attempts and/or reboot.

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 20.04
  3.36.8

  (I typed 'apt-cache policy pkgname' into terminal but the answer I
  received was: 'N: Unable to locate package pkgname')

  Correct password is not accepted until several attempts are made.

   The password is definitely correct.  Have verified this.  When this
  problem occurs, another problem also occurs, where the password
  displays without being concealed as it is typed.  After typing the
  same password in several times, it will work.  Rebooting also often
  seems to temporarily resolve the problem.  The issue comes up
  sporadically, perhaps once every twenty times I try to log into
  ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 17 10:42:54 2022
  InstallationDate: Installed on 2020-09-16 (669 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1973428] Re: Totem crashes when started (segmentation fault) in Ubuntu 22.04

2022-08-15 Thread Daniel van Vugt
This bug is closed. If you would like to discuss related issues then
please open a new bug by running:

  ubuntu-bug totem

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1973428

Title:
  Totem crashes when started (segmentation fault) in Ubuntu 22.04

Status in totem package in Ubuntu:
  Expired

Bug description:
  When I start totem (by clicking its icon in the dock or when I double click  
a video file or when I run it from CLI), it immediately crashes.
  This issue occurs since I upgraded from 21.10 to 22.04.

  When run from CLI with debug emssages activated, the following messages 
appear:
   $ G_MESSAGES_DEBUG=all totem
  (totem:1015458): GLib-GIO-DEBUG: 19:14:57.264: _g_io_module_get_default: 
Found default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’
  (totem:1015458): dconf-DEBUG: 19:14:57.264: watch_fast: "/org/gnome/Totem/" 
(establishing: 0, active: 0)
  Gtk-Message: 19:14:57.266: Failed to load module "xapp-gtk3-module"
  (totem:1015458): dconf-DEBUG: 19:14:57.267: watch_established: 
"/org/gnome/Totem/" (establishing: 1)
  (totem:1015458): GLib-GIO-DEBUG: 19:14:57.293: _g_io_module_get_default: 
Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
  (totem:1015458): GLib-DEBUG: 19:14:57.339: unsetenv() is not thread-safe and 
should not be used after threads are created
  (totem:1015458): Gtk-DEBUG: 19:14:57.339: Connecting to session manager
  (totem:1015458): Handy-DEBUG: 19:14:57.341: Trying to initialize portal
  (totem:1015458): dconf-DEBUG: 19:14:57.520: watch_fast: "/org/gnome/Totem/" 
(establishing: 0, active: 1)
  (totem:1015458): dconf-DEBUG: 19:14:57.520: watch_fast: 
"/org/gnome/desktop/lockdown/" (establishing: 0, active: 0)
  (totem:1015458): dconf-DEBUG: 19:14:57.520: watch_established: 
"/org/gnome/desktop/lockdown/" (establishing: 1)
  (totem:1015458): dconf-DEBUG: 19:14:57.636: watch_fast: 
"/org/gnome/desktop/thumbnailers/" (establishing: 0, active: 0)
  (totem:1015458): dconf-DEBUG: 19:14:57.636: watch_established: 
"/org/gnome/desktop/thumbnailers/" (establishing: 1)
  (totem:1015458): GLib-GIO-DEBUG: 19:14:57.639: Failed to initialize portal 
(GNetworkMonitorPortal) for gio-network-monitor: Not using portals
  (totem:1015458): GLib-GIO-DEBUG: 19:14:57.643: _g_io_module_get_default: 
Found default implementation networkmanager (GNetworkMonitorNM) for 
‘gio-network-monitor’
  (totem:1015458): dconf-DEBUG: 19:14:57.643: watch_fast: "/org/gnome/Totem/" 
(establishing: 0, active: 2)
  (totem:1015458): dconf-DEBUG: 19:14:57.643: unwatch_fast: "/org/gnome/Totem/" 
(active: 3, establishing: 0)
  (totem:1015458): GLib-GIO-DEBUG: 19:14:57.657: _g_io_module_get_default: 
Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’
  (totem:1015458): dconf-DEBUG: 19:14:57.744: change_fast
  (totem:1015458): dconf-DEBUG: 19:14:57.744: watch_fast: "/org/gnome/Totem/" 
(establishing: 0, active: 2)
  (totem:1015458): dconf-DEBUG: 19:14:57.744: unwatch_fast: "/org/gnome/Totem/" 
(active: 3, establishing: 0)
  (totem:1015458): dconf-DEBUG: 19:14:57.745: watch_fast: "/org/gnome/Totem/" 
(establishing: 0, active: 2)
  (totem:1015458): dconf-DEBUG: 19:14:57.753: watch_fast: "/org/gnome/Totem/" 
(establishing: 0, active: 3)
  (totem:1015458): dconf-DEBUG: 19:14:57.768: watch_fast: 
"/org/gnome/desktop/lockdown/" (establishing: 0, active: 1)
  (totem:1015458): Totem-DEBUG: 19:14:57.769: totem_playlist_add_one_mrl (): 
Akira (1988).mkv (null) (null) (null) 0 true
  (totem:1015458): Totem-DEBUG: 19:14:57.844: TotemGrilo: Pausing videos 
thumbnailing
  (totem:1015458): Totem-DEBUG: 19:14:57.889: Adding popup busy for reason 
opening file
  (totem:1015458): Totem-DEBUG: 19:14:57.889: emitting PlaybackStatus change
  (totem:1015458): Totem-DEBUG: 19:14:57.889: Not enabling offline save, as 
'file:///home/raffaele/Video/Film/Akira/Akira%20(1988).mkv' already in $HOME, 
and native
  (totem:1015458): Totem-DEBUG: 19:14:57.890: TotemGrilo: Pausing videos 
thumbnailing
  (totem:1015458): Totem-DEBUG: 19:14:57.890: TotemGrilo: Pausing videos 
thumbnailing
  (totem:1015458): Totem-DEBUG: 19:14:57.898: successfully acquired dbus name 
org.mpris.MediaPlayer2.totem
  (totem:1015458): GStreamer-CRITICAL **: 19:14:58.367: gst_caps_from_string: 
assertion 'string' failed
  (totem:1015458): GStreamer-CRITICAL **: 19:14:58.367: gst_pad_template_new: 
assertion 'caps != NULL' failed
  (totem:1015458): GStreamer-CRITICAL **: 19:14:58.367: gst_mini_object_unref: 
assertion 'mini_object != NULL' failed
  (totem:1015458): GStreamer-CRITICAL **: 19:14:58.367: 
gst_element_class_add_pad_template: assertion 'GST_IS_PAD_TEMPLATE (templ)' 
failed
  (totem:1015458): GStreamer-Video-CRITICAL **: 19:14:58.367: 
gst_video_decoder_init: assertion 'pad_template != NULL' failed
  (totem:1015458): GStreamer-WARNING **: 19:14:58.367: Element vaapidecode0 has 
an ALWAYS 

[Desktop-packages] [Bug 1986446] Re: Webkit appears garbled in Wayland sessions

2022-08-15 Thread Dave Jones
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251

I'm afraid this is a long-standing issue under KMS; duplicate of LP:
#1924251

** This bug has been marked a duplicate of bug 1924251
   Embedded browser display corruption under Wayland on Pi desktop

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1986446

Title:
  Webkit appears garbled in Wayland sessions

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  When using a wayland session, Webkit is garbled in all applications
  (including online-accounts) which makes it unusable. The expected
  result should be a correct and viewable webpage.

  Ubuntu 22.04.1 LTS
  Release:  22.04
  Installed: 2.36.4-0ubuntu0.22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gir1.2-javascriptcoregtk-4.0 2.36.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-1013.15-raspi 5.15.39
  Uname: Linux 5.15.0-1013-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 14 07:05:54 2022
  ImageMediaBuild: 20220419
  SourcePackage: webkit2gtk
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1986513] [NEW] Software & Updates doesn't handle sources files properly when an entry has options

2022-08-15 Thread Paddy Landau
Public bug reported:

— SYNOPSIS —

Software & Updates (software-properties-gtk) has a tab "Other Software"
that lists all entries in /etc/apt/sources.list and in
/etc/apt/sources.list.d/*.list

Some entries have an option in square brackets, e.g.:

deb [arch=amd64] ...

But, Software & Updates doesn't handle these options properly.

1. It removes the option if you edit the entry.
2. If the option contains "signed-by", Software & Updates doesn't even list the 
entry, and thus allows you to add a duplicate entry (normally prevented).

— EXAMPLES —

Example of point 1:

Consider Google Chrome:
deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main #Chrome

If you edit this entry in Software & Updates, it removes [arch=amd64].

The same applies to [trusted=yes].

Example of point 2:

Consider SpiderOakONE, which needs "signed-by".
deb [signed-by=/usr/share/keyrings/spideroakone.gpg] 
https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE

This also happens with combinations:
deb [arch=amd64 signed-by=/usr/share/keyrings/spideroakone.gpg] 
https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE

Software & Updates doesn't even display this entry. Thus, you can
manually re-add this deb, albeit without the signed-by option.

— MORE DETAIL —

Confusingly, you can add the option [arch=amd64] or [trusted=yes] (or
both) when you add an entry in Software & Updates, but if you then edit
the entry, Software & Updates removes the option.

— EXPECTED BEHAVIOUR —

Software & Updates should:

• Display all entries
• Preserve all options when editing an entry
• Allow you to add suitable options when adding an entry
• Allow you to edit options when editing an entry

— VERSIONS —

Ubuntu version:
Tested on Ubuntu 20.04.4 and Ubuntu 22.04.1

software-properties-gtk version:
0.99.9.8 (on Ubuntu 20.04)
0.99.22.3 (on Ubuntu 22.04)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.22.3
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 15 09:19:51 2022
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2022-05-05 (101 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
InterpreterPath: /usr/bin/python3.10
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Software & Updates doesn't handle sources files properly when an entry
  has options

Status in software-properties package in Ubuntu:
  New

Bug description:
  — SYNOPSIS —

  Software & Updates (software-properties-gtk) has a tab "Other
  Software" that lists all entries in /etc/apt/sources.list and in
  /etc/apt/sources.list.d/*.list

  Some entries have an option in square brackets, e.g.:

  deb [arch=amd64] ...

  But, Software & Updates doesn't handle these options properly.

  1. It removes the option if you edit the entry.
  2. If the option contains "signed-by", Software & Updates doesn't even list 
the entry, and thus allows you to add a duplicate entry (normally prevented).

  — EXAMPLES —

  Example of point 1:

  Consider Google Chrome:
  deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main #Chrome

  If you edit this entry in Software & Updates, it removes [arch=amd64].

  The same applies to [trusted=yes].

  Example of point 2:

  Consider SpiderOakONE, which needs "signed-by".
  deb [signed-by=/usr/share/keyrings/spideroakone.gpg] 
https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE

  This also happens with combinations:
  deb [arch=amd64 signed-by=/usr/share/keyrings/spideroakone.gpg] 
https://apt.spideroak.com/ubuntu/ release restricted #SpiderOakONE

  Software & Updates doesn't even display this entry. Thus, you can
  manually re-add this deb, albeit without the signed-by option.

  — MORE DETAIL —

  Confusingly, you can add the option [arch=amd64] or [trusted=yes] (or
  both) when you add an entry in Software & Updates, but if you then
  edit the entry, Software & Updates removes the option.

  — EXPECTED BEHAVIOUR —

  Software & Updates should:

  • Display all entries
  • Preserve all options when editing an entry
  • Allow you to add suitable options when adding an entry
  • Allow you to edit options when editing an 

[Desktop-packages] [Bug 1986168] Missing required logs.

2022-08-15 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1986168

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1986168

Title:
  Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS

Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  1. In 20.04 LTS I had configured the Marble Mouse by adding 39 conf
  etc according to
  https://help.ubuntu.com/community/Logitech_Marblemouse_USB

  2. On upgrade to 22.04.1 LTS, these no longer work. The edits etc are
  still in place but the Marble Mouse buttons I configured previously
  are not working. Expected behavior is they should still work.

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


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


[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock

2022-08-15 Thread Daniel van Vugt
** Summary changed:

- ubuntu dock bug
+ Can't click context menu items when they cover the dock

** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)

** Summary changed:

- Can't click context menu items when they cover the dock
+ Can't click context menu items when they cover the dock (in a Xorg session)

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

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

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper

2022-08-15 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1986450

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and
  then change back to 100%. That white vertical line will stay at the
  former 100% window size location until the Settings window is closed.
  It disappears when the Settings is closed.

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


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


[Desktop-packages] [Bug 1986168] Re: Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS

2022-08-15 Thread Daniel van Vugt
At a guess, you have a Xorg config file but are using Wayland by default
(like most users of 22.04). Please try selecting 'Ubuntu on Xorg' on the
login screen.


** Tags added: jammy

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

** Also affects: xserver-xorg-input-libinput (Ubuntu)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1986168

Title:
  Logitech Marble Mouse no longer works on upgrde to 22.04.1 LTS

Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  1. In 20.04 LTS I had configured the Marble Mouse by adding 39 conf
  etc according to
  https://help.ubuntu.com/community/Logitech_Marblemouse_USB

  2. On upgrade to 22.04.1 LTS, these no longer work. The edits etc are
  still in place but the Marble Mouse buttons I configured previously
  are not working. Expected behavior is they should still work.

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


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


[Desktop-packages] [Bug 1986373] Re: Xorg config logout when using wayland with multiple monitors

2022-08-15 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Tags added: multimonitor wayland wayland-session

** Summary changed:

- Xorg config logout  when using wayland with multiple monitors
+ Logout  when using wayland with multiple monitors

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

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

** Tags added: hybrid multigpu nouveau radeon

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1986373

Title:
  Logout  when using wayland with multiple monitors

Status in Ubuntu:
  Incomplete

Bug description:
  I have a 5 monitor setup. Below is the xrandr account of the monitors:
   xrandr --listmonitors
  Monitors: 5
   0: +*DisplayPort-0 1920/509x1080/286+0+1124  DisplayPort-0
   1: +HDMI-0 1920/477x1080/268+1920+1080  HDMI-0
   2: +DVI-1 1920/519x1200/324+3840+1110  DVI-1
   3: +DVI-I-1-1 1680/473x1050/296+3840+60  DVI-I-1-1
   4: +VGA-1-1 1920/521x1080/293+1920+0  VGA-1-1

  All works fine if Wayland is disabled in /etc/gd3/custom.conf but if it is 
the default enabled an attempt to adjust monitor layout or which is primary 
leads to a logout when apply is punched.
  lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  just upgraded from 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 12 14:33:16 2022
  DistUpgraded: 2022-08-12 10:35:15,953 DEBUG running apport_crash()
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03ea]
   NVIDIA Corporation G96C [GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. G96C [GeForce 9400 GT] 
[19da:2107]
  InstallationDate: Installed on 2018-07-21 (1482 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: MSI MS-7758
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=000141a2-0f41-4525-accb-1cd881fa7072 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (0 days ago)
  dmi.bios.date: 11/01/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G41 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd11/01/2013:br4.6:svnMSI:pnMS-7758:pvr3.0:rvnMSI:rnZ77A-G41(MS-7758):rvr3.0:cvnMSI:ct3:cvr3.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1986503] Re: Wrong glyph for greek 'ano teleia' U+0387

2022-08-15 Thread Michalis Kaloumenos
** Description changed:

  The Greek punctuation mark of 'ano teleia' (U+0387) is equivalent to the 
English semi colon.
- Windows fonts (such as Arial, Times New Roman, and Georgia) display the glyph 
correctly, that is the dot appears at the same height as the dot of the 
(english) semi colon, and the higher dot of the colon. However, ubuntu fonts 
such as Liberation Serif and Nimbus Roman, have a glyph where the dot is 
replaced significantly lower. It appears to me that U+0387 is the exact glyph 
as 'middle dot' (U+00B7)
+ Windows fonts (such as Arial, Times New Roman, and Georgia) display the glyph 
correctly, that is the dot appears at the same height as the dot of the 
(english) semi colon, and the higher dot of the colon. However, ubuntu fonts 
such as Liberation Serif and Nimbus Roman, have a glyph where the dot is 
wrongfully positioned significantly lower. It appears to me that U+0387 is the 
exact glyph as 'middle dot' (U+00B7)
  Depending on the system you use, here is the problem graphically ;:· (ano 
teleia in the end) against ;:· (middle dot at the end).
  
  If you read this post in a system with windows fonts the two characters
  above are visually different. With Ubuntu fonts, they appear to be the
  same.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsfonts in Ubuntu.
https://bugs.launchpad.net/bugs/1986503

Title:
  Wrong glyph for greek 'ano teleia' U+0387

Status in Ubuntu:
  New
Status in gsfonts package in Ubuntu:
  New
Status in liberation-fonts package in Ubuntu:
  New

Bug description:
  The Greek punctuation mark of 'ano teleia' (U+0387) is equivalent to the 
English semi colon.
  Windows fonts (such as Arial, Times New Roman, and Georgia) display the glyph 
correctly, that is the dot appears at the same height as the dot of the 
(english) semi colon, and the higher dot of the colon. However, ubuntu fonts 
such as Liberation Serif and Nimbus Roman, have a glyph where the dot is 
wrongfully positioned significantly lower. It appears to me that U+0387 is the 
exact glyph as 'middle dot' (U+00B7)
  Depending on the system you use, here is the problem graphically ;:· (ano 
teleia in the end) against ;:· (middle dot at the end).

  If you read this post in a system with windows fonts the two
  characters above are visually different. With Ubuntu fonts, they
  appear to be the same.

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


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


[Desktop-packages] [Bug 1985968] Re: Maximized windows often end up behind the dock on session unlock

2022-08-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508

Sounds like bug 1961508.

** This bug has been marked a duplicate of bug 1961508
   Dock displaying over window after resuming from blank screen

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1985968

Title:
  Maximized windows often end up behind the dock on session unlock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using the default Ubuntu 22.04 desktop on Wayland, with little tweaks.

  I have a bunch of maximized windows, two screens extended
  horizontally.

  Often when I unlock the session, one of the maximized windows will be
  maximized behind the dock. I have to un- and maximize them again to
  bring them back.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 12 12:51:09 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-29 (104 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


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

2022-08-15 Thread Daniel van Vugt
Thanks for the bug report. Please attach a video showing the problem.
The easiest way to do that is to press PrtScn.

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

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

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

Title:
  Horiontal nav flicks

Status in Ubuntu:
  Incomplete

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

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

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


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


[Desktop-packages] [Bug 1982472] Re: Support A+N platform

2022-08-15 Thread jeremyszu
https://github.com/tseliot/nvidia-settings/pull/14 for nvidia-settings
UI.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1982472

Title:
  Support A+N platform

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  The 'Power Saving Mode' of Nvidia app should change to ATI when the
  integrated graphic is Advanced Micro Devices.

  [Steps to reproduce]
  1. Install the OEM image
  2. Boot and log
  3. 'Dash' -> 'Nvidia Settings'
  4. Verify the 'PRIME Profiles'

  [Expected result]
  Nvidia (Performance Mode)
  Nvidia On-Demand
  AMD (Power Saving Mode)

  u@Thor-P3-AMD-2:~$ prime-select
  Usage: /usr/bin/prime-select nvidia|AMD|on-demand|query

  [Actual result]
  Nvidia (Performance Mode)
  Nvidia On-Demand
  Intel (Power Saving Mode)

  u@Thor-P3-AMD-2:~$ prime-select
  Usage: /usr/bin/prime-select nvidia|intel|on-demand|query

  [Failure rate]
  100%

  [Other Information]
  ubuntu 22.04
  nvidia-prime 0.8.17.1
  nvidia-settings 510.47.03-0ubuntu1
  nvidia-driver 510.73.05-0ubuntu0.22.04.1

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


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


[Desktop-packages] [Bug 1985869] Re: Unable to wake up screen when it sleeps. Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not foun

2022-08-15 Thread Daniel van Vugt
Sounds like a regression of bug 1967274 which was originally fixed in
mutter 42.1

** Tags added: matrox mgag200

** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2384
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2384

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2384
   Importance: Unknown
   Status: Unknown

** No longer affects: linux (Ubuntu)

** Summary changed:

- Unable to wake up screen when it sleeps. Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found and  Page flip discarded: CRTC property 
(GAMMA_LUT) not found
+ [mgag200] Unable to wake up screen when it sleeps. Failed to post KMS update: 
CRTC property (GAMMA_LUT) not found and  Page flip discarded: CRTC property 
(GAMMA_LUT) not found

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1985869

Title:
  [mgag200] Unable to wake up screen when it sleeps. Failed to post KMS
  update: CRTC property (GAMMA_LUT) not found and  Page flip discarded:
  CRTC property (GAMMA_LUT) not found

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  == ApportVersion =
  2.20.11-0ubuntu82.1

  == Architecture =
  amd64

  == CasperMD5CheckResult =
  pass

  == Date =
  Fri Aug 12 16:01:31 2022

  == Dependencies =
  accountsservice 22.07.5-2ubuntu1.3
  acl 2.3.1-1
  adduser 3.118ubuntu5
  adwaita-icon-theme 41.0-1ubuntu1
  alsa-topology-conf 1.2.5.1-2
  alsa-ucm-conf 1.2.6.3-1ubuntu1
  apg 2.2.3.dfsg.1-5build2
  apport 2.20.11-0ubuntu82.1
  apport-symptoms 0.24
  apt 2.4.6
  apt-utils 2.4.6
  aptdaemon 1.1.1+bzr982-0ubuntu39
  aptdaemon-data 1.1.1+bzr982-0ubuntu39
  aspell 0.60.8-4build1
  aspell-en 2018.04.16-0-1
  at-spi2-core 2.44.0-3
  avahi-daemon 0.8-5ubuntu5
  avahi-utils 0.8-5ubuntu5
  base-files 12ubuntu4.2
  bash 5.1-6ubuntu1
  bash-completion 1:2.11-5ubuntu1
  bind9-host 1:9.18.1-1ubuntu1.1
  bind9-libs 1:9.18.1-1ubuntu1.1
  bluez 5.64-0ubuntu1
  bolt 0.9.2-1
  bsdextrautils 2.37.2-4ubuntu3
  bubblewrap 0.6.1-1
  ca-certificates 20211016
  cheese-common 41.1-1build1
  colord 1.4.6-1
  colord-data 1.4.6-1
  coreutils 8.32-4.1ubuntu1
  cpp 4:11.2.0-1ubuntu1
  cpp-11 11.2.0-19ubuntu1
  cracklib-runtime 2.9.6-3.4build4
  cups-pk-helper 0.2.6-1ubuntu5

  [ 6902.723370] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7123.822417] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7123.823384] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7124.335913] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd service: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
net.reactivated.Fprint was not provided by any .service files

asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  [ 7180.309459] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7180.311605] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7218.558479] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7218.559502] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7244.319195] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7244.320182] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7295.446436] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7295.447812] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7573.588299] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7573.590411] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7574.868039] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd service: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
net.reactivated.Fprint was not provided by any .service files

asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  [ 7654.509594] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7654.510955] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7751.955703] ubuntu1 gnome-shell[2773]: Failed to 

[Desktop-packages] [Bug 1985089] Re: Resizing two edge tiled windows is laggy

2022-08-15 Thread Daniel van Vugt
** Tags added: performance

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1985089

Title:
  Resizing two edge tiled windows is laggy

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  Just to report an issue that other people have reported to GNOME and
  in Reddit, that seems to also affect Ubuntu 22.04.

  If you snap 2 windows side-by-side in Wayland and then try to resize
  them, it's very slow and uses a lot of memory.

  Check here for more details:
  - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246
  - 
https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/

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


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


[Desktop-packages] [Bug 1984456] Re: display resolution max is 1920x1080, video card supports higher resolution, would like 2560x1440

2022-08-15 Thread Daniel van Vugt
** Tags added: nouveau

** Summary changed:

- display resolution max is 1920x1080, video card supports higher resolution, 
would like 2560x1440
+ [nouveau] display resolution max is 1920x1080, video card supports higher 
resolution, would like 2560x1440

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1984456

Title:
  [nouveau] display resolution max is 1920x1080, video card supports
  higher resolution, would like 2560x1440

Status in linux package in Ubuntu:
  New

Bug description:
  Current wayland display resolution max is 1920x1080, video card
  supports higher resolution, would like 2560x1440

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-45.48-generic 5.15.39
  Uname: Linux 5.15.0-45-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: Wed Aug 10 13:32:12 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.34, 5.15.0-45-generic, x86_64: installed
   virtualbox/6.1.34, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Apple Inc. G96C [GeForce 9500 GT] [106b:00b3]
  InstallationDate: Installed on 2022-06-20 (51 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Apple Inc. MacPro3,1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash video=eDP-1:2560x1440@60 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/29/08
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MP31.88Z.006C.B05.0802291410
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42C88C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto1
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42C88C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMP31.88Z.006C.B05.0802291410:bd02/29/08:br0.1:svnAppleInc.:pnMacPro3,1:pvr1.0:rvnAppleInc.:rnMac-F42C88C8:rvrProto1:cvnAppleInc.:ct2:cvrMac-F42C88C8:skuSystemSKU#:
  dmi.product.family: MacPro
  dmi.product.name: MacPro3,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep

2022-08-15 Thread Daniel van Vugt
This bug is closed. Please use bug 1961508 instead.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1917939

Title:
  Windows maximise underneath dock after monitor sleep

Status in Dash to dock:
  New
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Under wayland on 21.04 windows keep maximising underneath the dock. So
  I can see icons "through" the dock, when I shouldn't. In the attached
  screenshot you can see Telegram showing through the dock.

  If I switch to the application in question, unmaximise and re-
  maximise, it goes back to maximising inside the usable area of my
  desktop.

  But when I suspend and resume, then login, I'm left with windows under
  the dock again. Never seen this under xorg. I only discovered I was in
  wayland when I tried to ALT+F2, R to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 19:21:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-11 (267 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+subscriptions


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


[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

2022-08-15 Thread Daniel van Vugt
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1370
   https://github.com/micheleg/dash-to-dock/issues/1370

** Also affects: dash-to-dock via
   https://github.com/micheleg/dash-to-dock/issues/1370
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1961508

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


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


[Desktop-packages] [Bug 1986503] Re: Wrong glyph for greek 'ano teleia' U+0387

2022-08-15 Thread Michalis Kaloumenos
** Also affects: liberation-fonts (Ubuntu)
   Importance: Undecided
   Status: New

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

** Tags added: fonts

** Tags added: glyphs

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsfonts in Ubuntu.
https://bugs.launchpad.net/bugs/1986503

Title:
  Wrong glyph for greek 'ano teleia' U+0387

Status in Ubuntu:
  New
Status in gsfonts package in Ubuntu:
  New
Status in liberation-fonts package in Ubuntu:
  New

Bug description:
  The Greek punctuation mark of 'ano teleia' (U+0387) is equivalent to the 
English semi colon.
  Windows fonts (such as Arial, Times New Roman, and Georgia) display the glyph 
correctly, that is the dot appears at the same height as the dot of the 
(english) semi colon, and the higher dot of the colon. However, ubuntu fonts 
such as Liberation Serif and Nimbus Roman, have a glyph where the dot is 
replaced significantly lower. It appears to me that U+0387 is the exact glyph 
as 'middle dot' (U+00B7)
  Depending on the system you use, here is the problem graphically ;:· (ano 
teleia in the end) against ;:· (middle dot at the end).

  If you read this post in a system with windows fonts the two
  characters above are visually different. With Ubuntu fonts, they
  appear to be the same.

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


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


[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi

2022-08-15 Thread Daniel van Vugt
It appears the fix only exists in 21.04 and later, of which only 22.04
is currently supported.

A fix has been requested for 20.04 but it seems nobody has had the time
yet.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1905519

Title:
  Syslog is flooded with Object St.Bin (0x565425162c80), has been
  already deallocated — impossible to set any property on it. This might
  be caused by the object having been destroyed from C code using
  something such as destroy(), dispose(), or remove() vfuncs.

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  The syslog is full of these messages, continuously written all day
  long

  Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has 
been already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 
0x56541fffb220 ==
  Nov 25 07:46:42 pc1 gnome-shell[2980]: #0   7ffddbfa1940 b   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 
(1839cb6a2420 @ 208)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 07:42:45 2020
  InstallationDate: Installed on 2014-06-03 (2366 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions


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


[Desktop-packages] [Bug 1980386] Re: `radeonsi_dri.so` driver missing on riscv64

2022-08-15 Thread Timo Aaltonen
Which version of mesa on focal is that? The current backport version is
from jammy and doesn't enable gallium for riscv64.

Radeonsi requires llvm.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1980386

Title:
  `radeonsi_dri.so` driver missing on riscv64

Status in llvm-toolchain-14 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-14 source package in Jammy:
  New
Status in mesa source package in Jammy:
  Confirmed
Status in llvm-toolchain-14 source package in Kinetic:
  New
Status in mesa source package in Kinetic:
  Confirmed

Bug description:
  The package is missing the `radeonsi` driver, with the reasoning that
  LLVM is not implemented on the architecture:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618

  That said, it works just fine on focal, where it is still enabled.
  Without this driver there's no way to use AMD graphics cards on
  RISC-V.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.1-1ubuntu2
  ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30
  Uname: Linux 5.15.0-1007-generic riscv64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  Date: Thu Jun 30 15:48:11 2022
  ProcCpuinfoMinimal:
   processor: 3
   hart : 4
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-14/+bug/1980386/+subscriptions


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