MX-18.3 RC1 Feedback

Message
Author
User avatar
dolphin_oracle
Developer
Posts: 19926
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX-18.3 RC1 Feedback

#21 Post by dolphin_oracle »

Gerson wrote: Wed May 22, 2019 1:27 pm When I went to install to replace MX 18.2 and try, I get this message for the root partition:
Partition-info fatal error: device /dev/ is not a black device
And I could not continue.
I downloaded ISO RC1 without problem, the sums match.
can you post the /var/log/minstall.log please.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Gerson
Posts: 876
Joined: Sun Nov 12, 2017 10:58 am

Re: MX-18.3 RC1 Feedback

#22 Post by Gerson »

@dolphin_oracle: can you post the /var/log/minstall.log please.

Code: Select all

2019-05-22 15:49:45.414 DBG default: Installer version: 19.5.2
2019-05-22 15:49:45.537 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2019-05-22 15:49:45.556 DBG default: +++ void MInstall::firstRefresh(QDialog*) +++
2019-05-22 15:49:45.557 DBG default: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled'"
2019-05-22 15:49:45.614 DBG default: exit code: 0
2019-05-22 15:49:45.615 DBG default: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled --set false'"
2019-05-22 15:49:45.632 DBG default: exit code: 0
2019-05-22 15:51:24.482 DBG default: "fskbsetting"
2019-05-22 15:52:15.909 DBG default: exit code: 0
2019-05-22 15:52:15.914 DBG default: +++ void MInstall::setupkeyboardbutton() +++
2019-05-22 15:52:18.005 DBG default: +++ void MInstall::updateDiskInfo() +++
2019-05-22 15:52:18.005 DBG default: "/sbin/swapoff -a"
2019-05-22 15:52:18.022 DBG default: Exit code:  0 , status:  QProcess::ExitStatus(NormalExit)
2019-05-22 15:52:18.022 DBG default: "/sbin/partprobe"
2019-05-22 15:52:21.804 DBG default: Exit code:  0 , status:  QProcess::ExitStatus(NormalExit)
2019-05-22 15:52:21.804 DBG default: +++ void MInstall::updatePartitionWidgets() +++
2019-05-22 15:52:21.814 DBG default: "partition-info --exclude=boot --min-size=6000 -n drives"
2019-05-22 15:52:21.866 DBG default: exit code: 0
2019-05-22 15:52:24.746 DBG default: "partition-info -n --exclude=boot,swap --min-size=6000 /dev/"
2019-05-22 15:52:24.773 DBG default: exit code: 2
2019-05-22 15:52:24.777 DBG default: "partition-info all -n --exclude=boot,swap --min-size=1000"
2019-05-22 15:52:24.849 DBG default: exit code: 0
2019-05-22 15:52:24.851 DBG default: "partition-info all -n --exclude=boot,"
2019-05-22 15:52:24.896 DBG default: exit code: 0
2019-05-22 15:52:24.898 DBG default: "partition-info all -n --exclude=boot,efi --min-size=256"
2019-05-22 15:52:24.954 DBG default: exit code: 0
No todos ignoramos las mismas cosas. :confused:

User avatar
dolphin_oracle
Developer
Posts: 19926
Joined: Sun Dec 16, 2007 1:17 pm

Re: MX-18.3 RC1 Feedback

#23 Post by dolphin_oracle »

Ok its in partition-info. we have an updated partition-info coming shortly.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Stevo
Developer
Posts: 12774
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX-18.3 RC1 Feedback

#24 Post by Stevo »

zebedeeboss wrote: Wed May 22, 2019 2:24 am Hi,

Install went well. Gave it the whole SSD and it let me choose the EFI partition to use :)

One minor error so far when installing inxi from the Package Installer

Code: Select all

Preparing to unpack .../15-inxi_2.3.5-1_all.deb ...
Unpacking inxi (2.3.5-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-61XnyC/15-inxi_2.3.5-1_all.deb (--unpack):
 trying to overwrite '/etc/inxi.conf', which is also in package smxi-inxi-antix 0.4.16
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /tmp/apt-dpkg-install-61XnyC/15-inxi_2.3.5-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Regards Zeb...
Yes, we already ship the newer version of inxi from antiX. That package should have a "Breaks:" in it for inxi so we don't get the broken packages, though.

User avatar
Stevo
Developer
Posts: 12774
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX-18.3 RC1 Feedback

#25 Post by Stevo »

skidoo wrote: Wed May 22, 2019 1:07 pm I haven't recently checked whether the index file(s) get rebuilt with first apt update operation (or first synaptic launch)? In either case, as is, it presents a memory overhead double-whammy during toram livesession ~~ a copy of the index from the linuxfs + another copy in the upper overlayfs layer. Shrug, earmark it as an item to be mentioned within a "tweaks/optimizations" article.
which is slow
The most notable "slow" (same noticed in recent antiX buster alpha) seems to be attributable to rebuilding manpage cache -- in 47 languages -- pursuant to each package install//upgrade transaction. The second most noticable (to me) finger-drumming, thumb-twiddling slowness is related, it stems from the default Acquire-Languages apt preference causing redownloading of translations during each apt update operation.

The front-end dialog for dpkg-reconfigure locales lacks a "(de)select All" (and a "you must select at least one" control) and is tedious to navigate. A first-run wrapper toward facilitating
1) English-only users: quick dpkg-reconfigure locales and set Acquire-Languages::None
2) apt install localepurge
...could significantly improve the user experience
Installing locales-all (3 MB download expands to 130 MB installed) also means they don't have to be rebuilt during package updates, saving a lot of time.

