[Desktop-packages] [Bug 1988909] Re: Selected theme Yaru-dark losing selection in dconf

2022-09-06 Thread Marcos Alano
** Attachment removed: "Peek 2022-09-07 00-40.gif"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+attachment/5614188/+files/Peek%202022-09-07%2000-40.gif

** Attachment added: "A screencast showing the problem"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+attachment/5614189/+files/simplescreenrecorder-2022-09-07_00.52.42.webm

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

Title:
  Selected theme Yaru-dark losing selection in dconf

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

Bug description:
  Every time I go to Appearance the value for
  /org/gnome/desktop/interface/gtk-theme is reset back to "Yaru", even I
  selected the dark theme (Yaru-dark). The problem is that some apps (in
  my case Tilix) uses this GTK theme value and even all my applications
  are in dark mode the Tilix is in light mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~rc-1ubuntu1
  Uname: Linux 6.0.0-rc4 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  7 00:04:57 2022
  InstallationDate: Installed on 2021-11-26 (284 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+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 1988909] Re: Selected theme Yaru-dark losing selection in dconf

2022-09-06 Thread Marcos Alano
** Attachment added: "Peek 2022-09-07 00-40.gif"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+attachment/5614188/+files/Peek%202022-09-07%2000-40.gif

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

Title:
  Selected theme Yaru-dark losing selection in dconf

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

Bug description:
  Every time I go to Appearance the value for
  /org/gnome/desktop/interface/gtk-theme is reset back to "Yaru", even I
  selected the dark theme (Yaru-dark). The problem is that some apps (in
  my case Tilix) uses this GTK theme value and even all my applications
  are in dark mode the Tilix is in light mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~rc-1ubuntu1
  Uname: Linux 6.0.0-rc4 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  7 00:04:57 2022
  InstallationDate: Installed on 2021-11-26 (284 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+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 1988087] Re: GNOME Settings has two Screen Blank controls and only one of them works.

2022-09-06 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Confirmed => Fix Released

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

Title:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Fedora:
  Unknown

Bug description:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

  Expected

  Screen Blank controls should preserve the values you set them to.

  Actual

  One of the two Screen blank controls does not preserve the value that
  you set it to.

  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ gnome-control-center --version
  gnome-control-center 43.beta

  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2

  Reproducing

  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
  3. Change to another panel (tab) and change back to Power. (e.g. change to 
Audio then back to Power)
  4. Observe that your Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1988087/+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 1988909] Re: Selected theme Yaru-dark losing selection in dconf

2022-09-06 Thread Marcos Alano
It is fixed (until the next access to the tab) if I select the orange
(the default) color

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

Title:
  Selected theme Yaru-dark losing selection in dconf

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

Bug description:
  Every time I go to Appearance the value for
  /org/gnome/desktop/interface/gtk-theme is reset back to "Yaru", even I
  selected the dark theme (Yaru-dark). The problem is that some apps (in
  my case Tilix) uses this GTK theme value and even all my applications
  are in dark mode the Tilix is in light mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~rc-1ubuntu1
  Uname: Linux 6.0.0-rc4 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  7 00:04:57 2022
  InstallationDate: Installed on 2021-11-26 (284 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+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 1988909] [NEW] Selected theme Yaru-dark losing selection in dconf

2022-09-06 Thread Marcos Alano
Public bug reported:

Every time I go to Appearance the value for
/org/gnome/desktop/interface/gtk-theme is reset back to "Yaru", even I
selected the dark theme (Yaru-dark). The problem is that some apps (in
my case Tilix) uses this GTK theme value and even all my applications
are in dark mode the Tilix is in light mode.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-control-center 1:43~rc-1ubuntu1
Uname: Linux 6.0.0-rc4 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  7 00:04:57 2022
InstallationDate: Installed on 2021-11-26 (284 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

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


** Tags: amd64 apport-bug kinetic third-party-packages

** Attachment added: "Dark theme selected with Tilix in light theme"
   
https://bugs.launchpad.net/bugs/1988909/+attachment/5614180/+files/Screenshot%20from%202022-09-07%2000-13-24.png

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

Title:
  Selected theme Yaru-dark losing selection in dconf

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

Bug description:
  Every time I go to Appearance the value for
  /org/gnome/desktop/interface/gtk-theme is reset back to "Yaru", even I
  selected the dark theme (Yaru-dark). The problem is that some apps (in
  my case Tilix) uses this GTK theme value and even all my applications
  are in dark mode the Tilix is in light mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~rc-1ubuntu1
  Uname: Linux 6.0.0-rc4 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  7 00:04:57 2022
  InstallationDate: Installed on 2021-11-26 (284 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988909/+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 1988246] Re: Keeps reseting appearance to light mode theme every background-panel load

2022-09-06 Thread Augustin Berisa
There is being made mismatch somewhere between gtk3, gtk4 and gnome-
shell theme.

No extensions enabled.

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

Title:
  Keeps reseting appearance to light mode theme every background-panel
  load

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

Bug description:
  Steps

  1. Have dark mode enabled
  2. Open settings at background panel
  3. Shell theme is reset back to light theme

  It keeps resetting theme back to light one every time you open the
  panel which is unwanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988246/+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 1988246] Re: Keeps reseting appearance to light mode theme every background-panel load

2022-09-06 Thread Augustin Berisa
@jbicha That doesn't affect the misbehavior.

Another steps to reproduce

1. Set light theme in Appearance panel
2. Close Settings gnome-control-center
3. Enable dark mode in gnome-shell's aggregated menu
4. Open Appearance panel
5. GTK3 legacy and gnome-shell theme is always reset to light at this point.
6. Dark mode switch in aggregated menu is reset to light
7. Only GTK4 apps remained dark as expected since no action was taken by user.

$ dconf dump /org/gnome/desktop/interface/
[/]
clock-show-seconds=true
clock-show-weekday=true
color-scheme='prefer-dark'
cursor-theme='Yaru'
enable-animations=true
enable-hot-corners=true
font-hinting='slight'
gtk-enable-primary-paste=false
gtk-theme='Yaru-magenta'
icon-theme='Yaru-magenta'
text-scaling-factor=1.0
toolbar-detachable=true

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

Title:
  Keeps reseting appearance to light mode theme every background-panel
  load

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

Bug description:
  Steps

  1. Have dark mode enabled
  2. Open settings at background panel
  3. Shell theme is reset back to light theme

  It keeps resetting theme back to light one every time you open the
  panel which is unwanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988246/+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 1988906] [NEW] Night light and colour management has stopped working in 22.10

2022-09-06 Thread Daniel van Vugt
Public bug reported:

Night light and colour management has stopped working in 22.10, because
it's transitioning from the gnome-settings-daemon project into mutter.

** Affects: mutter (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: fixed-in-43.rc fixed-upstream kinetic

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

Title:
  Night light and colour management has stopped working in 22.10

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Night light and colour management has stopped working in 22.10,
  because it's transitioning from the gnome-settings-daemon project into
  mutter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1988906/+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 1988864] Re: Screen freezes after display turns on from standby

2022-09-06 Thread Daniel van Vugt
Thanks for the bug report.

Next time the bug happens, please:

1. Use the workaround to recover.

2. Run:

   journalctl -b0 > journal.txt

3. Attach the resulting text file here.


** Tags added: radeon

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

** Changed in: mutter (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/1988864

Title:
  Screen freezes after display turns on from standby

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  This happens after automatic Blank Screen about 25% of the time. Mouse
  cursor doesn't move and alt-tab doesn't work.

  Workaround: ctrl-alt-f3, ctrl-alt-f1, login screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 14:13:08 2022
  DistUpgraded: 2022-07-28 04:25:49,168 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon R7 Graphics] [1043:85cb]
  InstallationDate: Installed on 2020-06-25 (802 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=25ac8a19-c1fe-4cac-a26c-50c592bf9181 ro quiet splash 
video=HDMI-A-1:1920x1080M@72 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-07-28 (40 days ago)
  dmi.bios.date: 04/14/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3004:bd04/14/2017:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1988864/+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 1988885] Re: computer freezes on switching tabs

2022-09-06 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.


