date:20220330

See also bug 1778983.

** Tags removed: hirsute
** Tags added: jammy

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

** Changed in: mutter (Ubuntu)
   Status: Won't Fix => Confirmed

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

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

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

Title:
  Windows switch monitor after resuming from sleep

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832958] Re: Quirky preview behavior when autohide is on

** No longer affects: dash-to-dock

** Bug watch removed: github.com/micheleg/dash-to-dock/issues #963
   https://github.com/micheleg/dash-to-dock/issues/963

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

Title:
  Quirky preview behavior when autohide is on

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967182] Re: windows change desktop after lock screen

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

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 1927948, 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.


** Tags added: multimonitor

** This bug has been marked a duplicate of bug 1927948
   Windows switch monitor after resuming from sleep

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

Title:
  windows change desktop after lock screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

BTW the fix is two commits. It won't work if you only use the one
mentioned in comment #13.

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

The crash is bug 1964037 but it's the same fix for this bug. I'll
proposed a distro patch to mutter soon because it seems fairly common
that people plug a monitor into their hybrid laptop.

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

2022-03-30 Thread jeremyszu

Follow-up from comment#12, I can reproduce this issue on I+N (external
hdmi port wires to dGPU) on DELL-Precision-7760.

---
 三  31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc27c980 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bc40 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bc40 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:35 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce0075bf50 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:41 ubuntu-Precision-7760 gnome-shell[2492]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
 三  31 10:57:41 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: 
assertion 'width > 0' failed
 三  31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: 
assertion 'width > 0' failed
 三  31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: 
assertion 'width > 0' failed
 三  31 10:57:42 ubuntu-Precision-7760 gnome-shell[2492]: setup_framebuffers: 
assertion 'width > 0' failed
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faf74004130 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55ce03b87330 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x55cdffba6760 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc2f7df0 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:45 ubuntu-Precision-7760 gnome-shell[2492]: Object 0x7faffc23df40 
of type IBusText has been finalized while it was still owned by gjs, this is 
due to invalid memory management.
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Created gbm renderer 
for '/dev/dri/card1'
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Failed to allocate 
onscreen framebuffer for /dev/dri/card1: Failed to create gbm_surface: 
Operation not permitted
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: GNOME Shell crashed 
with signal 5
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: == Stack trace for 
context 0x55cdfef5c180 ==
 三  31 10:57:49 ubuntu-Precision-7760 gnome-shell[2492]: Failed to create 
fallback offscreen framebuffer: Failed to create texture 2d due to size/format 
constraint
...
 三  31 10:57:56 ubuntu-Precision-7760 gnome-shell[5958]: Running GNOME Shell 
(using mutter 42.beta) as a Wayland display server
---

Which also break the auto-login feature (after auto-login, gnome restart
then screen back to gdm login shell)

$ dpkg -l | grep mutter
ii  gir1.2-mutter-10:amd64 42~beta-1ubuntu2 
   amd64GObject introspection data for Mutter
ii  libmutter-10-0:amd64   42~beta-1ubuntu2 
   amd64window manager library from the Mutter window manager
ii  mutter-common  42~beta-1ubuntu2 
   all  shared files for the Mutter window manager

Hi Daniel,

Do you have a PPA could try your patch like this
https://gitlab.gnome.org/vanvugt/mutter/-/commit/8354289650aa3ae0c531820d3a95251b627f9eb4
?

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967204] Re: "help" app (yelp) just displays a blank window with "Ubuntu Desktop Guide" title on rpi

2022-03-30 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967204

** Tags added: iso-testing

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

Title:
  "help" app (yelp) just displays a blank window with "Ubuntu Desktop
  Guide" title on rpi

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967204] [NEW] "help" app (yelp) just displays a blank window with "Ubuntu Desktop Guide" title on rpi

Public bug reported:

I'm using the jammy beta (20220329) image running on an rpi4 8GB
clicking on the "help" app in the dock launches a window with the title "Ubuntu 
Desktop Guide". The icons for forward/back, bookmarks, search, etc. are all 
visible at the top of the window, but everything else in the window is just a 
blank white area. On amd64, however, it seems to work fine.

I also noticed that if I move the mouse around through the area, the
pointer sometimes changes, and if I hover there for a second, a tooltip
comes up with things like "Start applications" or "Visual overview of
Gnome". I can click on these and it seems to take me forward to
something, because the back icon is no longer greyed out, but I still
can't see any content in the window.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: yelp 42.0-1
ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
Uname: Linux 5.15.0-1003-raspi aarch64
ApportVersion: 2.20.11-0ubuntu79
Architecture: arm64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 21:47:52 2022
ImageMediaBuild: 20220329
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: yelp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 arm64-image iso-testing jammy raspi-image 
wayland-session

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

Title:
  "help" app (yelp) just displays a blank window with "Ubuntu Desktop
  Guide" title on rpi

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967150] Re: gnome-shell crashed with SIGSEGV

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

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 1964458, 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.


** This bug has been marked a duplicate of bug 1964458
   [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from 
js::gc::PostWriteBarrierImpl

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

Title:
  gnome-shell crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967176] Re: gnome-shell crashed with SIGSEGV

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
your system at the time of the report. Please upgrade your system to the
latest package versions. If you still encounter the crash, please file a
new report.

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


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

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

Title:
  gnome-shell crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966921] Re: Display freezes after entering password from login screen

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

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

Title:
  Display freezes after entering password from login screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen

** Tags added: impish

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

Title:
  Ubuntu Dock and Top bar accessible from lockscreen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen

2022-03-30 Thread Launchpad Bug Tracker

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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882353

Title:
  Ubuntu Dock and Top bar accessible from lockscreen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965686] Re: After the laptop comes out of sleep mode, the desktop environment for some reason breaks and appears crashes window

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.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

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


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

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

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

Title:
  After the laptop comes out of sleep mode, the desktop environment for
  some reason breaks and appears crashes window

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965869] Re: Screen only partially locked. Password promt was visible, but switching to window and typing eg in terminal was possible

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

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 1882353, 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.


** This bug has been marked a duplicate of bug 1882353
   Ubuntu Dock and Top bar accessible from lockscreen

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

Title:
  Screen only partially locked. Password promt was visible, but
  switching to window and typing eg in terminal was possible

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

So this is GTK only? GTK4 only?

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967079] Re: gnome-shell crashed with SIGSEGV in app_info_has_action() from g_desktop_app_info_launch_action()

I meant that if you can reproduce the crash then please try disabling
ubuntu-d...@ubuntu.com

Otherwise we should still keep this bug open to avoid duplicates (and
increase collaboration) when the next person encounters the crash.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967079/+attachment/5574678/+files/CoreDump.gz

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV in app_info_has_action() from
  g_desktop_app_info_launch_action()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Committed

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

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

Fixed in mutter 42.1 but we should probably patch it in sooner than that
for jammy.

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Committed

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

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

Title:
  gnome-shell crashes (fatal error logged in create_fallback_offscreen)
  when attempting to enable second monitor on second GPU (Nvidia >= 495)
  in a Wayland session

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2022-03-30 Thread Gunnar Hjalmarsson

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

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

2022-03-30 Thread Matthew Ruffell

Hi everyone, Fady, renbag,

I have been working on this bug on and off for a little while now, but I
am stuck because I can't reproduce what you are all seeing. Having a
reproducer will greatly speed up getting a fix created for this issue.

In my client gvfsd is always started via systemd --user, so I must be
configuring something differently. Can you try out my reproducer and let
me know what you are configuring differently?

Instructions to reproduce:

You will need a 20.04 server instance, and a 20.04 Desktop instance.

To set up the server:

1) Create a fresh 20.04 server instance
2) sudo apt update
3) sudo apt upgrade
4) sudo hostnamectl set-hostname samba-dc
5) sudo vim /etc/hosts
Add an entry with its IP address, e.g.:
192.168.122.199samba-dc samba-dc.example.com
6) sudo apt install -y samba smbclient winbind libpam-winbind libnss-winbind 
krb5-kdc libpam-krb5
Note: skip config of kerberos KDC.
7) sudo rm /etc/krb5.conf
8) sudo rm /etc/samba/smb.conf
9) sudo samba-tool domain provision --server-role=dc --use-rfc2307 
--dns-backend=SAMBA_INTERNAL --realm=samba-dc.EXAMPLE.COM --domain=SAMBA 
--adminpass=Password1
10) sudo cp /var/lib/samba/private/krb5.conf /etc/krb5.conf
11) sudo systemctl mask smbd nmbd winbind
12) sudo systemctl disable smbd nmbd winbind
13) sudo systemctl stop smbd nmbd winbind
14) sudo systemctl unmask samba-ad-dc
15) sudo systemctl start samba-ad-dc
16) sudo systemctl enable samba-ad-dc
17) sudo reboot
18) sudo systemctl stop systemd-resolved
19) sudo systemctl disable systemd-resolved
20) cat << EOF >> /etc/resolv.conf
nameserver 192.168.122.199
search SAMBA
EOF
21) sudo reboot
22) host -t SRV _ldap._tcp.samba-dc.example.com
_ldap._tcp.samba-dc.example.com has SRV record 0 100 389 
samba-dc.samba-dc.example.com.
23) $ smbclient -L localhost -N
Anonymous login successful

Sharename   Type  Comment
-     ---
sysvol  Disk  
netlogonDisk  
IPC$IPC   IPC Service (Samba 4.13.17-Ubuntu)
SMB1 disabled -- no workgroup available
24) $ smbclient //localhost/netlogon -UAdministrator -c 'ls'
Enter SAMBA\Administrator's password: 
  .   D0  Mon Feb 28 04:23:22 2022
  ..  D0  Mon Feb 28 04:23:27 2022

9983232 blocks of size 1024. 7995324 blocks available
25) kinit administrator
Password for administra...@samba-dc.example.com: 
Warning: Your password will expire in 41 days on Mon Apr 11 04:23:27 2022
26) klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal: administra...@samba-dc.example.com

Valid starting ExpiresService principal
02/28/22 04:32:47  02/28/22 14:32:47  
krbtgt/samba-dc.example@samba-dc.example.com
renew until 03/01/22 04:32:44
27)


Create a share:
28) sudo mkdir -p /srv/samba/Demo/
29) sudo vim /etc/samba/smb.conf
[Demo]
path = /srv/samba/Demo/
read only = no
30) sudo chmod 0770 /srv/samba/Demo/


Install a fresh 20.04.4 Desktop instance, and run the following:

31) sudo apt install realmd smbclient
32) sudo vim /etc/hosts
Add an entry with its IP address, e.g.:
192.168.122.199samba-dc samba-dc.example.com
33) sudo realm join --user=Administrator SAMBA-DC.EXAMPLE.COM
$ smbclient -U Administrator //samba-dc.example.com/demo
Enter WORKGROUP\Administrator's password: 
Try "help" to get a list of possible commands.
smb: \> ls
  .   D0  Mon Mar  7 15:20:30 2022
  ..  D0  Mon Mar  7 15:20:30 2022

9983232 blocks of size 1024. 7686220 blocks available
$ smbclient //samba-dc.example.com/demo -k
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in 
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER

Now open Nautilus, add smb://samba-dc.example.com/demo as a share, and you will
be faced with a dialog box asking for username / password credentials. Close
Nautilus.

Let's get a kerberos ticket:

$ kinit administra...@samba-dc.example.com
Password for administra...@samba-dc.example.com: 
Warning: Your password will expire in 11 days on Mon 11 Apr 2022 16:23:27
$ smbclient //samba-dc.example.com/demo -k
Try "help" to get a list of possible commands.
smb: \> ls
  .   D0  Mon Mar  7 15:20:30 2022
  ..  D0  Mon Mar  7 15:20:30 2022

