You are not logged in.
Hello everyone.
I seem to be unable to change locales (interface) on some applications, GIMP, Inkscape are the ones tested for now.
I am running on KDE and KDE apps seems to function fine in this regard so I guess it has to do with GTK applications; it didn't use to be like this before though.
All the appropriate language files are present but the programmes seem unable to read them; GIMP, for instance, regards the present of the lang-file but after a restart the language stays the same.
Any tips on this one?
Cheers,
Olav
Fond of you all!
Thanks for doing Devuan.
Cheers,
Olav
Hei Altoid.
Could this be related to having replaced consolekit with elogind?
I have not seen or noticed any adverse symptoms.
I went through the same procedure as you did, upgraded from ASCII to Beowulf; so, I don't think it has to do with that.
KWallet is working but, if I remember correctly, I had some issues initially; think I started from scratch and deleted every (user) kwallet associated files and repopulated the walletDB.
Not a good answer, and no proper solution, but that's how I believe I did manage to get the KWallet back working.
If you investigate further, which I didn't, you'll probably find a better way; the meaning of this reply was to state that it definitely may work!
Best of luck,
Olav
Thanks:)
Wait for tuxd3v's input then, to see if it's the right one.
Hello all!
What would be the right choice of architecture to download for an ARM Cortex-A9?
Cheers,
Olav
PS
All my current computers runs fine on Devuan!
Did not mean to have focus away from you're issue dice, sorry about that!
F_Sauce wrote:Hei Andy, I'll check, back soon.
Oh noes, F_Sauce might be caught in a time warp.
![]()
I'm a bit nostalgic, used to play (occasional «now» as well) some old games on it.
CPU: https://en.wikipedia.org/wiki/Pentium_III, still running fine!
GPU: (PCI) https://en.wikipedia.org/wiki/GeForce_FX_series.
Upgraded (spinning) hard-drives, but with 1999 original mother-board and RAM.
If you are very interested Andy, I will give you all the current hardware details; I booted it up last probably a year ago, no trouble I presume!
When I first installed Linux and SuSE 9.1 ... , it was newer hardware; it was a Dell from 2002/3 with a Pentium 4 CPU, I threw away Windows and started ![]()
Cheers,
Olav
Hei Andy, I'll check, back soon.
Beside the point all of this!
My former main-computer (day to day) was an Intel Q{xxx}, from 2007 (until 2019) I think?
I gave it away to my mum, but when I had it, it were constantly on; I think it is like that now as well; running all the time, without trouble (changed HD's of course).
My oldest OS is running on devices from 1999; SuSE 9.1. is installed now, I am a bit nostalgic.
Trouble with kernel, try to compile it yourself; it isn't too hard really; I started out with music as focus, building Linux DAWs; bit of a struggle, but got there in the end![]()
Please «boycottsystemd», be reasonable; I don't think there were any ill will in this case.
Good that you found a solution to you're problem, though.
Olav
Hi again.
I'm very happy with Devuan; but, what I actually wanted to point out (or thought I wanted to) was the viability of a non-systemd Linux environment, hence referring to those statistics.![]()
A bit perplexed now ![]()
OK ![]()
No, I did not know that DistroWatch were bullshit, and yes, that was what I refered to;
sorry about it!
Hi all!
I think maybe I saw this refered to before, somewhere here perhaps; however, it should be encouraging statistics for Devuan!
https://distrowatch.com/index.php?dataspan=52
Cheers,
Olav
This is a bit strange: I just restarted the installation not in expert mode, but with 'install' (first option on first screen). It now gives me all the filesystems options that I'd expect, including ext3 and ext4.
OK ![]()
Still strange though; you should have the same options in expert mode.
In any-case, hope you find a good solution and do well, and enjoy Devuan!!
Cheers,
Olav
Hi again.
Is this a fresh install, or are you migrating?
I have never experienced the lack of ext(x) options during an installation, I've done quite a few.
You may have issues with the install medium/image; perhaps you could try download Devuan again, and start afresh?
Cheers,
Olav
Hei.
No, this is a strange case, ext4 is on all mine partitions.
Maybe you could elaborate a bit more on: hardware, install medium, procedure ...?
Hei.
There is probably not too many programmes unique to only one distro, Linux is mostly Linux; however, having been with SuSE for 10-15 years, or so, I do miss YaST.
Cheers,
Olav
https://wiki.debian.org/iwlegacy
I believe Head_on_a_Stick and fsmithred might be on the track.
Cheers,
Olav
I'm very sorry for not following up this topic!
How are you doing?
It's really a sad mess this, PulseAudio does not offer anything which were not available in the first place; PA is just an unnecessary layer!
More of a mess comes from development thinking this is the future.
I have two computers running Devuan and one very old one running SuSE 9.1; the SuSE one is for nostalgic reasons, I was on SuSE for 13 years or so.
It may be that there is an issue with the legacy driver, I don't know.
But one thing I have experienced is that combining the official repoes and backports may result in conflicts; I haven't followed the thread closely so might have overlooked if you'we already done this, but I would try to get rid of all NVIDIA packages, disable the backports repo and start a fresh.
BTW, I have two computers running Beowulf, I have no issues with them; the problem I refer to was with ASCII, I learned from that and has not tried the same approach which gave me problems in ASCII on Beowulf.
Olav
Hei!
Do you use PulseAudio or not?
Olav
I run the proprietary NVIDIA driver without any issues on Beowulf, no lock-ups on my two computers I run this OS on (NVIDIA 970 and 760, respectively); I use the NVIDIA packages from the repo.
One thing though, if one has enabled the «backports» repo when installing the NVIDIA driver packages one might come into package conflicts; at least that was my experience a couple of times in ASCII. If this is the case, one might try removing all NVIDIA packages, disable «backports» and try again.
Just a suggestion.
Cheers,
Olav