** Package changed: gnome-shell-extension-ubuntu-dock (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 gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/195

Title:
  computer freezes on switching tabs

Status in Ubuntu:
  Incomplete

Bug description:
  my computer is getting frozen when I switched between windows or tabs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
  Uname: Linux 5.4.0-97-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_97_110_generic_89
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  7 03:20:33 2022
  InstallationDate: Installed on 2019-10-09 (1063 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-10-08 (698 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/195/+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 1988859] Re: Constant short periodic loss of desktop

2022-09-06 Thread Daniel van Vugt
Thanks for the bug report.

The attached log seems to explain the problem perfectly:

[10185.511277] rpi4b gnome-shell[2551]: Failed to post KMS update: drmModeAddFB 
does not support format 'AR24' (0x34325241)
[10185.547140] rpi4b gnome-shell[2551]: Page flip discarded: drmModeAddFB does 
not support format 'AR24' (0x34325241)
[10185.547707] rpi4b gnome-shell[2551]: Failed to post KMS update: drmModeAddFB 
does not support format 'AR24' (0x34325241)
[10185.548506] rpi4b gnome-shell[2551]: Page flip discarded: drmModeAddFB does 
not support format 'AR24' (0x34325241)
[10185.549013] rpi4b gnome-shell[2551]: Failed to post KMS update: drmModeAddFB 
does not support format 'AR24' (0x34325241)
[10185.549464] rpi4b gnome-shell[2551]: Page flip discarded: drmModeAddFB does 
not support format 'AR24' (0x34325241)
[10185.558077] rpi4b gnome-shell[2551]: Failed to post KMS update: drmModeAddFB 
does not support format 'AR24' (0x34325241)

** Tags added: raspi raspi-gfx

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

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

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

** Summary changed:

- Constant short periodic loss of desktop
+ Constant short periodic loss of desktop [Failed to post KMS update: 
drmModeAddFB does not support format 'AR24' (0x34325241)]

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

Title:
  Constant short periodic loss of desktop [Failed to post KMS update:
  drmModeAddFB does not support format 'AR24' (0x34325241)]

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

Bug description:
  Every so often, the desktop will go black and then re appear on Ubuntu
  22.10 Wayland Session which should not be occurring (this does not
  happen on 22.04.) Note that only the cursor can be seen.

  Reporting this before release so that it can be patched for (at least)
  the RasPi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
  Uname: Linux 5.19.0-1001-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 16:10:37 2022
  DisplayManager: gdm3
  ImageMediaBuild: 20220826
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1988859/+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 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child

2022-09-06 Thread Daniel van Vugt
Also reported in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=2124341

And this upstream bug looks related:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5832

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5832
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5832

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell crashed with SIGABRT
  [Clutter:ERROR:../clutter/clutter/clutter-
  actor.c:11749:clutter_actor_destroy_all_children: assertion failed:
  (self->priv->n_children < prev_n_children)] in
  indicatorStatusIcon.js:317

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Fedora:
  Unknown

Bug description:
  After upgrading to kinetic gnome-shell is crashing on start when using
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  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.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 10:28:31 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (834 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+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 1988889] ProcCpuinfoMinimal.txt

2022-09-06 Thread Marcos Alano
apport information

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

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

Title:
  Screen blank timeout not adjustable

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

Bug description:
  I tried to adjust screen blank timeout in Power tab, but after I go to 
another tab and come back, the value is the same, 5 min. The same behavior of 
changing the value back occurs for "Power Mode" and "Power Button Behavior".
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-11-26 (284 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:43~rc-1ubuntu1
  PackageArchitecture: amd64
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags: third-party-packages kinetic
  Uname: Linux 6.0.0-rc4 x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199/+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 1988246] Re: Keeps reseting appearance to light mode theme every background-panel load

2022-09-06 Thread Jeremy Bicha
Here's a workaround that may help. Close your settings app then run
these commands in your terminal

gsettings reset org.gnome.desktop.interface gtk-theme
gsettings reset org.gnome.desktop.interface icon-theme

Then open the Settings app and set your preferred theme.

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

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

Title:
  Keeps reseting appearance to light mode theme every background-panel
  load

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

Bug description:
  Steps

  1. Have dark mode enabled
  2. Open settings at background panel
  3. Shell theme is reset back to light theme

  It keeps resetting theme back to light one every time you open the
  panel which is unwanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988246/+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 1988889] ProcEnviron.txt

2022-09-06 Thread Marcos Alano
apport information

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

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

Title:
  Screen blank timeout not adjustable

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

Bug description:
  I tried to adjust screen blank timeout in Power tab, but after I go to 
another tab and come back, the value is the same, 5 min. The same behavior of 
changing the value back occurs for "Power Mode" and "Power Button Behavior".
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-11-26 (284 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:43~rc-1ubuntu1
  PackageArchitecture: amd64
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags: third-party-packages kinetic
  Uname: Linux 6.0.0-rc4 x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199/+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 1988889] Dependencies.txt

2022-09-06 Thread Marcos Alano
apport information

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

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

Title:
  Screen blank timeout not adjustable

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

Bug description:
  I tried to adjust screen blank timeout in Power tab, but after I go to 
another tab and come back, the value is the same, 5 min. The same behavior of 
changing the value back occurs for "Power Mode" and "Power Button Behavior".
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-11-26 (284 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:43~rc-1ubuntu1
  PackageArchitecture: amd64
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags: third-party-packages kinetic
  Uname: Linux 6.0.0-rc4 x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199/+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 1988889] Re: Screen blank timeout not adjustable

2022-09-06 Thread Marcos Alano
Thanks. It fixed almost anything. Now just Power Mode > Balanced isn't
working (Power Save and Performance are being selected as showed by
"dconf watch /" result)

** Tags added: apport-collected kinetic third-party-packages

** Description changed:

- I tried to adjust screen blank timeout in Power tab, but after I go to
- another tab and come back, the value is the same, 5 min. The same
- behavior of changing the value back occurs for "Power Mode" and "Power
- Button Behavior".
+ I tried to adjust screen blank timeout in Power tab, but after I go to 
another tab and come back, the value is the same, 5 min. The same behavior of 
changing the value back occurs for "Power Mode" and "Power Button Behavior".
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.0-0ubuntu1
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2021-11-26 (284 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-control-center 1:43~rc-1ubuntu1
+ PackageArchitecture: amd64
+ RebootRequiredPkgs: Error: path contained symlinks.
+ Tags: third-party-packages kinetic
+ Uname: Linux 6.0.0-rc4 x86_64
+ UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
+ UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
+ _MarkForUpload: True
+ modified.conffile..etc.default.apport:
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
+ mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

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

Title:
  Screen blank timeout not adjustable

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

Bug description:
  I tried to adjust screen blank timeout in Power tab, but after I go to 
another tab and come back, the value is the same, 5 min. The same behavior of 
changing the value back occurs for "Power Mode" and "Power Button Behavior".
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-11-26 (284 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:43~rc-1ubuntu1
  PackageArchitecture: amd64
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags: third-party-packages kinetic
  Uname: Linux 6.0.0-rc4 x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199/+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 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child

2022-09-06 Thread Daniel van Vugt
** Bug watch added: Red Hat Bugzilla #2124341
   https://bugzilla.redhat.com/show_bug.cgi?id=2124341

** Also affects: gnome-shell-extension-appindicator (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=2124341
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell crashed with SIGABRT
  [Clutter:ERROR:../clutter/clutter/clutter-
  actor.c:11749:clutter_actor_destroy_all_children: assertion failed:
  (self->priv->n_children < prev_n_children)] in
  indicatorStatusIcon.js:317

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in gnome-shell-extension-appindicator package in Fedora:
  Unknown

Bug description:
  After upgrading to kinetic gnome-shell is crashing on start when using
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  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.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 10:28:31 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (834 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+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 1988889] Re: Screen blank timeout not adjustable

2022-09-06 Thread Jeremy Bicha
Please make sure you are running gnome-control-center 1:43~rc-1ubuntu1.
That update was pushed today and should fix this issue.

In the future, please use this command to report a bug like this:

ubuntu-bug gnome-control-center

It will provide additional info like the specific versions installed on
your computer and it helps people better handle your bug report.

For instance, you never said what version of Ubuntu you are using. If
you had used that command, it would have been more clear.

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

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

Title:
  Screen blank timeout not adjustable

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

Bug description:
  I tried to adjust screen blank timeout in Power tab, but after I go to
  another tab and come back, the value is the same, 5 min. The same
  behavior of changing the value back occurs for "Power Mode" and "Power
  Button Behavior".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199/+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 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace

2022-09-06 Thread Daniel van Vugt
** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5834
   Importance: Unknown
   Status: Unknown

** Project changed: mutter => gnome-shell

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [Wayland] Can not select JetBrains IntelliJ IDEA windows (including
  Android Studio) with mouse in workspace

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have 3 apps open in 1 workspace,
  When i press window key and i want to select app 2 or 3 with mouse, app 1 
shows up!
  I can only go to app 2 with [window + tab] or [alt + tab]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 11:05:02 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-25 (145 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1969574/+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 1871262] Re: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

2022-09-06 Thread Daniel van Vugt
** Summary changed:

- gnome-shell freezes/crashes with meta_window_set_stack_position_no_sync: 
assertion 'window->stack_position >= 0' failed
+ meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 
0' failed

** No longer affects: gnome-shell (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

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

Bug description:
  GNOME Shell-Message: 20:18:17.677: Telepathy is not available, chat 
integration will be disabled.
  Gjs-Message: 20:18:18.189: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: 
unreachable code after return statement
  Ubuntu AppIndicators-Message: 20:18:19.456: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.79/org/ayatana/NotificationItem/software_update_available
  Ubuntu AppIndicators-Message: 20:18:19.461: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/livepatch
  GNOME Shell-Message: 20:18:19.742: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation

  (gnome-shell:21601): mutter-CRITICAL **: 20:18:45.274:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

  Was the error I got after restarting Gnome after it froze when I
  closed Visual Studio Code but the right-click menu appeared for it
  after Ubuntu froze for a second because I had regions enabled on my
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Mon Apr  6 20:16:51 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1871262/+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 1988246] Re: Keeps reseting appearance to light mode theme every background-panel load

2022-09-06 Thread Augustin Berisa
Before unwanted reset:

```
$ dconf dump /org/gnome/desktop/interface/
[/]
clock-show-seconds=true
clock-show-weekday=true
color-scheme='prefer-dark'
cursor-theme='Yaru'
enable-animations=true
enable-hot-corners=true
font-hinting='slight'
gtk-enable-primary-paste=false
gtk-theme='Yaru-red-dark'
icon-theme='Yaru-red-dark'
text-scaling-factor=1.0
```

After opening Appearance panel which keeps showing Dark settings as set
yet it gets reset:

```
$ dconf dump /org/gnome/desktop/interface/
[/]
clock-show-seconds=true
clock-show-weekday=true
color-scheme='prefer-dark'
cursor-theme='Yaru'
enable-animations=true
enable-hot-corners=true
font-hinting='slight'
gtk-enable-primary-paste=false
gtk-theme='Yaru-red'
icon-theme='Yaru-red'
text-scaling-factor=1.0
```

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

Title:
  Keeps reseting appearance to light mode theme every background-panel
  load

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

Bug description:
  Steps

  1. Have dark mode enabled
  2. Open settings at background panel
  3. Shell theme is reset back to light theme

  It keeps resetting theme back to light one every time you open the
  panel which is unwanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988246/+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 1738774]

2022-09-06 Thread Vstuart-foote
(In reply to bugzilla2 from comment #47)
> And can you explain that sentence further:
> "The mechanism for "detection" of HiDPI is "thresholded" at 168 dpi."
> I'm not sure what that means.

See the source for CountDPIScaleFactor() [1]. It previously was a single
threshold of >168dpi; and that got changed to a mix of dpi and scale
factor for bug 100164 for non-macOS builds with [2]

So current thresholding is:

  nDPI > 216
 250 (so 2.5x)
  nDPI > 168
 200 (so 2.0x)
  nDPI > 120
 150 (so 1.5x)
  otherwise 
 100 (or unscaled)

IIUC macOS passes usable dpi details, so does not need the mixed dpi &
scale percentage.

Also the nDPI is not the actual hardware provided dpi, rather it is a
calculated dpi that the os/DE is reporting--e.g. on Windows the Custom
Scaling value, or with use of fractional scaling on your Linux DE.

=-ref-=
[1] 
https://opengrok.libreoffice.org/xref/core/vcl/source/window/window.cxx?a=true&r=1df81daa&h=924#919

[2] https://gerrit.libreoffice.org/c/core/+/30379/

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+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 1738774]

2022-09-06 Thread Bugzilla2-r
I did some comparisons between png and svg and Stuart is right, up to
150% the png looks better then the svg. But over 150% scale, the svg
looks dramatically better then the png. So can't we male SVG default
when scale-factor is over 150%?

Sure we can say: "you can switch it manually in Preferences", but thats
not "nice" for new Users that maybe have a first look into LibreOffice
(because maybe they want to change from Microsoft Office) and then say:
"oh my god, that looks terrible, not thanks, I'll stick to MSO. It may
take years for those ppl to make another try, if ever.

And I do believe, that there are even many longterm LibreOffice Users,
that might not know that they can "fix" ugly Icons on HiDPI Monitors by
swichtching Icon-Sets...


And can you explain that sentence further:
"The mechanism for "detection" of HiDPI is "thresholded" at 168 dpi."
I'm not sure what that means.

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+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 1988889] Re: Screen blank timeout not adjustable

2022-09-06 Thread Marcos Alano
I kept running the command "dconf watch /" and these options don't
change any configurations. The other options, that options working fine,
change the values correctly.

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

Title:
  Screen blank timeout not adjustable

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

Bug description:
  I tried to adjust screen blank timeout in Power tab, but after I go to
  another tab and come back, the value is the same, 5 min. The same
  behavior of changing the value back occurs for "Power Mode" and "Power
  Button Behavior".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199/+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 1988889] [NEW] Screen blank timeout not adjustable

2022-09-06 Thread Marcos Alano
Public bug reported:

I tried to adjust screen blank timeout in Power tab, but after I go to
another tab and come back, the value is the same, 5 min. The same
behavior of changing the value back occurs for "Power Mode" and "Power
Button Behavior".

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

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

Title:
  Screen blank timeout not adjustable

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

Bug description:
  I tried to adjust screen blank timeout in Power tab, but after I go to
  another tab and come back, the value is the same, 5 min. The same
  behavior of changing the value back occurs for "Power Mode" and "Power
  Button Behavior".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199/+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 1988230] Re: glib 2.73 breaks modemmanager

2022-09-06 Thread Bug Watch Updater
** Changed in: glib
   Status: Fix Released => New

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

Title:
  glib 2.73 breaks modemmanager

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  Triaged
Status in modemmanager package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Confirmed

Bug description:
  I'm filing this bug in case we want to fix it before letting glib 2.73
  in to kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1988230/+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 1988885] [NEW] computer freezes on switching tabs

2022-09-06 Thread Ghulam Dastgir
Public bug reported:

my computer is getting frozen when I switched between windows or tabs.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
Uname: Linux 5.4.0-97-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_97_110_generic_89
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  7 03:20:33 2022
InstallationDate: Installed on 2019-10-09 (1063 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to focal on 2020-10-08 (698 days ago)

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  computer freezes on switching tabs

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

Bug description:
  my computer is getting frozen when I switched between windows or tabs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
  Uname: Linux 5.4.0-97-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_97_110_generic_89
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  7 03:20:33 2022
  InstallationDate: Installed on 2019-10-09 (1063 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-10-08 (698 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/195/+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 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child

2022-09-06 Thread Ken VanDine
I've tried removing them all, and still seeing the crash.  Of interest
though, it looks like only some apps using the indicator are triggering
the crash.  For example, starting mattermost-desktop or discord triggers
the crash when it registers the appindicator.  But starting telegram-
desktop doesn't.  Perhaps something about the libappindicator being
utilized?  telegram-desktop isn't using the content snap.

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

Title:
  gnome-shell crashed with SIGABRT
  [Clutter:ERROR:../clutter/clutter/clutter-
  actor.c:11749:clutter_actor_destroy_all_children: assertion failed:
  (self->priv->n_children < prev_n_children)] in
  indicatorStatusIcon.js:317

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to kinetic gnome-shell is crashing on start when using
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  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.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 10:28:31 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (834 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+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 1988873] Re: Show notification when systemd-oomd forces apps to stop

2022-09-06 Thread Jeremy Bicha
** Description changed:

  Impact
  --
  Ubuntu Desktop 22.04 LTS includes a new feature where systemd-oomd is enabled 
by default to hopefully improve system responsiveness and act before the 
kernel's OOM killer goes into effect.
  See https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668
  
  However, users are never informed that their app or process has been
  forced to stop or why it was done. This is a common complaint.
  
  GNOME 43 includes a notification for this so we should backport that
- notification to Ubuntu 22.04 LTS.
+ notification to Ubuntu 22.04 LTS. This notification is provided by
+ gnome-settings-daemon so it only benefits Ubuntu Desktop and Ubuntu
+ Budgie.
  
  Test Case
  -
  TODO
  
  What Could Go Wrong
  ---
  TODO
  
  Other Info
  ---
  This adds translatable strings but translations won't be updated until the 
next language package update, scheduled for shortly before Ubuntu 22.04.2 is 
released (so approximately late January).
  
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/d1fe7167d4f496

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

Title:
  Show notification when systemd-oomd forces apps to stop

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Incomplete

Bug description:
  Impact
  --
  Ubuntu Desktop 22.04 LTS includes a new feature where systemd-oomd is enabled 
by default to hopefully improve system responsiveness and act before the 
kernel's OOM killer goes into effect.
  See https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

  However, users are never informed that their app or process has been
  forced to stop or why it was done. This is a common complaint.

  GNOME 43 includes a notification for this so we should backport that
  notification to Ubuntu 22.04 LTS. This notification is provided by
  gnome-settings-daemon so it only benefits Ubuntu Desktop and Ubuntu
  Budgie.

  Test Case
  -
  TODO

  What Could Go Wrong
  ---
  TODO

  Other Info
  ---
  This adds translatable strings but translations won't be updated until the 
next language package update, scheduled for shortly before Ubuntu 22.04.2 is 
released (so approximately late January).

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/d1fe7167d4f496

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1988873/+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 1988873] [NEW] Show notification when systemd-oomd forces apps to stop

2022-09-06 Thread Jeremy Bicha
Public bug reported:

Impact
--
Ubuntu Desktop 22.04 LTS includes a new feature where systemd-oomd is enabled 
by default to hopefully improve system responsiveness and act before the 
kernel's OOM killer goes into effect.
See https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

However, users are never informed that their app or process has been
forced to stop or why it was done. This is a common complaint.

GNOME 43 includes a notification for this so we should backport that
notification to Ubuntu 22.04 LTS.

Test Case
-
TODO

What Could Go Wrong
---
TODO

Other Info
---
This adds translatable strings but translations won't be updated until the next 
language package update, scheduled for shortly before Ubuntu 22.04.2 is 
released (so approximately late January).

https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/commit/d1fe7167d4f496

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: gnome-settings-daemon (Ubuntu Jammy)
 Importance: High
 Status: Incomplete


** Tags: jammy kinetic

** Also affects: gnome-settings-daemon (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: gnome-settings-daemon (Ubuntu Jammy)
   Status: New => Incomplete

** Changed in: gnome-settings-daemon (Ubuntu Jammy)
   Importance: Undecided => High

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

Title:
  Show notification when systemd-oomd forces apps to stop

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Incomplete

Bug description:
  Impact
  --
  Ubuntu Desktop 22.04 LTS includes a new feature where systemd-oomd is enabled 
by default to hopefully improve system responsiveness and act before the 
kernel's OOM killer goes into effect.
  See https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

  However, users are never informed that their app or process has been
  forced to stop or why it was done. This is a common complaint.

  GNOME 43 includes a notification for this so we should backport that
  notification to Ubuntu 22.04 LTS.

  Test Case
  -
  TODO

  What Could Go Wrong
  ---
  TODO

  Other Info
  ---
  This adds translatable strings but translations won't be updated until the 
next language package update, scheduled for shortly before Ubuntu 22.04.2 is 
released (so approximately late January).

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/d1fe7167d4f496

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1988873/+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 1984233] Re: Please remove nautilus extensions incompatible with Nautilus 43

2022-09-06 Thread Jeremy Bicha
** Changed in: nautilus (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Please remove nautilus extensions incompatible with Nautilus 43

Status in eiciel package in Ubuntu:
  Fix Released
Status in folder-color package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus-dropbox package in Ubuntu:
  Fix Released
Status in nautilus-filename-repairer package in Ubuntu:
  Fix Released
Status in nautilus-ideviceinfo package in Ubuntu:
  Fix Released
Status in nautilus-image-converter package in Ubuntu:
  Fix Released
Status in nautilus-share package in Ubuntu:
  Fix Released
Status in nautilus-wipe package in Ubuntu:
  Fix Released
Status in seahorse-nautilus package in Ubuntu:
  Fix Released

Bug description:
  nautilus python 4.0~alpha is a major API update along with nautilus 43
  which had a major API update.

  Please remove these extensions since they are currently incompatible
  with the Nautilus and nautilus-python versions we are including in
  Kinetic

  - eiciel -- Needs to be ported from GTK3
  Debian maintainer thinks the package is not worth keeping without the 
extension
  https://salsa.debian.org/debian/eiciel/-/merge_requests/2

  - folder-color -- Needs to be ported from GTK3 
https://github.com/costales/folder-color/issues/17
  Ubuntu-specific package

  - nautilus-dropbox -- Needs to be ported from GTK3
  https://github.com/dropbox/nautilus-dropbox/issues/101

  - nautilus-filename-repairer -- Needs to be ported from GTK3

  - nautilus-ideviceinfo -- Needs to be ported from GTK3
  Ubuntu-specific package

  - nautilus-image-converter -- Needs to be ported from GTK3
  Debian removal bug filed. Unmaintained in Debian or upstream

  - nautilus-share -- Needs to be ported from GTK3

  - nautilus-wipe -- Needs to be ported from GTK3

  - seahorse-nautilus -- Needs to be ported from GTK3

  Transition tracker
  --
  We are going to try to fix several of the other affected source packages (not 
listed above) to either drop their Nautilus extension or port them to work with 
Nautilus 43.

  https://people.canonical.com/~ubuntu-archive/transitions/html/auto-
  nautilus.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eiciel/+bug/1984233/+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 1987833] Re: xdg-desktop-portal bails if DISPLAY is not set

2022-09-06 Thread Michał Sawicz
Actually it's either DISPLAY or WAYLAND_DISPLAY that it expects, but
doesn't say so...

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: New => Invalid

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

Title:
  xdg-desktop-portal bails if DISPLAY is not set

Status in xdg-desktop-portal package in Ubuntu:
  Invalid

Bug description:
  When DISPLAY is not set (which would be the case for a Wayland-only
  session), xdg-desktop-portal bails with:

  > xdg-desktop-portal[500395]: Error: no DISPLAY environment variable
  specified

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1
  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
  Date: Fri Aug 26 13:09:33 2022
  InstallationDate: Installed on 2022-04-29 (118 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: xdg-desktop-portal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1987833/+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 1987523] Re: Pulsaudio crashes once BT microphone is connected

2022-09-06 Thread Jorge Merlino
This big is fixed in kinetic

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

** Changed in: pulseaudio (Ubuntu Jammy)
 Assignee: (unassigned) => Jorge Merlino (jorge-merlino)

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

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

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

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

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  New

Bug description:
  When I connect my BT headset with microphone and change profile to
  HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog
  reports:

  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

  I've identified the upstream fix for this:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

  I've built packages with the fix and can confirm that it does solve
  the problem. Packages are available at:

  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987523/+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 1988648] StacktraceSource.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1988648/+attachment/5614072/+files/StacktraceSource.txt

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

Title:
  gnome-software crashed with SIGABRT when clicking on the firefox snap

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Clicking on the Install tab followed by the Firefox snap to display
  more info, gnome-software immediately crashes without displaying more
  info.

  Clicking on an installed deb package like gnome-calculator sometimes
  the more info is displayed - sometimes it is briefly displayed before
  crashing again.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~rc-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep  3 21:04:41 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (38 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap43~rc-2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gs_utils_format_size ()
   ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988648/+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 1961545] Re: Gnome Software recognizes from a newer package of Discord that it is already installed. However, it shows the Remove button, when it should show an "Update" button

2022-09-06 Thread Seija K.
** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1961545/+attachment/5562379/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "Screenshot from 2022-02-20 23-02-26.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1961545/+attachment/5562378/+files/Screenshot%20from%202022-02-20%2023-02-26.png

** Information type changed from Public to Private

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

Title:
  Gnome Software recognizes from a newer package of Discord that it is
  already installed. However, it shows the Remove button, when it should
  show an "Update" button since the version number is higher than the
  one installed

Status in gnome-software package in Ubuntu:
  New

Bug description:
  This issue occurs whenever one downloads a .deb file that is an update
  for a currently installed package.

  Software will offer to remove the installed version instead of
  updating it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 20 23:07:21 2022
  InstallationDate: Installed on 2021-10-03 (141 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1961545/+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 1988648] Stacktrace.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988648/+attachment/5614071/+files/Stacktrace.txt

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

Title:
  gnome-software crashed with SIGABRT when clicking on the firefox snap

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Clicking on the Install tab followed by the Firefox snap to display
  more info, gnome-software immediately crashes without displaying more
  info.

  Clicking on an installed deb package like gnome-calculator sometimes
  the more info is displayed - sometimes it is briefly displayed before
  crashing again.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~rc-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep  3 21:04:41 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (38 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap43~rc-2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gs_utils_format_size ()
   ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988648/+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 1988648] Crash report cannot be processed

2022-09-06 Thread Apport retracing service
Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for dbus-user-session
no debug symbol package found for fwupd-signed
no debug symbol package found for gir1.2-atk-1.0
no debug symbol package found for gir1.2-freedesktop
no debug symbol package found for gir1.2-gdkpixbuf-2.0
no debug symbol package found for gir1.2-glib-2.0
no debug symbol package found for gir1.2-goa-1.0
no debug symbol package found for gir1.2-gtk-3.0
no debug symbol package found for gir1.2-handy-1
no debug symbol package found for gir1.2-harfbuzz-0.0
no debug symbol package found for gir1.2-packagekitglib-1.0
no debug symbol package found for gir1.2-pango-1.0
no debug symbol package found for libavahi-common-data
no debug symbol package found for libjpeg-turbo8
no debug symbol package found for libperl5.34
no debug symbol package found for perl
no debug symbol package found for perl-base
no debug symbol package found for policykit-1
no debug symbol package found for secureboot-db
no debug symbol package found for systemd-sysv
no debug symbol package found for tcl
no debug symbol package found for ubuntu-advantage-tools
no debug symbol package found for libjpeg-turbo8


Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!


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

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

Title:
  gnome-software crashed with SIGABRT when clicking on the firefox snap

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Clicking on the Install tab followed by the Firefox snap to display
  more info, gnome-software immediately crashes without displaying more
  info.

  Clicking on an installed deb package like gnome-calculator sometimes
  the more info is displayed - sometimes it is briefly displayed before
  crashing again.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~rc-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep  3 21:04:41 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (38 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap43~rc-2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gs_utils_format_size ()
   ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988648/+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 1988648] gnome-software crashed with SIGABRT when clicking on the firefox snap

2022-09-06 Thread Apport retracing service
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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

Title:
  gnome-software crashed with SIGABRT when clicking on the firefox snap

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Clicking on the Install tab followed by the Firefox snap to display
  more info, gnome-software immediately crashes without displaying more
  info.

  Clicking on an installed deb package like gnome-calculator sometimes
  the more info is displayed - sometimes it is briefly displayed before
  crashing again.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~rc-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep  3 21:04:41 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (38 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap43~rc-2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gs_utils_format_size ()
   ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988648/+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 1988648] ThreadStacktrace.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988648/+attachment/5614073/+files/ThreadStacktrace.txt

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

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

Title:
  gnome-software crashed with SIGABRT when clicking on the firefox snap

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Clicking on the Install tab followed by the Firefox snap to display
  more info, gnome-software immediately crashes without displaying more
  info.

  Clicking on an installed deb package like gnome-calculator sometimes
  the more info is displayed - sometimes it is briefly displayed before
  crashing again.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~rc-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep  3 21:04:41 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (38 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap43~rc-2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gs_utils_format_size ()
   ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988648/+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 1871262] Re: gnome-shell freezes/crashes with meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

2022-09-06 Thread Seija K.
** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871262/+attachment/5348228/+files/Dependencies.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871262/+attachment/5348229/+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/1871262

Title:
  gnome-shell freezes/crashes with
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  GNOME Shell-Message: 20:18:17.677: Telepathy is not available, chat 
integration will be disabled.
  Gjs-Message: 20:18:18.189: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: 
unreachable code after return statement
  Ubuntu AppIndicators-Message: 20:18:19.456: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.79/org/ayatana/NotificationItem/software_update_available
  Ubuntu AppIndicators-Message: 20:18:19.461: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/livepatch
  GNOME Shell-Message: 20:18:19.742: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation

  (gnome-shell:21601): mutter-CRITICAL **: 20:18:45.274:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

  Was the error I got after restarting Gnome after it froze when I
  closed Visual Studio Code but the right-click menu appeared for it
  after Ubuntu froze for a second because I had regions enabled on my
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Mon Apr  6 20:16:51 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1871262/+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 1958334] Re: Nautilus says "preparing" yet never shows the actual operation of emptying the trash, even when finished; the program just says "Preparing"

2022-09-06 Thread Seija K.
** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1958334/+attachment/322/+files/Dependencies.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1958334/+attachment/323/+files/ProcCpuinfoMinimal.txt

** Information type changed from Public to Private

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

Title:
  Nautilus says "preparing" yet never shows the actual operation of
  emptying the trash, even when finished; the program just says
  "Preparing"

Status in nautilus package in Ubuntu:
  New

Bug description:
  I should know what operations are going on, and the operation should
  not be stuck being listed as "preparing" perpetually, even when said
  task finished. This happens whenever I empty the Trash in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 19 00:18:15 2022
  GsettingsChanges:
   b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1038, 552)'
   b'org.gnome.nautilus.preferences' b'fts-enabled' b'false'
  InstallationDate: Installed on 2021-10-03 (108 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1958334/+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 1988864] [NEW] Screen freezes after display turns on from standby

