SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
Originally Posted by ndavilam
Hello friends, I have a problem.
After a few minutes xfce crashes, but when trying to unlock my computer there is a black screen.
This did not happen weeks ago.
Do you know why this happens?
Slackware -current? Just I think Xfce screensaver is starting by default now, what does happen if you disable (or configure) it?
Just curious. I just noticed that the orage calendar app has been revitalised with a stable 4.18 release earlier this year with significant changes since 4.12.1 that was dropped from Slackware. Can anybody share their experience of building and running the latest orage calendar app?
I just built it because I used to use Orange and simple as it is it was the basic reminders app I needed. I grabbed the old slackbuild from 14.2, and used it to build the 4.18.0 release, on 15.0. Compiled/built/runs and seems to work just fine.
In terms of features and what not it seems pretty much unchanged from 4.12.0 just supports updated XFCE and libs.
Yes, I have done the same thing. I notice the option to add a tray icon has gone and it just loads into the tray automatically. The update to GTK3 means that my dark theme is applied.
I edited out the specification of the includes to libical to see whether the comment about libical's pkgconfig file being incomplete still applies, but I am not sure of how best to test this.
Could be fun to build radicale from SlackBuilds.org as a simple CalDAV server to see whether I can sync the calendar on my iPhone, but that apparently involves some dancing around with SSL certificates.
Another annoyance with 4.12.1 that I saw was how orage would pop open after fiddling with displays using xrandr. This looks as though it is supposed to be fixed, but I no longer have the system that I could easily trigger this on. Still working on a new test case.
Just a follow up.
The problem with orage popping open when an external monitor is plugged/unpluggeg is still occurring for me.
Yes, I can import and export calendars successfully with my build of orage that does not specify the libraries.
I now have radicale running behind an Apache reverse proxy backed with a wildcard SSL certificate from LetsEncrypt. Learning how to successfully complete an ACME dns-01 challenge using dnsmasq on a server behind a modem with a dynamic DNS address took some time.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Original Poster
Rep:
Quote:
Xfce's Wayland Roadmap Updated
By Michael Larabel. 13 September 2023.
Xfce 4.18 released last December with some strides on the Wayland front for this lightweight GTK-based desktop environment, but more work remains before Xfce will be fully compatible with Wayland and its own robust compositor. The Xfce Wayland road-map was recently updated to reflect the latest work on this major undertaking.........
Can someone recommend a good weather plugin for XFCE4? Looks like this one is having issues, if your longitude is negative, and while I'm told Kazakhstan is an interesting place, moving there would mean one hell of a commute.
I’m on Slackware 15.0 (not-current). Don’t know if I should post here or create a new thread. Creating a new thread seemed wasteful since this thread is about eveything related to Xfce. Let me know if I should delete this and create a new thread instead.
I've come across a problem with xfce4-appfinder, and I'm not sure if it is a bug that exists upstream or Slackware's defaults as I don't have a secondary device I can use to check for this bug in the latest version of xfce4-appfinder.
I always install Slackware without /e and /kde. I use Xfce as my main DE. I also use xfce4-appfinder for launching applications when I'm too lazy to move my hand over to the mouse.
Just now, for the first time ever, I mistyped "gvim" as "vim" in xfce4-appfinder. My X11 session froze. By that I mean everything was unresponsive except for the mouse. I could move it but not click anything. No new window opened, nothing happened. Tried to Alt+Fn<number> to switch to another session, that did not always work but when it did, i tried switching back to the original session and everything was still frozen. I couldn't figure out what caused the issue, so I tried these:
1) Reboot-ed and changed the default terminal back to the default xfce4-terminal, tried the same thing. Issue persists, everything froze.
2) Opened a new session, spawned a terminal and manually invoked "xfce4-appfinder"(non-collapsed) which, upon (intentionally) typing "vim" lead to gvim opening by default. Tried a few more times, no issue, gvim opened every single time.
3) In the same session as (2), manually invoked "xfce4-appfinder -c" (collapsed) and typed (intentionally) "vim". gvim did not run, instead after around 2 seconds, vim(terminal) opened up in the xfce4-terminal. After exiting vim, warning stated:
"Vim: Warning: Input is not from a terminal", which, i mean is uh, called for. Session was not affected, nothing happened.
I noticed in (2) and (3) xfce4-appfinder did not close within the terminal(I guess its supposed to be always running in the background) unless i either kill it(pid) or ctrl-c within the terminal.
If you try to replicate this, do it on a separate device or post-reboot so you won't lose any work when the DE freezes.
Now is this issue replicate-able or is it just localized to my desktop/configuration/session?
Note: I may not reply immediately due to the time difference/jetlag, i apologize in advance for my irresponsible behaviour.
Update: Problem solved after a reinstall and a full upgrade, was localized to my system/configuration, not a bug.
Last edited by BSD_areMyInitials; 10-14-2023 at 02:50 PM.
Reason: problem solved
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.