You are not logged in.
Hello:
Trying out the new version ...
... pretty serious regression ...
Haven't tried it yet.
But I've seen that regressions are not something unheard of.
More so in recently <resurrected | previously declared abandoned> | <dead> software.
... new version uses the "correct" DPI and breaks scaling ...
Nice.
Hmmm ...
Bummer.
You may want to consider giving Kanapickas a (well deserved) hand and report the bug in as much detail as possible.
https://gitlab.freedesktop.org/xorg/xserver/-/issues
I'm sure he'll appreciate your input and see to get it straightened out soon enough.
And all will be well again. 8^D
Best,
A.
Hello:
... SLIM is no more maintained ...
... sort of deprecated.
For the longest time more or less the same was said of Xorg-server.
But there it is, born again so to speak.
https://xorg.freedesktop.org/archive/in … 1.1.tar.gz
Reminds me of reports of deaths being greatly exaggerated ... 8^D
This thanks to someone (Povilas Kanapickas) who stepped up.
And despite this dumb Python2 decision, I believe Wicd will also survive.
Apparently SLiM (ArchWiki) it is not fully compatible with systemd, including logind sessions.
It is an excellent example of Linux philosophy, I like it much more than any of the other DMs I have tried.
ie: lightweight, easy to configure, requires minimal dependencies and is independent of the DE: ticks all the boxes.
SLiM works for me on Devuan so that's what I use.
I recall that installing SLiM solved all the auth/log-in issues I was having in Devuan by not having a DM.
--> I think it should be the default Devuan DM.
I have read that GhostBSD 10.3 dropped GDM in favour of SLiM back in 2016 and is still there.
See http://www.ghostbsd.org/10.3_enoch
Hopefully someone will eventually step up and update it so it can be used with non-systemd distributions.
Use a systemd distro?
Then use one of those other bloated DMs.
If I cannot have it in the future, I'll just opt for not using a DM and see how I manage to work things out.
Best,
A.
Hello:
Just received this in my inbox.
--- snip ---
This release fixes two relatively important issues that slipped into 21.1.0.
Jon Turney (1):
s/__/@/ in inputtestdrv manpage
Matthieu Herrb (1):
Make xf86CompatOutput() return NULL when there are no privates
Povilas Kanapickas (2):
Makefile.am: Add missing meson build files to release tarball
xserver 21.1.1
git tag: xorg-server-21.1.1
https://xorg.freedesktop.org/archive/in … 1.1.tar.gz
PGP: https://xorg.freedesktop.org/archive/in … tar.gz.sig
--- snip ---
As you can see, xorg-server is indeed alive and well.
Here's hoping Debian picks it up soon.
Kudos to Povilas Kanapickas!
Best,
A.
Hello:
... running all that Raspberry-ARM-stuff in a virtual machine on your "Sun Ultra24"-box ...
No.
Sorry if I was not clear.
Too early or too late, can't recall. 8^|
I had a long unused Devuan ascii (VBox) virtual machine on my U24 and managed to install Pi-Hole v5.6 on it.
I found a video on line with instructions on how to do it on Ubuntu Server (roughly same thing) and the run it as a recursive DNS server.
https://www.youtube.com/watch?v=FnFtWsZ8IP0
You have to watch it a few times to get a grasp of it, especially if you have not done it before but it is roughly all there.
The chap talks a bit fast, you'll have to do some stop/backwards with the video feed and strain your eyes a bit.
It does involve a no-no: an automated install script from the Pi-Hole website but you have alternatives if that makes you feel unsafe.
Installing Pi-Hole on Devuan ascii was quite straightforward although it is not a supported OS, you just have to override the initial OS check.
Instructions are on-screen when you run the script.
Then you have to install unbound for the DNS server bit.
Find it on the Devuan repository.
I then set the Devuan ascii virtual machine to start at boot and that's about it.
See https://pgaskin.net/linux-tips/configur … autostart/
A small side effect is that my box's boot sequence lags for a shortish while when the system starts the MTA.
This is due to a failed reverse DNS lookup that Exim4 is attempting at boot and happens because the DNS running on the virtual machine is not up yet.
Haven't found a suitable solution for that yet.
------
EDIT I:
It's an exim4 caused problem.
Solution to that here: https://dev1galaxy.org/viewtopic.php?id=4672
------
As for how Pi-Hole works, it seems alright but there are quite a few things that require uBlock to remain in my browser (Pale Moon).
You Tube adds is one of them.
I still have to dive into Pi-Hole fine tuning, just a question of time.
------
EDIT II:
Fine tuning was basically disabling the Pi-hole cache and letting the Unbound DNS do that job on the VM.
See: https://medium.com/nerd-for-tech/recurs … a766d4f703
As for You Tube ads, it seems that your best bet would be uBlock.
------
Some things are supposed to be intercepted/sunk by Pi-Hole but they still show up as blocked by uBlock, have to do dome research on that.
------
EDIT III:
The reason to that is that while Pi-hole just blocks requests to ads, uBlock still thinks that there are ads to be blocked, even though they were blocked by Pi-hole. Pi-hole can't modify the web site that you see, so it can't signal to uBlock that an ad is blocked.
The only way for uBlock to know that Pi-hole blocked an ad is to see if the ad's image/resources are missing.
Otherwise, uBlock sees that there's a match against their filter, even if it's already blocked, and tries to block it.
But that means it is blocking an empty element.
ie: already blocked by Pi-Hole.
------
Thanks for your input.
Best,
A.
Hello:
You still need proprietary boot files from an SD card to boot via the network.
Hmmm ...
I am not at all versed in how all this works and maybe don't understand it all well enough.
Please bear with me. 8^)
From what I do (?) understand, the usual way is to run Pi-Hole on a RPi.
The OS on the RPi can be the default one and I understand that it can also be Devuan.
But that's for later ...
My ADSL router (no WiFi, just cable) would use the RPi running Pi-Hole as a DNS instead of using a DNS from the net.
In this way Pi-Hole would filter all the unwanted crap from the web before it gets to my box.
The advantage being that it never gets loaded to then be blocked by uBlock and such.
My rig then would not waste resources (memory/CPU cycles, etc.), my browser would run lighter and as a result the connection is cleaner, safer and faster.
Is this an accurate account?
Thanks in advance.
A.
Hello:
I have an idle Raspberry Pi3B+ and have been wondering about setting up Pi-Hole and see if I can speed up my ADSL connection.
Then I thought that maybe it could be run from a VM on my Devuan box and have it come up with the OS instead of booting a RPi.
My Devuan Beowulf rig runs on a Core2 Q9550/8Gb. Sun Ultra24 WS,
Any suggestions?
Thanks in advance,
A.
Hello:
... understand why now ...
Quite so ...
Result of not enough (or too much) coffee. 8^|
use dpkg -l like so to search for unneeded config files.
dpkg -l | grep ^rc
Yes.
Came up empty, as it should.
then remove them like this.
sudo apt purge "~c" <-- double quotes.
Nothing to purge.
@Altoid, perhaps you where thinking
apt list --installed
Hmm ..
No, I was quite evidently not thinking, at least not coherently.
I started doing it right ie: with dpkg -l ... but at some point wandered into apt list | grep residual ... 8^|
What else could have come up but a file named "residual"?
Thank you both for your input.
Have a good week-end.
Best,
A.
Hello:
I run Devuan Beowulf on an Asus 1000HE netbook, used only for coffee roasting duty or to take along if I am out of town.
root@eee-dev3:~# uname -a
Linux eee-dev3 4.19.0-18-686-pae #1 SMP Debian 4.19.208-1 (2021-09-29) i686 GNU/Linux
root@eee-dev3:~# Being rather limited (Atom 280+2Gb), I try to keep it thin and free of stuff I don't need/want.
Recently I cleaned up a lot of residual files but I have come across a couple of rather stubborn ones:
root@eee-dev3:~# apt list | grep residual
residualvm-data/oldstable 0.3.1+dfsg-1 all
residualvm/oldstable 0.3.1+dfsg-1 i386
root@eee-dev3:~# I have no idea as to where these two came from as I have never installed anything related to them.
eg: 3D games, etc.
I cannot seem to get a reasonable answer to this:
oot@eee-dev3:~# apt remove --purge residualvm
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'residualvm' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@eee-dev3:~# oot@eee-dev3:~# aptitude why residualvm
Not currently installed
The candidate version 0.3.1+dfsg-1 has priority optional
No dependencies require to install residualvm
root@eee-dev3:~# Independently of how this file happened to be (?) in my system, how can I get rid of it?
Thanks in advance,
A.
Hello:
Good news ...
Just received this in my inbox.
---
This is the final release of X server 21.1. There has been just one fix since
the second RC and at this time there are no known regressions since the 1.20
release series.
I expect that increased usage after the final release may still uncover
something interesting, so there is a potential for subsequent 21.1.1 patch
being released in the coming weeks rather than after the usual interval of
several months.
Notable changes since 1.20 include:
- The meson support is now fully mature. While autotools support will still be
kept for this release series, it will be dropped afterwards.
- Glamor support for Xvfb.
- Variable refresh rate support in the modesetting driver.
- XInput 2.4 support which adds touchpad gestures.
- DMX DDX has been removed.
- X server now correctly reports display DPI in more cases. This may affect
rendering of client applications that have their own workarounds for hi-DPI
screens.
- A large number of small features and various bug fixes.
Note that since 21.1 series XWayland is released separately and thus this
release does not include it.
--- snip ---
---
git tag: xorg-server-21.1.0
https://xorg.freedesktop.org/archive/in … 1.0.tar.gz
https://xorg.freedesktop.org/archive/in … 1.0.tar.gz
Best,
A.
Hello:
... Debian hybrid Systemd-SysV-OpenRC gives me the creeps.
I can't see a reason to move.
+10
Because there is none.
But most important: the OPs original question has_already_been_answered (very wisely) by one of our admins.
Trust is a fragile thing and not easy to repair.
It's about more than code ...
As far as I am concerned, golinux's answer was more than enough.
What else was needed?
I cannot believe time and resources are still being wasted on this thread, three pages long and started eight months ago.
A thread to justify/question Devuan's existence and what it stands for?
Absurd.
A.
Hello:
Is there a source for supported sound cards?
Of course.
Just have to look ... ;^D
https://wiki.debian.org/SoundCard
http://linux-sound.org/drivers.html
https://wiki.linuxaudio.org/wiki/hardware_support
Best,
A.
Hello:
... would guess this is related to whatever service pcmanfm uses to mount drives.
This is what I have installed:
groucho@devuan:~$ apt list | grep installed | grep ud
--- snip ---
udev/oldstable,now 1:3.2.9+devuan4 amd64 [installed]
udiskie/oldstable,oldstable,now 1.7.7-1 all [installed]
udisks2/oldstable,now 2.8.1-4+devuan1 amd64 [installed,automatic]
groucho@devuan:~$ But none of these are listed as dependencies for PCManFM.
Now that I know what is going on, it is not much of a problem, but I do consider it to be a bug.
Thanks for your input.
A.
Hello:
Any ideas?
Seems not.
It took me a good while as I was not able to find anything about this on the web (maybe was not looking properly?).
So I resorted to a trial and error method.
The answer:
If a device shown in Devices is not mounted, instead of getting the expected pop-up ie: Authentication required to mount XXXX nnnnn (/dev/sdxN), you get the error I made reference to in my OP.
This is something that had not occurred to me: the expected behaviour is that you get the pop-up asking for the credentials or at the very least a pop-up saying that the user is not allowed to mount the bloody device instead of one saying that the specified directory is not valid.
Why is this so?
No idea.
Is it a bug?
Probably.
Posted.
https://sourceforge.net/p/pcmanfm/bugs/1129/
Let's see what happens.
Best,
A.
Hello:
... believe that relates to accessibility features ...
Ahh ...
That accessibility.
Thanks for clearing that up for me.
So many things one takes for granted in life ... 8^|
Someone on the team is attempting to port it to python3.
Good to know.
The Devuan Package Information page shows this:
wicd
1.7.4+tb2-6+devuan2
http://deb.devuan.org/merged chimaera-proposed-updates/main amd64
http://deb.devuan.org/merged chimaera-proposed-updates/main i386
http://deb.devuan.org/merged chimaera-proposed-updates/main arm64
http://deb.devuan.org/merged chimaera-proposed-updates/main ppc64el
And the wicd home page says:
Awaking from deep sleep
Written for wicd by Andreas Messer on 2021-10-14The wicd project has been in state of deep sleep for a while now while Python, GTK continue to develop. I'm trying to get it back on track. This will need several major changes to its code base and will take some time.
The previous entry in the Announcements was from 2014-12-21, almost seven years ago.
Seems more like a coma than deep sleep.
I'm in no hurry to leave Beowulf, so I can wait.
Thanks for the heads-up.
Best,
A.
Hello:
I have just been reading Devuan 4 Chimaera Release Notes and saw two things that called my attention:
1.
Note that slim (the default Display Manager for xfce) is not
accessible. Be sure to install lightdm or gdm3 if you require an
accessible Display Manager.
Q: why is this so?
It works perfectly well in Beowulf, why not in Chimaera?
The Devuan Package Information page says it is available for chimera, daedalus and ceres:
slim
1.3.6-5.2+devuan1
http://deb.devuan.org/merged ceres/main amd64
http://deb.devuan.org/merged daedalus/main amd64
http://deb.devuan.org/merged chimaera/main amd64
2.
wicd
Wicd is no longer available in Devuan 4 Chimaera having been removed
from Debian Bullseye because of it's dependency on python2 which is now
obsolete.
I have always liked wicd, other conneciton managers I tried gave me endless grief.
I think I have other applications that depend on python2 ...
Thanks in advance,
A.
Hello:
Bump ...
Posted to the PCManFM sub-forum at LXDE and the only answer received suggested I was probably posting to the wrong forum as Devuan Beowulf installs with Xfce and not lxde (!!!) and directed me back here. 8^D
https://forum.lxde.org/viewtopic.php?f= … e85d2bfbd0
Any ideas?
Thanks in advance,
A.
Hello:
On my Devuan Beowulf installation with a backported kernel ...
groucho@devuan:~$ uname -a
Linux devuan 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64 GNU/Linux
groucho@devuan:~$... when I open the filemanager (PCManFM 1.3.1) and go to the Devices folder, I can see all my drives.
But when I click on any of them I get this:
Error
The specified directory 'computer:///
Hitachi%HTS543216L9SA00.drive' is not valid
The taskbar for this example reads: computer:/Hitachi HTS543216L9SA00: 160 GB Volume
I think there is something wrong here but I can't find what it could be.
Any ideas?
Thanks in advance,
A.
Hello:
Received this update this morning, seems it is coming along fine.
----
This is the second release candidate of Xorg 21.1.0 release.
We have a number of fixes since the first RC.
Alex Richardson (1):
dix/privates.c: Avoid undefined behaviour after realloc()
Mario Kleiner (6):
xfree86: Avoid crash in xf86RandR12CrtcSetGamma() memcpy path.
xfree86: Let xf86RandR12CrtcComputeGamma() deal with non-power-of-2 sizes.
Revert "modesetting: Only use GAMMA_LUT if its size is 1024"
modesetting: Enable GAMMA_LUT for lut's with up to 4096 slots.
modesetting: Handle mixed VRR and non-VRR display setups better.
modesetting: Consider RandR primary output for selectioh of sync crtc.
Olivier Fourdan (1):
glamor: Fix leak in glamor_build_program()
Povilas Kanapickas (1):
xserver 21.1 RC 2
Ray Strode (1):
xkb: Drop check for XkbSetMapResizeTypes
nerdopolis (1):
xf86: Accept devices with the 'simpledrm' driver.
git tag: xorg-server-21.0.99.902
https://xorg.freedesktop.org/archive/in … 902.tar.gz
SHA256: 11d8f4bb405bfb0ebed23fb524ff355dcc9fa5013fcb32557eb733b09297ce51
---
Best,
A.
Hello:
Not quite sure what that says about Devuan . . .
Indeed ...
I'd add that there are 10 pages of unanswered posts to which no one had anything to say.
The last two pages being from this year.
Best,
A.
Hello:
Just a heads-up.
Got this in my inbox this evening from xorg-announce@lists.x.org:
This is the first release candidate of Xorg 21.1.0 release.
Notable changes since 1.20 include:- The meson support is now fully mature. While autotools support will still be
kept for this release series, it will be dropped afterwards.- Glamor support for Xvfb.
- Variable refresh rate support in the modesetting driver.
- XInput 2.4 support which adds touchpad gestures.
- DMX DDX has been removed.
- X server now correctly reports display DPI in more cases which may affect
rendering of client applications on hi-DPI screens.A large number of small features and various bug fixes.
Note that since 21.1 series XWayland is released separately and thus this
release does not include it.I expect to push subsequent release candidates roughly every two weeks.
The following is a full changelog since xserver 1.20.0. ...
--- snip ---
The changelog follows, long-ish as would be expected from such an upgrade. ie: 1.20.0 -> 21.1.0
The X.org site most surely has the details if anyone is interested in the details.
Seems that TEM was quite right. 8^D
https://dev1galaxy.org/viewtopic.php?pid=26536#p26536
It's FUD from Microsoft related company. X.org is still alive.
X.org is indeed still alive.
Best,
A.
Hello:
Altoid wrote:ie: Does it write to the conf file?
No it doesn't. It bypasses xorg.conf completely.
I found this bit at https://wiki.archlinux.org/title/Displa … _Signaling
Note:
XScreenSaver and xfce4-power-manager use their own DPMS settings and override xset configuration.
See XScreenSaver#DPMS https://wiki.archlinux.org/title/XScree … g_settings
and
Xfce#Display blanking https://wiki.archlinux.org/title/Xfce#Display_blanking
To note for anyone using Xfce:
XScreenSaver
If xscreensaver is installed and runs alongside Xfce Power Manager, it may not be clear which application is in control of blanking and DPMS as both are competing for control of the same settings. Therefore, in a situation where it is important that the monitor not be blanked (when watching a video for instance), it is advisable to disable blanking and DPMS through both applications. To know more about XScreenSaver options, see XScreenSaver#DPMS and blanking settings.
Hmm ...
... competing for control of the same settings.
A classic case of right hand not knowing what left one does or too many fingers in the pie.
Maybe a bit of both, you'd think the chaps at Xfce would be a bit more careful.
As my WS is not dependent on battery power, I long ago decided to get rid of xfce4-power-manager and all associated files.
Cheers,
A.
Hello:
... bypasses xorg.conf completely.
Interesting ...
Thanks.
I'll give it a read.
... need to figure out which system boot script would be the best ...
I guess (?) you could write up a script, save it to /usr/local/bin/ and put it in your /etc/rc.local so it will run.
eg: this is the stuff I have in mine, with comments.
groucho@devuan:~$ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
#
# to set all /proc/acpi/wakeup entries to 'disabled'
# no wakeup from S4 for anything
# does not survire reboot that's why it is here
# see https://dev1galaxy.org/viewtopic.php?pid=29113#p29113
#
/usr/local/bin/acpi_wakeups.sh
#
# to disable wol via ethtool at boot
# does not survire reboot that's why it is here
#
# /sbin/ethtool -s eth0 wol d
#
# 20210602 - changed for script in /usr/local/bin
# see https://dev1galaxy.org/viewtopic.php?id=4349
#
# /usr/local/bin/no_wol.sh
#
# e1000e module is now patched to disable WoL
# see /usr/src/e1000e-patch 1001
groucho@devuan:~$ May take a while I'm afraid ...
Nah!
Try the rc thing, should work.
The trick is to write the script with the correct syntax. 8^|
Best,
CIV
Hello:
... forgotten about DPMS and a quick search on the web gave me the command
xset dpms 0 0 0 && xset s noblank && xset s off #as root!
I wonder how that command relates to the settings in xorg.conf.
ie: Does it write to the conf file?
Could you please post the link where you got the information?
TIA.
Best,
A.
Hello:
Plain Beowulf+Mate install.
I run Beowulf on a backported kernel, Xfce and a three monitor setup:
Linux devuan 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64 GNU/Linux
It uses two Nvidia FX 580 (G96GL) cards and Nvidia proprietary legacy drivers.
I set up my xorg.conf file with DPMS set to disabled:
Section "Screen"
Identifier "ScreenLeft" <- same for "ScreenCenter and "ScreenRight"
Device "DeviceLeft"
Monitor "Monitor0"
DefaultDepth 24
Option "DPMS" "False"
SubSection "Display"
Depth 24
Modes "1280x1024"
EndSubSection
EndSection
This is clearly reflected in /var/log/Xorg.0.log:
groucho@devuan:~$ cat /var/log/Xorg.0.log | grep -i dpms
[ 33.335] (**) Extension "DPMS" is disabled
groucho@devuan:~$ In addition to all this, if I run Applications -> Settings -> Screensaver (XscreenSaver 5.42) I get a pop-up that says
Warning:
The XScreenSaver daemon doesn't seem to be running on display ":0.0".
Launch it now?
My three monitors are 2x SyncMaster 940n + a Dell P1914S in the centre.
One would think that none of them would blank at all, no?
Well, one of the SyncMaster 940n units ("ScreenLeft" in xorg.conf) turns off after a while.
No idea why and does not really matter but ....
Best,
A.
Hello:
... what is everyone using as their email program?
Everyone?
Nope, probably just me. 8^)
In my previous life as a MS OS user (DOS5.5 / W3.11 -> XPSP3), after a short run with the free version of Eudora, I switched to Pegasus Mail in early 1996.
Many years later, being able to use Pegasus Mail under Linux (via Wine) was one of the two deal-breaking programmes that made it possible to make a seamless switch to Linux and leave the MS OS environment for good, the other was Judd Montgomery's JPilot.
Once comfortably settled within Linux, I tried out most if not all the available options but none were good enough, Claws-Mail coming close.
But it simply did not have the same functionality I have come to appreciate in David Harris' free albeit not open source programme.
This year marks the 25th. I have been using Pegasus Mail and can only say it is quite solid and reliable, has never let me down.
Just my $0.02.
Best,
A.