2022-09-06 Thread user722
Public bug reported:

This happens after automatic Blank Screen about 25% of the time. Mouse
cursor doesn't move and alt-tab doesn't work.

Workaround: ctrl-alt-f3, ctrl-alt-f1, login screen appears.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 14:13:08 2022
DistUpgraded: 2022-07-28 04:25:49,168 DEBUG icon theme changed, re-reading
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon R7 Graphics] [1043:85cb]
InstallationDate: Installed on 2020-06-25 (802 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=25ac8a19-c1fe-4cac-a26c-50c592bf9181 ro quiet splash 
video=HDMI-A-1:1920x1080M@72 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-07-28 (40 days ago)
dmi.bios.date: 04/14/2017
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3004
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3004:bd04/14/2017:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze jammy ubuntu wayland-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/1988864

Title:
  Screen freezes after display turns on from standby

Status in xorg package in Ubuntu:
  New

Bug description:
  This happens after automatic Blank Screen about 25% of the time. Mouse
  cursor doesn't move and alt-tab doesn't work.

  Workaround: ctrl-alt-f3, ctrl-alt-f1, login screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 14:13:08 2022
  DistUpgraded: 2022-07-28 04:25:49,168 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon R7 Graphics] [1043:85cb]
  InstallationDate: Installed on 2020-06-25 (802 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=25ac8a19-c1fe-4cac-a26c-50c592bf9181 ro quiet splash 
video=HDMI-A-1:1920x1080M@72 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-07-28 (40

[Desktop-packages] [Bug 1987523] Re: Pulsaudio crashes once BT microphone is connected

2022-09-06 Thread Jorge Merlino
** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Jorge Merlino (jorge-merlino)

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

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I connect my BT headset with microphone and change profile to
  HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog
  reports:

  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

  I've identified the upstream fix for this:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

  I've built packages with the fix and can confirm that it does solve
  the problem. Packages are available at:

  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987523/+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 1988643] StacktraceSource.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1988643/+attachment/5614066/+files/StacktraceSource.txt

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 02:00:33 2022
  Disassembly: => 0x7f4e338e34f0:   Cannot access memory at address 
0x7f4e338e34f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1662228023', 
'--until=@1662228043'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/ibus-x11
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 
0x7f4e338e34f0
   PC (0x7f4e338e34f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-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: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988643] ThreadStacktrace.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988643/+attachment/5614067/+files/ThreadStacktrace.txt

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

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 02:00:33 2022
  Disassembly: => 0x7f4e338e34f0:   Cannot access memory at address 
0x7f4e338e34f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1662228023', 
'--until=@1662228043'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/ibus-x11
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 
0x7f4e338e34f0
   PC (0x7f4e338e34f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-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: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988643] Stacktrace.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988643/+attachment/5614065/+files/Stacktrace.txt

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 02:00:33 2022
  Disassembly: => 0x7f4e338e34f0:   Cannot access memory at address 
0x7f4e338e34f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1662228023', 
'--until=@1662228043'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/ibus-x11
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 
0x7f4e338e34f0
   PC (0x7f4e338e34f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-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: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988643] ibus-x11 crashed with SIGSEGV in g_closure_invoke()

2022-09-06 Thread Apport retracing service
StacktraceTop:
 ?? ()
 g_closure_invoke (closure=0x5585a8f5d740, return_value=0x0, n_param_values=2, 
param_values=0x7fffa8e38000, invocation_hint=0x7fffa8e37f80) at 
../../../gobject/gclosure.c:832
 signal_emit_unlocked_R.isra.0 (node=node@entry=0x5585a8e36990, 
detail=detail@entry=349, instance=instance@entry=0x5585a8e98840, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffa8e38000) at 
../../../gobject/gsignal.c:3796
 g_signal_emit_valist (instance=, signal_id=, 
detail=, var_args=var_args@entry=0x7fffa8e381c0) at 
../../../gobject/gsignal.c:3549
 g_signal_emit (instance=, signal_id=, 
detail=) at ../../../gobject/gsignal.c:3606

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 02:00:33 2022
  Disassembly: => 0x7f4e338e34f0:   Cannot access memory at address 
0x7f4e338e34f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1662228023', 
'--until=@1662228043'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/ibus-x11
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 
0x7f4e338e34f0
   PC (0x7f4e338e34f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-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: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988644] ThreadStacktrace.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988644/+attachment/5614070/+files/ThreadStacktrace.txt

** Tags added: apport-failed-retrace

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.39.90-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Fri Sep  2 15:34:33 2022
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  IpRoute:
   default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 
20600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 
metric 600
  JournalErrors: -- No entries --
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: network-manager
  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_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: N/A
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.39.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1988644] StacktraceSource.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1988644/+attachment/5614069/+files/StacktraceSource.txt

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.39.90-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Fri Sep  2 15:34:33 2022
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  IpRoute:
   default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 