User avatar
AK-47
Developer
Posts: 1051
Joined: Sun Mar 24, 2019 7:04 pm

Re: MX-18.3 RC1 Feedback

#26 Post by AK-47 »

chrispop99 wrote: Wed May 22, 2019 1:23 pm
figueroa wrote: Wed May 22, 2019 1:06 pm
chrispop99 wrote: Wed May 22, 2019 2:48 am It's already on the Welcome screen.
Many new users would benefit from having a shortcut to the manual on their desktop. The failure to find and read the manual is epidemic. Saying so is really out of scope for RC1 feedback, but, what the heck.
Users dismiss the welcome screen, and would remove or ignore a link to the manual, in just the same way. It's a problem for many forums and other help resources that doesn't have a simple solution I'm afraid.

Chris
It wouldn't do any harm to have one there though. There is only one shortcut on the desktop on the live boot, and none on the default installed system. Besides you have to close the welcome screen anyway to access the installer, unless that's placed in the whisker menu or as a shortcut on the panel.

User avatar
BitJam
Developer
Posts: 2283
Joined: Sat Aug 22, 2009 11:36 pm

Re: MX-18.3 RC1 Feedback

#27 Post by BitJam »

AK-47 wrote: Wed May 22, 2019 8:25 pm It wouldn't do any harm to have one there though. There is only one shortcut on the desktop on the live boot, and none on the default installed system. Besides you have to close the welcome screen anyway to access the installer, unless that's placed in the whisker menu or as a shortcut on the panel.
+1

We have superb documentation. Let's not hide it from the users.
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."

-- Richard Feynman

User avatar
Adrian
Developer
Posts: 8250
Joined: Wed Jul 12, 2006 1:42 am

Re: MX-18.3 RC1 Feedback

#28 Post by Adrian »

I vote to add the manual link too.

User avatar
JayM
Qualified MX Guide
Posts: 6793
Joined: Tue Jan 08, 2019 4:47 am

Re: MX-18.3 RC1 Feedback

#29 Post by JayM »

JayM wrote: Wed May 22, 2019 4:43 am I ran the 32-bit version on an old Averatec netbook for several hours, and the 64-bit version on my desktop PC via live persistent USB, also for several hours, with no problems so far when just running it, browsing web pages, configuring options and playing games. In fact, with the new 4.19.05 (I think it is) kernel I didn't even experience any lock-ups on the desktop so far with Cool'n'Quiet enabled in BIOS as I often did with the stock 4.19 kernel when Cool'n'Quiet was enabled. 18.3RC1 seems fine so far. I'll continue testing both, off and on, from live USBs (I already reinstalled antiX on the netbook as it's faster than MX on that low-end machine.)
The desktop PC did lock up once this morning: the mouse cursor wouldn't move and keystrokes were unrecognized. Some experimentation revealed that Cool'n'Quiet isn't the culprit after all, it's ASRock's Boot Failure Guard, which along with Cool'n'Quiet is enabled when the power saving default settings are selected in the BIOS. (This is stupid IMO because what Boot Failure Guard does is detect when there's a booting problem due to the CPU being overclocked and automatically boots using the default CPU frequency settings to overcome that failure. Anyone who''s overclocking is going to already have loaded the performance default settings, not power saving. At least I can't imagine loading very conservative default values for everything to save energy then overclocking the CPU to boost performance at the cost of using more power.)

Anyway, the new kernel in conjunction with that BIOS setting still causes lock-ups as does the default MX 4.19 kernel and also 4.15 and 4.14 which is why I went with the 4.9 kernel on my installed system, but now that I know the actual cause I guess I can start using the newer kernels again even with Cool'n'Quiet enabled. Yay for me!

Other than that, no problems with the kernel, and I already tested the heck out of the installer these past few weeks and it seems to be fine now. No problems with the 32-bit version either, other than being slower on the netbook than antiX which is probably due to the overhead from running a full desktop environment instead of only a lightweight window manager, and the fact that the netbook only has 2GB of RAM and a SATA1 controller (desktop has 8GB and SATA2.)
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
chrispop99
Global Moderator
Posts: 3171
Joined: Tue Jan 27, 2009 3:07 pm

Re: MX-18.3 RC1 Feedback

#30 Post by chrispop99 »

BitJam wrote: Wed May 22, 2019 9:02 pm
AK-47 wrote: Wed May 22, 2019 8:25 pm It wouldn't do any harm to have one there though. There is only one shortcut on the desktop on the live boot, and none on the default installed system. Besides you have to close the welcome screen anyway to access the installer, unless that's placed in the whisker menu or as a shortcut on the panel.
+1

We have superb documentation. Let's not hide it from the users.
At the moment, the Welcome screen only appears at first boot, with an option to have it appear at every boot. How about if that option was reversed, so that the Welcome screen appeared at every boot until the user unchecked the option box?

I've never needed to close the Welcome screen to access the installer, but I guess it would be dependent on screen resolution.Another option might be to have the installer icon on the Welcome screen at boot, and removed post-install, in the same way as the user name and password information.

Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines

Locked

Return to “General”