date:20241106

[Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8

2024-11-06 Thread Alessandro Astone

** Description changed:

- [Summary]
- On HP ZBook Fury G11 platform preloaded with Ubuntu 22.04. The windowing 
system in "Settings -> About" is Xorg. After doing kernel upgrade from 6.5-oem 
to 6.8-hwe, windowing system become Wayland.
+ [ Impact ]
  
+ On some nvidia hybrid systems, like the HP ZBook Fury G11 platform
+ preloaded with Ubuntu 22.04, the windowing system in "Settings -> About"
+ used to be Xorg but after doing kernel upgrade from 6.5-oem to 6.8-hwe,
+ the windowing system become Wayland.
  
- [Reproduce Steps]
- 1. Update kernel by command "sudo apt install linux-image-oem-22.04d 
linux-modules-nvidia-535-oem-22.04d"
- 2. Reboot system
- 3. After enter desktop, check windowing system via "Settings -> About"
+ There is a race condition in udev rules that makes the default desktop
+ session either Xorg or Wayland depending on the ordering of hardware
+ discovery and modules loading. This would affect both jammy and noble,
+ but being a race condition it is unpredictable which hardware defaults
+ to which desktop session, and the same hardware may behave differently
+ in jammy vs in noble.
  
- [Results]
- Expected: Windowing system remain Xorg
- Actual: Windowing system become Wayland
+ The intended default desktop session was meant to be Wayland, however
+ the vast majority of nvidia hybrid laptops defaulted to Xorg at launch,
+ including and particularly all Ubuntu Certified laptops. For this reason
+ we're considering this a bug and are taking measures to ensure that all
+ nvidia hybrid laptops keep defaulting to Xorg.
+ 
+ The fix removes the udev logic that was trying to make nvidia hybrid
+ laptops specifically prefer Wayland, making that hardware use the same
+ udev rules as nvidia desktops which already default to Xorg.
+ 
+ [ Test Plan ]
+ 
+ 1. Set up a nvidia hybrid laptop with Ubuntu 22.04 or 24.04
+ 2. Install the latest updates, particularly the latest kernel
+ 2. Install the gdm3 update from this bug
+ 3. Create a new a new User on the system
+ 3. Reboot
+ 4. At the log-in screen, select the new User
+ 5. Verify that there is a cogwheel icon at the bottom-right of the screen.
+ 6. Click on the cogwheel icon to open up the menu
+ 7. Verify that the selected option is "Ubuntu"
+ 8. Verify that the alternative option is "Ubuntu on Wayland"
+ 9. Close the menu without changing the selection
+ 10. Log-in
+ 11. Verify via "Settings -> About" that "Windowing System" is X11
+ 
+ [ Where problems could occur ]
+ 
+ The patch only touches the gdm udev rules, only removing some broken udev 
rules that matched specific hardware configurations.
+ At worst, Wayland on nvidia laptops could end up completely hidden away 
rather than opt-in -- it is expected to do so only for nvidia driver versions < 
470.
+ 
+ There should be no regression potential for nvidia desktops or non-
+ nvidia hardware, because such hardware would not have matched the udev
+ rules that are being removed here.

** No longer affects: linux-hwe-6.8 (Ubuntu)

** Also affects: gdm3 (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

** Description changed:

  [ Impact ]
  
  On some nvidia hybrid systems, like the HP ZBook Fury G11 platform
  preloaded with Ubuntu 22.04, the windowing system in "Settings -> About"
  used to be Xorg but after doing kernel upgrade from 6.5-oem to 6.8-hwe,
  the windowing system become Wayland.
  
  There is a race condition in udev rules that makes the default desktop
  session either Xorg or Wayland depending on the ordering of hardware
  discovery and modules loading. This would affect both jammy and noble,
  but being a race condition it is unpredictable which hardware defaults
  to which desktop session, and the same hardware may behave differently
  in jammy vs in noble.
  
  The intended default desktop session was meant to be Wayland, however
  the vast majority of nvidia hybrid laptops defaulted to Xorg at launch,
  including and particularly all Ubuntu Certified laptops. For this reason
  we're considering this a bug and are taking measures to ensure that all
  nvidia hybrid laptops keep defaulting to Xorg.
  
  The fix removes the udev logic that was trying to make nvidia hybrid
  laptops specifically prefer Wayland, making that hardware use the same
  udev rules as nvidia desktops which already default to Xorg.
  
  [ Test Plan ]
  
  1. Set up a nvidia hybrid laptop with Ubuntu 22.04 or 24.04
  2. Install the latest updates, particularly the latest kernel
- 2. Install the gdm3 update from this bug
+ 2. Install the gdm3 update being tested
  3. Create a new a new User on the system
  3. Reboot
  4. At the log-in screen, select the new User
  5. Verify that there is a cogwheel icon at the bottom-right of the screen.
  6. Click on the cogwheel icon to open up the menu
  7. Verify that the selected option is "Ubuntu"
  8. Verify that the alternative option is "Ubuntu on Wayland"
  9. Close the

[Bug 2085610] Re: gnome-control-center crashes on exit when gtk-theme is not Yaru

2024-11-06 Thread Alessandro Astone

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

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

Title:
  gnome-control-center crashes on exit when gtk-theme is not Yaru

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


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

[Bug 2086779] ProcCpuinfoMinimal.txt

2024-11-06 Thread Heinrich Schuchardt

apport information

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

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

Title:
  epiphany-browser on riscv64 crashes in socket_source_dispatch

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


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

[Bug 2086779] ProcEnviron.txt

2024-11-06 Thread Heinrich Schuchardt

apport information

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

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

Title:
  epiphany-browser on riscv64 crashes in socket_source_dispatch

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


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

[Bug 2086779] Re: epiphany-browser on riscv64 crashes in socket_source_dispatch

2024-11-06 Thread Heinrich Schuchardt

apport information

** Tags added: apport-collected noble

** Description changed:

  On two different riscv64 systems (SiFive HiFive Unmatched, HiFive P550
  Premier) running Ubuntu Noble I experienced crashes in
  socket_source_dispatch() when it invokes a callback function:
  
  Core was generated by `/usr/bin/epiphany'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x003f9319d5d6 in ?? () from 
/lib/riscv64-linux-gnu/libwebkitgtk-6.0.so.4
  [Current thread is 1 (Thread 0x3f8ceca940 (LWP 29863))]
  (gdb) up
  Downloading source file 
/usr/src/glib2.0-2.80.0-6ubuntu3.1/debian/build/deb/../../../gio/gsocket.c
  #1  0x003f982f283a in socket_source_dispatch (source=0x2d4b7f3210, 
callback=0x3f921ca254, user_data=0x2d4d1da7b8) at ../../../gio/gsocket.c:4267   

  warning: 4267   ../../../gio/gsocket.c: No such file or directory
  (gdb) 
  Downloading source file 
/usr/src/glib2.0-2.80.0-6ubuntu3.1/debian/build/deb/../../../glib/gmain.c
  #2  0x003f9847f876 in g_main_dispatch 
(context=context@entry=0x2d49735610) at ../../../glib/gmain.c:3344  
 
  warning: 3344   ../../../glib/gmain.c: No such file or directory
  (gdb) 
  #3  0x003f984823c4 in g_main_context_dispatch_unlocked 
(context=0x2d49735610) at ../../../glib/gmain.c:4152
  4152in ../../../glib/gmain.c
  (gdb) 
  #4  g_main_context_iterate_unlocked (context=context@entry=0x2d49735610, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:4217
  4217in ../../../glib/gmain.c
  (gdb) 
  #5  0x003f984828be in g_main_context_iteration 
(context=context@entry=0x2d49735610, may_block=may_block@entry=1) at 
../../../glib/gmain.c:4282
  4282in ../../../glib/gmain.c
  (gdb) 
  Downloading source file 
/usr/src/glib2.0-2.80.0-6ubuntu3.1/debian/build/deb/../../../gio/gapplication.c
  #6  0x003f983272e4 in g_application_run (application=0x2d4974f960, 
argc=, argv=0x3fe911a678) at ../../../gio/gapplication.c:2712

  warning: 2712   ../../../gio/gapplication.c: No such file or directory
  (gdb) 
  Downloading source file 
/usr/src/epiphany-browser-46.0-2build1/obj-riscv64-linux-gnu/../src/ephy-main.c
  #7  0x002d171ef660 in main (argc=, argv=) 
at ../src/ephy-main.c:459   
   
  warning: 459../src/ephy-main.c: No such file or directory
  (gdb) 
  
  To reproduce:
  
  * Install Ubuntu 24.40, ubuntu-desktop, gdm3, epiphany-browser on SiFive 
HiFive Unmatched board with GPU (such a board is available in the Taipeh lab)
  * Run epiphany-browser and load a complex page (e.g. https://www.faz.net).
  
  Best regards
  
  Heinrich
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.28.1-0ubuntu3.1
+ Architecture: riscv64
+ CasperMD5json:
+  {
+"result": "skip"
+  }
+ DistroRelease: Ubuntu 24.04
+ InstallationDate: Installed on 2024-11-06 (0 days ago)
+ InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release riscv64 
(20240827.1)
+ Package: epiphany-browser 46.0-2build1
+ PackageArchitecture: riscv64
+ ProcVersionSignature: Ubuntu 6.8.0-48.48.1-generic 6.8.12
+ Tags: noble
+ Uname: Linux 6.8.0-48-generic riscv64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True

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

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

Title:
  epiphany-browser on riscv64 crashes in socket_source_dispatch

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


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

[Bug 2086779] [NEW] epiphany-browser on riscv64 crashes in socket_source_dispatch

2024-11-06 Thread Heinrich Schuchardt

Public bug reported:

On two different riscv64 systems (SiFive HiFive Unmatched, HiFive P550
Premier) running Ubuntu Noble I experienced crashes in
socket_source_dispatch() when it invokes a callback function:

Core was generated by `/usr/bin/epiphany'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x003f9319d5d6 in ?? () from 
/lib/riscv64-linux-gnu/libwebkitgtk-6.0.so.4
[Current thread is 1 (Thread 0x3f8ceca940 (LWP 29863))]
(gdb) up
Downloading source file 
/usr/src/glib2.0-2.80.0-6ubuntu3.1/debian/build/deb/../../../gio/gsocket.c
#1  0x003f982f283a in socket_source_dispatch (source=0x2d4b7f3210, 
callback=0x3f921ca254, user_data=0x2d4d1da7b8) at ../../../gio/gsocket.c:4267   

warning: 4267   ../../../gio/gsocket.c: No such file or directory
(gdb) 
Downloading source file 
/usr/src/glib2.0-2.80.0-6ubuntu3.1/debian/build/deb/../../../glib/gmain.c
#2  0x003f9847f876 in g_main_dispatch (context=context@entry=0x2d49735610) 
at ../../../glib/gmain.c:3344   

warning: 3344   ../../../glib/gmain.c: No such file or directory
(gdb) 
#3  0x003f984823c4 in g_main_context_dispatch_unlocked 
(context=0x2d49735610) at ../../../glib/gmain.c:4152
4152in ../../../glib/gmain.c
(gdb) 
#4  g_main_context_iterate_unlocked (context=context@entry=0x2d49735610, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:4217
4217in ../../../glib/gmain.c
(gdb) 
#5  0x003f984828be in g_main_context_iteration 
(context=context@entry=0x2d49735610, may_block=may_block@entry=1) at 
../../../glib/gmain.c:4282
4282in ../../../glib/gmain.c
(gdb) 
Downloading source file 
/usr/src/glib2.0-2.80.0-6ubuntu3.1/debian/build/deb/../../../gio/gapplication.c
#6  0x003f983272e4 in g_application_run (application=0x2d4974f960, 
argc=, argv=0x3fe911a678) at ../../../gio/gapplication.c:2712