9983232 blocks of size 1024. 7616832 blocks available

34) Open Nautilus, add smb://samba-dc.example.com/demo as a share, and it will
open correctly using kerberos credentials.

When I look at my process list, gvfsd is where it is suppose to be, under the
systemd user session:

$ ps auxf
...
ubuntu  1207  0.5  0.2  19008 10128 ?Ss   12:12   0:00 
/lib/systemd/systemd --user
ubuntu  1208  0.0  0.0 179632  3544 ?S12:12   0:00  \_ (sd-pam)
ubuntu

[Bug 1967182] [NEW] windows change desktop after lock screen

2022-03-30 Thread Matthieu Clemenceau

Public bug reported:

Hello,

So I have a dual screen setup where my primary monitor isn't the laptop
built-in but an external wide screen.

So I would have 2 or 3 virtual desktop with various content organized
(mail, development, personal)

After a long break with the screen locked when I come back to my
computer, my windows have moved from Virtual desktop to another and
sometime from one monitor to another.

let me know if you need more information

Matthieu

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 16:44:57 2022
DisplayManager: gdm3
InstallationDate: Installed on 2020-01-05 (815 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-01-27 (62 days ago)

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


** Tags: amd64 apport-bug jammy third-party-packages uec-images wayland-session

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

Title:
  windows change desktop after lock screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

I reported this issue to Mesa also.

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

2022-03-30 Thread Adrian Perez

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

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

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

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

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

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

I hope this helps :)

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

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

iris

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

zink

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

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

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

i965

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

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2022-03-30 Thread Tim Wetzel

Two points
-Have not been able to find a combination of logind parameters that avoids this 
issue.
-Have also found that this problem is not limited to HDMI connection. It has 
also now appeared on a T480 in UltraDock using DP++ connection to external 
display. Again, the external display is the primary (only) monitor in use: 
laptop is docked, lid down, and uses external wireless Lenovo keyboard and 
mouse. On power up, after entering Ubuntu password, the system suspends

Please fix this!!! This has been an issue ever since the Ubuntu 20.04
updates September 2020!!!

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967176] gnome-shell crashed with SIGSEGV

2022-03-30 Thread Apport retracing service

Stacktrace:
 #0  0x7ffbc79eda7c in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60
StacktraceSource: #0  0x7ffbc79eda7c in ?? ()
StacktraceTop: ?? ()


** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967176] [NEW] gnome-shell crashed with SIGSEGV

2022-03-30 Thread Vladimir

Public bug reported:

1) lsb_release -rd
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04

2) apt-cache policy gnome-shell
gnome-shell:
  Installed: 42~beta-1ubuntu3
  Candidate: 42~beta-1ubuntu3
  Version table:
 *** 42~beta-1ubuntu3 500
500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

nvidia 1030. nvidia-driver-510

3) What you expected to happen
just logout and login again

4) What happened instead
after logout and login again, apport reported this crash.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 22:40:45 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2022-03-25 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0  0x7ffbc79eda7c in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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


** Tags: amd64 apport-crash jammy need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967168] Re: [Wayland] Yelp does not show the documentation

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

Thank you for taking the time to report this bug. I'm marking this a
duplicate of https://launchpad.net/bugs/1966418

** This bug has been marked a duplicate of bug 1966418
   [jammy regression] Evolution does not display message content anymore

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

Title:
  [Wayland] Yelp does not show the documentation

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967174] [NEW] Installing with zfs results in bpool, rpool drives locked on the dock

Public bug reported:

I installed the ubuntu 20220329 jammy beta with zfs root selected. After
installation, there are drives on the dock for the zfs bpool and rpool
(and in my case also a "1.6GB Encrypted" device since I also selected
disk encryption at install time). These don't do anything useful when
you click on them, and the only option when right-clicking is to mount
them, which also doesn't result in anything observable from the UI
(indeed, they should already be in use). Nor are they removable or 'un-
pinnable' from the dock. You're just stuck with them taking up space.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 13:25:07 2022
InstallationDate: Installed on 2022-03-30 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Installing with zfs results in bpool, rpool drives locked on the dock

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965558] Re: Cannot change wallpaper by right-clicking image in dark theme