20600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 
metric 600
  JournalErrors: -- No entries --
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: network-manager
  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_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: N/A
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.39.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1988644] Stacktrace.txt

2022-09-06 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988644/+attachment/5614068/+files/Stacktrace.txt

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.39.90-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Fri Sep  2 15:34:33 2022
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  IpRoute:
   default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 
20600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 
metric 600
  JournalErrors: -- No entries --
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: network-manager
  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_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: N/A
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.39.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1988644] NetworkManager crashed with SIGABRT in g_assertion_message_expr()

2022-09-06 Thread Apport retracing service
StacktraceTop:
 ?? () from /srv/vms/apport-sandbox-dir/Ubuntu 
22.10/amd64/report-sandbox/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7303.0
 ?? ()
 ?? ()
 ?? ()
 ?? () from /srv/vms/apport-sandbox-dir/Ubuntu 
22.10/amd64/report-sandbox/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7303.0

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.39.90-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Fri Sep  2 15:34:33 2022
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  IpRoute:
   default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 
20600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 
metric 600
  JournalErrors: -- No entries --
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: network-manager
  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_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: N/A
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.39.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1988859] [NEW] Constant short periodic loss of desktop

2022-09-06 Thread Dominic Parry
Public bug reported:

Every so often, the desktop will go black and then re appear on Ubuntu
22.10 Wayland Session which should not be occurring (this does not
happen on 22.04.) Note that only the cursor can be seen.

Reporting this before release so that it can be patched for (at least)
the RasPi.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
Uname: Linux 5.19.0-1001-raspi aarch64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.23.0-0ubuntu1
Architecture: arm64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 16:10:37 2022
DisplayManager: gdm3
ImageMediaBuild: 20220826
RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 arm64-image kinetic raspi-image wayland-session

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

Title:
  Constant short periodic loss of desktop

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Every so often, the desktop will go black and then re appear on Ubuntu
  22.10 Wayland Session which should not be occurring (this does not
  happen on 22.04.) Note that only the cursor can be seen.

  Reporting this before release so that it can be patched for (at least)
  the RasPi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8
  Uname: Linux 5.19.0-1001-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 16:10:37 2022
  DisplayManager: gdm3
  ImageMediaBuild: 20220826
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  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/1988859/+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 1987556] Re: Add a short alias (eg "gted") for gnome-text-editor

2022-09-06 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-text-editor - 42.2-1ubuntu2

---
gnome-text-editor (42.2-1ubuntu2) kinetic; urgency=medium

  * Add debian/links to install short gted alias (LP: #1987556)
  * Build-Depend on libpcre3-dev. This change should be dropped for 43

 -- Jeremy Bicha   Tue, 06 Sep 2022 09:31:39 -0400

** Changed in: gnome-text-editor (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Add a short alias (eg "gted") for gnome-text-editor

Status in GNOME Text Editor:
  Fix Released
Status in gnome-text-editor package in Ubuntu:
  Fix Released

Bug description:
  Unix pro users on the terminal emulator probably use vi, emacs or nano
  to edit plain text files. Those editors have all short binary names
  because it is a practical common UNIX practice to use short binary
  names for common usage patterns.

  With Ubuntu 22.10 gnome-text-editor is going to be the new default
  text editor instead of gedit. I used gedit quite often for editing
  files and "gedit" was as easy and fast to type as "vi" or "nano".

  gnome-text-editor is certainly not written for being invoked from the
  terminal but like gedit before it will be used a lot by Linux
  beginners for its ease of use (like notepad on Windows).

  Having a short alias name like e.g. "gted" by default would make it
  easy to invoke gnome-text-editor for those who don't know how to set
  aliases or edit the .bashrc. And having it set by default would help
  seeing it used in Ubuntu tutorials.

  Upstream is not willing to discuss the clunky binary name (tried to
  file a bug there to no avail) thus this would be a non intrusive
  downstream workaround.

  As Debian is more of a power user distribution and Ubuntu more
  beginner-centric, I decided to file the bug for Ubuntu only. I
  proposed "gted" because the full term doesn't seem to be commonly used
  in a UNIX context yet and the "ed" part is often used in a UNIX
  context to indicate a text editor ("ED", "sED", gEDit,...).

  1) System: Ubuntu 22.10 development version

  2) Package: gnome-text-editor 42.2

  3) What I expected to happen: a fast way to open the text editor that
  I am used to in gnome-terminal

  4) what happened instead: "gnome-text-editor filename"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-text-editor/+bug/1987556/+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 1987161] Re: 43: switching alert sounds doesn't persist after closing and reopening the app

2022-09-06 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:43~rc-1ubuntu1

---
gnome-control-center (1:43~rc-1ubuntu1) kinetic; urgency=medium

  * Merge with Debian
  * Refresh patches

gnome-control-center (1:43~rc-2) unstable; urgency=medium

  * New upstream release
