elav wrote:I can not install KDE Neon, neither with the last ISO, nor with the previous ISO on my Desktop PC. I have on that PC currently installed ArchLinux + Windows 10 without problems, but when I try to install KDE Neon I get this error in the partitioning of disks:

https://imgur.com/wvI1MZr

Hmm. That doesn't seem to be a problem with the Neon isos specifically, but rather a previously unnoticed and uncorrected problem with your fat32 partition that the installer has turned up. Good installers tend to be conservative with respect to storage device problems because it's better to fail the install than to irreversibly trash someone's storage media.

You should run a check on that partition while booted into Arch, correct any errors, then try the Neon install again once it's reported as error free. Do a backup first if it's important, though I'm not sure what crucial data exists on a 512.0 Mb partition. It will be a quick backup at least.

Eg.

Code: Select all

$> sudo umount /dev/sda2
$> sudo fsck /dev/sda2


I suspect that once you fix the errors reported by fsck, you'll be able to run the Neon installer without further problems (related to partition errors, anyhow).

Wouldn't the 512 mb partition be the default Windows Master Boot Record partition? If so it would be about the only reason for a "mystery" FAT32 partition to exist. Seems logical looking at the image posted of the installer. Windows creates the MBR in a separate partition at install and does so in FAT32 format so it is "readable". The system itself lives within an NTFS formatted partition.

It may be some sort of Windows related utility partition, but it isn't the MBR.

c0d3g33k wrote:It may be some sort of Windows related utility partition, but it isn't the MBR.

Sorry for not being very familiar with Windows 10 but I did ask someone who is and they explained it could be the MSR partition. Not being familiar with MSR i found this info: https://en.wikipedia.org/wiki/Microsoft_Reserved_Partition

kdeoldster wrote:

c0d3g33k wrote:It may be some sort of Windows related utility partition, but it isn't the MBR.

Sorry for not being very familiar with Windows 10 but I did ask someone who is and they explained it could be the MSR partition. Not being familiar with MSR i found this info: https://en.wikipedia.org/wiki/Microsoft_Reserved_Partition

Heh. One letter makes all the difference. It doesn't matter what that partition is, really. The installer is reporting this partition has errors and alerting the user. As it should.

So the next logical step is to use a disk check utility to identify whether there are any errors, and correct them if present. It could be as simple as the partition was not cleanly unmounted. If it's the MSR or other Windows-related utility partition, it might be better to run the checks under Windows to avoid messing anything up, then doing a clean shutdown to a powered down state, preferably with any 'fastboot' settings and such switched off.

Note also that the message is a warning, not an error. The installer gives the option to use the disk 'as-is' and Continue. There should probably be a stronger "At Your Own Risk" statement, but if Neon is to be installed using available unused disk space whilst leaving existing partitions alone, that would probably be fine.

I'm not sure why we're even talking about this. It's not an error in the installer or an issue with the ISOs. It's a warning message to the user about the current state of their system that they can choose to ignore and Continue (maybe not a good idea) or investigate before proceeding (good idea).

Distro: KDE neon User Edition 5.13
Is it ok? mix files name: kinfocenter / about-distro_5.13.4-0xneon + 18.04 + bionic + build12_amd64.deb

amateescu wrote:@catweazel, what command did you use to get that very useful system information output?

It's inxi from ppa:unit193/inxi

Cheers.

Was there any update today, to see if everything was working.
My manjaro with plasma 5.13.4 today have update 406 files, Neon Bionic user preview nothing.

I downloaded the Bionic iso a couple of days ago, and the only issue that I have run into so far is installing the “Lxqt”.

As I mentioned in my previous post, Kuser was no longer available in Kubutu 18.04. You need Kuser to activate the “virtualbox users” in order to activate the usb port in Virtualbox. So the solution was to install “Lxqt”, then go to root > usr > share > applications > and finally lxqt-admin-user.desktop. I was able to do that on Kubutu. I get the following error when I try to install LXQT now.

