date:20230412

** Bug watch added: gitlab.gnome.org/GNOME/tracker-miners/-/issues #265
   https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/265

** Also affects: tracker via
   https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/265
   Importance: Unknown
   Status: Unknown

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

Title:
  tracker-extract-3 crashed with SIGSEGV in
  decorator_item_cache_remove()

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


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

[Bug 2012287] Re: gjs-console crashed with signal 6 in g_assertion_message("assertion failed: (!priv->is_realized)") from g_assertion_message_expr() from gsk_renderer_dispose() from gsk_renderer_dispo

** Summary changed:

- GNOME Characters search provider for GNOME Shell 44 crashes
+ gjs-console crashed with signal 6 in g_assertion_message("assertion failed: 
(!priv->is_realized)") from g_assertion_message_expr() from 
gsk_renderer_dispose() from gsk_renderer_dispose() from g_object_unref()

** Description changed:

  Test Case
  -
  1. From Ubuntu 22.10, install Lunar's glib 2.76.1
  2. Log out
  3. Log back in
  4. Open the GNOME Shell Activities Overview and type the word smile
  5. Close the Activities Overview
  
  What Happens
  
  In my case, if I repeat 4 and 5 several times, I will eventually get an 
apport crash popup dialog reporting that the GNOME Shell search provider for 
GNOME Characters has crashed.
+ 
+ Tracking In
+ ---
+ https://errors.ubuntu.com/problem/031c8ecfc5e8a51d75d6a028554e9c5354792705
  
  Other Info
  --
  This isn't a gjs bug, but I'm leaving the gjs task open since I think apport 
looks for it.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gjs 1.75.90-1
  Uname: Linux 6.1.0-16-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 20 23:04:59 2023
  ExecutablePath: /usr/bin/gjs-console
  ExecutableTimestamp: 1678210639
  ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters 
--gapplication-service
  ProcCwd: /home/solomax
  Signal: 6
  SourcePackage: gjs
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo

** Bug watch added: gitlab.gnome.org/GNOME/gnome-characters/-/issues #124
   https://gitlab.gnome.org/GNOME/gnome-characters/-/issues/124

** Changed in: gnome-characters
   Status: Fix Released => Unknown

** Changed in: gnome-characters
 Remote watch: gitlab.gnome.org/GNOME/gnome-characters/-/issues #122 => 
gitlab.gnome.org/GNOME/gnome-characters/-/issues #124

** Changed in: gnome-characters (Ubuntu Lunar)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-characters (Ubuntu Lunar)
   Status: Triaged => In Progress

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

Title:
  gjs-console crashed with signal 6 in g_assertion_message("assertion
  failed: (!priv->is_realized)") from g_assertion_message_expr() from
  gsk_renderer_dispose() from gsk_renderer_dispose() from
  g_object_unref()

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


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

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

2023-04-12 Thread Matthew Ruffell

** Description changed:

[ 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.
+
+ 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
+ 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.
+ 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
+ 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.
+
+ 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: Denison Barbosa
+ Date: Tue, 21 Mar 2023 15:04:28 +
+ Subject: Removing [Install] section from tracker-extract-3.service
+ Link:
https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3
+
+ Focal requires three additional patches

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

2023-04-12 Thread Matthew Ruffell

** Also affects: gvfs (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: tracker-miners (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: tracker-miners (Ubuntu Focal)
   Status: New => In Progress

** Changed in: tracker-miners (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: tracker-miners (Ubuntu Focal)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

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


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

[Bug 2016007] Re: gnome-shell crashed with SIGSEGV in shell_global_get_display() from update_focus_app() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist

** Summary changed:

- gnome-shell crashed in shell_global_get_display -> update_focus_app -> 
g_closure_invoke:signal_emit_unlocked_R -> g_signal_emit_valist
+ gnome-shell crashed with SIGSEGV in shell_global_get_display() from 
update_focus_app() from g_closure_invoke() from signal_emit_unlocked_R() from 
g_signal_emit_valist

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

Title:
  gnome-shell crashed with SIGSEGV in shell_global_get_display() from
  update_focus_app() from g_closure_invoke() from
  signal_emit_unlocked_R() from g_signal_emit_valist

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


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

[Bug 2000743] Re: kinetic: UI unresponsive while lengthy disk operations complete.

My first thought is that gnome-shell might be blocked waiting to write
log messages to disk, and indeed I do see a number of these in your log:

  https://bugs.launchpad.net/ubuntu/+bugs?field.tag=logspam

Can you open two Terminal windows and run 'top' in one, and 'journalctl
-f /usr/bin/gnome-shell' in the other? Then repeat the bug and see if
anything is hogging the CPU or flooding the log while it's happening.

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 2000743] Re: kinetic: UI unresponsive while lengthy disk operations complete.

** Tags added: performance

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal conn

Maybe fixed in gjs 1.76.1 (Ubuntu 23.10 and later):
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868

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

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

** Changed in: gjs (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/1908429

Title:
  gnome-shell fills syslog: Attempting to run a JS callback during
  garbage collection. This is most likely caused by destroying a Clutter
  actor or GTK widget with ::destroy signal connected, or using the
  destroy(), dispose(), or remove() vfuncs. Because it would crash the
  application, it has been blocked. The offending callback was
  SourceFunc().

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


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

[Bug 2015997] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_client() from meta_wayland_keyboard_get_focus_client() from owner_changed_cb()

Maybe related to https://gitlab.gnome.org/GNOME/mutter/-/issues/2705

** Summary changed:

- gnome-shell crashes after watching video in Firefox on Telegram website
+ gnome-shell crashed with SIGSEGV in wl_resource_get_client() from 
meta_wayland_keyboard_get_focus_client() from owner_changed_cb()

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

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

** 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/2015997

Title:
  gnome-shell crashed with SIGSEGV in wl_resource_get_client() from
  meta_wayland_keyboard_get_focus_client() from owner_changed_cb()

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


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

[Bug 2012230] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from destroy_data_offer() from destroy_resource()

Generalised slightly to include
https://errors.ubuntu.com/problem/a7398b565431966ef5fd0f64400d9788c819449e

** Summary changed:

- gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() 
from display_from_offer() from destroy_data_offer() from destroy_resource() 
from for_each_helper()
+ gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() 
from display_from_offer() from destroy_data_offer() from destroy_resource()

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_wayland_compositor_get_context() from display_from_offer() from
  destroy_data_offer() from destroy_resource()

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


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

[Bug 2012974] Re: gnome-shell crashed with SIGSEGV at ...90ffb

Still happening (bug 2012974) even with the fix for bug 1974293.

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

Title:
  gnome-shell crashed with SIGSEGV at ...90ffb

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


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

[Bug 2016051] Re: /usr/bin/gnome-shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:wl_resource_destroy

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

** This bug has been marked a duplicate of bug 2012230
   gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() 
from display_from_offer() from destroy_data_offer() from destroy_resource()

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:wl_resource_destroy

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


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

[Bug 2016051] [NEW] /usr/bin/gnome-shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:wl_resource_destroy

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
44.0-2ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/a7398b565431966ef5fd0f64400d9788c819449e 
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: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lunar

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:wl_resource_destroy

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


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

Note to self:

One possible explanation here is that we're setting this twice in the
same commit, which some drivers might reject(?):

Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting connector 79 
(/dev/dri/card0) property 'CRTC_ID' (20) to 0
Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting connector 79 
(/dev/dri/card0) property 'CRTC_ID' (20) to 45

Another possible cause might be a bad size in:

Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting CRTC (45, 
/dev/dri/card0) gamma, size: 256
Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting CRTC 45 
(/dev/dri/card0) property 'GAMMA_LUT' (28) to 97

Although that doesn't explain all instances of the error.

Also curious that I don't see any confirmed cases of this bug in 22.10
and later.

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

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


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

Thanks but we do need drm.debug=0xff to make any progress here. You add
it in /etc/default/grub as part of GRUB_CMDLINE_LINUX_DEFAULT and then
run:

  sudo update-grub

and reboot.

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

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


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

[Bug 2015863] Re: authentication prompt does not respect monitor scaling when there are multiple monitors

I think it's too soon to set a closed status that will hide the bug from
other people. Let's keep it open to avoid duplicates. Also I'm not
convinced this can't/won't be fixed.

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

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

Title:
  authentication prompt does not respect monitor scaling when there are
  multiple monitors

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


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

[Bug 2015691] Re: gnome-shell crashes with SIGSEGV in meta_wayland_compositor_get_context()

This does look most likely to be bug 2012100 so it probably doesn't hurt
if this one expires.

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

Title:
  gnome-shell crashes with SIGSEGV in
  meta_wayland_compositor_get_context()

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


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

[Bug 2015691] Re: gnome-shell crashes with SIGSEGV in meta_wayland_compositor_get_context()

The link in comment #5 doesn't seem to lead to any known crash. So next
time you experience a crash please follow comment #4 again.

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

Title:
  gnome-shell crashes with SIGSEGV in
  meta_wayland_compositor_get_context()

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


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

[Bug 2011251] Re: gnome-shell gets into state where clicking on window title bars doesn't raise them

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

** Tags added: fixed-in-mutter-44.1 fixed-upstream

** Project changed: gnome-shell => mutter

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

Title:
  gnome-shell gets into state where clicking on window title bars
  doesn't raise them

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


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

[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

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

** Tags added: fixed-in-mutter-44.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/2013216

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

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


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

[Bug 2016046] [NEW] connecting to samba fileshare fails if smb1(now deprecated) is not supported by the server

2023-04-12 Thread beadon

Public bug reported:

When connecting with Nautilus to "smb://hostname.lan/" note - not the
full path to the samba share, and this is a resolvable ".lan" name
handled by the local DNS server - then gvfsd fails, and doesn't send a
proper error back to nautilus.  This display in Nautilus is simply
"Folder is empty"


Apr 12 19:31:31 semiauto dbus-daemon[729]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1635' (uid=1000 
pid=381751 comm="/usr/bin/nautilus --gapplication-service" label="unconfined")
Apr 12 19:31:31 semiauto gnome-shell[1916]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
Apr 12 19:31:31 semiauto systemd[1]: Starting Hostname Service...
Apr 12 19:31:31 semiauto dbus-daemon[729]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Apr 12 19:31:31 semiauto systemd[1]: Started Hostname Service.
Apr 12 19:31:42 semiauto nautilus[381751]: GtkText - did not receive a 
focus-out event.#012If you handle this event, you must 
return#012GDK_EVENT_PROPAGATE so the default handler#012gets the event as well
Apr 12 19:31:42 semiauto gvfsd[171389]: smbXcli_negprot_smb1_done: No 
compatible protocol selected by server.
Apr 12 19:32:01 semiauto systemd[1]: systemd-hostnamed.service: Deactivated 
successfully.


Since the client forces the server to use NT1 protocols, and the server
is configured to NOT permit this, then hte client connection fails -
ungracefully.

The solution is a few parts :

1. Negotatiate up to higher levels of encryption during connection time.
2. Gracefully provide a message back to nautilus that there is an error in 
connecting for X or Y reason (encryption related, specific to connection to 
this server )

It appears that this has been a known problem now for a few years, here
is a reference to it in 2021 (but in Linux Mint):

https://forums.linuxmint.com/viewtopic.php?t=363511

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gvfs 1.48.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85
Uname: Linux 5.15.0-67-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr 12 19:26:46 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gvfs
UpgradeStatus: Upgraded to jammy on 2022-11-22 (141 days ago)

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


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

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

Title:
  connecting to samba fileshare fails if smb1(now deprecated) is not
  supported by the server

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


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

[Bug 21110] Re: totem-xine mozilla plugin make firefox crash

2023-04-12 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:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/21110

** Tags added: iso-testing

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

Title:
  totem-xine mozilla plugin make firefox crash

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


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

[Bug 2011251] Re: gnome-shell gets into state where clicking on window title bars doesn't raise them

** Changed in: gnome-shell
   Status: New => Fix 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/2011251

Title:
  gnome-shell gets into state where clicking on window title bars
  doesn't raise them

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


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

[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

** Changed in: mutter
   Status: New => Fix 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/2013216

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

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


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

[Bug 2015691] Re: gnome-shell crashes with SIGSEGV in meta_wayland_compositor_get_context()

2023-04-12 Thread Bruce Elrick

BTW, if there is a config change I can do that will help capture more
information the next time this happens such that it will help diagnose
this or bug #2012100 then I'd be happy to do so.

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

Title:
  gnome-shell crashes with SIGSEGV in
  meta_wayland_compositor_get_context()

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


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

[Bug 2015691] Re: gnome-shell crashes with SIGSEGV in meta_wayland_compositor_get_context()

2023-04-12 Thread Bruce Elrick

I guess I should also note explicitly that there was no /var/crash file
for this problem.

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

Title:
  gnome-shell crashes with SIGSEGV in
  meta_wayland_compositor_get_context()

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


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

[Bug 2015691] Re: gnome-shell crashes with SIGSEGV in meta_wayland_compositor_get_context()

2023-04-12 Thread Bruce Elrick

This link is not from this instance of the problem but does appear to be
from a previous similar occurance:
https://errors.ubuntu.com/oops/02171978-cd8e-11ed-adb8-fa163e55efd0

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

Title:
  gnome-shell crashes with SIGSEGV in
  meta_wayland_compositor_get_context()

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


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

[Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal conn

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  gnome-shell fills syslog: Attempting to run a JS callback during
  garbage collection. This is most likely caused by destroying a Clutter
  actor or GTK widget with ::destroy signal connected, or using the
  destroy(), dispose(), or remove() vfuncs. Because it would crash the
  application, it has been blocked. The offending callback was
  SourceFunc().

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


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

[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session

2023-04-12 Thread Mark Burkut

thnx, this helped me resolve problem
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/comments/38
#38

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

Title:
  Using certain xkb-options, e.g. Alt+Shift, for switching input sources
  not reflected by the input source indicator in a wayland session

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


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

[Bug 2012287] Re: GNOME Characters search provider for GNOME Shell 44 crashes

2023-04-12 Thread Shy Zedaka

Had this aswell on a fresh install of Ubuntu 23.04 Beta.

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

Title:
  GNOME Characters search provider for GNOME Shell 44 crashes

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


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

[Bug 2016033] Re: gjs-console crashed with SIGABRT in g_assertion_message_expr()

2023-04-12 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2012287, so 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.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/2016033/+attachment/5663347/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2016033/+attachment/5663350/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2016033/+attachment/5663351/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/2016033/+attachment/5663352/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2016033/+attachment/5663353/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2016033/+attachment/5663354/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 2012287
   GNOME Characters search provider for GNOME Shell 44 crashes

** Tags removed: need-amd64-retrace

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

Title:
  gjs-console crashed with SIGABRT in g_assertion_message_expr()

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


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

[Bug 2016033] [NEW] gjs-console crashed with SIGABRT in g_assertion_message_expr()

2023-04-12 Thread Shy Zedaka

Public bug reported:

this happened on a fresh install of Ubuntu 23.04 beta. i am unsure what
is the cause. but i imagine it can be seen in the error logs, i didn't
check all too much but i thought it would be important to report it
regardless.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gjs 1.76.0-3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 12 19:28:41 2023
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2023-04-12 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters 
--gapplication-service
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
Signal: 6
SourcePackage: gjs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
Title: gjs-console crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

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


** Tags: amd64 apport-crash lunar need-amd64-retrace wayland-session

** 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 gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2016033

Title:
  gjs-console crashed with SIGABRT in g_assertion_message_expr()

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


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-12 Thread aleksey

Hi team and all.

I'm stuck with a similar issue.
The solution with MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 helped me! Thanks guys!

I created logs for you (without kernel parameter: drm.debug=0xff, can't find
how do it).
If somebody wants to help collect logs it easy perform without working screen:
1. Disable authorization after sleep in the settings->privacy->screen.
2. Send Ubuntu sleep.
3. Start Ubuntu.

Now goes steps with a black screen but PC looks working:
1. Ctrl + Alt + T for open terminal.
2. Write journalctl -b0 > journal.txt ( I used the UP key for using the last
terminal command).
3. restart your PC.
4. journal.txt will be in the HOME directory.

Good luck all us!

** Attachment added: "journal.txt"

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/566/+files/journal.txt

** Attachment removed: "journal.txt"

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5663331/+files/journal.txt

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

Title:
Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
Argument invalide] [drmModeAtomicCommit: Invalid argument]

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

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

[Bug 2015863] Re: authentication prompt does not respect monitor scaling when there are multiple monitors

This is something that will fix automatically when you enable the
"fractional scaling" even though you're not using fractional values, so
I feel that's something that we won't change as upstream integer scaling
is very likely being deprecated in non-x11.

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

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

Title:
  authentication prompt does not respect monitor scaling when there are
  multiple monitors

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


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

[Bug 2012991] Re: Insensitive items in system tray menus not visible

** Description changed:

- If you use the multicast system tray menu the text on the items that are
+ If you use the multipass system tray menu the text on the items that are
  insensitive aren't visible. It appears they have the same colour as the
  background.

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

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Insensitive items in system tray menus not visible

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


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-12 Thread aleksey

Hi team and all.

I'm stuck with the similar issue.
The solution with MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 helped me! Thanks guys!

I created logs for you (I removed MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
before).

If somebody wants to help collect logs it easy perform without working screen:
1. Desable authorization after sleep in the settings->privacy->screen.
2. Send Ubuntu sleep.
3. Start Ubuntu.
Now goes steps with a black screen but PC looks working:
1. Ctrl + Alt + T for open terminal.
2. Write journalctl -b0 > journal.txt ( I used the UP key for using last 
terminal command).
3. restart your PC.
4. journal.txt will be in the HOME directory.

Good luck all us!

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5663331/+files/journal.txt

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

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


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

[Bug 2000743] Re: kinetic: UI unresponsive while lengthy disk operations complete.

2023-04-12 Thread Paul White

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

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 2000743] Re: kinetic: UI unresponsive while lengthy disk operations complete.

I just did an update prior to testing. Yes it is still a problem... not
a big one, but VERY confusing until you figure out the culprit.  I'm
glad to be able to help out in a small way!

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 2000743] monitors.xml.txt

apport information

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

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 2000743] ShellJournal.txt

apport information

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

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 2013106] Re: ftbfs in lunar with glib 2.76

This bug was fixed in the package libfprint - 1:1.94.5+tod1-0ubuntu2

---
libfprint (1:1.94.5+tod1-0ubuntu2) lunar; urgency=medium

  * debian/patches/git_tests_fix.patch:
- cherry pick a fix for the tests failing with the new glib version
  (lp: #2013106)

 -- Sebastien Bacher   Wed, 12 Apr 2023 10:45:01
+0200

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

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

Title:
  ftbfs in lunar with glib 2.76

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


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

[Bug 2000743] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 2000743] Re: kinetic: UI unresponsive while lengthy disk operations complete.

apport information

** Tags added: apport-collected

** Description changed:

  This bug is easily reproducible on my system, a new installation of
  kinetic.
  
  1) Using a large file (my case is > 8gb), via the UI, drag and drop to copy.
  2) When the "pie chart" UI indicator starts filling up, click the pie chart 
UI item to show the speed of the transfer.
  3) Notice, once the pie chart is expanded to show the progress details, it is 
not possible to click on any window to switch applications. One either needs to 
wait for the transfer to complete or dismiss the file transfer progress UI.
  
- While writing this bug, I thought it would be useful to take a
- screenshot using the default method and even that locks up the UI and
- must be dismissed before the UI becomes responsive again.
+ While writing this bug, I thought it would be useful to take a screenshot 
using the default method and even that locks up the UI and must be dismissed 
before the UI becomes responsive again.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu3
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2022-12-06 (127 days ago)
+ InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 43.1-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
+ RelatedPackageVersions: mutter-common 43.0-1ubuntu4
+ Tags:  kinetic
+ Uname: Linux 5.19.0-38-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 2000743] GsettingsChanges.txt

