View Issue Details

IDProjectCategoryView StatusLast Update
0008659Kali LinuxGeneral Bugpublic2024-03-11 02:16
ReporterSalty___ Assigned Todaniruiz  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Summary0008659: Kali with Gnome in VMware will crash when attempting to move an icon in taskbar.

​Abstract. after installing a new image with Gnome, moving an icon will cause the DE to crash and on reboot it will not be corrected.

Steps to reproduce:
​Starting with Vmware pro 17, we will use the latest installer image from we are using 2024.1 installer.
Follow all default options for the installer.
Once installed run update/upgrate, followed by full-upgrade.
Now we will reboot the system to simulate a user shutoff.
when logged in, we can now attempt to move an icon. for consistency, I am moving cherry tree one spot over to the left.

looking through journalctl I found this:

Mar 04 13:41:07 kali gnome-shell[1468]: No cursor theme available, please install a cursor theme
Mar 04 13:41:07 kali gnome-shell[1468]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadCursor (invalid Cursor parameter)'.
(Details: serial 2919 error_code 6 request_code 95 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
Mar 04 13:41:07 kali gnome-shell[1468]: == Stack trace for context 0x55a710160de0 ==
Mar 04 13:41:07 kali gnome-shell[1468]: #0 55a71022c610 i resource:///org/gnome/shell/ui/dnd.js:390 (1bf2d29f2e20 @ 440)
Mar 04 13:41:07 kali gnome-shell[1468]: 0000001 55a71022c520 i resource:///org/gnome/shell/ui/dnd.js:560 (1bf2d29f70b0 @ 680)
Mar 04 13:41:07 kali gnome-shell[1468]: #2 55a71022c478 i resource:///org/gnome/shell/ui/dnd.js:323 (1bf2d29f2d80 @ 688)
Mar 04 13:41:07 kali gnome-shell[1468]: #3 55a71022c3e8 i resource:///org/gnome/shell/ui/init.js:21 (1bf2d2970bf0 @ 48)




2024-03-04 21:34

reporter   ~0018989

Mar 04 13:41:07 kali gnome-shell[1468]: No cursor theme available, please install a cursor theme
Mar 04 13:41:07 kali gnome-shell[1468]: Received an X Window System error.
This probably reflects a bug in the program.

Bugs in software goes to the bugtracker of that software, not to the linux distribution shipping it.




2024-03-04 23:48

reporter   ~0018990

I am not sure how you were able to determine that the issue was with Gnome, when Gnome with Wayland works as intended and that this is only with Xorg.



2024-03-05 05:33

reporter   ~0018993

Thats something the developers of that software needs to figure out (e.g. different code part used in Wayland vs. Xorg).



2024-03-05 05:36

reporter   ~0018994

Overall not an issue / bug in Kali but just an issue / bug in a software shipped within Kali so most likely nothing the Kali team can help with.



2024-03-05 05:48

reporter   ~0018995

No kali-bugreport, please refrain from commenting further on this report as you are unwilling to be helpful. This issue is specific to kali. After testing Trixie and installing experimental repos , I have no issues. I am not sure what you are rambling about, but its not helpful and I would kindly ask you to refrain from commenting further if you are not willing to assist. thank you for your understanding.

Note for the bug: After testing with trixie, I discovered that kalis gnome implementation is different from Trixie and instead is pulling from experimental, so I added experimental repo in etc/apt/sources.list. I was able to get full function However, Gnome version is 45.3, where Kali currently has 45.2. I was going to test it with Kali but found I had issues launching the DE when installing gnome-shell-extension-gsconnect from the experimental repo.



2024-03-05 08:07

manager   ~0018996

Last edited: 2024-03-05 08:56

We are hitting this bug:

This is due to adwaita-icon-theme version 46, and some versions of mutter that need to be updated in lockstep. Apparently it's fixed in Debian unstable with mutter 44.8-2 and in Debian experimental with mutter 45.3-3.

Kali is based on Debian testing, so we receive bugs (and fixes) with a bit of delay, compared to Debian unstable.

adwaita-icon-theme 46 entered Kali rolling on 27th of Feb: This is what caused the issue. As for mutter, we have 45.2-3 (indeed we pulled it from Debian experimental). So in short, we just need to update the gnome-shell+ mutter stack that we get from Debian experimental, and we should be good to go.



2024-03-05 08:56

manager   ~0018997

To clarify: the issue doesn't affect the 2024.1 release, as it was shipped with adwaita-icon-theme 45.0-2. Only kali-rolling is affected.



2024-03-05 15:24

reporter   ~0018999

@Salty: So as you can see this is not a Bug in Kali, nothing more to say...



2024-03-06 02:19

manager   ~0019001

At this point mutter 45.3-3 should be in Kali rolling, so the issue should be fixed with the usual apt update && apt full-upgrade. Closing, but feel free to re-open if it's not fixed.

Thanks for the report!



2024-03-11 02:16

manager   ~0019007

@kali-bugreport this was absolutely a bug in kali. it was due to us having outdated dependencies that we pulled in that we didn't pull in, in lock step as we should have. salty's report was correct, and was requested by me that he open.

Issue History

Date Modified Username Field Change
2024-03-04 19:49 Salty___ New Issue
2024-03-04 21:34 kali-bugreport Note Added: 0018989
2024-03-04 23:48 Salty___ Note Added: 0018990
2024-03-05 05:33 kali-bugreport Note Added: 0018993
2024-03-05 05:36 kali-bugreport Note Added: 0018994
2024-03-05 05:48 Salty___ Note Added: 0018995
2024-03-05 08:07 arnaudr Note Added: 0018996
2024-03-05 08:07 arnaudr Assigned To => daniruiz
2024-03-05 08:07 arnaudr Status new => assigned
2024-03-05 08:56 arnaudr Note Added: 0018997
2024-03-05 08:56 arnaudr Note Edited: 0018996
2024-03-05 15:24 kali-bugreport Note Added: 0018999
2024-03-06 02:19 arnaudr Note Added: 0019001
2024-03-06 02:19 arnaudr Status assigned => resolved
2024-03-06 02:19 arnaudr Resolution open => fixed
2024-03-11 02:16 steev Note Added: 0019007