You are not logged in.
What happened when you removed blueman from the autostart apps? Did that help? If not, did installing rfkill make the message go away?
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.
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.
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?
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'.
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.
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.
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.
What boxes did you check/uncheck at the tasksel window, and did you install with or without a network mirror?
I don't have any ideas on what you should do to fix it, but I found the following by poking around in the sysvinit-core source. This can be found in /lib/init/rc.
if ! test -e /proc/stat; then
# startpar requires /proc/stat
if [ "$(uname)" = "GNU/kFreeBSD" ] ; then
mount -t linprocfs linprocfs /proc
elif [ "$(uname)" = "GNU" ] ; then
mount -t proc none /proc -ocompatible
fi
fiMaybe use this or figure out how it does what it does:
# Skip fsck on reboot.
shutdown -f Here is my procedure for a debootstrap install. See 'man debootstrap' for other options.
chroot-dir is the directory where you want to do the debootstrap install. If you mount a separate volume for that, then chroot-dir is the mountpoint. Call it whatever you want.
debootstrap --arch amd64 chimaera chroot-dir http://deb.devuan.org/merged
# Copy files to the new system. Example:
cp /boot/grub/splash.png chroot-dir/boot/grub/Mount some things and chroot into the new system to make additions and changes.
mount --bind /proc chroot-dir/proc
mount --bind /sys chroot-dir/sys
mount --bind /dev chroot-dir/dev
mount --bind /dev/pts chroot-dir/dev/pts
chroot /chroot-dirInstall kernel and other packages
Install grub or other bootloader (run grub-install and update-grub)
Edit configs
Create root password
Create user
Leave the chroot:
exitUnmount stuff:
umount -l chroot-dir/dev/pts
umount -l chroot-dir/dev/
umount -l chroot-dir/sys
umount -l chroot-dir/proc
# And if it's a separate volume:
umount -l chroot-dirThe source of the problem is in desktop-base, and I pushed the fix to git. Removing desktop-base also brings back the menu icons.
Before I issue a build, I'd like to know if anyone notices anything else weird with the desktop that is related to theming or that gets corrected with removing desktop-base or the deepsea window and icon themes themes.
Sorry, I got distracted and forgot about this one. I didn't see anything odd with the usual suspects (policykit, et. al.) but I also don't know exactly where the break is between when stuff worked and when it didn't. I'm also not familiar with some of the apt options you used, so I don't know if that caused anything weird to happen.
@LinuC:
If this is your usual response to criticism, you may have accumulated a number of enemies over time. Please stop the baseless accusations against devuan.
Network setup in xfce is now handled by network-manager. If you want to use /etc/network/interfaces, you should disable or remove network-manager, or they will fight with each other.
I haven't tried the latest installers with a wireless connection yet, but with earlier ones, I had trouble if the wireless password had special characters in it. If I changed it to all lower case, the password worked in the installer. Special characters work correctly in the installed system.
I'm using the connman runit scripts from the antix collection, and connman seems to be working correctly. I have installed connman, connman-gtk, connman-ui and connman-vpn. The command connman-ui-gtk is in my startup apps. (xfce here)
I've seen a few cases where Video DownloadHelper in firefox shows me the video file in several formats, but only one of the files will play both video and audio.
Thanks, guys. I added the .png files to include-binaries instead of putting them in the patch. Just the .xpm is in the patch. Looks like it all works and builds now.
I'm trying to make a quilt patch to correct (replace) a couple of files in clearlooks-phenix-cinnabar-theme, following this guide: https://wiki.debian.org/UsingQuilt
I've used that guide successfully on the deepsea theme, but this patch is failing. Here's my command history with relevant output:
### Clone the repo and checkout the working branch
git clone git@git.devuan.org:devuan/clearlooks-phenix-cinnabar-theme.git
cd clearlooks-phenix-cinnabar-theme/
git checkout suites/unstable
### apply existing patches (there's one active in the series file)
$ quilt push -a
Applying patch color-change
patching file gtk-2.0/gtkrc
Now at patch color-change
### Create new patch
$ quilt new top-left-active-fix
Patch top-left-active-fix is now on top
### Start making the changes
$ quilt add xfwm4/top-left-active.xpm
File xfwm4/top-left-active.xpm added to patch top-left-active-fix
$ cp ../top-left-active.xpm xfwm4/
$ quilt refresh
Refreshed patch top-left-active-fix
$ quilt add xfwm4/top-left-active.png
File xfwm4/top-left-active.png added to patch top-left-active-fix
$ cp ../top-left-active.png xfwm4/
$ quilt refresh
Diff failed on file 'xfwm4/top-left-active.png', aborting
$ quilt add xfwm4/png/top-left-active.png
File xfwm4/png/top-left-active.png added to patch top-left-active-fix
$ cp ../top-left-active.png xfwm4/png/
$ quilt refresh
Diff failed on file 'xfwm4/png/top-left-active.png', aborting
### Get rid of the failed patch and remove all the applied patches.
quilt delete top-left-active-fix
quilt pop -aThe .xpm file is a text file, and that works. The .png is a binary file, and I don't know if there's a different way to handle that. Other than that, I have no ideas about what's wrong. Suggestions are welcome.
Here's a link to the unstable branch, for reference: https://git.devuan.org/devuan/clearlook … s/unstable
sudo apt update && sudo apt install -f && sudo apt upgradeToday that got me kernel 4.19.0-17 + an odd message about a potential 28 further upgrades. Re-running the commands now produces zero result. I'm still on beowulf-3.
If those commands completed without error, then it's correct that there are no more upgrades, because you already got them, and your beowulf is fully updated and current. You can check to see what got upgraded or installed by looking in /var/log/apt/history.log.
@andyprough:
How do you run linux on a computer with only 64k RAM???
In my fully updated beowulf without apparmor, man is working fine.
I notice you're using an older kernel. It's probably not related to the problem, but current kernel package in beowulf is 4.19.0-17.
There's no security repo for the Testing branch. As long as Chimaera is in testing, any security updates will filter down from Ceres, our unstable branch. Unstable means the versions can change quickly.
It takes a week for a version to move from Unstable to Testing. If you want to selectively get updates sooner than that, you can add a line for ceres to your sources.list and pin ceres to a lower priority, so that you can pick and choose what to take.
I'm not sure what will happen when Debian Bullseye goes stable. We might start tracking the security updates at that time.
Re-check your power manager settings as Camtaf suggested.
Look in /var/log/apt/history.log to see what packages you removed. (Let us see, too.)
FWIW, I tried your settings and theme choices, and it had no effect on shutdown. I'm guessing you removed something that you need.
What do "fixed" and "not affected" mean? I expect "not affected" to mean "doesn't need to be fixed" rather than "we fixed it".
Here's a little more explanation about what Camtaf posted -
If you install one of the kernel metapackages, you will always get the latest kernel on upgrade. Those packages are named like linux-image-amd64 or other linux-image-<arch>. Metapackages don't do anything themselves except automatically pull in other packages.
Without the metapackage, you need to manually install newer kernels when they come along. The actual kernel packages have the version in the package name, like linux-image-4.19.0-16-amd64 for instance.