date:20230502

[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libreoffice-common 1:7.4.4-0ubuntu0.22.10.1 failed to
  install/upgrade: installed libreoffice-common package post-
  installation script subprocess returned error exit status 134

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  Problem detected while system was attempting to update software.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: libreoffice-common 1:7.4.4-0ubuntu0.22.10.1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Jan 22 11:49:57 2023
  ErrorMessage: installed libreoffice-common package post-installation script 
subprocess returned error exit status 134
  InstallationDate: Installed on 2023-01-08 (14 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:7.4.4-0ubuntu0.22.10.1 failed to 
install/upgrade: installed libreoffice-common package post-installation script 
subprocess returned error exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003653/+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 109943] Re: Thunderbird: high CPU usage from progress bars

2023-05-02 Thread Bug Watch Updater

** Changed in: thunderbird
   Status: In Progress => Invalid

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

Title:
  Thunderbird: high CPU usage from progress bars

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: mozilla-thunderbird

  When sending a simple and short email with Thunderbird via SMTP the
  CPU is used intensively. This seems not to be necessary. If the
  sending failed and an corresponding error message dialog appears, the
  CPU is still being used. When pressing ok to close the error dialog
  the CPU is fine. This suggests it might be related specifically to the
  progress bar.  Such behavior is especially annoying on a laptop where
  you can hear the CPU usage because of a starting fan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/109943/+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 1987976] Re: firefox black window on wayland

2023-05-02 Thread Bug Watch Updater

** Changed in: firefox
   Status: Fix Released => Unknown

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

Title:
  firefox black window on wayland

Status in Mozilla Firefox:
  Unknown
Status in Mutter:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Lunar:
  In Progress

Bug description:
  [ Impact ]

  On some systems, when you open the Firefox snap right after having
  logged in into an Ubuntu on Wayland session, you are met by a black
  window. This happens because the FF snap is run under Xwayland, and
  Xwayland may not be enabled early enough to handle the start of the
  application properly.

  You can easily reproduce the issue in a Wayland session:

  * Close Firefox
  * Run the command "killall Xwayland" in terminal
  * Open Firefox

  An upstream mutter change addresses this issue, and the proposed lunar
  change cherry picks that upstream change as a patch.

  [ Test Plan ]

  On an updated Ubuntu 23.04:

  * Install the mutter related binaries from lunar-proposed

  * Reboot and log in to an Ubuntu on Wayland session

  * Run the command "killall Xwayland"

  * Open the Firefox snap, and find that it starts normally

  [ Where problems could occur ]

  This is the upstream merge request in question:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

  The changes (except for the test related ones) are small, and
  specifically intended to address issues like the one reported in this
  bug. There are also reviews by a couple of experienced GNOME devs.

  So even if the proposed change is not well tested yet, it seems to me
  that the risk for adverse side effects is limited.

  [ Original description ]

  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2023-05-02 Thread Vseerror

(In reply to Richard Marti (:Paenglab) from comment #83)
> I'll close the bug as we can't reproduce it.

Rather than Wontfix, it seems to me we should use WORKSFORME (for not
reproducible using the STR) or Fixed via comment 80.

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

Title:
  Thunderbird: high CPU usage from progress bars

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: mozilla-thunderbird

  When sending a simple and short email with Thunderbird via SMTP the
  CPU is used intensively. This seems not to be necessary. If the
  sending failed and an corresponding error message dialog appears, the
  CPU is still being used. When pressing ok to close the error dialog
  the CPU is fine. This suggests it might be related specifically to the
  progress bar.  Such behavior is especially annoying on a laptop where
  you can hear the CPU usage because of a starting fan.

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

2023-05-02 Thread Richard Marti

I'll close the bug as we can't reproduce it.

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

Title:
  Thunderbird: high CPU usage from progress bars

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: mozilla-thunderbird

  When sending a simple and short email with Thunderbird via SMTP the
  CPU is used intensively. This seems not to be necessary. If the
  sending failed and an corresponding error message dialog appears, the
  CPU is still being used. When pressing ok to close the error dialog
  the CPU is fine. This suggests it might be related specifically to the
  progress bar.  Such behavior is especially annoying on a laptop where
  you can hear the CPU usage because of a starting fan.

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

2023-05-02 Thread Vseerror

(In reply to Sebastian from comment #40)
> I am having the same issue with ~25% CPU usage when hovering over the 
> messages list and from what I can observer this is somehow related to the 
> HiDPI monitor I am using (27' LG, 4k)?
> 
> OS: Fedora 37
> TB: 102.9.1
> Nvidia 3060Ti + X11 (Also tested this with an AMD RX 580 and X11 and Wayland 
> - same issue)
> Ryzen 5 3400G (4 cores/8 threads)
> 16G Memory
> 
> Also recorded a profile: https://share.firefox.dev/3MNOpmA

nsTreeBodyFrame::PaintCell
nsTreeBodyFrame::PaintImage
nsMsgDBView::GetCellProperties

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

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later.
  Just moving the mouse cursor over a message list results in 365% CPU
  for me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

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

2023-05-02 Thread W-jan-k

*** Bug 1830482 has been marked as a duplicate of this bug. ***

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

Title:
  firefox black window on wayland

Status in Mozilla Firefox:
  Unknown
Status in Mutter:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Lunar:
  In Progress

Bug description:
  [ Impact ]

  On some systems, when you open the Firefox snap right after having
  logged in into an Ubuntu on Wayland session, you are met by a black
  window. This happens because the FF snap is run under Xwayland, and
  Xwayland may not be enabled early enough to handle the start of the
  application properly.

  You can easily reproduce the issue in a Wayland session:

  * Close Firefox
  * Run the command "killall Xwayland" in terminal
  * Open Firefox

  An upstream mutter change addresses this issue, and the proposed lunar
  change cherry picks that upstream change as a patch.

  [ Test Plan ]

  On an updated Ubuntu 23.04:

  * Install the mutter related binaries from lunar-proposed

  * Reboot and log in to an Ubuntu on Wayland session

  * Run the command "killall Xwayland"

  * Open the Firefox snap, and find that it starts normally

  [ Where problems could occur ]

  This is the upstream merge request in question:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

  The changes (except for the test related ones) are small, and
  specifically intended to address issues like the one reported in this
  bug. There are also reviews by a couple of experienced GNOME devs.

  So even if the proposed change is not well tested yet, it seems to me
  that the risk for adverse side effects is limited.

  [ Original description ]

  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1987976/+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 2017841] Re: Firefox drag/drop url onto desktop crashes ubuntu login session

2023-05-02 Thread 8bit Dingo

Identical issue.
 - first launch application after new logon opens a blank window surface. Kill 
then, wait for loading icon to stop, then launch again loads normally on second 
launch.
 - drag a link (padlock) from the window area causes an immediate end of 
desktop session.

Versions

NameWaterfox
Version G5.1.5
Build ID20230413101819
Update Directory /opt/waterfox
Update Channel  release
User Agent  Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 
Firefox/102.0
Kernel: Linux 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 
07:48:48 UTC 2023
OS: Ubuntu 23.04 x86_64 
DE: GNOME
WM: Mutter

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

Title:
  Firefox drag/drop url onto desktop crashes ubuntu login session

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Situation - while browsing I want to save page's url to desktop (likely any 
folder).
  I drag the url (by padlock icon in the address bar) onto my desktop folder to 
save shortcut to the page (for later view, to share it etc).
  The ubuntu user session (Wayland) will lock up and crash (bringing me back to 
user login screen) the moment I move the mouse (dragging the url) to FF windows 
boundary. Sometimes I'll get as far hovering over open desktop area but it'll 
crash withing seconds from me starting the task.
  No shortcut is saved to the desktop.
  FireFox can't restore session when launched again after login to system (I 
tried even restarting the pc before attempts at launching FF again). All you 
get is black/blank FF window and spinning cursor.
  Initially, the only way to get FF working again appeared to be to kill open 
FF window, switch to in private mode - this one will start fine and the next 
time FF would start normally. The session from before the crash would be gone 
though, really annoying for anyone with multiple open tabs. I'm quite certain 
that this was the reason why I'd given up on FF snap in 22.04 (normal/legacy 
install did not have the problem) but the same (?) problem on 23.04 forced me 
to have a closer look at what's going on, recovery options and to sing 
up/report the bug.
  What I've also noticed is that if following the crash I'd open in private FF 
windows 1st (instead of trying to open normal browser session only to have to 
terminate the browser showing blank window) and only then start normal FF 
session, FF would restore my tabs from before the crash. This is of little use 
now that I have to figure how to go back to my old session (I'll backtrack it 
somehow but this is pita). I'm tempted to pull the plug on snap FF again and 
move back to less fancy but more resilient setup (and with greater 
functionality).
  Btw, the same crash can be triggered when doing drag and drop from bookmark 
or history manager in FF.
  Chromium snap install does not crash the login/Wayland session but url drag 
and drop attempt just does nothing anyway, no file is left on the desktop. 
Quite a basic functionality that works from any browser on Windows or macOS, 
seems like a great omission. An unfortunate choice if limited interactivity 
with user's own file system was just inherent to snap packaged software. I 
understand security but it's personal computer desktop environment 1st.
  I'm not sure of any security impact but this surely does not look good and is 
definitely a risk of data/work lost (luckily I did not have whole lot of open 
windows besides terminal).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2017841/+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 2018343] [NEW] Single screen of multi-monitor setup went blank

2023-05-02 Thread Dayton Smith

Public bug reported:

Single screen of multi-monitor setup went blank

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue May  2 17:10:03 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-12-04 (149 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages 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/2018343

Title:
  Single screen of multi-monitor setup went blank

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Single screen of multi-monitor setup went blank

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  2 17:10:03 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-12-04 (149 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018343/+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 1994939] Re: It is not possible to add IPsec/IKEv2 (strongswan) vpn connection

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

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Confirmed

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

Title:
  It is not possible to add  IPsec/IKEv2 (strongswan) vpn connection

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  It is not possible to add  IPsec/IKEv2 (strongswan) vpn connection, the 
system freezes and then show "Error unable to load vpn connection editor".
  The package network-manager-strongswan and relative addon and libraries are 
installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager-gnome 1.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 27 08:59:35 2022
  InstallationDate: Installed on 2022-10-21 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  IpRoute:
   default via 192.168.128.1 dev enp0s31f6 proto dhcp src 192.168.128.101 
metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   172.16.175.0/24 dev vmnet1 proto kernel scope link src 172.16.175.1 
   172.16.249.0/24 dev vmnet8 proto kernel scope link src 172.16.249.1 
   192.168.128.0/24 dev enp0s31f6 proto kernel scope link src 192.168.128.101 
metric 100
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1994939/+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 2017859] Re: Unable to access the right top controls in chromium based browsers after ubuntu 23.04 upgrade

2023-05-02 Thread Paul White

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

** Tags added: lunar

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

Title:
  Unable to access the right top controls in chromium based browsers
  after ubuntu 23.04 upgrade

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Unable to access the right-top Vivaldi browser controls. Found with
  Vivaldi first but it affects all Chromium-based browsers. If I move
  the browser a little low, then I am able to click that controls. It
  looks like a particular part of the top right corner of the desktop is
  disabled when Vivaldi running. Something is loading on that part (plz
  check my video. The cursor is loading if I move the cursor on that
  part). So I am unable to click anything in that area.

  It only happens in Vivaldi and all other chromium based browsers (latest 
version)
  All other programs are working perfectly. (check video)
  The problem started immediately after Ubuntu 22.10 to Ubuntu 23.04 Upgrade.

  Plz check this video:
  
https://drive.google.com/file/d/1jscZ8ohltC27yi8ROrJ0tRvHMNunBlr9/view?usp=share_link

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2017859/+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 2018180] Re: nautilus crashing randomly

Yes, most cases the /snap/foo/current/ folders, but I also got it
crashed while using the Downloads folder also. But, it mostly happens
when I am working in that $SNAP folder.

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

Title:
  nautilus crashing randomly

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I recently updated my Ubuntu installation from 22.10 to 23.04, and after 
that, nautilus just crashes randomly. Even right-clicking on it often doesn't 
show up the list of folders as shortcuts.
  I think, this issue is related to some caches, which are from the previous 
version of nautilus. But, that makes it that we cannot upgrade a distro and be 
bug free.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 13:23:37 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1184, 815)'
  InstallationDate: Installed on 2023-02-02 (86 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (8 days ago)
  usr_lib_nautilus:
   file-roller  43.0-1
   nautilus-image-converter 0.4.0-2
   nautilus-share   0.7.5-0.3
   python3-nautilus 4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018180/+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 2018180] Re: nautilus crashing randomly

Are you able to find specific steps or folders triggering the issue? It
could be specific to some file or content of a directory or some
configuration...

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

Title:
  nautilus crashing randomly

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I recently updated my Ubuntu installation from 22.10 to 23.04, and after 
that, nautilus just crashes randomly. Even right-clicking on it often doesn't 
show up the list of folders as shortcuts.
  I think, this issue is related to some caches, which are from the previous 
version of nautilus. But, that makes it that we cannot upgrade a distro and be 
bug free.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 13:23:37 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1184, 815)'
  InstallationDate: Installed on 2023-02-02 (86 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (8 days ago)
  usr_lib_nautilus:
   file-roller  43.0-1
   nautilus-image-converter 0.4.0-2
   nautilus-share   0.7.5-0.3
   python3-nautilus 4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018180/+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 2018305] Re: Bluetooth headset suddenly stops playback (until power is turned off and on again)"

2023-05-02 Thread Erich Eickmeyer

bluetooth audio isn't handled by alsa, but by pulseaudio directly.

** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Bluetooth headset suddenly stops playback (until power is turned off
  and on again)"

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When watching videos using video players (SM Player, VLC, etc.) and
  repeatedly using the space key to toggle play/pause, the sound output
  to the Bluetooth headset stops working after a short while. When the
  Bluetooth headset's power is turned off, the sound that was not
  working immediately starts coming out of the built-in speaker. It's as
  if the sound data that was trapped in a queue suddenly pours out when
  the blockage is cleared. The same symptom occurs not only in video
  players, but also in other learning programs and places where keyboard
  or mouse clicks are repeated. Whenever the sound gets blocked, I have
  to repeatedly turn the Bluetooth headset off and on again. This issue
  occurs very frequently.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fts2436 F pulseaudio
   /dev/snd/controlC1:  fts2436 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  2 22:43:12 2023
  InstallationDate: Installed on 2022-07-09 (297 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03AJK.039.210920.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT850XCR-HD7AB
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03AJK.039.210920.SH:bd09/20/2021:br5.17:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XCJ:pvrP03AJK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT850XCR-HD7AB:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAJK:
  dmi.product.family: Odyssey Series
  dmi.product.name: 850XCJ
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAJK
  dmi.product.version: P03AJK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2018305/+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 2018305] Re: Bluetooth headset suddenly stops playback (until power is turned off and on again)"

2023-05-02 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Bluetooth headset suddenly stops playback (until power is turned off
  and on again)"

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When watching videos using video players (SM Player, VLC, etc.) and
  repeatedly using the space key to toggle play/pause, the sound output
  to the Bluetooth headset stops working after a short while. When the
  Bluetooth headset's power is turned off, the sound that was not
  working immediately starts coming out of the built-in speaker. It's as
  if the sound data that was trapped in a queue suddenly pours out when
  the blockage is cleared. The same symptom occurs not only in video
  players, but also in other learning programs and places where keyboard
  or mouse clicks are repeated. Whenever the sound gets blocked, I have
  to repeatedly turn the Bluetooth headset off and on again. This issue
  occurs very frequently.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fts2436 F pulseaudio
   /dev/snd/controlC1:  fts2436 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  2 22:43:12 2023
  InstallationDate: Installed on 2022-07-09 (297 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03AJK.039.210920.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT850XCR-HD7AB
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03AJK.039.210920.SH:bd09/20/2021:br5.17:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XCJ:pvrP03AJK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT850XCR-HD7AB:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAJK:
  dmi.product.family: Odyssey Series
  dmi.product.name: 850XCJ
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAJK
  dmi.product.version: P03AJK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2018305/+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 2018316] [NEW] wireplumber sometime segfault on bluez devices disconnect

Public bug reported:

* Impact

wireplumber sometime segfault on bluez devices disconnect leading to non
working pipewire audio

* Test case

Connect and disconnect bluetooth audio devices and ensure
wireplumber/pipewire-pulse don't hit an error and sound keeps working in
the desktop (sound settings testsound, rhythmbox, firefox playing video)

and check that error reports stop on 
https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53

* Regression potential

The change is in the pipewire bluez plugin so the testing should focus
on bluetooth audio devices

** Affects: pipewire (Ubuntu)
 Importance: High
 Status: Fix Committed

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

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

** Description changed:

  * Impact
  
  wireplumber sometime segfault on bluez devices disconnect leading to non
  working pipewire audio
- 
  
  * Test case
  
  Connect and disconnect bluetooth audio devices and ensure
  wireplumber/pipewire-pulse don't hit an error and sound keeps working in
  the desktop (sound settings testsound, rhythmbox, firefox playing video)
  
+ and check that error reports stop on 
+ https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53
+ 
  * Regression potential
  
  The change is in the pipewire bluez plugin so the testing should focus
  on bluetooth audio devices

** Bug watch added: gitlab.freedesktop.org/pipewire/wireplumber/-/issues #430
   https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/430

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

Title:
  wireplumber sometime segfault on bluez devices disconnect

Status in pipewire package in Ubuntu:
  Fix Committed

Bug description:
  * Impact

  wireplumber sometime segfault on bluez devices disconnect leading to
  non working pipewire audio

  * Test case

  Connect and disconnect bluetooth audio devices and ensure
  wireplumber/pipewire-pulse don't hit an error and sound keeps working
  in the desktop (sound settings testsound, rhythmbox, firefox playing
  video)

  and check that error reports stop on 
  https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53

  * Regression potential

  The change is in the pipewire bluez plugin so the testing should focus
  on bluetooth audio devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2018316/+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 2018314] Re: /usr/bin/wireplumber:6:loop_iterate:do_loop:start_thread:clone

The issue is a pipewire one handled in bug #2018316

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

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

Title:
  /usr/bin/wireplumber:6:loop_iterate:do_loop:start_thread:clone

Status in wireplumber package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
wireplumber.  This problem was most recently seen with package version 
0.4.13-1, the problem page at 
https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53 
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/ubuntu/+source/wireplumber/+bug/2018314/+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 2018315] [NEW] wireplumber sometime segfault on bluez devices disconnect

Public bug reported:

* Impact

wireplumber sometime segfault on bluez devices disconnect leading to non
working pipewire audio


* Test case

Connect and disconnect bluetooth audio devices and ensure
wireplumber/pipewire-pulse don't hit an error and sound keeps working in
the desktop (sound settings testsound, rhythmbox, firefox playing video)

* Regression potential

The change is in the pipewire bluez plugin so the testing should focus
on bluetooth audio devices

** Affects: pipewire (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

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

Title:
  wireplumber sometime segfault on bluez devices disconnect

Status in pipewire package in Ubuntu:
  Invalid

Bug description:
  * Impact

  wireplumber sometime segfault on bluez devices disconnect leading to
  non working pipewire audio

  
  * Test case

  Connect and disconnect bluetooth audio devices and ensure
  wireplumber/pipewire-pulse don't hit an error and sound keeps working
  in the desktop (sound settings testsound, rhythmbox, firefox playing
  video)

  * Regression potential

  The change is in the pipewire bluez plugin so the testing should focus
  on bluetooth audio devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2018315/+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 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

2023-05-02 Thread Jürgen Hörmann

@vanvugt
This bug is also present in Wayland session, not only on X11. Maybe it makes 
sense to cover this in the bug report title.

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

Yeah, thankyou @hoermannn.j it warked that way.

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2018314] [NEW] /usr/bin/wireplumber:6:loop_iterate:do_loop:start_thread:clone

