Welcome!
Important information
-- Spectre and Meltdown vulnerabilities

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-18 Final release info here
-- Migration Information to MX-18 here
-- antiX-17.3 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

I'm playing whack-a-mole with XFCE bugs - screensaver edition

Report Bugs, Issues and non- pacakage Requests
Post Reply
User avatar
Guido
Forum Novice
Forum  Novice
Posts: 35
Joined: Sat Nov 10, 2018 4:21 pm

I'm playing whack-a-mole with XFCE bugs - screensaver edition

#1

Post by Guido » Sun Jan 13, 2019 11:05 pm

XFCE seemed so rock solid until I started to really use it.

When I use Code::Blocks 17.12 (based on wxWidgets 3.x), the screensaver will start randomly popping up while I'm editing. It comes up almost randomly. The screen looks like whatever the previous image for the screensaver *was* with a few widgets or a line of text randomly redrawn on top of it. It blocks the panel and background too. It's like there was a redraw command that didn't get propagated all the way and only drew the lowest level background. After the screensaver appears, Code::Blocks will redraw a few things, some of the panel icons will redraw, the background never does. It's random. If I move a window around, it will trigger a redraw and the whole screen redraws. However, killing the screensaver doesn't seem to help. So far as I can tell, wx 3.x has some basic ability to interfere with XFCE. They're both on top of gtk. Doesn't happen with anything else.

I have to have a screensaver to lock the screen.
I'm using the wx3.0.4 from the repo.

I really need to build my own wxWidgets and code::blocks. The code::blocks in the repo was built with wx3.0, which means the symbol browser is disabled. I think a build with wx2.8 will fix that problem and possibly the XFCE problem, but need to check it out. Either way, I'd like to report this as a problem and see if there are any suggestions for a workaround. Doing my own builds may not fix anything.

User avatar
manyroads
Forum Regular
Forum Regular
Posts: 546
Joined: Sat Jun 30, 2018 6:33 pm

Re: I'm playing whack-a-mole with XFCE bugs - screensaver edition

#2

Post by manyroads » Mon Jan 14, 2019 1:38 pm

I'd remove the screensaver... but I don't like them so am biased.
"Don't believe everything you think."
Pax vobiscum,
Mark Rabideau - http://many-roads.com
MX-18 4.20.0-antix.1-amd64-smp x86_64
Dell Latitude E5470
Dual Core Intel i5-6300U (-MT MCP-)
Mem: 8GB SSD: 978.09 GiB
Reg. Linux User #449130

User avatar
Guido
Forum Novice
Forum  Novice
Posts: 35
Joined: Sat Nov 10, 2018 4:21 pm

Re: I'm playing whack-a-mole with XFCE bugs - screensaver edition

#3

Post by Guido » Wed Jan 16, 2019 12:30 pm

LIke I said, I need a lock screen, and that means screensaver. ALSO, as I mentioned it's not the screensaver having the problem... I can kill the screensaver job and it still happens. This means it's something XFCE or related video driver is doing. It's just grabbing the last image the screensaver made and popping that to the top, then not doing a redraw. So, it's likely XFCE's problem.

I'm questioning the wisdom of using XFCE at all. The only reason I went with it is because I can actually get it to build and therefore, theoretically, have the possibility of fixing things. Does anybody on the MX actually do their own build of XFCE, or is this just repackaged? I'm not sure how to debug XFCE. Does it have a debugging or logging mode? The XFCE code is so old, glade-2 can no longer open the UI files. Also, the code isn't internally documented, so I'm in the process of creating my own documentation before trying fixes to the display settings.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2682
Joined: Wed Apr 11, 2018 5:09 pm

Re: I'm playing whack-a-mole with XFCE bugs - screensaver edition

#4

Post by fehlix » Wed Jan 16, 2019 4:46 pm

Guido wrote:
Sun Jan 13, 2019 11:05 pm
.. I have to have a screensaver to lock the screen.
The default screen-locker in MX18 is light-locker:

Code: Select all

Package: light-locker
Description: simple screen locker for lightDM display manager
 light-locker is a simple screen locker that aims to have simple, sane, secure
 defaults and be well integrated with the desktop while not carrying any
 desktop-specific dependencies.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 23429
Joined: Wed Jul 19, 2006 6:13 am

Re: I'm playing whack-a-mole with XFCE bugs - screensaver edition

#5

Post by Jerry3904 » Wed Jan 16, 2019 5:01 pm

I'm questioning the wisdom of using XFCE at all. The only reason I went with it is because I can actually get it to build and therefore, theoretically, have the possibility of fixing things. Does anybody on the MX actually do their own build of XFCE, or is this just repackaged? I'm not sure how to debug XFCE. Does it have a debugging or logging mode? The XFCE code is so old, glade-2 can no longer open the UI files. Also, the code isn't internally documented, so I'm in the process of creating my own documentation before trying fixes to the display settings.
Nothing forces you to use Xfce. There are many other possibilities in Package Installer and you can just log into the one you like instead.

We don't try to repackage Xfce any more than we try to repackage Debian Stable. Xfce 4.14 is in the works for release this year, so that should change a great deal. One other thing: "Xfce" is a collection of components, many if not all of which have a debug version (e.g., thunar-dbg) that can be installed via Synaptic.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, SSD 120 GB, Data 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB
Personal: XPS 13, 4.18.0-19.3-liquorix, 4 GB

Post Reply

Return to “Bugs and Non-Package Requests Forum”