xfdesktop issueshttps://gitlab.xfce.org/xfce/xfdesktop/-/issues2024-03-27T20:07:07Zhttps://gitlab.xfce.org/xfce/xfdesktop/-/issues/290Opening the settings dialog when XfwScreen:show-desktop is enabled minimizes ...2024-03-27T20:07:07ZGaël BonithonOpening the settings dialog when XfwScreen:show-desktop is enabled minimizes the dialog on openingA little oddity specific to X11 and also reproducible with 4.18:
* Toggle show-desktop for example via the panel plugin
* Open xfdesktop settings dialog via context menu
The dialog is minimized on opening (or almost, after a few seconds).A little oddity specific to X11 and also reproducible with 4.18:
* Toggle show-desktop for example via the panel plugin
* Open xfdesktop settings dialog via context menu
The dialog is minimized on opening (or almost, after a few seconds).https://gitlab.xfce.org/xfce/xfdesktop/-/issues/289'show-icons-on-primary' lost in 4.19.22024-03-20T18:36:16ZGaël Bonithon'show-icons-on-primary' lost in 4.19.2It works with 4.18.1, but with 4.19.2 (actually git master):
```
GLib-GObject-CRITICAL **: 22:42:14.881: g_object_notify: object class 'XfdesktopIconView' has no property named 'show-icons-on-primary'
Core was generated by `/opt/bin/xfd...It works with 4.18.1, but with 4.19.2 (actually git master):
```
GLib-GObject-CRITICAL **: 22:42:14.881: g_object_notify: object class 'XfdesktopIconView' has no property named 'show-icons-on-primary'
Core was generated by `/opt/bin/xfdesktop.orig'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0 g_logv (log_domain=0x7e77e19e7015 "GLib-GObject", log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, args=args@entry=0x7ffebbc16d20) at ../glib/glib/gmessages.c:1277
1277 g_private_set (&g_log_depth, GUINT_TO_POINTER (depth));
[Current thread is 1 (Thread 0x7e77e036ba00 (LWP 8459))]
(gdb) bt
#0 g_logv (log_domain=0x7e77e19e7015 "GLib-GObject", log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, args=args@entry=0x7ffebbc16d20) at ../glib/glib/gmessages.c:1277
#1 0x00007e77e1a64754 in g_log (log_domain=<optimized out>, log_level=<optimized out>, format=<optimized out>) at ../glib/glib/gmessages.c:1315
#2 0x00007e77e19c7279 in object_set_property (object=0x5ca911c32120, pspec=0x5ca911c33510, value=0x7ffebbc16f00, nqueue=0x5ca9123b7690, user_specified=<optimized out>) at ../glib/gobject/gobject.c:2169
#3 0x00007e77e19ca116 in g_object_setv (values=0x7ffebbc16ec8, names=0x7ffebbc16ea8, n_properties=1, object=0x5ca911c32120) at ../glib/gobject/gobject.c:3080
#4 g_object_setv (object=0x5ca911c32120, n_properties=n_properties@entry=1, names=names@entry=0x7ffebbc16ec8, values=values@entry=0x7ffebbc16f00) at ../glib/gobject/gobject.c:3051
#5 0x00007e77e19ca350 in g_object_set_property (object=<optimized out>, property_name=<optimized out>, value=value@entry=0x7ffebbc16f00) at ../glib/gobject/gobject.c:3380
#6 0x00007e77e2951540 in xfconf_g_property_channel_notify (channel=<optimized out>, property=<optimized out>, value=0x5ca91227a890, user_data=0x5ca911b6f7f0) at xfconf-binding.c:334
#7 0x00007e77e19b6730 in g_closure_invoke (closure=0x5ca911b6f430, return_value=0x0, n_param_values=3, param_values=0x7ffebbc17110, invocation_hint=0x7ffebbc17060) at ../glib/gobject/gclosure.c:834
#8 0x00007e77e19e5896 in signal_emit_unlocked_R.isra.0
(node=node@entry=0x7ffebbc17210, detail=detail@entry=1402, instance=instance@entry=0x5ca911a2f5f0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffebbc17110)
at ../glib/gobject/gsignal.c:3888
#9 0x00007e77e19d67a2 in signal_emit_valist_unlocked (instance=instance@entry=0x5ca911a2f5f0, signal_id=signal_id@entry=256, detail=detail@entry=1402, var_args=var_args@entry=0x7ffebbc17370)
at ../glib/gobject/gsignal.c:3520
#10 0x00007e77e19d69d7 in g_signal_emit_valist (instance=0x5ca911a2f5f0, signal_id=256, detail=1402, var_args=var_args@entry=0x7ffebbc17370) at ../glib/gobject/gsignal.c:3263
#11 0x00007e77e19d6a94 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../glib/gobject/gsignal.c:3583
#12 0x00007e77e19b6730 in g_closure_invoke (closure=0x5ca911ab2740, return_value=0x0, n_param_values=4, param_values=0x7ffebbc17620, invocation_hint=0x7ffebbc17570) at ../glib/gobject/gclosure.c:834
#13 0x00007e77e19e5896 in signal_emit_unlocked_R.isra.0
(node=node@entry=0x7ffebbc17740, detail=detail@entry=0, instance=instance@entry=0x5ca911a522d0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffebbc17620)
at ../glib/gobject/gsignal.c:3888
#14 0x00007e77e19d67a2 in signal_emit_valist_unlocked (instance=instance@entry=0x5ca911a522d0, signal_id=signal_id@entry=257, detail=detail@entry=0, var_args=var_args@entry=0x7ffebbc178a0)
at ../glib/gobject/gsignal.c:3520
#15 0x00007e77e19d69d7 in g_signal_emit_valist (instance=0x5ca911a522d0, signal_id=257, detail=0, var_args=var_args@entry=0x7ffebbc178a0) at ../glib/gobject/gsignal.c:3263
#16 0x00007e77e19d6a94 in g_signal_emit (instance=instance@entry=0x5ca911a522d0, signal_id=<optimized out>, detail=detail@entry=0) at ../glib/gobject/gsignal.c:3583
#17 0x00007e77e295336e in xfconf_cache_handle_property_changed (parameters=<optimized out>, cache=0x5ca911a522d0) at xfconf-cache.c:528
#18 xfconf_cache_proxy_signal_received_cb (proxy=<optimized out>, sender_name=<optimized out>, signal_name=<optimized out>, parameters=<optimized out>, user_data=0x5ca911a522d0) at xfconf-cache.c:588
#19 0x00007e77e19b6730 in g_closure_invoke (closure=0x5ca911a529f0, return_value=0x0, n_param_values=4, param_values=0x7ffebbc17bb0, invocation_hint=0x7ffebbc17b00) at ../glib/gobject/gclosure.c:834
#20 0x00007e77e19e5896 in signal_emit_unlocked_R.isra.0
(node=node@entry=0x7ffebbc17cd0, detail=detail@entry=0, instance=instance@entry=0x5ca911b15b60, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffebbc17bb0)
at ../glib/gobject/gsignal.c:3888
#21 0x00007e77e19d67a2 in signal_emit_valist_unlocked (instance=instance@entry=0x5ca911b15b60, signal_id=signal_id@entry=24, detail=detail@entry=0, var_args=var_args@entry=0x7ffebbc17e30)
at ../glib/gobject/gsignal.c:3520
#22 0x00007e77e19d69d7 in g_signal_emit_valist (instance=0x5ca911b15b60, signal_id=24, detail=0, var_args=var_args@entry=0x7ffebbc17e30) at ../glib/gobject/gsignal.c:3263
#23 0x00007e77e19d6a94 in g_signal_emit (instance=instance@entry=0x5ca911b15b60, signal_id=<optimized out>, detail=<optimized out>) at ../glib/gobject/gsignal.c:3583
#24 0x00007e77e18e50d6 in on_signal_received
(connection=<optimized out>, sender_name=0x7e77cc017b80 ":1.309", object_path=<optimized out>, interface_name=<optimized out>, signal_name=0x7e77cc01c1d0 "PropertyChanged", parameters=0x7e77cc00bfb0, user_data=0x5ca911a69210) at ../glib/gio/gdbusproxy.c:874
#25 0x00007e77e18cff08 in emit_signal_instance_in_idle_cb (data=0x7e77cc01b7b0) at ../glib/gio/gdbusconnection.c:3798
#26 0x00007e77e1a5f199 in g_main_dispatch (context=0x5ca91188c500) at ../glib/glib/gmain.c:3344
#27 0x00007e77e1abe3bf in g_main_context_dispatch_unlocked (context=0x5ca91188c500) at ../glib/glib/gmain.c:4152
#28 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x5ca91188c500, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4217
#29 0x00007e77e1a5e712 in g_main_context_iteration (context=context@entry=0x5ca91188c500, may_block=may_block@entry=1) at ../glib/glib/gmain.c:4282
#30 0x00007e77e18aeed6 in g_application_run (application=application@entry=0x5ca911887d40, argc=argc@entry=1, argv=argv@entry=0x7ffebbc18278) at ../glib/gio/gapplication.c:2712
#31 0x00005ca90fd4aa58 in main (argc=1, argv=0x7ffebbc18278) at main.c:54
```https://gitlab.xfce.org/xfce/xfdesktop/-/issues/284Clicking on the desktop causes redraw of the root window erasing the root-tail2024-03-08T09:54:43ZJaroslav ŠkarvadaClicking on the desktop causes redraw of the root window erasing the root-tailThis worked earlier and stopped with some Xfce update. If root-tail is stuck to the root window of the desktop and if user clicks on the desktop by the left mouse button, the desktop is redrawn which erases the root tail output. Then the...This worked earlier and stopped with some Xfce update. If root-tail is stuck to the root window of the desktop and if user clicks on the desktop by the left mouse button, the desktop is redrawn which erases the root tail output. Then the logs have to be updated for the root-tail output to re-appear.
I think this behaviour could be configurable. Or maybe fully dropped, because the redraw seems useless to me. I.e. if there was no background change and no artifacts, the useless redraw just wastes CPU/GPU resources.
Reproducer:
```
$ root-tail -id `xwininfo -int -name 'Desktop' | sed -n '/Window id:/ s/[^0-9]*\([0-9]\+\).*/\1/p'` /var/log/messages,darkgreen,"ALL"
# Click on the desktop
```
xfdesktop-4.18.1
If there is a icon, I think just the box around the icon should be redrawn. If there is no icon, I think nothing should be redrawn.https://gitlab.xfce.org/xfce/xfdesktop/-/issues/281desktop settings not preserved after boot2024-02-24T15:38:07ZDL4SAIdesktop settings not preserved after bootIn case 'no picture' is chosen and a background color is selected in desktop-settings, the values will get stored in array 'rgba1' as type 'double'. As decimal point for language 'german' character ',' is used in xfe4-desktop.xml. This w...In case 'no picture' is chosen and a background color is selected in desktop-settings, the values will get stored in array 'rgba1' as type 'double'. As decimal point for language 'german' character ',' is used in xfe4-desktop.xml. This will cause an error in xfconfd. As consequence, the file in .config/xfce4/xfconf/xfce-perchannel-xml gets replaced with defaults on every boot and all settings are lost.
After replacing manually ',' by '.' settings will be kept.
xfconf-query shows version 4.16.0.https://gitlab.xfce.org/xfce/xfdesktop/-/issues/279Inconsistencies between two windows list menus2024-01-04T22:09:16ZPier Franco PaseroInconsistencies between two windows list menusHi everyone,
I've just noticed a few inconsistencies in the windows list menus present in Xfce 4.18.
The purpose of a windows list menu is to display a menu listing all your workspaces and the windows in each of them. To the best of my ...Hi everyone,
I've just noticed a few inconsistencies in the windows list menus present in Xfce 4.18.
The purpose of a windows list menu is to display a menu listing all your workspaces and the windows in each of them. To the best of my knowledge it seems like Xfce currently has two of these types of menus and they are almost the same, but not quite.
One of them is accessible through the panel's items and is called **Window Menu** and once clicked it displays a menu like shown in the following image ![xfce418-panel_window-menu-item](/uploads/0dcba62d833dcde4a3c1d4dddda85ae6/xfce418-panel_window-menu-item.png)
Instead the other one can be displayed by launching the following command `xfdesktop --windowlist` or by binding it to a keyboard shortcut with the following result ![xfce418-xfdesktop-windowlist](/uploads/422e5383a1be92badffba84cb7c7346c/xfce418-xfdesktop-windowlist.png)
As can be seen in the above images the two menus are almost identical but use different styles to list their entries, namely:
- the panel's menu lists minimized windows names within squared brackets, while the xfdesktop one does not
- both make the minimized windows icons grayish
- the panel's menu highlight the current workspace by displaying its name in bold characters (and the others in italic), while the xfdesktop menu puts all workspaces names in bold, no matter which one is currently used
Is it because these menus are two different implementations, i.e. they don't share the same code, or is it just a matter of styling preferences which are applied differently?
Thank you and keep up with the good work!https://gitlab.xfce.org/xfce/xfdesktop/-/issues/277Add Display Settings and Custom Shortcuts to the right click menu of Desktop2023-12-04T12:06:22ZTheBSODAndWSODFanAdd Display Settings and Custom Shortcuts to the right click menu of DesktopIt would be nice to add Display Settings and Custom Shortcuts without using Thunar Custom Actions.
https://www.reddit.com/r/xfce/comments/171dsqr/i_added_display_settings_to_xfdesktop_right_click/
![2023-10-06_21-26](/uploads/603b2a97fe2...It would be nice to add Display Settings and Custom Shortcuts without using Thunar Custom Actions.
https://www.reddit.com/r/xfce/comments/171dsqr/i_added_display_settings_to_xfdesktop_right_click/
![2023-10-06_21-26](/uploads/603b2a97fe2555e56769ed5cee38c8e1/2023-10-06_21-26.png)https://gitlab.xfce.org/xfce/xfdesktop/-/issues/275Don't use XfceSMClient on Wayland2024-02-10T22:32:37ZBrian TarriconeDon't use XfceSMClient on Waylandhttps://gitlab.xfce.org/xfce/xfdesktop/-/issues/274"Move window to x monitor" WM keyboard binds slowly break xfdesktop's alignme...2023-11-09T04:06:48ZJared Johnstone"Move window to x monitor" WM keyboard binds slowly break xfdesktop's alignment and rendering.Hi team,
I've discovered a strange one.
I frequently make use of Window Manager bindings `Move window to left monitor` and `Move window to right monitor` bound to Shift+Ctrl+Alt+Left and Shift+Ctrl+Alt+Right respectively. It helps me m...Hi team,
I've discovered a strange one.
I frequently make use of Window Manager bindings `Move window to left monitor` and `Move window to right monitor` bound to Shift+Ctrl+Alt+Left and Shift+Ctrl+Alt+Right respectively. It helps me move my windows around quickly when desired.
I noticed this afternoon that my desktop background's stopped rendering on my monitors as I was switching workspaces(2 monitors, 2 workspaces). Instead of my wallpapers drawing as usual, there was a black void-space due to <nothing> being drawn there. Dragging a window over the negative space left a hall of mirrors effect where the the void space retained pixels of whatever was drawn to that area last.
I found out I can reproduce this behavior by clicking on the empty Desktop area (xfdesktop) and repeatedly tapping the bindings to move a "Window" to the left and right monitor. Xfdesktop slowly shifts more and more pixels to the right with each repetition instead of returning to its true 0,0 position in Xorg. (Let alone the complication that Xfdesktop can be "shifted" to another monitor at all!). This results in the aforementioned void rendering problem I experienced in the beginning.
It seems running `pkill xfdesktop ; xfdesktop & exit` in my terminal is enough to undo this abnormality without having to restart lightdm.
I'm running a 3900x CPU with a 2080Ti GPU. Kernel 6.5.9 and NVIDIA 545.29.02 using xfce4 on lightdm.https://gitlab.xfce.org/xfce/xfdesktop/-/issues/272[4.19.1] no 50% alpha value on unmounted devices2023-11-23T09:29:11ZVonKossa[4.19.1] no 50% alpha value on unmounted devicesIn Thunar you have the following setting for setting alpha value 0.5 on unmounted devices:
/* 50% translucent for unmounted volumes */
if (shortcuts_icon_renderer->device != NULL
&& !thunar_device_is_mou...In Thunar you have the following setting for setting alpha value 0.5 on unmounted devices:
/* 50% translucent for unmounted volumes */
if (shortcuts_icon_renderer->device != NULL
&& !thunar_device_is_mounted (shortcuts_icon_renderer->device))
alpha = 0.50;
else
alpha = 1.00;
In xfdesktop-4.18 it displays the same as in Thunar.
But in xfdesktop-4.19.1 it always shows alpha value 1.0 on unmounted devices.
I may be wrong but this is not a gtk theme setting in gtk.css?https://gitlab.xfce.org/xfce/xfdesktop/-/issues/270Icon selection not updating properly2023-10-21T21:44:15Zmpv enjoyerIcon selection not updating properly(tested on xfdesktop version 4.18.1, running on Xfce 4.18.)
Sometimes desktop icons do not unselect when they should.
This is very rare though and I never managed to do the same thing with folders, only with files
Example: (here the fi...(tested on xfdesktop version 4.18.1, running on Xfce 4.18.)
Sometimes desktop icons do not unselect when they should.
This is very rare though and I never managed to do the same thing with folders, only with files
Example: (here the file with long name stays selected but it sometimes happens for short file names underneath long ones too)
![icon_no_unselect_bug](/uploads/7e0a40f416c978237c8b1222465758b2/icon_no_unselect_bug.gif)https://gitlab.xfce.org/xfce/xfdesktop/-/issues/266Extend confirmation dialog when clicking "Arrange Desktop Icons"2023-10-24T14:10:51ZManuel GrießmayrExtend confirmation dialog when clicking "Arrange Desktop Icons"In xfdesktop I can select "Arrange Desktop Icons" in the context menu. Then a dialog comes up asking for confirmation. I would like to add a checkbox to this dialog: "Don't ask again".
@kelnos:
Would you accept a merge request for this?...In xfdesktop I can select "Arrange Desktop Icons" in the context menu. Then a dialog comes up asking for confirmation. I would like to add a checkbox to this dialog: "Don't ask again".
@kelnos:
Would you accept a merge request for this? Please, please, please. :innocent:https://gitlab.xfce.org/xfce/xfdesktop/-/issues/263Set a default background for new monitors2023-09-20T07:56:52ZthirstyiceSet a default background for new monitorsWould like to be able to set a default background so that I don't have to re-configure the background image for every physical monitor port.
Other people seem to want this as well, according to these forum posts:
https://forum.xfce.org...Would like to be able to set a default background so that I don't have to re-configure the background image for every physical monitor port.
Other people seem to want this as well, according to these forum posts:
https://forum.xfce.org/viewtopic.php?id=1498
https://forum.xfce.org/viewtopic.php?id=13308
https://www.reddit.com/r/xfce/comments/evqx53/custom_default_background/https://gitlab.xfce.org/xfce/xfdesktop/-/issues/261Delay when switching focus/selection from windows to xfdesktop2023-09-22T16:37:37ZManuel GrießmayrDelay when switching focus/selection from windows to xfdesktopTested with xfdesktop 4.19.1
How to reproduce:
1. Open a window but not in fullscreen
2. Let the window have the focus
3. Select an icon on xfdesktop
The same can be observed with unselecting an icon by clicking on xfdesktop on space w...Tested with xfdesktop 4.19.1
How to reproduce:
1. Open a window but not in fullscreen
2. Let the window have the focus
3. Select an icon on xfdesktop
The same can be observed with unselecting an icon by clicking on xfdesktop on space where no icon is.
The deley is not much but noticable, maybe 200 or 300 milliseconds. It's noticable especially when comparing that selecting an icon feels instant when the focus is already at xfdesktop.
Window scaling of 2x is enabled in xfce4-appearance-settings and resolution is 4K.
Can this be reproduced by anyone?https://gitlab.xfce.org/xfce/xfdesktop/-/issues/260XFCE Desktop: Safe removal fails with non-mounted volume2023-08-05T20:41:53ZGeorg SchwarzXFCE Desktop: Safe removal fails with non-mounted volumeOn the XFCE4 (tried it with Manjaro with XFCE 4.18) a freshly plugged in USB storage device or a freshly inserted DVD appears on the desktop with the respective icons. The context menu (right click) is offering the options to mount it or...On the XFCE4 (tried it with Manjaro with XFCE 4.18) a freshly plugged in USB storage device or a freshly inserted DVD appears on the desktop with the respective icons. The context menu (right click) is offering the options to mount it or to safely remove it.
Selecting safe removal, which should result in the removal of the icon from the desktop (and a disk being ejected from the drive), fails to have any effect until the volume has been mounted (either by explicitly selecting that option or by opening it).
Please note that in contrast selecting the eject symbol next to the volume in the left pane in Thunar (listed under "devices") does eject/safely remove the medium even when it has not been mounted (opened).https://gitlab.xfce.org/xfce/xfdesktop/-/issues/248Icon view does not properly support touch screens2023-12-13T16:36:23ZMjsheepIcon view does not properly support touch screensmy xface version is 4.16;
why When I use the touch screen to control the xfce system, I cannot open the contents of the file system by touching it(4.16);
Whether I want to change any configuration when I use the touch screen control?my xface version is 4.16;
why When I use the touch screen to control the xfce system, I cannot open the contents of the file system by touching it(4.16);
Whether I want to change any configuration when I use the touch screen control?https://gitlab.xfce.org/xfce/xfdesktop/-/issues/245Multi-monitor offset positioning on Wayland2023-04-26T19:30:00ZGaël BonithonMulti-monitor offset positioning on WaylandXfdesktop `4.19.1+145+g983d11ff`
I have a laptop monitor on the left (1366x768) and an external monitor on the right (1920x1080):
On Labwc:
![20230425_14h10m58s_grim](/uploads/1d5a56a4b864a6a47dd5abebced33dfe/20230425_14h10m58s_grim.p...Xfdesktop `4.19.1+145+g983d11ff`
I have a laptop monitor on the left (1366x768) and an external monitor on the right (1920x1080):
On Labwc:
![20230425_14h10m58s_grim](/uploads/1d5a56a4b864a6a47dd5abebced33dfe/20230425_14h10m58s_grim.png)
On Wayfire:
![20230425_14h07m51s_grim](/uploads/e31e12b8a028fb76a323824b2a292d32/20230425_14h07m51s_grim.png)
It's truncated on the left on Wayfire for some reason, but the offset is the same.https://gitlab.xfce.org/xfce/xfdesktop/-/issues/243[4.19.1] Command "Arrange Desktop icons" started not using the correct screen...2023-05-29T10:16:24ZSebastian Pipping[4.19.1] Command "Arrange Desktop icons" started not using the correct screen sizeHi! :wave:
I'm a happy user of XFCE, thanks for making XFCE and sharing it as Open Source! :pray:
Starting with xfdesktop 4.19.1 (i.e. 4.19.0 worked fine, just re-confirmed), context menu command "Arrange Desktop icons" does not use th...Hi! :wave:
I'm a happy user of XFCE, thanks for making XFCE and sharing it as Open Source! :pray:
Starting with xfdesktop 4.19.1 (i.e. 4.19.0 worked fine, just re-confirmed), context menu command "Arrange Desktop icons" does not use the correct screen size. Cases I have observed are (a) only using ~70% of the full screen height and (b) using so much height that farthest down icons' labels are hidden behind the (xfce4-panel) panel bar.
It it matters, my setup is two monitors — one smaller built into the laptop, one bigger and external — where whenever the smaller laptop one is still active after log-in I would turn that off using [Arandr](https://christian.amsuess.com/tools/arandr/), and then screen resolution changes.
Any chance this could be fixed?
Thanks and best, Sebastian
CC #242https://gitlab.xfce.org/xfce/xfdesktop/-/issues/242[4.19.1] xfdesktop 4.19.1 shows empty desktop after upgrade from 4.19.0, was ...2024-02-27T05:37:29ZSebastian Pipping[4.19.1] xfdesktop 4.19.1 shows empty desktop after upgrade from 4.19.0, was showing file icons beforeHi! :wave:
I'm a happy user of XFCE, thanks for making XFCE and sharing it as Open Source! :pray:
I installed xfdesktop 4.19.1 two days ago and found my desktop with no icons today after reboot. What helped is to go to the settings ...Hi! :wave:
I'm a happy user of XFCE, thanks for making XFCE and sharing it as Open Source! :pray:
I installed xfdesktop 4.19.1 two days ago and found my desktop with no icons today after reboot. What helped is to go to the settings and switch "Icon Type" to "None" and back to "File/launcher icons". So there is apparently some problem in the upgrade path and/or a mismatch of settings dialog and reality. Any chance this could be fixed for 4.19.2?
Thanks and best, Sebastian
PS: This is ticket https://bugs.gentoo.org/904468 in Gentoo Linux.https://gitlab.xfce.org/xfce/xfdesktop/-/issues/233Support Thunar's custom per-file foreground and background highlight colors2023-04-29T10:31:08ZIoannisLMSupport Thunar's custom per-file foreground and background highlight colorsFile or folder highlights settings via thunar or desktop context menu properties its not visible.File or folder highlights settings via thunar or desktop context menu properties its not visible.https://gitlab.xfce.org/xfce/xfdesktop/-/issues/224Display layout changes when AOC display resumes from sleep or is turned back ...2023-04-24T23:14:17ZD33M0NDisplay layout changes when AOC display resumes from sleep or is turned back on (from on/off button)Have 4 displays -- 3 Dell, 1 AOC (Q3279VWFD8). Have learned to live with the reality that the layout and icons gets changed up every time displays resume from sleep (or is turned back on from power button), so had/have implemented xrandr...Have 4 displays -- 3 Dell, 1 AOC (Q3279VWFD8). Have learned to live with the reality that the layout and icons gets changed up every time displays resume from sleep (or is turned back on from power button), so had/have implemented xrandr script to fix this.
```
#!/bin/sh
xrandr --output DisplayPort-0 --primary --mode 2560x1440 --refresh 74.97 --pos 0x1080 --rotate normal\
--output DisplayPort-1 --mode 1920x1080 --pos 640x0 --rotate normal\
--output DisplayPort-2 --mode 1920x1200 --pos 2560x1080 --rotate normal\
--output HDMI-A-0 --mode 1920x1080 --pos 2560x0 --rotate normal
```
Default and wanted layout is this:
![image](/uploads/447c3efd131510d47f0271d3bc3e982c/image.png)
However with the update to Manjaro that updated the Xfce from 4.16 directly to 4.18, it got different and slightly more painful to restore. Now the script simply fixes the layout (if it got mixed up at all, sometimes it doesn't anymore), but all the icons remain scrambled -- well, moved and piled up to display 3+4 and displays 1+2 are left with 0 icons. Also there is this new/old popup every time when the AOC display comes online (previously only saw it once and never again, now I see it after every suspend).
![image](/uploads/4f4324ac2ca972a0a9da69cd61dffcd7/image.png)
Almost like it always detects this AOC display as "new monitor" that it has never seen before???
(So for a workaround have to run 2 scripts now, one that messes layout slightly more up, and the current one, so swapping between them couple of times the icons also shake to place).
And it only happens when AOC display (sadly main) is turned back on. Changing the primary display to any of the other displays didn't change the result/behavior. Don't understand how one monitor sleep / wake-up (from display power management `xfce4-power-manager`) or power off-on (from button on display) acts so differently from other displays. And/or why xfdesktop doesn't change the display layout back, when all 4 are back "on". Is it fixable from your end or any suggestions what I could do here?
Not quite sure how linux and/or xfce detects if the display is "NEW". And why AOC display turning off or going to sleep kind of removes the display from "OLD KNOWN" displays list, so when it comes back online, it's always detected as "NEW". How does the display remembering even work for xfce? what id or number it stores and compares to when some display is (re-)connected? Only visible "ID" difference I see from xrandr --verbose is that Dell displays EDID's are 8 lines, while AOC EDID is 16 lines (unexpected size for xfce, so it doesn't bother remembering it?).
EDIT: just now found another quality-of-life workaround: in `xfce4-settings` => Advanced => When new displays are connected : Show dialog > Do nothing.
Seems to fix the new display popup from appearing AND doesn't seem to scramble the icons that much (they twitch, but then jerk back to the old position almost...? not perfectly, but at least to some rather recent "save point", couple of icons have only moved.)