2023-05-02 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
wireplumber.  This problem was most recently seen with package version 
0.4.13-1, the problem page at 
https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53 
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/.

** Affects: wireplumber (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: kinetic lunar

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

Title:
  /usr/bin/wireplumber:6:loop_iterate:do_loop:start_thread:clone

Status in wireplumber package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
wireplumber.  This problem was most recently seen with package version 
0.4.13-1, the problem page at 
https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53 
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/ubuntu/+source/wireplumber/+bug/2018314/+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 2018180] Re: nautilus crashing randomly

Is there anything that I can do to help you from my side?

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

Title:
  nautilus crashing randomly

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I recently updated my Ubuntu installation from 22.10 to 23.04, and after 
that, nautilus just crashes randomly. Even right-clicking on it often doesn't 
show up the list of folders as shortcuts.
  I think, this issue is related to some caches, which are from the previous 
version of nautilus. But, that makes it that we cannot upgrade a distro and be 
bug free.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 13:23:37 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1184, 815)'
  InstallationDate: Installed on 2023-02-02 (86 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (8 days ago)
  usr_lib_nautilus:
   file-roller  43.0-1
   nautilus-image-converter 0.4.0-2
   nautilus-share   0.7.5-0.3
   python3-nautilus 4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018180/+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 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

2023-05-02 Thread Jürgen Hörmann

@kikezzdrums. 
If you disable/uninstall gnome-shell-extension-appindicator or disable the 
legacy tray icons option, you have to log out of your active gnome session and 
re-login again. If you do not log out, the bug will still occur.

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2018132] Re: wifi connection lost on firefox crash

2023-05-02 Thread Kyriakos Fytrakis

No problem.
I think it is a new bug, unrelated to any of my previous problems. 
Specifically, following your step-by-step guidance:
1. nothing found here
2. nothing related found here, but some bugs at the time of new fresh OS 
install (many days before the new bug submitted)
I don't know if this helps, but recently the firefox snap has been refreshed to 
a new version and if I remember correctly the submitted bug found after that 
time. Additionally, the black window bug when starting firefox snap remains, 
not as usual as before.

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

Title:
  wifi connection lost on firefox crash

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  firefox snap occasionally crashes, ie shown a black screen on startup.
  lately, when it crashes, nm-applet disappears from the tray without 
disconnecting from the router.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: network-manager 1.42.4-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 11:13:03 2023
  InstallationDate: Installed on 2023-04-24 (4 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp src 192.168.1.3 metric 600 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.3 metric 600
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATE   IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION  
CON-UUID  CON-PATH  
 
   wlo1  wifi  connected   full  full   
   /org/freedesktop/NetworkManager/Devices/2  Forthnet-4jPPK  
eb56363e-28c9-432a-864b-cebcedbfdacf  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   loloopback  connected (externally)  unknown   unknown
   /org/freedesktop/NetworkManager/Devices/1  lo  
ccbf9b80-8294-485c-bc1c-3050ad48b3d9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlo1  wifi-p2p  disconnectednone  none   
   /org/freedesktop/NetworkManager/Devices/3  --  --
--
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.42.4   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2018132/+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 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

Attached video reproducing how mouse pointer does not affect windows at
certain point at top-right corner.

** Attachment added: "icon-tray-click-2023-05-02_10.29.40.mkv"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+attachment/5670330/+files/icon-tray-click-2023-05-02_10.29.40.mkv

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2018180] Re: nautilus crashing randomly

Thanks, the most recent error points to
https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus%3A11%3A__GI___libc_free%3Ag_free%3Agdk_content_formats_unref%3Agdk_content_formats_unref%3Agtk_drop_target_finalize
which is a nautilus report

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

Title:
  nautilus crashing randomly

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I recently updated my Ubuntu installation from 22.10 to 23.04, and after 
that, nautilus just crashes randomly. Even right-clicking on it often doesn't 
show up the list of folders as shortcuts.
  I think, this issue is related to some caches, which are from the previous 
version of nautilus. But, that makes it that we cannot upgrade a distro and be 
bug free.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 13:23:37 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1184, 815)'
  InstallationDate: Installed on 2023-02-02 (86 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (8 days ago)
  usr_lib_nautilus:
   file-roller  43.0-1
   nautilus-image-converter 0.4.0-2
   nautilus-share   0.7.5-0.3
   python3-nautilus 4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018180/+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 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

When disabled 'Ubuntu AppIndicators', clicks at minimize worked ok; but later, 
those clicks stopped working again even with all extensions disabled :/
Update: Discovered that I was clicking at an specific pixel that is not stollen 
by the icon tray.

I noticed that even the 'hover' mouse action over minimize-restore-close
buttons, does not trigger.

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2017426] Re: Can't connect with RDP from/to LTS22.04

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.

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

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

Title:
  Can't connect with RDP from/to LTS22.04

Status in gnome-remote-desktop package in Ubuntu:
  Incomplete

Bug description:
  I use on both side the default apps and desktop environment: 
gnome-control-center, remmina & wayland.
  I tried with all three possible server side session locked/unlocked/closed.
  lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  apt-cache policy gnome-remote-desktop
  gnome-remote-desktop:
Installé : 42.7-0ubuntu1
Candidat : 42.7-0ubuntu1
   Table de version :
   *** 42.7-0ubuntu1 500 (phased 0%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-4ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  I tried also with ssh tunnel disabled (and port 3389 opened for remote 
access) 
  Chain INPUT (policy DROP 4 packets, 240 bytes)
   pkts bytes target prot opt in out source   
destination 
140 15693 ACCEPT tcp  --  *  *   192.168.22.290.0.0.0/0 
   tcp dpt:3389
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2014-07-26 (3201 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: gnome-remote-desktop 42.7-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92
  Tags:  jammy
  Uname: Linux 5.15.0-71-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-04-07 (23 days ago)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2017426/+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 2018132] Re: wifi connection lost on firefox crash

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.

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

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

Title:
  wifi connection lost on firefox crash

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  firefox snap occasionally crashes, ie shown a black screen on startup.
  lately, when it crashes, nm-applet disappears from the tray without 
disconnecting from the router.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: network-manager 1.42.4-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 11:13:03 2023
  InstallationDate: Installed on 2023-04-24 (4 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp src 192.168.1.3 metric 600 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.3 metric 600
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATE   IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION  
CON-UUID  CON-PATH  
 
   wlo1  wifi  connected   full  full   
   /org/freedesktop/NetworkManager/Devices/2  Forthnet-4jPPK  
eb56363e-28c9-432a-864b-cebcedbfdacf  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   loloopback  connected (externally)  unknown   unknown
   /org/freedesktop/NetworkManager/Devices/1  lo  
ccbf9b80-8294-485c-bc1c-3050ad48b3d9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlo1  wifi-p2p  disconnectednone  none   
   /org/freedesktop/NetworkManager/Devices/3  --  --
--
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.42.4   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2018132/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

** Changed in: gvfs (Ubuntu Lunar)
   Importance: Unknown => Undecided

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

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

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

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

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

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

Status in gvfs package in Ubuntu:
  New
Status in tracker-miners package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Invalid
Status in tracker-miners source package in Bionic:
  Won't Fix
Status in gvfs source package in Focal:
  Invalid
Status in tracker-miners source package in Focal:
  In Progress
Status in gvfs source package in Jammy:
  Invalid
Status in tracker-miners source package in Jammy:
  In Progress
Status in gvfs source package in Kinetic:
  Invalid
Status in tracker-miners source package in Kinetic:
  In Progress
Status in gvfs source package in Lunar:
  Invalid
Status in tracker-miners source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  The KRB5CCNAME environment variable points to the Kerberos ticket of
  the current machine and this ticket is used for authentication in
  Active Directory  servers.

  This variable is set by pam_sss when the user authenticates and can be
  used by other processes, such as gio, to skip the credentials input
  when accessing network shares, for example.

  Some services rely on gvfs-daemon in order to properly function, such
  as tracker-extract-3.service and tracker-miner-fs-3.service, which
  means they will ask for the gvfs-daemon to be initialized when they
  are executed by systemd. This creates problems if one service that
  relies on gvfsd is started too early, as it would result in gvfsd
  being started too early as well.

  As of version 3.1 of tracker-miners, the install target of tracker-
  miners-fs-3.service was set to gnome-session.target:
  https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283

  However, the tracker-extract-3.service was not updated and its target
  is still default.target, which is too early for the service to start.

  Starting tracker-extract too early is also starting gvfsd too early,
  before the session environment gets fully updated. Which means that
  gvfsd does not have the KRB5CCNAME variable and can not do any
  operations with it.

  Tracker-extract is supposed to be a helper service managed by tracker-
  miner-fs-3.service. By using a [Install] section, we are actually
  telling systemd that it should manage this service as well, when it
  shouldn't.

  So, by removing the [Install] section and having tracker-miner-
  fs-3.service being tied to gnome-session.target, we fix the issue of
  gvfsd starting too early without the updated session environment.

  [ Test Plan ]

  In order to test this issue, it's required to have an Active Directory server 
running.
  1) Authenticate with an AD user (as this would set the KRB5CCNAME env);
  2) Check gvfsd environment. This can be done by running:
  cat /proc/$(pidof gvfsd)/environ | xargs --null -n1

     You will be able to see that it does not have the variable listed.
  3) Check that the information mentioned above about tracker-miner-fs-
     3.service is true.
  4) Disable tracker-extract-3.service (This is a bit tricky, since its
     target was default.target. The easiest way is to remove the symlink that
     systemd created when enabling the unit, located under
     /etc/systemd/user/default.target.wants/tracker-extract-3.service
  5) Reboot the machine;
  6) Repeat steps 1 and 2.
     This will show that gvfsd is now started with the proper environment.

  Is not enough to look at ptree and the pids of the processes, instead
  it's better to look into the session logs with:

     journalctl --user -b

  And check the order in which the services were started and when they
  were triggered.

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test

  After installing test packages of tracker-miners, KRB5CCNAME should be
  set in gvfs environment upon login to gnome.

  [ Where problems could occur ]

  The tracker project is a search engine that speeds up search
  operations in Gnome. The tracker-miners is the indexing daemon that
  populates the database with information, so changing its start does
  not affect the system behavior.

  This changes fix the startup of gvfs-daemon.service, which could delay
  services that relied on it running to be executed.

  [ Other info ]

  This was fixed upstream by the following commit:

  commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3
  From:

