You are not logged in.
Hi @Sector11,
Thanks for your offer of help. However, I'm reasonably happy with that conky file I posted in the configuration thread, which was why I posted it there - in the right distro (and I've got it set up in Fedora Rawhide at the moment), I think it's fine.
I've recently downloaded the latest version of Bunsen Boron and when I get that one set up and running, that will be the time I'll be looking for a more Gotham-type Conky config.
Last edited by Colonel Panic (2023-08-28 19:43:31)
Online
@ CP
Totally respect that.
Enjoy.
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
@ CP
Totally respect that.
Enjoy.
Thanks, I will.
A couple more distros have come out this week that may be of interest; the latest version of AntiX (23), is one, and also the latest version of Pardus, also by coincidence 23 but which I haven't tried (I've got the beta version of AntiX 23).
Online
My old computers are getting on in years. The siduction installations on them (kde-plasma 'patience'2017 and lxde 'paint-it-black'2016) are also not the youngest anymore and show their quirks.
So, I took the latest ISO without X and installed it in QEMU
with the Tilling window manager dk. The goal is to repeat this later on one of the 'old ones' because it's 'easy' and I like the keyboard operation. Thanks to @cog and @knob for the ideas and to the developer of dk, @natemaia.
A few remarks on how I proceeded.
First, thanks to the siduction team for the nox. It is perfect, has no bugs (anymore) and is also OK with 1,1GB size.
-I always recommend to prepare the partition(s) with gparted;
-the small cli-installer is in english;
-its defaults are correct except for the use of os-prober, although deselected in the detection of other OS for GRUB;
-after the installation and the first reboot (we are back in tty1), a system update is mandatory. If a new kernel was installed, another reboot is necessary.
-debian requires for dk
libxcb-randr0-dev libxcb-util-dev libxcb-icccm4-dev libxcb-cursor-dev libxcb-keysyms1-dev sxhkd-I had the premonition to set up sudo
root
password:
usermod -aG sudo username-for the dk installation, the easiest way is then to clone the above @natemaia repo into the nox
git clone https://bitbucket.org/natemaia/dk.gitI then installed thunar; mousepad; xfce4-terminal; lxappearance; feh; xinit; rofi; polybar to work with.
Done.
Edit
-I had the premonition to set up sudo
you could also use doas or now opendoas as a tool in siduction. I have not thought about it. ![]()
Last edited by unklar (2023-09-01 17:35:12)
Offline
Interesting!
/Martin
"Problems worthy of attack
prove their worth by hitting back."
Piet Hein
Offline
@unklar, and your review? How complete is it, how's the workflow, stability, RAM usage, bugs etc...
I don't care what you do at home. Would you care to explain?
Offline
@unklar, and your review? How complete is it, how's the workflow, stability, RAM usage, bugs etc...
Well, do you mean siduction or dk?
I swear by siduction, have been using it since 2009 (at that time still aptosid). The workflows (rules - you know them) are second nature and I have NEVER experienced a bust (forced reinstall) because I pay attention to what apt tells me.
This NOX has the best quality so far. No errors. As the 'manifest' says, about 1300 packages, which is already a significant improvement over before, where the enormous number of packages always upset me. The team is just too small to take care of everything - see my beloved lxde with openbox, which is no longer in the 'offer'.
This is now my third installation with the cli-installer. I'm still 'yanking' around with it. Really sure sometimes I am not... But through him I have learned how to use cfdisk.
As for dk, I'm thrilled and still grateful to @cog for giving me the sugar with 'hatchery'.
I play now three days with this installation, today I searched and found a power-menu for rofi. What I haven't figured out yet is how to remove entries in rofi when the program is no longer there.
As for RAM, it's all not much different, as with others. In short: siduction always brings plenty; dk is frugal! ![]()
But what I have already seen as a 'bug'(?), when not used for a long time, the tapte and polybar area display disappears 2-10. It helps to log on -and log off.
Offline
^ Awesome review, thank you. I also started getting deeper into Linux distros with Aptosid. Devil, in particular, seemed like someone who really knew his stuff. His temporary packages when things broke on Debian unstable were amazing.
The only reason I don't run siduction is because I had to leave an aptosid system without updates for like 6 or 7 months, and the timing for Debian development was really bad on my part, so when I went to finally update the system it flat out broke. Even if I knew going in that it was going to break, I don't think I could have worked up an Apollo 13 sequence of steps to get it to boot after that dist-upgrade.
Thankfully, Debian stable is pretty current these days, and you can leave that system alone for seven months without blinking an eye.
I don't care what you do at home. Would you care to explain?
Offline
I've just downloaded the latest version of Manjaro 23.0 (XFce). I've had problems with earlier versions of Manjaro because it wouldn't find my network card, but this one is working well.
I've also got Siduction 22.1 installed ("Standing on The Shoulders of Giants", the distro's tribute to 30 years of Debian's being in existence) and it's mostly OK except that udisksctl doesn't work. I've made a post to this effect on the Siduction forum but haven't had a reply so far.
Last edited by Colonel Panic (2023-09-06 10:57:13)
Online
I've also got Siduction 22.1 installed ("Standing on The Shoulders of Giants", the distro's tribute to 30 years of Debian's being in existence) and it's mostly OK except that udisksctl doesn't work. I've made a post to this effect on the Siduction forum but haven't had a reply so far.
What, this?
https://packages.debian.org/sid/udisks2
So that means, what... you can't file-browse your phone or other connected device?
I don't care what you do at home. Would you care to explain?
Offline
Hi hhh,
I don't have a connected 'phone, my problem is not being able to use udisks2 to access my other hard drive partitions from within Siduction. Basically, it times out;
https://forum.siduction.org/index.php?topic=9094.0
Last edited by Colonel Panic (2023-09-07 23:16:36)
Online
The result of the installation on bare metal. ![]()
With 10 work surfaces conky came to its position with the help of 'wmctrl'. Without conky was out of the question!
This time I didn't use sudo, but, siduction's own tool doas, which works wonderfully.
The found power-menu for rofi (I got rid of the icons) works reliably.
@PackRat, if you're reading this, I still haven't found a way to remove obsolete entries (from programs etc. that are no longer installed) from rofi to remove. Do you have any advice ? Thanks!
Edit, and thanks for nsxiv ![]()
Last edited by unklar (2023-09-07 18:07:58)
Offline
@unklar -
Look in the ~/.cache directory. rofi and dmenu write files there. Deleting them clears the rofi/demenu lists. I think that's what your after; otherwise I need some more info and maybe a screenshot.
And doas is originally an OpenBSD tool. Several Linux devs have ported it to their distros (including one of Void's). If it's not available for a given distro, a user can clone a git repo and compile it.
You must unlearn what you have learned.
-- yoda
Offline
If it's not available for a given distro
Doas have been in debian repos since bullseye.
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
The result of the installation on bare metal.
I am also testing dk on bare metal, on my side-kick Lenovo X230. Right now it is running i3 as I have not had time to make audio volume and screen brightness adjustments work.
/Martin
"Problems worthy of attack
prove their worth by hitting back."
Piet Hein
Offline
@unklar -
Look in the ~/.cache directory. rofi and dmenu write files there. Deleting them clears the rofi/demenu lists. I think that's what your after; otherwise I need some more info and maybe a screenshot.
And doas is originally an OpenBSD tool. Several Linux devs have ported it to their distros (including one of Void's). If it's not available for a given distro, a user can clone a git repo and compile it.
OK, I had already read about the cache. The writer recommended not to manipulate it. So I thought there is another way.
Now I did that and I'm happy with the result, @PackRat. Thanks.
Offline
unklar wrote:The result of the installation on bare metal.
I am also testing dk on bare metal, on my side-kick Lenovo X230. Right now it is running i3 as I have not had time to make audio volume and screen brightness adjustments work.
/Martin
i3 is cool ![]()
Offline
Hi hhh,
I don't have a connected 'phone, my problem is not being able to use udisks2 to access my other hard drive partitions from within Siduction. Basically, it times out;
If I'm not mistaken, I had already replied to you once:
In the siduction forum there is no good chance to get an answer on 'error descriptions'.
Offline
Colonel Panic wrote:Hi hhh,
I don't have a connected 'phone, my problem is not being able to use udisks2 to access my other hard drive partitions from within Siduction. Basically, it times out;
If I'm not mistaken, I had already replied to you once:
In the siduction forum there is no good chance to get an answer on 'error descriptions'.
Yes you did, but on a different issue (the desirable or necessary frequency of updates) and it was over a year ago.
https://forums.bunsenlabs.org/viewtopic … 79#p122779
I think it's a good idea to let the Siduction devs know what's going on with their distro even if they don't reply. It could be a Debian Testing or later problem as I've just tested udisks2 in Salix and it works fine, but it also times out in Sparky 8 (another Debian distro, based on Testing).
Last edited by Colonel Panic (2023-09-10 17:41:43)
Online
unklar wrote:Colonel Panic wrote:Hi hhh,
I don't have a connected 'phone, my problem is not being able to use udisks2 to access my other hard drive partitions from within Siduction. Basically, it times out;
If I'm not mistaken, I had already replied to you once:
In the siduction forum there is no good chance to get an answer on 'error descriptions'.Yes you did, but on a different issue (the desirable or necessary frequency of updates) and it was over a year ago.
https://forums.bunsenlabs.org/viewtopic … 79#p122779
I think it's a good idea to let the Siduction devs know what's going on with their distro even if they don't reply. It could be a Debian Testing or later problem as I've just tested udisks2 in Salix and it works fine, but it also times out in Sparky 8 (another Debian distro, based on Testing).
Since you seem to be the only one with this error, the obvious thing to do is to look in your own system?
Well, you could provide terminal output as support for the developers.
e.g. about the partitioning scheme:
lsblk -f -o +PARTUUIDand the fstab.
You could use the journal and show what happens. e.g.
open a terminal and write 'in
journalctl -af leave this open and open another terminal and start this application (file manager), finally, mount the other partition...
For the developer is now interesting, what is in the 1.terminal etc. usf.
Offline