Skip to main content
Topic: Xlibre release 25.0.0.0 now available for testing (Read 25914 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Re: Xlibre release 25.0.0.0 now available for testing

Reply #45
As a simple test I ran 'xset dpms force standby', but that does not result in a freeze.

artist


Re: Xlibre release 25.0.0.0 now available for testing

Reply #47
I made it I fixed the patch
Code: [Select]
--- a/src/x11/xf86Wacom.c	2025-07-03 15:00:41.490240766 +0200
+++ b/src/x11/xf86Wacom.c 2025-07-03 15:00:24.959844978 +0200
@@ -71,7 +71,7 @@
  va_list args;
 
  va_start(args, format);
- xf86VIDrvMsgVerb(priv->frontend, xtype, 0, format, args);
+ xf86IDrvMsgVerb(priv->frontend, (MessageType)xtype, 0, format, args);
  va_end(args);
 }


the (MessageType) thing was missing
it seems like I was wrong the thing's crashing again

the only workaround that actually work so far is to comment out that line entirely

Re: Xlibre release 25.0.0.0 now available for testing

Reply #48
I made it I fixed the patch
Code: [Select]
--- a/src/x11/xf86Wacom.c	2025-07-03 15:00:41.490240766 +0200
+++ b/src/x11/xf86Wacom.c 2025-07-03 15:00:24.959844978 +0200
@@ -71,7 +71,7 @@
  va_list args;
 
  va_start(args, format);
- xf86VIDrvMsgVerb(priv->frontend, xtype, 0, format, args);
+ xf86IDrvMsgVerb(priv->frontend, (MessageType)xtype, 0, format, args);
  va_end(args);
 }


the (MessageType) thing was missing
it seems like I was wrong the thing's crashing again


+   xf86VIDrvMsgVerb(priv->frontend, (MessageType)xtype, 0, format, args);

Possibly because the letter V is missing.  ???
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons,fonts} -gnome3 -kde -plasma -wayland "

Re: Xlibre release 25.0.0.0 now available for testing

Reply #49
dpms still freezes the screen with the latest version.

 

Re: Xlibre release 25.0.0.0 now available for testing

Reply #50

it seems like I was wrong the thing's crashing again


+   xf86VIDrvMsgVerb(priv->frontend, (MessageType)xtype, 0, format, args);

Possibly because the letter V is missing.  ???


no, metux in his infinite wisdom unexported the function with the V thinking no one needed that thing or something (honestly that whole story actually is making me lose faith in xlibre maybe the transgender people are right and this fork ain't gonna go anywhere good)

someone on github made a fix that maybe actually work https://github.com/X11Libre/xf86-input-wacom/pull/6/commits/b8ccb92eecf2798831e76d943763bc8f16c0f836

haven't tried to compile it yet i'm happy with my own patch where the thing is just commented out

edit: I'm using that patch and everything is working flawlessly so far

full diff file to spare pkg maintainer's time:
Code: [Select]
diff --git a/src/x11/xf86Wacom.c b/src/x11/xf86Wacom.c
index adb1643..4c05b81 100644
--- a/src/x11/xf86Wacom.c
+++ b/src/x11/xf86Wacom.c
@@ -68,11 +68,20 @@ void
 wcmLog(WacomDevicePtr priv, WacomLogType type, const char *format, ...)
 {
  MessageType xtype = (MessageType)type;
- va_list args;
-
+ va_list args,args2;
  va_start(args, format);
- xf86VIDrvMsgVerb(priv->frontend, xtype, 0, format, args);
+ va_copy(args2,args);
+
+ int str_size = vsnprintf(NULL, 0, format, args);
+ char *str = calloc(1, str_size + 1);
  va_end(args);
+
+ vsnprintf(str,str_size + 1, format, args2);
+ va_end(args2);
+
+ xf86IDrvMsgVerb(priv->frontend, xtype, 0, "%s", str);
+
+ free(str);
 }
 
 void wcmLogSafe(WacomDevicePtr priv, WacomLogType type, const char *format, ...)

Re: Xlibre release 25.0.0.0 now available for testing

Reply #51
Thank you for the all the feedback.
The dev indeed was too trusting with this commit; I hope he rememberes this lesson.
It's good to know the patch works now.

artist

Re: Xlibre release 25.0.0.0 now available for testing

Reply #52
25.0.0.4 is now available; shortlog can be found on our Xlibre wiki page.

artist

Re: Xlibre release 25.0.0.0 now available for testing

Reply #53
maybe the transgender people are right and this fork ain't gonna go anywhere good
Please don't. It's depressing. Take off the Polaroid glasses. Be the change you want to see etc. etc. ........

Re: Xlibre release 25.0.0.0 now available for testing

Reply #54
I have just installed the xlibre iso (cinnamon-dinit) on two laptops and they are both working flawlessly so far. I do wish this project success and thanks to all who have made it possible!

Re: Xlibre release 25.0.0.0 now available for testing

Reply #55
25.0.0.4 is now available; shortlog can be found on our Xlibre wiki page.

artist

The freeze is still happening.

Re: Xlibre release 25.0.0.0 now available for testing

Reply #56
Has anybody tried to run a compositor (picom or compton) on this new display server? The opacity seems not working properly.

Code: [Select]
[chris@mars ~]$ picom --version
v12.5 (/srcdest/picom revision a456d43)
Supercalifragilisticexpialidocious

Re: Xlibre release 25.0.0.0 now available for testing

Reply #57
no, metux in his infinite wisdom unexported [...]
No, It wasn't Enrico, it was an MR by a 3rd party, this was only upstreamed by Enrico, so this character assassination is unnecessary.
[...] honestly that whole story actually is making me lose faith in xlibre [...]
Please, if you're gonna moan about alpha tier update that:
- Was never released to "stable" repos
- You have to go out of your way to install Xlibre either by enabling the repos or downloading the packages
- Was specifically said that this is for TESTING ONLY
Then maybe don't use it if you want something stable? Are you another one of those that expects enterprise-grade SLA reaction times for faults on FOSS software?
Because this pattern of entitlement is through the roof.

Re: Xlibre release 25.0.0.0 now available for testing

Reply #58
Everything works on my system now.  Great work, Artix dev!