apport information

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

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

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

** Tags added: rls-jj-tracking

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

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

** Also affects: gnome-shell-extension-appindicator (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

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


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

[Bug 2016013] [NEW] New windows don't get centered if Desktop Icons NG is loaded

Public bug reported:

New windows don't get centered if Desktop Icons NG is loaded.

With vanilla GNOME, if an app window is too large for tiling (larger
than a quarter of the screen) then it will be centered by default. But
this doesn't happen when DING is loaded, probably because DING is
incorrectly treated as an app window.

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: lunar

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

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

Title:
  New windows don't get centered if Desktop Icons NG is loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+subscriptions


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

[Bug 1978017] Re: Desktop Icons NG steals keyboard focus from apps launched via search

** Summary changed:

- Broken keyboard navigation in the Power Off dialog if launched via app search
+ Desktop Icons NG steals keyboard focus from apps launched via search

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

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Importance: Low => Medium

** Tags added: focus

** Tags added: lunar

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

Title:
  Desktop Icons NG steals keyboard focus from apps launched via search

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

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

** This bug has been marked a duplicate of bug 1978017
   Desktop Icons NG steals keyboard focus from apps launched via search

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

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

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

** Changed in: gnome-shell-extension-desktop-icons-ng (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/2015768

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

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

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

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

I can reproduce it now. It's the desktop-icons-ng extension stealing
focus from the new window. Sounds related to bug 1978017 and bug 1969598

** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2016011] [NEW] GIMP segmentation fault

2023-04-12 Thread Ed Caputo

Public bug reported:




```
GNU Image Manipulation Program version 2.10.30
git-describe: GIMP_2_10_30
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-11 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr
 --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu 
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.2.0 (Ubuntu 11.2.0-16ubuntu1) 

# Libraries #
using babl version 0.1.92 (compiled against version 0.1.88)
using GEGL version 0.4.34 (compiled against version 0.4.34)
using GLib version 2.72.4 (compiled against version 2.71.1)
using GdkPixbuf version 2.42.8 (compiled against version 2.42.6)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.6 (compiled against version 1.50.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 3877 - Thread 3877 #

[New LWP 3883]
[New LWP 3886]
[New LWP 3887]
[New LWP 3889]
[New LWP 3933]
[New LWP 3963]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7ffeef447050, fd=24) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x7f9d780f4e80 (LWP 3877) "gimp-2.10"   __GI___libc_read 
(nbytes=256, buf=0x7ffeef447050, fd=24) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f9d7766f640 (LWP 3883) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f9d6fd24640 (LWP 3886) "gmain"   0x7f9d78df4d7f in 
__GI___poll (fds=0x559e8a238650, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7f9d7692a640 (LWP 3887) "gdbus"   0x7f9d78df4d7f in 
__GI___poll (fds=0x559e8c21a520, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  5Thread 0x7f9d546f2640 (LWP 3889) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f9d5283a640 (LWP 3933) "threaded-ml" 0x7f9d78df4d7f in 
__GI___poll (fds=0x7f9d48015a10, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7f9d530db640 (LWP 3963) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 7 (Thread 0x7f9d530db640 (LWP 3963) "swap writer"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f9d7908f1d3 in g_cond_wait () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f9d79618c99 in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3  0x7f9d7906fa51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f9d78d70b43 in start_thread (arg=) at 
./nptl/pthread_create.c:442
ret = 
pd = 
out = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140732912656656, 
-7973011147088718526, 14031368576, 11, 140314313951312, 140732912657008, 
7953509230970672450, 7953600160851694914}, mask_was_saved = 0}}, priv = {pad = 
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
#5  0x7f9d78e02a00 in clone3 () at 
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
No locals.

Thread 6 (Thread 0x7f9d5283a640 (LWP 3933) "threaded-ml"):
#0  0x7f9d78df4d7f in __GI___poll (fds=0x7f9d48015a10, nfds=3, timeout=-1) 
at

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

2023-04-12 Thread Raymond Kimathi

Daniel van Vugt (vanvugt) - Thanks for the gjs fix. It works!

sudo apt install --reinstall gjs gnome-shell mutter

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

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

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


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

[Bug 161785] Re: "Location" field should show beginning ... end of path

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/161785

Title:
  "Location" field should show beginning ... end of path

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


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

[Bug 2016007] Re: gnome-shell crashed in shell_global_get_display -> update_focus_app -> g_closure_invoke:signal_emit_unlocked_R -> g_signal_emit_valist

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  gnome-shell crashed in shell_global_get_display -> update_focus_app ->
  g_closure_invoke:signal_emit_unlocked_R -> g_signal_emit_valist

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


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

[Bug 2016007] Re: /usr/bin/gnome-shell:11:shell_global_get_display:update_focus_app:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

Upstream issue with proposed fix: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/6536

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

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

** Summary changed:

- 
/usr/bin/gnome-shell:11:shell_global_get_display:update_focus_app:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
+ gnome-shell crashed in shell_global_get_display -> update_focus_app -> 
g_closure_invoke:signal_emit_unlocked_R -> g_signal_emit_valist

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

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6536
   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/2016007

Title:
  gnome-shell crashed in shell_global_get_display -> update_focus_app ->
  g_closure_invoke:signal_emit_unlocked_R -> g_signal_emit_valist

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


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

[Bug 2016007] [NEW] /usr/bin/gnome-shell:11:shell_global_get_display:update_focus_app:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
44.0-2ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/746bcf4f26f269a08ef5a7b5748fcf8e16bb7a51 
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: gnome-shell (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress


** Tags: lunar

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

Title:
  /usr/bin/gnome-
  
shell:11:shell_global_get_display:update_focus_app:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

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


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

[Bug 2012287] Re: GNOME Characters search provider for GNOME Shell 44 crashes

I think this should improve the situation
https://gitlab.gnome.org/GNOME/gnome-characters/-/merge_requests/92

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

Title:
  GNOME Characters search provider for GNOME Shell 44 crashes

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


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

[Bug 1993125] Re: /usr/bin/gjs-console:6:g_assertion_message:g_assertion_message_expr:gsk_renderer_dispose:g_object_unref:g_object_unref

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

** This bug has been marked a duplicate of bug 2012287
   GNOME Characters search provider for GNOME Shell 44 crashes

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

Title:
  /usr/bin/gjs-
  
console:6:g_assertion_message:g_assertion_message_expr:gsk_renderer_dispose:g_object_unref:g_object_unref

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


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

[Bug 2012550] Re: /usr/bin/gjs-console:6:g_assertion_message:g_assertion_message_expr:gsk_renderer_dispose:gsk_renderer_dispose:g_object_unref

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

** This bug has been marked a duplicate of bug 2012287
   GNOME Characters search provider for GNOME Shell 44 crashes

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

Title:
  /usr/bin/gjs-
  
console:6:g_assertion_message:g_assertion_message_expr:gsk_renderer_dispose:gsk_renderer_dispose:g_object_unref

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


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

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

2023-04-12 Thread Jean

Affected here, 22.04.1 with Wayland, didn't happen with X11.

 I thought that this bug was this one:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1627

How can we fix this? Is there any possible workaround?

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

Title:
  Dock displaying over window after resuming from blank screen

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


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

[Bug 161785] Re: "Location" field should show beginning ... end of path

2023-04-12 Thread Paul White

Upstream issue is now at:
https://gitlab.gnome.org/GNOME/rhythmbox/issues/313

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #313
   https://gitlab.gnome.org/GNOME/rhythmbox/issues/313

** Changed in: rhythmbox
   Importance: Wishlist => Unknown

** Changed in: rhythmbox
   Status: Expired => Unknown

** Changed in: rhythmbox
 Remote watch: GNOME Bug Tracker #403284 => 
gitlab.gnome.org/GNOME/rhythmbox/issues #313

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/161785

Title:
  "Location" field should show beginning ... end of path

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


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

[Bug 2000743] Re: kinetic: UI unresponsive while lengthy disk operations complete.

2023-04-12 Thread Paul White

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.

Further to your comment #2 I'm moving this to the gnome-shell package
which will bring this issue to the attention of the Desktop Team.

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

  apport-collect 2000743

However, if this issue has since resolved itself then please let us
know.

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

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

** Tags added: kinetic

** Changed in: gnome-shell (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/2000743

Title:
  kinetic: UI unresponsive while lengthy disk operations complete.

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


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

[Bug 2000743] [NEW] kinetic: UI unresponsive while lengthy disk operations complete.

You have been subscribed to a public bug:

This bug is easily reproducible on my system, a new installation of
kinetic.

1) Using a large file (my case is > 8gb), via the UI, drag and drop to copy.
2) When the "pie chart" UI indicator starts filling up, click the pie chart UI 
item to show the speed of the transfer.
3) Notice, once the pie chart is expanded to show the progress details, it is 
not possible to click on any window to switch applications. One either needs to 
wait for the transfer to complete or dismiss the file transfer progress UI.

While writing this bug, I thought it would be useful to take a
screenshot using the default method and even that locks up the UI and
must be dismissed before the UI becomes responsive again.

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


** Tags: bot-comment
-- 
kinetic: UI unresponsive while lengthy disk operations complete.
https://bugs.launchpad.net/bugs/2000743
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

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

[Bug 2016000] [NEW] Settings > Online Accounts > Add Google Account > foreverloading password prompt

2023-04-12 Thread you-nerd

Public bug reported:

when trying to add a google account in Settings > Online Accounts, it is
forever stuck on loading.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-control-center 1:44.0-1ubuntu5
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.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 12 21:26:57 2023
InstallationDate: Installed on 2023-04-12 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230412)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug lunar

** Attachment added: "Screenshot from 2023-04-12 21-29-08.png"
   
https://bugs.launchpad.net/bugs/2016000/+attachment/5663265/+files/Screenshot%20from%202023-04-12%2021-29-08.png

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

Title:
  Settings > Online Accounts > Add Google Account > foreverloading
  password prompt

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


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

[Bug 2014136] Re: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)]

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

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

Title:
  gnome-shell[957]: message repeated 2 times: [
  (../src/backends/native/meta-onscreen-
  native.c:283):page_flip_feedback_ready: runtime check failed:
  (!onscreen_native->gbm.next_fb)]

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


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

[Bug 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]

** Changed in: gnome-shell (Ubuntu)
Milestone: ubuntu-23.04 => None

** Changed in: accountsservice (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

-- 
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:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  free_fetch_user_request() [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 2012230] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from destroy_data_offer() from destroy_resource() from for_each_helper()

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_wayland_compositor_get_context() from display_from_offer() from
  destroy_data_offer() from destroy_resource() from for_each_helper()

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

Yes it's a lot but often that's enough for us to identify the problem
without needing to ask you questions. Unfortunately not this time.


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

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

the apport replies really is a lot.

Also regarding bug https://bugs.launchpad.net/bugs/1997550, I also don't
have an always on top window.

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

Submitted the report produced using the apport-collect.

Also this is the report for the gnome-shell.

** Attachment added: "error.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015768/+attachment/5663217/+files/error.txt

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015863] Re: authentication prompt does not respect monitor scaling when there are multiple monitors

** Tags added: multimonitor

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

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

Title:
  authentication prompt does not respect monitor scaling when there are
  multiple monitors

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


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

[Bug 2015768] monitors.xml.txt

apport information

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

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] ShellJournal.txt

apport information

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

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] GsettingsChanges.txt

apport information

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

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  As per my thread on askubuntu,
  https://askubuntu.com/questions/1463079/lunar-lobster-beta-application-
  window-not-active-highlighted-when-running-from
  
  
  1) farr@farr-RedmiBook:~$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04
  
  On Lunar Lobster Beta build, if you run apps from the gnome shell /
  search, the app is not active/highlighted automatically. It will not be
  on top of other app window.
  
  Example: Running terminal application from the search. When the terminal
  window loaded, you can't directly type on the terminal. Need to click on
  the icon first to activate the window.
  
  Uploaded the video to streamable, but it will expire in a day.
  https://streamable.com/l1pa8n
  
  Thanks.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.26.0-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 23.04
+ InstallationDate: Installed on 2023-04-07 (5 days ago)
+ InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
+ Package: gnome-shell 44.0-2ubuntu3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+ ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
+ RelatedPackageVersions: mutter-common 44.0-2ubuntu3
+ Tags:  lunar wayland-session
+ Uname: Linux 6.2.0-19-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sudo users
+ _MarkForUpload: True

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

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

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 2013106] Re: ftbfs in lunar with glib 2.76

2023-04-12 Thread Sebastien Bacher

Fix uploaded for libfprint which should also resolve the fprintd issue

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

** Changed in: fprintd (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  ftbfs in lunar with glib 2.76

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


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

[Bug 2015865] Re: window size changing randomly

Looks a lot like 'tiling-assist...@ubuntu.com' is to blame. Hopefully
it's not enabled by default in lunar final.

** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
tiling-assistant (Ubuntu)

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

Title:
  window size changing randomly

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


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

[Bug 2015768] Re: Application Window Not Active/Highlighted Automatically when Running from Gnome Shell

I can't seem to reproduce the bug. Please run this command to collect
more system info:

  apport-collect 2015768

and in future please consider reporting bugs using the 'ubuntu-bug'
command.

See also bug 1997550.

** Tags added: focus

** Changed in: gnome-shell (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/2015768

Title:
  Application Window Not Active/Highlighted Automatically when Running
  from Gnome Shell

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


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

[Bug 1993881] Re: shotwell does not support file format WebP

2023-04-12 Thread Jens Georg

Did you patch it to use the gdk-pixbuf-webp loader? (If so, great, then
I don't have to do it) - if not and you took the patches from master,
it's not necessary, it decodes webp itself

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

Title:
  shotwell does not support file format WebP

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


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

[Bug 2015743] Re: Default Ubuntu (gnome) desktop doesn't follow systemd-inhibit

If you're using Wayland then the issue is bug 1740771
(https://gitlab.gnome.org/GNOME/mutter/-/issues/20)

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

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

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

Title:
  Default Ubuntu (gnome) desktop doesn't follow systemd-inhibit

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


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

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

This bug was fixed in the package gjs - 1.76.0-3

---
gjs (1.76.0-3) experimental; urgency=medium

  * debian/patches: Drop patch causing GNOME Characters not to show emojis
(LP: #2015948)

gjs (1.76.0-2) experimental; urgency=medium

  [ Daniel van Vugt ]
  * Add context-Clear-all-vectors-of-JS-Heap-on-dispose.patch (LP: #1974293)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Do not leak GVariants and other handled objects
(LP: #1991709, #2012978)

 -- Marco Trevisan (Treviño)   Wed, 12 Apr 2023
05:40:15 +0200

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

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

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

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


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

[Bug 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

This bug was fixed in the package gjs - 1.76.0-3

---
gjs (1.76.0-3) experimental; urgency=medium

  * debian/patches: Drop patch causing GNOME Characters not to show emojis
(LP: #2015948)

gjs (1.76.0-2) experimental; urgency=medium

  [ Daniel van Vugt ]
  * Add context-Clear-all-vectors-of-JS-Heap-on-dispose.patch (LP: #1974293)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Do not leak GVariants and other handled objects
(LP: #1991709, #2012978)

 -- Marco Trevisan (Treviño)   Wed, 12 Apr 2023
05:40:15 +0200

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

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

Title:
  gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

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


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

[Bug 2012230] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from destroy_data_offer() from destroy_resource() from for_each_helper()

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

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2708
   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/2012230

Title:
  gnome-shell crashed with SIGSEGV in
  meta_wayland_compositor_get_context() from display_from_offer() from
  destroy_data_offer() from destroy_resource() from for_each_helper()

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


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

[Bug 2012100] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64()

Tracking in
https://errors.ubuntu.com/problem/d525586b43c9aeae86d5c9c7bb28ba925afb

** Summary changed:

- gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() 
from display_from_offer() from data_offer_receive(mime_type="text/html") from 
ffi_call_unix64()
+ gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() 
from display_from_offer() from data_offer_receive() from ffi_call_unix64()

** Description changed:

+ https://errors.ubuntu.com/problem/d525586b43c9aeae86d5c9c7bb28ba925afb
+ 
  I have this error when I'm connecting to nym-connect (nymtech.net)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~beta-1ubuntu1
  Uname: Linux 5.19.0-21-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 17 18:10:09 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1677216555
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/judemont
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sudo users

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_wayland_compositor_get_context() from display_from_offer() from
  data_offer_receive() from ffi_call_unix64()

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


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

[Bug 2012978] Re: Memory leak

This bug was fixed in the package gjs - 1.76.0-3

---
gjs (1.76.0-3) experimental; urgency=medium

  * debian/patches: Drop patch causing GNOME Characters not to show emojis
(LP: #2015948)

gjs (1.76.0-2) experimental; urgency=medium

  [ Daniel van Vugt ]
  * Add context-Clear-all-vectors-of-JS-Heap-on-dispose.patch (LP: #1974293)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Do not leak GVariants and other handled objects
(LP: #1991709, #2012978)

 -- Marco Trevisan (Treviño)   Wed, 12 Apr 2023
05:40:15 +0200

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

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

Title:
  Memory leak

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


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

[Bug 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors

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

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

Title:
  cursor does not track window when dragging between monitors with
  different scaling factors

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


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

[Bug 2015974] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64() from ffi_call_int()

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

** Summary changed:

- 
/usr/bin/gnome-shell:11:meta_wayland_compositor_get_context:display_from_offer:data_offer_receive:ffi_call_unix64:ffi_call_int
+ gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() 
from display_from_offer() from data_offer_receive() from ffi_call_unix64() from 
ffi_call_int()

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

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

** This bug has been marked a duplicate of bug 2012100
   gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() 
from display_from_offer() from data_offer_receive() from ffi_call_unix64()

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_wayland_compositor_get_context() from display_from_offer() from
  data_offer_receive() from ffi_call_unix64() from ffi_call_int()

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


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

[Bug 2015691] Re: gnome-shell crashes with SIGSEGV in meta_wayland_compositor_get_context()

Sounds like bug 2012230 or bug 2015974...

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.

** Summary changed:

- gnome-shell crashes while interacting with firefox
+ gnome-shell crashes with SIGSEGV in meta_wayland_compositor_get_context()

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

** Changed in: gnome-shell (Ubuntu)
Milestone: ubuntu-23.04 => None

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

Title:
  gnome-shell crashes with SIGSEGV in
  meta_wayland_compositor_get_context()

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


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

[Bug 2015974] [NEW] gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64() from ffi_call_int()

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
44.0-2ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/d525586b43c9aeae86d5c9c7bb28ba925afb 
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: gnome-shell
 Importance: Unknown
 Status: Unknown

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


** Tags: lunar

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_wayland_compositor_get_context() from display_from_offer() from
  data_offer_receive() from ffi_call_unix64() from ffi_call_int()

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


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

[Bug 2015654] Re: Chrome has blank windows for some minutes then it displays who's browsing window finally

Thanks for the bug report. However, Chrome is not distributed by Ubuntu
and so is not supported here. Please report Chrome bugs at
https://bugs.chromium.org/p/chromium/issues/list

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

** Changed in: 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/2015654

Title:
  Chrome has blank windows for some minutes then it displays who's
  browsing window finally

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


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

[Bug 2015637] Re: gnome shell often freeze after wake up from mode sleep an after press super button

Thanks for the bug report. Next time the freeze happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.


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

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

** Tags added: amdgpu

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

Title:
  gnome shell often freeze after wake up from mode sleep an after press
  super button

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


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

[Bug 2015534] Re: totem crashed with SIGSEGV in gtk_tree_store_get_value()

Tracking in
https://errors.ubuntu.com/problem/697e848909ae84313dc5a1775f29739c17b3e570

** Description changed:

- crash without knowing the exact problem
+ https://errors.ubuntu.com/problem/697e848909ae84313dc5a1775f29739c17b3e570
  
  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: totem 43.0-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  7 07:50:46 2023
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2023-04-07 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230406)
  JournalErrors:
-  avril 07 07:50:36 hostname kernel: kauditd_printk_skb: 52 callbacks 
suppressed
-  avril 07 07:50:41 hostname kernel: kauditd_printk_skb: 50 callbacks 
suppressed
-  avril 07 07:50:46 hostname kernel: kauditd_printk_skb: 52 callbacks 
suppressed
-  avril 07 07:50:51 hostname kernel: kauditd_printk_skb: 51 callbacks 
suppressed
+  avril 07 07:50:36 hostname kernel: kauditd_printk_skb: 52 callbacks 
suppressed
+  avril 07 07:50:41 hostname kernel: kauditd_printk_skb: 50 callbacks 
suppressed
+  avril 07 07:50:46 hostname kernel: kauditd_printk_skb: 52 callbacks 
suppressed
+  avril 07 07:50:51 hostname kernel: kauditd_printk_skb: 51 callbacks 
suppressed
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
-  LANG=fr_FR.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  SegvAnalysis:
-  Segfault happened at: 0x7effc770d280:mov(%rdi),%rdi
-  PC (0x7effc770d280) ok
-  source "(%rdi)" (0x556009d62cb5) not located in a known VMA region (needed 
readable region)!
-  destination "%rdi" ok
+  Segfault happened at: 0x7effc770d280:mov(%rdi),%rdi
+  PC (0x7effc770d280) ok
+  source "(%rdi)" (0x556009d62cb5) not located in a known VMA region (needed 
readable region)!
+  destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
-  ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
-  ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
-  gtk_tree_model_get_valist () from /lib/x86_64-linux-gnu/libgtk-3.so.0
-  gtk_tree_model_get () from /lib/x86_64-linux-gnu/libgtk-3.so.0
-  ?? () from /lib/x86_64-linux-gnu/libtotem.so.0
+  ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
+  ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
+  gtk_tree_model_get_valist () from /lib/x86_64-linux-gnu/libgtk-3.so.0
+  gtk_tree_model_get () from /lib/x86_64-linux-gnu/libgtk-3.so.0
+  ?? () from /lib/x86_64-linux-gnu/libtotem.so.0
  Title: totem crashed with SIGSEGV in gtk_tree_model_get_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'
  separator:

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

Title:
  totem crashed with SIGSEGV in gtk_tree_store_get_value()

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


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

[Bug 2015534] Re: totem crashed with SIGSEGV in gtk_tree_store_get_value()

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

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

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

Title:
  totem crashed with SIGSEGV in gtk_tree_store_get_value()

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


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

[Bug 2015540] Re: Loop PCIe Bus Error

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

** This bug has been marked a duplicate of bug 2015670
   Kernel loop PCIe Bus Error on RTL810xE

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

Title:
  Loop PCIe Bus Error

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


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

[Bug 2015969] Re: /usr/bin/totem:11:gtk_tree_store_get_value:gtk_tree_model_sort_get_value:gtk_tree_model_get_valist:gtk_tree_model_get:build_selection_list_foreach

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

** This bug has been marked a duplicate of bug 2015534
   totem crashed with SIGSEGV in gtk_tree_store_get_value()

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

Title:
  
/usr/bin/totem:11:gtk_tree_store_get_value:gtk_tree_model_sort_get_value:gtk_tree_model_get_valist:gtk_tree_model_get:build_selection_list_foreach

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


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

[Bug 2015969] [NEW] /usr/bin/totem:11:gtk_tree_store_get_value:gtk_tree_model_sort_get_value:gtk_tree_model_get_valist:gtk_tree_model_get:build_selection_list_foreach

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
totem.  This problem was most recently seen with package version 43.0-2ubuntu1, 
the problem page at 
https://errors.ubuntu.com/problem/697e848909ae84313dc5a1775f29739c17b3e570 
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: totem (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lunar

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

Title:
  
/usr/bin/totem:11:gtk_tree_store_get_value:gtk_tree_model_sort_get_value:gtk_tree_model_get_valist:gtk_tree_model_get:build_selection_list_foreach

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


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

[Bug 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors

I have looked into this bug before. From what I recall there was a
fundamental conflict between:

 (a) Keeping the absolute cursor position on both monitors' boundaries when 
crossing; and
 (b) Keeping the relative cursor position on the titlebar.

So mutter chose (a) over (b).

More recently however, upstream claim to have solved (changed) it in mutter 
44.1:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2942

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

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

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

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

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

** Tags added: fixed-in-mutter-44.1 fixed-upstream

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

Title:
  cursor does not track window when dragging between monitors with
  different scaling factors

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


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

[Bug 2015479] Re: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array()