2022-03-30 Thread Nicholas Harvey

I've just tried this fix in Jammy nightly and it works for me. Thanks!

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

Title:
  Cannot change wallpaper by right-clicking image in dark theme

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967168] Re: [Wayland] Ubuntu-docs does not show the documentation

2022-03-30 Thread lotuspsychje

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

** Changed in: ubuntu-docs (Ubuntu)
   Status: Confirmed => Invalid

** Description changed:

  Ubuntu 22.04 development branch @ 30/03/2022
  
- Opening ubuntu-docs ?-icon does not show the help documentation items on 
Wayland only
+ Opening yelp ?-icon does not show the help documentation items on Wayland only
  on Xorg it works
  
  The items exist, as hovering the mouse pointer over they show tooltips
  but overall the whole window is blank, see screenshot
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-docs 22.04.2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 19:12:52 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- [Wayland] Ubuntu-docs does not show the documentation
+ [Wayland] Yelp does not show the documentation

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

Title:
  [Wayland] Yelp does not show the documentation

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

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

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

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1964795] Re: gnome-keyring-daemon crashed with signal 7

2022-03-30 Thread Marc Deslauriers

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

** Information type changed from Private Security to Public

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

Title:
  gnome-keyring-daemon crashed with signal 7

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965686] Re: After the laptop comes out of sleep mode, the desktop environment for some reason breaks and appears crashes window

2022-03-30 Thread Marc Deslauriers

** Information type changed from Private Security to Public

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

Title:
  After the laptop comes out of sleep mode, the desktop environment for
  some reason breaks and appears crashes window

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965869] Re: Screen only partially locked. Password promt was visible, but switching to window and typing eg in terminal was possible

2022-03-30 Thread Marc Deslauriers

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

** Information type changed from Private Security to Public

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

Title:
  Screen only partially locked. Password promt was visible, but
  switching to window and typing eg in terminal was possible

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966786] Re: login screen shown twice

2022-03-30 Thread BertN45

Maybe switching from wayland to xorg caused the problem.

That menu was only present on the first login screen, so I tried moving
back to Wayland. The double login screen remained and I had the old
issues again with DOSBOX and Conky :(

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

Title:
  login screen shown twice

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966786] Re: login screen shown twice

2022-03-30 Thread BertN45

1. When I reinstalled with "sh autorun.sh", I got two terminals and the
first one said:

bertadmin@vm-ubuntu-2204:/media/bertadmin/VBox_GAs_6.1.32$ sh autorun.sh
# Option “-x” is deprecated and might be removed in a later version of
gnome-terminal.
# Use “-- ” to terminate the options and put the command line to execute after
it.
bertadmin@vm-ubuntu-2204:/media/bertadmin/VBox_GAs_6.1.32$

The Second Terminal executed the install as expected, see also
attachment.

2. When I uninstalled Virtual box with "sh VBoxLinuxAdditions.run uninstall"
the problem disappeared. The boot and login were normal.
But the problem reappeared after a reinstall "sh VBoxLinuxAdditions.run".

3. I have upgraded the system from Ubuntu 20.04. After a while I noticed
that DOSBOX and Conky did not run anymore with wayland, so I moved back
to xorg through the menu in the login screen. According to "the
Internet", it is a known issue with Conky and DOSDOX.

Maybe switching from wayland to xorg caused the problem, but that menu
disappeared from the login screen, so I cant move back to wayland.

** Attachment added: "vbox-issue"

https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+attachment/5574845/+files/vbox-issue

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

Title:
login screen shown twice

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

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967150] Re: gnome-shell crashed with SIGSEGV

2022-03-30 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967150

** Tags added: iso-testing

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