warning: 2712   ../../../gio/gapplication.c: No such file or directory
(gdb) 
Downloading source file 
/usr/src/epiphany-browser-46.0-2build1/obj-riscv64-linux-gnu/../src/ephy-main.c
#7  0x002d171ef660 in main (argc=, argv=) at 
../src/ephy-main.c:459  

warning: 459../src/ephy-main.c: No such file or directory
(gdb) 

To reproduce:

* Install Ubuntu 24.40, ubuntu-desktop, gdm3, epiphany-browser on SiFive HiFive 
Unmatched board with GPU (such a board is available in the Taipeh lab)
* Run epiphany-browser and load a complex page (e.g. https://www.faz.net).

Best regards

Heinrich
--- 
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: riscv64
CasperMD5json:
 {
   "result": "skip"
 }
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-11-06 (0 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release riscv64 
(20240827.1)
Package: epiphany-browser 46.0-2build1
PackageArchitecture: riscv64
ProcVersionSignature: Ubuntu 6.8.0-48.48.1-generic 6.8.12
Tags: noble
Uname: Linux 6.8.0-48-generic riscv64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True

** Affects: epiphany-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected noble

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

Title:
  epiphany-browser on riscv64 crashes in socket_source_dispatch

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


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

[Bug 2085610] Re: gnome-control-center crashes on exit when gtk-theme is not Yaru

2024-11-06 Thread Alessandro Astone

** Description changed:

+ [ Impact ]
+
When not using gtk-theme Yaru, if you visit the Mouse panel in
gnome-control-center the process will then crash on exit, in
`g_static_resource_fini` with abort message:
assertion failed: (g_atomic_int_get (&resource->ref_count) >= 2)

+ [ Test Case ]
+
+ 1. If it was open, close the Settings app (gnome-control-center)
+ 1. Run
+$ gsettings set org.gnome.desktop.interface gtk-theme Adwaita
+ 2. Open the Settings app
+ 3. Navigate to the "Mouse & Touchpad" panel
+ 4. Close the Settings app
+ 5. Verify that you did not get a crash prompt
+
+ To restore the default settings, run
+$ gsettings reset org.gnome.desktop.interface gtk-theme
+
+ [ Where problems could occur ]
+
+ Animations not showing or not matching the accent colors
+
+ [ Other Info ]
+
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-control-center. This problem was most recently seen with package version
1:47.0.1-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/4b22b5495d1b1c935fc8f0a12e9e5dca173fb406
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/.

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

Title:
gnome-control-center crashes on exit when gtk-theme is not Yaru

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

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

[Bug 2043517] Re: gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)

2024-11-06 Thread Alessandro Astone

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

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

** Changed in: xwayland (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

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

** Also affects: xwayland (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

** Also affects: xwayland (Ubuntu Oracular)
   Importance: Undecided
   Status: New

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

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

** Changed in: xwayland (Ubuntu Noble)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: xwayland (Ubuntu Oracular)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

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

Title:
  gnome-shell on non-active VT busy-loops through libwayland-server.so
  (sometimes)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2043517/+subscriptions


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

[Bug 2086779] HookError_ubuntu.txt

2024-11-06 Thread Heinrich Schuchardt

apport information

** Attachment added: "HookError_ubuntu.txt"
   
https://bugs.launchpad.net/bugs/2086779/+attachment/5835008/+files/HookError_ubuntu.txt

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

Title:
  epiphany-browser on riscv64 crashes in socket_source_dispatch

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


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

[Bug 2086760] [NEW] GIMP crashed on changing the color temparature

2024-11-06 Thread Java Jim

Public bug reported:

Ubuntu 24.04.1 LTS
2.10.36-3ubuntu0.24.04.1 500
Changed the color temperature via the slider, but after dragging it GIMP 
crashes with the error below




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/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 
13.2.0-23ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --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-13-uJ7kn6/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-uJ7kn6/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Speicherzugriffsfehler

Stack trace:
```

# Stack traces obtained from PID 16770 - Thread 16780 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 16823]
[New LWP 16794]
[New LWP 16790]
[New LWP 16788]
[New LWP 16786]
[New LWP 16785]
[New LWP 16784]
[New LWP 16783]
[New LWP 16782]
[New LWP 16781]
[New LWP 16780]
[New LWP 16779]
[New LWP 16778]
[New LWP 16777]
[New LWP 16776]
[New LWP 16775]
[New LWP 16774]
[New LWP 16773]
[New LWP 16772]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  Id   Target IdFrame 
* 1Thread 0x7d43fa87f640 (LWP 16770) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  2Thread 0x7d43ae0006c0 (LWP 16823) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7d43ad6006c0 (LWP 16794) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7d43aea006c0 (LWP 16790) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7d43b90006c0 (LWP 16788) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7d43ce6006c0 (LWP 16786) "gimp-2.10"0x7d43fb098d61 in 
__futex_abstimed_wait_common64 (private=-2147483648, cancel=true, abstime=0x0, 
op=393, expected=0, futex_word=0x60fccc862b94) at ./nptl/futex-internal.c:57
  7Thread 0x7d43ecc006c0 (LWP 16785) "gdbus"0x7d43fb11b4cd in 
__GI___poll (fds=0x7d43a4000b90, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7d43ed6006c0 (LWP 16784) "gmain"0x7d43fb11b4cd in 
__GI___poll (fds=0x60fccb95d1f0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x7d43ee0006c0 (LWP 16783) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7d43ef4006c0 (LWP 16782) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7d43efe006c0 (LWP 16781) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7d43f4a006c0 (LWP 1678

[Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8

2024-11-06 Thread Alessandro Astone

** Changed in: gdm3 (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: gdm3 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: gdm3 (Ubuntu Noble)
   Status: New => In Progress

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

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

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

** Changed in: gdm3 (Ubuntu Jammy)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: gdm3 (Ubuntu Noble)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: gdm3 (Ubuntu)
Milestone: jammy-updates => None

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

Title:
  Default session type changed from Xorg to Wayland in some installs of
  22.04 on Nvidia hybrids since kernel 6.8

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


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

[Bug 2063038] Re: Very high touchpad cursor latency, sometimes

2024-11-06 Thread Daniel van Vugt

Reopened. Still happening on Oracular using a Zenbook S 13. Putting the
screen to sleep didn't fix it, but putting the whole machine to sleep
did fix it.

This reminds me of a (cursor timers) fix that went into Mutter in the
last couple of months which I will need to find...


** Tags added: oracular

** This bug is no longer a duplicate of bug 2067657
   Cursor response to touchpad sporadically becomes laggy

** Summary changed:

- Very high touchpad cursor latency, sometimes
+ Very high touchpad cursor latency, sometimes after resuming from sleep

** Tags added: suspend-resume

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

Title:
  Very high touchpad cursor latency, sometimes after resuming from sleep

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


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

[Bug 2084554] Re: touchscreen drag-select is interrupted by context menu

2024-11-06 Thread Alessandro Astone

** Description changed:

- After 0.5s of starting a multi-file selection by dragging from an empty
- space, the action is interrupted by the context menu opening.
+ [ Impact ]
+ 
+ When using a touchscreen, after 0.5s of starting a multi-file selection
+ by dragging from an empty space, the action is interrupted by the
+ context menu opening.
+ 
+ The fix backports a patch from GNOME 47 to GNOME 46, which is now also
+ backported to the upstream gnome-46 stable branch and queued up for when
+ upstream will decide to make a new release.
+ 
+ [ Test Case ]
+ 
+ 1. Install the nautilus update being tested
+ 2. Log-out and log-in (or reboot)
+ 3. Open the Nautilus file manager
+ 4. Drag from an empty space to start a rectangle selection
+ 5. Verify that you could select multiple files/directories
+ 
+ [ Regression Test Case ]
+ 
+ 1. Long-press on an empty space
+ 2. Verify that the context menu opens.
+ 
+ [ Where problems could occur ]
+ 
+ Either the long-press gesture or the touch-drag gesture may not work.
+ The test cases will verify both.
+ 
+ [ Other Info ]
+ 
+ Do not be scared by the HACK and FIXME comments in the patch, they refer
+ to adding functionality to Gtk rather than implementing possibly
+ inefficient workarounds in Gtk apps like Nautilus.

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

Title:
  touchscreen drag-select is interrupted by context menu

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


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

[Bug 2062128] Re: Booting with nvidia proprietary drivers 550.67 results in gdm3 being displayed on X11 rather than Wayland

2024-11-06 Thread Alessandro Astone

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

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

Title:
  Booting with nvidia proprietary drivers 550.67 results in gdm3 being
  displayed on X11 rather than Wayland

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


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

[Bug 2080602] Re: [regression] GNOME 46/47 dropped support for Xilinx Mali graphics

2024-11-06 Thread Talha Can Havadar

Hello all,

Just tested the the mutter in -proposed version 46.2-1ubuntu0.24.04.4 on
target device. It seems like it is working fine as expected

```
ubuntu@kria:~$ apt policy libmutter-14-0
libmutter-14-0:
  Installed: 46.2-1ubuntu0.24.04.4
  Candidate: 46.2-1ubuntu0.24.04.4
  Version table:
 *** 46.2-1ubuntu0.24.04.4 100
100 http://ports.ubuntu.com/ubuntu-ports noble-proposed/main arm64 
Packages
100 /var/lib/dpkg/status
 46.2-1ubuntu0.24.04.3~xlnx01 500
500 
https://private-ppa.launchpadcontent.net/limerick-team/limerick-proposed/ubuntu 
noble/main arm64 Packages
 46.2-1ubuntu0.24.04.2 500
500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 
Packages
 46.0-1ubuntu9 500
500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages
ubuntu@kria:~$ apt policy mutter


mutter:
  Installed: 46.2-1ubuntu0.24.04.4
  Candidate: 46.2-1ubuntu0.24.04.4
  Version table:
 *** 46.2-1ubuntu0.24.04.4 100
100 http://ports.ubuntu.com/ubuntu-ports noble-proposed/universe arm64 
Packages

100 /var/lib/dpkg/status
 46.2-1ubuntu0.24.04.3~xlnx01 500
500 
https://private-ppa.launchpadcontent.net/limerick-team/limerick-proposed/ubuntu 
noble/main arm64 Packages
 46.2-1ubuntu0.24.04.2 500

500 http://ports.ubuntu.com/ubuntu-ports noble-updates/universe arm64 
Packages
 46.0-1ubuntu9 500

500 http://ports.ubuntu.com/ubuntu-ports noble/universe arm64 Packages
ubuntu@kria:~$ echo $XDG_SESSION_TYPE 
wayland
ubuntu@kria:~$ echo $WAYLAND_DISPLAY 
wayland-0
```

** Tags removed: verification-needed-noble
** Tags added: verification-done-noble

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [regression] GNOME 46/47 dropped support for Xilinx Mali graphics

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


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

[Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8

[Bug 2085610] Re: gnome-control-center crashes on exit when gtk-theme is not Yaru

[Bug 2086779] ProcCpuinfoMinimal.txt

[Bug 2086779] ProcEnviron.txt

[Bug 2086779] Re: epiphany-browser on riscv64 crashes in socket_source_dispatch

[Bug 2086779] [NEW] epiphany-browser on riscv64 crashes in socket_source_dispatch

[Bug 2085610] Re: gnome-control-center crashes on exit when gtk-theme is not Yaru

[Bug 2043517] Re: gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)

[Bug 2086779] HookError_ubuntu.txt

[Bug 2086760] [NEW] GIMP crashed on changing the color temparature

[Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8

[Bug 2063038] Re: Very high touchpad cursor latency, sometimes

[Bug 2084554] Re: touchscreen drag-select is interrupted by context menu

[Bug 2062128] Re: Booting with nvidia proprietary drivers 550.67 results in gdm3 being displayed on X11 rather than Wayland

[Bug 2080602] Re: [regression] GNOME 46/47 dropped support for Xilinx Mali graphics

15 matches

Site Navigation

Mail list logo

Footer information