The following packages have unmet dependencies:
lxqt : Depends: lximage-qt but it is not going to be installed
Depends: lxqt-core (= 25) but it is not going to be installed
Depends: lxqt-about but it is not going to be installed
Depends: lxqt-admin but it is not going to be installed
Depends: lxqt-openssh-askpass but it is not going to be installed
Depends: lxqt-powermanagement but it is not going to be installed
Depends: lxqt-sudo but it is not going to be installed
Recommends: calibre but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

@fredhoud,

most likely lxqt is formally found on the list but is not available, when searching in kubuntu through synaptic is obtained this text:

LXQt is an advanced, easy-to-use, and fast desktop environment based on Qt
technologies. It has been tailored for users who value simplicity, speed, and
an intuitive interface. Unlike most desktop environments, LXQt also works
fine with less powerful machines.

This package is a metapackage meant to provide all components of LXQt plus
some recommended components to provide a nearly feature complete desktop
environment.

When looking at Neon there is no description, maybe some Ubuntu repository is missing

edit.
I did a little research, Kubuntu has plasma 5.12.5 or 5.12.6 if using kubuntu backport ppa. Neon has plasma 5.13.4 and new framework

@lideda,

Needless to say either Kuser or Lxqt is needed in order to access the "Groups", and check the box for "vboxusers". Otherwise you the "usb" in virtualbox is disabled, and you won't be able to use it in virtualbox. So one of them should to be added!

@fredhoud,
I understand all, just some people have decided to remove groups from the GUI mode. Does gnome have an alternative to using the gnome program. More and more explained and insisted that you can only do the ban. I'm on facebook Neon teamed up against deleting root for Dolphin and now I do not have access anymore. I was discussing one group around it and told me that I was ridiculous and ungrateful because they do it for free and do what they like.

Code: Select all

sudo apt-get update
sudo apt-get install gnome-system-tools

users-admin

I've found two ways around this kuser problem . . .
1. Archlinux Wiki - quick and simple if you are only doing this vboxusers thing
2. Install kuser from Debian Stretch which works but pulls in quite a few dependancies. And I don't know if this will effect system stability. Use at your own risk.

https://wiki.archlinux.org/index.php/users_and_groups#User_groups
Go down to "Add users to a group with the gpasswd command:"
# gpasswd -a user group
user = your user name
group = vboxusers

or

https://packages.debian.org/search?keywords=kuser
Download kuser stretch(unstable)
sudo dpkg -i kuser
sudo apt-get -f install

It will pull in the following dependencies.

docbook-xsl
fonts-dejavu
fonts-dejavu-extra
icoutils
kde-runtime
kde-runtime-data
kdelibs-bin
kdelibs5-plugins
kdoctools
libcanberra-pulse
libclucene-core1v5
libgpgme++2v5
libkactivities6
libkcmutils4
libkde3support4
libkdeclarative5
libkdesu5
libkdewebkit5
libkdnssd4
libkemoticons4
libkfile4
libkhtml5
libkio5
libkjsapi4
libkjsembed4
libkldap4
libkmediaplayer4
libknewstuff3-4
libknotifyconfig4
libkntlm4
libkparts4
libkpty4
libkrosscore4
libktexteditor4
libkxmlrpcclient4
libnl-route-3-200
libntrack-qt4-1
libntrack0
libplasma3
libpolkit-qt-1-1
libqca2
libqca2-plugins
libqt4-designer
libqt4-qt3support
libqtwebkit4
libsolid4
libstreamanalyzer0v5
libstreams0v5
libthreadweaver4
libutempter0
libxml2-utils
ntrack-module-libnl-0
oxygen-icon-theme
plasma-scriptengine-javascript

Nvidia card is still giving problems. I've got a GeForce GTX 1050/PCIe/SSE2
Needed to add "nouveau.noaccel=1" to get both the livedvd to start and again after Neon was installed but before I got the Nvidia drivers installed.
My nvidia ppa didn't seem to be working.
This link solved my problem: "https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux"

$ sudo ubuntu-drivers autoinstall

This installed nvidia-390 and I'm in business.

@cylverbak,
In my suggestion, 2 additional files are required. Your suggestion Debian stretch is for the plasma-desktop version (4: 5.8.6-1) and I suspect it will cause the problem.