- Fixes Screen Blank control (Closes: #1018672, LP: #1988087)
  * debian/control.in: Bump minimum meson to 0.57.0
  * Build against libsoup3 libraries
  * Drop sound patch: applied in new release

gnome-control-center (1:43~beta-4) unstable; urgency=medium

  * Cherry-pick patch to fix sound alert selection (LP: #1987161)
  * Recommend gnome-bluetooth-sendto

gnome-control-center (1:43~beta-3) unstable; urgency=medium

  * Add patch to disable new Device Security panel.
It's too technical and unhelpful currently (LP: #1987162)
You can get the same info by running
  fwupdmgr security
  * debian/control.in: Depend on webp-pixbuf-loader
- This is required to display several of the new GNOME 43
  wallpapers. Please log out and log back in for this feature
  to work fully.

 -- Jeremy Bicha   Tue, 06 Sep 2022 09:25:05 -0400

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  43: switching alert sounds doesn't persist after closing and reopening
  the app

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  The alert sound feature is broken. See
  https://launchpad.net/bugs/1987160

  The sound theme feature got worse in 43. In 43, GNOME changed their
  alert sounds. The alert sounds are provided directly and not as actual
  sound themes. I think the following bug was caused by an attempt to
  migrate users to the new alert sounds.

  I've reported this issue to GNOME.
  The chosen alert sound doesn't persist in the viewer.

  I'm filing this as a separate bug because this is a separate upstream
  issue than the other alert sound bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1987161/+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 1988087] Re: GNOME Settings has two Screen Blank controls and only one of them works.

2022-09-06 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:43~rc-1ubuntu1

---
gnome-control-center (1:43~rc-1ubuntu1) kinetic; urgency=medium

  * Merge with Debian
  * Refresh patches

gnome-control-center (1:43~rc-2) unstable; urgency=medium

  * New upstream release
- Fixes Screen Blank control (Closes: #1018672, LP: #1988087)
  * debian/control.in: Bump minimum meson to 0.57.0
  * Build against libsoup3 libraries
  * Drop sound patch: applied in new release

gnome-control-center (1:43~beta-4) unstable; urgency=medium

  * Cherry-pick patch to fix sound alert selection (LP: #1987161)
  * Recommend gnome-bluetooth-sendto

gnome-control-center (1:43~beta-3) unstable; urgency=medium

  * Add patch to disable new Device Security panel.
It's too technical and unhelpful currently (LP: #1987162)
You can get the same info by running
  fwupdmgr security
  * debian/control.in: Depend on webp-pixbuf-loader
- This is required to display several of the new GNOME 43
  wallpapers. Please log out and log back in for this feature
  to work fully.

 -- Jeremy Bicha   Tue, 06 Sep 2022 09:25:05 -0400

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Fedora:
  Unknown

Bug description:
  GNOME Settings has two Screen Blank controls and only one of them
  works.

  Expected

  Screen Blank controls should preserve the values you set them to.

  Actual

  One of the two Screen blank controls does not preserve the value that
  you set it to.

  Version Info
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ gnome-control-center --version
  gnome-control-center 43.beta

  $ dpkg -l gnome-control-center | tail -n 1 | awk '{print $3}'
  1:43~beta-1ubuntu2

  Reproducing

  1. Run gnome-control-center power
  2. Change "Screen Blank" from the current setting (e.g. 5 minutes) to a 
different value.
  3. Change to another panel (tab) and change back to Power. (e.g. change to 
Audio then back to Power)
  4. Observe that your Screen Blank setting has reverted to the prior value 
(e.g. if you set it to "never" it will return to 5 minutes).
  5. Change to the Privacy panel, then to the Screen panel.
  6. Change the setting for Blank Screen Display to a different value.
  7. Change to another panel and then back to Privacy->Screen.
  8. Your change to the value of Blank Screen Display will have been retained 
(will be the same as you set it a moment ago).
  9. Change to the Power panel and the Screen Blank setting that you selected 
will be displayed there too.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 29 15:14:39 2022
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1988087/+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 1988686] Re: Read failure Photo SD Memory Card in USB

2022-09-06 Thread Cliff Carson
Picture files on the SD Memory card can be access/view/copied from a
terminal window.

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

Title:
  Read failure Photo SD Memory Card in USB

Status in nautilus package in Ubuntu:
  New

Bug description:
  Tried to read my SD memory card in the USB slot.  Nautilus responded
  with message box "Force Close" or "Wait".  Nautilus is outputting the
  following messages to Syslog when trying to display the device.

  Sep  4 14:41:42 Desktopps nautilus[31175]: specified class size for type 
'NautilusXContentBar' is smaller than the parent type's 'GtkInfoBar' class size
  Sep  4 14:41:42 Desktopps nautilus[31175]: g_once_init_leave: assertion 
'result != 0' failed
  Sep  4 14:41:42 Desktopps nautilus[31175]: g_object_new_valist: assertion 
'G_TYPE_IS_OBJECT (object_type)' failed
  Sep  4 14:41:42 Desktopps nautilus[31175]: gtk_widget_show: assertion 
'GTK_IS_WIDGET (widget)' failed
  Sep  4 14:41:42 Desktopps nautilus[31175]: gtk_box_append: assertion 
'GTK_IS_WIDGET (child)' failed

  Able to read this memory card in a Ubuntu 22.04 system.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 15:08:36 2022
  InstallationDate: Installed on 2022-09-03 (1 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988686/+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 1988847] Re: Add a direct link to the irc support channel list

2022-09-06 Thread C de-Avillez
Marking as wishlist per request from OP on Libera

** Changed in: yelp (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Add a direct link to the irc support channel list

Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04.1 @ 6/9/2022

  [Current Case]

  When launching the gnome Yelp icon under category 'Get more
  help'/community support

  the user is forwarded to https://ubuntu.com/support/community-support

  and needs to click 4 times to actualy get to the irc channel list to
  get support

  
  [Wislist]

  Please add a more direct link towards the Ubuntu irc support channels

  from inside Yelp/get more help so the user can get a better support
  experience.

  The Yelp icon is on the Ubuntu-desktops dock by default, so this could
  benefit to a quick irc help

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 42.1-1
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 14:56:22 2022
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1988847/+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 1988583] Re: ubuntu 18.04 cups network printer not working

2022-09-06 Thread Terrence Buckey
added information, the gui is seeing a canon printer in one of the
"adds", it does not see any network printer if you you a find network
printer.

Using the "Add" at the top of the printer gui, I was able to add the
Canon printer, and printer.conf has all the info.

The gui adds a MG3600 printer instead of the Canon_MG3600_series that
the qt qpinfo sees.

Looks like none of the command line commands can be used to add default
printer which breaks my embedded qt app.

Thanks,

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

Title:
  ubuntu 18.04 cups network printer not working

Status in cups package in Ubuntu:
  New

Bug description:
  all debug info from the ubuntu cup help page looks correct except that
  none of the snmp command work.

   netstat -rn
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG0 0  0 wlo1
  10.0.0.0192.168.168.54  255.255.0.0 UG0 0  0 ppp0
  10.0.0.00.0.0.0 255.255.0.0 U 0 0  0 eno2
  66.196.209.178  192.168.1.254   255.255.255.255 UGH   0 0  0 wlo1
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 eno2
  172.16.0.0  192.168.168.54  255.255.0.0 UG0 0  0 ppp0
  192.0.2.1   0.0.0.0 255.255.255.255 UH0 0  0 ppp0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 wlo1
  192.168.1.254   0.0.0.0 255.255.255.255 UH0 0  0 wlo1
  tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 
1892.168.1.102
  ^C
  tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 
192.168.1.102
  PING 192.168.1.102 (192.168.1.102) 56(84) bytes of data.
  64 bytes from 192.168.1.102: icmp_seq=1 ttl=64 time=50.6 ms
  64 bytes from 192.168.1.102: icmp_seq=2 ttl=64 time=5.60 ms
  64 bytes from 192.168.1.102: icmp_seq=3 ttl=64 time=5.75 ms
  ^C
  --- 192.168.1.102 ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2003ms
  rtt min/avg/max/mdev = 5.603/20.676/50.675/21.212 ms
  tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ nmap 
192.168.1.102

  Starting Nmap 7.60 ( https://nmap.org ) at 2022-09-02 10:11 CDT
  Nmap scan report for 192.168.1.102
  Host is up (0.035s latency).
  Not shown: 996 closed ports
  PORTSTATE SERVICE
  80/tcp  open  http
  443/tcp open  https
  515/tcp open  printer
  631/tcp open  ipp

  lpinfo -v gives
  network ipp
  file cups-brf:/
  network https
  network beh
  serial serial:/dev/ttyS0?baud=115200
  serial serial:/dev/ttyS4?baud=115200
  serial serial:/dev/ttyUSB0?baud=230400
  serial serial:/dev/ttyUSB1?baud=230400
  serial serial:/dev/ttyUSB2?baud=230400
  network lpd
  network http
  direct hp
  network socket
  network ipps
  direct hpfax
  network 
dnssd://Canon%20MG3600%20series._ipp._tcp.local/?uuid=--1000-8000-F4A997389B3C
  network ipp://389B3C00.local:631/ipp/print
  network cnijbe2://Canon/?port=net&serial=F4-A9-97-38-9B-3C

  lpoptions -d Canon_MG3600_series
  device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ 
printer-info='Canon MG3600 series' printer-location 
printer-make-and-model='Canon MG3600 series' printer-type=83890204
  tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions
  device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ 
printer-info='Canon MG3600 series' printer-location 
printer-make-and-model='Canon MG3600 series' printer-type=83890204
  tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions -l
  lpoptions: Unable to get PPD file for Canon_MG3600_series: The printer or 
class does not exist.
  tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpq
  lpq: Error - no default destination available.
  tbuckley@tbuckley-OptiPlex-7070:/tmp$ 

  this use to work but now it seems that cups is not setting the default
  printer using lpoption or something is failing in the setup.

  This is happening on a product and on my person ubuntu 18.04 home
  machine

  Thanks,
  Terry

  972-814-9422(c)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.9
  ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-generic 5.4.195
  Uname: Linux 5.4.0-124-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  2 10:13:02 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+bison-elk-cougar-mlk+X53
  InstallationDate: Installed on 2019-10-16 (1051 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lpstat:
   device for

[Desktop-packages] [Bug 1988246] Re: Keeps reseting appearance to light mode theme every background-panel load

2022-09-06 Thread Jeremy Bicha
Could you paste the output of this command?

dconf dump /org/gnome/desktop/interface/

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

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

Title:
  Keeps reseting appearance to light mode theme every background-panel
  load

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

Bug description:
  Steps

  1. Have dark mode enabled
  2. Open settings at background panel
  3. Shell theme is reset back to light theme

  It keeps resetting theme back to light one every time you open the
  panel which is unwanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988246/+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 1988660] Re: snap doesn't map joystick buttons correctly

2022-09-06 Thread Carlos V
set 06 15:25:47 carlos-notebook gsd-power[2252]: Call to iio-proxy failed: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.136 was not 
provided by any .service files
set 06 15:25:47 carlos-notebook upowerd[1314]: treated changed event as add on 
/sys/devices/pci:00/:00:08.1/:03:00.4/usb3/3-2/3-2:1.0/bluetooth/hci0/hci0:1/0005:054C:09CC.0002/power_supply/sony_cont>
set 06 15:25:47 carlos-notebook audit[966]: USER_AVC pid=966 uid=102 
auid=4294967295 ses=4294967295 subj=? msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system" path="/org/freedesktop/UPower" 
interface=">
 exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
set 06 15:25:47 carlos-notebook audit: MAC_TASK_CONTEXTS 
subj_apparmor=unconfined
set 06 15:25:48 carlos-notebook kernel: audit: type=1107 
audit(1662470747.995:163): pid=966 uid=102 auid=4294967295 ses=4294967295 
subj=? msg='apparmor="DENIED" operation="dbus_signal"  bus="system" path="/org/>
 exe="/usr/bin/dbus-daemon" sauid=102 
hostname=? addr=? terminal=?'
set 06 15:25:48 carlos-notebook kernel: audit: type=1420 
audit(1662470747.995:164): subj_apparmor=unconfined

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

Title:
  snap doesn't map joystick buttons correctly

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I tested the deb version and works fine.

  Steps to reproduce the problem:
  1.Connect the PS4 joystick by Bluetooth in Linux
  2.Test mapping in a webpage like gamepad-tester.com
  3.Almost all buttons are incorrectly mapped

  Problem Description:
  The buttons of the joystick are incorrectly mapped in the browser and this 
makes impossible to play Stadia, even the right axis remain always pressed when 
you press R2 once, you can see the error by yourself at this short video: 
https://www.youtube.com/watch?v=VLPQkXyVAsM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1988660/+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 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace

2022-09-06 Thread Dmitry Batrak
As per the above request, I've created a new upstream ticket for this
problem - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5834

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5834
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5834

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

Title:
  [Wayland] Can not select JetBrains IntelliJ IDEA windows (including
  Android Studio) with mouse in workspace

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have 3 apps open in 1 workspace,
  When i press window key and i want to select app 2 or 3 with mouse, app 1 
shows up!
  I can only go to app 2 with [window + tab] or [alt + tab]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 11:05:02 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-25 (145 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969574/+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 1988807] Re: Certain Nautilus windows interfer with behaviour of "switch windows of an application"

2022-09-06 Thread Rasmus Blanck
** Description changed:

  Normally, tapping Alt + ` (or your favorite shortcut for "switch windows
  of an application") switches to the most recent window of the same
- application. However, when any Nautilus window has been opened using the
- dock context menu, Alt + ` instead switches to the most recent Nautilus
- window regardless of what application is currently in focus.
+ application. However, when any Nautilus window has been opened using a
+ shortcut in the dock context menu, Alt + ` instead switches to the most
+ recent Nautilus window regardless of what application is currently in
+ focus.
  
  Steps to reproduce:
  1) Open two terminal windows.
  2) Open a Nautilus window.
- 3) Open a second Nautilus window using the dock context menu.
+ 3) Open a second Nautilus window using a shortcut in the dock context menu.
  4) Switch to one of the terminal windows.
  5) Tap Alt + `
  
  Expected behaviour: Switch to the other terminal window.
  Observed behaviour: Switch to the first Nautilus window.
  
  This persists even if the second Nautilus window has been closed.
  Closing Nautilus entirely makes Alt + ` work as expected again. Note
  also that opening windows from the dock context menu has up until
  recently caused Nautilus to crash (Bug #1934579).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.2-0ubuntu1
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 09:08:08 2022
  InstallationDate: Installed on 2020-01-10 (969 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (134 days ago)
  usr_lib_nautilus:
-  evince42.3-0ubuntu2
-  file-roller   3.42.0-1
-  nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
-  nautilus-share0.7.3-2ubuntu6
+  evince42.3-0ubuntu2
+  file-roller   3.42.0-1
+  nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
+  nautilus-share0.7.3-2ubuntu6

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

Title:
  Certain Nautilus windows interfer with behaviour of "switch windows of
  an application"

Status in nautilus package in Ubuntu:
  New

Bug description:
  Normally, tapping Alt + ` (or your favorite shortcut for "switch
  windows of an application") switches to the most recent window of the
  same application. However, when any Nautilus window has been opened
  using a shortcut in the dock context menu, Alt + ` instead switches to
  the most recent Nautilus window regardless of what application is
  currently in focus.

  Steps to reproduce:
  1) Open two terminal windows.
  2) Open a Nautilus window.
  3) Open a second Nautilus window using a shortcut in the dock context menu.
  4) Switch to one of the terminal windows.
  5) Tap Alt + `

  Expected behaviour: Switch to the other terminal window.
  Observed behaviour: Switch to the first Nautilus window.

  This persists even if the second Nautilus window has been closed.
  Closing Nautilus entirely makes Alt + ` work as expected again. Note
  also that opening windows from the dock context menu has up until
  recently caused Nautilus to crash (Bug #1934579).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.2-0ubuntu1
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 09:08:08 2022
  InstallationDate: Installed on 2020-01-10 (969 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (134 days ago)
  usr_lib_nautilus:
   evince42.3-0ubuntu2
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988807/+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 1987161] Re: 43: switching alert sounds doesn't persist after closing and reopening the app

2022-09-06 Thread Jeremy Bicha
** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  43: switching alert sounds doesn't persist after closing and reopening
  the app

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  The alert sound feature is broken. See
  https://launchpad.net/bugs/1987160

  The sound theme feature got worse in 43. In 43, GNOME changed their
  alert sounds. The alert sounds are provided directly and not as actual
  sound themes. I think the following bug was caused by an attempt to
  migrate users to the new alert sounds.

  I've reported this issue to GNOME.
  The chosen alert sound doesn't persist in the viewer.

  I'm filing this as a separate bug because this is a separate upstream
  issue than the other alert sound bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1987161/+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 1988847] Re: Add a direct link to the irc support channel list

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

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

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

Title:
  Add a direct link to the irc support channel list

Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04.1 @ 6/9/2022

  [Current Case]

  When launching the gnome Yelp icon under category 'Get more
  help'/community support

  the user is forwarded to https://ubuntu.com/support/community-support

  and needs to click 4 times to actualy get to the irc channel list to
  get support

  
  [Wislist]

  Please add a more direct link towards the Ubuntu irc support channels

  from inside Yelp/get more help so the user can get a better support
  experience.

  The Yelp icon is on the Ubuntu-desktops dock by default, so this could
  benefit to a quick irc help

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 42.1-1
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 14:56:22 2022
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1988847/+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 1988847] [NEW] Add a direct link to the irc support channel list

2022-09-06 Thread lotuspsychje
Public bug reported:

Ubuntu 22.04.1 @ 6/9/2022

[Current Case]

When launching the gnome Yelp icon under category 'Get more
help'/community support

the user is forwarded to https://ubuntu.com/support/community-support

and needs to click 4 times to actualy get to the irc channel list to get
support


[Wislist]

Please add a more direct link towards the Ubuntu irc support channels

from inside Yelp/get more help so the user can get a better support
experience.

The Yelp icon is on the Ubuntu-desktops dock by default, so this could
benefit to a quick irc help

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: yelp 42.1-1
Uname: Linux 5.17.7-051707-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 14:56:22 2022
SourcePackage: yelp
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: yelp (Ubuntu)
 Importance: Undecided
 Status: Confirmed


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

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

Title:
  Add a direct link to the irc support channel list

Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04.1 @ 6/9/2022

  [Current Case]

  When launching the gnome Yelp icon under category 'Get more
  help'/community support

  the user is forwarded to https://ubuntu.com/support/community-support

  and needs to click 4 times to actualy get to the irc channel list to
  get support

  
  [Wislist]

  Please add a more direct link towards the Ubuntu irc support channels

  from inside Yelp/get more help so the user can get a better support
  experience.

  The Yelp icon is on the Ubuntu-desktops dock by default, so this could
  benefit to a quick irc help

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 42.1-1
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 14:56:22 2022
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1988847/+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 1980839] Re: thunderbird -compose returns error since the 102 snap update?

2022-09-06 Thread gnubug
There seems to be a similar bug the other way around:
https://askubuntu.com/questions/1426478/snap-firefox-is-already-running-
but-is-not-responding

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

Title:
  thunderbird -compose returns error since the 102 snap update?

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04,
  it is no longer possible to open mailto links from the firefox snap in
  thunderbird. When clicking a mailto link in the firefox 102.0.1 snap,
  thunderbird returns the following error message: "Thunderbird is
  already running, but is not responding. To use Thunderbird, you must
  first close the existing Thunderbird process, restart your device, or
  use a different profile." The issue appears related to the thunderbird
  update as there was no issue opening links in the previous 91 version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 1988842] [NEW] [NUC11PAHi5, Realtek ALC256, Analog audio 3.5mmnot listed in Ubuntu GUI audio settings

2022-09-06 Thread Mattias Andersson
Public bug reported:

It is posible to apply "workaround" by adding options snd-hda-intel
model=dell-headset-multi in a -cong file in  /etc/modprobe.d/ then
restart.

Hardware is Intel NUC gen 11 and it has been out for over a year,
perhaps it is a good idea that a more permanent fix i being pushed in to
wherever it is required. Unfortunatly I do not have the competence to
solve this but it would make sense to make it work "out of the box" if
possible.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mattias 923 F pulseaudio
 /dev/snd/pcmC0D0c:   mattias 923 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 13:32:58 2022
InstallationDate: Installed on 2022-08-30 (6 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mattias 923 F pulseaudio
 /dev/snd/pcmC0D0c:   mattias 923 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [NUC11PAHi5, Realtek ALC256, Black Headphone Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2022
dmi.bios.release: 0.46
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PATGL357.0046.2022.0608.1909
dmi.board.name: NUC11PABi5
dmi.board.vendor: Intel Corporation
dmi.board.version: K90634-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.1
dmi.modalias: 
dmi:bvnIntelCorp.:bvrPATGL357.0046.2022.0608.1909:bd06/08/2022:br0.46:efr3.1:svnIntel(R)ClientSystems:pnNUC11PAHi5:pvrM15533-303:rvnIntelCorporation:rnNUC11PABi5:rvrK90634-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC11PAHi5000:
dmi.product.family: PA
dmi.product.name: NUC11PAHi5
dmi.product.sku: RNUC11PAHi5000
dmi.product.version: M15533-303
dmi.sys.vendor: Intel(R) Client Systems

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

** Summary changed:

- [NUC11PAHi5, Realtek ALC256, BAnalog audio not listes in GUI settings
+ [NUC11PAHi5, Realtek ALC256, Analog audio 3.5mmnot listed in Ubuntu GUI audio 
settings

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

Title:
  [NUC11PAHi5, Realtek ALC256, Analog audio 3.5mmnot listed in Ubuntu
  GUI audio settings

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It is posible to apply "workaround" by adding options snd-hda-intel
  model=dell-headset-multi in a -cong file in  /etc/modprobe.d/ then
  restart.

  Hardware is Intel NUC gen 11 and it has been out for over a year,
  perhaps it is a good idea that a more permanent fix i being pushed in
  to wherever it is required. Unfortunatly I do not have the competence
  to solve this but it would make sense to make it work "out of the box"
  if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mattias 923 F pulseaudio
   /dev/snd/pcmC0D0c:   mattias 923 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 13:32:58 2022
  InstallationDate: Installed on 2022-08-30 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mattias 923 F pulseaudio
   /dev/snd/pcmC0D0c:   mattias 923 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [NUC11PAHi5, Realtek ALC256, Black Headphone Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2022
  dmi.bios.release: 0.46
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PATGL357.0046.2022.0608.1909
  dmi.board.name: NUC

[Desktop-packages] [Bug 1988660] Re: snap doesn't map joystick buttons correctly

2022-09-06 Thread Nathan Teodosio
Can you attach Chromium's stderr and the journalctl output?

** Tags added: snap

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

Title:
  snap doesn't map joystick buttons correctly

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I tested the deb version and works fine.

  Steps to reproduce the problem:
  1.Connect the PS4 joystick by Bluetooth in Linux
  2.Test mapping in a webpage like gamepad-tester.com
  3.Almost all buttons are incorrectly mapped

  Problem Description:
  The buttons of the joystick are incorrectly mapped in the browser and this 
makes impossible to play Stadia, even the right axis remain always pressed when 
you press R2 once, you can see the error by yourself at this short video: 
https://www.youtube.com/watch?v=VLPQkXyVAsM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1988660/+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 1855711] Re: Add keyboard navigation to desktop icons

2022-09-06 Thread Sergio Costas
Oh... :-(

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

Title:
  Add keyboard navigation to desktop icons

Status in gnome-shell-extension-desktop-icons:
  New
Status in Gnome Shell Extension Desktop Icons Ng:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Pressing tab does not allow the user to select UI elements. If tab is
  pressed "Activities" should be selected. Left or right arrow to select
  items on Activities bar. If tab is pressed again, select top icon on
  Dock. Press down arrow to navigate down the dock. Press enter to start
  app. If tab is pressed instead of enter, Desktop icons should be
  selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1855711/+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 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

2022-09-06 Thread Sebastien Bacher
-updates is recommended and enabled by default, those are stable serie
bugfixes, I'm unsure why it got disabled on your installation. Closing
the bug since that was not a problem in the package

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of archives.
  After this operation, 16,0 MB of additional disk space will be

[Desktop-packages] [Bug 1988825] Re: [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01

2022-09-06 Thread Daniel van Vugt
Being machine-specific means this is almost certainly a kernel bug.

** Summary changed:

- Cannot turn Bluetooth on in Ubuntu 22.04.01
+ [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01

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

** Summary changed:

- [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01
+ [mt7921e] Cannot turn Bluetooth on in Ubuntu 22.04.01

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

Title:
  [mt7921e] Cannot turn Bluetooth on in Ubuntu 22.04.01

Status in linux package in Ubuntu:
  New

Bug description:
  The steps:

  * Going to settings -> Bluetooth
  * Turn Bluetooth on. Seems to stay on, but can't connect anything to it
  * Go to another place in Settings, go back to Bluetooth
  * Result: Bluetooth is turned off

  Thank you!
  Alex

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 11:52:13 2022
  InstallationDate: Installed on 2022-06-16 (81 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  InterestingModules: bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: GV301RE.313
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GV301RE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: ROG Flow X13
  dmi.product.name: ROG Flow X13 GV301RE_GV301RE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988825/+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 1988825] [NEW] Cannot turn Bluetooth on in Ubuntu 22.04.01

2022-09-06 Thread Alexandru Bolboaca
Public bug reported:

The steps:

* Going to settings -> Bluetooth
* Turn Bluetooth on. Seems to stay on, but can't connect anything to it
* Go to another place in Settings, go back to Bluetooth
* Result: Bluetooth is turned off

Thank you!
Alex

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 11:52:13 2022
InstallationDate: Installed on 2022-06-16 (81 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
InterestingModules: bnep btusb bluetooth
MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: GV301RE.313
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GV301RE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.8
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
dmi.product.family: ROG Flow X13
dmi.product.name: ROG Flow X13 GV301RE_GV301RE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

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


** Tags: amd64 apport-bug jammy

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

Title:
  Cannot turn Bluetooth on in Ubuntu 22.04.01

Status in bluez package in Ubuntu:
  New

Bug description:
  The steps:

  * Going to settings -> Bluetooth
  * Turn Bluetooth on. Seems to stay on, but can't connect anything to it
  * Go to another place in Settings, go back to Bluetooth
  * Result: Bluetooth is turned off

  Thank you!
  Alex

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 11:52:13 2022
  InstallationDate: Installed on 2022-06-16 (81 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  InterestingModules: bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: GV301RE.313
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GV301RE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: ROG Flow X13
  dmi.product.name: ROG Flow X13 GV301RE_GV301RE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988825/+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 1761532] Re: nautilus crashed with SIGSEGV in nautilus_query_matches_string()

2022-09-06 Thread Daniel van Vugt
** Changed in: nautilus (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  nautilus crashed with SIGSEGV in nautilus_query_matches_string()

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Nautilus error

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 10:38:47 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'238'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x543+95+55'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-11 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_PE:es
   PATH=(custom, user)
   LANG=es_PE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x5611943fb070 :
cmpq   $0x0,0x18(%rdi)
   PC (0x5611943fb070) ok
   source "$0x0" ok
   destination "0x18(%rdi)" (0x0018) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_query_matches_string ()
   ()
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   start_thread (arg=0x7f62f70c5700) at pthread_create.c:463
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: nautilus crashed with SIGSEGV in nautilus_query_matches_string()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1761532/+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 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing

2022-09-06 Thread Dean Kiss
I can confirm i have the same issue (22.04). I have  Tweaks -> Windows -> Focus 
on Hover set. When i close a window with GUI (click X) the window underneath 
(the X button) gets brought over the top of all others. I note that using Xorg 
or X11 is a workaround but for some reason gdm3 is breaking my DisplayLink so 
i'm stuck using Wayland.
A fix for this would be great, both behaviours are annnoying!
thanks

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

Title:
  gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have set gnome to "focus on hover", i.e. focus follows mouse. If I
  alt-tab to bring a window to the front but the mouse is over another
  window, then the hovered-over window will reclaim focus and the window
  I raised will typically get covered up again.

  In previous gnome versions, if I explicitly focussed a window via
  keyboard shortcuts, it remained focussed and I think this is the
  preferred behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 11:35:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-17 (33 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1969602/+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 1848951] Re: High CPU when just moving the mouse

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-upstream

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

Title:
  High CPU when just moving the mouse

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1848951/+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 1911921] Re: auto-move-windows extension crashes gnome-shell with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_

2022-09-06 Thread Daniel van Vugt
** Changed in: gnome-shell-extensions (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  auto-move-windows extension crashes gnome-shell with SIGABRT in
  src/core/workspace.c:375:meta_workspace_add_window: assertion failed:
  (g_list_find (workspace->mru_list, window) == NULL)

Status in Mutter:
  Unknown
Status in gnome-shell-extensions package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes when auto-move-windows extension is used with
  windows that want to be on all workspaces (like Chrome PiP).

  https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97
  https://gitlab.gnome.org/GNOME/mutter/-/issues/992

  [Test Plan]

  1. Install gnome-shell-extensions

  2. Open the 'Extensions' app and enable auto-move-windows.

  3. Configure auto-move-windows with a rule for Chrome/Chromium.

  4. Open Chrome/Chromium and point it at a simple video like from
  https://download.blender.org/peach/bigbuckbunny_movies/ or
  https://download.blender.org/demo/movies/BBB/

  5. Set the Chrome tab playing the video to PiP mode.

  Expect: No crashes and the video moves to an external window.

  [Where problems could occur]

  Changing mutter's window management code always brings risk of
  regression to the GNOME desktop.

  [Other Info]

  As in bug 1864052, putting a Chrome video into PiP mode crashes gnome-
  shell, although this time, in a different location.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6
  Uname: Linux 5.10.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jan 15 16:04:30 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-03-14 (1037 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-7.so.0
   () at /lib/x86_64-linux-gnu/libmutter-7.so.0
   meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1911921/+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 1951599] Re: gnome-shell logs errors when ejecting SD card

2022-09-06 Thread Daniel van Vugt
** No longer affects: gnome-shell-extension-dashtodock (Ubuntu)

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

Title:
  gnome-shell logs errors when ejecting SD card

Status in OEM Priority Project:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  When I click eject SD card in Files(nautilus), I found the gnome-shell
  reported some crash logs.

  [ Test case ]

  - Mount a device
  - Eject the device
  - No errors should be shown and the device re-mountable

  [ Regression Potential ]

  Devices could be leaked if gc doesn't work as expected

  
  ---

  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object 
.Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already 
deallocated — impossible to emit any signal 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 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object 
Gio.Settings (0x55a9db521970), has been already deallocated — impossible to 
access it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack 
trace for context 0x55a9d8a00120 ==
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0   
7ffc0b63cc20 b   resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 
@ 149)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1   
55a9d8f150b0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 
69)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2   
55a9d8f15018 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 
25)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3   
7ffc0b63d8c0 b   self-hosted:850 (1ec3f0b2a650 @ 454)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1951599/+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 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions

2022-09-06 Thread Daniel van Vugt
** Changed in: xorg-server (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Nvidia driver installed but X apps are using software rendering
  (LLVMpipe) in Wayland sessions

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xwayland package in Ubuntu:
  Fix Released

Bug description:
  Nvidia driver installed but X apps are using software rendering
  (LLVMpipe) in Wayland sessions.

  I am using kernel parameter nvidia-drm.modeset=1, which is required to
  get the "Ubuntu on Wayland" option. But after logging in I see:

  $ glxinfo | grep OpenGL
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 19.0.1
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  $ es2_info | grep ^GL
  GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1
  GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nvidia-driver-418 418.56-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  Date: Sun Apr  7 17:26:07 2019
  InstallationDate: Installed on 2018-12-04 (124 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: nvidia-graphics-drivers-418
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1823516/+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 1947149] Re: Dock auto-hide off but hidden on screen unlock

2022-09-06 Thread Daniel van Vugt
** No longer affects: gnome-shell-extension-dashtodock (Ubuntu)

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

Title:
  Dock auto-hide off but hidden on screen unlock

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

Bug description:
  When the dock is set to "Auto-hide the Dock" = Off, the dock will un-
  hide when logging on. Both on boot and after locking the user. This
  causes any open full-screen windows to move and resize as needed.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 21.10
  Release:  21.10
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  gnome-shell-extension-ubuntu-dock:
    Installed: 70~ubuntu3
    Candidate: 70~ubuntu3
    Version table:
   *** 70~ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu impish/main i386 Packages
  100 /var/lib/dpkg/status
  3) What you expected to happen
  The dock to start displayed (un-hidden) as per the settings. And not move.
  4) What happened instead
  The dock appears from the left, as if hidden.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1947149/+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 1826056] Re: Desktop context: Keep aligned, Organize desktop by name missing

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-upstream

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

Title:
  Desktop context: Keep aligned, Organize desktop by name missing

Status in gnome-shell-extension-desktop-icons:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  After upgrading from 18.10 to 19.04 the desktop context menu no longer
  contains the choices:

  Keep aligned
  Organize desktop by name

  These were very useful to me. I would like them to be restored.

  Ubuntu 19.04, 64bit
  Gnome 3.32.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1826056/+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 1919972] Re: Icon grid flashes briefly before the spring animation

2022-09-06 Thread Daniel van Vugt
** No longer affects: gnome-shell-extension-dashtodock (Ubuntu)

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

Title:
  Icon grid flashes briefly before the spring animation

Status in Dash to dock:
  Fix Released
Status in GNOME Shell:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  When clicking 'Show Applications', the icon grid flashes up briefly
  before vanishing again and the spring animation reveals it properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1919972/+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 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-in-42.1
** Tags added: fixed-in-gtk-3.24.35

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

Title:
  All the windows and the desktop icons disappear constantly after
  setting Scaling to 300%

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Summary
  ===

  Device with nvidia GPU, using proprietary drivers, wayland activated
  by default.

  By default, the scaling is set to 200% (the screen is UHD). If
  selecting 300%, all the windows close down, as well as the desktop
  icons (Home) as long as the mouse cursor is in the way.

  To fix the issue, one has to open the Display Settings (while making
  sure the mouse cursor is never above any of the Settings windows!),
  then set Scaling back to 200% using the keyboard.

  This problem does not happen in X11, and does not happen in Wayland if
  I select 100%, 200% or even 400% scaling!

  Steps to reproduce
  ==

  - Install 22.04 beta, selecting "install third party software" to make sure 
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
  - After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE 
should return `wayland`)
  - Go to Settings > Display, select 300% scaling, then press Apply

  Expected result
  ===

  The scaling is set to 300% and user can keep using the device.

  Actual result
  =

  The scaling is set to 300% and all the windows are shut down. If user
  tries to reopen a window (e.g. Terminal), it is shut down immediately
  if the mouse cursor is hovering it. The desktop icons keep
  disappearing and reappearing for as long as the mouse cursor is
  hovering the background.

  The only way to stop this is to go back to Settings > Display, and,
  using the keyboard, set the scaling back to 200%.

  Information
  ===

  Version:  Ubuntu Jammy Jellyfish (development branch) [Beta image]
  Release:  22.04

  Device: Dell Precision 7760 with Nvidia GPU
  CID: 202103-28858

  Third party software installed during installation

  Wayland in use.

  ii  linux-generic-hwe-20.045.15.0.23.25   
 amd64Complete Generic Linux kernel and headers
  ii  linux-headers-5.15.0-235.15.0-23.23   
 all  Header files related to Linux kernel version 5.15.0
  ii  linux-headers-5.15.0-23-generic5.15.0-23.23   
 amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
  ii  linux-headers-generic-hwe-20.045.15.0.23.25   
 amd64Generic Linux kernel headers
  ii  linux-image-5.15.0-23-generic  5.15.0-23.23   
 amd64Signed kernel image generic
  ii  linux-image-generic-hwe-20.04  5.15.0.23.25   
 amd64Generic Linux kernel image
  ii  linux-modules-5.15.0-23-generic5.15.0-23.23   
 amd64Linux kernel extra modules for version 5.15.0 on 64 bit 
x86 SMP
  ii  linux-modules-extra-5.15.0-23-generic  5.15.0-23.23   
 amd64Linux kernel extra modules for version 5.15.0 on 64 bit 
x86 SMP
  ii  linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 
 amd64Linux kernel nvidia modules for version 5.15.0-23
  ii  linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 
 amd64Extra drivers for nvidia-510 for the generic-hwe-20.04 
flavour
  ii  linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 
 amd64Linux kernel nvidia modules for version 5.15.0-23 
(objects)
  ii  linux-signatures-nvidia-5.15.0-23-generic  5.15.0-23.23+1 
 amd64Linux kernel signatures for nvidia modules for version 
5.15.0-23-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 10:24:25 2022
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 

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

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

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

** Tags added: patch

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  New

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

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

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

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

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


-- 
Mailing list: https://launchpad.net/~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 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen

2022-09-06 Thread Daniel van Vugt
Fixed in focal updates and all later releases.

** Changed in: xorg-server (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  forced software cursor with PageFlip enabled triggers artifacts on
  screen

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  The following Xorg configuration triggers faulty behaviour, like
  blinking cursor, corrupt graphics around it etc.:

1 Section "Device"
2   Identifier "graphicsdriver"
3   Driver  "modesetting"
4   Option "SWCursor" "true"
5   #Option "PageFlip" "off"
6   #Option "AccelMethod" "none"
7 EndSection

  Either switching SWCursor to false or uncommenting line 5 or 6 makes the 
issue disappear.
  Disabling accelleration is naturally the least recommended way of resolving 
the issue.
  As far as I've analyzed Xorg's source code shipped with 20.04, I can see that 
https://gitlab.freedesktop.org/xorg/xserver/commit/0aaac8d783e78c040a70a55ba8d67809abd7e625
  which should probably automatically handle the issue (haven't tried to build 
with those changes yet) is not included. If it ever should be in (as it looks 
like a workaround only), reamains an open question.

  I am not entirely sure which package to attach this bug to, Xorg seems
  the most viable at the moment. My reason for the uncertainty
  originates from the fact, that I have also tested other distros, e.g.
  SuSE tumbleweed (build from this week, exact versions to be added if
  needed) with KDE plasma, which happens to reproduce the bug only with
  OpenGL set as compositor's backend; XRender operates perfectly fine
  there; hence it is a bit unclear to me which compoment is the "owning
  interface" and which one is actually buggy, be it Xorg, mesa or
  compositor; please reassign the bug accordingly if needed.

  My plan for the nearest future is to verify whether the aforementioned
  change actually circumvents the issue. If anything else should be
  looked at to fix the problem, I am open for suggestions.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:41:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1b7a03b4-95ff-4d1b-9897-848a0dc6f8b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1870512/+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 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

2022-09-06 Thread Daniel van Vugt
Fixed in Ubuntu 22.04 and later.

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

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

Title:
  pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from
  pa_x11_wrapper_unref()

Status in X.Org X server:
  Fix Released
Status in libx11 package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584

  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  Uname: Linux 5.13.13-xanmod1-cacule x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anasc  1719 F pulseaudio
   /dev/snd/pcmC0D0p:   anasc  1719 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Aug 28 21:00:59 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-08-26 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  SegvAnalysis:
   Segfault happened at: 0x7fbcc9d6a8a4 :  mov%edx,0x4(%rax)
   PC (0x7fbcc9d6a8a4) ok
   source "%edx" ok
   destination "0x4(%rax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6
   XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
   pa_x11_wrapper_unref () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
   module_x11_publish_LTX_pa__done () from 
/usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
  Title: pulseaudio crashed with SIGSEGV in XFreeGC()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/05/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.36
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 5SU52EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1941962/+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 1951599] Re: gnome-shell logs errors when ejecting SD card

2022-09-06 Thread Daniel van Vugt
dashtodock is no longer in the Ubuntu archive.

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
   Status: Fix Committed => Won't Fix

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

Title:
  gnome-shell logs errors when ejecting SD card

Status in OEM Priority Project:
  Fix Released
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Won't Fix
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  When I click eject SD card in Files(nautilus), I found the gnome-shell
  reported some crash logs.

  [ Test case ]

  - Mount a device
  - Eject the device
  - No errors should be shown and the device re-mountable

  [ Regression Potential ]

  Devices could be leaked if gc doesn't work as expected

  
  ---

  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object 
.Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already 
deallocated — impossible to emit any signal 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 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object 
Gio.Settings (0x55a9db521970), has been already deallocated — impossible to 
access it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack 
trace for context 0x55a9d8a00120 ==
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0   
7ffc0b63cc20 b   resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 
@ 149)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1   
55a9d8f150b0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 
69)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2   
55a9d8f15018 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 
25)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3   
7ffc0b63d8c0 b   self-hosted:850 (1ec3f0b2a650 @ 454)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1951599/+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 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace

2022-09-06 Thread Daniel van Vugt
Let's assume this is not fixed still and that
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5395 was a different
problem.

Anyone still experiencing this bug, please report it upstream and then
tell us the new issue ID.

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: mutter (Ubuntu)
   Status: Fix Released => Confirmed

** No longer affects: mutter (Ubuntu Jammy)

** Tags removed: fixed-in-42.1 fixed-upstream

** No longer affects: gnome-shell

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Incomplete

** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5395
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5395

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

Title:
  [Wayland] Can not select JetBrains IntelliJ IDEA windows (including
  Android Studio) with mouse in workspace

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have 3 apps open in 1 workspace,
  When i press window key and i want to select app 2 or 3 with mouse, app 1 
shows up!
  I can only go to app 2 with [window + tab] or [alt + tab]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 11:05:02 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-25 (145 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969574/+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 1855711] Re: Add keyboard navigation to desktop icons

2022-09-06 Thread Daniel van Vugt
It looks like we forgot to get version 47 into Ubuntu 22.10 before
feature freeze :(

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

Title:
  Add keyboard navigation to desktop icons

Status in gnome-shell-extension-desktop-icons:
  New
Status in Gnome Shell Extension Desktop Icons Ng:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Pressing tab does not allow the user to select UI elements. If tab is
  pressed "Activities" should be selected. Left or right arrow to select
  items on Activities bar. If tab is pressed again, select top icon on
  Dock. Press down arrow to navigate down the dock. Press enter to start
  app. If tab is pressed instead of enter, Desktop icons should be
  selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1855711/+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 1976204] Re: Screen freeze and high CPU when a second monitor of different scaling factor is attached (but only if DING is active)

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-upstream

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

Title:
  Screen freeze and high CPU when a second monitor of different scaling
  factor is attached (but only if DING is active)

Status in Mutter:
  New
Status in OEM Priority Project:
  Fix Committed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in gnome-shell-extension-desktop-icons-ng source package in Jammy:
  Fix Released

Bug description:
  [Summary]
  The system will run into freeze if I connect the external monitor through 
DP/HDMI with dongle DA310 or Docking WD19TB

  Per further check, it will freeze only if the built-in and external
  display has different scale factors.

  [Steps to reproduce]
  1. Attact DA310 or WD19TB to DUT
  2. Cold Boot into OS
  3. Plug the DP/HDMI cable to DA310 or WD19TB
  4. Check the external monitor has signal
  5. Click keyboard or move mouse to check system can work well

  [Expected result]
  System won't be freeze with external monitor.

  [Actual result]
  Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse
  don't work during the screen freeze.
  It can be recovered after unplug the external monitor sometime.

  [gnome-shell stack trace]
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.

  This system is using OLED (3456x2160) panel, and I can't reproduce
  this issue on FHD panel.

  [What could go wrong]
  This 2 line bugfix maximizes the desktop icons window avoiding an infinite 
loop. This is a workaround for an apparent bug in mutter but fixing mutter is 
much more complicated.

  The Desktop Icons NG GNOME Shell extension is enabled by default on
  Ubuntu 22.04 LTS so a bug here could make desktops unusable.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-17 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  Package: gnome-shell 42.1-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-s

[Desktop-packages] [Bug 1761374] Re: Scrolling the app grid incurs very high CPU usage

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-in-43
** Tags added: fixed-in-43.beta

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Scrolling the app grid incurs very high CPU usage

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/174

  Scrolling the app grid incurs very high CPU usage. On an i7-7700
  desktop it uses 47% CPU (compared to 17% to display a maximized
  glxgears).

  I imagine most machines can't scroll the app grid smoothly. It doesn't
  appear smooth on this machine so I would look at the CPU usage problem
  first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1761374/+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 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages()

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-in-43.0
** Tags added: fixed-in-43.rc

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_context_terminate(context=0x0) from process_ice_messages()

Status in GNOME Shell:
  New
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  The error occurred when I ran apt update/upgrade in a terminal window
  after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 09:03:52 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'hu')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-initial-setup']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-02-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 41.3-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-9.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_context_terminate()
  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/gnome-shell/+bug/1959937/+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 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-in-43
** Tags added: fixed-in-43.rc

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

Title:
  gnome-shell 42 leaks tens of megabytes with every screenshot

Status in GNOME Shell:
  Unknown
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gjs source package in Jammy:
  Fix Released
Status in gnome-shell source package in Jammy:
  Triaged

Bug description:
  [Impact]

  gnome-shell's memory usage grows by tens of megabytes with every
  screenshot. A few screenshots make it 100MB larger and a few dozen
  screenshots make it 1GB larger.

  [Test Plan for GNOME Shell Fix]

  TODO

  [Test Plan for GJS Fix]

  1. Log into gnome-shell.

  2. Measure its real memory usage:

     grep RSS /proc/`pidof gnome-shell`/status

  3. Take 20 full screen screenshots by pressing PrtScn each time. No
  need to save them anywhere.

  4. Measure the memory usage again.

  Expected: Memory usage grows a little but growth does not exceed a few
  hundred megabytes. It should level off after a while and sometimes
  even shrink due to garbage collection.

  Observed: Memory usage grows without bounds, easily exceeding 1GB
  after about 20 screenshots (depending on screen resolution). It never
  shrinks significantly.

  [Where problems could occur]

  Since the fix affects GJS, problems could occur in any part of gnome-
  shell.

  [Other Info]

  This leak requires multiple fixes to minimize the memory usage. For
  the moment we are only aiming to fix the main GJS portion of the bug
  that allows memory usage to exceed 1GB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1988256] Re: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-in-43.0
** Tags added: fixed-in-43.rc

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

Title:
  gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node()
  from pointer_can_grab_surface() from
  meta_wayland_pointer_can_grab_surface() from
  meta_wayland_seat_get_grab_info() from token_can_activate()

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1988256/+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 1988660] Re: snap doesn't map joystick buttons correctly

2022-09-06 Thread Carlos V
As I said chromium in the deb version works ok I tested a PPA, all snaps
of chromium and chromium based like brave have the same problem.

Even flatpak chromium if you add this command flatpak --user override
--filesystem=/run/udev:ro  org.chromium.Chromium works fine.

I tested a PS4 controller but maybe all joysticks are also affected.

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

Title:
  snap doesn't map joystick buttons correctly

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I tested the deb version and works fine.

  Steps to reproduce the problem:
  1.Connect the PS4 joystick by Bluetooth in Linux
  2.Test mapping in a webpage like gamepad-tester.com
  3.Almost all buttons are incorrectly mapped

  Problem Description:
  The buttons of the joystick are incorrectly mapped in the browser and this 
makes impossible to play Stadia, even the right axis remain always pressed when 
you press R2 once, you can see the error by yourself at this short video: 
https://www.youtube.com/watch?v=VLPQkXyVAsM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1988660/+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 1857191] Re: Dark themes don't work well with highlighted current line in gedit

2022-09-06 Thread Daniel van Vugt
** Tags removed: fixed-in-5.2.0 fixed-upstream

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

Title:
  Dark themes don't work well with highlighted current line in gedit

Status in GtkSourceView:
  Fix Released
Status in gtksourceview4 package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  In order to checkout out an old bug report I started gedit, enabled
  "Highlight current line" and changed the application theme to "Yaru-
  dark" The current line is highlighted correctly but the text is
  unreadable because it is too light. The text needs to be much darker.

  This is not a theme that I would normally use so I'm not too bothered
  about how the problem is fixed but this configuration makes gedit very
  difficult to use as you can't actually see the text that you're
  adding, changing or deleting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-gtk 19.10.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 21 16:33:03 2019
  InstallationDate: Installed on 2019-05-17 (218 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtksourceview/+bug/1857191/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2022-09-06 Thread Daniel van Vugt
** Tags added: kivu performance

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2022-09-06 Thread Daniel van Vugt
** Tags added: kivu performance

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the Chromium snap,

     sudo snap install --channel candidate/hwacc chromium

  2. Start Chromium,

 snap run chromium

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar, click the
  corresponding box (if the video is playing, it will have the "(kPlay)"
  identifier) and note what the page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1988393] Re: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4

2022-09-06 Thread Daniel van Vugt
** Tags added: logspam

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

Title:
  JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js
  287]: Too many arguments to method Gio.AsyncInitable.init_async:
  expected 3, got 4

Status in gjs package in Ubuntu:
  New

Bug description:
  I'm seeing this in everyone's kinetic logs:

  JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js
  287]: Too many arguments to method Gio.AsyncInitable.init_async:
  expected 3, got 4

  and it appears gjs is the only place where too many arguments are
  provided.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1988393/+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 1988791] Re: ubuntu-appindicat...@ubuntu.com[...]: unable to update icon for multiload

2022-09-06 Thread Daniel van Vugt
** Tags added: logspam

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

Title:
  ubuntu-appindicat...@ubuntu.com[...]: unable to update icon for
  multiload

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in indicator-multiload package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing this flooding peoples' logs in a lot of unrelated bug
  reports:

ubuntu-appindicat...@ubuntu.com[...]: unable to update icon for
  multiload

  And it seems to happen when I install indicator-multiload myself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988791/+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


  1   2   >