[Desktop-packages] [Bug 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

@Daniel, you said that's a newer issue, did we change the default of
that option?

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-ll-incoming

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

2023-05-02 Thread herrsaalfeld

I am having the same problem, but I prevented snap from updating firefox with
```
snap refresh --hold firefox
```
Since Ubuntu's transitional deb package does not understand my snap 
preferences, it now simply *uninstalls* the firefox deb package, and I have to 
manually update it with
```
sudo apt install firefox
```
after Ubuntu's software updater, kind of silly, and the opposite of user 
friendly.  However, @vanadium offered a solution at

https://askubuntu.com/questions/1407913/how-to-stop-an-individual-snap-
from-updating-ubuntu-22-04-lts

that disables Ubuntu's transitional deb package.  For me, the combination of 
setting the priority of the Mozilla PPA and disabling Ubuntu's transitional 
firefox package looks like this
```
cat

[Desktop-packages] [Bug 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

Open gnome-shell-extension-prefs, scroll down to 'Ubuntu Appindicators'
and disable it.

I already did, and icon tray stopped stealing click actions.

'Enable Legacy tray icons' is an option of 'Ubuntu Appindicators'
extension. You can see it if you click on Settings at 'Ubuntu
AppIndicators' extension, but disabling only that setting did not work
for me, I had to disable the entire extension.

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2012978] Re: Memory leak

2023-05-02 Thread Treviño

Currently we're getting

❯ env G_SLICE=always-malloc valgrind --leak-check=full 
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp gjs -c "const 
GLib=imports.gi['GLib'];function leak(){const 
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();" 
==131398== Memcheck, a memory error detector
==131398== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==131398== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==131398== Command: gjs -c const\ GLib=imports.gi['GLib'];function\ 
leak(){const\ l=GLib.Variant['new']('i',1)};leak();imports.system.gc();
==131398== 
==131398== Warning: set address range perms: large range [0x1663bc3af000, 
0x16643bfaf000) (noaccess)
==131398== Warning: set address range perms: large range [0x1663bc3af000, 
0x16643bfaf000) (noaccess)
==131398== 
==131398== HEAP SUMMARY:
==131398== in use at exit: 191,779 bytes in 2,483 blocks
==131398==   total heap usage: 18,733 allocs, 16,250 frees, 8,376,620 bytes 
allocated
==131398== 
==131398== 108 (64 direct, 44 indirect) bytes in 1 blocks are definitely lost 
in loss record 1,885 of 2,041
==131398==at 0x4844899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==131398==by 0x4A22948: g_malloc (gmem.c:130)
==131398==by 0x4A6598F: UnknownInlinedFun (gvariant-core.c:565)
==131398==by 0x4A6598F: g_variant_new_from_bytes (gvariant-core.c:608)
==131398==by 0x4A65EF3: UnknownInlinedFun (gvariant.c:327)
==131398==by 0x4A65EF3: g_variant_new_int32 (gvariant.c:491)
==131398==by 0x51B8E2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
==131398==by 0x51B5492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
==131398==by 0x48C8198: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==131398==by 0x48C8A06: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==131398==by 0x532FC81: js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (Interpreter.cpp:420)
==131398==by 0x533A46B: UnknownInlinedFun (Interpreter.cpp:574)
==131398==by 0x533A46B: UnknownInlinedFun (Interpreter.cpp:578)
==131398==by 0x533A46B: Interpret(JSContext*, js::RunState&) [clone 
.lto_priv.0] (Interpreter.cpp:3314)
==131398==by 0x532F692: js::RunScript(JSContext*, js::RunState&) 
(Interpreter.cpp:389)
==131398==by 0x532FA8E: js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (Interpreter.cpp:539)
==131398== 
==131398== 352 bytes in 1 blocks are possibly lost in loss record 1,999 of 2,041
==131398==at 0x4849A83: calloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==131398==by 0x4012949: calloc (rtld-malloc.h:44)
==131398==by 0x4012949: allocate_dtv (dl-tls.c:375)
==131398==by 0x4012949: _dl_allocate_tls (dl-tls.c:634)
==131398==by 0x5019F99: allocate_stack (allocatestack.c:423)
==131398==by 0x5019F99: pthread_create@@GLIBC_2.34 (pthread_create.c:650)
==131398==by 0x5A97B54: mozilla::TimeStamp::ComputeProcessUptime() 
(TimeStamp_posix.cpp:275)
==131398==by 0x5A97BE7: mozilla::TimeStamp::ProcessCreation() 
(TimeStamp.cpp:62)
==131398==by 0x53FD5FC: JS::detail::InitWithFailureDiagnostic(bool) 
(Initialization.cpp:145)
==131398==by 0x48A3E25: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==131398==by 0x4004FBD: call_init.part.0 (dl-init.c:70)
==131398==by 0x40050A7: call_init (dl-init.c:33)
==131398==by 0x40050A7: _dl_init (dl-init.c:117)
==131398==by 0x401D8AF: ??? (in 
/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2)
==131398==by 0x2: ???
==131398==by 0x1FFEFFF606: ???
==131398== 
==131398== LEAK SUMMARY:
==131398==definitely lost: 64 bytes in 1 blocks
==131398==indirectly lost: 44 bytes in 2 blocks
==131398==  possibly lost: 352 bytes in 1 blocks
==131398==still reachable: 75,986 bytes in 985 blocks
==131398== suppressed: 97,525 bytes in 1,306 blocks
==131398== Reachable blocks (those to which a pointer was found) are not shown.
==131398== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==131398== 
==131398== For lists of detected and suppressed errors, rerun with: -s
==131398== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 2 from 2

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

Title:
  Memory leak

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Triaged
Status in gjs source package in Kinetic:
  Triaged

Bug description:
  [ Impact ]

  High Memory Usage 3.1gb in 2h after reboot

  [ Test case ]

  Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
  --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
  gjs -c "const GLib=imports.gi['GLib'];function leak(){const 
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"

  No leak should be detected

[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

** Description changed:

+ [ Impact ]
+ 
+ gnome-shell often crashes on logout causing annoyance to the user as an
+ error report dialog is displayed at the next login.
+ 
+ [ Test Plan ]
+ 
+ 1. Log into gnome-shell
+ 
+ 2. Use gnome-shell for long enough to trigger a garbage collection
+ cycle: Scroll the app grid and repeatedly open the calendar from the top
+ bar for 30 seconds.
+ 
+ 3. Log out.
+ 
+ 4. Verify no new gnome-shell crash files appear in /var/crash/
+ 
+ [ Where problems could occur ]
+ 
+ Only gnome-shell shutdown/logout is affected.
+ 
+ [ Other Info ]
+ 
  https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
  https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7
  
  Description: Ubuntu 22.04 LTS
  Release: 22.04
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 16:06:35 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-05 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

Title:
  gnome-shell crashed on logout with SIGSEGV in
  js::gc::Cell::storeBuffer() from
  js::gc::PostWriteBarrierImpl()

Status in gjs:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Triaged
Status in gjs source package in Kinetic:
  Triaged
Status in gjs source package in Lunar:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  [ Impact ]

  gnome-shell often crashes on logout causing annoyance to the user as
  an error report dialog is displayed at the next login.

  [ Test Plan ]

  1. Log into gnome-shell

  2. Use gnome-shell for long enough to trigger a garbage collection
  cycle: Scroll the app grid and repeatedly open the calendar from the
  top bar for 30 seconds.

  3. Log out.

  4. Verify no new gnome-shell crash files appear in /var/crash/

  [ Where problems could occur ]

  Only gnome-shell shutdown/logout is affected.

  [ Other Info ]

  https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
  https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7

  Description: Ubuntu 22.04 LTS
  Release: 22.04

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 16:06:35 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-05 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_object_unref()
  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/gjs/+bug/1974293/+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 2018258] Re: lock-screen-on-disconnect not honnoured

** Changed in: gnome-remote-desktop (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-remote-desktop (Ubuntu)
   Status: New => Triaged

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

Title:
  lock-screen-on-disconnect not honnoured

Status in gnome-remote-desktop package in Ubuntu:
  Triaged

Bug description:
  The setting in /org/gnome/desktop/remote-access/lock-screen-on-
  disconnect won't lock the screen when set to true and one (single
  connection) disconnects

  Notice : same behaviour whether or not the extension that allows
  access to login screen (Allow Locked Remote Desktop UUID:
  allowlockedremotedesk...@kamens.us version 9) is enabled or disabled.

  lsb_release -d
  Description:  Ubuntu 22.04.2 LTS
  dpkg-query -l gnome-remote-desktop
  ii  gnome-remote-desktop 42.7-0ubuntu1 amd64Remote desktop daemon for 
GNOME using PipeWire
  gnome-shell --version
  GNOME Shell 42.5

  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/153

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2018258/+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 2018262] Re: nm-connection-editor exits with coredump when importing ovpn file

Thank you for the bug report, upstream pushed a fix in their vcs

https://gitlab.gnome.org/GNOME/network-manager-applet/-/commit/01281fae

** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Fix Committed

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

Title:
  nm-connection-editor exits with coredump when importing ovpn file

Status in network-manager-applet package in Ubuntu:
  Fix Committed

Bug description:
  Software versions:
  Networkmanager: 1.42.6-1
  nm-connection-editor: 1.32.0-1
  networkmanager-openvpn: 1.10.2-1
  openvpn: 2.6.2-1

  Arch Linux kernel: 6.2.13-zen-1-zen

  While trying to import an ovpn file downloaded from NordVPN, nm-
  connection-editor exits with a coredump.

  Downgrading to nm-connection-editor ver 1.30.0-1 allowed me to import
  the configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2018262/+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 2012978] Re: Memory leak

2023-05-02 Thread Treviño

** Description changed:

+ [ Impact ]
+ 
  High Memory Usage 3.1gb in 2h after reboot
  
- ProblemType: Bug
- DistroRelease: Ubuntu 22.04
+ [ Test case ]
+ 
+ Run:
+   env G_SLICE=always-malloc valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ gjs -c "const GLib=imports.gi['GLib'];function leak(){const 
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
+ 
+ No leak should be detected
+ 
+ [ Regression potential ]
+ 
+ Gjs applications (including gnome Shell) using GVariant may misbehave
+ 
+ 
+ ProblemType: BugDistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  Uname: Linux 6.2.8-060208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 22:46:07 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-25 (366 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
- RelatedPackageVersions: mutter-common 42.5-0ubuntu1
- SourcePackage: gnome-shell
+ RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)

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

Title:
  Memory leak

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Triaged
Status in gjs source package in Kinetic:
  Triaged

Bug description:
  [ Impact ]

  High Memory Usage 3.1gb in 2h after reboot

  [ Test case ]

  Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
  --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
  gjs -c "const GLib=imports.gi['GLib'];function leak(){const 
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"

  No leak should be detected

  [ Regression potential ]

  Gjs applications (including gnome Shell) using GVariant may misbehave

  
  ProblemType: BugDistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  Uname: Linux 6.2.8-060208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 22:46:07 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-25 (366 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+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 2012978] Re: Memory leak

2023-05-02 Thread Jeremy Bícha

** Also affects: gjs (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: gjs (Ubuntu Kinetic)
   Status: New => Triaged

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

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

Title:
  Memory leak

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Triaged
Status in gjs source package in Kinetic:
  Triaged

Bug description:
  [ Impact ]

  High Memory Usage 3.1gb in 2h after reboot

  [ Test case ]

  Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
  --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
  gjs -c "const GLib=imports.gi['GLib'];function leak(){const 
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"

  No leak should be detected

  [ Regression potential ]

  Gjs applications (including gnome Shell) using GVariant may misbehave

  
  ProblemType: BugDistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  Uname: Linux 6.2.8-060208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 22:46:07 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-25 (366 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+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 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

2023-05-02 Thread Luis Alvarado

If I disable the "legacy tray icons" option...

How can I disable the legacy tray icons to try to replicate this? Just
to test it thoroughly.

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2018297] Re: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

Could you add the journalctl log from the session where you had the
issue?

** Changed in: iio-sensor-proxy (Ubuntu)
   Importance: Undecided => Low

** Changed in: iio-sensor-proxy (Ubuntu)
   Status: New => Incomplete

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

Title:
  ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

Status in gnome-shell package in Ubuntu:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Incomplete

Bug description:
  The auto-rotation feature of my Laptop stoped working.

  - screen orientation was in landscape mode 
  - closed the lid of my laptop 
=> laptop entered suspension mode 
  - opened the lid
=> laptop was waking up
  - screen orientation was in portait mode

  I could not change the screen orientation by rotating the laptop
  physically nor change the orientation manually (the "Orientation"
  setting in the "Display Settings" Menu showed no dropdown menu). After
  a quick reboot everything worked fine.

  This are the specs of my Device:

  OS: Ubuntu 23.04 x86_64 
  Host: 20EM000VGE ThinkPad Yoga 460 
  Kernel: 6.2.0-20-generic 
  Resolution: 1920x1080 
  DE: GNOME 44.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  CPU: Intel i7-6500U (4) @ 3.100GHz 
  GPU: Intel Skylake GT2 [HD Graphics 520] 
  Memory: 7682MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018297/+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 2012178] Re: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined

** Information type changed from Private to Public

** Changed in: hplip (Ubuntu)
   Importance: Medium => High

** Also affects: hplip (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: hplip (Ubuntu Lunar)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

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

** Changed in: hplip (Ubuntu Lunar)
   Status: New => Triaged

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

Title:
  toolbox.py crashed with NameError in __readAuthType(): name
  'get_distro_std_name' is not defined

Status in hplip package in Ubuntu:
  Fix Committed
Status in hplip source package in Lunar:
  Triaged

Bug description:
  Error occurred after installing hplip-gui

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: hplip-data 3.22.10+dfsg0-1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sun Mar 19 05:07:34 2023
  ExecutablePath: /usr/share/hplip/toolbox.py
  InstallationDate: Installed on 2023-03-18 (0 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230318)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: -- No entries --
  Lpstat: device for HP_Color_LaserJet_Pro_MFP_M177fw_0342B1: 
implicitclass://HP_Color_LaserJet_Pro_MFP_M177fw_0342B1/
  MachineType: HP HP ZBook 17 G4
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd: 
Permission denied
  ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic 
root=UUID=20a0c66a-2dc4-41ec-a5f0-7eb86e995862 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonArgs: ['/usr/bin/hp-toolbox']
  PythonDetails: N/A
  SourcePackage: hplip
  Title: toolbox.py crashed with NameError in __readAuthType(): name 
'get_distro_std_name' is not defined
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  dmi.bios.date: 04/08/2022
  dmi.bios.release: 1.41
  dmi.bios.vendor: HP
  dmi.bios.version: P70 Ver. 01.41
  dmi.board.name: 8270
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 46.80
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 70.128
  dmi.modalias: 
dmi:bvnHP:bvrP70Ver.01.41:bd04/08/2022:br1.41:efr70.128:svnHP:pnHPZBook17G4:pvr:rvnHP:rn8270:rvrKBCVersion46.80:cvnHP:ct10:cvr:skuY3J83AV:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ZBook 17 G4
  dmi.product.sku: Y3J83AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2012178/+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 2006460] Re: hp-toolbox fails on load due to call to undefined "get_distro_std_name' function

*** This bug is a duplicate of bug 2012178 ***
https://bugs.launchpad.net/bugs/2012178

** This bug has been marked a duplicate of bug 2012178
   toolbox.py crashed with NameError in __readAuthType(): name 
'get_distro_std_name' is not defined

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

Title:
  hp-toolbox fails on load due to call to undefined
  "get_distro_std_name' function

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  When starting hp-toolbox from the GUI, nothing happens. From the CLI I
  get the information :

  HP Linux Imaging and Printing System (ver. 3.22.10)
  HP Device Manager ver. 15.0

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Traceback (most recent call last):
File "/usr/bin/hp-toolbox", line 280, in 
  toolbox = ui.DevMgr5(__version__, device_uri,  None)
^^
File "/usr/share/hplip/ui5/devmgr5.py", line 238, in __init__
  core =  CoreInstall(MODE_CHECK)
  ^^^
File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
  self.passwordObj = password.Password(ui_mode)
 ^^
File "/usr/share/hplip/base/password.py", line 94, in __init__
  self.__readAuthType()  # self.__authType
  ^
File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
  distro_name = get_distro_std_name(os_name)
^^^

  Changing the instances of get_distro_std_name(os_name) to
  get_distro_name() as suggested resolved the bug.

  When installing the plugin for the scanner, the same issue crops up
  again, here at line 322. An identical substitution allows the plugin
  installer to complete successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: hplip-data 3.22.10+dfsg0-1 [modified: 
usr/share/hplip/base/password.py]
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CupsErrorLog:
   W [07/Feb/2023:11:47:17 +0100] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
   W [07/Feb/2023:11:47:23 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_Color_LaserJet_MFP_M281fdw_5543F1-Gray..\' already exists
   W [07/Feb/2023:11:47:23 +0100] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP_Color_LaserJet_MFP_M281fdw_5543F1-DeviceN..\' already exists
   E [07/Feb/2023:11:47:24 +0100] [Client 17] Returning IPP 
client-error-not-possible for CUPS-Create-Local-Printer (ipp://localhost/) from 
localhost.
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  7 12:10:42 2023
  InstallationDate: Installed on 2020-06-20 (961 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  Lpstat:
   device for HP_Color_LaserJet_MFP_M281fdw_5543F1: 
implicitclass://HP_Color_LaserJet_MFP_M281fdw_5543F1/
   device for HP_ColorLaserJet_MFP_M278-M281: 
hp:/net/HP_ColorLaserJet_MFP_M278-M281?ip=192.168.0.102
   device for HP_ColorLaserJet_MFP_M278-M281_fax: 
hpfax:/net/HP_ColorLaserJet_MFP_M278-M281?ip=192.168.0.102
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M281fdw_5543F1.ppd', 
'/etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281.ppd', 
'/etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281_fax.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M281fdw_5543F1.ppd: Permission 
denied
   grep: /etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281.ppd: Permission denied
   grep: /etc/cups/ppd/HP_ColorLaserJet_MFP_M278-M281_fax.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=05f71b34-3a5a-42e5-adb6-8a11af401188 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to lunar on 2022-12-21 (47 days ago)
  dmi.bios.date: 10/27/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4408
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X570-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Desktop-packages] [Bug 2015529] Re: can't install hp-plugin

*** This bug is a duplicate of bug 2012178 ***
https://bugs.launchpad.net/bugs/2012178

Till, could you check that one? It seems it was fixed in Debian in
https://tracker.debian.org/news/1425292/accepted-
hplip-32210dfsg0-2-source-into-unstable/ and we would need to SRU the
change

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

** Changed in: hplip (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

** This bug has been marked a duplicate of bug 2012178
   toolbox.py crashed with NameError in __readAuthType(): name 
'get_distro_std_name' is not defined

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

Title:
  can't install hp-plugin

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 23.04.
  I need to install plug-in in order to scan documents properly. No problem 
with previous Kubuntu versions.

  -
  | PLUG-IN INSTALLATION FOR HPLIP 3.22.10 |
  --

Option  Description   
--  --
d   Download plug-in from HP (recommended)
p   Specify a path to the plug-in (advanced)  
q   Quit hp-plugin (skip installation)

  Enter option (d=download*, p=specify path, q=quit) ? d

  ---
  | DOWNLOAD PLUGIN |
  ---

  Checking for network connection...
  Downloading plug-in from: 
  Downloading plug-in: [\] 0% Traceback (most recent call 
last):
File "/usr/bin/hp-plugin", line 363, in 
  status, plugin_path, error_str = pluginObj.download(plugin_path, 
plugin_download_callback)
   
^
File "/usr/share/hplip/installer/pluginhandler.py", line 257, in download
  core = core_install.CoreInstall()
 ^^
File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
  self.passwordObj = password.Password(ui_mode)
 ^^
File "/usr/share/hplip/base/password.py", line 94, in __init__
  self.__readAuthType()  # self.__authType
  ^
File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
  distro_name = get_distro_std_name(os_name)
^^^
  NameError: name 'get_distro_std_name' is not defined. Did you mean: 
'get_distro_name'?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: hplip 3.22.10+dfsg0-1
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   W [07/Apr/2023:00:00:13 +0200] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
   W [07/Apr/2023:00:00:13 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Color-LaserJet-Pro-MFP-M176n-Gray..\' already exists
   W [07/Apr/2023:08:52:52 +0200] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
  CurrentDesktop: KDE
  Date: Fri Apr  7 09:00:55 2023
  InstallationDate: Installed on 2023-03-19 (18 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230319)
  Lpstat: device for HP-Color-LaserJet-Pro-MFP-M176n: 
hp:/usb/HP_Color_LaserJet_Pro_MFP_M176n?serial=CND7G8NJJL
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-Color-LaserJet-Pro-MFP-M176n.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP-Color-LaserJet-Pro-MFP-M176n.ppd: Permission denied
  ProcEnviron:
   LANG=it_IT.UTF-8
   LANGUAGE=it:en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic 
root=UUID=baca8e64-c620-410c-8401-dc64ddeef942 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  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:

[Desktop-packages] [Bug 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created

** Merge proposal linked:

https://code.launchpad.net/~slyon/network-manager/+git/network-manager/+merge/423735

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

Title:
The Netplan Everywhere NetworkManager fails to supply Netplan with
networking information until a connection is deleted and re-created

Status in netplan:
Invalid
Status in network-manager package in Ubuntu:
Fix Committed

Bug description:
Steps to reproduce:

1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a
WiFi adapter. (I used Lubuntu Lunar.)
2. Connect to WiFi and install all updates.
3. Enable the Netplan Everywhere PPA and install the updated NetworkManager
from it (further details at
https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3)
4. When the installation finishes, run "sudo netplan get".

Expected result: Networking information related to the WiFi connection
should appear in the "sudo netplan get" output.

Actual result: "sudo netplan get" returns the following:

** (process:4088): WARNING **: 12:41:41.394; Permissions for
/etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration
should NOT be accessible by others.
network:
version: 2
renderer: NetworkManager

End of output. Additionally, the /etc/netplan folder does not contain
files that I would expect to be there that would contain the
networking info.

Additional information:

If I disconnect from WiFi, then delete my WiFi connection entirely in
nmtui, and *then* reconnect to the same WiFi network, "sudo netplan
get" returns the expected networking information. /etc/netplan is also
properly populated after doing this.

This bug seems like it will probably cause unintended behavior after
an upgrade from 23.04 (which uses normal NetworkManager) to 23.10
(which is supposed to be using the Netplan Everywhere NetworkManager).
People probably won't know to entirely delete the WiFi and other
connections and then reconnect them in order for the netplan output to
be usable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2010561/+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 2015529] Re: can't install hp-plugin

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

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

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

Title:
  can't install hp-plugin

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 23.04.
  I need to install plug-in in order to scan documents properly. No problem 
with previous Kubuntu versions.

  -
  | PLUG-IN INSTALLATION FOR HPLIP 3.22.10 |
  --

Option  Description   
--  --
d   Download plug-in from HP (recommended)
p   Specify a path to the plug-in (advanced)  
q   Quit hp-plugin (skip installation)

  Enter option (d=download*, p=specify path, q=quit) ? d

  ---
  | DOWNLOAD PLUGIN |
  ---

  Checking for network connection...
  Downloading plug-in from: 
  Downloading plug-in: [\] 0% Traceback (most recent call 
last):
File "/usr/bin/hp-plugin", line 363, in 
  status, plugin_path, error_str = pluginObj.download(plugin_path, 
plugin_download_callback)
   
^
File "/usr/share/hplip/installer/pluginhandler.py", line 257, in download
  core = core_install.CoreInstall()
 ^^
File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
  self.passwordObj = password.Password(ui_mode)
 ^^
File "/usr/share/hplip/base/password.py", line 94, in __init__
  self.__readAuthType()  # self.__authType
  ^
File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
  distro_name = get_distro_std_name(os_name)
^^^
  NameError: name 'get_distro_std_name' is not defined. Did you mean: 
'get_distro_name'?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: hplip 3.22.10+dfsg0-1
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   W [07/Apr/2023:00:00:13 +0200] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
   W [07/Apr/2023:00:00:13 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Color-LaserJet-Pro-MFP-M176n-Gray..\' already exists
   W [07/Apr/2023:08:52:52 +0200] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
  CurrentDesktop: KDE
  Date: Fri Apr  7 09:00:55 2023
  InstallationDate: Installed on 2023-03-19 (18 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230319)
  Lpstat: device for HP-Color-LaserJet-Pro-MFP-M176n: 
hp:/usb/HP_Color_LaserJet_Pro_MFP_M176n?serial=CND7G8NJJL
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-Color-LaserJet-Pro-MFP-M176n.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP-Color-LaserJet-Pro-MFP-M176n.ppd: Permission denied
  ProcEnviron:
   LANG=it_IT.UTF-8
   LANGUAGE=it:en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic 
root=UUID=baca8e64-c620-410c-8401-dc64ddeef942 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  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.:bvr4105:bd07/01/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX: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

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


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

[Desktop-packages] [Bug 2018296] Re: 23.04 org.gnome.Shell@wayland.service dumped randomly

2023-05-02 Thread Paul White

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

** Tags added: lunar wayland

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

Title:
  23.04 org.gnome.Shell@wayland.service dumped randomly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I would like to report an issue with "org.gnome.Shell@wayland.service".
  The process seem to randomly crash with a code dumped, leading to getting 
disconnected from the session.

  1751786184:May 02 12:52:01 lapbios systemd[336486]:
  org.gnome.Shell@wayland.service: Main process exited, code=dumped,
  status=11/SEGV

  I found a similar report on AskUbuntu
  (https://askubuntu.com/questions/1465560/lunar-lobster-wayland-
  crashes) without answer yet.

  I'm running Ubuntu 23.04 on a Razer Blade 15 2019 (i7, RTX 2070). This
  issue appeared after upgrade to 23.04.

  I identified a few cases where the bug occurs, 100% chance when
  dragging a tab in Firefox over the taskbar. Sometimes when dragging an
  icon on the desktop. Sometimes when the screen dim to lock the laptop.

  I am not sure where to find the core dump or crash report. (Apport
  never showed up) I will gladly help gather more information !

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018296/+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 2018155] Re: gnome-magnifier prevents starting a graphical session

2023-05-02 Thread Paul White

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

** Tags added: lunar

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

Title:
  gnome-magnifier prevents starting a graphical session

Status in mutter package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 22.10 to Ubuntu 23.04, I am unable to
  login to my session as I always get the "Oh no! Something has gone
  wrong." error message.

  I have screen magnifier enabled, but disabling it using:
  gsettings set org.gnome.desktop.a11y.applications screen-magnifier-enabled 
false
  makes the issue disappear. I can reproduce the bug inside a virtual machine 
on Windows as well, with different hardware.
  The only piece of log I can find and that might be linked to the issue is:

  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
org.gnome.Shell@x11.service - GNOME Shell on X11...
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating via systemd: service 
name='org.freedesktop.impl.portal.desktop.gtk' 
unit='xdg-desktop-portal-gtk.service' requested by ':1.52' (uid=1000 pid=7773 
comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Activating service name='org.a11y.atspi.Registry' requested 
by ':1.5' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating service name='org.gnome.ScreenSaver' requested by 
':1.55' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Successfully activated service 'org.a11y.atspi.Registry'
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7869]: 
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7863]: Running GNOME 
Shell (using mutter 44.0) as a X11 window and compositing manager
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 'org.gnome.ScreenSaver'
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session[7361]: 
gnome-session-binary[7361]: WARNING: Could not retrieve current screensaver 
active state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient 
disconnected from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session-binary[7361]: 
WARNING: Could not retrieve current screensaver active state: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.impl.portal.desktop.gtk'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.portal.Desktop'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal.service - Portal service.
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: New theme: 
gtk=Yaru icon=Yaru cursor=(null), sound=Yaru
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: All 
available theme snaps installed
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7984]: libEGL warning: 
DRI2: failed to authenticate
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: gnome-shell[7863]: 
segfault at 18 ip 7f7af86b2004 sp 7ffeb1dc3a18 error 4 in 
libmutter-12.so.0.0.0[7f7af864a000+13d000] likely on CPU 15 (core 15, socket 0)
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: Code: 00 00 00 00 66 90 f3 
0f 1e fa 48 63 05 79 67 16 00 48 8b 04 07 c3 f3 0f 1e fa 48 8b 87 40 01 00 00 
c3 0f 1f 40 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 
8b 47 28 c3 0f
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Main process exited, code=dumped, status=11/SEGV
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Failed with result 'core-dump'.
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: Failed to start 
org.gnome.Shell@x11.service - GNOME Shell on X11.
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 3.
  avril 29

[Desktop-packages] [Bug 2011244] Re: emacs launching in GNOME is all messed up

2023-05-02 Thread Bug Watch Updater

** Changed in: emacs
   Status: Unknown => New

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

Title:
  emacs launching in GNOME is all messed up

Status in GNU Emacs:
  New
Status in emacs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the most recent Lunar updates, which I believe include both an
  Emacs update and a GNOME update, I have encountered multiple annoying
  / bizarre problems with launching Emacs in GNOME. In particular:

  1) Sometimes Emacs launches as a tiny window rather than a window of the 
correct size.
  2) Sometimes it gets into a state where when I click on the icon in the dock 
instead of bringing the open Emacs window to the front it launches a new Emacs 
every time I click.
  3) Sometimes it fails to show up in the dock at all when I launch it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: emacs 1:28.2+1-10ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 16:13:14 2023
  InstallationDate: Installed on 2019-08-16 (1302 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: emacs
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/2011244/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

2023-05-02 Thread BloodyIron

SMB1 is disabled on the server/NAS end. And I'm using the out of the box
experience for Ubuntu 23.04. The UX of this whole situation is
effectively broken. And while I know that I can just "killall gvfsd-smb-
browse" to trigger it to restart, that's not the whole point of why this
needs to be fixed.

This needs to be fixed, yes, because of the security aspect. But
primarily because a user shouldn't have to worry about having to kill
gvfsd-smb-browse just to reach an SMB network share using an actually
secure protocol version.

So again, what's the hold-up here? SMB1 is off, and has been for years.

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2018180] Re: nautilus crashing randomly

Here are some more

https://errors.ubuntu.com/oops/195a084d-e77f-11ed-af15-fa163e55efd0
https://errors.ubuntu.com/oops/550a2b24-e6a8-11ed-af10-fa163e55efd0
https://errors.ubuntu.com/oops/0728bcbe-e139-11ed-baca-fa163ef35206

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

Title:
  nautilus crashing randomly

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I recently updated my Ubuntu installation from 22.10 to 23.04, and after 
that, nautilus just crashes randomly. Even right-clicking on it often doesn't 
show up the list of folders as shortcuts.
  I think, this issue is related to some caches, which are from the previous 
version of nautilus. But, that makes it that we cannot upgrade a distro and be 
bug free.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 13:23:37 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1184, 815)'
  InstallationDate: Installed on 2023-02-02 (86 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (8 days ago)
  usr_lib_nautilus:
   file-roller  43.0-1
   nautilus-image-converter 0.4.0-2
   nautilus-share   0.7.5-0.3
   python3-nautilus 4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018180/+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 2018180] Re: nautilus crashing randomly

The link from whoopsie.
https://errors.ubuntu.com/oops/7a540de0-e813-11ed-bb2c-fa163ef35206
https://errors.ubuntu.com/oops/5f10e1c1-e794-11ed-a10d-fa163e993415

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

Title:
  nautilus crashing randomly

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I recently updated my Ubuntu installation from 22.10 to 23.04, and after 
that, nautilus just crashes randomly. Even right-clicking on it often doesn't 
show up the list of folders as shortcuts.
  I think, this issue is related to some caches, which are from the previous 
version of nautilus. But, that makes it that we cannot upgrade a distro and be 
bug free.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 13:23:37 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1184, 815)'
  InstallationDate: Installed on 2023-02-02 (86 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (8 days ago)
  usr_lib_nautilus:
   file-roller  43.0-1
   nautilus-image-converter 0.4.0-2
   nautilus-share   0.7.5-0.3
   python3-nautilus 4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018180/+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

Re: [Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

2023-05-02 Thread Jon

The SMB1 code should be entirely removed from the stack.  It’s insecure and
deprecated everywhere.

On Tue, May 2, 2023 at 8:56 AM BloodyIron <1828...@bugs.launchpad.net>
wrote:

> Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get
> fixed? This is now over 4 years old.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1881780).
> https://bugs.launchpad.net/bugs/1828107
>
> Title:
>   gvfs can't list shares from smb servers that disabled SMB1
>
> Status in gvfs:
>   New
> Status in gvfs package in Ubuntu:
>   Triaged
>
> Bug description:
>   After bug #1778322 is fixed (just needs a gvfs rebuild with newer
>   samba), samba machines will start to show up again in the "windows
>   network" tab in nautilus. But if a server has disabled the SMB1
>   protocol, nautilus will show an error when that server is clicked on,
>   instead of showing the shares list.
>
>   Even with SMB1 disabled, it should still be technically possible to
>   get a share list, since smbclient can do it:
>
>   andreas@nsnx:~$ nmblookup -A 192.168.122.101
>   Looking up status of 192.168.122.101
> D-NO-SMB1   <00> - B 
> D-NO-SMB1   <03> - B 
> D-NO-SMB1   <20> - B 
> ..__MSBROWSE__. <01> -  B 
> WORKGROUP   <00> -  B 
> WORKGROUP   <1d> - B 
> WORKGROUP   <1e> -  B 
>
>   MAC Address = 00-00-00-00-00-00
>
>   andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
>   WARNING: The "syslog" option is deprecated
>
> Sharename   Type  Comment
> -     ---
> print$  Disk  Printer Drivers
> pub_no_smb1 Disk
> IPC$IPC   IPC Service (d-no-smb1 server (Samba,
> Ubuntu))
>   Reconnecting with SMB1 for workgroup listing.
>   protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
>   Failed to connect with SMB1 -- no workgroup available
>
>   andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U
> ubuntu%ubuntu -m NT1
>   WARNING: The "syslog" option is deprecated
>   protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
>
>   andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U
> ubuntu%ubuntu -m SMB2
>   WARNING: The "syslog" option is deprecated
>   Try "help" to get a list of possible commands.
>   smb: \> dir
> .   D0  Fri May  3 18:16:38
> 2019
> ..  D0  Fri May  3 18:15:24
> 2019
> hello.txt   N   21  Fri May  3 18:16:12
> 2019
> hello-from-nsnx.txt A9  Fri May  3 18:16:38
> 2019
>
>   20509264 blocks of size 1024. 13121800 blocks
>   available
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions
>
>

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

2023-05-02 Thread BloodyIron

Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get
fixed? This is now over 4 years old.

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2018297] Re: Auto-Rotation stoped working after suspension

** Tags added: lunar

** Summary changed:

- Auto-Rotation stoped working after suspension
+ ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

** Also affects: iio-sensor-proxy (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: suspend-resume

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

Title:
  ThinkPad Yoga 460 Auto-Rotation stoped working after suspension

Status in gnome-shell package in Ubuntu:
  New
Status in iio-sensor-proxy package in Ubuntu:
  New

Bug description:
  The auto-rotation feature of my Laptop stoped working.

  - screen orientation was in landscape mode 
  - closed the lid of my laptop 
=> laptop entered suspension mode 
  - opened the lid
=> laptop was waking up
  - screen orientation was in portait mode

  I could not change the screen orientation by rotating the laptop
  physically nor change the orientation manually (the "Orientation"
  setting in the "Display Settings" Menu showed no dropdown menu). After
  a quick reboot everything worked fine.

  This are the specs of my Device:

  OS: Ubuntu 23.04 x86_64 
  Host: 20EM000VGE ThinkPad Yoga 460 
  Kernel: 6.2.0-20-generic 
  Resolution: 1920x1080 
  DE: GNOME 44.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  CPU: Intel i7-6500U (4) @ 3.100GHz 
  GPU: Intel Skylake GT2 [HD Graphics 520] 
  Memory: 7682MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018297/+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 2011244] Re: emacs launching in GNOME is all messed up

2023-05-02 Thread Walter Garcia-Fontes

I confirm this issue with the final release of 23.04.

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

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

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

Title:
  emacs launching in GNOME is all messed up

Status in GNU Emacs:
  Unknown
Status in emacs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the most recent Lunar updates, which I believe include both an
  Emacs update and a GNOME update, I have encountered multiple annoying
  / bizarre problems with launching Emacs in GNOME. In particular:

  1) Sometimes Emacs launches as a tiny window rather than a window of the 
correct size.
  2) Sometimes it gets into a state where when I click on the icon in the dock 
instead of bringing the open Emacs window to the front it launches a new Emacs 
every time I click.
  3) Sometimes it fails to show up in the dock at all when I launch it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: emacs 1:28.2+1-10ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 16:13:14 2023
  InstallationDate: Installed on 2019-08-16 (1302 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: emacs
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/2011244/+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 2011244] Re: emacs launching in GNOME is all messed up

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => 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/2011244

Title:
  emacs launching in GNOME is all messed up

Status in GNU Emacs:
  Unknown
Status in emacs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the most recent Lunar updates, which I believe include both an
  Emacs update and a GNOME update, I have encountered multiple annoying
  / bizarre problems with launching Emacs in GNOME. In particular:

  1) Sometimes Emacs launches as a tiny window rather than a window of the 
correct size.
  2) Sometimes it gets into a state where when I click on the icon in the dock 
instead of bringing the open Emacs window to the front it launches a new Emacs 
every time I click.
  3) Sometimes it fails to show up in the dock at all when I launch it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: emacs 1:28.2+1-10ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 16:13:14 2023
  InstallationDate: Installed on 2019-08-16 (1302 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: emacs
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/2011244/+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 2011244] Re: emacs launching in GNOME is all messed up

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

** Changed in: emacs (Ubuntu)
   Status: New => 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/2011244

Title:
  emacs launching in GNOME is all messed up

Status in GNU Emacs:
  Unknown
Status in emacs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the most recent Lunar updates, which I believe include both an
  Emacs update and a GNOME update, I have encountered multiple annoying
  / bizarre problems with launching Emacs in GNOME. In particular:

  1) Sometimes Emacs launches as a tiny window rather than a window of the 
correct size.
  2) Sometimes it gets into a state where when I click on the icon in the dock 
instead of bringing the open Emacs window to the front it launches a new Emacs 
every time I click.
  3) Sometimes it fails to show up in the dock at all when I launch it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: emacs 1:28.2+1-10ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 16:13:14 2023
  InstallationDate: Installed on 2019-08-16 (1302 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: emacs
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/2011244/+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 2018297] [NEW] Auto-Rotation stoped working after suspension

2023-05-02 Thread Dominik Viererbe

Public bug reported:

The auto-rotation feature of my Laptop stoped working.

- screen orientation was in landscape mode 
- closed the lid of my laptop 
  => laptop entered suspension mode 
- opened the lid
  => laptop was waking up
- screen orientation was in portait mode

I could not change the screen orientation by rotating the laptop
physically nor change the orientation manually (the "Orientation"
setting in the "Display Settings" Menu showed no dropdown menu). After a
quick reboot everything worked fine.

This are the specs of my Device:

OS: Ubuntu 23.04 x86_64 
Host: 20EM000VGE ThinkPad Yoga 460 
Kernel: 6.2.0-20-generic 
Resolution: 1920x1080 
DE: GNOME 44.0 
WM: Mutter 
WM Theme: Adwaita 
Theme: Yaru [GTK2/3] 
Icons: Yaru [GTK2/3] 
CPU: Intel i7-6500U (4) @ 3.100GHz 
GPU: Intel Skylake GT2 [HD Graphics 520] 
Memory: 7682MiB

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

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

Title:
  Auto-Rotation stoped working after suspension

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The auto-rotation feature of my Laptop stoped working.

  - screen orientation was in landscape mode 
  - closed the lid of my laptop 
=> laptop entered suspension mode 
  - opened the lid
=> laptop was waking up
  - screen orientation was in portait mode

  I could not change the screen orientation by rotating the laptop
  physically nor change the orientation manually (the "Orientation"
  setting in the "Display Settings" Menu showed no dropdown menu). After
  a quick reboot everything worked fine.

  This are the specs of my Device:

  OS: Ubuntu 23.04 x86_64 
  Host: 20EM000VGE ThinkPad Yoga 460 
  Kernel: 6.2.0-20-generic 
  Resolution: 1920x1080 
  DE: GNOME 44.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  CPU: Intel i7-6500U (4) @ 3.100GHz 
  GPU: Intel Skylake GT2 [HD Graphics 520] 
  Memory: 7682MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018297/+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 2000644] Re: switching workspaces with shortcut sometimes freezes screen

The suggested workaround is:

Settings > Multitasking > Workspaces > Fixed number of workspaces

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

Title:
  switching workspaces with shortcut sometimes freezes screen

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The bottom panel with dots to show which workspace you are on when
  switching with ctrl+alt+arrow sometimes doesn't disappear and gets
  stuck in a half faded or not faded state.  In that state the mouse
  appear stuck and the screen freezes until the super key is pressed to
  show overview or the workspace is switched again.

  Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand,
  Nvidia driver 525.60.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2000644/+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 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks

** Summary changed:

- AnyDesk X11 window at top-right of the screen is invisible and steals mouse 
clicks
+ X11 window at top-right of the screen is invisible and steals mouse clicks

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

Title:
  X11 window at top-right of the screen is invisible and steals mouse
  clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2018180] Re: nautilus crashing randomly

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.

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

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

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

Title:
  nautilus crashing randomly

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I recently updated my Ubuntu installation from 22.10 to 23.04, and after 
that, nautilus just crashes randomly. Even right-clicking on it often doesn't 
show up the list of folders as shortcuts.
  I think, this issue is related to some caches, which are from the previous 
version of nautilus. But, that makes it that we cannot upgrade a distro and be 
bug free.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 30 13:23:37 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1184, 815)'
  InstallationDate: Installed on 2023-02-02 (86 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (8 days ago)
  usr_lib_nautilus:
   file-roller  43.0-1
   nautilus-image-converter 0.4.0-2
   nautilus-share   0.7.5-0.3
   python3-nautilus 4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018180/+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 2012388] Re: AnyDesk X11 window at top-right of the screen is invisible and steals mouse clicks

2023-05-02 Thread Luis Alvarado

Hi Daniel, just in case this is not an Anydesk bug. I installed anydesk
today but I have had the issue since the first day I installed
Ubuntu.23.04. I am saying this because my bug report was marked as
duplicate of this one but it is not an anydesk issue. I did not even
have anydesk installed since today.

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

Title:
  AnyDesk X11 window at top-right of the screen is invisible and steals
  mouse clicks

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

Bug description:
  Hardware Model: Dell Inc. Inspiron 16 Plus 7620
  Firmware version: 1.5.1
  CPU i7-12700H x20
  GPU: Nvidia RTX3060 / MaxQ
  GPU: Intel Alder Lake-P
  Release: Lunar Lobster
  Architecture: AMD64
  Kernel: 6.1.0-16-generic
  GNOME version: 44.rc

  Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue
  with window focus when windows are placed under the top-right system
  tray.

  Since it is hard to explain, I am attaching a screenshot. I am unable to 
click or interact with anything in the area within green rectangle. 
Applications affected:
  - Firefox (snap)
  - Chromium (snap)
  - Vivaldi Browser (deb)
  - Mattermost (snap)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 21 20:35:05 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-01-23 (56 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 44~rc-1ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2018290] Re: Clicking on the top right corner fails

*** This bug is a duplicate of bug 2012388 ***
https://bugs.launchpad.net/bugs/2012388

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2012388, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


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

** This bug has been marked a duplicate of bug 2012388
   AnyDesk X11 window at top-right of the screen is invisible and steals mouse 
clicks

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

Title:
  Clicking on the top right corner fails

Status in Ubuntu:
  New

Bug description:
  Problem is that when any app gets maximized, or uses the half screen
  technique (eg: Drag a window to the left or right side of the screen
  so it half-screen maximizes itself) the top portion of the window can
  not be clicked (left or right clicked). So any button on that area do
  not work. Like something is overlapping the buttons. The solution is
  to drag the window back to a smaller size to use those buttons again.

  It also has a similar issue where, when clicking on the gnome
  extensions at the top or even the options of ubuntu at the top, you
  need to slightly click below them a bit for them to actually register
  the click.

  
  The problem has been mentioned here which is the same one:
  
https://askubuntu.com/questions/1464858/right-corner-at-chrome-not-response-to-mouse-click

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  530.41.03  Thu Mar 16 
19:48:20 UTC 2023
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1)
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  2 03:55:34 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus: nvidia/530.41.03, 6.2.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation AD102 [GeForce RTX 4090] [10de:2684] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. AD102 [GeForce RTX 4090] 
[19da:4675]
  InstallationDate: Installed on 2023-04-20 (11 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUS System Product Name
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=276e1671-8c73-42fc-bf30-ea9c79e82647 ro mitigations=off pci=nommconf 
nvidia-drm.modeset=1 intel_idle.max_cstate=1 ibt=off
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2023
  dmi.bios.release: 9.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0904
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS Z790 HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0904:bd03/29/2023:br9.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ790HERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati:

[Desktop-packages] [Bug 2018160] Re: gnome-shell crashes when top right panel touched on touchscreen

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: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  gnome-shell crashes when top right panel touched on touchscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Version: ubuntu 23.04

  Package: gnome-shell:
Installed: 44.0-2ubuntu3
Candidate: 44.0-2ubuntu3
Version table:
   *** 44.0-2ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expected: I expected the wifi/bluetooth/dark... menu (in the
  upper right hand corner) to popup when I touched it on my touchscreen
  (clicking with a mouse or touchpad works fine, touchscreen press does
  not). This works as intended on Ubuntu 22.04.2 LTS.

  What happened: The menu popped up as intended, but 2 seconds later it
  disappeared, along with the top gnome shell panel (presumably it
  crashed). A few seconds later the gnome panel restores but without the
  menu. Running applications (such as firefox) don't seem to be
  affected.

  
  Running on an Asus Vivobook 14 (touchscreen).

  Tried using both safe mode and proprietary graphic mode with same
  result. Earlier versions of gnome seem to work fine. Same problem
  happens in Fedora too.

  Willing to do additional testing. Really wanna get this working.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 18:06:49 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] 
[1043:13d2]
  LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP470EA_TP470EA
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: TP470EA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP470EA
  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.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP470EA.311:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP470EA_TP470EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP470EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP470EA_TP470EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this

[Desktop-packages] [Bug 2018233] Re: Xorg crash / Wayland

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: xorg (Ubuntu) => ubuntu

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

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

Title:
  Xorg crash / Wayland

Status in Ubuntu:
  Incomplete

Bug description:
  I'm not sure if it's Xorg crashing, i'm using wayland. 
  Clean installation Ubuntu 22.10 and upgraded to 23.04.

  The bug can be re-produced.

  Symptom:
  Moving firefox with ongoing video for example Youtube. Moving the firefox 
window from screen 2 or 3 to screen1 then it crashes 100% of times.

  Screen 1 is in vertical view mode.
  Screen 2 and 3 landscape.

  ##

  unk@unk-ThinkPad-X1-Carbon-Gen-10:~$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  1 15:17:51 2023
  DistUpgraded: 2023-04-23 20:27:46,523 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7]
  InstallationDate: Installed on 2023-03-22 (39 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 21CB00AYMX
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (7 days ago)
  dmi.bios.date: 03/02/2023
  dmi.bios.release: 1.37
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3AET72W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CB00AYMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.18:svnLENOVO:pn21CB00AYMX:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CB00AYMX:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
  dmi.product.family: ThinkPad X1 Carbon Gen 10
  dmi.product.name: 21CB00AYMX
  dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
  dmi.product.version: ThinkPad X1 Carbon Gen 10
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2018233/+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 2000644] Re: switching workspaces with shortcut sometimes freezes screen

2023-05-02 Thread Michał Fita

I confirm freeze on workspace switch with two screens, main being the
external one. In my case it's Ubuntu 23.04, there were no such problems
with 22.04. The "upgrade" solve some other issues, mostly with screen
energy saving, but now this annoying one happens.

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

Title:
  switching workspaces with shortcut sometimes freezes screen

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The bottom panel with dots to show which workspace you are on when
  switching with ctrl+alt+arrow sometimes doesn't disappear and gets
  stuck in a half faded or not faded state.  In that state the mouse
  appear stuck and the screen freezes until the super key is pressed to
  show overview or the workspace is switched again.

  Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand,
  Nvidia driver 525.60.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2000644/+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 2017956] Re: Display Server Preference Icon does not show up in gdm3.

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

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

Title:
  Display Server Preference Icon does not show up in gdm3.

Status in gdm3 package in Ubuntu:
  Invalid

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

   Description: Ubuntu 22.04.2 LTS
   Release: 22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   gdm3/jammy-updates,now 42.0-1ubuntu7.22.04.1 amd64

  3) What you expected to happen
   A preference icon is displayed at the bottom right of the login screen, and 
you can switch between xorg and wayland.

  4) What happened instead
Icon does not show up in gdm3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2017956/+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 2017984] Re: "Save as" window from browser is not in dark mode