Title:
  gnome-shell crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1881712] Re: gnome-software says connection is metered while is not

2022-03-30 Thread caio tor

Hello the issue continues with Ubuntu Mate 20.04 while using USB
Thetering( But smartphone is using a WIfi and Not using 4g)

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

Title:
  gnome-software says connection is metered while is not

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967150] gnome-shell crashed with SIGSEGV

2022-03-30 Thread Apport retracing service

Stacktrace:
 #0  0x7f8255af2f44 in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
StacktraceSource: #0  0x7f8255af2f44 in ?? ()
StacktraceTop: ?? ()


** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2022-03-30 Thread Sebastien Bacher

Upstream gave some debugging hints

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

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

You could try putting

g_object_unref (user);

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


Could you give it a try?

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967150] Re: gnome-shell crashed with SIGSEGV

Marking public since this was from a live session in qemu and did not
yet contain anything I'm concerned about.

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

Title:
  gnome-shell crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967150] [NEW] gnome-shell crashed with SIGSEGV

Public bug reported:

This was running a live session of the jammy beta candidate image
20220329.1 in qemu. I let it sit for a bit after booting, came back to
the session and came out of the screen blank and saw it reporting this
crash had occurred.  The session has been up 41 minutes but the files in
/var/crash are timestamped from just a few minutes ago so I think it may
have happened coming out of the screen blank.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 14:31:13 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'), 
('xkb', 'cm'), ('xkb', 'gb')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
 PATH=(custom, no user)
 LANG=C.UTF-8
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SegvAnalysis:
 Segfault happened at: 0x7f8255af2f44:  mov(%rsi),%rax
 PC (0x7f8255af2f44) ok
 source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0  0x7f8255af2f44 in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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


** Tags: amd64 apport-crash jammy need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

Ubuntu 21.04 is no longer supported. If you are using 21.04, please upgrade to 
21.10.
https://wiki.ubuntu.com/Releases

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/36812

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

2022-03-30 Thread renbag

I see the same problem with Ubuntu 20.04 and 22.04, inside an Active Directory 
domain.
With slow machines (e.g. with rotational hard disks) it is always present; with 
fast machines (with SSDs) it is randomly present, maybe because it depends also 
on the time needed to contact the domain controller.

(I'm using a cinnamon desktop and I do not have ibus installed)
I have applied the following workaround:
copy /usr/lib/systemd/user/gvfs-daemon.service to 
/etc/systemd/user/gvfs-daemon.service
insert in the last file the following line, at the start of the [Service] 
section:

ExecStartPre=bash -c "for i in echo {1..20} ; do if [ $(env | grep
KRB5CCNAME) == "" ]; then sleep 0.2 ; fi ; done"

In this way it is possible to browse the network with Nemo or Nautilus,
without asking for user authentication.

When the workaround is not present I see this message in
/var/log/syslog:

Mar 30 10:30:36 pc000327 gvfsd[2656]: got no contact to IPC$
Mar 30 10:30:39 pc000327 gvfsd[2672]: Kerberos auth with 'aduser@WORKGROUP' 
(WORKGROUP\aduser) to access '10.1.0.107' not possible

(Here kerberos is not aware of the real domain name and tries the
generic WORKGROUP)

I report here also the relevant processes in the case of no workaround:

USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
...
root 977  0.0  0.4  78692 19508 ?Ss   12:52   0:00 
/usr/sbin/winbindd --foreground --no-process-group
root 985  0.0  0.2  78596 11168 ?S12:52   0:00 winbindd: 
domain child [PC000327]
root 989  0.1  0.7 105008 28716 ?Ss   12:52   0:00 
/usr/sbin/smbd --foreground --no-process-group
root 990  0.0  0.4  79840 17180 ?S12:52   0:00 winbindd: 
domain child [DOMAIN]
root 994  0.0  0.4  80464 16344 ?S12:52   0:00 winbindd: 
idmap child
root1002  0.0  0.5  97132 20524 ?S12:52   0:00 
/usr/lib/x86_64-linux-gnu/samba/samba-bgqd --ready-signal-fd=48 
--parent-watch-fd=12 --debuglevel=0 -F
root1014  1.2  2.5 153464 99180 ?S12:52   0:01 
/usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
root1015  0.0  0.3  98056 14612 ?S12:52   0:00 
/usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files
root1021  0.1  0.2  57304  8144 ?Ss   12:52   0:00 
/lib/systemd/systemd-logind
root1121 15.2  2.7 272756 108420 ?   S12:52   0:18 
/usr/libexec/sssd/sssd_be --domain addomain.it --uid 0 --gid 0 --logger=files
root1213  0.0  0.2 190492 11168 ?Sl   12:53   0:00 lightdm 
--session-child 12 19
root1271  0.0  0.4 138968 16544 ?Ss   12:53   0:00 
/usr/libexec/sssd/sssd_pac --logger=files --socket-activated
aduser  1279  0.5  0.2  17388 10136 ?Ss   12:53   0:00 
/lib/systemd/systemd --user
aduser  1292  0.6  0.1  29736  5824 ?Ss   12:53   0:00 
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
aduser  1294  0.0  0.1 241124  7680 ?Sl   12:53   0:00 
/usr/bin/gnome-keyring-daemon --daemonize --login
aduser  1298  0.1  0.2 240844  8672 ?Ssl  12:53   0:00 
/usr/libexec/gvfsd
aduser  1305  0.0  0.1 380884  7012 ?Sl   12:53   0:00 
/usr/libexec/gvfsd-fuse /run/user/1136602666/gvfs -f
aduser  1314  0.6  0.6 376912 27500 ?Ssl  12:53   0:00 
cinnamon-session --session cinnamon
aduser  1326  1.5  0.6 707460 26600 ?SNsl 12:53   0:00 
/usr/libexec/tracker-miner-fs-3
aduser  1372  0.0  0.2 325748 10224 ?Ssl  12:53   0:00 
/usr/libexec/gvfs-udisks2-volume-monitor

and when the workaround is present:

USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
...
root 873  0.4  2.5 153440 98936 ?S12:43   0:01 
/usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
root 874  0.0  0.3  98068 14344 ?S12:43   0:00 
/usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files
root 885  0.0  0.3  70704 15060 ?Ss   12:43   0:00 
/usr/sbin/nmbd --foreground --no-process-group
root 973  0.0  0.4  78692 19632 ?Ss   12:43   0:00 
/usr/sbin/winbindd --foreground --no-process-group
root 981  0.0  0.2  78596 11108 ?S12:43   0:00 winbindd: 
domain child [PC000327]
root 982  0.0  0.4  79844 17164 ?S12:43   0:00 winbindd: 
domain child [DOMAIN]
root 986  0.0  0.7 105008 28736 ?Ss   12:43   0:00 
/usr/sbin/smbd --foreground --no-process-group
root1001  0.0  0.4  80464 16344 ?S12:43   0:00 winbindd: 
idmap child
root1004  0.0  0.5  97132 20376 ?S12:43   0:00 
/usr/lib/x86_64-linux-gnu/samba/samba-bgqd --ready-signal-fd=48 
--parent-watch-fd=12 --debuglevel=0 -F
root1010  0.0  0.2 249880  8900 ?Ssl  12:43   0:00 
/usr/libexec/accounts-daemon
root1013  0.0  0.2  57312  7968 ?Ss   12:43   0:00

[Bug 1967127] Re: [FFe] update libarchive to 3.6.0

** Description changed:

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

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

** Description changed:

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

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

Title:
  [FFe] update libarchive to 3.6.0

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

2022-03-30 Thread WildWeasel

I don't understand why hirsute has been removed, I'm using it and just
hit this bug. Please restore the hirsute tag.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/36812

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966410] Re: jañskdlfjñklasdfasdf

2022-03-30 Thread Adolfo Jayme

