You are not logged in.
Well recently downgraded from Devuan 4 to 3.1.1 and sound coming out of all speakers, so problem solved! (And I removed Pulse in Synaptic - pure ALSA - the best!)
My current desktop after downgrading to 3.1.1 from 4 where I could not get 2nd Monitor to be picked up!
Solved the problem as my Devuan 4 was running out of space on root, so downgraded to Devuan 3.1.1 - back to normal!
My posting related to what shows in Discover | Settings, which is what I posted, not the sources list which does indeed give the full addresses as in your post. Perhaps I should have stated that in the first place. Thanks for your replies everyone.
Tried installing Devuan 4.0 "chimaera" with accessibility option ticked - great job Devs on this - I also note that this was available in 3.1.1 "beowulf".
Can't comment on Discover and KDE, not my DE.
But what hits my eyes is that for Chimaera you just have enabled main. And for the others also contrib nonfree. Does not make sense. Either all in or all out.
rolfie
That is all that is available to me - should I keep the 'sources' in? Guess it's because I have come from a different GNU/Linux prior to Devuan.
Thanks for your time and input.
Hi Head_on_a_Stick, It's been a while but I have never had a response to the bug I reported, no email, de nada.
No longer an issue as now using Devuan 4.0
Discover just isn't working at all. When I enter the root password to edit the settings it falls over (cannot access settings). If I select 'Ignore' it states I should start Discover with the command:
kdesudo
which results in no such command.
Have repositories changed?
Currently I have:
Chimaera (main)
Chimaera security (main contrib non-free)
Chimaera updates (main contrib non-free)
I have unchecked the 'Sources'
My current Devuan 4.0 Plasma Desktop:
D'OH! I was looking at folders instead of files!
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
# The default runlevel.
id:2:initdefault:
# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS
# What to do in single-user mode.
~~:S:wait:/sbin/sulogin --force
# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin --force
# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."
# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty --noclear 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
#
# or on a USB serial line
#U0:23:respawn:/sbin/getty -L ttyUSB0 9600 vt100
# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
# Example for systemd-nspawn
# Only /dev/console exists inside nspawn, so we need a getty on that.
# Also make sure to comment out the gettys on tty* above.
#C0:2345:respawn:/sbin/getty -8 --noclear --keep-baud console 115200,38400,9600
Hi Head_on_a_Stick, Many thanks for your investigations on this. I don't have inittab in /etc, only init.d and initramfs-tools. Will report bug as suggested.
I always choose GDM.
# chvt 4
Same result as Fn keys 1 through 6 - flashing line and no tty login. Thanks.
Sorry for the off-topic - will post elsewhere.
Adding to xorg.conf is a red herring, imo – there's no issue with the keyboard layout in X, or after X has started, e.g., unlocking the screensaver.
swarfendor437 wrote:After logging in and press key combination of Ctrl+ Alt+ F1 I don't get a console but back to login screen after a brief black screen with my login details.
That is not normal. What about with the other virtual consoles (Ctrl-Alt-F2 to -F6)? It this a standard desktop keyboard or a laptop with other functions on the Fn keys? Do you have proprietary (i.e., nVidia) graphics?
swarfendor437 wrote:... there was reference to a
... dirty bit ...
Dirty filesystem, usually caused by abruptly switching off instead of shutting down gracefully. Should be fixable by fsck, but the partition must be unmounted to do that.
Edit: typo.
This is a desktop pc that previously had Devuan 3.0 then I 'upgraded' or rather installed Devuan 3.1.1 after the drive Devuan 3.0 was on started to die. Tried to do an upgrade to 4.0 from 3.1.1 but that went disastrously wrong. On this install I have chosen the following layouts:
1. Devuan default (LXQt)
2. Gnome flashback
3. LXQt
4. KDE (Plasma) - this is the DE I use each day.
The keyboard is a Cherry DW 9000 SLIM keyboard with mouse - both wireless. No keyboard or password issues in Devuan 3.0 or 3.1.1. - will get back to you regarding other Fn keys.
Update - Fn 2 through Fn 6 just displays a flashing underscore on a black screen, no tty login - reinstall?
I've never liked nVidia proprietary drivers as they always gave me a poor experience, especially in Firefox, but now that Firefox no longer supports ALSA I won't be using it in future and will be removing Firefox ESR and replace with epiphany and possibly FlashPeak Slimjet browser as alternatives.
Any reason why you're not sharing the actual file? I would think that would be easier than posting a vague description.
Anyway, here's what systemd created in my Arch box:
archie:~$ cat /etc/X11/xorg.conf.d/00-keyboard.conf # Written by systemd-localed(8), read by systemd-localed and Xorg. It's # probably wise not to edit this file manually. Use localectl(1) to # instruct systemd-localed to update it. Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "gb" EndSection archie:~$
Try that.
EDIT: the name of the file isn't really important. It needs to end in .conf and the files are read in lexicographical order but you shouldn't have any conflicts anyway.
Here is the entries from the file:
Section "InputClass"
Identifier "keyboard"
MatchIsKeyboard "yes"
Option "XkbLayout" "gb"
Option "XKbVariant" "nodeadkeys"
EndSection
That's strange, I was sure I put 40 in there somewhere. I named the file 40-keyboard.conf and it is located in /etc/X11/xorg.conf.d
swarfendor437 wrote:changed 20 to 40
I have no idea what this means.
Please share the exact, full contents of the configuration file along with it's precise location and also share the full X.Org & display manager (LightDM?) logs. Remember to use code tags when posting terminal output and perhaps consider using a pastebin and sharing a link here if the logs are large. Thanks.
I followed your link to that article - there was no config file - there was just the xorg.conf.d folder with nothing in it.
I copied the entry you gave a link to [https://bbs.archlinux.org/viewtopic.php?id=245451].
In that file there was reference to "20" - when using older versions of GNU/Linux I remembered that en-gb used to be listed as number "40" which is why I changed the number from that original post and replaced "de" in that post with "gb". Should it have been "en-gb"?
swarfendor437 wrote:... if I leave the machine for some time and it logs me out, I can enter my password with the hash key - but not at login!
Before you log in, your user preferences are not known. Try this:
After logging in, change to a console (e.g., Ctrl-Alt-F1) and log in as root – you'll probably have to use Shift-3 for the # symbol. Having logged in, run dpkg-reconfigure keyboard-configuration again. This shouldn't be necessary, but ... just to be sure.
Now run setupcon to have the your default keyboard settings applied to the console. After that, you should get a # on the console when you press that key; Shift-3 should give you £. Now try rebooting and see what you get at the login screen.
Incidentally, I agree with what's been said – pc105 and gb for a standard UK keyboard.
After logging in and press key combination of Ctrl+ Alt+ F1 I don't get a console but back to login screen after a brief black screen with my login details.
Just also to mention that after a recent login I briefly saw during the scrolling consol on populating devs etc there was reference to a
... dirty bit ...
Is this indication of a hard drive error? I only replaced the last failing drive this March with a WD Gold which is supposed to be built for machines to be on 24/7. it sounds like a Hitachi 'DeathStar' (deskstar) drive at times.
In Devuan 3.0 I did not have an issue, but in 3.1.1, 4.0 and other recent OS's I have the following issue. I have a soundblaster Audigy Rx 5.1 surround sound card connected to a Logitech 5.1 Surround sound system.
Front Left, Middle (2 mini speakers for centre), Front Right, Rear Left and Rear Right, and subwoofer.
Centre is coming out of left speaker, Front left channel is coming out of centre, Front Right is coming out of subwoofer, subwoofer is coming out of front right. Only Rear left and rear right speakers are correct. Any others had similar experiences?
I enter the root password which works for Synaptic and su in terminal but states authentication failure when I want to uncheck KDE Wallet in Plasma DE.
In Devuan 3.0 and 3.1.1 (installed after hard drive failure with 3.0) had no issues with both monitors attached to Nvidiat GT1030 powered card. But with Devuan 4.0 have no luck. Have installed 'arandr' and 'autorarandr' to no avail.
Tried that - changed 20 to 40 and made the Xkblayout to "gb" - still no joy. Made a mistake in last post, instead of '#' when I press the # key it shows '\' and not '/'
OK, I boot into Devuan and arrive at the Login page. I select my user. I enter my user password setup during install which has the hash sign within it. The hash sign is also present in my root user password. Ironically, if I leave the machine for some time and it logs me out, I can enter my password with the hash key - but not at login! If I use the hash key in root user password when using Synaptic Package Manager, no issue, and no issue when using root password that has a hash key when using 'su' in the terminal. It is just at initial login! If I uncheck the hide password, if I press the hash key [#] on the keyboard I get '/' - I have to use Shift plus 3 to get '#'
pc105 should be fine, that's what I have in /etc/default/keyboard.
Are you experiencing this problem in both the console (TTY) and graphical desktops?
EDIT: does this fix things in the graphical environment:
setxkbmap gb
I can use the # key as normal as i have it in Root password in GUI (Synaptic Package Manager authorizaton box) and when using su - just user login.
Tried the last command you gave me, rebooted and still the same.
Oops! What a lazy boy I am!
OK, changed to what the installer pointed to, 101-pc as I noticed 105-pc had (Intl.) [International] and guessed this was the issue. Made changes, rebooted but still have to use Shift+ 3 to get '#'.