You are not logged in.
... a selection box near the bottom left corner, really hard to see...
Yes, white screen, and found it. Thanks for that. It is invisible until you roll the mouse over it whereupon it shows a thin rectangular outline. Clicking in it brings up a choice between Wayland and X11. Did they intend that only the cognoscenti are aware of the option? Simple Screen Recorder now works, so it must have made a difference
The login manager is sddm.
Having installed Daedalus with KDE, I am finding some stuff does not work, for example Simple Screen Recorder. This is because Daedalus installed with Wayland rather than the X window system (I don't recall being offered a choice) and eg Simple Screen Recorder does not support Wayland (or vice-versa). My package manager Synaptic tells me that x11 is installed, but it seems that Daedalus is not using it. What do I need to do to tell Daedalus to boot using x11 and not Wayland? To comment or uncomment some lines in /etc perhaps?
Googling for help found some discussion on how to do this for Gnome, but it involved some files that do not exist in my Deadalus/KDE installation.
Duke Nukem wrote:I will stop using YT is this goes on.
Statements like that are meaningless. Even if YouTube saw it, they don't care.
It is just a statement of fact, and means no more and no less than that. Yes, I'm sure YT won't care.
In the last couple of days I have had ads showing up at the start of YouTube videos (I use YT quite a lot). By using uBlock Origin on Firefox I have not seen ads for a long time, so I guess YT have recently upped their anti-adblocking game. There are usually two ads and can last up to a minute. In fact I hear the ad but the screen is black so I guess uBlock is half-working.
Anyone else found this? Perhaps there is a uBlock Origin update to counter it? I will stop using YT is this goes on.
I did a fresh install after re-formatting the partition (I could not upgrade from Ascii) and the sources.list is whatever it defaulted to. I first tried to install Chimaera (that was just before Daedalus was released) and found the same problem. Here are the lines with "non-free" in the sources.list that the Daedalus installation gave me :-
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
I have a GeForce GTX460 card which worked under Ascii with driver version 390.116 (as nvidia-detect tells me)
I have now installed Daedalus, apparently successfully, until I try to boot it - when the screen goes blank during the boot messages just after the "populating /dev" message and a couple of lines after it changes font (going into a graphical mode?). The disk drive seems to stop shortly after that. Thinking I could go into a text screen (ie Ctrl-Alt-F1) to try installing drivers from a command prompt like it says on the Nvidia web page https://www.nvidia.co.uk/download/drive … 6226/en-uk, I found that was completely blank too. I guess the boot process had not just vanished from the screen, it had stopped completely. This happens in the advanced recovery boot mode too.
Fortunately I still have Ascii on a different partition (I'm using it now) and that does work with the GTX460. I have also tried an older GeForce GT430 and found that works with both Ascii and Daedalus, and the Nvidia website says both cards use the same drivers (the latest version of which is 390.157).
I would prefer to use the newer and faster GTX460 card (for games). Can anyone tell me what is going on?
My workaround has been to create a bash script with the above full command and save it as ~/bin/gpg_script. That allowed me to create a kde menu entry using that script name without needing the filename, options or pipes. Obviously I ticked the "Run in Terminal" box in the Advanced tab. It is a nuisance that the kde menu seems less powerful than it was before, unless I have missed something.
I have just installed Daedalus which came with kde v5.27.5. The menu editor is not allowing me to add an item such as this :
gpg -d /home/dukenukem/secrets.gpg |less
I was previously using Devuan Ascii with whatever its default kde version was, and it allowed me to specify a complete command line such as the one above. Now however the menu editor splits the command into a "Program" field and a "Command-Line Arguments" field. I have tried putting "gpg" in the "Program" field and the rest in the the "Command-Line Arguments" field, and also tried putting it all in the "Program" field. I have also tried omiting the "|less". But the best I get is a brief flash of a terminal window.
The above command works fine in a terminal. In the "Advanced" tab of the menu editor I have the "Run in Terminal" tab ticked.
Is there a way around this? What was the idea of splitting up the command - an attempt to dumb things down? It is very frustrating if you can no longer put a staightforward bash command into the menu editor.
I can't help you, but I'm posting to confirm I found exactly the same. Not only does it claim I have no internet connection, but it reckons I have nothing installed either - crazy.
I don't even know what Discover is, partly because its developers must have thought it was cool not to enable (at least by default) a menu bar, so I cannot do a Help/About, and I can't be bothered to dig deeper. I'm guessing it is yet another front end for apt, but aptitude works fine for me. On the same subject I notice that Synaptic is not installed by default.
Thanks for that, now solved. Assumptions confirmed BTW.
As I had been using Ascii day-to-day until now (I had only installed Chimaera experimentally) I had not previously encountered the new need to add a dash suffix to the su command to get root's environment settings, and hence get the system apps in the path. I fail to see the point of this change, but still ...
I also needed to enable os-prober in grub (for the benefit of other readers, the file /etc/default/grub), by uncommenting the existing "false" line :
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
GRUB_DISABLE_OS_PROBER=false
Shame that update-grub interpreted my DOS FAT partition as a Windows7 installation, but I guess you can't have everything, and I suppose I could change the name if I edited /boot/grub/grub.cfg, despite the dire warning at the top not to do so.
I updated Chimaera to Daedalus with the "apt-get upgrade" and "apt-get dist-upgrade" commands. I also have an Ascii installation on a different partition on the same HDD, and Windows and DOS on two further different HDDs. With Chimera I had the ability to boot into all those and I want to keep that ability.
For safety during the Daedalus upgrade I unmounted the Ascii partition, my data partitions, and physically disconnected the Windows HDD. I left the DOS HDD connected because it was too hard to reach.
As expected after the installation the Grub menu did not show Ascii or Windows, nor (surprisingly) DOS. So after reconnecting everything and mounting the Ascii partition I tried to run "update-grub" and it said "Command not found". So I tried "apt-get install update-grub" and it said "Unable to locate package update-grub". I'm using root of course. I then tried "grub-mkconfig" with the same result. Yet I can see the man pages of these commands. My sources.list is as recommended by Devuan's upgrade-to-daedalus page.
So is "update-grub" no longer avaiable and if so is there a replacement? According to aptitude I have grub-common, grub-pc, grub-pc-bin and grub2-common installed. How do I get out of this fix other than wiping the Daedalus partition and doing a fresh installation of it?
Kye ( www.kye.me.uk ) A puzzle game with hundreds of levels (+ design your own). There is a Python version for Linux. This website explains it, but for the Python Kye download, follow link from its Links page.
PRBoom ( https://sourceforge.net/projects/prboom/ ) A port of Doom, with a Linux version
Soma ( https://www.somagame.com/ ) Available for Linux, Mac and Windows
In order to deal with exfat file systems, you need to have the exfat-fuse and exfat-utils packages installed.
I had never heard of exfat and Wikipedia says it is a file system for flash drives etc. Surely my hard drives formated under Windows as NTFS would not be exfat? I understood that the "Type" shown eg by cfstab (Type 7 in this case and described as "HPFS/NTFS/exFAT") is purely nominal and is not used functionally by modern Linux - you could call it what type you like and it would make no difference, or so I thought.
Could we see the exact command you tried and the error you got? I mean, from the command line.
OK :-
[root@mesh-devuan:~] # mount -t ntfs-3g /dev/sdb2 /mnt/windows/
ntfs-3g: Failed to access volume '/dev/sdb2': No such file or directory
ntfs-3g 2014.2.15AR.2 integrated FUSE 28 - Third Generation NTFS Driver
Configuration type 7, XATTRS are on, POSIX ACLS are on
Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2014 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson
Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
Options: ro (read-only mount), windows_names, uid=, gid=,
umask=, fmask=, dmask=, streams_interface=.
Please see the details in the manual (type: man ntfs-3g).
Example: ntfs-3g /dev/sda1 /mnt/windows
News, support and information: http://tuxera.com
FWIW I get exactly the same result with mount -t ntfs-3g /dev/sdb2 /mnt/windows/ and ntfs-3g /dev/sdb2 /mnt/windows/
blkid shows info about the other drives but sdb does not appear at all.
This is ASCII and ntfs-3g is installed. It would seem the problem is with non-recognition of the partitions' existence and it does not even get as far as trying to read the file system. I'm wondering if partitions created in Windows have a different indexing or header or something, which is why Linux does not recognise them. It is an older mother board without UEFI.
sdd1 and sdd2 are vfat partitions and they can be mounted with no problem in Linux.
I have four HDDs, one of which is dedicated to Windows and has four primary MBR type partitions. Windows works fine, but although Linux sees the drive as sdb, it does not see the partitions. I first noticed this because trying to mount the Windows partitions under Devuan failed.
[root@mesh-devuan:~] # cat /proc/partitions
major minor #blocks name
8 0 244198584 sda
8 1 51761398 sda1
8 2 51761430 sda2
8 3 51761430 sda3
8 4 88911742 sda4
8 32 976762584 sdc
8 33 156250112 sdc1
8 34 156250112 sdc2
8 35 156250112 sdc3
8 36 156250112 sdc4
8 37 8388608 sdc5
8 38 25165824 sdc6
8 39 318206663 sdc7
8 16 78150744 sdb
8 48 4202415 sdd
8 49 262206 sdd1
8 50 999810 sdd2
8 51 2940367 sdd3
11 0 1048575 sr0
Yet cfdisk does see them :-
Disk: /dev/sdb
Size: 74.5 GiB, 80026361856 bytes, 156301488 sectors
Label: dos, identifier: 0x2de32de2
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sdb2 208845 31423139 31214295 14.9G 7 HPFS/NTFS/exFAT
/dev/sdb3 31423140 110157704 78734565 37.6G 7 HPFS/NTFS/exFAT
/dev/sdb4 110157705 156296384 46138680 22G 7 HPFS/NTFS/exFAT
Free space 156297216 156301487 4272 2.1M
What is going on here? AFAIR I created the sdb partitions under Windows, because in my experience Windows does not see partitions as the correct size if installed into partitions created earlier under Linux.
BTW, the 100Mb sdb1 was created by Windows 7 for some purpose.
I was puzzled by this screen too. For a moment I thought that Devuan had developed its own graphical desktop environment [DE]! But I took it to mean that the top tick box meant whether you wanted a graphical DE or not, and the next five chose which specific type of DE you wanted. So I ticked the top box and also KDE, with the other four DE boxes blank - that worked for me.
It seemed to me that the top box was redundant because if you ticked one of the five specific DEs then of course you wanted a DE. The five specific DE lines might have been indented like subheadings. I don't know what would happen if you ticked one of the five DEs but not the top box :-S
That's how I interpreted it - does anyone kow better?
Shouldn't be a problem, although I've never done it with Win10, only XP and Win7. Windows should be installed first (for a simple life) which you have already done. Now install Devuan, during which it will ask you where you want Devuan installed (at least it does so if you choose the expert installation, as I always have) and obviously you choose the other drive. You will later be asked where you want Grub installed and you can choose the Master Boot Record of the first drive. Grub will detect that there is also Windows available and will add it to the boot menu alongside Devuan.
The Pale Moon browser is not in the Devuan repositories, although it is in the Debian ones (I could try it from there). Is this an oversight? There does not seem much choice of browsers these days with Chrome almost taking over the world (even Microsoft have now switched to it), although Safari survives for Apple users. People are predicting the death of Firefox, but I've seen good reports of Pale Moon which forked from it.
Does anyone know how to change the console background colour in an SSH session?
I have Konsole set (via its Menu Bar "Settings"->"Edit Current Profile") to white text on black, but any changes apply to all sessions, not just the local one. I would like a background (eg dark grey) in SSH sessions that is different from that of other PCs on the network, so I can see at a glance which one I am using. Fiddling around with the PS1 variable in .bashrc in the remote PC I have only succeded in changing the background colour under the text itself, not the whole background.
All are [Ok] and [info] messages. No one in red color.
But isn't it nice to see that it is all OK? I like to see the boot messages, and not have them papered over with wallpaper. I only ever shut down and reboot once every three months on average so I don't much care what booting looks like anyway. Sorry to be of little help.
@ fsmithred : Thanks for that, I get it now.
- not free: these are redistributable packages but not free according to the Debian Free Software Guidelines (DFSG).
- contrib: is free software compatible with the DFSG, but depends on some packages that are not free.
- main: it is the standard repository of devuan and all the software included here includes free software according with the DFSG.
Thanks for that, I now understand the definitions. But with that, and with searching other threads, I still have a simple practical question : is the stuff in the "main" repositories included as a subset in the "non-free" repositories, or does the "non-free" repository contain only "non-free" stuff?
Or putting it another way, if I want free and non-free stuff, should I have both "main" and "non-free" repositories in my sources.list or is just "non-free" enough?
Or putting it third way, does the line :-
deb http://gb.deb.devuan.org/merged ascii main non-free contrib
.... refer to three different repositories ("main" "non-free" and "contrib") that are all included by that statement? Or is it refering to a single block of stuff that contains it all, and there is a separate block, invoked by :-
deb http://deb.devuan.org/merged ascii main
.... that contains free stuff and only free stuff?
Sorry, I was not intending to start an ideological discussion here :-S
I have just installed ASCII and I don't recognise some of the reviewer's complaints.
I chose the expert non-graphical install from DVD, and it went smoothly except it said I had an EFI motherboard and I should put GRUB on a USB stick. However I don't have an EFI motherboard so I ignored it, with no repercussions.
I used Debian before I used Devuan, and it seemed to me that the installation procedures were practically identical : has this guy never installed Debian? I once did a net install of Debian and it did take hours (literally, waiting for packages to be downloaded) and would never try that again, Debian or Devuan.
He was installing on a VM, so he had graphics problems. I have rarely managed to install anything on a VM without graphics problems and I usually just give up and have to accept a shrunken a 800x600 (or whatever) subscreen.
I was not asked to set up partitions manually; the option was only offered (and I took it). It also offered to make partition decisions itself, even in this "custom" installation - I don't know what it would do with that option.
He seemed to find the account set-up stage confusing. I was simply asked to set up a root account and then a user account. I never like the sudo method of doing admin (AFAIR Ubuntu insists on it). I find when I need to do admin tasks that I am doing them for a little while, so I don't want to have to keep adding "sudo" in front of every command.