You are not logged in.
- Topics: Active | Unanswered
#826 Desktop and Multimedia » Wicd in Chimaera (It's not, but...) » 2021-08-22 17:56:27
- fsmithred
- Replies: 12
Wicd is no longer maintained and is not in chimaera or ceres repos. However, someone in IRC yesterday mentioned that wicd did not get removed when they upgraded from beowulf to chimaera. So I decided to try it.
On my laptop running chimaera with xfce, I removed connman, added a single line for beowulf main repo, ran 'apt update' and then 'apt -t beowulf install wicd-gtk'. Below is posted a copy of my apt history.log showing what else got pulled in. (Disclaimer: I have not checked versions of any those packages to see which repo they came from.)
I tested wired and wireless connections, and wicd seems to be working normally. I commented out the beowulf line and ran 'apt update' again when I was done.
Start-Date: 2021-08-21 18:57:13
Commandline: apt -t beowulf install wicd-gtk
Install: python-gtk2:amd64 (2.24.0-5.1+b1, automatic), wicd-gtk:amd64 (1.7.4+tb2-6+devuan1.1), python-is-python2:amd64 (2.7.18-9, automatic), python2-minimal:amd64 (2.7.16-1, automatic), python2:amd64 (2.7.16-1, automatic), libglade2-0:amd64 (1:2.6.4-2+b1, automatic), libpython2-stdlib:amd64 (2.7.16-1, automatic), python-dbus:amd64 (1.2.8-3, automatic), python-pkg-resources:amd64 (40.8.0-1, automatic), python-glade2:amd64 (2.24.0-5.1+b1, automatic), python-cairo:amd64 (1.16.2-1+b1, automatic), python-numpy:amd64 (1:1.16.2-1, automatic), wicd-daemon:amd64 (1.7.4+tb2-6+devuan1.1, automatic), python-gobject-2:amd64 (2.28.6-13+b1, automatic), python-wicd:amd64 (1.7.4+tb2-6+devuan1.1, automatic)
End-Date: 2021-08-21 18:57:28Edit: OK, I checked two packages. python-gtk2 and python-dbus are from beowulf. I don't yet know if I broke anything that depends on python3.
#827 Re: Hardware & System Configuration » Questions Regarding Beowulf Netinstall » 2021-08-22 17:20:40
KDE and lxqt are choices in the tasksel menu. If you have a network connection during installation, you can install them. The statement about CD and DVD only apply to off-line installs.
Ignore that first question about missing firmware. There's wireless firmware in the iso, and it will be installed if you need it. If you don't want non-free firmware, choose Expert install to get some extra questions about that.
#828 Re: Devuan » Missing init scripts » 2021-08-22 01:30:03
This package is in debian and devuan:
orphan-sysvinit-scripts
apt-file list orphan-sysvinit-scripts
orphan-sysvinit-scripts: /usr/lib/orphan-sysvinit-scripts/mapping
orphan-sysvinit-scripts: /usr/lib/orphan-sysvinit-scripts/update_init_d.sh
orphan-sysvinit-scripts: /usr/share/doc/orphan-sysvinit-scripts/README.Debian
orphan-sysvinit-scripts: /usr/share/doc/orphan-sysvinit-scripts/changelog.gz
orphan-sysvinit-scripts: /usr/share/doc/orphan-sysvinit-scripts/copyright
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/dirsrv
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/dirsrv.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/dnscrypt-proxy
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/dnscrypt-proxy.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/gpsd
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/gpsd.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/iwd
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/iwd.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/network-manager
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/network-manager.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/nftables
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/nftables.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/tomcat9
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/tomcat9.md5sum#829 Re: News & Announcements » Migrating from Bullseye to Chimaera - feedback needed » 2021-08-19 16:29:59
Nixer, big thanks for the report.
libreoffice should have been taken off the autoremove list along with other things when you installed task-xfce-desktop. You're sure it's still there and didn't get removed again behind your back?
#830 Re: Other Issues » Can I share a "data" LVM logical volume in a multi-boot linux setup? » 2021-08-19 14:24:45
The commands I posted for you are from the release notes of refracta gnu/linux. I wrote that part about 10 years ago, and I've used it multiple times over the years. It really is just like mounting any other data partition.
On the other hand, if you try to share system files between two different systems, you'll probably run into some interesting problems we've never seen before. But that would happen with or without lvm.
#831 Re: Other Issues » Missing LSB tags under Chimaera » 2021-08-18 18:58:23
I don't know if it's related, but I had 'Debian' in my boot menu until I installed lsb-release so that the lsb_release command in /etc/default/grub worked, and I then got 'Devuan' in the boot menu.
#832 Re: Other Issues » Can I share a "data" LVM logical volume in a multi-boot linux setup? » 2021-08-18 01:46:30
I've booted a live-usb and mounted lvm many times. it's just like mounting any other block device, with a few extra commands. Once it's attached to the filesystem, you can read and write files as you normally would.
I've also mounted lvm from another installation on a different hard drive in the same computer. It works the same way.
A few extra commands. (Leave out the cryptsetup lines if your lvm is not encrypted.)
___ MOUNT/UNMOUNT ENCRYPTED LVM ___
sudo cryptsetup luksOpen /dev/sdxY label # then run lvdisplay to get the vg name and lv name
sudo vgchange -a y <volume_group_name>
mount /dev/mapper/<vg_name-lv_name> <mountpoint>
umount <mountpoint>
sudo vgchange -a n <volume_group_name>
sudo cryptsetup luksClose label#833 Re: Other Issues » Can I share a "data" LVM logical volume in a multi-boot linux setup? » 2021-08-17 18:50:08
The host system does not need to be lvm to mount the data lvm. You just need lvm2 to be installed, and you can open the volume and mount it with a few commands.
A howto on keeping the configs separate on a shared home would probably be useful for a lot of people.
#834 Re: Installation » how to install on big memory card (128 or 256 GB) with grub and » 2021-08-17 16:49:55
Install to the card like it's another hard drive. Make sure the bootloader gets installed to the mbr of that drive. If you want it to be uefi compatible, you will have to do some different things.
Once the installation is done and you know you can boot into it, copy the live-iso into that system and create a grub menu entry to boot the .iso file directly. See these:
https://dev1galaxy.org/viewtopic.php?id=2334
https://dev1galaxy.org/viewtopic.php?pid=6176#p6176
#835 Re: Installation » how to build myself a absolutely minimal Live ISO » 2021-08-17 16:27:25
Yeah, we hang out in the Devuan Derivatives section.
https://dev1galaxy.org/viewforum.php?id=9
#836 Re: Installation » pls help me to find a way to move the minimal live CD to the HD » 2021-08-17 16:21:07
The only reason the live isos are named 'alpha' right now is because they were the first set that I uploaded. You can consider them to be betas. I will probably make new live isos in a week or two.
#837 News & Announcements » Migrating from Bullseye to Chimaera - feedback needed » 2021-08-16 14:19:34
- fsmithred
- Replies: 10
I installed Debian Bullseye from a debian-live xfce iso in a qemu VM and then proceeded to migrate to Devuan Chimaera.
CAVEAT - These are NOTES. They are NOT instructions. With a few more data points (supplied by you) we can hammer out some real instructions. (Hint: the yellow-highlighted commands might end up being the instructions.)
FIRST ATTEMPT
Failed. I tried to use nixer's method for buster to beowulf migration. Briefly, that involves doing the full migration to devuan with systemd still installed and running, and then rebooting into devuan with sysvinit at the end. See https://dev1galaxy.org/viewtopic.php?id=3044
This failed because it wanted to remove systemd while it was running. I also had a problem with apt wanting to remove the running kernel (5.10.0-7) because there's a newer one. I didn't bother to upgrade the debian system before the migration, but still, this is the first time I've ever seen an upgrade try to replace the running kernel. In the past, any dist-upgrades I did were happy to keep using the older kernel, even after the reboot.
SECOND ATTEMPT
Switched back to debian sources and apt-update failed, saying that bullseye-security doesn't have an InRelease file. I didn't get that error earlier, so it was probably a network glitch. I got around it by only enabling the one main repo line for bullseye.
Ran apt -f install as advised by apt.
apt install sysvinit-core
apt install linux-image-amd64 (which got removed earlier)
rebooted to sysvinit and linux-image-5.10.0-8 (still in debian)
Re-edited sources.list to chimaera
apt update (had to run dhclient to get network back)
apt dist-upgrade (no errors!)
reboot (still had a large autoremove list, including Atril)
-----------------------------------------------------
This section should only be needed after installing from debian-live,
but you may still need to reinstall task-xfce-desktop
Got to console login on reboot. Lightdm was removed but slim was not installed.
task-desktop and task-<language>-desktop are installed, but not task-xfce-desktop.
To remove all the language packs, apt remove task-* (This is only needed after installing from debian-live.)
then
apt install task-desktop task-xfce-desktop (this brinds in slim, synaptic, network-manager)
apt autoremove
reboot
OK! No network connection and boot menu still says Debian.
-----------------------------------------------------
I messed with network-manager and /etc/network/interfaces.d/setup in every way I could think of, and I still can't get a network connection.
Rebooted a live-iso with the virtual disk attached.
In chroot:
installed lsb-release and ran update-grub. That changed the boot menu to say Devuan.
also installed dnsutils thinking that might help.
After reboot, I still couldn't ping by name or number (even as root) but I tried a web browser, and I do have network.
#838 Re: Installation » My chimaera install issues #2: Can't abort LXQt WM choice » 2021-07-31 16:39:34
Here's a screenshot of the window in question.
https://transfer.sh/rg1/Screenshot_lxqt-first.png
The default window manager for lxqt is currently xfwm. Muffin is there because cinnamon was also installed. This window comes up on the first login to lxqt. I don't recall seeing it in a system that had only lxqt installed. In that case, I assume there was only one window manager installed, so there was no need to ask.
The only way "back" would be to kill the desktop that's in the middle of loading itself and restart the display manager to log into one of the other desktops. It's probably easier and safer to just press ENTER, let it load, and then log out. As it says on the screen, the choice can be changed later.
#839 Re: Installation » My chimaera install issues #10: We will take Jerusalem! » 2021-07-29 14:41:24
Can anyone reproduce this? I just tried and failed. I chose English, American English, and Israel for language, keyboard and timezone. On reboot, 'date' tells me that it's 17:36 IDT. By my count, it's 14:36 UTC. Looks like it works the way it's supposed to work.
#840 Re: Installation » My chimaera install issues #9: meld'ing as root gives errors » 2021-07-25 12:04:50
It might be a mismatch between versions of meld and gtk3. That's not a surprise, because gtk3 devs are notorious for changing APIs with every minor version, repeatedly causing problems for app developers.
Searching for one of the error messages, I found this:
https://gitlab.gnome.org/GNOME/meld/-/issues/224
If meld is working, I would ignore the error messages.
BTW, I can get the same "Error creating proxy..." message running meld as root from terminal in debian with cinnamon desktop.
Try xinomilo's suggestions. There's also probably a way to do it with pkexec, but I don't know how to do that.
#841 Re: Installation » My chimaera install issues #9: meld'ing as root gives errors » 2021-07-24 11:50:18
I think it's a gtk3 issue, not necessarily meld. See if changing the desktop theme makes a difference. Since it mentions the scrollbar, maybe try installing or uninstalling gtk3-nooverlayscrollbar or gtk3-nocsd.
#842 Re: Installation » My chimaera install issues #2: Can't abort LXQt WM choice » 2021-07-24 11:47:34
#843 Re: Installation » My Chimaera install issues #1: Forced manual choice of LXQt WM » 2021-07-24 11:45:31
LXQt was probably the last desktop to be installed
But there is no user-acknowledged notion of a "last desktop environment to be installed".
so the alternatives system set it as the default, thus replacing any previous default settings. That's normal behavior of the alternatives system.
But is this the intended Debian/Devuan policy? That is, Devuan defaults to xfce4. If one installs xfce4 + something else, should Devuan default to not-xfce4? And not just that, but have a priority order of defaults based on the order of package installation? Surely that's not right.
The user does not get to control the order of package installation during the install of the operating system. That's up to the package manager, which has to resolve dependencies of the chosen metapackages. The behavior of the alternatives system will make more sense when you read the man page for update-alternatives.
And again - even suppose it's legitimate to set LXQt as the default desktop environment. Then, surely a default window manager should be set and used, rather than the user faced with a forced selection dialog.
In fact, a default window manager was selected for you. The lxqt devs thought they should double-check with you, because you had more than one window manager installed. They presented you with a list, and on that list the pre-selected window manager was highlighted. All you had to do was press enter or click OK. If you think that behavior should change, you could file a bug report. I'm guessing that behavior comes from the lxqt authors, upstream of debian.
#844 Re: Installation » My chimaera install issues #4: root credentials demanded after login » 2021-07-23 12:58:08
What happened when you removed blueman from the autostart apps? Did that help? If not, did installing rfkill make the message go away?
#845 Re: Installation » My Chimaera install issues #1: Forced manual choice of LXQt WM » 2021-07-23 12:48:38
fsmithred wrote:The current chimaera installer isos (and live isos) are alpha level. They should work essentially the same as previous installer isos. That they don't is no surprise. The default desktop is supposed to be xfce, and if you select something else, you should get what you select.
I didn't select LXQt as my default desktop environment; although I did select multiple desktop environment for installation.
Plus, even if I had selected it to be the default during installation - there should still be an automatic selection of window manager for the user on their first login. Either that, or the installation should mandate making that selection beforehand.
LXQt was probably the last desktop to be installed, so the alternatives system set it as the default, thus replacing any previous default settings. That's normal behavior of the alternatives system. You can change the default desktop by running update-alternatives --config x-session-manager and if needed, you can change the default window manager with update-alternatives --config x-window-manager
If you only install one desktop environment, you get that desktop's default window manager automatically. If you have multiple window managers installed, the desktop software has the logic coded into it to ask you if the additional window manager is there because you want to use it.
Installiing multiple desktop environments used to be a simple matter. But that doesn't seem to be the case now. It would work better if they were installed one at a time, so any conflicts might be more apparent.
Look in /var/log/installer/syslog for task-xfce-desktop task-cinnamon-desktop and task-lxqt-desktop to see which were checked at the tasksel window in the installer.
#846 Re: Installation » My chimaera install issues #9: meld'ing as root gives errors » 2021-07-23 11:31:51
I don't know about the gtk errors. I see them frequently when I start graphical apps from a terminal, and I have been mostly ignoring them for years.
#847 Re: Installation » My chimaera install issues #11: Everything is a plain text document? » 2021-07-23 11:29:38
I got no icons on the desktop in my cinnamon install. If I go into preferences and set the desktop to show those items, their names show correctly.
Look inside those text files to see what's there. If they are actual .desktop files, they should look similar to the files in /usr/share/applications. Are they functional when you click on them?
#848 Re: Installation » My chimaera install issues #9: meld'ing as root gives errors » 2021-07-23 11:16:56
See the release notes for devuan beowulf or debian buster to read about changes in the behavior of su and how to revert it. It's also in 'man su'.
#849 Re: Installation » My chimaera install issues #3: Misleading LXQt WM choice » 2021-07-22 23:27:27
It sounds like lxqt is coded in such a way that it will use just about any window manager. It can recognize a few if they are installed, and ask you which one to use. I recall that lxde lets you easily change the window manager, and I recall long ago being given a choice of wm in gnome 2.x (sawtooth or metacity?).
This is a good thing. It means the software was written to be interoperable with lots of different things. In such cases, the user can usually ignore the choices and just press enter to get a sane default.
#850 Re: Installation » My chimaera install issues #2: Can't abort LXQt WM choice » 2021-07-21 22:06:41
I'm guessing there's more than one desktop environment installed, so the system wants to know which one you prefer. We need to know what you chose and what actually got installed. Then we can untangle the dependencies.
Board footer