** Package changed: gimp (Ubuntu) => null-and-void

** Changed in: null-and-void
   Status: New => Invalid

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

Title:
  jañskdlfjñklasdfasdf

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1966410/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2022-03-30 Thread Sebastien Bacher

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

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

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

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2022-03-30 Thread Luis Alberto Pabón

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

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967121] [NEW] Glitch on multiple windows selector when auto-hide is enabled

2022-03-30 Thread Paligi

Public bug reported:

Currently testing a fresh install of the beta for 22.04.
All packages are up to date.

When having the dock auto-hide option enabled, a glitch occurs when opening the 
windows selector (when multiple instances of the same program are opened).
Miniatures do open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
miniatures will align with the hidden dock in a non natural way before 
disappearing.

My opinion would be to prevent the dock from auto-hiding when the
miniatures selector opens.

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


** Tags: jammy

** Tags added: jammy

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

Title:
  Glitch on multiple windows selector when auto-hide is enabled

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2022-03-30 Thread Timo Aaltonen

the gnome-chess crash does

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966786] Re: login screen shown twice

2022-03-30 Thread Tim Blokdijk

When installed within VirtualBox with Guest Additions the first login prompt is 
sized 800x600 the second login prompt has dynamic screen resolution so is full 
screen.
With "auto-login" for the user enabled the first 800x600 login prompt is 
skipped.

So my guess is that the Guest Additions code is run after you get
through the first login prompt. Other code might also be run that allows
you to successfully login with a second try?

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

Title:
  login screen shown twice

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966921] Re: Display freezes after entering password from login screen

2022-03-30 Thread Matt Austin

Thanks Daniel.

You were right about the extensions, thank you for the suggestion.

It appears to be caused by the "Nothing to Say" gnome extension. I
uninstalled this, and can now use the wayland session again.

It looks like it's probably the same issue as reported here (by a user running 
20.04):
https://github.com/wbolster/nothing-to-say/issues/49

Thanks for your time, sorry if I wasted it by suggesting the bug was was
mutter-related.

** Bug watch added: github.com/wbolster/nothing-to-say/issues #49
   https://github.com/wbolster/nothing-to-say/issues/49

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

Title:
  Display freezes after entering password from login screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)

2022-03-30 Thread Joseph Maillardet

MUTTER_DEBUG_USE_KMS_MODIFIERS=0
fixes the issue for me too.
I will give a new try without this variable after update 42.0-1ubuntu1 is 
released.

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

Title:
  [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to
  lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers
  failed: Invalid argument)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967082] [NEW] SIGSEGV and out-of-bounds write during processing file via objdump

2022-03-30 Thread Nils

*** This bug is a security vulnerability ***

Public security bug reported:

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

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

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

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

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

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

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

[Bug 1965897] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) from meta_window_actor_queue_destroy() from meta_compositor_real_remove_window() from meta_window_unmanag

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_get_window_type(window=NULL) from
  meta_window_actor_queue_destroy() from
  meta_compositor_real_remove_window() from meta_window_unmanage() from
  meta_display_unmanage_windows()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

Oh the upstream tags 'crocus' and 'iris' suggest it affects old and new
Intel GPUs equally.

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2022-03-30 Thread Sebastien Bacher

Report upstream as
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6229 and git bisected
to https://gitlab.freedesktop.org/mesa/mesa/-/commit/60d95c5d

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

** Changed in: mesa (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Invalid

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

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

The proposed fix is
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341

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

Title:
  gnome-shell crashes (fatal error logged in create_fallback_offscreen)
  when attempting to enable second monitor on second GPU (Nvidia >= 495)
  in a Wayland session

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967064] Re: wayland crash when plugging in external monitor

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

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


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

** This bug has been marked a duplicate of bug 1964037
   gnome-shell crashes (fatal error logged in create_fallback_offscreen) when 
attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland 
session

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

Title:
  wayland crash when plugging in external monitor

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966921] Re: Display freezes after entering password from login screen