Page 1 of 1
MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:13 am
by dolphin_oracle
Blog post with details here:
https://mxlinux.org/blog/mx-19-beta-1-a ... r-testing/
Any specific bugs can go to our Bug Manager at bugs.mxlinux.org
If posting hardware issues, please post the output of “quick-system-info” from the menu or terminal, at a minimum.
If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting installer issues, please include the contents of /var/log/minstall.log
If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:32 am
by Sparky
Probably a dumb question, but where can I download it from? Do I have to reinstall it on top of MX 18.3?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:40 am
by Eadwine Rose
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:40 am
by Sparky
Thanks, should have read more posts before asking, sorry about that.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:42 am
by Jerry3904
Do I have to reinstall it on top of MX 18.3?
There is no simple migration path when the Debian base changes.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:46 am
by m_pav
Betas are for testing and reporting faults, not for production environments. MX Linux 18.3 is based on old Debian stable, MX19 is based on the new Debian stable which have two entirely different backends. To answer your question about installing, it will have to be a fresh install, not an upgrade. Check the forum announcements for download locations and don't do anything to your production system without getting a really good back up of your data first.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:56 am
by Sparky
I'll use an older laptop I have to try it out. It is currently running freedos, so I don't have any data I can't replace and it 64 bit (AMD)
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 8:39 am
by Eadwine Rose
Nothing major, at all. When I boot I don't have the F keys option (I know why, no need to get into that), I select the 2nd on the list where I can pick what I want, I have let is check md5sum, all perfect.
However..
I select to see the boot messages. I then see the boot messages, I can see it testing that md5sum, and then it hops back to the splash screen stating md5sum ok, and in order to see the rest of the boot messages I have to press key combo again. I think it is supposed to stay on the boot messages, and not hop back?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 8:52 am
by Huckleberry Finn
Excuse my asking (I know, you may not have time at such a busy stage):
Is there a possibility to make a torrent at this page ?
https://mxlinux.org/torrent-files/
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 9:09 am
by chrispop99
Torrents are not usually provided until Final as there is unlikely to be enough users seeding.
Chris
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 9:26 am
by danielson
Great!
-Secondary (external) monitor failed to show up at initial boot from usb as well as after installation.
Did however work when selected from display.
-Cairo-dock installed and worked as expected (always a worry when "upgrading")!
-Conky can no longer be moved while selected and holding alt.
So much to discover!!
Thanks MX guys and gals for the hard work! :)
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 10:08 am
by Jerry3904
Conky can no longer be moved while selected and holding alt.
I had noticed that too, and can confirm. I thought it might be b/c the compositor is now enabled by default, but turning it off did not solve it (though maybe I needed to log out/in, will try again later).
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 10:34 am
by Gaer Boy
Beta runs fine live on laptop and desktop. Installation to laptop (Thinkpad X220) clean and most things I use regularly work as expected.
I have the same problem with installation to the desktop as I had with a4. On the first installer screen, there's a popup request for root password to mount sda2. Whether I enter the password or cancel, Thunar proceeds to mount 13 partitions and open instances for each. At about 4 sec intervals, I have to sit and wait for a minute and then clear them before I can proceed with installation.
I avoided the problem by disabling Volume Management in Thunar on the live system before installation. I don't see why this works - I thought Volume Management only affected plugged-in drives and the mounted partitions are on 2 of my 3 fixed disks.
I have 28 partitions in total - 7 on sda (SSD, ESP + 6 ext4), 11 on sdb (HDD, 3 primary ext4, 5 ext4 + 1 ntfs + 1 swap) and 10 on sdc (3 primary ext4, 5 ext4 + 1 ntfs). sdb is mainly a data disk and sdc is used for internal backup. Thunar mounted all the sdc partitions, none of the sdb partitions and 4 of the sda primary partitions. There doesn't seem to be any logic here. I identified all the partitions by UUID to eliminate any confusion.
I'm leaving any testing of b1 until I can resolve this.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:04 am
by ChrisUK
As above trying to install, problem with Thunar mounting all partitions... close a window, and it opens again - desktop full of Thunar windows. Solved same way by disabling Volume Management and starting Installation again.
Successfully installed on the following Laptop - all OK so far, except FN Brightness keys not working (not investigated yet, just reporting not working out of the box like MX16/17/18)
Code: Select all
Desktop: Xfce 4.14.1 Distro: MX-19beta-1_x64 patito feo August 25 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: SAMSUNG product: RV411/RV511/E3511/S3511/RV711 v: N/A
serial: <filter>
Mobo: SAMSUNG model: RV411/RV511/E3511/S3511/RV711 serial: <filter> BIOS: Phoenix
v: 03PA.M001.20110312.XW date: 03/12/2011
Battery: ID-1: BAT1 charge: 6.3 Wh condition: 6.5/47.5 Wh (14%) model: SAMSUNG Electronics
status: Unknown
CPU: Topology: Dual Core model: Intel Core i3 M 380 bits: 64 type: MT MCP arch: Nehalem
rev: 5 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20217
Speed: 1463 MHz min/max: 933/2533 MHz Core speeds (MHz): 1: 1463 2: 1463 3: 1463
4: 1463
Graphics: Device-1: NVIDIA GT218M [GeForce 315M] vendor: Samsung Co driver: nouveau v: kernel
bus ID: 02:00.0
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: NVA8 v: 3.3 Mesa 18.3.6 direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Samsung Co
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Device-2: NVIDIA High Definition Audio vendor: Samsung Co driver: snd_hda_intel
v: kernel bus ID: 02:00.1
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter vendor: Askey
driver: wl v: kernel port: 2000 bus ID: 03:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co
driver: r8169 v: kernel port: 4000 bus ID: 05:00.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.14 TiB used: 5.22 GiB (0.4%)
ID-1: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB
ID-2: /dev/sdb type: USB vendor: Toshiba model: MK2555GSX H size: 232.89 GiB
Partition: ID-1: / size: 25.71 GiB used: 5.22 GiB (20.3%) fs: ext4 dev: /dev/sdb8
Sensors: System Temperatures: cpu: 59.0 C mobo: 59.0 C gpu: nouveau temp: 62 C
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 190 Uptime: 1m Memory: 5.69 GiB used: 464.7 MiB (8.0%) Init: SysVinit
runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:08 am
by Jerry3904
On the first installer screen, there's a popup request for root password to mount sda2
I saw that as well, so just exited the installer, then started it again and didn't see it after that.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:09 am
by fehlix
ChrisUK wrote: Mon Aug 26, 2019 11:04 am
As above trying to install, problem with Thunar mounting all partitions... close a window, and it opens again - desktop full of Thunar windows. Solved same way by disabling Volume Management and starting Installation again.
So the automounts (and the corresponding popup's) are triggered after starting the installer, right?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:12 am
by Jerry3904
For me: right after starting.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:15 am
by dolphin_oracle
Gaer Boy wrote: Mon Aug 26, 2019 10:34 am
Beta runs fine live on laptop and desktop. Installation to laptop (Thinkpad X220) clean and most things I use regularly work as expected.
I have the same problem with installation to the desktop as I had with a4. On the first installer screen, there's a popup request for root password to mount sda2. Whether I enter the password or cancel, Thunar proceeds to mount 13 partitions and open instances for each. At about 4 sec intervals, I have to sit and wait for a minute and then clear them before I can proceed with installation.
I avoided the problem by disabling Volume Management in Thunar on the live system before installation. I don't see why this works - I thought Volume Management only affected plugged-in drives and the mounted partitions are on 2 of my 3 fixed disks.
I have 28 partitions in total - 7 on sda (SSD, ESP + 6 ext4), 11 on sdb (HDD, 3 primary ext4, 5 ext4 + 1 ntfs + 1 swap) and 10 on sdc (3 primary ext4, 5 ext4 + 1 ntfs). sdb is mainly a data disk and sdc is used for internal backup. Thunar mounted all the sdc partitions, none of the sdb partitions and 4 of the sda primary partitions. There doesn't seem to be any logic here. I identified all the partitions by UUID to eliminate any confusion.
I'm leaving any testing of b1 until I can resolve this.
please post the /var/log/minstall.log file. we've included a lot more debugging output to track down this sort of thing. we may need to disable automounting earlier for instance. also, is that without any input or did you run gparted at some point, either from inside the installer or from outside the installer.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:38 am
by dolphin_oracle
I can't reproduce the issue here, so going to need those logs...
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:39 am
by Jerry3904
I will look as well, but aren't those logs lost as soon as the Live session ends and the user removes the USB?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:41 am
by dolphin_oracle
Jerry3904 wrote: Mon Aug 26, 2019 11:39 am
I will look as well, but aren't those logs lost as soon as the Live session ends and the user removes the USB?
yes...saved on install though if you go through with it.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:46 am
by Jerry3904
OK
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:54 am
by Gerson
The ugly duckling for now has flaws in the panel, does not have the time and the conky is not transparent, I miss Docky and Openastro that was in the test repository, I congratulate them for placing FreeOffice, I hope to test it soon. Are there two types of screensavers?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:55 am
by dolphin_oracle
Gerson wrote: Mon Aug 26, 2019 11:54 am
The ugly duckling for now has flaws in the panel, does not have the time and the conky is not transparent, I miss Docky and Openastro that was in the test repository, I congratulate them for placing FreeOffice, I hope to test it soon. Are there two types of screensavers?
did you turn off the compositor? you need the compositor on for transparency on the new Xfce. or are you using an existing home folder perhaps?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 11:58 am
by asqwerth
It's this particular conky.
Is compositing turned on?
You may also have to edit the conky itself in a text editor.
Read my post here:
viewtopic.php?p=522161#p522161
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 12:00 pm
by ChrisUK
Here's the minstall.log from my install:
minstall.log
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 12:02 pm
by ChrisUK
fehlix wrote: Mon Aug 26, 2019 11:09 am
ChrisUK wrote: Mon Aug 26, 2019 11:04 am
As above trying to install, problem with Thunar mounting all partitions... close a window, and it opens again - desktop full of Thunar windows. Solved same way by disabling Volume Management and starting Installation again.
So the automounts (and the corresponding popup's) are triggered after starting the installer, right?
I'm actually not sure, but I think it was straight away... may have been after a password entry though... not sure
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 12:07 pm
by dolphin_oracle
so for you guys running into the installer issue, could you try, from the live usb without launching the installer
Code: Select all
sudo partprobe
sudo blkid -c /dev/null
please and thank you.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 12:09 pm
by fehlix
Jerry3904 wrote: Mon Aug 26, 2019 11:12 am
For me: right after starting.
OK, will post a potential "solution" with the dev-thread for further considerations.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 12:14 pm
by dolphin_oracle
fehlix wrote: Mon Aug 26, 2019 12:09 pm
Jerry3904 wrote: Mon Aug 26, 2019 11:12 am
For me: right after starting.
OK, will post a potential "solution" with the dev-thread for further considerations.
I think I know where you're going...
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 12:26 pm
by Jerry3904
It looks like this is the first time I ran it and exited when it wanted root password:
Code: Select all
2019-08-25 20:15:12.610 DBG default: +++ void MInstall::startup() +++
2019-08-25 20:15:12.611 DBG default: Exec #1: "uname -m | grep -q i686"
2019-08-25 20:15:12.730 DBG default: Exit #1: 1 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.730 DBG default: Exec #2: "test -d /sys/firmware/efi"
2019-08-25 20:15:12.751 DBG default: Exit #2: 0 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.751 DBG default: uefi = true
2019-08-25 20:15:12.751 DBG default: Exec #3: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled'"
2019-08-25 20:15:12.883 DBG default: Exit #3: 0 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.883 DBG default: Exec #4: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled --set false'"
2019-08-25 20:15:12.926 DBG default: Exit #4: 0 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.926 DBG default: Exec #5: "ps -aux |grep -v grep | grep devmon"
2019-08-25 20:15:12.955 DBG default: Exit #5: 1 QProcess::ExitStatus(NormalExit)
2019-08-25 20:15:12.955 DBG default: Exec #6: "grep space /home/$(logname)/.desktop-session/desktop-code.*"
2019-08-25 20:15:12.967 DBG default: SErr #6: "grep: /home/demo/.desktop-session/desktop-code.*: No such file or directory\n"
2019-08-25 20:15:12.967 DBG default: Exit #6: 2 QProcess::ExitStatus(NormalExit)
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 12:30 pm
by ChrisUK
dolphin_oracle wrote: Mon Aug 26, 2019 12:07 pm
so for you guys running into the installer issue, could you try, from the live usb without launching the installer
Code: Select all
sudo partprobe
sudo blkid -c /dev/null
please and thank you.
...
code]
sudo partprobe
Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
[/code]
Code: Select all
sudo blkid -c /dev/null
/dev/sda1: LABEL="MX18" UUID="51741f74-0727-47ea-a731-63f43e640978" TYPE="ext4" PARTUUID="ce682fae-01"
/dev/sda2: LABEL="MX175" UUID="70cfd9e8-676e-4fa4-86ba-e302fb5ede00" TYPE="ext4" PARTUUID="ce682fae-02"
/dev/sda3: LABEL="Data" UUID="23A7668A02124A50" TYPE="ntfs" PTTYPE="dos" PARTUUID="ce682fae-03"
/dev/sda5: LABEL="DataExt4" UUID="36f9ff28-7a4b-4598-9b1a-363ba6302bd2" TYPE="ext4" PARTUUID="ce682fae-05"
/dev/sda6: LABEL="NTFS1" UUID="3DE1D3681D7E6DBE" TYPE="ntfs" PTTYPE="dos" PARTUUID="ce682fae-06"
/dev/sdb1: UUID="2019-08-25-19-38-05-00" LABEL="MX-Live" TYPE="iso9660" PTUUID="5d95e9ad" PTTYPE="dos" PARTUUID="5d95e9ad-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI-LIVE" LABEL="EFI-LIVE" UUID="6CFD-B910" TYPE="vfat" PARTUUID="5d95e9ad-02"
/dev/loop0: TYPE="squashfs"
/dev/sdd5: LABEL="MX172" UUID="bf7cffcc-b28d-49f6-8736-b4da5e5270d6" TYPE="ext4" PARTUUID="b38f0398-05"
/dev/sdd6: LABEL="Data" UUID="0D90E40DA50DEF3B" TYPE="ntfs" PARTUUID="b38f0398-06"
/dev/sdd7: LABEL="DataExt4" UUID="000ec35e-c8c0-4b02-ba91-aa51ed2c6bbe" TYPE="ext4" PTTYPE="dos" PARTUUID="b38f0398-07"
/dev/sdd8: LABEL="rootMX19" UUID="e15eb685-05ad-4247-85c3-0dd1d79914f1" TYPE="ext4" PARTUUID="b38f0398-08"
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 12:34 pm
by dolphin_oracle
ChrisUK wrote: Mon Aug 26, 2019 12:30 pm
dolphin_oracle wrote: Mon Aug 26, 2019 12:07 pm
so for you guys running into the installer issue, could you try, from the live usb without launching the installer
Code: Select all
sudo partprobe
sudo blkid -c /dev/null
please and thank you.
...
code]
sudo partprobe
Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
[/code]
Code: Select all
sudo blkid -c /dev/null
/dev/sda1: LABEL="MX18" UUID="51741f74-0727-47ea-a731-63f43e640978" TYPE="ext4" PARTUUID="ce682fae-01"
/dev/sda2: LABEL="MX175" UUID="70cfd9e8-676e-4fa4-86ba-e302fb5ede00" TYPE="ext4" PARTUUID="ce682fae-02"
/dev/sda3: LABEL="Data" UUID="23A7668A02124A50" TYPE="ntfs" PTTYPE="dos" PARTUUID="ce682fae-03"
/dev/sda5: LABEL="DataExt4" UUID="36f9ff28-7a4b-4598-9b1a-363ba6302bd2" TYPE="ext4" PARTUUID="ce682fae-05"
/dev/sda6: LABEL="NTFS1" UUID="3DE1D3681D7E6DBE" TYPE="ntfs" PTTYPE="dos" PARTUUID="ce682fae-06"
/dev/sdb1: UUID="2019-08-25-19-38-05-00" LABEL="MX-Live" TYPE="iso9660" PTUUID="5d95e9ad" PTTYPE="dos" PARTUUID="5d95e9ad-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="EFI-LIVE" LABEL="EFI-LIVE" UUID="6CFD-B910" TYPE="vfat" PARTUUID="5d95e9ad-02"
/dev/loop0: TYPE="squashfs"
/dev/sdd5: LABEL="MX172" UUID="bf7cffcc-b28d-49f6-8736-b4da5e5270d6" TYPE="ext4" PARTUUID="b38f0398-05"
/dev/sdd6: LABEL="Data" UUID="0D90E40DA50DEF3B" TYPE="ntfs" PARTUUID="b38f0398-06"
/dev/sdd7: LABEL="DataExt4" UUID="000ec35e-c8c0-4b02-ba91-aa51ed2c6bbe" TYPE="ext4" PTTYPE="dos" PARTUUID="b38f0398-07"
/dev/sdd8: LABEL="rootMX19" UUID="e15eb685-05ad-4247-85c3-0dd1d79914f1" TYPE="ext4" PARTUUID="b38f0398-08"
thank you.
I'm starting to think that the automount-disable happens too fast for some systems, and xfconf hasn't caught up before we probe for drives. fehlix is working on it.
for now, workaround is to manually disable automounting before launching for those machines so affected (mine isn't one, but my hardware is slow, which might actually help if timing is the issue).
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 1:05 pm
by BV206
I want to use zsync to download the beta (and the August 18.3 iso).
I see the zsync "files" listed on sourceforge.net but because of their mirrors or something the .zsync url doesn't link to the actual file.
Is there an easy way to do that?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 2:04 pm
by fehlix
BV206 wrote: Mon Aug 26, 2019 1:05 pm
I want to use zsync to download the beta (and the August 18.3 iso).
I see the zsync "files" listed on sourceforge.net but because of their mirrors or something the .zsync url doesn't link to the actual file.
Is there an easy way to do that?
Yea, zsync-ing from sourcefourge is a bit tricky.
The attached zsync-helper script will get first closest mirror before the actually zsync is taking place:
The best result you would have with "binary" close iso.
Ok just testing how it would go, using MX18.3 iso (which is not very "binary" close):
Code: Select all
./zsync-mx-19-testing.sh MX-19beta-1_x64.iso MX-18.3_August_x64.iso
Well at least it tells us that "Target 22.5% complete."
Code: Select all
./zsync-mx-19-testing.sh MX-19beta-1_x64.iso MX-18.3_August_x64.iso
Downloading "MX-19beta-1_x64.iso" file
MX-19beta-1_x64.iso
Using input file: MX-18.3_August_x64.iso
Executing zsync command
#################### 100.0% 601.4 kBps DONE
reading seed file MX-18.3_August_x64.iso: *****************************
**************
++++
***Read MX-18.3_August_x64.iso. Target 22.5% complete.
*******************************************************
downloading from http://iweb.dl.sourceforge.net/project/mx-linux/Testing/MX-19/MX-19beta-1_x64.iso:
######-------------- 32.2% 7147.5 kBps 2:16 ETA
Attached the zsync helper script:
zsync-mx-19-testing.sh
Code: Select all
#!/bin/bash
# zsync helper script
# for MX-19-beta Testing
# filename zsync-mx-19-testing.sh
usage()
{
echo "Usage $0 script"
echo "$0 download_filename.iso inputfile.iso"
echo " Where inputfile.iso is the file you already have that's similar to the one you download"
echo
echo "$0 download_filename.iso"
echo " This command format will search automatically for the most recent MX*x64.iso file in the current folder"
exit
}
[[ "$1" == "--help" || "$1" == "-h" ]] && usage
TARGET="$1"
[[ -z "$1" ]] && {
echo "You need to specify a file name to download. exiting..."
echo
usage
}
echo "Downloading \"$1\" file"
grep "x64" <<< "$1" && ARCH="x64" || ARCH="386"
# add available local ISO-sources here - newest first
# check latest ISO-sources are available
SOURCE="$2"
[[ -f "$SOURCE" ]] && echo "Using input file:" "$SOURCE" || {
[[ "$SOURCE" == "" ]] && echo "Input source not specified, trying to find a useful ISO in current path"
[[ "$SOURCE" != "" ]] && echo "Input file \"$SOURCE\" not found, trying to find a useful ISO in current path"
SOURCE=$(find . -iname "MX*$ARCH*.iso" -printf "%T+\t%p\n" | sort -r | head -1 | cut -f2)
[[ "$SOURCE" != "" ]] && echo "Using "$SOURCE" source file" || {
echo "Could not found an appropriate input file, exiting..."
echo
usage
}
}
# do we have zsync
command -v zsync >&- || {
# opps we need to and install zsync
sudo apt-get update
sudo apt-get install zsync
}
ZSYNC="${TARGET}".zsync
# get closest sourceforge server for zsync
DOWNLD=https://sourceforge.net/projects/mx-linux/files/Testing/MX-19/"${ZSYNC}"/download
SPIDER=$(wget -nv --spider "${DOWNLD}" 2>&1 | grep -Eo https.*iso.zsync | sed 's/https/http/')
[[ -z "$SPIDER" ]] && {
echo; echo "Could not find \"$1\" file on SourceForge server, please check the name. Exiting..."
echo
usage
}
# let's do zsync
[[ -f "${TARGET}" ]] || echo; echo "Executing zsync command"; zsync -i "$SOURCE" "${SPIDER}" || {
echo
usage
}
HTH
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 2:07 pm
by franksmcb
The beta is looking good.
No issues booting into systemd and install snapd.
Snaps seem to be working well.
First impressions are very good.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 2:12 pm
by Gerson
dolphin_oracle wrote: Mon Aug 26, 2019 11:55 am
Gerson wrote: Mon Aug 26, 2019 11:54 am
The ugly duckling for now has flaws in the panel, does not have the time and the conky is not transparent, I miss Docky and Openastro that was in the test repository, I congratulate them for placing FreeOffice, I hope to test it soon. Are there two types of screensavers?
did you turn off the compositor? you need the compositor on for transparency on the new Xfce. or are you using an existing home folder perhaps?
I'm sorry, it's my mistake, I used the old /home folder.
I reinstalled from zeros and now everything works normally, I just hope to have Openastro back in the repository.
Great job, thank you.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 2:35 pm
by penguin
How to import MX-19 GPG key ?
Tried to verify MX-19beta-1_x64.iso (Highly recommended to verify MX iso file that you download , these days that MX Linux keeps continuously first position
) . Why ? I remember, times ago, someone altered iso files of Manjaro or Mint on their original repositories(website) and that was noticed by admins, hours later!
Code: Select all
gpg --verify MX-19beta-1_x64.iso.sig
gpg: assuming signed data in 'MX-19beta-1_x64.iso'
gpg: Signature made Sun 25 Aug 2019 09:38:38 PM CEST
gpg: using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpg: Can't check signature: No public key
Seems GPGkey is missing in my laptop.
Commands
gpg --list-keys and
gpg --list-secret-keys in Terminal
returns empty result, meanwhile FiX GPG Keys in MX Tools gives :
Code: Select all
Checking security.debian.org_dists_stretch_updates_InRelease
Good GPG signature found.
Checking it.mxrepo.com_antix_stretch_dists_stretch_InRelease
Good GPG signature found.
Checking ftp.bg.debian.org_debian_dists_stretch_Release
Good GPG signature found.
Checking ftp.bg.debian.org_debian_dists_stretch-updates_InRelease
Good GPG signature found.
Checking repo.skype.com_deb_dists_stable_InRelease
Good GPG signature found.
Checking download.mono-project.com_repo_debian_dists_stable-stretch_InRelease
Good GPG signature found.
Checking it.mxrepo.com_mx_repo_dists_stretch_InRelease
Good GPG signature found.
Checking deb.opera.com_opera-stable_dists_stable_InRelease
Good GPG signature found.
P.S
Some GPG tuts for folks.
Code: Select all
https://wiki.manjaro.org/index.php?title=How-to_verify_GPG_key_of_official_.ISO_images
Code: Select all
http://irtfweb.ifa.hawaii.edu/~lockhart/gpg/
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 2:39 pm
by dolphin_oracle
penguin wrote: Mon Aug 26, 2019 2:35 pm
How to import MX-19 GPG key ?
Tried to verify MX-19beta-1_x64.iso
Code: Select all
gpg --verify MX-19beta-1_x64.iso.sig
gpg: assuming signed data in 'MX-19beta-1_x64.iso'
gpg: Signature made Sun 25 Aug 2019 09:38:38 PM CEST
gpg: using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpg: Can't check signature: No public key
Seems GPGkey is missing in my laptop.
Commands
gpg --list-keys and
gpg --list-secret-keys in Terminal
returns empty result, meanwhile FiX GPG Keys in MX Tools gives :
Code: Select all
Checking security.debian.org_dists_stretch_updates_InRelease
Good GPG signature found.
Checking it.mxrepo.com_antix_stretch_dists_stretch_InRelease
Good GPG signature found.
Checking ftp.bg.debian.org_debian_dists_stretch_Release
Good GPG signature found.
Checking ftp.bg.debian.org_debian_dists_stretch-updates_InRelease
Good GPG signature found.
Checking repo.skype.com_deb_dists_stable_InRelease
Good GPG signature found.
Checking download.mono-project.com_repo_debian_dists_stable-stretch_InRelease
Good GPG signature found.
Checking it.mxrepo.com_mx_repo_dists_stretch_InRelease
Good GPG signature found.
Checking deb.opera.com_opera-stable_dists_stable_InRelease
Good GPG signature found.
P.S
Some GPG tuts for folks.
Code: Select all
https://wiki.manjaro.org/index.php?title=How-to_verify_GPG_key_of_official_.ISO_images
Code: Select all
http://irtfweb.ifa.hawaii.edu/~lockhart/gpg/
per wiki
https://mxlinux.org/wiki/system/signed-iso-files/#MX-17
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 2:50 pm
by penguin
dolphin_oracle wrote: Mon Aug 26, 2019 2:39 pm
penguin wrote: Mon Aug 26, 2019 2:35 pm
How to import MX-19 GPG key ?
Tried to verify MX-19beta-1_x64.iso
Code: Select all
gpg --verify MX-19beta-1_x64.iso.sig
gpg: assuming signed data in 'MX-19beta-1_x64.iso'
gpg: Signature made Sun 25 Aug 2019 09:38:38 PM CEST
gpg: using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpg: Can't check signature: No public key
Seems GPGkey is missing in my laptop.
Commands
gpg --list-keys and
gpg --list-secret-keys in Terminal
returns empty result, meanwhile FiX GPG Keys in MX Tools gives :
Code: Select all
Checking security.debian.org_dists_stretch_updates_InRelease
Good GPG signature found.
Checking it.mxrepo.com_antix_stretch_dists_stretch_InRelease
Good GPG signature found.
Checking ftp.bg.debian.org_debian_dists_stretch_Release
Good GPG signature found.
Checking ftp.bg.debian.org_debian_dists_stretch-updates_InRelease
Good GPG signature found.
Checking repo.skype.com_deb_dists_stable_InRelease
Good GPG signature found.
Checking download.mono-project.com_repo_debian_dists_stable-stretch_InRelease
Good GPG signature found.
Checking it.mxrepo.com_mx_repo_dists_stretch_InRelease
Good GPG signature found.
Checking deb.opera.com_opera-stable_dists_stable_InRelease
Good GPG signature found.
P.S
and
Some GPG tuts for folks.
Code: Select all
https://wiki.manjaro.org/index.php?title=How-to_verify_GPG_key_of_official_.ISO_images
Code: Select all
http://irtfweb.ifa.hawaii.edu/~lockhart/gpg/
per wiki
https://mxlinux.org/wiki/system/signed-iso-files/#MX-17
Thanks dolphin_oracle !
Before writing my post I made a search on MX Linux using
GPG key as word for my search , but I have been not strictly cautious. And I remembered that have read this info before ...
Code: Select all
gpg --keyserver hkp://keys.gnupg.net --recv-keys B9B6375C 0679EE98 892C32F1
gpg: key 13C74A22892C32F1: public key "Steven Pusser <stevep@mxlinux.org>" imported
gpg: key 70938C780679EE98: public key "Adrian <adrian@mxlinux.org>" imported
gpg: key 9B68A1E8B9B6375C: public key "Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>" imported
gpg: Total number processed: 3
gpg: imported: 3
and
Code: Select all
gpg --list-keys
/home/penguin/.gnupg/pubring.kbx
--------------------------------
pub rsa2048 2016-10-20 [SC]
09DA59435EF8C739C8ED615613C74A22892C32F1
uid [ unknown] Steven Pusser <stevep@mxlinux.org>
sub rsa2048 2016-10-20 [E]
pub rsa2048 2015-10-29 [SC] [expires: 2019-10-08]
F27753A18E92E3937E6335E770938C780679EE98
uid [ unknown] Adrian <adrian@mxlinux.org>
sub rsa2048 2015-10-29 [E] [expires: 2019-10-08]
pub rsa4096 2017-09-06 [SC]
F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
uid [ unknown] Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>
sub rsa4096 2017-09-06 [E]
and
Code: Select all
gpg --verify MX-19beta-1_x64.iso.sig
gpg: assuming signed data in 'MX-19beta-1_x64.iso'
gpg: Signature made Sun 25 Aug 2019 09:38:38 PM CEST
gpg: using RSA key F62EDEAA3AE70A9C99DAC4189B68A1E8B9B6375C
gpg: Good signature from "Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: F62E DEAA 3AE7 0A9C 99DA C418 9B68 A1E8 B9B6 375C
Thanks for your time and effort, Mx Linux Team !
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 3:09 pm
by Eadwine Rose
Mind, I am not seeing the "standard screen" with all the F-key options in the bottom, but I can go to the options using the text menus option.
IMG_8222.JPG
I didn't see the F-key options in 18.3 anymore either, so to me this is normal behavior.
Everything ends up on the desktop in the end with both screens working (just left and right are swapped, as always). I managed to get the sound working after selecting the correct source in MX Tools Select Sound.
Haven't installed yet, as I am not ready to deal with stuff going wrong at this hour, should that happen.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 3:25 pm
by Gerson
Installed zeros with /home clean, runs perfect except that when turned off returns to display for 20 seconds the login screen and then if you start the shutdown.
All the applications I use even some of KDE have no problem, Virtualbox 6, Write and TextMaker comply well, even installed Brave-browser and does not give problem.
This is my desk:
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 3:28 pm
by chrispop99
The login screen re-appearing is something that is known
Chris
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 3:29 pm
by Stevo
Gerson wrote: Mon Aug 26, 2019 2:12 pm
dolphin_oracle wrote: Mon Aug 26, 2019 11:55 am
Gerson wrote: Mon Aug 26, 2019 11:54 am
The ugly duckling for now has flaws in the panel, does not have the time and the conky is not transparent, I miss Docky and Openastro that was in the test repository, I congratulate them for placing FreeOffice, I hope to test it soon. Are there two types of screensavers?
did you turn off the compositor? you need the compositor on for transparency on the new Xfce. or are you using an existing home folder perhaps?
I'm sorry, it's my mistake, I used the old /home folder.
I reinstalled from zeros and now everything works normally, I just hope to have Openastro back in the repository.
Great job, thank you.
Yes, we are still working on populating the repo, so let us know what's missing!
If you install xscreensaver to get more screensavers, you will get two entries in the settings. We patched the new xfce4-screensaver applet to add "XFCE4", otherwise we had two identical entries with the same icon. The xscreensavers will automatically appear as choices in the XFCE4 Screensaver settings.
We also know that some Compiz users will have to use workarounds to get it to start, depending on their hardware and video driver.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 4:44 pm
by Paul..
Eadwine Rose wrote: Mon Aug 26, 2019 3:09 pm
Mind, I am not seeing the "standard screen" with all the F-key options in the bottom, but I can go to the options using the text menus option.
Welcome to the wacky world of UEFI...
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 4:48 pm
by Eadwine Rose
Yeps. It happened on the 18.3 as well. I don't mind, I can get to what I need easily enough. Just wanted to show things can look.. different
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 5:00 pm
by fladd
(Some of) the new XFCE features do not seem to be properly integrated yet (maybe because it is still a beta?). For instance, the new screensaver and its lock screen are not active by default (clicking on the lock screen icon does nothing). Even more confusing, there is a shortcut for locking the screen preconfigured that uses a different locking mechanism than the (new) default XFCE one. Also the new colour profiles settings dialogue seems to be entirely missing (or at least I could not find it).
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:01 pm
by fehlix
fladd wrote: Mon Aug 26, 2019 5:00 pm
the new screensaver and its lock screen are not active by default (clicking on the lock screen icon does nothing). Even more confusing, there is a shortcut for locking the screen preconfigured that uses a different locking mechanism than the (new) default XFCE one.
After having enabled the new screensaver/locker combo both the keyboard shortcut "Ctrl-Alt-Del" and the Lockicon in the Whisker menu will work. Note xflock4 command will call the new Screensaver/Locker.
See here for settings up the Screensaver/Locker app
https://docs.xfce.org/apps/screensaver/start
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:07 pm
by Jerry3904
Also the new colour profiles settings dialogue seems to be entirely missing (or at least I could not find it).
I don't see it either and, according to
the Help file, it does not work automatically yet. We'll be checking that out...
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:22 pm
by Dede
In the MX Package Installer, Debian Backports didn't work. I enabled them in the repos, and now any MX Tool doesn't work at all! And in Thunar, "Open root Thunar here" doesn't work neither.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:26 pm
by Jerry3904
I believe there are no Debian backports yet, so the screen is empty. What you enabled may have been for Stretch maybe?
The Open Root Thunar works fine for me (on a folder that needs it).
Re: MX-19 Beta 1 Feedback (frugal-persist woes?)
Posted: Mon Aug 26, 2019 6:35 pm
by baldyeti
i thought i'd use frugal persist because i had never tried it and was always intrigued by the feature.
Maybe i did something wrong but it wasn't all smooth sailing.
Note i did not allow the installer to relabel my target partition.
The generated grub.cfg looks for a kernel at antiX/vmlinuz,
but the directory created to host the frugal install is actually called antiX-4.19-amd64 (or somesuch)
After fixing that, i still could not boot with the default grub entry (fails to find antiX/linuxfs, although it exists)
*but* the failsafe option actually proceeds and works. Hooray!
Unfortunately persistence did not actually work, persist-save tells me rootfs persistence is not enabled, although i chose frugal with persistence of both root and home (i had to choose sizes smaller than the default because of space limitations)
I may very well have missed an option, tick-box or whatnot during my rushed install, sorry if that is the case - do not spend too much time trying to educate me on the subject as the focus of this thread is the MX beta.
Otherwise the OS itself looks and acts fine AFAICT.
Very promising,
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:43 pm
by fehlix
Dede wrote: Mon Aug 26, 2019 6:22 pm
And in Thunar, "Open root Thunar here" doesn't work neither.
What folder did you right click to "Open root Thunar here" ?
Just checked it, with a not really useful example by
right-clicking on Documents an selecting "Open root Thunar here".
You might need to enter the root-password, not your own/user password.
Open-Thunar-as-root.png
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:45 pm
by timkb4cq
Gerson wrote: Mon Aug 26, 2019 2:12 pm
... I just hope to have Openastro back in the repository.
You got it. The new version works well.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:53 pm
by Adrian
Dede wrote: Mon Aug 26, 2019 6:22 pm
In the MX Package Installer, Debian Backports didn't work. I enabled them in the repos, and now any MX Tool doesn't work at all! And in Thunar, "Open root Thunar here" doesn't work neither.
Fixed the Backports in Package Installer, for some reason Buster doesn't have .gz Package list, it has only .xz, I changed the code to download that. The other issue is not related to MX Package Installer.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:57 pm
by Dede
What folder did you right click to "Open root Thunar here" ?
Just checked it, with a not really useful example by
right-clicking on Documents an selecting "Open root Thunar here".
You might need to enter the root-password, not your own/user password.
It doesn't work anywhere... and my password and the root password are the same...
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 6:59 pm
by dolphin_oracle
Jerry3904 wrote: Mon Aug 26, 2019 6:07 pm
Also the new colour profiles settings dialogue seems to be entirely missing (or at least I could not find it).
I don't see it either and, according to
the Help file, it does not work automatically yet. We'll be checking that out...
there are "profiles" under Display->advanced, although I don't know how they work. Is that the same as the color profiles?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 7:03 pm
by Stevo
Jerry3904 wrote: Mon Aug 26, 2019 6:26 pm
I believe there are no Debian backports yet, so the screen is empty. What you enabled may have been for Stretch maybe?
The Open Root Thunar works fine for me (on a folder that needs it).
Buster backports has been up and running for several weeks at least, and does have some packages in it, such as Musescore (which also is in MX 19 main, though):
https://lists.debian.org/debian-backpor ... reads.html
We've added some packages that would be in MX 18 test to the main MX 19 repo so we can take advantage of the beta phase to get them tested. If there's something wrong, we can pull or move them easily. One of them is Kdenlive 19.08, for example, in addition to Musescore.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 7:10 pm
by Stevo
Well, it looks like Debian is also setting up a "FastTrack" backports repo for packages that haven't already made their way into testing, just to make it more complicated:
https://wiki.debian.org/FastTrack
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 7:14 pm
by Dede
Jerry3904 wrote: Mon Aug 26, 2019 6:26 pm
I believe there are no Debian backports yet, so the screen is empty. What you enabled may have been for Stretch maybe?
The Open Root Thunar works fine for me (on a folder that needs it).
Well... after that, I can't open any of the MX Tools...!
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 7:16 pm
by Dede
fehlix wrote: Mon Aug 26, 2019 6:43 pm
Dede wrote: Mon Aug 26, 2019 6:22 pm
And in Thunar, "Open root Thunar here" doesn't work neither.
What folder did you right click to "Open root Thunar here" ?
Just checked it, with a not really useful example by
right-clicking on Documents an selecting "Open root Thunar here".
You might need to enter the root-password, not your own/user password.
Open-Thunar-as-root.png
It doesn't work anywhere... and my password and the root password are the same...
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 7:17 pm
by Jerry3904
Take out that repo
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 7:29 pm
by Dede
Jerry3904 wrote: Mon Aug 26, 2019 7:17 pm
Take out that repo
I can't... MX Package Installer (as every MX Tool) doesn't open anymore...
I'll try to reinstall MX 19...
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 7:32 pm
by nathan2423
In whisker menu, "position search entry next to panel button" does not appear to work for me as it does in 18.3.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 7:55 pm
by Jerry3904
Works here, putting the search box at the bottom.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 8:00 pm
by Jerry3904
Back to the Color Profiles question: we are apparently missing a package: xfce4-color-settings
No clue where that package is. I posted on the Xfce Forum, and was told it was in the Xubuntu Dev repo, but it isn't there. Then I looked at the Xfce GIT repo, and it's not there either. Looks like maybe they took it down...?
Re: MX-19 Beta 1 Feedback (frugal-persist woes?)
Posted: Mon Aug 26, 2019 8:00 pm
by fehlix
baldyeti wrote: Mon Aug 26, 2019 6:35 pm
i thought i'd use frugal persist because i had never tried it and was always intrigued by the feature.
Maybe i did something wrong but it wasn't all smooth sailing.
Note i did not allow the installer to relabel my target partition.
The generated grub.cfg looks for a kernel at antiX/vmlinuz,
but the directory created to host the frugal install is actually called antiX-4.19-amd64 (or somesuch)
After fixing that, i still could not boot with the default grub entry (fails to find antiX/linuxfs, although it exists)
*but* the failsafe option actually proceeds and works. Hooray!
Not sure: I just done a frugal install. The created grub.entry look as it should be:
Code: Select all
menuentry "MX 19beta-1 (patito feo) Frugal Install" {
search --no-floppy --set=root --fs-uuid 2635ed5c-9868-48c5-bfd6-55dedc20cc01
linux /antiX-Frugal-4.19.0-5-amd64/vmlinuz bdir=antiX-Frugal-4.19.0-5-amd64 buuid=2635ed5c-9868-48c5-bfd6-55dedc20cc01 quiet splasht=v kbd=de
initrd /antiX-Frugal-4.19.0-5-amd64/initrd.gz
}
The frugal-directory is correctly named: "/antiX-Frugal-4.19.0-5-amd64".
The created grub.entry shall work if you copy it into an existing grub-install under /boot/grub/custom.cfg,
which provide an new menuentry with the grub-menu.
If you want to boot from the LiveUSB/ISO and if you not re-label the frugal partition, you need to tell it where to look for the the frugal-files, e.g with boot options flab=xxx, fdev=/dev/sda2 or fuuid=XXXXXXXX
Also I think, the symptoms you describe have nothing to do with MX-19Beta-1, but rather that you need first to find out how frugal booting works.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 8:56 pm
by nathan2423
Re: MX-19 Beta 1 Feedback
#65
Post by Jerry3904 » Mon Aug 26, 2019 7:55 pm
Works here, putting the search box at the bottom.
-------------------
Yes it does put it at the bottom, but in 18.3 my Search box is to the left, directly over the startup button, while in 19 the search box is over to the right. Probably not significant enough to worry about, but I noticed it and thought I would report. Maybe it's a change in Whisker.
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 9:00 pm
by Jerry3904
Not like this?
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 9:21 pm
by Stevo
Jerry3904 wrote: Mon Aug 26, 2019 8:00 pm
Back to the Color Profiles question: we are apparently missing a package:
xfce4-color-settings
No clue where that package is. I posted on the Xfce Forum, and was told it was in the Xubuntu Dev repo, but it isn't there. Then I looked at the Xfce GIT repo, and it's not there either. Looks like maybe they took it down...?
It's a program that's supposed to be part of xfce4-settings, but I don't see it as part of our package. Let me rebuild Sid's, since they have it:
https://packages.debian.org/search?sear ... e&arch=any
Re: MX-19 Beta 1 Feedback
Posted: Mon Aug 26, 2019 9:33 pm
by Stevo
Here's the new packages, ignore the dbgym packages as usual.
https://drive.google.com/open?id=1y3jrh ... Cv-gKvn_ek
Wait, they are uninstallable, since we don't have xiccd (yet). Let me backport that.
OK, here's xiccd. Install that deb for your architecture first.
https://drive.google.com/open?id=1q7V_H ... KNiu4UoxGi
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 12:16 am
by entropyfoe
OK, I am impressed.
Downloaded 64 nit, the md5 is good. A couple minutes to get it on an old USB 2 stick. It booted with the option toram. Everything worked after the sound card was selected. So, I installed to my 4th test partition, I think a window popped up during the install like it was automounting the drives. I closed it and proceeded.
Installed as normal. I rebooted, went into MX 18.3, and did the update-grub thing. Booted into the MX-19 beta1.
Selected the sound card. Sound works. Wired eth0 works. Enabled the data drive with disk manager, set wallpaper. synaptic installed 129 packages including dependencies.
Installed the nvidia driver with the MX tool. Got the 418.74. Rebooted normally, driver is in use. The machine boots to about 520MB of RAM.
Suspend and wake works, 3 second sound resumes, 7 sec to the full system is back.
Earlier comments were about open root thunar here. That function seems to work here on folders.
Also, catfish works finding files fast.
Hmm, samba seems not to be working. This is one of the MX magical OTB things that usually just works, to my amazement, my windows machine just shows up, and files area accessible with authentication.But in this beta, the windows machine is not showing up. samba is installed, and the configuration does not show a way to find the network shares on the Win 7 machine.
I just did 4 synaptic updates, and got this error message at completion
Code: Select all
E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
So far very fast and stable, needs more testing and messing about. The samba- would like to get it working, I use that often.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 1:11 am
by JayM
1. Frugal_static installation worked with no problems.
2. The desktop's display was garbled after booting then auto-logging in as demo the very first time but it cleared up in a few seconds except that the panel looks partially white like this:
Changing themes in Settings/Appearance, enabling a compositor in MX Tweak, or doing anything in Panel Preferences didn't fix it, but logging out and back in did:
After a restart I had the garbling for just a fraction of a second, then it went to a dark screen with the (normal looking) panel, then the desktop wallpaper and conky loaded and everything looks fine. I rebooted again a few minutes later and there was no garbling at all.
3. Development/Icon Browser is slow to load icons. It takes over 10 seconds. My past experience with a frugal_static installation of MX 18.3 was that everything ran as fast as on an installed system so I don't know what's happening here. Maybe it has something to do with my system and the recent CPU upgrade? I did underclock the new CPU from 2.8GHz to 2.6GHz and also lowered the CPU voltage by two "notches" so it would run cooler. I haven't had any stability issues so far in my installed MX 18.3 though. Or maybe that app is just slow?
4. I can't duplicate any of the issues that others are reporting. All of the MX Tools I've tested launch OK, and I can open a root Thunar wherever I like. Firefix, GIMP, the updater works, and many other apps that I've tested all open.
5. I saved my testing notes and QSI info in Documents and my two screencaps in Pictures within Demo's home directory thinking they'd be available in my frugal partition later when I booted back into 18.3 but they were nowhere to be found. They weren't in Live-usb-storage/demo/ on the USB either. I had to boot back into 19b1 and copy/paste them into /media/jay/antiX-Frugal/Live-usb-storage/demo/ to make them available in 18. I wonder where Demo's home directory is? Within the squashfs? Again this seems different from my previous experience of an MX-18 frugal installation.
Code: Select all
System: Host: mx1 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19beta-1_x64 patito feo August 25 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASRock model: A780GM-LE serial: <filter>
BIOS: American Megatrends v: P1.50 date: 05/25/2010
CPU: Topology: Quad Core model: AMD Phenom II X4 925 bits: 64 type: MCP arch: K10
family: 10 (16) model-id: 4 stepping: 2 microcode: 10000DB L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 20755
Speed: 800 MHz min/max: 800/2600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 1600
Vulnerabilities: Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: AMD RS780 [Radeon HD 3200] vendor: ASRock driver: radeon v: kernel
bus ID: 01:05.0 chip ID: 1002:9610
Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1280x1024~60Hz
OpenGL: renderer: AMD RS780 (DRM 2.50.0 / 4.19.0-5-amd64 LLVM 7.0.1)
v: 3.3 Mesa 18.3.6 compat-v: 3.0 direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: ASRock driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock
driver: r8169 v: kernel port: e800 bus ID: 02:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.03 TiB used: 3.45 GiB (0.3%)
ID-1: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 61.3 scheme: MBR
ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC43
ID-3: /dev/sdc type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
Partition: ID-1: / raw size: N/A size: 7.81 GiB used: 41.4 MiB (0.5%) fs: overlay
source: ERR-102
Sensors: Message: No sensors data was found. Is sensors configured?
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 202 Uptime: 3m Memory: 7.55 GiB used: 510.0 MiB (6.6%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
running in: quick-system-in inxi: 3.0.33
Re: MX-19 Beta 1 Feedback (frugal-persist woes?)
Posted: Tue Aug 27, 2019 1:43 am
by baldyeti
fehlix wrote: Mon Aug 26, 2019 8:00 pm
The frugal-directory is correctly named: "/antiX-Frugal-4.19.0-5-amd64".
The created grub.entry shall work if you copy it into an existing grub-install under /boot/grub/custom.cfg,
You're absolutely right: i had copied /antiX-Frugal-4.19.0-5-amd64/boot/grub/grub.cfg instead of /antiX-Frugal-4.19.0-5-amd64/grub.entry
Working well now, persistence and all.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 3:11 am
by rpcm
Just found out about MX recently and wanted to try out XFCE 4.14, so I'm writing this from the MX-19 Beta! So far things are running
very well. Nice work dev team! Also, it is great to see another non-systemd distro, although I am not completely opposed to systemd, I am glad there are options out there.
I did notice a small quirk when booting into the system using full disk encryption. If you have a very long passphrase, it goes outside the display box. Other distros handle this better and hide any input that goes outside the box. Here's a photo for reference:
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 3:24 am
by JayM
MX-18 does that too. I just ignore it. But if it's something that can be changed or tweaked to make MX look nicer this is a good time to suggest it.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 3:31 am
by AK-47
I've seen this too, not sure how easy it would be to fix that. Another option is to open MX Boot Options, select the Tribar theme and you'll be sorted.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 3:57 am
by JayM
If it works in other boot themes maybe the default one can be modified to hide overflow characters? I wouldn't have the slightest idea how to go about doing that though.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 4:22 am
by Dede
Root Terminal disappeared?
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 4:28 am
by asqwerth
Dede wrote: Tue Aug 27, 2019 4:22 am
Root Terminal disappeared?
I've never encountered this problem at all, and I've tried all the early alphas.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 5:00 am
by Dede
asqwerth wrote: Tue Aug 27, 2019 4:28 am
Dede wrote: Tue Aug 27, 2019 4:22 am
Root Terminal disappeared?
I've never encountered this problem at all, and I've tried all the early alphas.
I do not have it...
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 5:57 am
by davemx
1. About Me/Mugshot demands my password, but won't accept it. My password is the same as the root password, so it's not accepting either.
2. I've made a change to the conky rc files which means that they only work if you have compositing enabled (xfce or compton), but if so, they work better! These should be the only "own_window_" lines. own_window_color should be deleted.
Code: Select all
own_window yes
own_window_transparent yes
own_window_type desktop
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
own_window_class Conky
3. A little thing, which may have also applied to previous versions but I only just discovered it. If you use "Intel Driver" instead of "modsetting driver", Google Earth Pro won't run properly. It runs after a fashion but the main window is frozen.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:01 am
by Eadwine Rose
Just installed the beta, the one thing I noticed is that even though I told the liveUSB the timezone, it didn't handle it like it should, it was 2 hours ahead IIRC. Only when I ticked that it should use LOCAL in mx time settings did it jump to the right time. That is the only thing I saw so far that was wonky, but easily sorted. I rebooted back into 18.3 right after the install, just to see that it was still there
I am such a wuss.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:03 am
by fladd
fehlix wrote: Mon Aug 26, 2019 6:01 pm
After having enabled the new screensaver/locker combo both the keyboard shortcut "Ctrl-Alt-Del" and the Lockicon in the Whisker menu will work.
Yes, confirmed.
fehlix wrote: Mon Aug 26, 2019 6:01 pm
Note xflock4 command will call the new Screensaver/Locker.
Not here (tested in VM).
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:13 am
by chrispop99
davemx wrote: Tue Aug 27, 2019 5:57 am
1. About Me/Mugshot demands my password, but won't accept it. My password is the same as the root password, so it's not accepting either.
I tested this, and it's not asking for any password in my case.
Chris
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:23 am
by Jerry3904
2. I've made a change to the conky rc files which means that they only work if you have compositing enabled (xfce or compton), but if so, they work better! These should be the only "own_window_" lines. own_window_color should be deleted.
CODE: SELECT ALL
own_window yes
own_window_transparent yes
own_window_type desktop
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
own_window_class Conky
Thanks for the suggestion. In MX-19 compositing is enabled by default, so that should be no problem.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:27 am
by mcury
I'm getting errors during codecs install, first installed nvidia driver, which worked.
Performed a reboot, installed the codecs and when it was around 99% (Fix missing dependencies), it presented me an error: Error running 'apt-get -fm install' command.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:33 am
by Jerry3904
Not seeing that here. Maybe try a second reboot (which nvidia sometimes requires) and try again; if it continues, paste back Quick System Info.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:40 am
by fehlix
fladd wrote: Tue Aug 27, 2019 6:03 am
fehlix wrote: Mon Aug 26, 2019 6:01 pm
Note xflock4 command will call the new Screensaver/Locker.
Not here (tested in VM).
Let's see what's different. Do run this from terminal command line:
the output shall be something like this:
Code: Select all
sh -x /usr/bin/xflock4
+ xfconf-query -c xfce4-session -p /general/LockCommand
+ LOCK_CMD=
+ [ ! -z ]
+ [ ! -z xfce4-screensaver-command --lock ]
+ xfce4-screensaver-command --lock
+ exit
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:41 am
by mcury
Tried a second reboot, but got same error, follows Quick System Info:
Code: Select all
System: Host: mx-beta Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19beta-1_x64 patito feo August 25 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASUSTeK model: H170 PRO GAMING v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 3805 date: 05/16/2018
CPU: Topology: Quad Core model: Intel Core i7-7700 bits: 64 type: MT MCP arch: Kaby Lake
family: 6 model-id: 9E (158) stepping: 9 microcode: B4 L2 cache: 8192 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57600
Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 801 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800
Vulnerabilities: Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI driver: nvidia
v: 418.74 bus ID: 01:00.0 chip ID: 10de:1c82
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74
direct render: Yes
Audio: Device-1: Intel Sunrise Point-H HD Audio
vendor: ASUSTeK 100 Series/C230 Series Family driver: snd_hda_intel v: kernel
bus ID: 00:1f.3 chip ID: 8086:a170
Device-2: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k port: f000
bus ID: 00:1f.6 chip ID: 8086:15b8
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.13 TiB used: 5.73 GiB (0.5%)
ID-1: /dev/sda vendor: Corsair model: Neutron GTX SSD size: 223.57 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: M311 scheme: GPT
ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC43 scheme: GPT
Partition: ID-1: / raw size: 31.25 GiB size: 30.63 GiB (98.03%) used: 5.71 GiB (18.6%) fs: ext4
dev: /dev/sda8
ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda9
Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 30 C
Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 35%
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://sft.if.usp.br/mx-workspace/antix//buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://sft.if.usp.br/mx-workspace/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 238 Uptime: 1m Memory: 15.61 GiB used: 824.5 MiB (5.2%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
running in: quick-system-in inxi: 3.0.33
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 6:49 am
by richb
Compiz update:
Disabled compositing and set vBlank to xrender. I installed all the Compiz packages including emerald. I started Compiz with the fusion icon. Compiz works well.
There is the same glitch with the Simple Compiz Configurator. All functions work except setting the edges, They can be set in the full Compiz configuration application but harder to find and the indvidual "effects" are in different places.
Setting vBlank in the Compiz Configuration app without setting vBlank to xrender with MX Tweak did not work this time.
Bottom line is that a working Compiz can be achieved in MX 19.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:17 am
by asqwerth
mcury wrote: Tue Aug 27, 2019 6:41 am
Tried a second reboot, but got same error, follows Quick System Info:
Code: Select all
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://sft.if.usp.br/mx-workspace/antix//buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://sft.if.usp.br/mx-workspace/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Maybe set a different mirror for MX Repos from MX Repo Manager, and then
sudo apt update
again?
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:21 am
by Gerson
timkb4cq wrote: Mon Aug 26, 2019 6:45 pm
Gerson wrote: Mon Aug 26, 2019 2:12 pm
... I just hope to have Openastro back in the repository.
You got it. The new version works well.
Thank you, I've seen it and installed it, it works perfect.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:25 am
by mcury
asqwerth wrote: Tue Aug 27, 2019 7:17 am
mcury wrote: Tue Aug 27, 2019 6:41 am
Tried a second reboot, but got same error, follows Quick System Info:
Code: Select all
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://sft.if.usp.br/mx-workspace/antix//buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://sft.if.usp.br/mx-workspace/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Maybe set a different mirror for MX Repos from MX Repo Manager, and then
sudo apt update
again?
Changed the repo, tried LA, tried Anycast, tried a few nearest to my location, after changing the repo, I went to terminal and set sudo apt update.
But still, I'm getting the same error when installing codecs.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:34 am
by dolphin_oracle
mcury wrote: Tue Aug 27, 2019 7:25 am
asqwerth wrote: Tue Aug 27, 2019 7:17 am
mcury wrote: Tue Aug 27, 2019 6:41 am
Tried a second reboot, but got same error, follows Quick System Info:
Code: Select all
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://sft.if.usp.br/mx-workspace/antix//buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://sft.if.usp.br/mx-workspace/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Maybe set a different mirror for MX Repos from MX Repo Manager, and then
sudo apt update
again?
Changed the repo, tried LA, tried Anycast, tried a few nearest to my location, after changing the repo, I went to terminal and set sudo apt update.
But still, I'm getting the same error when installing codecs.
can you run from the terminal and provide the output please?
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:37 am
by mcury
dolphin_oracle wrote: Tue Aug 27, 2019 7:34 am
mcury wrote: Tue Aug 27, 2019 7:25 am
asqwerth wrote: Tue Aug 27, 2019 7:17 am
Maybe set a different mirror for MX Repos from MX Repo Manager, and then
sudo apt update
again?
Changed the repo, tried LA, tried Anycast, tried a few nearest to my location, after changing the repo, I went to terminal and set sudo apt update.
But still, I'm getting the same error when installing codecs.
can you run from the terminal and provide the output please?
Follows the output requested:
Code: Select all
chicralla@mx-beta:~
$ sudo mx-codecs
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Program Version: 19.8
"mktemp -d"
exit code: 0
"dpkg --print-architecture"
exit code: 0
"grep VERSION= /etc/os-release | grep -Eo [a-z]+ "
exit code: 0
"wget -qO- http://deb-multimedia.org/dists/buster/main/binary-amd64/Packages.gz | zgrep ^Filename | grep libdvdcss2 | awk '{print $2}'"
exit code: 0
"wget -q http://deb-multimedia.org/pool/main/libd/libdvdcss/libdvdcss2_1.4.2-dmo1_amd64.deb"
exit code: 0
"wget -qO- http://deb-multimedia.org/dists/buster/non-free/binary-amd64/Packages.gz | zgrep ^Filename | grep w.*codecs | awk '{print $2}'"
exit code: 0
"wget -q http://deb-multimedia.org/pool/non-free/w/w64codecs/w64codecs_20071007-dmo2_amd64.deb"
exit code: 0
"wget -qO- http://deb-multimedia.org/dists/buster/main/binary-amd64/Packages.gz | zgrep ^Filename | grep libtxc-dxtn0 | awk '{print $2}'"
exit code: 0
"wget -q http://deb-multimedia.org/pool/main/libt/libtxc-dxtn/libtxc-dxtn0_1.0.1-dmo3_amd64.deb"
exit code: 0
"wget -qO- http://deb-multimedia.org/dists/buster/main/binary-i386/Packages.gz | zgrep ^Filename | grep libtxc-dxtn0 | awk '{print $2}'"
exit code: 0
"wget -q http://deb-multimedia.org/pool/main/libt/libtxc-dxtn/libtxc-dxtn0_1.0.1-dmo3_i386.deb"
exit code: 0
"dpkg --print-architecture"
exit code: 0
filelist ("libdvdcss2_1.4.2-dmo1_amd64.deb", "libtxc-dxtn0_1.0.1-dmo3_amd64.deb", "libtxc-dxtn0_1.0.1-dmo3_i386.deb", "w64codecs_20071007-dmo2_amd64.deb")
file "./libdvdcss2_1.4.2-dmo1_amd64.deb ./libtxc-dxtn0_1.0.1-dmo3_amd64.deb ./libtxc-dxtn0_1.0.1-dmo3_i386.deb ./w64codecs_20071007-dmo2_amd64.deb "
"dpkg --remove libtxc-dxtn-s2tc:amd64"
exit code: 0
"dpkg --remove libtxc-dxtn-s2tc:i386"
exit code: 0
"dpkg -i ./libdvdcss2_1.4.2-dmo1_amd64.deb ./libtxc-dxtn0_1.0.1-dmo3_amd64.deb ./libtxc-dxtn0_1.0.1-dmo3_i386.deb ./w64codecs_20071007-dmo2_amd64.deb "
exit code: 0
"apt-get -f install"
exit code: 100
chicralla@mx-beta:~
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:38 am
by Paul..
Dede wrote: Tue Aug 27, 2019 4:22 am
Root Terminal disappeared?
Please elaborate. Your comment as it appears is not helpful to developers without more details.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:41 am
by dolphin_oracle
mcury wrote: Tue Aug 27, 2019 7:37 am
dolphin_oracle wrote: Tue Aug 27, 2019 7:34 am
mcury wrote: Tue Aug 27, 2019 7:25 am
Changed the repo, tried LA, tried Anycast, tried a few nearest to my location, after changing the repo, I went to terminal and set sudo apt update.
But still, I'm getting the same error when installing codecs.
can you run from the terminal and provide the output please?
Follows the output requested:
chicralla@mx-beta:~
$ sudo mx-codecs
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Program Version: 19.8
"mktemp -d"
exit code: 0
"dpkg --print-architecture"
exit code: 0
"grep VERSION= /etc/os-release | grep -Eo [a-z]+ "
exit code: 0
"wget -qO-
http://deb-multimedia.org/dists/buster/ ... ackages.gz | zgrep ^Filename | grep libdvdcss2 | awk '{print $2}'"
exit code: 0
"wget -q
http://deb-multimedia.org/pool/main/lib ... _amd64.deb"
exit code: 0
"wget -qO-
http://deb-multimedia.org/dists/buster/ ... ackages.gz | zgrep ^Filename | grep w.*codecs | awk '{print $2}'"
exit code: 0
"wget -q
http://deb-multimedia.org/pool/non-free ... _amd64.deb"
exit code: 0
"wget -qO-
http://deb-multimedia.org/dists/buster/ ... ackages.gz | zgrep ^Filename | grep libtxc-dxtn0 | awk '{print $2}'"
exit code: 0
"wget -q
http://deb-multimedia.org/pool/main/lib ... _amd64.deb"
exit code: 0
"wget -qO-
http://deb-multimedia.org/dists/buster/ ... ackages.gz | zgrep ^Filename | grep libtxc-dxtn0 | awk '{print $2}'"
exit code: 0
"wget -q
http://deb-multimedia.org/pool/main/lib ... 3_i386.deb"
exit code: 0
"dpkg --print-architecture"
exit code: 0
filelist ("libdvdcss2_1.4.2-dmo1_amd64.deb", "libtxc-dxtn0_1.0.1-dmo3_amd64.deb", "libtxc-dxtn0_1.0.1-dmo3_i386.deb", "w64codecs_20071007-dmo2_amd64.deb")
file "./libdvdcss2_1.4.2-dmo1_amd64.deb ./libtxc-dxtn0_1.0.1-dmo3_amd64.deb ./libtxc-dxtn0_1.0.1-dmo3_i386.deb ./w64codecs_20071007-dmo2_amd64.deb "
"dpkg --remove libtxc-dxtn-s2tc:amd64"
exit code: 0
"dpkg --remove libtxc-dxtn-s2tc:i386"
exit code: 0
"dpkg -i ./libdvdcss2_1.4.2-dmo1_amd64.deb ./libtxc-dxtn0_1.0.1-dmo3_amd64.deb ./libtxc-dxtn0_1.0.1-dmo3_i386.deb ./w64codecs_20071007-dmo2_amd64.deb "
exit code: 0
"apt-get -f install"
exit code: 100
chicralla@mx-beta:~
thank you. now run
and post any output please.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:42 am
by mcury
dolphin_oracle wrote: Tue Aug 27, 2019 7:41 am
thank you. now run
and post any output please.
Output:
Code: Select all
chicralla@mx-beta:~
$ sudo apt-get install -f
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
1 pacotes não totalmente instalados ou removidos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
Configurando nvidia-persistenced (418.56-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: erro ao processar o pacote nvidia-persistenced (--configure):
o subprocesso instalado, do pacote nvidia-persistenced, o script post-installation retornou erro do status de saída 1
Erros foram encontrados durante o processamento de:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
chicralla@mx-beta:~
$
Checked syslog and found:
Code: Select all
chicralla@mx-beta:~
$ sudo cat /var/log/syslog | grep nvidia-per
Aug 27 06:25:30 mx-beta nvidia-persistenced: Started (29782)
Aug 27 06:25:30 mx-beta nvidia-persistenced: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory
Aug 27 06:25:30 mx-beta nvidia-persistenced: Shutdown (29782)
Aug 27 06:28:11 mx-beta nvidia-persistenced: Failed to lock PID file: Resource temporarily unavailable
Aug 27 06:28:11 mx-beta nvidia-persistenced: Shutdown (3993)
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:49 am
by dolphin_oracle
mcury wrote: Tue Aug 27, 2019 7:42 am
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
Configurando nvidia-persistenced (418.56-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: erro ao processar o pacote nvidia-persistenced (--configure):
o subprocesso instalado, do pacote nvidia-persistenced, o script post-installation retornou erro do status de saída 1
Erros foram encontrados durante o processamento de:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
chicralla@mx-beta:~
$
Checked syslog and found:
chicralla@mx-beta:~
$ sudo cat /var/log/syslog | grep nvidia-per
Aug 27 06:25:30 mx-beta nvidia-persistenced: Started (29782)
Aug 27 06:25:30 mx-beta nvidia-persistenced: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory
Aug 27 06:25:30 mx-beta nvidia-persistenced: Shutdown (29782)
Aug 27 06:28:11 mx-beta nvidia-persistenced: Failed to lock PID file: Resource temporarily unavailable
Aug 27 06:28:11 mx-beta nvidia-persistenced: Shutdown (3993)
so the error is not with mx-codecs. the error is with the nvidia-persistenced setup. Looks like its missing some pieces. I suggest reinstalling.
Code: Select all
sudo apt-get install --reinstall nvidia-persistenced
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:52 am
by mcury
dolphin_oracle wrote: Tue Aug 27, 2019 7:49 am
mcury wrote: Tue Aug 27, 2019 7:42 am
Code: Select all
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
Configurando nvidia-persistenced (418.56-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: erro ao processar o pacote nvidia-persistenced (--configure):
o subprocesso instalado, do pacote nvidia-persistenced, o script post-installation retornou erro do status de saída 1
Erros foram encontrados durante o processamento de:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
chicralla@mx-beta:~
$
Checked syslog and found:
Code: Select all
chicralla@mx-beta:~
$ sudo cat /var/log/syslog | grep nvidia-per
Aug 27 06:25:30 mx-beta nvidia-persistenced: Started (29782)
Aug 27 06:25:30 mx-beta nvidia-persistenced: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory
Aug 27 06:25:30 mx-beta nvidia-persistenced: Shutdown (29782)
Aug 27 06:28:11 mx-beta nvidia-persistenced: Failed to lock PID file: Resource temporarily unavailable
Aug 27 06:28:11 mx-beta nvidia-persistenced: Shutdown (3993)
[/quote]
so the error is not with mx-codecs. the error is with the nvidia-persistenced setup. Looks like its missing some pieces. I suggest reinstalling.
Code: Select all
sudo apt-get install --reinstall nvidia-persistenced
No joy
Code: Select all
chicralla@mx-beta:~
$ sudo apt-get install --reinstall nvidia-persistenced
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
0 pacotes atualizados, 0 pacotes novos instalados, 1 reinstalados, 0 a serem removidos e 0 não atualizados.
1 pacotes não totalmente instalados ou removidos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
E: Internal Error, No file name for nvidia-persistenced:amd64
chicralla@mx-beta:~
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:57 am
by dolphin_oracle
maybe I had a typo.
Code: Select all
sudo apt-get update && sudo apt-get install --reinstall nvidia-persistenced
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:06 am
by mcury
dolphin_oracle wrote: Tue Aug 27, 2019 7:57 am
maybe I had a typo.
Code: Select all
sudo apt-get update && sudo apt-get install --reinstall nvidia-persistenced
I have a 18.3 installation which works perfectly
Code: Select all
$ sudo apt-get update && sudo apt-get install --reinstall nvidia-persistenced
Atingido:1 http://deb.debian.org/debian buster-updates InRelease
Atingido:2 http://deb.debian.org/debian buster InRelease
Atingido:3 http://mirror.ufam.edu.br/mx/antix//buster buster InRelease
Atingido:4 http://deb.debian.org/debian-security buster/updates InRelease
Atingido:5 http://mirror.ufam.edu.br/mx/mx/repo buster InRelease
Lendo listas de pacotes... Pronto
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libegl-mesa0:i386
libegl-nvidia0:i386 libegl1:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgbm1:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libgles-nvidia1:i386
libgles-nvidia2:i386 libgles1:i386 libgles2:i386 libglvnd0:i386 libglx-mesa0:i386 libglx-nvidia0:i386 libglx0:i386 libllvm7:i386 libnvidia-cbl libnvidia-eglcore:i386
libnvidia-glcore:i386 libnvidia-glvkspirv libnvidia-glvkspirv:i386 libnvidia-rtcore libopengl0:i386 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libtinfo6:i386
libvulkan1:i386 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386
libxcb-present0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxshmfence1:i386
libxxf86vm1:i386 nvidia-egl-icd:i386 zlib1g:i386
Utilize 'sudo apt autoremove' para os remover.
0 pacotes atualizados, 0 pacotes novos instalados, 1 reinstalados, 0 a serem removidos e 0 não atualizados.
1 pacotes não totalmente instalados ou removidos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
E: Internal Error, No file name for nvidia-persistenced:amd64
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:10 am
by Eadwine Rose
Can you please put code output into code tags? It's the thing that looks like </>
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:15 am
by mcury
Eadwine Rose wrote: Tue Aug 27, 2019 8:10 am
Can you please put code output into code tags? It's the thing that looks like </>
Sorry, new to the forum, I'll use the code tags.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:16 am
by Eadwine Rose
It's alright.. it helps with readability :)
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:21 am
by Paul..
Error exiting from Live USB after completed HDD installation...
Exit-error.JPG
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:28 am
by dolphin_oracle
mcury wrote: Tue Aug 27, 2019 8:06 am
dolphin_oracle wrote: Tue Aug 27, 2019 7:57 am
maybe I had a typo.
Code: Select all
sudo apt-get update && sudo apt-get install --reinstall nvidia-persistenced
I have a 18.3 installation which works perfectly
Code: Select all
$ sudo apt-get update && sudo apt-get install --reinstall nvidia-persistenced
Atingido:1 http://deb.debian.org/debian buster-updates InRelease
Atingido:2 http://deb.debian.org/debian buster InRelease
Atingido:3 http://mirror.ufam.edu.br/mx/antix//buster buster InRelease
Atingido:4 http://deb.debian.org/debian-security buster/updates InRelease
Atingido:5 http://mirror.ufam.edu.br/mx/mx/repo buster InRelease
Lendo listas de pacotes... Pronto
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libegl-mesa0:i386
libegl-nvidia0:i386 libegl1:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgbm1:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libgles-nvidia1:i386
libgles-nvidia2:i386 libgles1:i386 libgles2:i386 libglvnd0:i386 libglx-mesa0:i386 libglx-nvidia0:i386 libglx0:i386 libllvm7:i386 libnvidia-cbl libnvidia-eglcore:i386
libnvidia-glcore:i386 libnvidia-glvkspirv libnvidia-glvkspirv:i386 libnvidia-rtcore libopengl0:i386 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libtinfo6:i386
libvulkan1:i386 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386
libxcb-present0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxshmfence1:i386
libxxf86vm1:i386 nvidia-egl-icd:i386 zlib1g:i386
Utilize 'sudo apt autoremove' para os remover.
0 pacotes atualizados, 0 pacotes novos instalados, 1 reinstalados, 0 a serem removidos e 0 não atualizados.
1 pacotes não totalmente instalados ou removidos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
E: Internal Error, No file name for nvidia-persistenced:amd64
well something has gone wrong with the nvidia installation, and you have a partially configured package that apt can't seem to find. which is weird for sure.
did you install from teh installer tool or use something like sgfxi?
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:31 am
by mcury
dolphin_oracle wrote: Tue Aug 27, 2019 8:28 am
mcury wrote: Tue Aug 27, 2019 8:06 am
dolphin_oracle wrote: Tue Aug 27, 2019 7:57 am
maybe I had a typo.
Code: Select all
sudo apt-get update && sudo apt-get install --reinstall nvidia-persistenced
I have a 18.3 installation which works perfectly
Code: Select all
$ sudo apt-get update && sudo apt-get install --reinstall nvidia-persistenced
Atingido:1 http://deb.debian.org/debian buster-updates InRelease
Atingido:2 http://deb.debian.org/debian buster InRelease
Atingido:3 http://mirror.ufam.edu.br/mx/antix//buster buster InRelease
Atingido:4 http://deb.debian.org/debian-security buster/updates InRelease
Atingido:5 http://mirror.ufam.edu.br/mx/mx/repo buster InRelease
Lendo listas de pacotes... Pronto
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libegl-mesa0:i386
libegl-nvidia0:i386 libegl1:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgbm1:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libgles-nvidia1:i386
libgles-nvidia2:i386 libgles1:i386 libgles2:i386 libglvnd0:i386 libglx-mesa0:i386 libglx-nvidia0:i386 libglx0:i386 libllvm7:i386 libnvidia-cbl libnvidia-eglcore:i386
libnvidia-glcore:i386 libnvidia-glvkspirv libnvidia-glvkspirv:i386 libnvidia-rtcore libopengl0:i386 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libtinfo6:i386
libvulkan1:i386 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386
libxcb-present0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxshmfence1:i386
libxxf86vm1:i386 nvidia-egl-icd:i386 zlib1g:i386
Utilize 'sudo apt autoremove' para os remover.
0 pacotes atualizados, 0 pacotes novos instalados, 1 reinstalados, 0 a serem removidos e 0 não atualizados.
1 pacotes não totalmente instalados ou removidos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
E: Internal Error, No file name for nvidia-persistenced:amd64
well something has gone wrong with the nvidia installation, and you have a partially configured package that apt can't seem to find. which is weird for sure.
did you install from teh installer tool or use something like sgfxi?
I have installed through mx-tools.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:32 am
by Jerry3904
@Paul: Seems like I've seen that in the past...
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:34 am
by Paul..
Yes, it is odd...may be a timing issue (as noted in other posts)...with nvme, this machine is very quick.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:37 am
by NGIB
Just 2 quick things. Settings menu did not scroll. And the other issue is trying to uninstall Firefox. When you select Firefox to uninstall it then marks Firefox ESR, if you unmark Firefox ESR it marks Epiphany, if you unmark Epiphany it marks Konqueror. I just want to uninstall Firefox and use my browser of choice which is Palemoon...
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:39 am
by dolphin_oracle
NGIB wrote: Tue Aug 27, 2019 8:37 am
Just 2 quick things. Settings menu did not scroll. And the other issue is trying to uninstall Firefox. When you select Firefox to uninstall it then marks Firefox ESR, if you unmark Firefox ESR it marks Epiphany, if you unmark Epiphany it marks Konqueror. I just want to uninstall Firefox and use my browser of choice which is Palemoon...
If I remember correctly, the libreoffice help files require a browser to be installed. so if you want to remove one of the dependency browsers, you need to remove the libreoffice-help.
irritating I know.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:41 am
by NGIB
I had already installed Palemoon, maybe it's not "seen"? Also, I installed additional theme engines and they did not show up in the window manager...
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:41 am
by dolphin_oracle
mcury wrote: Tue Aug 27, 2019 8:31 am
dolphin_oracle wrote: Tue Aug 27, 2019 8:28 am
mcury wrote: Tue Aug 27, 2019 8:06 am
I have a 18.3 installation which works perfectly
Code: Select all
$ sudo apt-get update && sudo apt-get install --reinstall nvidia-persistenced
Atingido:1 http://deb.debian.org/debian buster-updates InRelease
Atingido:2 http://deb.debian.org/debian buster InRelease
Atingido:3 http://mirror.ufam.edu.br/mx/antix//buster buster InRelease
Atingido:4 http://deb.debian.org/debian-security buster/updates InRelease
Atingido:5 http://mirror.ufam.edu.br/mx/mx/repo buster InRelease
Lendo listas de pacotes... Pronto
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libegl-mesa0:i386
libegl-nvidia0:i386 libegl1:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgbm1:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libgles-nvidia1:i386
libgles-nvidia2:i386 libgles1:i386 libgles2:i386 libglvnd0:i386 libglx-mesa0:i386 libglx-nvidia0:i386 libglx0:i386 libllvm7:i386 libnvidia-cbl libnvidia-eglcore:i386
libnvidia-glcore:i386 libnvidia-glvkspirv libnvidia-glvkspirv:i386 libnvidia-rtcore libopengl0:i386 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libtinfo6:i386
libvulkan1:i386 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386
libxcb-present0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxshmfence1:i386
libxxf86vm1:i386 nvidia-egl-icd:i386 zlib1g:i386
Utilize 'sudo apt autoremove' para os remover.
0 pacotes atualizados, 0 pacotes novos instalados, 1 reinstalados, 0 a serem removidos e 0 não atualizados.
1 pacotes não totalmente instalados ou removidos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
E: Internal Error, No file name for nvidia-persistenced:amd64
well something has gone wrong with the nvidia installation, and you have a partially configured package that apt can't seem to find. which is weird for sure.
did you install from teh installer tool or use something like sgfxi?
I have installed through mx-tools.
something is wrong, your autoremoves is full of nvidia stuff.
I suggest removing the nvidia drivers, rebooting, and reinstalling.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:42 am
by caprea
@dolphin_oracle
I got the same error like mcury during nvidia-driver installation and after, with ddm-mx
Looks like entropyfoe, too.
viewtopic.php?p=523443#p523443
Btw, also on antiX19-beta.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:42 am
by dolphin_oracle
NGIB wrote: Tue Aug 27, 2019 8:41 am
I had already installed Palemoon, maybe it's not "seen"? Also, I installed additional theme engines and they did not show up in the window manager...
its not a depend. libreoffice-help has really stupid depends. from the package info.
Code: Select all
dep: firefox-esr
Mozilla Firefox web browser - Extended Support Release (ESR)
or epiphany-browser
Intuitive GNOME web browser
or konqueror
advanced file manager, web browser and document viewer
or chromium
web browser
or firefox
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:43 am
by dolphin_oracle
caprea wrote: Tue Aug 27, 2019 8:42 am
@dolphin_oracle
I got the same error like mcury during nvidia-driver installation and after, with ddm-mx
Looks like entropyfoe, too.
viewtopic.php?p=523443#p523443
Btw, also on antiX19-beta.
I think we need the /var/log/ddm.log files. just attach them. there is something wrong there...might be a systemd thing.
f**kn nvidia is a moving target....
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:47 am
by mcury
dolphin_oracle wrote: Tue Aug 27, 2019 8:43 am
caprea wrote: Tue Aug 27, 2019 8:42 am
@dolphin_oracle
I got the same error like mcury during nvidia-driver installation and after, with ddm-mx
Looks like entropyfoe, too.
viewtopic.php?p=523443#p523443
Btw, also on antiX19-beta.
I think we need the /var/log/ddm.log files. just attach them. there is something wrong there...might be a systemd thing.
f**kn nvidia is a moving target....
As I've already messed with things here, I'll perform a clean OS installation, and install nvidia drivers again, then I'll attach the ddm.log.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:50 am
by caprea
Sorry, german.
Code: Select all
Sperrung wird hergestellt.....
===================================
Installiere Treiber für: nvidia
Start am (m/t/j): 08/27/2019 01:10:26
===================================
Aktualisiere Quellen mit apt-get update
Kandidat ist: 340.107-4
Installiert ist: (none)
Möchten Sie im MX Test Repo nach einer neueren Version suchen?
Ja oder nein?
1: Ja
2: Nein
Enter Number of selection
Ok...
Aktualisiere Quellen mit apt-get update
Installiere aktuelles nvidia-detect Paket
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
nvidia-detect ist schon die neueste Version (418.74-1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Kandidat ist: 340.107-4
Installiert ist: (none)
Kandidat ist: 340.107-4
Kandidat aus dem MX Test Repository ist: 340.107-4
Installiert ist: (none)
Treiber benötigt:nvidia-legacy-340xx-driver (340.107-4)
packages to install are nvidia-legacy-340xx-driver nvidia-settings-legacy-340xx nvidia-legacy-340xx-kernel-dkms nvidia-xconfig
Frontend:
Nvidia-Befehl = apt-get install --install-recommends --reinstall -y nvidia-legacy-340xx-driver nvidia-settings-legacy-340xx nvidia-legacy-340xx-kernel-dkms nvidia-xconfig
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
0 aktualisiert, 0 neu installiert, 3 erneut installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 777 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Holen:1 http://deb.debian.org/debian buster/main amd64 build-essential amd64 12.6 [7.576 B]
Holen:2 http://deb.debian.org/debian-security buster/updates/main amd64 linux-headers-4.19.0-5-amd64 amd64 4.19.37-5+deb10u2 [750 kB]
Holen:3 http://mxrepo.com/mx/repo buster/non-free amd64 firmware-linux-nonfree all 20190717-1~mx19+1 [18,9 kB]
Es wurden 777 kB in 1 s geholt (1.274 kB/s).
(Lese Datenbank ...
(Lese Datenbank ... 5%
(Lese Datenbank ... 10%
(Lese Datenbank ... 15%
(Lese Datenbank ... 20%
(Lese Datenbank ... 25%
(Lese Datenbank ... 30%
(Lese Datenbank ... 35%
(Lese Datenbank ... 40%
(Lese Datenbank ... 45%
(Lese Datenbank ... 50%
(Lese Datenbank ... 55%
(Lese Datenbank ... 60%
(Lese Datenbank ... 65%
(Lese Datenbank ... 70%
(Lese Datenbank ... 75%
(Lese Datenbank ... 80%
(Lese Datenbank ... 85%
(Lese Datenbank ... 90%
(Lese Datenbank ... 95%
(Lese Datenbank ... 100%
(Lese Datenbank ... 268225 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../build-essential_12.6_amd64.deb ...
Entpacken von build-essential (12.6) über (12.6) ...
Vorbereitung zum Entpacken von .../firmware-linux-nonfree_20190717-1~mx19+1_all.deb ...
Entpacken von firmware-linux-nonfree (20190717-1~mx19+1) über (20190717-1~mx19+1) ...
Vorbereitung zum Entpacken von .../linux-headers-4.19.0-5-amd64_4.19.37-5+deb10u2_amd64.deb ...
Entpacken von linux-headers-4.19.0-5-amd64 (4.19.37-5+deb10u2) über (4.19.37-5+deb10u2) ...
linux-headers-4.19.0-5-amd64 (4.19.37-5+deb10u2) wird eingerichtet ...
firmware-linux-nonfree (20190717-1~mx19+1) wird eingerichtet ...
build-essential (12.6) wird eingerichtet ...
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
Die folgenden zusätzlichen Pakete werden installiert:
glx-alternative-mesa glx-alternative-nvidia glx-diversions libbsd0:i386
libegl1-nvidia-legacy-340xx libegl1-nvidia-legacy-340xx:i386
libgl1-nvidia-legacy-340xx-glx libgl1-nvidia-legacy-340xx-glx:i386
libgles1-nvidia-legacy-340xx libgles1-nvidia-legacy-340xx:i386
libgles2-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx:i386
libnvidia-legacy-340xx-cfg1 libnvidia-legacy-340xx-cfg1:i386
libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-eglcore:i386
libnvidia-legacy-340xx-glcore libnvidia-legacy-340xx-glcore:i386
libnvidia-legacy-340xx-ml1 libx11-6:i386 libxau6:i386 libxcb1:i386
libxdmcp6:i386 libxext6:i386 nvidia-installer-cleanup nvidia-kernel-common
nvidia-legacy-340xx-alternative nvidia-legacy-340xx-driver-bin
nvidia-legacy-340xx-driver-libs nvidia-legacy-340xx-driver-libs:i386
nvidia-legacy-340xx-driver-libs-i386:i386 nvidia-legacy-340xx-kernel-support
nvidia-legacy-340xx-vdpau-driver nvidia-modprobe nvidia-persistenced
nvidia-support update-glx xserver-xorg-video-nvidia-legacy-340xx
Vorgeschlagene Pakete:
nvidia-driver
Die folgenden NEUEN Pakete werden installiert:
glx-alternative-mesa glx-alternative-nvidia glx-diversions libbsd0:i386
libegl1-nvidia-legacy-340xx libegl1-nvidia-legacy-340xx:i386
libgl1-nvidia-legacy-340xx-glx libgl1-nvidia-legacy-340xx-glx:i386
libgles1-nvidia-legacy-340xx libgles1-nvidia-legacy-340xx:i386
libgles2-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx:i386
libnvidia-legacy-340xx-cfg1 libnvidia-legacy-340xx-cfg1:i386
libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-eglcore:i386
libnvidia-legacy-340xx-glcore libnvidia-legacy-340xx-glcore:i386
libnvidia-legacy-340xx-ml1 libx11-6:i386 libxau6:i386 libxcb1:i386
libxdmcp6:i386 libxext6:i386 nvidia-installer-cleanup nvidia-kernel-common
nvidia-legacy-340xx-alternative nvidia-legacy-340xx-driver
nvidia-legacy-340xx-driver-bin nvidia-legacy-340xx-driver-libs
nvidia-legacy-340xx-driver-libs:i386
nvidia-legacy-340xx-driver-libs-i386:i386 nvidia-legacy-340xx-kernel-dkms
nvidia-legacy-340xx-kernel-support nvidia-legacy-340xx-vdpau-driver
nvidia-modprobe nvidia-persistenced nvidia-settings-legacy-340xx
nvidia-support nvidia-xconfig update-glx
xserver-xorg-video-nvidia-legacy-340xx
0 aktualisiert, 42 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 40,8 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 220 MB Plattenplatz zusätzlich benutzt.
Holen:1 http://deb.debian.org/debian buster/contrib amd64 update-glx amd64 1.0.0 [10,5 kB]
Holen:2 http://deb.debian.org/debian buster/contrib amd64 glx-alternative-mesa amd64 1.0.0 [9.592 B]
Holen:3 http://deb.debian.org/debian buster/contrib amd64 nvidia-installer-cleanup amd64 20151021+9 [19,2 kB]
Holen:4 http://deb.debian.org/debian buster/contrib amd64 glx-diversions amd64 1.0.0 [12,0 kB]
Holen:5 http://deb.debian.org/debian buster/contrib amd64 glx-alternative-nvidia amd64 1.0.0 [10,8 kB]
Holen:6 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-alternative amd64 340.107-4 [80,3 kB]
Holen:7 http://deb.debian.org/debian buster/non-free amd64 libnvidia-legacy-340xx-glcore amd64 340.107-4 [7.010 kB]
Holen:8 http://deb.debian.org/debian buster/contrib amd64 nvidia-support amd64 20151021+9 [20,0 kB]
Holen:9 http://deb.debian.org/debian buster/non-free amd64 libgl1-nvidia-legacy-340xx-glx amd64 340.107-4 [468 kB]
Holen:10 http://deb.debian.org/debian buster/non-free i386 libnvidia-legacy-340xx-glcore i386 340.107-4 [7.018 kB]
Holen:11 http://deb.debian.org/debian buster/main i386 libxau6 i386 1:1.0.8-1+b2 [20,3 kB]
Holen:12 http://deb.debian.org/debian buster/main i386 libbsd0 i386 0.9.1-2 [104 kB]
Holen:13 http://deb.debian.org/debian buster/main i386 libxdmcp6 i386 1:1.1.2-3 [26,7 kB]
Holen:14 http://deb.debian.org/debian buster/main i386 libxcb1 i386 1.13.1-2 [141 kB]
Holen:15 http://deb.debian.org/debian buster/main i386 libx11-6 i386 2:1.6.7-1 [778 kB]
Holen:16 http://deb.debian.org/debian buster/main i386 libxext6 i386 2:1.3.3-1+b2 [55,2 kB]
Holen:17 http://deb.debian.org/debian buster/non-free i386 libgl1-nvidia-legacy-340xx-glx i386 340.107-4 [451 kB]
Holen:18 http://deb.debian.org/debian buster/non-free amd64 libnvidia-legacy-340xx-eglcore amd64 340.107-4 [6.981 kB]
Holen:19 http://deb.debian.org/debian buster/non-free amd64 libegl1-nvidia-legacy-340xx amd64 340.107-4 [230 kB]
Holen:20 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-driver-libs amd64 340.107-4 [78,6 kB]
Holen:21 http://deb.debian.org/debian buster/non-free amd64 libnvidia-legacy-340xx-ml1 amd64 340.107-4 [359 kB]
Holen:22 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-driver-bin amd64 340.107-4 [160 kB]
Holen:23 http://deb.debian.org/debian buster/non-free amd64 xserver-xorg-video-nvidia-legacy-340xx amd64 340.107-4 [2.721 kB]
Holen:24 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-vdpau-driver amd64 340.107-4 [916 kB]
Holen:25 http://deb.debian.org/debian buster/contrib amd64 nvidia-kernel-common amd64 20151021+9 [10,8 kB]
Holen:26 http://deb.debian.org/debian buster/contrib amd64 nvidia-modprobe amd64 418.56-1 [19,2 kB]
Holen:27 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-kernel-support amd64 340.107-4 [79,4 kB]
Holen:28 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-kernel-dkms amd64 340.107-4 [3.977 kB]
Holen:29 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-driver amd64 340.107-4 [364 kB]
Holen:30 http://deb.debian.org/debian buster/non-free amd64 libnvidia-legacy-340xx-cfg1 amd64 340.107-4 [135 kB]
Holen:31 http://deb.debian.org/debian buster/contrib amd64 nvidia-persistenced amd64 418.56-1 [26,7 kB]
Holen:32 http://deb.debian.org/debian buster/contrib amd64 nvidia-settings-legacy-340xx amd64 340.107-2 [741 kB]
Holen:33 http://deb.debian.org/debian buster/contrib amd64 nvidia-xconfig amd64 418.56-1 [84,3 kB]
Holen:34 http://deb.debian.org/debian buster/non-free i386 libnvidia-legacy-340xx-eglcore i386 340.107-4 [6.846 kB]
Holen:35 http://deb.debian.org/debian buster/non-free i386 libegl1-nvidia-legacy-340xx i386 340.107-4 [202 kB]
Holen:36 http://deb.debian.org/debian buster/non-free amd64 libgles1-nvidia-legacy-340xx amd64 340.107-4 [94,3 kB]
Holen:37 http://deb.debian.org/debian buster/non-free i386 libgles1-nvidia-legacy-340xx i386 340.107-4 [93,4 kB]
Holen:38 http://deb.debian.org/debian buster/non-free i386 libgles2-nvidia-legacy-340xx i386 340.107-4 [96,2 kB]
Holen:39 http://deb.debian.org/debian buster/non-free amd64 libgles2-nvidia-legacy-340xx amd64 340.107-4 [96,8 kB]
Holen:40 http://deb.debian.org/debian buster/non-free i386 libnvidia-legacy-340xx-cfg1 i386 340.107-4 [135 kB]
Holen:41 http://deb.debian.org/debian buster/non-free i386 nvidia-legacy-340xx-driver-libs i386 340.107-4 [78,6 kB]
Holen:42 http://deb.debian.org/debian buster/non-free i386 nvidia-legacy-340xx-driver-libs-i386 i386 340.107-4 [78,5 kB]
Vorkonfiguration der Pakete ...
Es wurden 40,8 MB in 15 s geholt (2.683 kB/s).
Vormals nicht ausgewähltes Paket update-glx wird gewählt.
(Lese Datenbank ...
(Lese Datenbank ... 5%
(Lese Datenbank ... 10%
(Lese Datenbank ... 15%
(Lese Datenbank ... 20%
(Lese Datenbank ... 25%
(Lese Datenbank ... 30%
(Lese Datenbank ... 35%
(Lese Datenbank ... 40%
(Lese Datenbank ... 45%
(Lese Datenbank ... 50%
(Lese Datenbank ... 55%
(Lese Datenbank ... 60%
(Lese Datenbank ... 65%
(Lese Datenbank ... 70%
(Lese Datenbank ... 75%
(Lese Datenbank ... 80%
(Lese Datenbank ... 85%
(Lese Datenbank ... 90%
(Lese Datenbank ... 95%
(Lese Datenbank ... 100%
(Lese Datenbank ... 268225 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../update-glx_1.0.0_amd64.deb ...
Entpacken von update-glx (1.0.0) ...
Vormals nicht ausgewähltes Paket glx-alternative-mesa wird gewählt.
Vorbereitung zum Entpacken von .../glx-alternative-mesa_1.0.0_amd64.deb ...
Entpacken von glx-alternative-mesa (1.0.0) ...
Vormals nicht ausgewähltes Paket nvidia-installer-cleanup wird gewählt.
Vorbereitung zum Entpacken von .../nvidia-installer-cleanup_20151021+9_amd64.deb ...
Entpacken von nvidia-installer-cleanup (20151021+9) ...
nvidia-installer-cleanup (20151021+9) wird eingerichtet ...
Vormals nicht ausgewähltes Paket glx-diversions wird gewählt.
(Lese Datenbank ...
(Lese Datenbank ... 5%
(Lese Datenbank ... 10%
(Lese Datenbank ... 15%
(Lese Datenbank ... 20%
(Lese Datenbank ... 25%
(Lese Datenbank ... 30%
(Lese Datenbank ... 35%
(Lese Datenbank ... 40%
(Lese Datenbank ... 45%
(Lese Datenbank ... 50%
(Lese Datenbank ... 55%
(Lese Datenbank ... 60%
(Lese Datenbank ... 65%
(Lese Datenbank ... 70%
(Lese Datenbank ... 75%
(Lese Datenbank ... 80%
(Lese Datenbank ... 85%
(Lese Datenbank ... 90%
(Lese Datenbank ... 95%
(Lese Datenbank ... 100%
(Lese Datenbank ... 268325 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../00-glx-diversions_1.0.0_amd64.deb ...
Entpacken von glx-diversions (1.0.0) ...
Vormals nicht ausgewähltes Paket glx-alternative-nvidia wird gewählt.
Vorbereitung zum Entpacken von .../01-glx-alternative-nvidia_1.0.0_amd64.deb ...
Entpacken von glx-alternative-nvidia (1.0.0) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-alternative wird gewählt.
Vorbereitung zum Entpacken von .../02-nvidia-legacy-340xx-alternative_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-alternative (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-glcore:i386 wird gewählt.
Vorbereitung zum Entpacken von .../03-libnvidia-legacy-340xx-glcore_340.107-4_i386.deb ...
Entpacken von libnvidia-legacy-340xx-glcore:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-support wird gewählt.
Vorbereitung zum Entpacken von .../04-nvidia-support_20151021+9_amd64.deb ...
Entpacken von nvidia-support (20151021+9) ...
Vormals nicht ausgewähltes Paket libxau6:i386 wird gewählt.
Vorbereitung zum Entpacken von .../05-libxau6_1%3a1.0.8-1+b2_i386.deb ...
Entpacken von libxau6:i386 (1:1.0.8-1+b2) ...
Vormals nicht ausgewähltes Paket libbsd0:i386 wird gewählt.
Vorbereitung zum Entpacken von .../06-libbsd0_0.9.1-2_i386.deb ...
Entpacken von libbsd0:i386 (0.9.1-2) ...
Vormals nicht ausgewähltes Paket libxdmcp6:i386 wird gewählt.
Vorbereitung zum Entpacken von .../07-libxdmcp6_1%3a1.1.2-3_i386.deb ...
Entpacken von libxdmcp6:i386 (1:1.1.2-3) ...
Vormals nicht ausgewähltes Paket libxcb1:i386 wird gewählt.
Vorbereitung zum Entpacken von .../08-libxcb1_1.13.1-2_i386.deb ...
Entpacken von libxcb1:i386 (1.13.1-2) ...
Vormals nicht ausgewähltes Paket libx11-6:i386 wird gewählt.
Vorbereitung zum Entpacken von .../09-libx11-6_2%3a1.6.7-1_i386.deb ...
Entpacken von libx11-6:i386 (2:1.6.7-1) ...
Vormals nicht ausgewähltes Paket libxext6:i386 wird gewählt.
Vorbereitung zum Entpacken von .../10-libxext6_2%3a1.3.3-1+b2_i386.deb ...
Entpacken von libxext6:i386 (2:1.3.3-1+b2) ...
Vormals nicht ausgewähltes Paket libgl1-nvidia-legacy-340xx-glx:i386 wird gewählt.
Vorbereitung zum Entpacken von .../11-libgl1-nvidia-legacy-340xx-glx_340.107-4_i386.deb ...
Entpacken von libgl1-nvidia-legacy-340xx-glx:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-glcore:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../12-libnvidia-legacy-340xx-glcore_340.107-4_amd64.deb ...
Entpacken von libnvidia-legacy-340xx-glcore:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgl1-nvidia-legacy-340xx-glx:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../13-libgl1-nvidia-legacy-340xx-glx_340.107-4_amd64.deb ...
Entpacken von libgl1-nvidia-legacy-340xx-glx:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-eglcore:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../14-libnvidia-legacy-340xx-eglcore_340.107-4_amd64.deb ...
Entpacken von libnvidia-legacy-340xx-eglcore:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libegl1-nvidia-legacy-340xx:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../15-libegl1-nvidia-legacy-340xx_340.107-4_amd64.deb ...
Entpacken von libegl1-nvidia-legacy-340xx:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver-libs:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../16-nvidia-legacy-340xx-driver-libs_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-driver-libs:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-ml1:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../17-libnvidia-legacy-340xx-ml1_340.107-4_amd64.deb ...
Entpacken von libnvidia-legacy-340xx-ml1:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver-bin wird gewählt.
Vorbereitung zum Entpacken von .../18-nvidia-legacy-340xx-driver-bin_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-driver-bin (340.107-4) ...
Vormals nicht ausgewähltes Paket xserver-xorg-video-nvidia-legacy-340xx wird gewählt.
Vorbereitung zum Entpacken von .../19-xserver-xorg-video-nvidia-legacy-340xx_340.107-4_amd64.deb ...
Entpacken von xserver-xorg-video-nvidia-legacy-340xx (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-vdpau-driver:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../20-nvidia-legacy-340xx-vdpau-driver_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-vdpau-driver:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-kernel-common wird gewählt.
Vorbereitung zum Entpacken von .../21-nvidia-kernel-common_20151021+9_amd64.deb ...
Entpacken von nvidia-kernel-common (20151021+9) ...
Vormals nicht ausgewähltes Paket nvidia-modprobe wird gewählt.
Vorbereitung zum Entpacken von .../22-nvidia-modprobe_418.56-1_amd64.deb ...
Entpacken von nvidia-modprobe (418.56-1) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-kernel-support wird gewählt.
Vorbereitung zum Entpacken von .../23-nvidia-legacy-340xx-kernel-support_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-kernel-support (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-kernel-dkms wird gewählt.
Vorbereitung zum Entpacken von .../24-nvidia-legacy-340xx-kernel-dkms_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-kernel-dkms (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver wird gewählt.
Vorbereitung zum Entpacken von .../25-nvidia-legacy-340xx-driver_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-driver (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-cfg1:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../26-libnvidia-legacy-340xx-cfg1_340.107-4_amd64.deb ...
Entpacken von libnvidia-legacy-340xx-cfg1:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-persistenced wird gewählt.
Vorbereitung zum Entpacken von .../27-nvidia-persistenced_418.56-1_amd64.deb ...
Entpacken von nvidia-persistenced (418.56-1) ...
Vormals nicht ausgewähltes Paket nvidia-settings-legacy-340xx wird gewählt.
Vorbereitung zum Entpacken von .../28-nvidia-settings-legacy-340xx_340.107-2_amd64.deb ...
Entpacken von nvidia-settings-legacy-340xx (340.107-2) ...
Vormals nicht ausgewähltes Paket nvidia-xconfig wird gewählt.
Vorbereitung zum Entpacken von .../29-nvidia-xconfig_418.56-1_amd64.deb ...
Entpacken von nvidia-xconfig (418.56-1) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-eglcore:i386 wird gewählt.
Vorbereitung zum Entpacken von .../30-libnvidia-legacy-340xx-eglcore_340.107-4_i386.deb ...
Entpacken von libnvidia-legacy-340xx-eglcore:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libegl1-nvidia-legacy-340xx:i386 wird gewählt.
Vorbereitung zum Entpacken von .../31-libegl1-nvidia-legacy-340xx_340.107-4_i386.deb ...
Entpacken von libegl1-nvidia-legacy-340xx:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgles1-nvidia-legacy-340xx:i386 wird gewählt.
Vorbereitung zum Entpacken von .../32-libgles1-nvidia-legacy-340xx_340.107-4_i386.deb ...
Entpacken von libgles1-nvidia-legacy-340xx:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgles1-nvidia-legacy-340xx:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../33-libgles1-nvidia-legacy-340xx_340.107-4_amd64.deb ...
Entpacken von libgles1-nvidia-legacy-340xx:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgles2-nvidia-legacy-340xx:i386 wird gewählt.
Vorbereitung zum Entpacken von .../34-libgles2-nvidia-legacy-340xx_340.107-4_i386.deb ...
Entpacken von libgles2-nvidia-legacy-340xx:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgles2-nvidia-legacy-340xx:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../35-libgles2-nvidia-legacy-340xx_340.107-4_amd64.deb ...
Entpacken von libgles2-nvidia-legacy-340xx:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-cfg1:i386 wird gewählt.
Vorbereitung zum Entpacken von .../36-libnvidia-legacy-340xx-cfg1_340.107-4_i386.deb ...
Entpacken von libnvidia-legacy-340xx-cfg1:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver-libs:i386 wird gewählt.
Vorbereitung zum Entpacken von .../37-nvidia-legacy-340xx-driver-libs_340.107-4_i386.deb ...
Entpacken von nvidia-legacy-340xx-driver-libs:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver-libs-i386:i386 wird gewählt.
Vorbereitung zum Entpacken von .../38-nvidia-legacy-340xx-driver-libs-i386_340.107-4_i386.deb ...
Entpacken von nvidia-legacy-340xx-driver-libs-i386:i386 (340.107-4) ...
nvidia-support (20151021+9) wird eingerichtet ...
libxau6:i386 (1:1.0.8-1+b2) wird eingerichtet ...
nvidia-kernel-common (20151021+9) wird eingerichtet ...
nvidia-xconfig (418.56-1) wird eingerichtet ...
update-glx (1.0.0) wird eingerichtet ...
nvidia-modprobe (418.56-1) wird eingerichtet ...
libnvidia-legacy-340xx-glcore:amd64 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-glcore:i386 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-eglcore:amd64 (340.107-4) wird eingerichtet ...
libbsd0:i386 (0.9.1-2) wird eingerichtet ...
libxdmcp6:i386 (1:1.1.2-3) wird eingerichtet ...
libxcb1:i386 (1.13.1-2) wird eingerichtet ...
glx-alternative-mesa (1.0.0) wird eingerichtet ...
glx-diversions (1.0.0) wird eingerichtet ...
libx11-6:i386 (2:1.6.7-1) wird eingerichtet ...
libxext6:i386 (2:1.3.3-1+b2) wird eingerichtet ...
libnvidia-legacy-340xx-eglcore:i386 (340.107-4) wird eingerichtet ...
Trigger für desktop-file-utils (0.23-4) werden verarbeitet ...
Trigger für mime-support (3.62) werden verarbeitet ...
Trigger für libc-bin (2.28-10) werden verarbeitet ...
Trigger für systemd (1:241-5+mx19+2) werden verarbeitet ...
Trigger für man-db (2.8.5-2) werden verarbeitet ...
Trigger für glx-alternative-mesa (1.0.0) werden verarbeitet ...
update-alternatives: /usr/lib/mesa-diverted wird verwendet, um /usr/lib/glx (glx) im automatischen Modus bereitzustellen
glx-alternative-nvidia (1.0.0) wird eingerichtet ...
update-initramfs: deferring update (trigger activated)
Trigger für glx-alternative-nvidia (1.0.0) werden verarbeitet ...
nvidia-legacy-340xx-alternative (340.107-4) wird eingerichtet ...
Trigger für nvidia-legacy-340xx-alternative (340.107-4) werden verarbeitet ...
update-alternatives: /usr/lib/nvidia/legacy-340xx wird verwendet, um /usr/lib/nvidia/nvidia (nvidia) im automatischen Modus bereitzustellen
libegl1-nvidia-legacy-340xx:amd64 (340.107-4) wird eingerichtet ...
libegl1-nvidia-legacy-340xx:i386 (340.107-4) wird eingerichtet ...
libgl1-nvidia-legacy-340xx-glx:amd64 (340.107-4) wird eingerichtet ...
libgl1-nvidia-legacy-340xx-glx:i386 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-cfg1:amd64 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-cfg1:i386 (340.107-4) wird eingerichtet ...
xserver-xorg-video-nvidia-legacy-340xx (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-vdpau-driver:amd64 (340.107-4) wird eingerichtet ...
libgles2-nvidia-legacy-340xx:amd64 (340.107-4) wird eingerichtet ...
libgles2-nvidia-legacy-340xx:i386 (340.107-4) wird eingerichtet ...
libgles1-nvidia-legacy-340xx:amd64 (340.107-4) wird eingerichtet ...
libgles1-nvidia-legacy-340xx:i386 (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-kernel-support (340.107-4) wird eingerichtet ...
nvidia-settings-legacy-340xx (340.107-2) wird eingerichtet ...
nvidia-persistenced (418.56-1) wird eingerichtet ...
Warnung: Auf das von Ihnen angegebene Home-Verzeichnis /var/run/nvpd/ kann nicht zugegriffen werden: No such file or directory
Lege Systembenutzer »nvpd« (UID 119) an ...
Lege neue Gruppe »nvpd« (GID 129) an ...
Lege neuen Benutzer »nvpd« (UID 119) mit Gruppe »nvpd« an ...
Erstelle Home-Verzeichnis »/var/run/nvpd/« nicht.
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: Fehler beim Bearbeiten des Paketes nvidia-persistenced (--configure):
»installiertes nvidia-persistenced-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
nvidia-legacy-340xx-driver-libs:amd64 (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-driver-libs:i386 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-ml1:amd64 (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-driver-bin (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-driver-libs-i386:i386 (340.107-4) wird eingerichtet ...
Trigger für nvidia-legacy-340xx-alternative (340.107-4) werden verarbeitet ...
update-alternatives: Alternative /usr/lib/nvidia/legacy-340xx wird aktualisiert, weil Linkgruppe nvidia geänderte Slave-Links hat
nvidia-legacy-340xx-kernel-dkms (340.107-4) wird eingerichtet ...
Loading new nvidia-legacy-340xx-340.107 DKMS files...
Building for 4.19.0-5-amd64
Building initial module for 4.19.0-5-amd64
Done.
nvidia-legacy-340xx.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
nvidia-legacy-340xx-uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
depmod....
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Der Rechner ist nicht aktiv
DKMS: install completed.
nvidia-legacy-340xx-driver (340.107-4) wird eingerichtet ...
Trigger für libc-bin (2.28-10) werden verarbeitet ...
Trigger für initramfs-tools (0.133) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=576eb5a9-c73e-4846-9d66-bc4547026eae)
I: Set the RESUME variable to override this.
Trigger für update-glx (1.0.0) werden verarbeitet ...
Trigger für glx-alternative-nvidia (1.0.0) werden verarbeitet ...
update-alternatives: /usr/lib/nvidia wird verwendet, um /usr/lib/glx (glx) im automatischen Modus bereitzustellen
Trigger für systemd (1:241-5+mx19+2) werden verarbeitet ...
Trigger für libc-bin (2.28-10) werden verarbeitet ...
Trigger für initramfs-tools (0.133) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=576eb5a9-c73e-4846-9d66-bc4547026eae)
I: Set the RESUME variable to override this.
Fehler traten auf beim Bearbeiten von:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
New X configuration file written to '/etc/X11/xorg.conf'
Abgeschlossen
Drücke <Enter> zum verlassen
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:02 am
by dolphin_oracle
caprea wrote: Tue Aug 27, 2019 8:50 am
Sorry, german.
Code: Select all
Sperrung wird hergestellt.....
===================================
Installiere Treiber für: nvidia
Start am (m/t/j): 08/27/2019 01:10:26
===================================
Aktualisiere Quellen mit apt-get update
Kandidat ist: 340.107-4
Installiert ist: (none)
Möchten Sie im MX Test Repo nach einer neueren Version suchen?
Ja oder nein?
1: Ja
2: Nein
Enter Number of selection
Ok...
Aktualisiere Quellen mit apt-get update
Installiere aktuelles nvidia-detect Paket
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
nvidia-detect ist schon die neueste Version (418.74-1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Kandidat ist: 340.107-4
Installiert ist: (none)
Kandidat ist: 340.107-4
Kandidat aus dem MX Test Repository ist: 340.107-4
Installiert ist: (none)
Treiber benötigt:nvidia-legacy-340xx-driver (340.107-4)
packages to install are nvidia-legacy-340xx-driver nvidia-settings-legacy-340xx nvidia-legacy-340xx-kernel-dkms nvidia-xconfig
Frontend:
Nvidia-Befehl = apt-get install --install-recommends --reinstall -y nvidia-legacy-340xx-driver nvidia-settings-legacy-340xx nvidia-legacy-340xx-kernel-dkms nvidia-xconfig
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
0 aktualisiert, 0 neu installiert, 3 erneut installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 777 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Holen:1 http://deb.debian.org/debian buster/main amd64 build-essential amd64 12.6 [7.576 B]
Holen:2 http://deb.debian.org/debian-security buster/updates/main amd64 linux-headers-4.19.0-5-amd64 amd64 4.19.37-5+deb10u2 [750 kB]
Holen:3 http://mxrepo.com/mx/repo buster/non-free amd64 firmware-linux-nonfree all 20190717-1~mx19+1 [18,9 kB]
Es wurden 777 kB in 1 s geholt (1.274 kB/s).
(Lese Datenbank ...
(Lese Datenbank ... 5%
(Lese Datenbank ... 10%
(Lese Datenbank ... 15%
(Lese Datenbank ... 20%
(Lese Datenbank ... 25%
(Lese Datenbank ... 30%
(Lese Datenbank ... 35%
(Lese Datenbank ... 40%
(Lese Datenbank ... 45%
(Lese Datenbank ... 50%
(Lese Datenbank ... 55%
(Lese Datenbank ... 60%
(Lese Datenbank ... 65%
(Lese Datenbank ... 70%
(Lese Datenbank ... 75%
(Lese Datenbank ... 80%
(Lese Datenbank ... 85%
(Lese Datenbank ... 90%
(Lese Datenbank ... 95%
(Lese Datenbank ... 100%
(Lese Datenbank ... 268225 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../build-essential_12.6_amd64.deb ...
Entpacken von build-essential (12.6) über (12.6) ...
Vorbereitung zum Entpacken von .../firmware-linux-nonfree_20190717-1~mx19+1_all.deb ...
Entpacken von firmware-linux-nonfree (20190717-1~mx19+1) über (20190717-1~mx19+1) ...
Vorbereitung zum Entpacken von .../linux-headers-4.19.0-5-amd64_4.19.37-5+deb10u2_amd64.deb ...
Entpacken von linux-headers-4.19.0-5-amd64 (4.19.37-5+deb10u2) über (4.19.37-5+deb10u2) ...
linux-headers-4.19.0-5-amd64 (4.19.37-5+deb10u2) wird eingerichtet ...
firmware-linux-nonfree (20190717-1~mx19+1) wird eingerichtet ...
build-essential (12.6) wird eingerichtet ...
Paketlisten werden gelesen...
Abhängigkeitsbaum wird aufgebaut....
Statusinformationen werden eingelesen....
Die folgenden zusätzlichen Pakete werden installiert:
glx-alternative-mesa glx-alternative-nvidia glx-diversions libbsd0:i386
libegl1-nvidia-legacy-340xx libegl1-nvidia-legacy-340xx:i386
libgl1-nvidia-legacy-340xx-glx libgl1-nvidia-legacy-340xx-glx:i386
libgles1-nvidia-legacy-340xx libgles1-nvidia-legacy-340xx:i386
libgles2-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx:i386
libnvidia-legacy-340xx-cfg1 libnvidia-legacy-340xx-cfg1:i386
libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-eglcore:i386
libnvidia-legacy-340xx-glcore libnvidia-legacy-340xx-glcore:i386
libnvidia-legacy-340xx-ml1 libx11-6:i386 libxau6:i386 libxcb1:i386
libxdmcp6:i386 libxext6:i386 nvidia-installer-cleanup nvidia-kernel-common
nvidia-legacy-340xx-alternative nvidia-legacy-340xx-driver-bin
nvidia-legacy-340xx-driver-libs nvidia-legacy-340xx-driver-libs:i386
nvidia-legacy-340xx-driver-libs-i386:i386 nvidia-legacy-340xx-kernel-support
nvidia-legacy-340xx-vdpau-driver nvidia-modprobe nvidia-persistenced
nvidia-support update-glx xserver-xorg-video-nvidia-legacy-340xx
Vorgeschlagene Pakete:
nvidia-driver
Die folgenden NEUEN Pakete werden installiert:
glx-alternative-mesa glx-alternative-nvidia glx-diversions libbsd0:i386
libegl1-nvidia-legacy-340xx libegl1-nvidia-legacy-340xx:i386
libgl1-nvidia-legacy-340xx-glx libgl1-nvidia-legacy-340xx-glx:i386
libgles1-nvidia-legacy-340xx libgles1-nvidia-legacy-340xx:i386
libgles2-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx:i386
libnvidia-legacy-340xx-cfg1 libnvidia-legacy-340xx-cfg1:i386
libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-eglcore:i386
libnvidia-legacy-340xx-glcore libnvidia-legacy-340xx-glcore:i386
libnvidia-legacy-340xx-ml1 libx11-6:i386 libxau6:i386 libxcb1:i386
libxdmcp6:i386 libxext6:i386 nvidia-installer-cleanup nvidia-kernel-common
nvidia-legacy-340xx-alternative nvidia-legacy-340xx-driver
nvidia-legacy-340xx-driver-bin nvidia-legacy-340xx-driver-libs
nvidia-legacy-340xx-driver-libs:i386
nvidia-legacy-340xx-driver-libs-i386:i386 nvidia-legacy-340xx-kernel-dkms
nvidia-legacy-340xx-kernel-support nvidia-legacy-340xx-vdpau-driver
nvidia-modprobe nvidia-persistenced nvidia-settings-legacy-340xx
nvidia-support nvidia-xconfig update-glx
xserver-xorg-video-nvidia-legacy-340xx
0 aktualisiert, 42 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 40,8 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 220 MB Plattenplatz zusätzlich benutzt.
Holen:1 http://deb.debian.org/debian buster/contrib amd64 update-glx amd64 1.0.0 [10,5 kB]
Holen:2 http://deb.debian.org/debian buster/contrib amd64 glx-alternative-mesa amd64 1.0.0 [9.592 B]
Holen:3 http://deb.debian.org/debian buster/contrib amd64 nvidia-installer-cleanup amd64 20151021+9 [19,2 kB]
Holen:4 http://deb.debian.org/debian buster/contrib amd64 glx-diversions amd64 1.0.0 [12,0 kB]
Holen:5 http://deb.debian.org/debian buster/contrib amd64 glx-alternative-nvidia amd64 1.0.0 [10,8 kB]
Holen:6 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-alternative amd64 340.107-4 [80,3 kB]
Holen:7 http://deb.debian.org/debian buster/non-free amd64 libnvidia-legacy-340xx-glcore amd64 340.107-4 [7.010 kB]
Holen:8 http://deb.debian.org/debian buster/contrib amd64 nvidia-support amd64 20151021+9 [20,0 kB]
Holen:9 http://deb.debian.org/debian buster/non-free amd64 libgl1-nvidia-legacy-340xx-glx amd64 340.107-4 [468 kB]
Holen:10 http://deb.debian.org/debian buster/non-free i386 libnvidia-legacy-340xx-glcore i386 340.107-4 [7.018 kB]
Holen:11 http://deb.debian.org/debian buster/main i386 libxau6 i386 1:1.0.8-1+b2 [20,3 kB]
Holen:12 http://deb.debian.org/debian buster/main i386 libbsd0 i386 0.9.1-2 [104 kB]
Holen:13 http://deb.debian.org/debian buster/main i386 libxdmcp6 i386 1:1.1.2-3 [26,7 kB]
Holen:14 http://deb.debian.org/debian buster/main i386 libxcb1 i386 1.13.1-2 [141 kB]
Holen:15 http://deb.debian.org/debian buster/main i386 libx11-6 i386 2:1.6.7-1 [778 kB]
Holen:16 http://deb.debian.org/debian buster/main i386 libxext6 i386 2:1.3.3-1+b2 [55,2 kB]
Holen:17 http://deb.debian.org/debian buster/non-free i386 libgl1-nvidia-legacy-340xx-glx i386 340.107-4 [451 kB]
Holen:18 http://deb.debian.org/debian buster/non-free amd64 libnvidia-legacy-340xx-eglcore amd64 340.107-4 [6.981 kB]
Holen:19 http://deb.debian.org/debian buster/non-free amd64 libegl1-nvidia-legacy-340xx amd64 340.107-4 [230 kB]
Holen:20 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-driver-libs amd64 340.107-4 [78,6 kB]
Holen:21 http://deb.debian.org/debian buster/non-free amd64 libnvidia-legacy-340xx-ml1 amd64 340.107-4 [359 kB]
Holen:22 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-driver-bin amd64 340.107-4 [160 kB]
Holen:23 http://deb.debian.org/debian buster/non-free amd64 xserver-xorg-video-nvidia-legacy-340xx amd64 340.107-4 [2.721 kB]
Holen:24 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-vdpau-driver amd64 340.107-4 [916 kB]
Holen:25 http://deb.debian.org/debian buster/contrib amd64 nvidia-kernel-common amd64 20151021+9 [10,8 kB]
Holen:26 http://deb.debian.org/debian buster/contrib amd64 nvidia-modprobe amd64 418.56-1 [19,2 kB]
Holen:27 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-kernel-support amd64 340.107-4 [79,4 kB]
Holen:28 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-kernel-dkms amd64 340.107-4 [3.977 kB]
Holen:29 http://deb.debian.org/debian buster/non-free amd64 nvidia-legacy-340xx-driver amd64 340.107-4 [364 kB]
Holen:30 http://deb.debian.org/debian buster/non-free amd64 libnvidia-legacy-340xx-cfg1 amd64 340.107-4 [135 kB]
Holen:31 http://deb.debian.org/debian buster/contrib amd64 nvidia-persistenced amd64 418.56-1 [26,7 kB]
Holen:32 http://deb.debian.org/debian buster/contrib amd64 nvidia-settings-legacy-340xx amd64 340.107-2 [741 kB]
Holen:33 http://deb.debian.org/debian buster/contrib amd64 nvidia-xconfig amd64 418.56-1 [84,3 kB]
Holen:34 http://deb.debian.org/debian buster/non-free i386 libnvidia-legacy-340xx-eglcore i386 340.107-4 [6.846 kB]
Holen:35 http://deb.debian.org/debian buster/non-free i386 libegl1-nvidia-legacy-340xx i386 340.107-4 [202 kB]
Holen:36 http://deb.debian.org/debian buster/non-free amd64 libgles1-nvidia-legacy-340xx amd64 340.107-4 [94,3 kB]
Holen:37 http://deb.debian.org/debian buster/non-free i386 libgles1-nvidia-legacy-340xx i386 340.107-4 [93,4 kB]
Holen:38 http://deb.debian.org/debian buster/non-free i386 libgles2-nvidia-legacy-340xx i386 340.107-4 [96,2 kB]
Holen:39 http://deb.debian.org/debian buster/non-free amd64 libgles2-nvidia-legacy-340xx amd64 340.107-4 [96,8 kB]
Holen:40 http://deb.debian.org/debian buster/non-free i386 libnvidia-legacy-340xx-cfg1 i386 340.107-4 [135 kB]
Holen:41 http://deb.debian.org/debian buster/non-free i386 nvidia-legacy-340xx-driver-libs i386 340.107-4 [78,6 kB]
Holen:42 http://deb.debian.org/debian buster/non-free i386 nvidia-legacy-340xx-driver-libs-i386 i386 340.107-4 [78,5 kB]
Vorkonfiguration der Pakete ...
Es wurden 40,8 MB in 15 s geholt (2.683 kB/s).
Vormals nicht ausgewähltes Paket update-glx wird gewählt.
(Lese Datenbank ...
(Lese Datenbank ... 5%
(Lese Datenbank ... 10%
(Lese Datenbank ... 15%
(Lese Datenbank ... 20%
(Lese Datenbank ... 25%
(Lese Datenbank ... 30%
(Lese Datenbank ... 35%
(Lese Datenbank ... 40%
(Lese Datenbank ... 45%
(Lese Datenbank ... 50%
(Lese Datenbank ... 55%
(Lese Datenbank ... 60%
(Lese Datenbank ... 65%
(Lese Datenbank ... 70%
(Lese Datenbank ... 75%
(Lese Datenbank ... 80%
(Lese Datenbank ... 85%
(Lese Datenbank ... 90%
(Lese Datenbank ... 95%
(Lese Datenbank ... 100%
(Lese Datenbank ... 268225 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../update-glx_1.0.0_amd64.deb ...
Entpacken von update-glx (1.0.0) ...
Vormals nicht ausgewähltes Paket glx-alternative-mesa wird gewählt.
Vorbereitung zum Entpacken von .../glx-alternative-mesa_1.0.0_amd64.deb ...
Entpacken von glx-alternative-mesa (1.0.0) ...
Vormals nicht ausgewähltes Paket nvidia-installer-cleanup wird gewählt.
Vorbereitung zum Entpacken von .../nvidia-installer-cleanup_20151021+9_amd64.deb ...
Entpacken von nvidia-installer-cleanup (20151021+9) ...
nvidia-installer-cleanup (20151021+9) wird eingerichtet ...
Vormals nicht ausgewähltes Paket glx-diversions wird gewählt.
(Lese Datenbank ...
(Lese Datenbank ... 5%
(Lese Datenbank ... 10%
(Lese Datenbank ... 15%
(Lese Datenbank ... 20%
(Lese Datenbank ... 25%
(Lese Datenbank ... 30%
(Lese Datenbank ... 35%
(Lese Datenbank ... 40%
(Lese Datenbank ... 45%
(Lese Datenbank ... 50%
(Lese Datenbank ... 55%
(Lese Datenbank ... 60%
(Lese Datenbank ... 65%
(Lese Datenbank ... 70%
(Lese Datenbank ... 75%
(Lese Datenbank ... 80%
(Lese Datenbank ... 85%
(Lese Datenbank ... 90%
(Lese Datenbank ... 95%
(Lese Datenbank ... 100%
(Lese Datenbank ... 268325 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../00-glx-diversions_1.0.0_amd64.deb ...
Entpacken von glx-diversions (1.0.0) ...
Vormals nicht ausgewähltes Paket glx-alternative-nvidia wird gewählt.
Vorbereitung zum Entpacken von .../01-glx-alternative-nvidia_1.0.0_amd64.deb ...
Entpacken von glx-alternative-nvidia (1.0.0) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-alternative wird gewählt.
Vorbereitung zum Entpacken von .../02-nvidia-legacy-340xx-alternative_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-alternative (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-glcore:i386 wird gewählt.
Vorbereitung zum Entpacken von .../03-libnvidia-legacy-340xx-glcore_340.107-4_i386.deb ...
Entpacken von libnvidia-legacy-340xx-glcore:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-support wird gewählt.
Vorbereitung zum Entpacken von .../04-nvidia-support_20151021+9_amd64.deb ...
Entpacken von nvidia-support (20151021+9) ...
Vormals nicht ausgewähltes Paket libxau6:i386 wird gewählt.
Vorbereitung zum Entpacken von .../05-libxau6_1%3a1.0.8-1+b2_i386.deb ...
Entpacken von libxau6:i386 (1:1.0.8-1+b2) ...
Vormals nicht ausgewähltes Paket libbsd0:i386 wird gewählt.
Vorbereitung zum Entpacken von .../06-libbsd0_0.9.1-2_i386.deb ...
Entpacken von libbsd0:i386 (0.9.1-2) ...
Vormals nicht ausgewähltes Paket libxdmcp6:i386 wird gewählt.
Vorbereitung zum Entpacken von .../07-libxdmcp6_1%3a1.1.2-3_i386.deb ...
Entpacken von libxdmcp6:i386 (1:1.1.2-3) ...
Vormals nicht ausgewähltes Paket libxcb1:i386 wird gewählt.
Vorbereitung zum Entpacken von .../08-libxcb1_1.13.1-2_i386.deb ...
Entpacken von libxcb1:i386 (1.13.1-2) ...
Vormals nicht ausgewähltes Paket libx11-6:i386 wird gewählt.
Vorbereitung zum Entpacken von .../09-libx11-6_2%3a1.6.7-1_i386.deb ...
Entpacken von libx11-6:i386 (2:1.6.7-1) ...
Vormals nicht ausgewähltes Paket libxext6:i386 wird gewählt.
Vorbereitung zum Entpacken von .../10-libxext6_2%3a1.3.3-1+b2_i386.deb ...
Entpacken von libxext6:i386 (2:1.3.3-1+b2) ...
Vormals nicht ausgewähltes Paket libgl1-nvidia-legacy-340xx-glx:i386 wird gewählt.
Vorbereitung zum Entpacken von .../11-libgl1-nvidia-legacy-340xx-glx_340.107-4_i386.deb ...
Entpacken von libgl1-nvidia-legacy-340xx-glx:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-glcore:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../12-libnvidia-legacy-340xx-glcore_340.107-4_amd64.deb ...
Entpacken von libnvidia-legacy-340xx-glcore:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgl1-nvidia-legacy-340xx-glx:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../13-libgl1-nvidia-legacy-340xx-glx_340.107-4_amd64.deb ...
Entpacken von libgl1-nvidia-legacy-340xx-glx:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-eglcore:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../14-libnvidia-legacy-340xx-eglcore_340.107-4_amd64.deb ...
Entpacken von libnvidia-legacy-340xx-eglcore:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libegl1-nvidia-legacy-340xx:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../15-libegl1-nvidia-legacy-340xx_340.107-4_amd64.deb ...
Entpacken von libegl1-nvidia-legacy-340xx:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver-libs:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../16-nvidia-legacy-340xx-driver-libs_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-driver-libs:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-ml1:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../17-libnvidia-legacy-340xx-ml1_340.107-4_amd64.deb ...
Entpacken von libnvidia-legacy-340xx-ml1:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver-bin wird gewählt.
Vorbereitung zum Entpacken von .../18-nvidia-legacy-340xx-driver-bin_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-driver-bin (340.107-4) ...
Vormals nicht ausgewähltes Paket xserver-xorg-video-nvidia-legacy-340xx wird gewählt.
Vorbereitung zum Entpacken von .../19-xserver-xorg-video-nvidia-legacy-340xx_340.107-4_amd64.deb ...
Entpacken von xserver-xorg-video-nvidia-legacy-340xx (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-vdpau-driver:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../20-nvidia-legacy-340xx-vdpau-driver_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-vdpau-driver:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-kernel-common wird gewählt.
Vorbereitung zum Entpacken von .../21-nvidia-kernel-common_20151021+9_amd64.deb ...
Entpacken von nvidia-kernel-common (20151021+9) ...
Vormals nicht ausgewähltes Paket nvidia-modprobe wird gewählt.
Vorbereitung zum Entpacken von .../22-nvidia-modprobe_418.56-1_amd64.deb ...
Entpacken von nvidia-modprobe (418.56-1) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-kernel-support wird gewählt.
Vorbereitung zum Entpacken von .../23-nvidia-legacy-340xx-kernel-support_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-kernel-support (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-kernel-dkms wird gewählt.
Vorbereitung zum Entpacken von .../24-nvidia-legacy-340xx-kernel-dkms_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-kernel-dkms (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver wird gewählt.
Vorbereitung zum Entpacken von .../25-nvidia-legacy-340xx-driver_340.107-4_amd64.deb ...
Entpacken von nvidia-legacy-340xx-driver (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-cfg1:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../26-libnvidia-legacy-340xx-cfg1_340.107-4_amd64.deb ...
Entpacken von libnvidia-legacy-340xx-cfg1:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-persistenced wird gewählt.
Vorbereitung zum Entpacken von .../27-nvidia-persistenced_418.56-1_amd64.deb ...
Entpacken von nvidia-persistenced (418.56-1) ...
Vormals nicht ausgewähltes Paket nvidia-settings-legacy-340xx wird gewählt.
Vorbereitung zum Entpacken von .../28-nvidia-settings-legacy-340xx_340.107-2_amd64.deb ...
Entpacken von nvidia-settings-legacy-340xx (340.107-2) ...
Vormals nicht ausgewähltes Paket nvidia-xconfig wird gewählt.
Vorbereitung zum Entpacken von .../29-nvidia-xconfig_418.56-1_amd64.deb ...
Entpacken von nvidia-xconfig (418.56-1) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-eglcore:i386 wird gewählt.
Vorbereitung zum Entpacken von .../30-libnvidia-legacy-340xx-eglcore_340.107-4_i386.deb ...
Entpacken von libnvidia-legacy-340xx-eglcore:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libegl1-nvidia-legacy-340xx:i386 wird gewählt.
Vorbereitung zum Entpacken von .../31-libegl1-nvidia-legacy-340xx_340.107-4_i386.deb ...
Entpacken von libegl1-nvidia-legacy-340xx:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgles1-nvidia-legacy-340xx:i386 wird gewählt.
Vorbereitung zum Entpacken von .../32-libgles1-nvidia-legacy-340xx_340.107-4_i386.deb ...
Entpacken von libgles1-nvidia-legacy-340xx:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgles1-nvidia-legacy-340xx:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../33-libgles1-nvidia-legacy-340xx_340.107-4_amd64.deb ...
Entpacken von libgles1-nvidia-legacy-340xx:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgles2-nvidia-legacy-340xx:i386 wird gewählt.
Vorbereitung zum Entpacken von .../34-libgles2-nvidia-legacy-340xx_340.107-4_i386.deb ...
Entpacken von libgles2-nvidia-legacy-340xx:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket libgles2-nvidia-legacy-340xx:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../35-libgles2-nvidia-legacy-340xx_340.107-4_amd64.deb ...
Entpacken von libgles2-nvidia-legacy-340xx:amd64 (340.107-4) ...
Vormals nicht ausgewähltes Paket libnvidia-legacy-340xx-cfg1:i386 wird gewählt.
Vorbereitung zum Entpacken von .../36-libnvidia-legacy-340xx-cfg1_340.107-4_i386.deb ...
Entpacken von libnvidia-legacy-340xx-cfg1:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver-libs:i386 wird gewählt.
Vorbereitung zum Entpacken von .../37-nvidia-legacy-340xx-driver-libs_340.107-4_i386.deb ...
Entpacken von nvidia-legacy-340xx-driver-libs:i386 (340.107-4) ...
Vormals nicht ausgewähltes Paket nvidia-legacy-340xx-driver-libs-i386:i386 wird gewählt.
Vorbereitung zum Entpacken von .../38-nvidia-legacy-340xx-driver-libs-i386_340.107-4_i386.deb ...
Entpacken von nvidia-legacy-340xx-driver-libs-i386:i386 (340.107-4) ...
nvidia-support (20151021+9) wird eingerichtet ...
libxau6:i386 (1:1.0.8-1+b2) wird eingerichtet ...
nvidia-kernel-common (20151021+9) wird eingerichtet ...
nvidia-xconfig (418.56-1) wird eingerichtet ...
update-glx (1.0.0) wird eingerichtet ...
nvidia-modprobe (418.56-1) wird eingerichtet ...
libnvidia-legacy-340xx-glcore:amd64 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-glcore:i386 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-eglcore:amd64 (340.107-4) wird eingerichtet ...
libbsd0:i386 (0.9.1-2) wird eingerichtet ...
libxdmcp6:i386 (1:1.1.2-3) wird eingerichtet ...
libxcb1:i386 (1.13.1-2) wird eingerichtet ...
glx-alternative-mesa (1.0.0) wird eingerichtet ...
glx-diversions (1.0.0) wird eingerichtet ...
libx11-6:i386 (2:1.6.7-1) wird eingerichtet ...
libxext6:i386 (2:1.3.3-1+b2) wird eingerichtet ...
libnvidia-legacy-340xx-eglcore:i386 (340.107-4) wird eingerichtet ...
Trigger für desktop-file-utils (0.23-4) werden verarbeitet ...
Trigger für mime-support (3.62) werden verarbeitet ...
Trigger für libc-bin (2.28-10) werden verarbeitet ...
Trigger für systemd (1:241-5+mx19+2) werden verarbeitet ...
Trigger für man-db (2.8.5-2) werden verarbeitet ...
Trigger für glx-alternative-mesa (1.0.0) werden verarbeitet ...
update-alternatives: /usr/lib/mesa-diverted wird verwendet, um /usr/lib/glx (glx) im automatischen Modus bereitzustellen
glx-alternative-nvidia (1.0.0) wird eingerichtet ...
update-initramfs: deferring update (trigger activated)
Trigger für glx-alternative-nvidia (1.0.0) werden verarbeitet ...
nvidia-legacy-340xx-alternative (340.107-4) wird eingerichtet ...
Trigger für nvidia-legacy-340xx-alternative (340.107-4) werden verarbeitet ...
update-alternatives: /usr/lib/nvidia/legacy-340xx wird verwendet, um /usr/lib/nvidia/nvidia (nvidia) im automatischen Modus bereitzustellen
libegl1-nvidia-legacy-340xx:amd64 (340.107-4) wird eingerichtet ...
libegl1-nvidia-legacy-340xx:i386 (340.107-4) wird eingerichtet ...
libgl1-nvidia-legacy-340xx-glx:amd64 (340.107-4) wird eingerichtet ...
libgl1-nvidia-legacy-340xx-glx:i386 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-cfg1:amd64 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-cfg1:i386 (340.107-4) wird eingerichtet ...
xserver-xorg-video-nvidia-legacy-340xx (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-vdpau-driver:amd64 (340.107-4) wird eingerichtet ...
libgles2-nvidia-legacy-340xx:amd64 (340.107-4) wird eingerichtet ...
libgles2-nvidia-legacy-340xx:i386 (340.107-4) wird eingerichtet ...
libgles1-nvidia-legacy-340xx:amd64 (340.107-4) wird eingerichtet ...
libgles1-nvidia-legacy-340xx:i386 (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-kernel-support (340.107-4) wird eingerichtet ...
nvidia-settings-legacy-340xx (340.107-2) wird eingerichtet ...
nvidia-persistenced (418.56-1) wird eingerichtet ...
Warnung: Auf das von Ihnen angegebene Home-Verzeichnis /var/run/nvpd/ kann nicht zugegriffen werden: No such file or directory
Lege Systembenutzer »nvpd« (UID 119) an ...
Lege neue Gruppe »nvpd« (GID 129) an ...
Lege neuen Benutzer »nvpd« (UID 119) mit Gruppe »nvpd« an ...
Erstelle Home-Verzeichnis »/var/run/nvpd/« nicht.
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: Fehler beim Bearbeiten des Paketes nvidia-persistenced (--configure):
»installiertes nvidia-persistenced-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
nvidia-legacy-340xx-driver-libs:amd64 (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-driver-libs:i386 (340.107-4) wird eingerichtet ...
libnvidia-legacy-340xx-ml1:amd64 (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-driver-bin (340.107-4) wird eingerichtet ...
nvidia-legacy-340xx-driver-libs-i386:i386 (340.107-4) wird eingerichtet ...
Trigger für nvidia-legacy-340xx-alternative (340.107-4) werden verarbeitet ...
update-alternatives: Alternative /usr/lib/nvidia/legacy-340xx wird aktualisiert, weil Linkgruppe nvidia geänderte Slave-Links hat
nvidia-legacy-340xx-kernel-dkms (340.107-4) wird eingerichtet ...
Loading new nvidia-legacy-340xx-340.107 DKMS files...
Building for 4.19.0-5-amd64
Building initial module for 4.19.0-5-amd64
Done.
nvidia-legacy-340xx.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
nvidia-legacy-340xx-uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
depmod....
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Der Rechner ist nicht aktiv
DKMS: install completed.
nvidia-legacy-340xx-driver (340.107-4) wird eingerichtet ...
Trigger für libc-bin (2.28-10) werden verarbeitet ...
Trigger für initramfs-tools (0.133) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=576eb5a9-c73e-4846-9d66-bc4547026eae)
I: Set the RESUME variable to override this.
Trigger für update-glx (1.0.0) werden verarbeitet ...
Trigger für glx-alternative-nvidia (1.0.0) werden verarbeitet ...
update-alternatives: /usr/lib/nvidia wird verwendet, um /usr/lib/glx (glx) im automatischen Modus bereitzustellen
Trigger für systemd (1:241-5+mx19+2) werden verarbeitet ...
Trigger für libc-bin (2.28-10) werden verarbeitet ...
Trigger für initramfs-tools (0.133) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=576eb5a9-c73e-4846-9d66-bc4547026eae)
I: Set the RESUME variable to override this.
Fehler traten auf beim Bearbeiten von:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
New X configuration file written to '/etc/X11/xorg.conf'
Abgeschlossen
Drücke <Enter> zum verlassen
well, it has a sysVinit init script, but its failing to launch. or at least failing to launch from the install script.
I wonder if a reboot, then
Code: Select all
sudo dpkg-reconfigure nvidia-persistenced
would work.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:09 am
by zebedeeboss
Got it installed using the same method used in antiX19 :D
This works on an RTX series Card
1 Boot to live USB
2 drop to tty login as root (it will probably do this auto due to RTX issues - this is Linux wide and not anything specific to do with Antix)
3 perform a full update & upgrade
4 run nvidia cli commands as per Dolphin instructions - see below
sudo apt install --install-recommends nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
5 run cli-installer
6 reboot
Regards Zeb...
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:13 am
by mcury
dolphin_oracle wrote: Tue Aug 27, 2019 8:43 am
caprea wrote: Tue Aug 27, 2019 8:42 am
@dolphin_oracle
I got the same error like mcury during nvidia-driver installation and after, with ddm-mx
Looks like entropyfoe, too.
viewtopic.php?p=523443#p523443
Btw, also on antiX19-beta.
I think we need the /var/log/ddm.log files. just attach them. there is something wrong there...might be a systemd thing.
f**kn nvidia is a moving target....
Follows the file /var/log/ddm.log:
https://pastebin.com/YtfcUpdv
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:23 am
by Eadwine Rose
Another nvidia thingie. Installed ok, driver is running. Just installed another package after it and am getting this:
Code: Select all
E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
clicking on details:
Code: Select all
Selecting previously unselected package xboxdrv.
(Reading database ... 270028 files and directories currently installed.)
Preparing to unpack .../xboxdrv_0.8.8-1_amd64.deb ...
Unpacking xboxdrv (0.8.8-1) ...
Setting up nvidia-persistenced (418.56-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Setting up xboxdrv (0.8.8-1) ...
Processing triggers for man-db (2.8.5-2) ...
Errors were encountered while processing:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up nvidia-persistenced (418.56-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
nvidia-persistenced
I remember leaving test checked by mistake early on in the install when I was searching for xbindkeys, didn't find it in synaptic, closed that, then started MXPI, and installed it using that from the stable tab.
Now.. I COULD have had the test repo checked in synaptic still when I hit the nvidia installer. I don't remember exactly the point where I unchecked it again. Didn't let the nvidia installer check backports or anything. SO.. this all MIGHT be because of that stupidity that I pulled. It's unchecked now, of course, and below is some more info for posterity sake.
Also.. does installing nvidia affect grub? I had it set to load 18.3 per default and after the install it was kicked back to 19beta per default.
Code: Select all
System: Host: MX19beta Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19beta-1_x64 patito feo August 25 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 1607 date: 06/17/2019
Battery: Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: Discharging
CPU: Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102193
Speed: 1385 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1380
2: 1379 3: 1467 4: 1426 5: 1479 6: 1389 7: 1544 8: 1546 9: 1378 10: 1382 11: 1376
12: 1542 13: 1547 14: 1547 15: 1543 16: 1540
Vulnerabilities: Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74
bus ID: 08:00.0 chip ID: 10de:1c82
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
resolution: 1920x1080~60Hz, 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74
direct render: Yes
Audio: Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D
Comb
vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880
Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9
Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 0a:00.3 chip ID: 1022:1457
Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo
bus ID: 3-1:2 chip ID: 046d:09a4 serial: <filter>
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2
chip ID: 148f:7601 serial: <filter>
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 1.82 TiB used: 80.38 GiB (4.3%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT
ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT
ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT
ID-4: /dev/sdd type: USB vendor: Seagate model: BUP Slim RD size: 931.51 GiB
block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0109 scheme: MBR
ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 5.63 GiB (9.8%) fs: ext4
dev: /dev/sdc3
ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 121.8 MiB (0.1%)
fs: ext4 dev: /dev/sdc2
ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sdc1
Sensors: System Temperatures: cpu: 47.6 C mobo: 38.0 C gpu: nvidia temp: 46 C
Fan Speeds (RPM): cpu: 715 fan-2: 903 fan-3: 0 fan-4: 829 fan-6: 0 gpu: nvidia
fan: 26%
Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.29
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster/ buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
2: deb http://mxrepo.com/mx/testrepo/ buster test
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 309 Uptime: 8m Memory: 31.41 GiB used: 1.23 GiB (3.9%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
running in: quick-system-in inxi: 3.0.33
/var/log/ddm.log
Code: Select all
creating lock ...
===================================
Install drivers for: nvidia
Start at (m/d/y): 08/27/2019 14:59:52
===================================
Refreshing Sources with apt-get update
Candidate is: 418.74-1
Installed is: (none)
Would you like to check MX Test Repo for a later version?
Yes or No?
1: Yes
2: No
Enter Number of selection
Ok...
Candidate is: 418.74-1
Installed is: (none)
Candidate is: 418.74-1
Installed is: (none)
Need driver: nvidia-driver (418.74-1)
packages to install are nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
Frontend:
Nvidia command = apt-get install --install-recommends --reinstall -y nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 0 not upgraded.
Need to get 777 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://mxrepo.com/mx/repo buster/non-free amd64 firmware-linux-nonfree all 20190717-1~mx19+1 [18.9 kB]
Get:2 http://cdn-fastly.deb.debian.org/debian buster/main amd64 build-essential amd64 12.6 [7,576 B]
Get:3 http://cdn-fastly.deb.debian.org/debian-security buster/updates/main amd64 linux-headers-4.19.0-5-amd64 amd64 4.19.37-5+deb10u2 [750 kB]
Fetched 777 kB in 1s (1,501 kB/s)
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 268910 files and directories currently installed.)
Preparing to unpack .../build-essential_12.6_amd64.deb ...
Unpacking build-essential (12.6) over (12.6) ...
Preparing to unpack .../firmware-linux-nonfree_20190717-1~mx19+1_all.deb ...
Unpacking firmware-linux-nonfree (20190717-1~mx19+1) over (20190717-1~mx19+1) ...
Preparing to unpack .../linux-headers-4.19.0-5-amd64_4.19.37-5+deb10u2_amd64.deb ...
Unpacking linux-headers-4.19.0-5-amd64 (4.19.37-5+deb10u2) over (4.19.37-5+deb10u2) ...
Setting up linux-headers-4.19.0-5-amd64 (4.19.37-5+deb10u2) ...
Setting up firmware-linux-nonfree (20190717-1~mx19+1) ...
Setting up build-essential (12.6) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
glx-alternative-mesa glx-alternative-nvidia glx-diversions libatomic1:i386
libbsd0:i386 libcuda1 libcuda1:i386 libcuda1-i386:i386 libdrm-amdgpu1:i386
libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386
libedit2:i386 libegl-mesa0:i386 libegl-nvidia0 libegl-nvidia0:i386
libegl1:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgbm1:i386
libgl1:i386 libgl1-mesa-dri:i386 libgl1-nvidia-glvnd-glx
libgl1-nvidia-glvnd-glx:i386 libglapi-mesa:i386 libgles-nvidia1
libgles-nvidia1:i386 libgles-nvidia2 libgles-nvidia2:i386 libgles1
libgles1:i386 libgles2:i386 libglvnd0:i386 libglx-mesa0:i386 libglx-nvidia0
libglx-nvidia0:i386 libglx0:i386 libllvm7:i386 libnvcuvid1 libnvidia-cbl
libnvidia-cfg1 libnvidia-eglcore libnvidia-eglcore:i386
libnvidia-fatbinaryloader libnvidia-fatbinaryloader:i386 libnvidia-glcore
libnvidia-glcore:i386 libnvidia-glvkspirv libnvidia-glvkspirv:i386
libnvidia-ml1 libnvidia-ptxjitcompiler1 libnvidia-ptxjitcompiler1:i386
libnvidia-rtcore libopengl0 libopengl0:i386 libpciaccess0:i386
libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libvulkan1:i386
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386
libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386
libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386
libxshmfence1:i386 libxxf86vm1:i386 nvidia-alternative nvidia-driver-bin
nvidia-driver-libs nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386
nvidia-egl-common nvidia-egl-icd nvidia-egl-icd:i386
nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-support
nvidia-legacy-check nvidia-modprobe nvidia-persistenced nvidia-smi
nvidia-support nvidia-vdpau-driver nvidia-vulkan-common nvidia-vulkan-icd
nvidia-vulkan-icd:i386 update-glx xserver-xorg-video-nvidia zlib1g:i386
Suggested packages:
nvidia-cuda-mps lm-sensors:i386 vulkan-utils vulkan-utils:i386
The following NEW packages will be installed:
glx-alternative-mesa glx-alternative-nvidia glx-diversions libatomic1:i386
libbsd0:i386 libcuda1 libcuda1:i386 libcuda1-i386:i386 libdrm-amdgpu1:i386
libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386
libedit2:i386 libegl-mesa0:i386 libegl-nvidia0 libegl-nvidia0:i386
libegl1:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgbm1:i386
libgl1:i386 libgl1-mesa-dri:i386 libgl1-nvidia-glvnd-glx
libgl1-nvidia-glvnd-glx:i386 libglapi-mesa:i386 libgles-nvidia1
libgles-nvidia1:i386 libgles-nvidia2 libgles-nvidia2:i386 libgles1
libgles1:i386 libgles2:i386 libglvnd0:i386 libglx-mesa0:i386 libglx-nvidia0
libglx-nvidia0:i386 libglx0:i386 libllvm7:i386 libnvcuvid1 libnvidia-cbl
libnvidia-cfg1 libnvidia-eglcore libnvidia-eglcore:i386 libnvidia-encode1
libnvidia-fatbinaryloader libnvidia-fatbinaryloader:i386 libnvidia-glcore
libnvidia-glcore:i386 libnvidia-glvkspirv libnvidia-glvkspirv:i386
libnvidia-ml1 libnvidia-ptxjitcompiler1 libnvidia-ptxjitcompiler1:i386
libnvidia-rtcore libopengl0 libopengl0:i386 libpciaccess0:i386
libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libvulkan1:i386
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386
libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386
libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386
libxshmfence1:i386 libxxf86vm1:i386 nvidia-alternative nvidia-driver
nvidia-driver-bin nvidia-driver-libs nvidia-driver-libs:i386
nvidia-driver-libs-i386:i386 nvidia-egl-common nvidia-egl-icd
nvidia-egl-icd:i386 nvidia-installer-cleanup nvidia-kernel-common
nvidia-kernel-dkms nvidia-kernel-support nvidia-legacy-check nvidia-modprobe
nvidia-persistenced nvidia-settings nvidia-smi nvidia-support
nvidia-vdpau-driver nvidia-vulkan-common nvidia-vulkan-icd
nvidia-vulkan-icd:i386 update-glx xserver-xorg-video-nvidia zlib1g:i386
0 upgraded, 107 newly installed, 0 to remove and 0 not upgraded.
Need to get 103 MB of archives.
After this operation, 525 MB of additional disk space will be used.
Get:1 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 update-glx amd64 1.0.0 [10.5 kB]
Get:2 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 glx-alternative-mesa amd64 1.0.0 [9,592 B]
Get:3 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 nvidia-installer-cleanup amd64 20151021+9 [19.2 kB]
Get:4 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 glx-diversions amd64 1.0.0 [12.0 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 glx-alternative-nvidia amd64 1.0.0 [10.8 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-legacy-check amd64 418.74-1 [206 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 nvidia-support amd64 20151021+9 [20.0 kB]
Get:8 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-alternative amd64 418.74-1 [203 kB]
Get:9 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-ptxjitcompiler1 amd64 418.74-1 [3,503 kB]
Get:10 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-fatbinaryloader amd64 418.74-1 [322 kB]
Get:11 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libcuda1 amd64 418.74-1 [2,100 kB]
Get:12 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-glcore amd64 418.74-1 [6,337 kB]
Get:13 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libglx-nvidia0 amd64 418.74-1 [458 kB]
Get:14 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libgl1-nvidia-glvnd-glx amd64 418.74-1 [360 kB]
Get:15 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-egl-common amd64 418.74-1 [202 kB]
Get:16 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-eglcore amd64 418.74-1 [6,312 kB]
Get:17 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libegl-nvidia0 amd64 418.74-1 [431 kB]
Get:18 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-egl-icd amd64 418.74-1 [201 kB]
Get:19 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-driver-libs amd64 418.74-1 [202 kB]
Get:20 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-ml1 amd64 418.74-1 [638 kB]
Get:21 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-driver-bin amd64 418.74-1 [290 kB]
Get:22 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 xserver-xorg-video-nvidia amd64 418.74-1 [2,459 kB]
Get:23 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-vdpau-driver amd64 418.74-1 [891 kB]
Get:24 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 nvidia-kernel-common amd64 20151021+9 [10.8 kB]
Get:25 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 nvidia-modprobe amd64 418.56-1 [19.2 kB]
Get:26 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-kernel-support amd64 418.74-1 [202 kB]
Get:27 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-kernel-dkms amd64 418.74-1 [11.4 MB]
Get:28 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-driver amd64 418.74-1 [509 kB]
Get:29 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-cfg1 amd64 418.74-1 [266 kB]
Get:30 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 nvidia-persistenced amd64 418.56-1 [26.7 kB]
Get:31 http://cdn-fastly.deb.debian.org/debian buster/contrib amd64 nvidia-settings amd64 418.74-1 [976 kB]
Get:32 http://cdn-fastly.deb.debian.org/debian buster/main i386 libatomic1 i386 8.3.0-6 [9,472 B]
Get:33 http://cdn-fastly.deb.debian.org/debian buster/main i386 libbsd0 i386 0.9.1-2 [104 kB]
Get:34 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libnvidia-ptxjitcompiler1 i386 418.74-1 [3,572 kB]
Get:35 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libnvidia-fatbinaryloader i386 418.74-1 [328 kB]
Get:36 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libcuda1 i386 418.74-1 [2,065 kB]
Get:37 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libcuda1-i386 i386 418.74-1 [201 kB]
Get:38 http://cdn-fastly.deb.debian.org/debian buster/main i386 libdrm2 i386 2.4.97-1 [42.5 kB]
Get:39 http://cdn-fastly.deb.debian.org/debian buster/main i386 libdrm-amdgpu1 i386 2.4.97-1 [30.1 kB]
Get:40 http://cdn-fastly.deb.debian.org/debian buster/main i386 zlib1g i386 1:1.2.11.dfsg-1 [95.7 kB]
Get:41 http://cdn-fastly.deb.debian.org/debian buster/main i386 libpciaccess0 i386 0.14-1 [55.7 kB]
Get:42 http://cdn-fastly.deb.debian.org/debian buster/main i386 libdrm-intel1 i386 2.4.97-1 [72.9 kB]
Get:43 http://cdn-fastly.deb.debian.org/debian buster/main i386 libdrm-nouveau2 i386 2.4.97-1 [28.0 kB]
Get:44 http://cdn-fastly.deb.debian.org/debian buster/main i386 libdrm-radeon1 i386 2.4.97-1 [32.5 kB]
Get:45 http://cdn-fastly.deb.debian.org/debian buster/main i386 libtinfo6 i386 6.1+20181013-2 [326 kB]
Get:46 http://cdn-fastly.deb.debian.org/debian buster/main i386 libedit2 i386 3.1-20181209-1 [98.2 kB]
Get:47 http://cdn-fastly.deb.debian.org/debian buster/main i386 libexpat1 i386 2.2.6-2 [103 kB]
Get:48 http://cdn-fastly.deb.debian.org/debian buster/main i386 libffi6 i386 3.2.1-9 [20.0 kB]
Get:49 http://cdn-fastly.deb.debian.org/debian buster/main i386 libwayland-server0 i386 1.16.0-1 [33.7 kB]
Get:50 http://cdn-fastly.deb.debian.org/debian buster/main i386 libgbm1 i386 18.3.6-2 [69.4 kB]
Get:51 http://cdn-fastly.deb.debian.org/debian buster/main i386 libglapi-mesa i386 18.3.6-2 [66.0 kB]
Get:52 http://cdn-fastly.deb.debian.org/debian buster/main i386 libwayland-client0 i386 1.16.0-1 [27.0 kB]
Get:53 http://cdn-fastly.deb.debian.org/debian buster/main i386 libx11-xcb1 i386 2:1.6.7-1 [190 kB]
Get:54 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxau6 i386 1:1.0.8-1+b2 [20.3 kB]
Get:55 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxdmcp6 i386 1:1.1.2-3 [26.7 kB]
Get:56 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxcb1 i386 1.13.1-2 [141 kB]
Get:57 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxcb-dri2-0 i386 1.13.1-2 [101 kB]
Get:58 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxcb-dri3-0 i386 1.13.1-2 [101 kB]
Get:59 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxcb-present0 i386 1.13.1-2 [99.4 kB]
Get:60 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxcb-sync1 i386 1.13.1-2 [103 kB]
Get:61 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxcb-xfixes0 i386 1.13.1-2 [103 kB]
Get:62 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxshmfence1 i386 1.3-1 [8,976 B]
Get:63 http://cdn-fastly.deb.debian.org/debian buster/main i386 libegl-mesa0 i386 18.3.6-2 [142 kB]
Get:64 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libnvidia-eglcore i386 418.74-1 [6,222 kB]
Get:65 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libegl-nvidia0 i386 418.74-1 [416 kB]
Get:66 http://cdn-fastly.deb.debian.org/debian buster/main i386 libelf1 i386 0.176-1.1 [166 kB]
Get:67 http://cdn-fastly.deb.debian.org/debian buster/main i386 libstdc++6 i386 8.3.0-6 [424 kB]
Get:68 http://cdn-fastly.deb.debian.org/debian buster/main i386 libllvm7 i386 1:7.0.1-8 [13.0 MB]
Get:69 http://cdn-fastly.deb.debian.org/debian buster/main i386 libsensors5 i386 1:3.5.0-3 [53.5 kB]
Get:70 http://cdn-fastly.deb.debian.org/debian buster/main i386 libgl1-mesa-dri i386 18.3.6-2 [7,096 kB]
Get:71 http://cdn-fastly.deb.debian.org/debian buster/main i386 libglvnd0 i386 1.1.0-1 [41.9 kB]
Get:72 http://cdn-fastly.deb.debian.org/debian buster/main i386 libx11-6 i386 2:1.6.7-1 [778 kB]
Get:73 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxext6 i386 2:1.3.3-1+b2 [55.2 kB]
Get:74 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxcb-glx0 i386 1.13.1-2 [117 kB]
Get:75 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxfixes3 i386 1:5.0.3-1 [22.4 kB]
Get:76 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxdamage1 i386 1:1.1.4-3+b3 [15.0 kB]
Get:77 http://cdn-fastly.deb.debian.org/debian buster/main i386 libxxf86vm1 i386 1:1.1.4-1+b2 [21.7 kB]
Get:78 http://cdn-fastly.deb.debian.org/debian buster/main i386 libglx-mesa0 i386 18.3.6-2 [188 kB]
Get:79 http://cdn-fastly.deb.debian.org/debian buster/main i386 libglx0 i386 1.1.0-1 [31.3 kB]
Get:80 http://cdn-fastly.deb.debian.org/debian buster/main i386 libgl1 i386 1.1.0-1 [83.1 kB]
Get:81 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libnvidia-glcore i386 418.74-1 [6,311 kB]
Get:82 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libglx-nvidia0 i386 418.74-1 [446 kB]
Get:83 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libgl1-nvidia-glvnd-glx i386 418.74-1 [360 kB]
Get:84 http://cdn-fastly.deb.debian.org/debian buster/main i386 libgles1 i386 1.1.0-1 [13.9 kB]
Get:85 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libgles-nvidia1 i386 418.74-1 [217 kB]
Get:86 http://cdn-fastly.deb.debian.org/debian buster/main amd64 libgles1 amd64 1.1.0-1 [13.8 kB]
Get:87 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libgles-nvidia1 amd64 418.74-1 [221 kB]
Get:88 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libgles-nvidia2 amd64 418.74-1 [231 kB]
Get:89 http://cdn-fastly.deb.debian.org/debian buster/main i386 libgles2 i386 1.1.0-1 [18.8 kB]
Get:90 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libgles-nvidia2 i386 418.74-1 [224 kB]
Get:91 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvcuvid1 amd64 418.74-1 [898 kB]
Get:92 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-cbl amd64 418.74-1 [332 kB]
Get:93 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-encode1 amd64 418.74-1 [244 kB]
Get:94 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 libnvidia-glvkspirv i386 418.74-1 [4,661 kB]
Get:95 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-glvkspirv amd64 418.74-1 [4,332 kB]
Get:96 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 libnvidia-rtcore amd64 418.74-1 [7,100 kB]
Get:97 http://cdn-fastly.deb.debian.org/debian buster/main i386 libvulkan1 i386 1.1.97-2 [102 kB]
Get:98 http://cdn-fastly.deb.debian.org/debian buster/main i386 libegl1 i386 1.1.0-1 [35.3 kB]
Get:99 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 nvidia-egl-icd i386 418.74-1 [201 kB]
Get:100 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 nvidia-driver-libs i386 418.74-1 [202 kB]
Get:101 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 nvidia-driver-libs-i386 i386 418.74-1 [201 kB]
Get:102 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-smi amd64 418.74-1 [389 kB]
Get:103 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-vulkan-common amd64 418.74-1 [202 kB]
Get:104 http://cdn-fastly.deb.debian.org/debian buster/non-free i386 nvidia-vulkan-icd i386 418.74-1 [201 kB]
Get:105 http://cdn-fastly.deb.debian.org/debian buster/non-free amd64 nvidia-vulkan-icd amd64 418.74-1 [201 kB]
Get:106 http://cdn-fastly.deb.debian.org/debian buster/main i386 libopengl0 i386 1.1.0-1 [31.0 kB]
Get:107 http://cdn-fastly.deb.debian.org/debian buster/main amd64 libopengl0 amd64 1.1.0-1 [33.4 kB]
Preconfiguring packages ...
Fetched 103 MB in 5s (19.1 MB/s)
Selecting previously unselected package update-glx.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 268910 files and directories currently installed.)
Preparing to unpack .../update-glx_1.0.0_amd64.deb ...
Unpacking update-glx (1.0.0) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.0.0_amd64.deb ...
Unpacking glx-alternative-mesa (1.0.0) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20151021+9_amd64.deb ...
Unpacking nvidia-installer-cleanup (20151021+9) ...
Setting up nvidia-installer-cleanup (20151021+9) ...
Selecting previously unselected package glx-diversions.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 269010 files and directories currently installed.)
Preparing to unpack .../glx-diversions_1.0.0_amd64.deb ...
Unpacking glx-diversions (1.0.0) ...
Selecting previously unselected package glx-alternative-nvidia.
Preparing to unpack .../glx-alternative-nvidia_1.0.0_amd64.deb ...
Unpacking glx-alternative-nvidia (1.0.0) ...
Selecting previously unselected package nvidia-legacy-check.
Preparing to unpack .../nvidia-legacy-check_418.74-1_amd64.deb ...
Unpacking nvidia-legacy-check (418.74-1) ...
Selecting previously unselected package nvidia-support.
Preparing to unpack .../nvidia-support_20151021+9_amd64.deb ...
Unpacking nvidia-support (20151021+9) ...
Setting up nvidia-legacy-check (418.74-1) ...
Selecting previously unselected package nvidia-alternative.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 269046 files and directories currently installed.)
Preparing to unpack .../00-nvidia-alternative_418.74-1_amd64.deb ...
Unpacking nvidia-alternative (418.74-1) ...
Selecting previously unselected package libnvidia-ptxjitcompiler1:amd64.
Preparing to unpack .../01-libnvidia-ptxjitcompiler1_418.74-1_amd64.deb ...
Unpacking libnvidia-ptxjitcompiler1:amd64 (418.74-1) ...
Selecting previously unselected package libnvidia-fatbinaryloader:amd64.
Preparing to unpack .../02-libnvidia-fatbinaryloader_418.74-1_amd64.deb ...
Unpacking libnvidia-fatbinaryloader:amd64 (418.74-1) ...
Selecting previously unselected package libcuda1:amd64.
Preparing to unpack .../03-libcuda1_418.74-1_amd64.deb ...
Unpacking libcuda1:amd64 (418.74-1) ...
Selecting previously unselected package libnvidia-glcore:amd64.
Preparing to unpack .../04-libnvidia-glcore_418.74-1_amd64.deb ...
Unpacking libnvidia-glcore:amd64 (418.74-1) ...
Selecting previously unselected package libglx-nvidia0:amd64.
Preparing to unpack .../05-libglx-nvidia0_418.74-1_amd64.deb ...
Unpacking libglx-nvidia0:amd64 (418.74-1) ...
Selecting previously unselected package libgl1-nvidia-glvnd-glx:amd64.
Preparing to unpack .../06-libgl1-nvidia-glvnd-glx_418.74-1_amd64.deb ...
Unpacking libgl1-nvidia-glvnd-glx:amd64 (418.74-1) ...
Selecting previously unselected package nvidia-egl-common.
Preparing to unpack .../07-nvidia-egl-common_418.74-1_amd64.deb ...
Unpacking nvidia-egl-common (418.74-1) ...
Selecting previously unselected package libnvidia-eglcore:amd64.
Preparing to unpack .../08-libnvidia-eglcore_418.74-1_amd64.deb ...
Unpacking libnvidia-eglcore:amd64 (418.74-1) ...
Selecting previously unselected package libegl-nvidia0:amd64.
Preparing to unpack .../09-libegl-nvidia0_418.74-1_amd64.deb ...
Unpacking libegl-nvidia0:amd64 (418.74-1) ...
Selecting previously unselected package nvidia-egl-icd:amd64.
Preparing to unpack .../10-nvidia-egl-icd_418.74-1_amd64.deb ...
Unpacking nvidia-egl-icd:amd64 (418.74-1) ...
Selecting previously unselected package nvidia-driver-libs:amd64.
Preparing to unpack .../11-nvidia-driver-libs_418.74-1_amd64.deb ...
Unpacking nvidia-driver-libs:amd64 (418.74-1) ...
Selecting previously unselected package libnvidia-ml1:amd64.
Preparing to unpack .../12-libnvidia-ml1_418.74-1_amd64.deb ...
Unpacking libnvidia-ml1:amd64 (418.74-1) ...
Selecting previously unselected package nvidia-driver-bin.
Preparing to unpack .../13-nvidia-driver-bin_418.74-1_amd64.deb ...
Unpacking nvidia-driver-bin (418.74-1) ...
Selecting previously unselected package xserver-xorg-video-nvidia.
Preparing to unpack .../14-xserver-xorg-video-nvidia_418.74-1_amd64.deb ...
Unpacking xserver-xorg-video-nvidia (418.74-1) ...
Selecting previously unselected package nvidia-vdpau-driver:amd64.
Preparing to unpack .../15-nvidia-vdpau-driver_418.74-1_amd64.deb ...
Unpacking nvidia-vdpau-driver:amd64 (418.74-1) ...
Selecting previously unselected package nvidia-kernel-common.
Preparing to unpack .../16-nvidia-kernel-common_20151021+9_amd64.deb ...
Unpacking nvidia-kernel-common (20151021+9) ...
Selecting previously unselected package nvidia-modprobe.
Preparing to unpack .../17-nvidia-modprobe_418.56-1_amd64.deb ...
Unpacking nvidia-modprobe (418.56-1) ...
Selecting previously unselected package nvidia-kernel-support.
Preparing to unpack .../18-nvidia-kernel-support_418.74-1_amd64.deb ...
Unpacking nvidia-kernel-support (418.74-1) ...
Selecting previously unselected package nvidia-kernel-dkms.
Preparing to unpack .../19-nvidia-kernel-dkms_418.74-1_amd64.deb ...
Unpacking nvidia-kernel-dkms (418.74-1) ...
Selecting previously unselected package nvidia-driver.
Preparing to unpack .../20-nvidia-driver_418.74-1_amd64.deb ...
Unpacking nvidia-driver (418.74-1) ...
Selecting previously unselected package libnvidia-cfg1:amd64.
Preparing to unpack .../21-libnvidia-cfg1_418.74-1_amd64.deb ...
Unpacking libnvidia-cfg1:amd64 (418.74-1) ...
Selecting previously unselected package nvidia-persistenced.
Preparing to unpack .../22-nvidia-persistenced_418.56-1_amd64.deb ...
Unpacking nvidia-persistenced (418.56-1) ...
Selecting previously unselected package nvidia-settings.
Preparing to unpack .../23-nvidia-settings_418.74-1_amd64.deb ...
Unpacking nvidia-settings (418.74-1) ...
Selecting previously unselected package libatomic1:i386.
Preparing to unpack .../24-libatomic1_8.3.0-6_i386.deb ...
Unpacking libatomic1:i386 (8.3.0-6) ...
Selecting previously unselected package libbsd0:i386.
Preparing to unpack .../25-libbsd0_0.9.1-2_i386.deb ...
Unpacking libbsd0:i386 (0.9.1-2) ...
Selecting previously unselected package libnvidia-ptxjitcompiler1:i386.
Preparing to unpack .../26-libnvidia-ptxjitcompiler1_418.74-1_i386.deb ...
Unpacking libnvidia-ptxjitcompiler1:i386 (418.74-1) ...
Selecting previously unselected package libnvidia-fatbinaryloader:i386.
Preparing to unpack .../27-libnvidia-fatbinaryloader_418.74-1_i386.deb ...
Unpacking libnvidia-fatbinaryloader:i386 (418.74-1) ...
Selecting previously unselected package libcuda1:i386.
Preparing to unpack .../28-libcuda1_418.74-1_i386.deb ...
Unpacking libcuda1:i386 (418.74-1) ...
Selecting previously unselected package libcuda1-i386:i386.
Preparing to unpack .../29-libcuda1-i386_418.74-1_i386.deb ...
Unpacking libcuda1-i386:i386 (418.74-1) ...
Selecting previously unselected package libdrm2:i386.
Preparing to unpack .../30-libdrm2_2.4.97-1_i386.deb ...
Unpacking libdrm2:i386 (2.4.97-1) ...
Selecting previously unselected package libdrm-amdgpu1:i386.
Preparing to unpack .../31-libdrm-amdgpu1_2.4.97-1_i386.deb ...
Unpacking libdrm-amdgpu1:i386 (2.4.97-1) ...
Selecting previously unselected package zlib1g:i386.
Preparing to unpack .../32-zlib1g_1%3a1.2.11.dfsg-1_i386.deb ...
Unpacking zlib1g:i386 (1:1.2.11.dfsg-1) ...
Selecting previously unselected package libpciaccess0:i386.
Preparing to unpack .../33-libpciaccess0_0.14-1_i386.deb ...
Unpacking libpciaccess0:i386 (0.14-1) ...
Selecting previously unselected package libdrm-intel1:i386.
Preparing to unpack .../34-libdrm-intel1_2.4.97-1_i386.deb ...
Unpacking libdrm-intel1:i386 (2.4.97-1) ...
Selecting previously unselected package libdrm-nouveau2:i386.
Preparing to unpack .../35-libdrm-nouveau2_2.4.97-1_i386.deb ...
Unpacking libdrm-nouveau2:i386 (2.4.97-1) ...
Selecting previously unselected package libdrm-radeon1:i386.
Preparing to unpack .../36-libdrm-radeon1_2.4.97-1_i386.deb ...
Unpacking libdrm-radeon1:i386 (2.4.97-1) ...
Selecting previously unselected package libtinfo6:i386.
Preparing to unpack .../37-libtinfo6_6.1+20181013-2_i386.deb ...
Unpacking libtinfo6:i386 (6.1+20181013-2) ...
Selecting previously unselected package libedit2:i386.
Preparing to unpack .../38-libedit2_3.1-20181209-1_i386.deb ...
Unpacking libedit2:i386 (3.1-20181209-1) ...
Selecting previously unselected package libexpat1:i386.
Preparing to unpack .../39-libexpat1_2.2.6-2_i386.deb ...
Unpacking libexpat1:i386 (2.2.6-2) ...
Selecting previously unselected package libffi6:i386.
Preparing to unpack .../40-libffi6_3.2.1-9_i386.deb ...
Unpacking libffi6:i386 (3.2.1-9) ...
Selecting previously unselected package libwayland-server0:i386.
Preparing to unpack .../41-libwayland-server0_1.16.0-1_i386.deb ...
Unpacking libwayland-server0:i386 (1.16.0-1) ...
Selecting previously unselected package libgbm1:i386.
Preparing to unpack .../42-libgbm1_18.3.6-2_i386.deb ...
Unpacking libgbm1:i386 (18.3.6-2) ...
Selecting previously unselected package libglapi-mesa:i386.
Preparing to unpack .../43-libglapi-mesa_18.3.6-2_i386.deb ...
Unpacking libglapi-mesa:i386 (18.3.6-2) ...
Selecting previously unselected package libwayland-client0:i386.
Preparing to unpack .../44-libwayland-client0_1.16.0-1_i386.deb ...
Unpacking libwayland-client0:i386 (1.16.0-1) ...
Selecting previously unselected package libx11-xcb1:i386.
Preparing to unpack .../45-libx11-xcb1_2%3a1.6.7-1_i386.deb ...
Unpacking libx11-xcb1:i386 (2:1.6.7-1) ...
Selecting previously unselected package libxau6:i386.
Preparing to unpack .../46-libxau6_1%3a1.0.8-1+b2_i386.deb ...
Unpacking libxau6:i386 (1:1.0.8-1+b2) ...
Selecting previously unselected package libxdmcp6:i386.
Preparing to unpack .../47-libxdmcp6_1%3a1.1.2-3_i386.deb ...
Unpacking libxdmcp6:i386 (1:1.1.2-3) ...
Selecting previously unselected package libxcb1:i386.
Preparing to unpack .../48-libxcb1_1.13.1-2_i386.deb ...
Unpacking libxcb1:i386 (1.13.1-2) ...
Selecting previously unselected package libxcb-dri2-0:i386.
Preparing to unpack .../49-libxcb-dri2-0_1.13.1-2_i386.deb ...
Unpacking libxcb-dri2-0:i386 (1.13.1-2) ...
Selecting previously unselected package libxcb-dri3-0:i386.
Preparing to unpack .../50-libxcb-dri3-0_1.13.1-2_i386.deb ...
Unpacking libxcb-dri3-0:i386 (1.13.1-2) ...
Selecting previously unselected package libxcb-present0:i386.
Preparing to unpack .../51-libxcb-present0_1.13.1-2_i386.deb ...
Unpacking libxcb-present0:i386 (1.13.1-2) ...
Selecting previously unselected package libxcb-sync1:i386.
Preparing to unpack .../52-libxcb-sync1_1.13.1-2_i386.deb ...
Unpacking libxcb-sync1:i386 (1.13.1-2) ...
Selecting previously unselected package libxcb-xfixes0:i386.
Preparing to unpack .../53-libxcb-xfixes0_1.13.1-2_i386.deb ...
Unpacking libxcb-xfixes0:i386 (1.13.1-2) ...
Selecting previously unselected package libxshmfence1:i386.
Preparing to unpack .../54-libxshmfence1_1.3-1_i386.deb ...
Unpacking libxshmfence1:i386 (1.3-1) ...
Selecting previously unselected package libegl-mesa0:i386.
Preparing to unpack .../55-libegl-mesa0_18.3.6-2_i386.deb ...
Unpacking libegl-mesa0:i386 (18.3.6-2) ...
Selecting previously unselected package libnvidia-eglcore:i386.
Preparing to unpack .../56-libnvidia-eglcore_418.74-1_i386.deb ...
Unpacking libnvidia-eglcore:i386 (418.74-1) ...
Selecting previously unselected package libegl-nvidia0:i386.
Preparing to unpack .../57-libegl-nvidia0_418.74-1_i386.deb ...
Unpacking libegl-nvidia0:i386 (418.74-1) ...
Selecting previously unselected package libelf1:i386.
Preparing to unpack .../58-libelf1_0.176-1.1_i386.deb ...
Unpacking libelf1:i386 (0.176-1.1) ...
Selecting previously unselected package libstdc++6:i386.
Preparing to unpack .../59-libstdc++6_8.3.0-6_i386.deb ...
Unpacking libstdc++6:i386 (8.3.0-6) ...
Selecting previously unselected package libllvm7:i386.
Preparing to unpack .../60-libllvm7_1%3a7.0.1-8_i386.deb ...
Unpacking libllvm7:i386 (1:7.0.1-8) ...
Selecting previously unselected package libsensors5:i386.
Preparing to unpack .../61-libsensors5_1%3a3.5.0-3_i386.deb ...
Unpacking libsensors5:i386 (1:3.5.0-3) ...
Selecting previously unselected package libgl1-mesa-dri:i386.
Preparing to unpack .../62-libgl1-mesa-dri_18.3.6-2_i386.deb ...
Unpacking libgl1-mesa-dri:i386 (18.3.6-2) ...
Selecting previously unselected package libglvnd0:i386.
Preparing to unpack .../63-libglvnd0_1.1.0-1_i386.deb ...
Unpacking libglvnd0:i386 (1.1.0-1) ...
Selecting previously unselected package libx11-6:i386.
Preparing to unpack .../64-libx11-6_2%3a1.6.7-1_i386.deb ...
Unpacking libx11-6:i386 (2:1.6.7-1) ...
Selecting previously unselected package libxext6:i386.
Preparing to unpack .../65-libxext6_2%3a1.3.3-1+b2_i386.deb ...
Unpacking libxext6:i386 (2:1.3.3-1+b2) ...
Selecting previously unselected package libxcb-glx0:i386.
Preparing to unpack .../66-libxcb-glx0_1.13.1-2_i386.deb ...
Unpacking libxcb-glx0:i386 (1.13.1-2) ...
Selecting previously unselected package libxfixes3:i386.
Preparing to unpack .../67-libxfixes3_1%3a5.0.3-1_i386.deb ...
Unpacking libxfixes3:i386 (1:5.0.3-1) ...
Selecting previously unselected package libxdamage1:i386.
Preparing to unpack .../68-libxdamage1_1%3a1.1.4-3+b3_i386.deb ...
Unpacking libxdamage1:i386 (1:1.1.4-3+b3) ...
Selecting previously unselected package libxxf86vm1:i386.
Preparing to unpack .../69-libxxf86vm1_1%3a1.1.4-1+b2_i386.deb ...
Unpacking libxxf86vm1:i386 (1:1.1.4-1+b2) ...
Selecting previously unselected package libglx-mesa0:i386.
Preparing to unpack .../70-libglx-mesa0_18.3.6-2_i386.deb ...
Unpacking libglx-mesa0:i386 (18.3.6-2) ...
Selecting previously unselected package libglx0:i386.
Preparing to unpack .../71-libglx0_1.1.0-1_i386.deb ...
Unpacking libglx0:i386 (1.1.0-1) ...
Selecting previously unselected package libgl1:i386.
Preparing to unpack .../72-libgl1_1.1.0-1_i386.deb ...
Unpacking libgl1:i386 (1.1.0-1) ...
Selecting previously unselected package libnvidia-glcore:i386.
Preparing to unpack .../73-libnvidia-glcore_418.74-1_i386.deb ...
Unpacking libnvidia-glcore:i386 (418.74-1) ...
Selecting previously unselected package libglx-nvidia0:i386.
Preparing to unpack .../74-libglx-nvidia0_418.74-1_i386.deb ...
Unpacking libglx-nvidia0:i386 (418.74-1) ...
Selecting previously unselected package libgl1-nvidia-glvnd-glx:i386.
Preparing to unpack .../75-libgl1-nvidia-glvnd-glx_418.74-1_i386.deb ...
Unpacking libgl1-nvidia-glvnd-glx:i386 (418.74-1) ...
Selecting previously unselected package libgles1:i386.
Preparing to unpack .../76-libgles1_1.1.0-1_i386.deb ...
Unpacking libgles1:i386 (1.1.0-1) ...
Selecting previously unselected package libgles-nvidia1:i386.
Preparing to unpack .../77-libgles-nvidia1_418.74-1_i386.deb ...
Unpacking libgles-nvidia1:i386 (418.74-1) ...
Selecting previously unselected package libgles1:amd64.
Preparing to unpack .../78-libgles1_1.1.0-1_amd64.deb ...
Unpacking libgles1:amd64 (1.1.0-1) ...
Selecting previously unselected package libgles-nvidia1:amd64.
Preparing to unpack .../79-libgles-nvidia1_418.74-1_amd64.deb ...
Unpacking libgles-nvidia1:amd64 (418.74-1) ...
Selecting previously unselected package libgles-nvidia2:amd64.
Preparing to unpack .../80-libgles-nvidia2_418.74-1_amd64.deb ...
Unpacking libgles-nvidia2:amd64 (418.74-1) ...
Selecting previously unselected package libgles2:i386.
Preparing to unpack .../81-libgles2_1.1.0-1_i386.deb ...
Unpacking libgles2:i386 (1.1.0-1) ...
Selecting previously unselected package libgles-nvidia2:i386.
Preparing to unpack .../82-libgles-nvidia2_418.74-1_i386.deb ...
Unpacking libgles-nvidia2:i386 (418.74-1) ...
Selecting previously unselected package libnvcuvid1:amd64.
Preparing to unpack .../83-libnvcuvid1_418.74-1_amd64.deb ...
Unpacking libnvcuvid1:amd64 (418.74-1) ...
Selecting previously unselected package libnvidia-cbl:amd64.
Preparing to unpack .../84-libnvidia-cbl_418.74-1_amd64.deb ...
Unpacking libnvidia-cbl:amd64 (418.74-1) ...
Selecting previously unselected package libnvidia-encode1:amd64.
Preparing to unpack .../85-libnvidia-encode1_418.74-1_amd64.deb ...
Unpacking libnvidia-encode1:amd64 (418.74-1) ...
Selecting previously unselected package libnvidia-glvkspirv:i386.
Preparing to unpack .../86-libnvidia-glvkspirv_418.74-1_i386.deb ...
Unpacking libnvidia-glvkspirv:i386 (418.74-1) ...
Selecting previously unselected package libnvidia-glvkspirv:amd64.
Preparing to unpack .../87-libnvidia-glvkspirv_418.74-1_amd64.deb ...
Unpacking libnvidia-glvkspirv:amd64 (418.74-1) ...
Selecting previously unselected package libnvidia-rtcore:amd64.
Preparing to unpack .../88-libnvidia-rtcore_418.74-1_amd64.deb ...
Unpacking libnvidia-rtcore:amd64 (418.74-1) ...
Selecting previously unselected package libvulkan1:i386.
Preparing to unpack .../89-libvulkan1_1.1.97-2_i386.deb ...
Unpacking libvulkan1:i386 (1.1.97-2) ...
Selecting previously unselected package libegl1:i386.
Preparing to unpack .../90-libegl1_1.1.0-1_i386.deb ...
Unpacking libegl1:i386 (1.1.0-1) ...
Selecting previously unselected package nvidia-egl-icd:i386.
Preparing to unpack .../91-nvidia-egl-icd_418.74-1_i386.deb ...
Unpacking nvidia-egl-icd:i386 (418.74-1) ...
Selecting previously unselected package nvidia-driver-libs:i386.
Preparing to unpack .../92-nvidia-driver-libs_418.74-1_i386.deb ...
Unpacking nvidia-driver-libs:i386 (418.74-1) ...
Selecting previously unselected package nvidia-driver-libs-i386:i386.
Preparing to unpack .../93-nvidia-driver-libs-i386_418.74-1_i386.deb ...
Unpacking nvidia-driver-libs-i386:i386 (418.74-1) ...
Selecting previously unselected package nvidia-smi.
Preparing to unpack .../94-nvidia-smi_418.74-1_amd64.deb ...
Unpacking nvidia-smi (418.74-1) ...
Selecting previously unselected package nvidia-vulkan-common.
Preparing to unpack .../95-nvidia-vulkan-common_418.74-1_amd64.deb ...
Unpacking nvidia-vulkan-common (418.74-1) ...
Selecting previously unselected package nvidia-vulkan-icd:i386.
Preparing to unpack .../96-nvidia-vulkan-icd_418.74-1_i386.deb ...
Unpacking nvidia-vulkan-icd:i386 (418.74-1) ...
Selecting previously unselected package nvidia-vulkan-icd:amd64.
Preparing to unpack .../97-nvidia-vulkan-icd_418.74-1_amd64.deb ...
Unpacking nvidia-vulkan-icd:amd64 (418.74-1) ...
Selecting previously unselected package libopengl0:i386.
Preparing to unpack .../98-libopengl0_1.1.0-1_i386.deb ...
Unpacking libopengl0:i386 (1.1.0-1) ...
Selecting previously unselected package libopengl0:amd64.
Preparing to unpack .../99-libopengl0_1.1.0-1_amd64.deb ...
Unpacking libopengl0:amd64 (1.1.0-1) ...
Setting up nvidia-support (20151021+9) ...
Setting up libnvidia-glvkspirv:amd64 (418.74-1) ...
Setting up libnvidia-glvkspirv:i386 (418.74-1) ...
Setting up libexpat1:i386 (2.2.6-2) ...
Setting up libnvidia-eglcore:amd64 (418.74-1) ...
Setting up libnvidia-eglcore:i386 (418.74-1) ...
Setting up libx11-xcb1:i386 (2:1.6.7-1) ...
Setting up libxau6:i386 (1:1.0.8-1+b2) ...
Setting up nvidia-egl-common (418.74-1) ...
Setting up nvidia-kernel-common (20151021+9) ...
Setting up libglvnd0:i386 (1.1.0-1) ...
Setting up zlib1g:i386 (1:1.2.11.dfsg-1) ...
Setting up libffi6:i386 (3.2.1-9) ...
Setting up update-glx (1.0.0) ...
Setting up libopengl0:amd64 (1.1.0-1) ...
Setting up libopengl0:i386 (1.1.0-1) ...
Setting up nvidia-modprobe (418.56-1) ...
Setting up libgles2:i386 (1.1.0-1) ...
Setting up libgles1:amd64 (1.1.0-1) ...
Setting up libgles1:i386 (1.1.0-1) ...
Setting up libatomic1:i386 (8.3.0-6) ...
Setting up libsensors5:i386 (1:3.5.0-3) ...
Setting up libnvidia-glcore:amd64 (418.74-1) ...
Setting up libnvidia-glcore:i386 (418.74-1) ...
Setting up libglapi-mesa:i386 (18.3.6-2) ...
Setting up libvulkan1:i386 (1.1.97-2) ...
Setting up libnvidia-ptxjitcompiler1:amd64 (418.74-1) ...
Setting up libnvidia-ptxjitcompiler1:i386 (418.74-1) ...
Setting up libdrm2:i386 (2.4.97-1) ...
Setting up nvidia-vulkan-common (418.74-1) ...
Setting up libxshmfence1:i386 (1.3-1) ...
Setting up libnvidia-fatbinaryloader:amd64 (418.74-1) ...
Setting up libnvidia-fatbinaryloader:i386 (418.74-1) ...
Setting up libbsd0:i386 (0.9.1-2) ...
Setting up libelf1:i386 (0.176-1.1) ...
Setting up libstdc++6:i386 (8.3.0-6) ...
Setting up libtinfo6:i386 (6.1+20181013-2) ...
Setting up libnvidia-rtcore:amd64 (418.74-1) ...
Setting up libdrm-amdgpu1:i386 (2.4.97-1) ...
Setting up libwayland-client0:i386 (1.16.0-1) ...
Setting up libwayland-server0:i386 (1.16.0-1) ...
Setting up libnvidia-cbl:amd64 (418.74-1) ...
Setting up libpciaccess0:i386 (0.14-1) ...
Setting up libxdmcp6:i386 (1:1.1.2-3) ...
Setting up libdrm-nouveau2:i386 (2.4.97-1) ...
Setting up libxcb1:i386 (1.13.1-2) ...
Setting up libxcb-xfixes0:i386 (1.13.1-2) ...
Setting up libgbm1:i386 (18.3.6-2) ...
Setting up libdrm-radeon1:i386 (2.4.97-1) ...
Setting up libxcb-glx0:i386 (1.13.1-2) ...
Setting up libedit2:i386 (3.1-20181209-1) ...
Setting up libdrm-intel1:i386 (2.4.97-1) ...
Setting up glx-alternative-mesa (1.0.0) ...
Setting up libxcb-present0:i386 (1.13.1-2) ...
Setting up libxcb-sync1:i386 (1.13.1-2) ...
Setting up glx-diversions (1.0.0) ...
Setting up libxcb-dri2-0:i386 (1.13.1-2) ...
Setting up libllvm7:i386 (1:7.0.1-8) ...
Setting up libx11-6:i386 (2:1.6.7-1) ...
Setting up libxcb-dri3-0:i386 (1.13.1-2) ...
Setting up libgl1-mesa-dri:i386 (18.3.6-2) ...
Setting up libxext6:i386 (2:1.3.3-1+b2) ...
Setting up libxxf86vm1:i386 (1:1.1.4-1+b2) ...
Setting up libegl-mesa0:i386 (18.3.6-2) ...
Setting up libxfixes3:i386 (1:5.0.3-1) ...
Setting up libegl1:i386 (1.1.0-1) ...
Setting up libxdamage1:i386 (1:1.1.4-3+b3) ...
Setting up libglx-mesa0:i386 (18.3.6-2) ...
Setting up libglx0:i386 (1.1.0-1) ...
Setting up libgl1:i386 (1.1.0-1) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for systemd (1:241-5+mx19+2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for glx-alternative-mesa (1.0.0) ...
update-alternatives: using /usr/lib/mesa-diverted to provide /usr/lib/glx (glx) in auto mode
Setting up glx-alternative-nvidia (1.0.0) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for glx-alternative-nvidia (1.0.0) ...
Setting up nvidia-alternative (418.74-1) ...
Processing triggers for nvidia-alternative (418.74-1) ...
update-alternatives: using /usr/lib/nvidia/current to provide /usr/lib/nvidia/nvidia (nvidia) in auto mode
Setting up libnvidia-ml1:amd64 (418.74-1) ...
Setting up libcuda1:amd64 (418.74-1) ...
Setting up libcuda1:i386 (418.74-1) ...
Setting up libnvidia-cfg1:amd64 (418.74-1) ...
Setting up libglx-nvidia0:amd64 (418.74-1) ...
Setting up libglx-nvidia0:i386 (418.74-1) ...
Setting up nvidia-kernel-support (418.74-1) ...
Setting up xserver-xorg-video-nvidia (418.74-1) ...
Setting up libcuda1-i386:i386 (418.74-1) ...
Setting up nvidia-vulkan-icd:amd64 (418.74-1) ...
Setting up nvidia-vulkan-icd:i386 (418.74-1) ...
Setting up nvidia-vdpau-driver:amd64 (418.74-1) ...
Setting up libgl1-nvidia-glvnd-glx:amd64 (418.74-1) ...
Setting up libgl1-nvidia-glvnd-glx:i386 (418.74-1) ...
Setting up libgles-nvidia1:amd64 (418.74-1) ...
Setting up libgles-nvidia1:i386 (418.74-1) ...
Setting up libegl-nvidia0:amd64 (418.74-1) ...
Setting up libegl-nvidia0:i386 (418.74-1) ...
Setting up nvidia-settings (418.74-1) ...
Setting up nvidia-smi (418.74-1) ...
Setting up libgles-nvidia2:amd64 (418.74-1) ...
Setting up libgles-nvidia2:i386 (418.74-1) ...
Setting up nvidia-driver-bin (418.74-1) ...
Setting up libnvcuvid1:amd64 (418.74-1) ...
Setting up nvidia-persistenced (418.56-1) ...
Warning: The home dir /var/run/nvpd/ you specified can't be accessed: No such file or directory
Adding system user `nvpd' (UID 119) ...
Adding new group `nvpd' (GID 129) ...
Adding new user `nvpd' (UID 119) with group `nvpd' ...
Not creating home directory `/var/run/nvpd/'.
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Setting up nvidia-egl-icd:amd64 (418.74-1) ...
Setting up nvidia-egl-icd:i386 (418.74-1) ...
Setting up libnvidia-encode1:amd64 (418.74-1) ...
Setting up nvidia-driver-libs:amd64 (418.74-1) ...
Setting up nvidia-driver-libs:i386 (418.74-1) ...
Setting up nvidia-driver-libs-i386:i386 (418.74-1) ...
Processing triggers for nvidia-alternative (418.74-1) ...
update-alternatives: updating alternative /usr/lib/nvidia/current because link group nvidia has changed slave links
Setting up nvidia-kernel-dkms (418.74-1) ...
Loading new nvidia-current-418.74 DKMS files...
Building for 4.19.0-5-amd64
Building initial module for 4.19.0-5-amd64
Done.
nvidia-current.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
nvidia-current-modeset.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
nvidia-current-drm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
nvidia-current-uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
DKMS: install completed.
Setting up nvidia-driver (418.74-1) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/sdc1
I: (UUID=29031897-5548-499e-962b-b264dd7bd948)
I: Set the RESUME variable to override this.
Processing triggers for update-glx (1.0.0) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in auto mode
Processing triggers for glx-alternative-mesa (1.0.0) ...
Processing triggers for systemd (1:241-5+mx19+2) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/sdc1
I: (UUID=29031897-5548-499e-962b-b264dd7bd948)
I: Set the RESUME variable to override this.
Errors were encountered while processing:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
Finished
Press <Enter> to exit
Ah I missed that error there.. anyway.. yeah.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:25 am
by dolphin_oracle
zebedeeboss wrote: Tue Aug 27, 2019 9:09 am
Got it installed using the same method used in antiX19 :D
This works on an RTX series Card
1 Boot to live USB
2 drop to tty login as root (it will probably do this auto due to RTX issues - this is Linux wide and not anything specific to do with Antix)
3 perform a full update & upgrade
4 run nvidia cli commands as per Dolphin instructions - see below
sudo apt install --install-recommends nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
5 run cli-installer
6 reboot
Regards Zeb...
Zeb, did that pull in nvidia-persistenced?
in our user's case here, the drivers are installed but there is an error in the nvidia-persistenced installation.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:30 am
by dolphin_oracle
@ER - nvidia installer does not touch grub
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:32 am
by dolphin_oracle
um...debian is apparently updating nvidia this morning. in the last hour the drivers have bumped from 418.56 to 418.74, including persistenced (in the last 10 minutes). so maybe try again to install nvidia-persistenced. could be a conflict in package versions...
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:39 am
by Eadwine Rose
Newer version is not here yet, not in testing either.
Reinstall gives: E: Internal Error, No file name for nvidia-persistenced:amd64
I wager things are still propagating across the repos or something. Dang, what timing!
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:40 am
by Eadwine Rose
I encountered a little looks thing, moved the panel to the bottom and got this. The wired Synaptic icon behaved the same way.
Screenshot.png
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 10:07 am
by Eadwine Rose
mcury wrote: Tue Aug 27, 2019 6:27 am
I'm getting errors during codecs install, first installed nvidia driver, which worked.
Performed a reboot, installed the codecs and when it was around 99% (Fix missing dependencies), it presented me an error: Error running 'apt-get -fm install' command.
Just stating for the record that I have this happening here as well.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 10:15 am
by zebedeeboss
dolphin_oracle wrote: Tue Aug 27, 2019 9:25 am
zebedeeboss wrote: Tue Aug 27, 2019 9:09 am
Got it installed using the same method used in antiX19 :D
This works on an RTX series Card
1 Boot to live USB
2 drop to tty login as root (it will probably do this auto due to RTX issues - this is Linux wide and not anything specific to do with Antix)
3 perform a full update & upgrade
4 run nvidia cli commands as per Dolphin instructions - see below
sudo apt install --install-recommends nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
5 run cli-installer
6 reboot
Regards Zeb...
Zeb, did that pull in nvidia-persistenced?
in our user's case here, the drivers are installed but there is an error in the nvidia-persistenced installation.
complete file here
Hi, Yes it did, here is the end of an apt dist-upgrade
Code: Select all
Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
zebedee@mx-2950x:~
Regards Zeb...
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 10:23 am
by Eadwine Rose
dolphin_oracle wrote: Tue Aug 27, 2019 9:30 am
@ER - nvidia installer does not touch grub
Noob grub user error, have never fiddled in that section there. I had grub set to possibly save last boot option. Now I know what that means
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 10:27 am
by bigbenaugust
I just slapped 19b1 on my Lenovo W530 and I went to set up the work VPN (openconnect) to see if I could reproduce the issue I have at home with my MX 18.3 machines, (namely that that I get a 404 and a "can't do HTTP 1.0" sort of an error from openconnect in NetworkManager, but it runs fine from the CLI).
I go to the NetworkManager applet, down to VPN Connections, click Add a VPN Connection, and see that openconnect is an option, so the bits are all installed.
But I select the Cisco OpenConnect option and the VPN tab is missing, so I can't actually configure the connection.
For comparison, my BunsenLabs Lithium box (also Deb 10 based), there is a VPN tab there and I can configure it.
I did notice that MX 19b1 is missing the network-manager-openconnect-gnome package, but BL has it installed.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 10:37 am
by anticapitalista
bigbenaugust wrote: Tue Aug 27, 2019 10:27 am
I did notice that MX 19b1 is missing the network-manager-openconnect-gnome package, but BL has it installed.
So, if you install that package, does it solve your problem? If it does, then perhaps it should be included on the iso.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 10:43 am
by bigbenaugust
anticapitalista wrote: Tue Aug 27, 2019 10:37 am
bigbenaugust wrote: Tue Aug 27, 2019 10:27 am
I did notice that MX 19b1 is missing the network-manager-openconnect-gnome package, but BL has it installed.
So, if you install that package, does it solve your problem? If it does, then perhaps it should be included on the iso.
Well, you can all slap me now.
I did a
Code: Select all
sudo apt search network-manager-openconnect-gnome
and it returned nothing at all, so I was curious if y'all were hiding the package for some reason.
But this is a fresh install and a
is necessary first. Oops.
So that works and it actually connects, unlike MX 18! Thanks, I'll go back to feeling silly now.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:06 am
by dolphin_oracle
Eadwine Rose wrote: Tue Aug 27, 2019 10:07 am
mcury wrote: Tue Aug 27, 2019 6:27 am
I'm getting errors during codecs install, first installed nvidia driver, which worked.
Performed a reboot, installed the codecs and when it was around 99% (Fix missing dependencies), it presented me an error: Error running 'apt-get -fm install' command.
Just stating for the record that I have this happening here as well.
you nvidia users...
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:09 am
by dolphin_oracle
zebedeeboss wrote: Tue Aug 27, 2019 10:15 am
dolphin_oracle wrote: Tue Aug 27, 2019 9:25 am
zebedeeboss wrote: Tue Aug 27, 2019 9:09 am
Got it installed using the same method used in antiX19 :D
This works on an RTX series Card
1 Boot to live USB
2 drop to tty login as root (it will probably do this auto due to RTX issues - this is Linux wide and not anything specific to do with Antix)
3 perform a full update & upgrade
4 run nvidia cli commands as per Dolphin instructions - see below
sudo apt install --install-recommends nvidia-driver nvidia-settings nvidia-kernel-dkms libnvidia-encode1
5 run cli-installer
6 reboot
Regards Zeb...
Zeb, did that pull in nvidia-persistenced?
in our user's case here, the drivers are installed but there is an error in the nvidia-persistenced installation.
complete file here
Hi, Yes it did, here is the end of an apt dist-upgrade
Code: Select all
Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
zebedee@mx-2950x:~
Regards Zeb...
thanks. confirms my suspicion that debian is mucking this up this morning. might be OK later today.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:15 am
by Dede
Paul.. wrote: Tue Aug 27, 2019 7:38 am
Dede wrote: Tue Aug 27, 2019 4:22 am
Root Terminal disappeared?
Please elaborate. Your comment as it appears is not helpful to developers without more details.
It's not in the system, I can't find it anywhere...
Re: MX-19 Beta 1 Feedback nvidia-persistenced
Posted: Tue Aug 27, 2019 11:19 am
by entropyfoe
Here is the tail of that ddm.log for the nvidia-persistenced error. I am not sure how big a deal this is, nvidia is loaded, working, and video with comptom compositing is working fine.
Code: Select all
Setting up nvidia-persistenced (418.56-1) ...
Warning: The home dir /var/run/nvpd/ you specified can't be accessed: No such file or directory
Adding system user `nvpd' (UID 119) ...
Adding new group `nvpd' (GID 129) ...
Adding new user `nvpd' (UID 119) with group `nvpd' ...
Not creating home directory `/var/run/nvpd/'.
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Setting up nvidia-egl-icd:amd64 (418.74-1) ...
Setting up nvidia-egl-icd:i386 (418.74-1) ...
Setting up libnvidia-encode1:amd64 (418.74-1) ...
Setting up nvidia-driver-libs:amd64 (418.74-1) ...
Setting up nvidia-driver-libs:i386 (418.74-1) ...
Setting up nvidia-driver-libs-i386:i386 (418.74-1) ...
Processing triggers for nvidia-alternative (418.74-1) ...
update-alternatives: updating alternative /usr/lib/nvidia/current because link group nvidia has changed slave links
Setting up nvidia-kernel-dkms (418.74-1) ...
Loading new nvidia-current-418.74 DKMS files...
Building for 4.19.0-5-amd64
Building initial module for 4.19.0-5-amd64
Done.
nvidia-current.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
nvidia-current-modeset.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
nvidia-current-drm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
nvidia-current-uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
DKMS: install completed.
Setting up nvidia-driver (418.74-1) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/nvme0n1p2
I: (UUID=4ce88423-c5cf-4a69-b6d4-1d9fcafa7353)
I: Set the RESUME variable to override this.
Processing triggers for update-glx (1.0.0) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in auto mode
Processing triggers for glx-alternative-mesa (1.0.0) ...
Processing triggers for systemd (1:241-5+mx19+2) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/nvme0n1p2
I: (UUID=4ce88423-c5cf-4a69-b6d4-1d9fcafa7353)
I: Set the RESUME variable to override this.
Errors were encountered while processing:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
Finished
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:20 am
by Eadwine Rose
dolphin_oracle wrote: Tue Aug 27, 2019 11:06 am
Eadwine Rose wrote: Tue Aug 27, 2019 10:07 am
mcury wrote: Tue Aug 27, 2019 6:27 am
I'm getting errors during codecs install, first installed nvidia driver, which worked.
Performed a reboot, installed the codecs and when it was around 99% (Fix missing dependencies), it presented me an error: Error running 'apt-get -fm install' command.
Just stating for the record that I have this happening here as well.
you nvidia users...
Yeah.. I know.. we're an annoying lot huh.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:25 am
by fehlix
Dede wrote: Tue Aug 27, 2019 11:15 am
Paul.. wrote: Tue Aug 27, 2019 7:38 am
Dede wrote: Tue Aug 27, 2019 4:22 am
Root Terminal disappeared?
Please elaborate. Your comment as it appears is not helpful to developers without more details.
It's not in the system, I can't find it anywhere...
Seems "Root Terminal" menu entry didn't made into beta-1.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:33 am
by dolphin_oracle
for you guys with the nvidia-persistenced problem, I think just remove it for now.
Code: Select all
sudo apt purge nvidia-persistenced -s
and if it looks like your system will survive then run it again without the -s.
once debian settles down you can reinstall it.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:39 am
by Eadwine Rose
*bookmarks page* I'll get back to this tomorrow I think, should be sorted by then I wager.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:41 am
by TheLamerLinux
dolphin_oracle wrote: Tue Aug 27, 2019 11:33 am
for you guys with the nvidia-persistenced problem, I think just remove it for now.
Code: Select all
sudo apt purge nvidia-persistenced -s
and if it looks like your system will survive then run it again without the -s.
once debian settles down you can reinstall it.
Thanks Dolphin I was about to post this on the forums, I found another bug (idk if you would call it a bug), when you install Chromium from the MX Package Manager and also from the Terminal you can't open Chromium till you install chromium-sandbox. Probably need to add that line in the MX Package Manager.
Other than that Dolphin awesome MX 19 beta really loving it
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:53 am
by entropyfoe
I rebooted, nvidia still working, no errors. I did a synaptic reload on the repositories, no updates, no nvidia error messages. the nvidia-persistenced shows as installed in synaptic version 418.74.
Still no samba shares on the home network, which usually happens automagically!
Any ideas on this? Does anyone have samba shares on their network?
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 11:54 am
by Eadwine Rose
entropyfoe wrote: Tue Aug 27, 2019 11:53 am
I rebooted, nvidia still working, no errors. I did a synaptic reload on the repositories, no updates, no nvidia error messages. the nvidia-persistenced shows as installed in synaptic version 418.74.
Still no samba shares on the home network, which usually happens automagically!
Any ideas on this? Does anyone have samba shares on their network?
Have you tried installing something else already?
Nothing seemed amiss until I did that and found out. If you don't get that error then it's at least sorted on your end :)
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 12:04 pm
by dolphin_oracle
TheLamerLinux wrote: Tue Aug 27, 2019 11:41 am
dolphin_oracle wrote: Tue Aug 27, 2019 11:33 am
for you guys with the nvidia-persistenced problem, I think just remove it for now.
Code: Select all
sudo apt purge nvidia-persistenced -s
and if it looks like your system will survive then run it again without the -s.
once debian settles down you can reinstall it.
Thanks Dolphin I was about to post this on the forums, I found another bug (idk if you would call it a bug), when you install Chromium from the MX Package Manager and also from the Terminal you can't open Chromium till you install chromium-sandbox. Probably need to add that line in the MX Package Manager.
Other than that Dolphin awesome MX 19 beta really loving it
nice lamer, thanks!
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 1:47 pm
by entropyfoe
Can anyone see samba shares on your local network?
I usually see a windows 7 machine I can log into shares. No configuration needed, it is there in the file manager, Network, browse network.
I click the Windows network icon, and I get smb:///
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 1:50 pm
by chrispop99
entropyfoe wrote: Tue Aug 27, 2019 1:47 pm
Can anyone see samba shares on your local network?
I usually see a windows 7 machine I can log into shares. No configuration needed, it is there in the file manager, Network, browse network.
I click the Windows network icon, and I get smb:///
Yes, same here.
Chris
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 2:04 pm
by entropyfoe
OK, so all my testing (antix 19 beta , MX 19 beta) - I do on a fourth partition, so I can boot back to my working MX 18.3 and see hwo it is working.
In response to smb://mshome/, which produces a list of machines on the network, including the windows 7 machine, which I can log in to.
Instead the beta displays a pop up window stating: Failed to open "File System"
Failed to retrieve share list from server: Success."
Hmmm, does not sound like success to me.
On a better note, I really like the FAQ. It is great for those new to MX, well written.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 2:13 pm
by asqwerth
I seem to recall in Manjaro that in the past year I have had difficulty getting my NAS connecting via smb (from the file manager), so I use a diff protocol in the file manager options (ftp and afp, I think).
I also recall some complaints about this in Dedoimedo's reviews?
e.g.
https://www.dedoimedo.com/computers/man ... lasma.html
his previous workaround:
https://www.dedoimedo.com/computers/ubu ... hares.html
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 2:16 pm
by duane
MX Conkypatch conky shows different date on calendar than on line in conky.
calendar says 23 line says 27th.
I don't like the colors selected for the terminal but those are easily changed.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 2:26 pm
by dolphin_oracle
I can connect directly to my samba shares, but the browse feature does not work (in my case,didn't work under mx17/18 either).
smb:///servername/sharename
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 2:37 pm
by Gerson
Taskbar icons don't show well, I tried several pre-installed themes.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 2:38 pm
by dolphin_oracle
Gerson wrote: Tue Aug 27, 2019 2:37 pm
Taskbar icons don't show well, I tried several pre-installed themes.
any change if you turn off the frame?
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 2:41 pm
by Gerson
dolphin_oracle wrote: Tue Aug 27, 2019 2:38 pm
Gerson wrote: Tue Aug 27, 2019 2:37 pm
Taskbar icons don't show well, I tried several pre-installed themes.
any change if you turn off the frame?
Corrected by removing the frame.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 2:47 pm
by Stevo
Can anyone test if the nvidia-persistenced file installs successfully if you boot with systemd?
I did get the same error message on my Optimus system weeks ago when I tried a backport of the 430 driver from experimental, which didn't work, so reinstalled our MX 18 test repo version of 418.74 from my local repo. But I just removed the package to no ill effect to fix that issue. I couldn't figure out what package was pulling it in either...maybe our installer could remove it as the last step if it's present and then fix the system.
I know it's an ugly workaround, but the alternative is to find out what's pulling it in, rebuild the package to stop that happening, and possibly then breaking the system if you boot it with systemd.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 3:00 pm
by dolphin_oracle
Stevo wrote: Tue Aug 27, 2019 2:47 pm
Can anyone test if the nvidia-persistenced file installs successfully if you boot with systemd?
I did get the same error message on my Optimus system weeks ago when I tried a backport of the 430 driver from experimental, which didn't work, so reinstalled our MX 18 test repo version of 418.74 from my local repo. But I just removed the package to no ill effect to fix that issue. I couldn't figure out what package was pulling it in either...maybe our installer could remove it as the last step if it's present and then fix the system.
I know it's an ugly workaround, but the alternative is to find out what's pulling it in, rebuild the package to stop that happening, and possibly then breaking the system if you boot it with systemd.
its a recommend of nvidia-driver.
I have no idea what it actually does.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 3:51 pm
by KBD
Quick first impressions: I like the clear panel default. I like Conky up in the right hand corner, but the default clock in Conky is distracting. Having menubar enabled by default in the terminal might be useful for new users. The default icons seem tiny, smaller than in MX 18 anyway, and they don't appear to expand like they should when I increase the panel bar unless I make it huge. Would be interesting if it seems the same on larger screens, this is on a 12" screen.
So far MX 19 is working great on my X220 Thinkpad. Next will try it on my other Lenovo 11e laptop as well as my HP laptop.
Edit 1: I must be having some of the same intel issues mentioned earlier in this thread. On my HP laptop it will not launch at all when I select the drive MX is installed on in the bios. It skips to the default Debian install on that machine. On my Lenovo 11e it gets past Plymouth screen then crashes.
Edit 2: My Acer C720 laptop boots up fine with MX 19.
Edit 3: I can boot the live version of MX 19 on my HP laptop with the Sandybridge cpu and intel graphics. And I can run a full install of MX 18 on it, but not a full install of MX 19.
My Lenovo 11e with a Bay Trail cpu and intel graphics will not boot a live or installed version of MX 19, but it boots up an installed version of MX 18 without issue. If any other info is needed let me know.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 3:56 pm
by Eadwine Rose
Stevo wrote: Tue Aug 27, 2019 2:47 pm
Can anyone test if the nvidia-persistenced file installs successfully if you boot with systemd?
I did get the same error message on my Optimus system weeks ago when I tried a backport of the 430 driver from experimental, which didn't work, so reinstalled our MX 18 test repo version of 418.74 from my local repo. But I just removed the package to no ill effect to fix that issue. I couldn't figure out what package was pulling it in either...maybe our installer could remove it as the last step if it's present and then fix the system.
I know it's an ugly workaround, but the alternative is to find out what's pulling it in, rebuild the package to stop that happening, and possibly then breaking the system if you boot it with systemd.
I am in systemd now, or rather
has a systemd thing right at the top, so.. I wager that is it, even though the boot whined about not being able to boot due to missing .. something. It was gone before I knew it.
Of course nvidia is already installed here, as is nvidia-persistenced. Reinstalling throws an error..
can you tell me what you want me to do exactly? (back in 18.3 now, but holler if you see me)
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 7:48 pm
by dolphin_oracle
Paul.. wrote: Tue Aug 27, 2019 8:21 am
Error exiting from Live USB after completed HDD installation...
Exit-error.JPG
anything special you had mounted??
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:22 pm
by dolphin_oracle
KBD wrote: Tue Aug 27, 2019 3:51 pm
Quick first impressions: I like the clear panel default. I like Conky up in the right hand corner, but the default clock in Conky is distracting. Having menubar enabled by default in the terminal might be useful for new users. The default icons seem tiny, smaller than in MX 18 anyway, and they don't appear to expand like they should when I increase the panel bar unless I make it huge. Would be interesting if it seems the same on larger screens, this is on a 12" screen.
So far MX 19 is working great on my X220 Thinkpad. Next will try it on my other Lenovo 11e laptop as well as my HP laptop.
Edit 1: I must be having some of the same intel issues mentioned earlier in this thread. On my HP laptop it will not launch at all when I select the drive MX is installed on in the bios. It skips to the default Debian install on that machine. On my Lenovo 11e it gets past Plymouth screen then crashes.
Edit 2: My Acer C720 laptop boots up fine with MX 19.
Edit 3: I can boot the live version of MX 19 on my HP laptop with the Sandybridge cpu and intel graphics. And I can run a full install of MX 18 on it, but not a full install of MX 19.
My Lenovo 11e with a Bay Trail cpu and intel graphics will not boot a live or installed version of MX 19, but it boots up an installed version of MX 18 without issue. If any other info is needed let me know.
what is the symptom of "not booting?" I ask because many folks mistake not bootin for X not starting or some other issue.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:23 pm
by dolphin_oracle
Eadwine Rose wrote: Tue Aug 27, 2019 3:56 pm
Stevo wrote: Tue Aug 27, 2019 2:47 pm
Can anyone test if the nvidia-persistenced file installs successfully if you boot with systemd?
I did get the same error message on my Optimus system weeks ago when I tried a backport of the 430 driver from experimental, which didn't work, so reinstalled our MX 18 test repo version of 418.74 from my local repo. But I just removed the package to no ill effect to fix that issue. I couldn't figure out what package was pulling it in either...maybe our installer could remove it as the last step if it's present and then fix the system.
I know it's an ugly workaround, but the alternative is to find out what's pulling it in, rebuild the package to stop that happening, and possibly then breaking the system if you boot it with systemd.
I am in systemd now, or rather
has a systemd thing right at the top, so.. I wager that is it, even though the boot whined about not being able to boot due to missing .. something. It was gone before I knew it.
Of course nvidia is already installed here, as is nvidia-persistenced. Reinstalling throws an error..
can you tell me what you want me to do exactly? (back in 18.3 now, but holler if you see me)
re-install nvidia-persistenced while running in systemd mode. you may have to purge it first
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:35 pm
by colin_b
Sorry for butting in, but I've found something which should be mentioned. If I leave it I'm sure I'll forget.
https://www.youtube.com/watch?v=MKVUzScmS00 has a review of MX 19, and at about 6 min it talks about a problem with wireless transfers and how a program installation solves the problem.
If this software is required to get things working is it go to be included in MX 19?
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:39 pm
by dolphin_oracle
colin_b wrote: Tue Aug 27, 2019 8:35 pm
Sorry for butting in, but I've found something which should be mentioned. If I leave it I'm sure I'll forget.
https://www.youtube.com/watch?v=MKVUzScmS00 has a review of MX 19, and at about 6 min it talks about a problem with wireless transfers and how a program installation solves the problem.
If this software is required to get things working is it go to be included in MX 19?
already done
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:50 pm
by colin_b
I should have guessed
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:53 pm
by caprea
I just purged, installed and reinstalled nvidia-persistenced while NOT in systemd mode. Seems to work now without errors.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 8:59 pm
by dolphin_oracle
caprea wrote: Tue Aug 27, 2019 8:53 pm
I just purged, installed and reinstalled nvidia-persistenced while NOT in systemd mode. Seems to work now without errors.
thanks for the update!
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:10 pm
by KBD
dolphin_oracle wrote: Tue Aug 27, 2019 8:22 pm
what is the symptom of "not booting?" I ask because many folks mistake not bootin for X not starting or some other issue.
The HP laptop skips past my selection to boot a full install of MX 19 like it isn't even there and boots into my Debian install instead. It boots into the Live version of MX 19, but a full install does nothing. Something happening after the installation.
The Lenovo 11e laptop starts to boot a full install but gets hung up after plymouth screen. Same thing with live MX 19. Looks a graphic issue on the Lenovo 11e which has a Bay Trail cpu, I think that one is a system on a chip deal.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 9:23 pm
by dolphin_oracle
for the baytrail, go with "nosplash" boot code to disable plymouth.
for the HP, sounds like secure boot is still enabled.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 10:12 pm
by zukahn1
Have come across one minor issue Chromium won't start after install click on icon and nothing happens running on USB everything else and the other browsers work fine on a couple of different computers.
Re: MX-19 Beta 1 Feedback
Posted: Tue Aug 27, 2019 10:16 pm
by dolphin_oracle
zukahn1 wrote: Tue Aug 27, 2019 10:12 pm
Have come across one minor issue Chromium won't start after install click on icon and nothing happens running on USB everything else and the other browsers work fine on a couple of different computers.
install chromium-sandbox
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 2:14 am
by zebedeeboss
Hi all, Installing some packages from the MX Package Insaller - I get errors for Atom and Softmaker Office
Regards Zeb...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 2:20 am
by AK-47
The softmaker.com repos are not official Debian or MX repos. We can't guarantee that the softmaker.com repos will work, and if something breaks, we may not be able to support them.
However it sounds like you don't have a public key for those repos installed. You need to get the public key for those repos from SoftMaker and install it using sudo apt key add <gpg-key-file> and then run sudo apt update to sync it all up.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 2:27 am
by zebedeeboss
Installing the Atom .deb file from there
solves the error from appearing during updates but I guess still needs to be resolved in the MX Package Installer
Regards Zeb...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 2:31 am
by zebedeeboss
AK-47 wrote: Wed Aug 28, 2019 2:20 am
The softmaker.com repos are not official Debian or MX repos. We can't guarantee that the softmaker.com repos will work, and if something breaks, we may not be able to support them.
However it sounds like you don't have a public key for those repos installed. You need to get the public key for those repos from SoftMaker and install it using
sudo apt key add <gpg-key-file> and then run
sudo apt update to sync it all up.
Thanks - I do understand that - however you are proving the installation process via the MX Package Installer - so that method should work? Should it not ?
Regards Zeb
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 2:38 am
by chrispop99
Eadwine Rose wrote: Tue Aug 27, 2019 9:40 am
I encountered a little looks thing, moved the panel to the bottom and got this. The wired Synaptic icon behaved the same way.
Screenshot.png
Yep, this has happened through the Alphas as well, but nothing tried so far has fixed it.
Chris
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 3:01 am
by AK-47
zebedeeboss wrote: Wed Aug 28, 2019 2:31 amThanks - I do understand that - however you are proving the installation process via the MX Package Installer - so that method should work? Should it not ?
Regards Zeb
The installation process via MX Package Installer should work, and by all means if your package presents an issue with MXPI then please report it to us as well as what package you're trying to install.
However because the package comes from a foreign (non-Debian, non-MX repo), once it's installed, we can try to help to a limited extent, but we can't guarantee any results.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 3:17 am
by zebedeeboss
AK-47 wrote: Wed Aug 28, 2019 3:01 am
zebedeeboss wrote: Wed Aug 28, 2019 2:31 amThanks - I do understand that - however you are proving the installation process via the MX Package Installer - so that method should work? Should it not ?
Regards Zeb
The installation process via MX Package Installer should work, and by all means if your package presents an issue with MXPI then please report it to us as well as what package you're trying to install.
However because the package comes from a foreign (non-Debian, non-MX repo), once it's installed, we can try to help to a limited extent, but we can't guarantee any results.
Thanks - original packages mentioned in first post. Atom and Softmaker Office - output repeated here for ease of referal
Code: Select all
Err:5 http://shop.softmaker.com/repo/apt wheezy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3413DA98AA3E7F5E
Hit:8 https://packagecloud.io/AtomEditor/atom/any any InRelease
Reading package lists... Done
W: GPG error: http://shop.softmaker.com/repo/apt wheezy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3413DA98AA3E7F5E
E: The repository 'http://shop.softmaker.com/repo/apt wheezy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Regards Zeb...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 3:27 am
by Dede
Problem adding font Chicago.ttf (both for the whole system and the single user): it displays little rectangles instead of letters...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 3:54 am
by Eadwine Rose
chrispop99 wrote: Wed Aug 28, 2019 2:38 am
Eadwine Rose wrote: Tue Aug 27, 2019 9:40 am
I encountered a little looks thing, moved the panel to the bottom and got this. The wired Synaptic icon behaved the same way.
Screenshot.png
Yep, this has happened through the Alphas as well, but nothing tried so far has fixed it.
Chris
Indeed, I tried changing the size of the panel, nope, still like that. I DO always change my icon theme, so maybe then it'll get sorted. I'll report back if it does when I get back into the beta.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:24 am
by Eadwine Rose
My beloved used for years now nuvola-icon-theme package is gone
Is it possible to port this baby over? I like NONE of the alternatives, and I have been looking around for a long time back when to find something I liked... *sniff*
Anyway.. to report back.. I blanked the background first.. and...
I made screenshots in 19 and didn't save them to my backup drive....
OWH!! I can mount the drive *snort* I learn something new every day haha.
Here is the system tray with the blanked background:
panel1.png
You can see something isn't right, when the background is colored you don't see those little lines.
Now.. when I click that expand button twice the weirdness is gone.
panelaftercloseopen.png
And I have been able to repeat this with all the icon themes.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:31 am
by JayM
Eadwine Rose wrote: Wed Aug 28, 2019 4:24 am
My beloved used for years now nuvola-icon-theme package is gone
Is it possible to port this baby over? I like NONE of the alternatives, and I have been looking around for a long time back when to find something I liked... *sniff*
Available here:
https://pkgs.org/download/nuvola-icon-theme
They have a .deb package for Stretch but nothing yet for Buster. But it's just an icon package so...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:32 am
by Eadwine Rose
If you have spent WEEKS looking for something you like it becomes more than "just" an icon package
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:34 am
by JayM
I meant that it shouldn't be complicated to forwardport to Buster since it's just icons with no dependencies and stuff. :)
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:35 am
by Eadwine Rose
OWHHH like so..
*grin* Gotta love text without intonation huh.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:44 am
by Eadwine Rose
Debian 9 installs fine and works! WOOT!
Anyway, sorry for the deviation
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:45 am
by ChrisUK
I wouldn't do this until the final, but as a test, I did it with the Beta... result might be helpful to others in the future:
I backed up everything using Aptik - packages, settings, home (all of it, config and Vbox VMs etc), mounts (only swap, as it's a file. Aptik just edits fstab)... everything. Remember, you have a choice what not to restore, and if a package is already installed and up to date, it's not touched. So I backed up all of my themes, but didn't need to restore any of them same with Fonts and Icons
Anyway, after restoring so far, I can't tell the difference between the 18.3 Desktop and the 19 Beta - Whisker menu has the same entries, Panel is the same. Firefox is identical - Thunderbird too. Oh, I needed to install chromium-sandbox to get Chromium up and running.
I'll do some more checks later, but it seems like the easiest way to get everything running how you like.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:57 am
by Eadwine Rose
I found something in the action buttons that is not working right.. but if that belongs here.. I have no idea how to file a bug report on XFCE or anything though (I looked in the past, came back with my hair frazzled and fried).
In the panel you can put something called Action Buttons, selecting the...
wait..
An image says more than text here:
action.png
This SHOULD have two images showing, but one of the two doesn't have an image so they get put on top of each other (I think), when I uncheck the shutdown button the restart function appears.. or rather, it is a blank area which pops up Restart when hovering over it.
This is independent of the icon theme, I can select others with the same effect.
If you select that dropdown and change it to session you get a text menu where you can also see that things are missing.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 5:32 am
by Jerry3904
If you check the "Invert buttons" box they will appear one on top of the other. But they used to appear side by side, which I liked.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 5:53 am
by Eadwine Rose
As you can see in the screenie.. I checked that.. they won't do it. In 18.3, yep, not in 19.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 6:31 am
by BobbieAN
Great to see screen tearing is finally fixed in XFCE 4.14. MX 19 gonna be fantastic!
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 6:54 am
by tascoast
I had a simple and fast install. A couple of small changes, in the choice of location for Grub, option two seeming to correspond to a root location given I wanted to retain my existing Grub manager. A slight change to the password entry was the only other difference I noticed.
I was slightly confused by my dual monitor setup but quickly noticed the new layout tool in Settings, where I always go to right after rebooting, along with MX Tweak, Disk Manager, Panel/clock/Thunar preferences and options.
Nice updated icons in MX Tools. A new iDeviceMounter for those things....
Synaptic defaults worked quickly and updated fast, along with Australian spelling and thesaurus packages I typically add.
Looking forward to exploring more.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 7:17 am
by Gerson
zebedeeboss wrote: Wed Aug 28, 2019 2:31 am
AK-47 wrote: Wed Aug 28, 2019 2:20 am
The softmaker.com repos are not official Debian or MX repos. We can't guarantee that the softmaker.com repos will work, and if something breaks, we may not be able to support them.
However it sounds like you don't have a public key for those repos installed. You need to get the public key for those repos from SoftMaker and install it using
sudo apt key add <gpg-key-file> and then run
sudo apt update to sync it all up.
Thanks - I do understand that - however you are proving the installation process via the MX Package Installer - so that method should work? Should it not ?
Regards Zeb
From the official page they give the instructions to place the public key and to have available the updates:
https://www.freeoffice.com/en/tips-and-tricks-linux
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 7:36 am
by dolphin_oracle
zebedeeboss wrote: Wed Aug 28, 2019 2:14 am
Hi all, Installing some packages from the MX Package Insaller - I get errors for Atom and Softmaker Office
Regards Zeb...
thanks...we probably need to update the the softmaker routines in mxpi (looks like atom should be working). do you still have a /var/log/mxpi.log (or /var/log/mxpi.log.old) file showing the errors?
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 7:51 am
by fehlix
zebedeeboss wrote: Wed Aug 28, 2019 2:14 am
Hi all, Installing some packages from the MX Package Insaller - I get errors for Atom and Softmaker Office
I can't reproduce this issue. Without seeing the full console log, it's only a guess: The only reason I can think of that you manually might have added the softmaker repo, without adding the the public signing key first. The MXPI procedure will make sure that a public key will be added.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 7:59 am
by davemx
I reported earlier that Mugshot demanded a password then rejected it. Well, after a reboot, it demanded it once, accepted it, and since then hasn't demanded it at all. Weird but all working correctly now.
About Eadwine's problem with Notification Area (System Tray) icons being a bit distorted, I fixed this on mine, by finding a spot on the tray that, when right-clicked, gets you access to its settings and not an individual app's settings. Bring up the Properties icon. Selecting "Square Icons" fixes the problem at the expense of moving the icons too far apart. What you can do is to increase the "Maximum Icon Size" a little. You'll find that the icons don't really get bigger but move a little further apart, fixing the problem! Maybe this default spacing can be changed for the final release.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 8:01 am
by dolphin_oracle
ugh...the softmaker people are irritating...they've changed their repo keys (probably) and hid the information inside their deb for freeoffice.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 8:07 am
by dolphin_oracle
Gerson wrote: Wed Aug 28, 2019 7:17 am
zebedeeboss wrote: Wed Aug 28, 2019 2:31 am
AK-47 wrote: Wed Aug 28, 2019 2:20 am
The softmaker.com repos are not official Debian or MX repos. We can't guarantee that the softmaker.com repos will work, and if something breaks, we may not be able to support them.
However it sounds like you don't have a public key for those repos installed. You need to get the public key for those repos from SoftMaker and install it using
sudo apt key add <gpg-key-file> and then run
sudo apt update to sync it all up.
Thanks - I do understand that - however you are proving the installation process via the MX Package Installer - so that method should work? Should it not ?
Regards Zeb
From the official page they give the instructions to place the public key and to have available the updates:
https://www.freeoffice.com/en/tips-and-tricks-linux
their file they reference in the instructions isn't present in the deb.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 8:10 am
by dolphin_oracle
the freeoffice install routine is supposed to download a signing key prior to enabling the repo and installing the package. I suspect, but I cannot confirm right now, that the key has expired or that they changed the signing key but didn't publish it. will have to investigate later.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 8:15 am
by fehlix
dolphin_oracle wrote: Wed Aug 28, 2019 8:01 am
ugh...the softmaker people are irritating...they've changed their repo keys (probably) and hid the information inside their deb for freeoffice.
MXPI Installer will add latest repo-key from softmaker,
which they have not changed still the same:
Code: Select all
pub rsa2048 2018-01-04 [SC]
CC7D2EDF4808EFFA0E00FC723413DA98AA3E7F5E
uid SoftMaker repository (GPG key for signing files) <info@softmaker.com>
EDIT: Anyway, I'll go and add some double check in case fetching or adding the key failed...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 9:01 am
by danielson
Terminal window always opens split in the middle of dual monitors.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 9:21 am
by fehlix
danielson wrote: Wed Aug 28, 2019 9:01 am
Terminal window always opens split in the middle of dual monitors.
How do you open the Terminal window?
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 9:41 am
by zebedeeboss
fehlix wrote: Wed Aug 28, 2019 7:51 am
zebedeeboss wrote: Wed Aug 28, 2019 2:14 am
Hi all, Installing some packages from the MX Package Insaller - I get errors for Atom and Softmaker Office
I can't reproduce this issue. Without seeing the full console log, it's only a guess: The only reason I can think of that you manually might have added the softmaker repo, without adding the the public signing key first. The MXPI procedure will make sure that a public key will be added.
Hi Thanks for the Reply, I did not add anything manually - see Dolphin_Oracle reply and I will provide a copy of the mxpi.log - which contains, I believe, all the apps I installed incl Atom and Sofmaker
Regards Zeb...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 9:45 am
by zebedeeboss
dolphin_oracle wrote: Wed Aug 28, 2019 7:36 am
thanks...we probably need to update the the softmaker routines in mxpi (looks like atom should be working). do you still have a /var/log/mxpi.log (or /var/log/mxpi.log.old) file showing the errors?
Hi Dolpin
I will send the file via a pm as it will have limited DL to it. I hope it contains additional info to help
Regards Zeb...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 9:48 am
by fehlix
zebedeeboss wrote: Wed Aug 28, 2019 9:41 am
Hi Thanks for the Reply, I did not add anything manually - see Dolphin_Oracle reply and I will provide a copy of the mxpi.log - which contains, I believe, all the apps I installed incl Atom and Sofmaker
Thanks, we will adjust the FreeOffice installer, in case the public-signing key could not fetched due to a network or server issue.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 9:59 am
by Ghost67
davemx wrote: Wed Aug 28, 2019 7:59 am
...by finding a spot on the tray that, when right-clicked, gets you access to its settings and not an individual app's settings. Bring up the Properties icon. Selecting "Square Icons" fixes the problem at the expense of moving the icons too far apart. What you can do is to increase the "Maximum Icon Size" a little. You'll find that the icons don't really get bigger but move a little further apart, fixing the problem! Maybe this default spacing can be changed for the final release.
Another way to do this without hunting for that right-click spot in the system tray is to just right click
any empty space on the panel itself, then on the menu shown select 'panel' then 'panel preferences' and then in the dialog that is displayed select the 'items' tab. that will show all the panel components including the 'notification area'. Select that, then click the 'edit' button from the list to the right. This will give you the controls you mention above. I hope that helps :)
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 10:04 am
by Ghost67
The beta installed beautifully as a single-boot OS on my Toshiba Satellite laptop. No problems at all installing 'my essential software' from MXPI and Synaptic. Updates going well. No problems at all.
I'm very happy so far, and my previous experiences with MX-14 right through to MX-18 suggest to me that I will continue to be very happy with it!
Many thanks for a superb Beta!
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 10:44 am
by Eadwine Rose
I am still having probs trying to get the panel to be transparent. So far making it transparent makes everything in the panel disappear. Uhm.. I only want the BACKGROUND to disappear.
Has anyone gotten that to work? If so.. how?
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 10:57 am
by KBD
dolphin_oracle wrote: Tue Aug 27, 2019 9:23 pm
for the baytrail, go with "nosplash" boot code to disable plymouth.
for the HP, sounds like secure boot is still enabled.
Thanks!
The HP doesn't have secure boot, but I'm beginning to think that because I already have Debian 10 installed on that machine there might be a quirk in boot up defaulting to Debian instead of allowing me to choose MX 19. Like I said, the Live usb of MX 19 will boot, and MX 18 will boot on the machine.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 11:11 am
by fehlix
KBD wrote: Wed Aug 28, 2019 10:57 am
The HP doesn't have secure boot, but I'm beginning to think that because I already have Debian 10 installed on that machine there might be a quirk in boot up defaulting to Debian instead of allowing me to choose MX 19.
If you would post the grub-menu's config-file /boot/grub/grub.cfg
from the controlling grub (which might be MX Linux or Debian, depending whether you have chosen MBR for grub target within the MX Installer )
and the output of
we might spot the issue - or not.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 11:13 am
by v17564
About Spanish translation:
- in home user folder, change "Desktop" to "Escritorio"
- In "MX-Tweak":
- In "Opciones para configurar", change "Restablecer Lightdm (pantalla de inicio) a la predeterminado" to "Restablecer Lightdm (pantalla de inicio) a la predeterminada" or better "Restablecer la pantalla de inicio de Lightdm predeterminada"
- In "Otro", change "Mostrar ventanas de todos los áreas de trabajos en el panel" to "Mostrar ventanas de todas las áreas de trabajo en el panel"
- In "Panel, Preferencias del panel", change "Selector de pupitre" to "Selector de áreas de trabajo"
- Cange the size of the windowv in: "Apariencia, Tipos de letra", is bigger than other windows in the same dialog
- In "Configuración":
- ArandR is a multimonitor configuration tool, perhaps you should add some little explanation like "Multimonitor configuration (ARandR)". Translate: "Configuración de multimonitor (ARandR)"
- "Advance Network Configuration" isn't translate, "Configuración avanzada de red"
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 11:28 am
by chrispop99
davemx wrote: Wed Aug 28, 2019 7:59 am
About Eadwine's problem with Notification Area (System Tray) icons being a bit distorted, I fixed this on mine, by finding a spot on the tray that, when right-clicked, gets you access to its settings and not an individual app's settings. Bring up the Properties icon. Selecting "Square Icons" fixes the problem at the expense of moving the icons too far apart. What you can do is to increase the "Maximum Icon Size" a little. You'll find that the icons don't really get bigger but move a little further apart, fixing the problem! Maybe this default spacing can be changed for the final release.
Thanks, but this was tried during Alpha testing, and didn't work on all machines.
Chris
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 12:02 pm
by Ghost67
Eadwine Rose wrote: Wed Aug 28, 2019 10:44 am
I am still having probs trying to get the panel to be transparent. So far making it transparent makes everything in the panel disappear. Uhm.. I only want the BACKGROUND to disappear.
Has anyone gotten that to work? If so.. how?
'Panel preferences' dialog - 'Appearance' - 'Background' Style = Solid colour, click the colour box, then in the 'Pick a panel colour' dialog, just below where it says 'custom' click the '+' box. There will be shown a colour gradient selector with a slider on the left for the hue, a slider on the bottom for the transparency, and the main square where you pick how bright or dark you want the selected colour by click-dragging.
The slider at the bottom is the one you need. Drag it all the way to the left for a transparent panel.
I show how to do this at the beginning of this video:
https://www.youtube.com/watch?v=RgqEa0N9DmU :)
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 12:04 pm
by KBD
fehlix wrote: Wed Aug 28, 2019 11:11 am
If you would post the grub-menu's config-file /boot/grub/grub.cfg
from the controlling grub (which might be MX Linux or Debian, depending whether you have chosen MBR for grub target within the MX Installer )
and the output of
we might spot the issue - or not.
Thanks felix!
is this what you want?
Code: Select all
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 be186784-3f23-4ff4-9df8-855197a418cc
else
search --no-floppy --fs-uuid --set=root be186784-3f23-4ff4-9df8-855197a418cc
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 be186784-3f23-4ff4-9df8-855197a418cc
else
search --no-floppy --fs-uuid --set=root be186784-3f23-4ff4-9df8-855197a418cc
fi
insmod png
if background_image /usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-be186784-3f23-4ff4-9df8-855197a418cc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 be186784-3f23-4ff4-9df8-855197a418cc
else
search --no-floppy --fs-uuid --set=root be186784-3f23-4ff4-9df8-855197a418cc
fi
echo 'Loading Linux 4.19.0-5-amd64 ...'
linux /boot/vmlinuz-4.19.0-5-amd64 root=UUID=be186784-3f23-4ff4-9df8-855197a418cc ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.19.0-5-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-be186784-3f23-4ff4-9df8-855197a418cc' {
menuentry 'Debian GNU/Linux, with Linux 4.19.0-5-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-5-amd64-advanced-be186784-3f23-4ff4-9df8-855197a418cc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 be186784-3f23-4ff4-9df8-855197a418cc
else
search --no-floppy --fs-uuid --set=root be186784-3f23-4ff4-9df8-855197a418cc
fi
echo 'Loading Linux 4.19.0-5-amd64 ...'
linux /boot/vmlinuz-4.19.0-5-amd64 root=UUID=be186784-3f23-4ff4-9df8-855197a418cc ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.19.0-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 4.19.0-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-5-amd64-recovery-be186784-3f23-4ff4-9df8-855197a418cc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 be186784-3f23-4ff4-9df8-855197a418cc
else
search --no-floppy --fs-uuid --set=root be186784-3f23-4ff4-9df8-855197a418cc
fi
echo 'Loading Linux 4.19.0-5-amd64 ...'
linux /boot/vmlinuz-4.19.0-5-amd64 root=UUID=be186784-3f23-4ff4-9df8-855197a418cc ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.19.0-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 4.19.0-4-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-4-amd64-advanced-be186784-3f23-4ff4-9df8-855197a418cc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 be186784-3f23-4ff4-9df8-855197a418cc
else
search --no-floppy --fs-uuid --set=root be186784-3f23-4ff4-9df8-855197a418cc
fi
echo 'Loading Linux 4.19.0-4-amd64 ...'
linux /boot/vmlinuz-4.19.0-4-amd64 root=UUID=be186784-3f23-4ff4-9df8-855197a418cc ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.19.0-4-amd64
}
menuentry 'Debian GNU/Linux, with Linux 4.19.0-4-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-4-amd64-recovery-be186784-3f23-4ff4-9df8-855197a418cc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 be186784-3f23-4ff4-9df8-855197a418cc
else
search --no-floppy --fs-uuid --set=root be186784-3f23-4ff4-9df8-855197a418cc
fi
echo 'Loading Linux 4.19.0-4-amd64 ...'
linux /boot/vmlinuz-4.19.0-4-amd64 root=UUID=be186784-3f23-4ff4-9df8-855197a418cc ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.19.0-4-amd64
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
and:
Code: Select all
$ lsblk -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1
│ ext4 be186784-3f23-4ff4-9df8-855197a418cc 90.5G 8% /
├─sda2
│
└─sda5
swap c95b29f6-fbfa-434e-b5b1-b6b1902a64af [SWAP]
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 12:35 pm
by fehlix
KBD wrote: Wed Aug 28, 2019 12:04 pm
is this what you want?
Code: Select all
$ lsblk -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1
│ ext4 be186784-3f23-4ff4-9df8-855197a418cc 90.5G 8% /
├─sda2
│
└─sda5
swap c95b29f6-fbfa-434e-b5b1-b6b1902a64af [SWAP]
Doesn't look like there is any MX Linux installed.
But you wrote:
KBD wrote: Tue Aug 27, 2019 9:10 pm
The HP laptop skips past my selection to boot a full install of MX 19 like it isn't even there and boots into my Debian install instead.
Where do you select MX-19 to boot, their is no menu entry with the Debian Grub-menu?
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 1:52 pm
by bigbenaugust
I set up AppArmor on MX 19b1, to put it a little more in line with Debian 10. No issues, no surprises as expected!
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 3:12 pm
by KBD
fehlix wrote: Wed Aug 28, 2019 12:35 pm
Doesn't look like there is any MX Linux installed.
But you wrote:
KBD wrote: Tue Aug 27, 2019 9:10 pm
The HP laptop skips past my selection to boot a full install of MX 19 like it isn't even there and boots into my Debian install instead.
Where do you select MX-19 to boot, their is no menu entry with the Debian Grub-menu?
I think we didn't understand each other and I didn't explain it well. I'm testing MX 19 from a full install on a usb stick. I hit F9 on my laptop to choose MX 19 and select it, but it skips right by and loads My regular Debian install instead. I can get a Live USB to load on that machine, but not my full install. I know the install is good because it boots up fine on my X220 and Acer C720 without issue.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 3:27 pm
by davemx
System Sounds.
Sorry if this is covered already, but there is a superfluous line at the end of the /usr/bin/logoutsound-mx file. I don't think it's actually causing a problem, but it has the potential to do so if xfce changes its code. That line is xfce4-session-logout. It's already in the process of logging out!
Also, it needs 3 entries in Session & Startup. One, as now for logout, one for restart and one for shutdown.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 3:32 pm
by fehlix
KBD wrote: Wed Aug 28, 2019 3:12 pm
fehlix wrote: Wed Aug 28, 2019 12:35 pm
Doesn't look like there is any MX Linux installed.
But you wrote:
KBD wrote: Tue Aug 27, 2019 9:10 pm
The HP laptop skips past my selection to boot a full install of MX 19 like it isn't even there and boots into my Debian install instead.
Where do you select MX-19 to boot, their is no menu entry with the Debian Grub-menu?
I think we didn't understand each other and I didn't explain it well. I'm testing MX 19 from a full install on a usb stick. I hit F9 on my laptop to choose MX 19 and select it, but it skips right by and loads My regular Debian install instead.
So you try to boot from an attached USB stick, which has a "hdd" install (not a LiveUSB-install) on it.
OTOH, the lsblk command does not show any attached USBstick?
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 3:45 pm
by dolphin_oracle
davemx wrote: Wed Aug 28, 2019 3:27 pm
System Sounds.
Sorry if this is covered already, but there is a superfluous line at the end of the
/usr/bin/logoutsound-mx file. I don't think it's actually causing a problem, but it has the potential to do so if xfce changes its code. That line is
xfce4-session-logout. It's already in the process of logging out!
Also, it needs 3 entries in Session & Startup. One, as now for logout, one for restart and one for shutdown.
thank you! I'll take care of that. Its a hold over from the xfce 4.12 when we did some trickery to make that work.
as to the 3 startup entries, there should be 2. 1 for login, and one for logout. on my machine at home the logout entries also happen during shutdown and reboot.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 4:53 pm
by Stevo
JayM wrote: Wed Aug 28, 2019 4:34 am
I meant that it shouldn't be complicated to forwardport to Buster since it's just icons with no dependencies and stuff. :)
It's not a standalone source package, it's part of the kdeartwork package. We'll have to make it standalone.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 5:15 pm
by davemx
dolphin_oracle wrote: Wed Aug 28, 2019 3:45 pm
davemx wrote: Wed Aug 28, 2019 3:27 pm
System Sounds.
Sorry if this is covered already, but there is a superfluous line at the end of the
/usr/bin/logoutsound-mx file. I don't think it's actually causing a problem, but it has the potential to do so if xfce changes its code. That line is
xfce4-session-logout. It's already in the process of logging out!
Also, it needs 3 entries in Session & Startup. One, as now for logout, one for restart and one for shutdown.
thank you! I'll take care of that. Its a hold over from the xfce 4.12 when we did some trickery to make that work.
as to the 3 startup entries, there should be 2. 1 for login, and one for logout. on my machine at home the logout entries also happen during shutdown and reboot.
They don't on mine. I had to make the other two entries (reboot and shutdown) else I was greeted with silence. When I said three entries I was not including the login sound.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 5:36 pm
by danielson
fehlix wrote: Wed Aug 28, 2019 9:21 am
danielson wrote: Wed Aug 28, 2019 9:01 am
Terminal window always opens split in the middle of dual monitors.
How do you open the Terminal window?
Just made a liar out of me!
Usually hit super-key and type terminal.
After a reboot, did it three times, and three times it came out on default desktop as expected.
Go figure!
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 5:50 pm
by fehlix
danielson wrote: Wed Aug 28, 2019 5:36 pm
fehlix wrote: Wed Aug 28, 2019 9:21 am
danielson wrote: Wed Aug 28, 2019 9:01 am
Terminal window always opens split in the middle of dual monitors.
How do you open the Terminal window?
Usually hit super-key and type terminal.
After a reboot, did it three times, and three times it came out on default desktop as expected.
Actually it was a good report, as I thought you mentioned the terminal popup when right-click on Update icon and select check for updates, which indeed does have a multi-monitor size issue.
But the good news, the multi-monitor size issue of the update popup terminal window, is about to be fixed ...
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 6:47 pm
by Stevo
Stevo wrote: Wed Aug 28, 2019 4:53 pm
JayM wrote: Wed Aug 28, 2019 4:34 am
I meant that it shouldn't be complicated to forwardport to Buster since it's just icons with no dependencies and stuff. :)
It's not a standalone source package, it's part of the kdeartwork package. We'll have to make it standalone.
And it was pretty easy to take the deb apart and make it into a standalone source package.
Sending it up to the MX 19 repo. It will be seen as an upgrade to the installed Stretch version.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 7:01 pm
by davemx
This one affects beta versions of both antiX and MX. It's not a big thing, but they both seem to spend a while during bootup starting cups. Maybe 4-5 seconds. I'd have thought that it should just flash past, unless other stuff is going on in the background.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 7:12 pm
by KBD
So far so good on my Lenovo C440 all-in-one desktop computer. Looks sweet on this machine.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 7:24 pm
by danielson
@fehlix - thanks for pertinent info.
Update window does have that issue (and perhaps i was mistaken too!)
Sure am glad to know it under repairs!
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 7:42 pm
by rasat
installed via CD... does well and beautiful. Few cosmetic comments:
1) CD boot splash.... could have a better look
2) (patito feo)... didn't realize its MX 19 name
3) Thanks, conky position and look is now great
4) systemd-shim is there....
$ dpkg -S /sbin/init
sysvinit-core: /sbin/init
5) Good responds and fast
6) Well done!!
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 8:05 pm
by Old Giza
v17564 wrote: Wed Aug 28, 2019 11:13 am
About Spanish translation:
- in home user folder, change "Desktop" to "Escritorio"
- In "MX-Tweak":
- In "Opciones para configurar", change "Restablecer Lightdm (pantalla de inicio) a la predeterminado" to "Restablecer Lightdm (pantalla de inicio) a la predeterminada" or better "Restablecer la pantalla de inicio de Lightdm predeterminada"
- In "Otro", change "Mostrar ventanas de todos los áreas de trabajos en el panel" to "Mostrar ventanas de todas las áreas de trabajo en el panel"
- In "Panel, Preferencias del panel", change "Selector de pupitre" to "Selector de áreas de trabajo"
- Cange the size of the windowv in: "Apariencia, Tipos de letra", is bigger than other windows in the same dialog
- In "Configuración":
- ArandR is a multimonitor configuration tool, perhaps you should add some little explanation like "Multimonitor configuration (ARandR)". Translate: "Configuración de multimonitor (ARandR)"
- "Advance Network Configuration" isn't translate, "Configuración avanzada de red"
I corrected transaltions for the first two strings requested under MX-Tweak. They will show up in a future beta or final.
I'm not sure where the other strings are located, maybe Xfce or another app.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 8:26 pm
by Jerry3904
The desktop file for ARandR is horribly short and has only one translation:
Code: Select all
[Desktop Entry]
Name=ARandR
GenericName=Screen Settings
GenericName[de]=Bildschirmeinstellungen
Icon=display
Exec=arandr
Terminal=false
Type=Application
Categories=Settings;HardwareSettings;
StartupNotify=true
We could add to it, but it wouldn't survive an upgrade I bet.
Re: MX-19 Beta 1 Feedback
Posted: Wed Aug 28, 2019 9:10 pm
by Jerry3904
Now posting from an installation on my ThinkPad T60, where all seems to be running fine so far. (I love this machine!)
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 12:45 am
by JayM
I just installed it to my 20GB ex-frugal partition, installing boot to root and not installing grub, then booting back into 18.3 and running sudo update-grub. It added 19b1 at the end of my (flat) boot menu under memtest and it boots up and runs fine as far as I can tell. No screen garbling or tearing either when booting from my USB stick without persistence or from my SSD.
One thing I noticed that threw me for a while is that the currently-active app's icon gets superimposed over the workspace switcher for the workspace in which the app is running. I thought it was the windows button in the wrong place at first and thought I'd found a bug, but then I noticed that I also had a (small) window button for Firefox, and I remembered that other distros did the same thing re: their workspace switchers. It's just that the one in Xfce 4.12 in MX-18 didn't behave that way and I'd gotten used to that. Xfce now behaves more like the other DEs in that regard.
I also had to run sudo sensors-detect and say yes to everything, let it add them to the proper file in /etc/init.d and start them, then run the sensor viewer and select sensors to display, plus change permissions of /usr/sbin/hddtemp to stop getting the nag notifications before the sensor plugin had anything available other than ACPI. I guess that's normal. It's mentioned in the manual, but I just did it from memory as I recalled having to jump through a couple of hoops to get the sensors working in MX. I'm still keeping an eye on my "new" CPU's temperature.
I'll report back if I encounter any problems. If I don't say anything it's because nothing's wrong.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 2:36 am
by JayM
OK, I found something: I can't decrypt, mount and open encrypted file systems from within Thunar. I've enabled allowing mounting of internal drives by non-root users in MX Tweaks, logged out and back in. When I click on an encrypted drive or partition it prompts me for the passphrase then nothing happens after I enter it, it just sits there in my home directory. I'm able to manually decrypt and mount them in a terminal. I ran Thunar from a terminal but there was no output or text. The various logs contain no entries which seem to be relevant.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 8:05 am
by dolphin_oracle
JayM wrote: Thu Aug 29, 2019 2:36 am
OK, I found something: I can't decrypt, mount and open encrypted file systems from within Thunar. I've enabled allowing mounting of internal drives by non-root users in MX Tweaks, logged out and back in. When I click on an encrypted drive or partition it prompts me for the passphrase then nothing happens after I enter it, it just sits there in my home directory. I'm able to manually decrypt and mount them in a terminal. I ran Thunar from a terminal but there was no output or text. The various logs contain no entries which seem to be relevant.
does it work without the "mounting internal drives by non-root users" override?
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 8:08 am
by JayM
dolphin_oracle wrote: Thu Aug 29, 2019 8:05 am
JayM wrote: Thu Aug 29, 2019 2:36 am
OK, I found something: I can't decrypt, mount and open encrypted file systems from within Thunar. I've enabled allowing mounting of internal drives by non-root users in MX Tweaks, logged out and back in. When I click on an encrypted drive or partition it prompts me for the passphrase then nothing happens after I enter it, it just sits there in my home directory. I'm able to manually decrypt and mount them in a terminal. I ran Thunar from a terminal but there was no output or text. The various logs contain no entries which seem to be relevant.
does it work without the "mounting internal drives by non-root users" override?
No.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 8:15 am
by dolphin_oracle
and that is luks, not encryptfs?
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 8:33 am
by JayM
dolphin_oracle wrote: Thu Aug 29, 2019 8:15 am
and that is luks, not encryptfs?
Correct.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 8:56 am
by richb
Attempt to install brightness-controller:
Code: Select all
root@mx:/home/richb# apt install brightness-controller
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
brightness-controller : Depends: python-pyside but it is not installable
E: Unable to correct problems, you have held broken packages.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 10:51 am
by davemx
My backup of my personal stereo files makes use of folder.jpg, so I can confirm it works, lovely!
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 11:00 am
by Jerry3904
Pic?
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 11:55 am
by v17564
Hi Old Giza.
I post some image for clarified where i see the translation to Spanish issue.
MX tweak -> Options and show the position of "Panel" and "Apariencia"
MX tweak - Opciones, Panel, Apariencia.png
"Apariencia" and "Preferencias del panel" is in Xfce, in MX-Tweak there are a direct access ?.
Whisker Menu -> Configuration -> Appearance -> Types of letters, window too big
Apariencia.png
Whisker Menu -> Configuration -> Panel
Preferencias de panel.png
MX-Tweak -> Other
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 12:52 pm
by Jerry3904
This comment to the Blog announcement comes from Ruud Kuin
Testing 19-Beta-1 on my Acer Aspire One Netbook. Quite fast for an old machine!
Some windows (MXTools) are too high for the screen, Maybe some/one of dev’s could look into that? Maximum height 550 pixels, for instance. Scrolling works, so give it a try…
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 1:04 pm
by KBD
Jerry3904 wrote: Thu Aug 29, 2019 12:52 pm
This comment to the Blog announcement comes from Ruud Kuin
Testing 19-Beta-1 on my Acer Aspire One Netbook. Quite fast for an old machine!
Some windows (MXTools) are too high for the screen, Maybe some/one of dev’s could look into that? Maximum height 550 pixels, for instance. Scrolling works, so give it a try…
That is not unusual for netbooks, I had that issue on every distro years ago with my netbooks.
I believe you use a combo of Alt-F7 keys to move/resize the window for those small screens.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 1:16 pm
by KBD
I tried hitting the esc key while booting MX 19 on my Lenovo 11e with the bay trail cpu and it just refuses to get past the initial boot screen. It goes black and freezes right at the plymouth/MX screen. It gets to the screen that says udev and that's it.
MX 18 boots on this machine, as does Ubuntu. So I'm not sure what the issue is with MX 19 beta. The usb MX 19 live works on other machines, so it's not the boot media.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 1:26 pm
by Jerry3904
I tried hitting the esc key
Why, exactly? Was that a live or installed boot?
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 1:56 pm
by KBD
Jerry3904 wrote: Thu Aug 29, 2019 1:26 pm
I tried hitting the esc key
Why, exactly? Was that a live or installed boot?
Live, though same issue when I tried a full install on an external drive. When it came to the plymouth screen to see what the text said, thought maybe I could find out why it was freezing, plus felix recommend I try it in an earlier post. But it just stays stuck on a black screen.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 2:25 pm
by v17564
Hi Old Gita (again).
I post some image for clarified where i see the translation to Spanish issue.
- MX tweak -> Others
Change "Habilitar un solo click en Thunar gestor de archivos"
If only affect to Thunar: "Habilitar un solo click en el gestor de archivos Thunar"
or if affect to any file manager, others differents to Thunar: "Habilitar un solo click en el gestor de archivos"
Change "Mostrar marco de systray (área de notificación)" to "Mostrar marco en el área de notificación"
Change "Mostrar ventanas de tod
os las áreas de trabajo en el panel" to "Mostrar ventanas de tod
as las áreas de trabajo en el panel"
MX-Tweak - Otros.png
- Thunar
Thunar.png
- Menu Whisker -> Configuration
Configuracion.png
If you need more information not dudde in asking me for it.
Greetings.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 2:44 pm
by dolphin_oracle
KBD wrote: Thu Aug 29, 2019 1:16 pm
I tried hitting the esc key while booting MX 19 on my Lenovo 11e with the bay trail cpu and it just refuses to get past the initial boot screen. It goes black and freezes right at the plymouth/MX screen. It gets to the screen that says udev and that's it.
MX 18 boots on this machine, as does Ubuntu. So I'm not sure what the issue is with MX 19 beta. The usb MX 19 live works on other machines, so it's not the boot media.
does it go black, or does it still have text on the screen.
if black, try the i915.invert_brightness=1 as a boot parameter. or try just adjusting the brightness (up and down, because the values could be backwards) after waiting a while. I have 2 lenovo cheapies that do this. its annoying, and yes, they both worked fine on 18.3, but exhibit this issue on 19. antiX has the same issue on those machines (lenovo s21e and a ideapad 110s)
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 2:46 pm
by dolphin_oracle
v17564 wrote: Thu Aug 29, 2019 2:25 pm
Hi Old Gita (again).
I post some image for clarified where i see the translation to Spanish issue.
- MX tweak -> Others
Change "Habilitar un solo click en Thunar gestor de archivos"
If only affect to Thunar: "Habilitar un solo click en el gestor de archivos Thunar"
or if affect to any file manager, others differents to Thunar: "Habilitar un solo click en el gestor de archivos"
Change "Mostrar marco de systray (área de notificación)" to "Mostrar marco en el área de notificación"
Change "Mostrar ventanas de tod
os las áreas de trabajo en el panel" to "Mostrar ventanas de tod
as las áreas de trabajo en el panel"
MX-Tweak - Otros.png
- Thunar
Thunar.png
- Menu Whisker -> Configuration
Configuracion.png
If you need more information not dudde in asking me for it.
Greetings.
we appreciate the help, but this is much easier on our end if you sign up for an account on transifex and submit translation changes that way. Submitting them hear is a very manual process.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 4:47 pm
by Jerry3904
On the Live screen, down in the corner, it says use F1 to see, F10 to restore
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 6:19 pm
by Old Giza
v17564 wrote: Thu Aug 29, 2019 2:25 pm
Hi Old Gita (again).
I post some image for clarified where i see the translation to Spanish issue.
- MX tweak -> Others
Change "Habilitar un solo click en Thunar gestor de archivos"
If only affect to Thunar: "Habilitar un solo click en el gestor de archivos Thunar"
or if affect to any file manager, others differents to Thunar: "Habilitar un solo click en el gestor de archivos"
Change "Mostrar marco de systray (área de notificación)" to "Mostrar marco en el área de notificación"
Change "Mostrar ventanas de tod
os las áreas de trabajo en el panel" to "Mostrar ventanas de tod
as las áreas de trabajo en el panel"
Thanks for informing us of these translation improvements. I carried them out on Transifex. The others relate to Xfce over which I have no control.
As dolphin_oracle says, it's simpler to make these changes directly through Transifex. We welcome your input. Please send me a personal message, or continue the discussion in the
Translations forum (start a new topic).
Xfce also uses Transifex, so if you want to contribute, you can easily do for both Xfce and MX.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 6:28 pm
by KBD
dolphin_oracle wrote: Thu Aug 29, 2019 2:44 pm
does it go black, or does it still have text on the screen.
if black, try the i915.invert_brightness=1 as a boot parameter. or try just adjusting the brightness (up and down, because the values could be backwards) after waiting a while. I have 2 lenovo cheapies that do this. its annoying, and yes, they both worked fine on 18.3, but exhibit this issue on 19. antiX has the same issue on those machines (lenovo s21e and a ideapad 110s)
I tried the i915 boot parameter but it is still getting stuck right before plymouth. I get a completely black screen with a tiny semi-white 'promt' at the top left corner, but it is frozen at this point and will do nothing.
Edit: adjusting the screen brightness changes the background color a bit, but nothing else has any affect.
Edit2: it will boot in failsafe. Would be interested to know why it won't boot otherwise.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 6:46 pm
by KBD
My system info:
Code: Select all
Host: mx1 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19beta-1_x64 patito feo August 25 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: LENOVO product: 20GB000LUS v: ThinkPad 11e 3rd Gen
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: Intel powered classmate PC v: SDK0J40697 WIN serial: <filter>
UEFI [Legacy]: LENOVO v: R0AET27W (1.10) date: 04/22/2016
Battery: ID-1: BAT1 charge: 41.6 Wh condition: 41.6/42.0 Wh (99%) volts: 12.4/11.2
model: SMP LNV-00HW44 type: Li-poly serial: <filter> status: Full
CPU: Topology: Quad Core model: Intel Celeron N3150 bits: 64 type: MCP arch: Airmont
family: 6 model-id: 4C (76) stepping: 3 microcode: 368 L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 12800
Speed: 1423 MHz min/max: 480/2080 MHz Core speeds (MHz): 1: 808 2: 928 3: 945 4: 1432
Vulnerabilities: Type: l1tf status: Not affected
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Not affected
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated
Graphics
vendor: Lenovo driver: N/A bus ID: 00:02.0 chip ID: 8086:22b1
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1368x768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1
direct render: Yes
Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High
Definition Audio
vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:2284
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo
driver: r8169 v: kernel port: 1000 bus ID: 02:00.0 chip ID: 10ec:8168
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: 1000 bus ID: 03:00.0
chip ID: 8086:095b
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 122.99 GiB used: 289.7 MiB (0.2%)
ID-1: /dev/sda vendor: Samsung model: MZNLF128HCHP-000L1 size: 119.24 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1L4Q scheme: GPT
ID-2: /dev/sdb type: USB vendor: SanDisk model: SanDisk Cruzer size: 3.75 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 8.02 scheme: MBR
Partition: ID-1: / raw size: N/A size: 6.04 GiB used: 289.7 MiB (4.7%) fs: overlay
source: ERR-102
Sensors: System Temperatures: cpu: 44.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 217 Uptime: 11m Memory: 7.62 GiB used: 1.06 GiB (13.8%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 7:14 pm
by dolphin_oracle
stupid nvidia postinst script.
bug report over at bugs.debian.org.
https://bugs.debian.org/cgi-bin/bugrepo ... bug=928497
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 8:25 pm
by Stevo
davemx wrote: Wed Aug 28, 2019 3:27 pm
System Sounds.
Sorry if this is covered already, but there is a superfluous line at the end of the
/usr/bin/logoutsound-mx file. I don't think it's actually causing a problem, but it has the potential to do so if xfce changes its code. That line is
xfce4-session-logout. It's already in the process of logging out!
Also, it needs 3 entries in Session & Startup. One, as now for logout, one for restart and one for shutdown.
Could that be why we see the login screen for a second or more as we're shutting down now? Some testers have remarked about that.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 9:09 pm
by dolphin_oracle
Stevo wrote: Thu Aug 29, 2019 8:25 pm
davemx wrote: Wed Aug 28, 2019 3:27 pm
System Sounds.
Sorry if this is covered already, but there is a superfluous line at the end of the
/usr/bin/logoutsound-mx file. I don't think it's actually causing a problem, but it has the potential to do so if xfce changes its code. That line is
xfce4-session-logout. It's already in the process of logging out!
Also, it needs 3 entries in Session & Startup. One, as now for logout, one for restart and one for shutdown.
Could that be why we see the login screen for a second or more as we're shutting down now? Some testers have remarked about that.
don't know, but its updated and fixed now
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 10:07 pm
by jj1j1
For a beta mx 19 works great. Props to the developers. One small thing that I didn't see mentioned before has to do with restarting, or shutting down the system. When buttons in xfce panel is clicked the logon screen will appear for about 2 or 3 seconds then changes to normal shutdown screen.
Uh, cough, cough, I guess I should have read a few posts above...
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 10:16 pm
by dolphin_oracle
jj1j1 wrote: Thu Aug 29, 2019 10:07 pm
For a beta mx 19 works great. Props to the developers. One small thing that I didn't see mentioned before has to do with restarting, or shutting down the system. When buttons in xfce panel is clicked the logon screen will appear for about 2 or 3 seconds then changes to normal shutdown screen.
Uh, cough, cough, I guess I should have read a few posts above...
I'm afraid that is a hangup from not using systemd. I think. Maybe. Its been that way for a while. On the other hand you know you are logged out!
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 10:33 pm
by dolphin_oracle
JayM wrote: Thu Aug 29, 2019 2:36 am
OK, I found something: I can't decrypt, mount and open encrypted file systems from within Thunar. I've enabled allowing mounting of internal drives by non-root users in MX Tweaks, logged out and back in. When I click on an encrypted drive or partition it prompts me for the passphrase then nothing happens after I enter it, it just sits there in my home directory. I'm able to manually decrypt and mount them in a terminal. I ran Thunar from a terminal but there was no output or text. The various logs contain no entries which seem to be relevant.
I'm confirming you luks partitions issue. works from command line, does not work from the thunar gui.
more info: thunar can mount once the partition is "opened" with "cryptsetup luksOpen" and can unmount, but can't close the container. there is a udisks error on unmount.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 10:35 pm
by JayM
OK, let me know if you need me to do anything on my end.
Re: MX-19 Beta 1 Feedback
Posted: Thu Aug 29, 2019 10:38 pm
by dolphin_oracle
JayM wrote: Thu Aug 29, 2019 10:35 pm
OK, let me know if you need me to do anything on my end.
will do.
I think the problem is in udisks2. nemo has same problem, and gives same error.
Re: MX-19 Beta 1 Feedback-samba working
Posted: Thu Aug 29, 2019 10:53 pm
by entropyfoe
Dolphin_Oracle
You were right
Re: MX-19 Beta 1 Feedback
#153
Post by dolphin_oracle » 27 Aug 2019 13:26
I can connect directly to my samba shares, but the browse feature does not work (in my case,didn't work under mx17/18 either).
smb:///servername/sharename
I got my samba share to work, connecting to a windows 7 machine on the network.
I copied the /etc/samba/samba.conf from MX-18.3 over the beta, but still no shares were visible after a reboot.
So unlike MX-18, the file manager does not display of find shares on the network in the beta.
Then, I looked at the formation of the server line in the MX-18.3 and applied that to the beta.
You were right, a working line in the address bar of the file manager is smb://X7/J/ . If I type that in, I can authenticate.
Where X7 is the name of the windows computer, and /J/ is the shared volume.
So, a few days of uptime, no crashes.
The samba was the last thing not working for me. I did another synaptic update, 9 more packages.
Many reboots, suspends, packages added, all working so the beta is fast and stable.
Amazing to see these buster betas so fast and good for antiX and MX 19s.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 12:02 am
by SwampRabbit
Apologies if someone already brought these up, but its hard to check this often, and there is a lot of movement from testers and devs.
1) Running the beta in VirtualBox 6, I seem to have an odd random flicker of the XFCE panel and Conky, I assume it is the compositor.
Nothing seems to set it off per say, it does it on its own. I can send the inxi, but its a stock beta install with mostly all defaults in VirtualBox.
I didn't install the extensions directly from VirtualBox, just using what came with the install
But besides the default I set:
Para-Virt Interface - KVM
Video memory - 32MB
Enabled 3d Acceleration
2) The beta seems to default to to a gigantic mouse icon size, under "Mouse and Touchpad" it doesn't seem to be lowered below size 16.
3) MX Package Installer doesn't seem to like me clicking the "Debian Backports" tab, it dumps back to "Popular Applications"... although this could be because nothing exists in it?
4) This is a long shot request, but it seems that DockBarX and the XFCE plugin haven't been brought over to 4.14. I would really appreciate it if its possible to have this on MX, as it was the simplest and best way to add a dock directly to the XFCE panel. Should I put a Package Request in for this instead?
5) I thought I saw that in MX-18.3 had OBS-Studio version 23 (Stable Repo) and version 22 was in the Test Repo. Wasn't sure if I was losing my mind or just too tired at the time, but MX-19 beta only has version 22.
Will it be possible to have OBS 23 in MX-19 at some point?
Other than all of that it seems really really good, booted painlessly via live USB on 3 different systems and VirtualBox!
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 12:07 am
by Stevo
Now that Debian has updated their upstream version to 23.2.1, I'll give it a try tomorrow.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 12:13 am
by SwampRabbit
Thanks Stevo, you're the best!
But no rush really, in time for MX-19 official release would be great, even after is good.
Ya'll do an awesome job keeping all the different wanted applications updated.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 12:48 am
by SwampRabbit
Also, is it possible to not have Onboard as a dependency for lightdm-gtk-greeter-mx19?
Not that it affects anything, just asking for those of us who go a little overboard slimming down the already slim MX base install.
Re: MX-19 Beta 1 Feedback - sgfxi
Posted: Fri Aug 30, 2019 4:22 am
by zebedeeboss
Code: Select all
root@mx-2950x:/home/zebedee# sgfxi -k
Checking sgfxi versions.... Failed to aquire remote version data. Will try direct download instead.
Updating sgfxi now using the default server
ERROR: (198) The url/file: sgfxi
failed to download - wget error.
Exiting script now.
root@mx-2950x:/home/zebedee#
Trying to install the very latest drivers - what am I doing wrong please.
Regards Zeb...
Re: MX-19 Beta 1 Feedback - sgfxi
Posted: Fri Aug 30, 2019 6:55 am
by dolphin_oracle
zebedeeboss wrote: Fri Aug 30, 2019 4:22 am
Code: Select all
root@mx-2950x:/home/zebedee# sgfxi -k
Checking sgfxi versions.... Failed to aquire remote version data. Will try direct download instead.
Updating sgfxi now using the default server
ERROR: (198) The url/file: sgfxi
failed to download - wget error.
Exiting script now.
root@mx-2950x:/home/zebedee#
Trying to install the very latest drivers - what am I doing wrong please.
Regards Zeb...
there's apparently a problem with sgfxi. :/
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 7:27 am
by Gerson
I bring a comment from the Spanish forum on Google Earth:
http://forum.mxlinux.org/viewtopic.php? ... d4#p524105
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 7:32 am
by Jerry3904
Let's get an English translation. You mean this?
Hello Gerson: because of your suggestion, I directly upgraded to MX Linux 19 Beta 1.
I was able to enable recovery mode in the Grub, no problem.
Still not working the latest Google Earth 7.3, which installs correctly.
The Nvidia Legacy driver is not available for my card.
Google Earth 7.1 that works, can not be installed for lack of dependencies, which I downloaded from
Jessie's repo: lsb-core lsb-invalid lsb-securityy and so I could install.
Greetings.
Translated with
www.DeepL.com/Translator
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 7:41 am
by JayM
dolphin_oracle wrote: Thu Aug 29, 2019 10:38 pm
JayM wrote: Thu Aug 29, 2019 10:35 pm
OK, let me know if you need me to do anything on my end.
will do.
I think the problem is in udisks2. nemo has same problem, and gives same error.
FYI, unfortunately the power button on my desktop's case (or more likely its wires) failed this afternoon so I won't be able to do anymore testing until I can move the motherboard, PSU, drives, fans etc. to a spare case that I have. I hope to be able to do that over the weekend.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 7:45 am
by Jerry3904
I just used MX Package Installer to install GE, and it works fine here.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 7:52 am
by Head_on_a_Stick
The live image works fine under QEMU/KVM, the new qxl video drivers mean that it should also work in gnome-boxes.
There is no GTK+ 3 configuration for either the theme or icons, this seems to be a peculiarity of the Xfce settings manager with no ~/.config/gtk-3.0/settings.ini file at all.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 8:13 am
by tstc
Overall, Beta 1 has been very smooth. Have come across one nasty little glitch however, the lspci program creates a blank terminal screen-runaway/lockup/unresponsive condition. This is called from the main menu's "Quick System Info" (inxi-Fxrz).
System Info:Installed on Lenovo W540 Notebook Computer
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 8:48 am
by Jerry3904
live or installed?
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 9:22 am
by dolphin_oracle
luks: can someone check to see if libblockdev-crypto2 is installed by default?
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 9:28 am
by Jerry3904
No
Re: MX-19 Beta 1 Feedback - sgfxi
Posted: Fri Aug 30, 2019 10:13 am
by zebedeeboss
dolphin_oracle wrote: Fri Aug 30, 2019 6:55 am
zebedeeboss wrote: Fri Aug 30, 2019 4:22 am
Code: Select all
root@mx-2950x:/home/zebedee# sgfxi -k
Checking sgfxi versions.... Failed to aquire remote version data. Will try direct download instead.
Updating sgfxi now using the default server
ERROR: (198) The url/file: sgfxi
failed to download - wget error.
Exiting script now.
root@mx-2950x:/home/zebedee#
Trying to install the very latest drivers - what am I doing wrong please.
Regards Zeb...
there's apparently a problem with sgfxi. :/
Unfortunate - but at least it's not something I am doing wrong
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 10:28 am
by dolphin_oracle
ah...no its not installed or no you can't check
assuming you mean no not installed, good that gives an avenue to check.
is a new package for buster, so it may be required.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 11:20 am
by SwampRabbit
I've done another test to try and see why the panel and Conky flicker in VirtualBox.
I booted off the ISO and selected VirtualBox video driver, but I noticed that my virtual screen is defaulted by 800x600, it does not flicker at all though.
But if I change the display size inside MX it starts to flicker again.
Code: Select all
Graphics: Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 bus ID: 00:02.0
chip ID: 15ad:0405
Display: x11 server: X.Org 1.20.4 driver: vmware unloaded: fbdev,modesetting,vesa
resolution: 1280x800~60Hz
OpenGL: renderer: SVGA3D; build v: 2.1 Mesa 18.3.6 direct render: Yes
Within the VM Settings I changed the default Graphics Controller to VBoxVGA and rebooted.
The screen scaled on its own perfectly fine and the flickering seems to have gone away.
Code: Select all
Graphics: Device-1: InnoTek Systemberatung VirtualBox Graphics Adapter vendor: VMware
driver: vboxvideo v: 6.0.10_Debian r132055 bus ID: 00:02.0 chip ID: 80ee:beef
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
alternate: vboxvideo resolution: 1920x912~60Hz
So it looks like the vmwgfx driver has issues.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 11:36 am
by dolphin_oracle
yeah for whatever reason Virtualbox defaults to the vmware driver now. its weird.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 12:20 pm
by SwampRabbit
Please ignore my item about the mouse cursor size.... it seems that I forgot that I had scaling (150%) on the monitor that I keep my VirtualBox screens on!
Oddly it didn't affect anything desktop or anywhere else.... just the mouse cursor, which is why I even said anything. But it can be chalked up to user configuration error.
I guess I at least don't have any
real issues so far with the beta at all so far.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 1:17 pm
by entropyfoe
Beta is looking pretty good...
" patito feo" will turn into
----> " pulcher olor"
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 1:36 pm
by ChrisUK
entropyfoe wrote: Fri Aug 30, 2019 1:17 pm
Beta is looking pretty good...
" patito feo" will turn into
----> " pulcher olor"
Nah... but maybe Cygnus olor
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 1:46 pm
by davemx
I noticed a reference to the Spanish forum about Google Earth. The pro version doesn't like the Intel driver, and you have to use Modsetting for it to work (testing on this and another distro). I have an earlier version (rpm only), which does work with the Intel driver, but since XFCE4 went to v4.14, it's occasionally closing unexpectedly. The Pro-version problem isn't a consequence of our beta version, and I don't think the other one is either. But I thought I'd mention it.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 1:49 pm
by Jerry3904
Didn't know that. I have seen no reason to switch to the Intel driver, so GE works fine.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 2:08 pm
by tosim
I placed the iso on flash drive, using MultiBootUSB. It will not boot beyond first page(sorry, no screenshot). I tried Grub, Grub2, and other available options (within the Grubs), and still the same. I run AntiX from MultiBoot USB with no problems, and would really like to try out MX. I realize I can burn iso to disc, and probably to a different flash, but I prefer MutiBoot USB.Any suggestions gratefully appreciated. Thank you.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 2:20 pm
by Gerson
Jerry3904 wrote: Fri Aug 30, 2019 7:32 am
Let's get an English translation. You mean this?
Hello Gerson: because of your suggestion, I directly upgraded to MX Linux 19 Beta 1.
I was able to enable recovery mode in the Grub, no problem.
Still not working the latest Google Earth 7.3, which installs correctly.
The Nvidia Legacy driver is not available for my card.
Google Earth 7.1 that works, can not be installed for lack of dependencies, which I downloaded from
Jessie's repo: lsb-core lsb-invalid lsb-securityy and so I could install.
Greetings.
Translated with
www.DeepL.com/Translator
That's right, I didn't put it directly into English for developers to check for origin.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 2:48 pm
by dolphin_oracle
tosim wrote: Fri Aug 30, 2019 2:08 pm
I placed the iso on flash drive, using MultiBootUSB. It will not boot beyond first page(sorry, no screenshot). I tried Grub, Grub2, and other available options (within the Grubs), and still the same. I run AntiX from MultiBoot USB with no problems, and would really like to try out MX. I realize I can burn iso to disc, and probably to a different flash, but I prefer MutiBoot USB.Any suggestions gratefully appreciated. Thank you.
antiX and MX use exactly the same boot loaders, so whatever you did for antiX should work for MX. BTW, the legacy live boots use syslinux/isolinux, not grub.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 2:56 pm
by Stevo
Jerry3904 wrote: Fri Aug 30, 2019 7:45 am
I just used MX Package Installer to install GE, and it works fine here.
I get the impression that the OP is using an old Nvidia GPU, must use the nouveau driver now in Buster because Nvidia doesn't support the legacy 304xx drivers any longer, and GE Pro doesn't work with nouveau for them.
If that's the case, they could check and see if the using the Web version at maps.google.com is an acceptable workaround. Otherwise, they could bite the bullet and find an upgrade for the card, or stick with MX 18.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 3:09 pm
by Stevo
Jerry3904 wrote: Fri Aug 30, 2019 1:49 pm
Didn't know that. I have seen no reason to switch to the Intel driver, so GE works fine.
Yes, it's a long-standing issue. If you have a Intel laptop with hybrid graphics like Optimus working with Bumblebee, you can sidestep that problem by having the discrete GPU handle GE Pro instead, which gives better performance also.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 5:08 pm
by dolphin_oracle
JayM wrote: Fri Aug 30, 2019 7:41 am
dolphin_oracle wrote: Thu Aug 29, 2019 10:38 pm
JayM wrote: Thu Aug 29, 2019 10:35 pm
OK, let me know if you need me to do anything on my end.
will do.
I think the problem is in udisks2. nemo has same problem, and gives same error.
FYI, unfortunately the power button on my desktop's case (or more likely its wires) failed this afternoon so I won't be able to do anymore testing until I can move the motherboard, PSU, drives, fans etc. to a spare case that I have. I hope to be able to do that over the weekend.
when you get running again, installing libblockdev-crypto2 and its depends, then restart your system, and you should be able to mount those luks partitions.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 6:16 pm
by jbMacAZ
Only problem I've encountered was installing to sda19. The work around from
viewtopic.php?f=92&t=51965 still works. Everything else seems a bit cleaner. MX-Linux 19b is looking good.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 8:28 pm
by davemx
tosim wrote: Fri Aug 30, 2019 2:08 pm
I placed the iso on flash drive, using MultiBootUSB. It will not boot beyond first page(sorry, no screenshot). I tried Grub, Grub2, and other available options (within the Grubs), and still the same. I run AntiX from MultiBoot USB with no problems, and would really like to try out MX. I realize I can burn iso to disc, and probably to a different flash, but I prefer MutiBoot USB.Any suggestions gratefully appreciated. Thank you.
I posted about this, with a solution, for MX18, I'm on my phone at the moment but tomorrow when I'm at the computer I'll find the link. A similar solution can be adapted for MX19ß1 and antiX19ß3. It wasn't necessary with antiX17.
EDIT: I found it!
viewtopic.php?f=108&t=50646#p506184
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 8:42 pm
by jj1j1
I migrated a conky I had in mx18 into mx19, and noticed that the colors changed. Did the color scheme change?
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 9:00 pm
by Jerry3904
Some changes to go with the wallpaper. Simple to change them with MX Conky.
Re: MX-19 Beta 1 Feedback
Posted: Fri Aug 30, 2019 9:37 pm
by joesplace
I loaded MX-19 Beta 1 on my Dell Latitude E6330 SSD and I must be a bad beta tester cause it seems to run just fine. I changed many things, installed apps, downloaded and uploaded with no problem. I have been using this Beta for 2 days with no problems . . .
Great job!
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 12:16 am
by Herve33
Hello,
I would like to install MX linux on the PC of one of my friends. Since the stable version 19 will be released in a few days, I would not want to reinstall it in a few weeks. If I install the beta version, will it automatically switch to stable as soon as it comes out? Or do we have to install with an iso of the stable version?
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 1:08 am
by JayM
dolphin_oracle wrote: Fri Aug 30, 2019 5:08 pm
JayM wrote: Fri Aug 30, 2019 7:41 am
dolphin_oracle wrote: Thu Aug 29, 2019 10:38 pm
will do.
I think the problem is in udisks2. nemo has same problem, and gives same error.
FYI, unfortunately the power button on my desktop's case (or more likely its wires) failed this afternoon so I won't be able to do anymore testing until I can move the motherboard, PSU, drives, fans etc. to a spare case that I have. I hope to be able to do that over the weekend.
when you get running again, installing libblockdev-crypto2 and its depends, then restart your system, and you should be able to mount those luks partitions.
Yes, that fixed it. Thank you.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 3:28 am
by Eadwine Rose
Herve33 wrote: Sat Aug 31, 2019 12:16 am
Hello,
I would like to install MX linux on the PC of one of my friends. Since the stable version 19 will be released in a few days, I would not want to reinstall it in a few weeks. If I install the beta version, will it automatically switch to stable as soon as it comes out? Or do we have to install with an iso of the stable version?
Stable MX19 is not going to be released in a few days. We're only at a first beta right now. We're likely going to see an RC as well before the final comes out.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 4:26 am
by Herve33
So no choice, I have to install the current stable, and reinstall later when the new version will be released.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 4:42 am
by chrispop99
Herve33 wrote: Sat Aug 31, 2019 4:26 am
So no choice, I have to install the current stable, and reinstall later when the new version will be released.
This isn't really the right place to discuss this, but no, you won't have to reinstall unless you want to. The Debian version of MX Linux 18.3 will be supported until June 2022, and further support from MX is likely.
Chris
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 5:23 am
by Herve33
Thank you for this clarification, excuse me if I'm not in the right column. Thank you all for your work!
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 5:26 am
by mystic
I have noticed the workplace switcher in the panel is not highlighting the current panel as blue when switching to Arc or arc dark theme in the appearance. It behaves the same way with adwaita-dark too.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 8:05 am
by dolphin_oracle
rpcm wrote: Tue Aug 27, 2019 3:11 am
Just found out about MX recently and wanted to try out XFCE 4.14, so I'm writing this from the MX-19 Beta! So far things are running
very well. Nice work dev team! Also, it is great to see another non-systemd distro, although I am not completely opposed to systemd, I am glad there are options out there.
I did notice a small quirk when booting into the system using full disk encryption. If you have a very long passphrase, it goes outside the display box. Other distros handle this better and hide any input that goes outside the box. Here's a photo for reference:
so the plymouth login box isn't really a box. its a graphic that looks like a box. as such it doesn't dynamically expand. I can make it bigger (I think), but the question is....when is too big or not big enough?
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 8:07 am
by AK-47
Why even have it as a box? If you know where the password starts, or have control over the start of the dots, you can put just the lock without the box.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 9:42 am
by milton
.
Not so much a bug .... but a typo.
File ...... /etc/X11/xorg.conf.d/synaptics.conf line 14 ...... looks like a space used where should be a tab.
Option "HorizEdgeScroll" "1" #### this line.####
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 11:30 am
by chrispop99
The Whisker menu is still showing the now superfluous 'Switch User' icon at the top. It just needs unticking in the Properties>Commands dialogue.
Chris
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 11:50 am
by Jerry3904
Superfluous -- a certain redundancy often helps the user, no?
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 12:57 pm
by TJ Hoye
Eadwine Rose wrote: Tue Aug 27, 2019 6:01 am
Just installed the beta, the one thing I noticed is that even though I told the liveUSB the timezone, it didn't handle it like it should, it was 2 hours ahead IIRC. Only when I ticked that it should use LOCAL in mx time settings did it jump to the right time. That is the only thing I saw so far that was wonky, but easily sorted. I rebooted back into 18.3 right after the install, just to see that it was still there
I am such a wuss.
Me, too. Thanks for the hint.
Now,... about the ghost of logins past that occurs on shut-down....
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 1:09 pm
by chrispop99
Jerry3904 wrote: Sat Aug 31, 2019 11:50 am
Superfluous -- a certain redundancy often helps the user, no?
I'm not sure how having an icon that doesn't do anything is helpful.
Chris
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 1:11 pm
by Jerry3904
Just have to change the code behind it, no?
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 1:14 pm
by Eadwine Rose
TJ Hoye wrote: Sat Aug 31, 2019 12:57 pm
Now,... about the ghost of logins past that occurs on shut-down....
You have to elaborate a bit more on that if you want us to understand what you mean?
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 1:37 pm
by TJ Hoye
TJ Hoye wrote: Sat Aug 31, 2019 12:57 pm
Now,... about the ghost of logins past that occurs on shut-down....
[quote}
You have to elaborate a bit more on that if you want us to understand what you mean?
[/quote]
Thanks for your suggestion about answering the local time prompt; that solved one nit I noted.
On my hint about a 'ghost',
I wanted first to revierw 32 pages of posts to see if my complaint was already covered.
I didn't catch any other similar complaints to what I notice peculiar to MX-19.
I've chosen to replace MX-19's original desktop background image with my own.
On shut-down I see, briefly a login screen with the original background image briefly before
things complete an otherwise orderly shutdown. I could just ignore this, but I'd rather get
rid of this 'ghost' if I knew how.
Otherwise, MX-19 beta is functional for all my needs AFAICT.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 1:45 pm
by Eadwine Rose
Oh THAT ghost.. that is seeing the login again after logout, yep same here.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 1:50 pm
by chrispop99
Jerry3904 wrote: Sat Aug 31, 2019 1:11 pm
Just have to change the code behind it, no?
But why? There is already a built-in way to switch user, and the additional icon does nothing at the moment as mx-switchuser is not installed. Should we not just remove the icon by unticking? Or am I missing something obvious here? (Entirely possible!)
Chris
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 2:03 pm
by Jerry3904
OK, not important
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 2:13 pm
by fehlix
chrispop99 wrote: Sat Aug 31, 2019 1:50 pm
Jerry3904 wrote: Sat Aug 31, 2019 1:11 pm
Just have to change the code behind it, no?
But why? There is already a built-in way to switch user, and the additional icon does nothing at the moment as mx-switchuser is not installed. Should we not just remove the icon by unticking? Or am I missing something obvious here?
Switch User Icon in the menu makes sense to me, as it has been there always and does not require to open first the logout popup. The missing mx-switchuser could be replace by "xfce4-session-logout --switch-user".
But the good thing about original "mx-switchuser" is that the user get's a little info-popup , where the user get explained how to switch between the VT's. So I would suggest, we keep the icon in the menu, but also adjust the mx-switch so it still's show the info to the user and use the new "xfce4-session-logout --switch-user".
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 3:13 pm
by dolphin_oracle
chrispop99 wrote: Sat Aug 31, 2019 1:50 pm
Jerry3904 wrote: Sat Aug 31, 2019 1:11 pm
Just have to change the code behind it, no?
But why? There is already a built-in way to switch user, and the additional icon does nothing at the moment as mx-switchuser is not installed. Should we not just remove the icon by unticking? Or am I missing something obvious here? (Entirely possible!)
Chris
Yeah I meant to change that to the xfce switcher. We are actaully overriding the default with out old settings. Will adjust
.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 7:51 pm
by joesplace
MX Updater having errors trying to update:
Err:1
http://mxrepo.com/mx/repo buster/main amd64 mx-cleanup amd64 19.8.1
404 Not Found [IP: 70.40.214.183 80]
E: Failed to fetch
http://mxrepo.com/mx/repo/pool/main/m/m ... _amd64.deb 404 Not Found [IP: 70.40.214.183 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 7:53 pm
by dolphin_oracle
the repos are updating pretty much now, so just hold on a bit.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 8:19 pm
by dolphin_oracle
until the mx-cleanup missing file is resolved, you can use
Code: Select all
sudo apt dist-upgrade --ignore-missing
to upgrade any other package that is available for download.
Timeout error creating a new folder or file mx19 beta [SOLVED]
Posted: Sat Aug 31, 2019 8:39 pm
by porkfriedmike
Right click on desktop, click create folder, type folder name in under 25 seconds or you receive a timeout error.
Repeatable on 2 different desktops, after rebooting and fresh default installs. Doesn't happen mx-18 or mx-17.
Let me know if I posted in the wrong place.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 9:11 pm
by dolphin_oracle
dolphin_oracle wrote: Sat Aug 31, 2019 8:19 pm
until the mx-cleanup missing file is resolved, you can use
Code: Select all
sudo apt dist-upgrade --ignore-missing
to upgrade any other package that is available for download.
fixed now. thanks tim.
Re: Timeout error creating a new folder or file mx19 beta
Posted: Sat Aug 31, 2019 10:09 pm
by JayM
There's already a dedicated topic for MX-19b1 feedback.
viewtopic.php?f=94&p=524568#p524568
Re: Timeout error creating a new folder or file mx19 beta
Posted: Sat Aug 31, 2019 10:10 pm
by dolphin_oracle
there doesn't appear to be a way to adjust that timeout. however, if you use the Desktop folder in your home folder inside thunar instead of on the desktop, the timeout doesn't appear to apply in my tests.
Re: MX-19 Beta 1 Feedback
Posted: Sat Aug 31, 2019 10:23 pm
by mystic
mystic wrote: Sat Aug 31, 2019 5:26 am
I have noticed the workplace switcher in the panel is not highlighting the current panel as blue when switching to Arc or arc dark theme in the appearance. It behaves the same way with adwaita-dark too.
Devs,
Please take a look at the above post. I found the issue with arc-darker too. A number of other themes are effected too.
Re: Timeout error creating a new folder or file mx19 beta [SOLVED]
Posted: Sat Aug 31, 2019 11:16 pm
by porkfriedmike
Thanks Jay and dolphin. Trying to learn with a 65 year old brain. I know just enough to be dangerous with a computer.
Re: Timeout error creating a new folder or file mx19 beta [SOLVED]
Posted: Sun Sep 01, 2019 12:09 am
by JayM
porkfriedmike wrote: Sat Aug 31, 2019 11:16 pm
Thanks Jay and dolphin. Trying to learn with a 65 year old brain. I know just enough to be dangerous with a computer.
Hey, I'll be 62 in October. If you'll just hold still for three years I'll catch up to you!
Re: MX-19 Beta 1 Feedback
Posted: Sun Sep 01, 2019 2:12 am
by SwampRabbit
I just updated the beta using MX Updater, but now I'm seeing an odd issue in Synaptic right now, using the Search function (not Quick filter) for i386 packages doesn't seem to work.
I've attempted it add ":i386" to package names and it doesn't work either.
apt-cache tells me Buster i386 packages are there, verified in Synaptic that the packages show up under the "Architecture" tab using All, arch:all, and arch:i386, but searching for them doesn't work. I'm also seeing multiple duplicate entries for some packages that aren't installed as I look through Synaptic.
Here is the history from MX Updater for the updates today:
Code: Select all
2019-08-31 23:58:46 upgrade mx-snapshot amd64 19.8.2 19.8.3
2019-08-31 23:58:46 upgrade mx-packageinstaller-pkglist all 19.08.03 19.08.04
2019-08-31 23:58:46 upgrade mx-cleanup amd64 19.8 19.8.1
2019-08-31 23:58:46 upgrade mx-boot-options amd64 19.8 19.8.1
2019-08-31 23:58:46 upgrade grub-themes-mx all 19.08.02 19.08.03
2019-08-31 23:58:46 upgrade desktop-defaults-mx-xfce all 19.08.03 19.08.04
2019-08-31 23:58:45 upgrade desktop-defaults-mx-common all 19.07.01 19.08.01
2019-08-31 23:58:45 upgrade ddm-mx all 19.08.02 19.08.03
I installed this VM yesterday and updated it twice and that's about it.
Re: Timeout error creating a new folder or file mx19 beta [SOLVED]
Posted: Sun Sep 01, 2019 4:52 am
by Eadwine Rose
I'll see about merging this thread into the beta one.
Edit: I'll see about asking Rich to merge this. *snort*
Re: MX-19 Beta 1 Feedback
Posted: Sun Sep 01, 2019 10:19 am
by dolphin_oracle
mystic wrote: Sat Aug 31, 2019 10:23 pm
mystic wrote: Sat Aug 31, 2019 5:26 am
I have noticed the workplace switcher in the panel is not highlighting the current panel as blue when switching to Arc or arc dark theme in the appearance. It behaves the same way with adwaita-dark too.
Devs,
Please take a look at the above post. I found the issue with arc-darker too. A number of other themes are effected too.
yes it just highlights with a white border. its a feature of the themes.
Re: MX-19 Beta 1 Feedback
Posted: Sun Sep 01, 2019 10:41 am
by asqwerth
Is Arc still being maintained? I understand from reading Manjaro forums previously that the original dev Horst no longer does it, and someone else took over:
https://github.com/NicoHood/arc-theme
Are we getting the theme from the new source for MX19/Buster? Or are we reusing the old Arc theme from Horst?
I ask this because currently in MX15/16 and MX17/18, so long as I install the flatpak version of Arc themes, and I apply Arc (or any Arc-based) theme (even those made in oomox with different colour combinations) on my normal system/desktop, my flatpak apps will follow the theming of my desktop.
But in MX19 Beta, my flatpak app totally ignores my desktop's Arc theme, and shows up in the gnome default Adwaita (light) theme, which I really dislike.
In comparison, flatpak greybird theme is applied if I am using greybird on my desktop.
Could that be also the reason why the XFCE workplace switcher/panel theming isn't so great with Arc?
Re: MX-19 Beta 1 Feedback
Posted: Sun Sep 01, 2019 1:32 pm
by dolphin_oracle
asqwerth wrote: Sun Sep 01, 2019 10:41 am
Is Arc still being maintained? I understand from reading Manjaro forums previously that the original dev Horst no longer does it, and someone else took over:
https://github.com/NicoHood/arc-theme
Are we getting the theme from the new source for MX19/Buster? Or are we reusing the old Arc theme from Horst?
I ask this because currently in MX15/16 and MX17/18, so long as I install the flatpak version of Arc themes, and I apply Arc (or any Arc-based) theme (even those made in oomox with different colour combinations) on my normal system/desktop, my flatpak apps will follow the theming of my desktop.
But in MX19 Beta, my flatpak app totally ignores my desktop's Arc theme, and shows up in the gnome default Adwaita (light) theme, which I really dislike.
In comparison, flatpak greybird theme is applied if I am using greybird on my desktop.
Could that be also the reason why the XFCE workplace switcher/panel theming isn't so great with Arc?
remember, the panel is now gtk3, so the same theme elements aren't being used. Just because something doesn't look like it did under gtk2 doesn't mean there is a problem, it just means its different.
I can't speak for the flatpak stuff though. the arc themes in use are from debian's archive.
**edit*** testing with abiword flatpak, if the flatpaks themes for arc and arc-dark are installed, abiword follows the respective theme ok.
Re: MX-19 Beta 1 Feedback WIFI
Posted: Sun Sep 01, 2019 4:27 pm
by gabbman
Installed and working fine on my HP Pavillion laptop, but the wifi drops off without warning and keeps asking by to put in the password again.
Re: MX-19 Beta 1 Feedback
Posted: Sun Sep 01, 2019 9:49 pm
by jj1j1
I haven't seen kodi mentioned yet. If so, I will re affirm that addons are not installing. (at least not for me). I tried with a laptop, and desktop; same issue. It will download zip, but when I try to install repository I get a dependency error. I've tried several different addons. Although different dependencies for different addons it's the same pattern.
Forgot to mention that this is the kodi from mxpi.
Example:
Re: MX-19 Beta 1 Feedback
Posted: Mon Sep 02, 2019 7:56 am
by TerryL
OK, I've been using MX-19b1 for nearly a week now as my daily driver and I have to say, apart from 2 small maybe errors in the installer, it's given me no problems at all. My usage probably isn't the most rigorous, poke all the corners, test all the features testing, just my daily tasks.
I have it now as the main boot option on 4 (laptop) machines, the 4 that one of which one is always within arms reach wherever I am around the flat (apartment). The 1st is on a Dell Latitude E6510, it was a clean install onto a partition that had had Devuan that I had been playing with. The 2 small errors with the install were that at 2 points the installer seemed to stall until I noticed it said it was waiting for user input. Clicking on the Next button took me to the next dialog where it wanted the input (i.e. I think it should have gone to that dialog automatically). Once those 2 steps were taken it completed the install, rebooted and it has been working fine ever since.
On the other 3 machines (A Thinkpad X230, a Thinkpad T430 and an HP EliteBook 8470p) I ran the install and told it to re-use the MX-18.3 partitions on those machines but leave the data on the /home directory. I've heard that this may not always work and seen one report of someone having a problem. I however have had no problems and once I'd re-installed my normal default packages (I have a script to do that) everything was working and I didn't have to reconfigure any of the packages.
I did, for once, change the themes (normally for MX-17 and MX-18 I've been perfectly happy with the stock themes. I'm using Arc-Dark for the desktop and Window Manager and Papirus-Dark for the icons. I also picked up a selection of wallpapers from wallpaperscraft.com (nice though the default grass wallpaper is) to better suit my dark themes.
I've used one or other of these 4 machine since last Wednesday (today is Monday) without problems. I've done a bit of SimpleScreenRecorder, I've used OpenShot, Compiled a couple of my C programs, run my personal scripts to do those things that I have scripts for and tested all the applications that I install as my standard add-on packages. Everything is working.
I'm sorry I can't contribute more to help the devs fix bugs, but I simply don't seem to do anything where bugs are lurking.
Well done to everyone responsible for MX-19 beta 1. MX continues to be my default distro.
Re: MX-19 Beta 1 Feedback
Posted: Mon Sep 02, 2019 2:50 pm
by harperx
A month ago I'd never heard of MX Linux. I've bounced back and forth between Windows and Linux over the years, and I was tired of Windows bloat and slowness. I was probably going to load Debian again until I noticed you on Distrowatch, and checked it out. I demo'd the 18.3 as live, and just before I loaded it, the 19 beta 1 came out. I took a chance, and I'm so glad I did. Install on my Dell Inspiron 620 was quick and uneventful. Everything worked out of the box, and it's been running rock solid for several days now. No bugs to report!
MX Linux matches my needs very well (solid, quick-running desktop on older hardware). The devs are the nicest I've ever met on a forum like this. I'm very grateful to benefit from all your hard work. Thank you!
Re: MX-19 Beta 1 Feedback
Posted: Mon Sep 02, 2019 4:37 pm
by Jerry3904
duane wrote: Tue Aug 27, 2019 2:16 pm
MX Conkypatch conky shows different date on calendar than on line in conky.
calendar says 23 line says 27th.
Thanks for the comment. Revising the data set now, I wanted to circle back to your comment. The "calendar" is just an icon, not an active object; the good news is that once a month it is going to look right and all will be well in the world again!
Re: MX-19 Beta 1 Feedback
Posted: Tue Sep 03, 2019 6:46 am
by Fibogacci
My first remarks after running MX-19 Beta 64 bit (Live USB).
1. Just after start MX-19 64bit Live USB memory usage (idle) is about 600 MB (in MX 18 it was about 300 MB less or more if I remember correctly). Is it because of Xfce 4.14?
2. MX Time Settings has no translations (I've checked in Polish and German versions) - it is in English.
3. MX Tweak - after clicking on Panel button, window is appearing below the main MX Tweak window which is still there.
Re: MX-19 Beta 1 Feedback
Posted: Tue Sep 03, 2019 8:53 am
by nixy
600? That's a lot. I'm hovering around 400.
Re: MX-19 Beta 1 Feedback
Posted: Tue Sep 03, 2019 11:54 am
by SwampRabbit
I'm trying to get my system specific application install/uninstall scripts set up for MX-19 when it releases. I use these to configure each system in the house quickly.
When adding the MX Test Repo in Synaptic I assume it's supposed to be showing up (at least for now) as "Not automatic: mx(mxrepo.com)" under "Origin".
Synaptic shows this "Not automatic: mx(mxrepo.com)" repo only having 294 packages, but....
MXPI shows 387 total packages in the MX Test Repo
Things like: cpuidtool, tlpui, i-nex used to be in the MX-18 Test Repo but don't exist under MX-19, even in the test repo yet.
I think I saw a post that not all test repo packages have been migrated yet to MX-19, but right now I'm just trying to figure out why Synaptic and MXPI are showing deltas.
The reason I use Synaptic is because I mark all the packages, recommends, and extra libs I use/need... then save out the markings to populate the scripts.
Kinda wonky I know but it works for me.
Also, the Debian Backports tab in MXPI seems to still not do anything, not sure if its supposed to at this point or not.
Re: MX-19 Beta 1 Feedback
Posted: Tue Sep 03, 2019 12:04 pm
by dolphin_oracle
we've changed the way the apt repos work. MX Test Repo now work similar to debian-backports, where you need to specify the -t to install. like this
I'm not sure how to duplicate that in synaptic, although there is probably a way.
also, mxpi counts total packages. synaptic may only be counting different packages, because some packages may be in both main and test. that's a guess though.
we've updated mx-packageinstaller to be able to access debian-backports. it wasn't at first but should after an update.
Re: MX-19 Beta 1 Feedback
Posted: Tue Sep 03, 2019 12:26 pm
by SwampRabbit
@dolphin ok thanks for that info.
Shouldn't clicking on "Origin" in Synaptic and then selecting the repo show everything in that repo though? That was my guess at least.
It's not a big deal, as when searching for packages the same version shows up in MXPI and Synaptic.
Re: MX-19 Beta 1 Feedback
Posted: Tue Sep 03, 2019 12:33 pm
by SwampRabbit
Very cool, always good to learn something new, thanks!
Re: MX-19 Beta 1 Feedback
Posted: Tue Sep 03, 2019 9:39 pm
by smilliken
Code: Select all
System: Host: mx1 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19beta-1_x64 patito feo August 25 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: Apple product: MacBookPro12,1 v: 1.0 serial: <filter> Chassis:
type: 9 v: Mac-E43C1C25D4880AD6 serial: <filter>
Mobo: Apple model: Mac-E43C1C25D4880AD6 v: MacBookPro12,1 serial: <filter>
UEFI: Apple v: 184.0.0.0.0 date: 04/11/2019
Battery: ID-1: BAT0 charge: 51.8 Wh condition: 62.1/74.8 Wh (83%) volts: 11.9/11.4
model: SMP bq20z451 type: Li-ion serial: N/A status: Discharging cycles: 463
CPU: Topology: Dual Core model: Intel Core i5-5257U bits: 64 type: MT MCP arch: Broadwell
family: 6 model-id: 3D (61) stepping: 4 microcode: 2B L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21598
Speed: 1201 MHz min/max: 500/3100 MHz Core speeds (MHz): 1: 1201 2: 1200 3: 1200
4: 1200
Vulnerabilities: Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Graphics: Device-1: Intel Iris Graphics 6100 vendor: Apple driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:162b
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 2560x1600~60Hz
OpenGL: renderer: Mesa DRI Intel Iris 6100 (Broadwell GT3) v: 4.5 Mesa 18.3.6
compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel Broadwell-U Audio vendor: Apple driver: snd_hda_intel v: kernel
bus ID: 00:03.0 chip ID: 8086:160c
Device-2: Intel Wildcat Point-LP High Definition Audio driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:9ca0
Device-3: Broadcom Limited 720p FaceTime HD Camera driver: N/A bus ID: 02:00.0
chip ID: 14e4:1570
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC vendor: Apple
driver: brcmfmac v: kernel port: efa0 bus ID: 03:00.0 chip ID: 14e4:43ba
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 938.97 GiB used: 183.7 MiB (0.0%)
ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P1SSD8 size: 931.51 GiB block size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter>
rev: P3CR010 scheme: GPT
ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 2.0 size: 7.46 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: MBR
Partition: ID-1: / raw size: N/A size: 6.10 GiB used: 183.7 MiB (2.9%) fs: overlay
source: ERR-102
Sensors: System Temperatures: cpu: 45.5 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 202 Uptime: 9m Memory: 7.70 GiB used: 587.9 MiB (7.5%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
running in: quick-system-in inxi: 3.0.33
Looks very eye appealing. I'm trying this on a Macbook Pro 2015 and the resolution is very tiny. 2560 x 1600. I need a magnifying glass to read the screen. Running off of a USB Live. BT icon disappeared on my while trying to connect my mouse. WiFi connected right off the hop. The track pad was not user friendly, but probably would adjust that if I were to install on the device.
Internet works just fine.
Poking around the other packages, this seems like it is almost ready for Prime Time.
Re: MX-19 Beta 1 Feedback
Posted: Tue Sep 03, 2019 11:40 pm
by asqwerth
smilliken wrote: Tue Sep 03, 2019 9:39 pm
...Looks very eye appealing. I'm trying this on a Macbook Pro 2015 and the resolution is very tiny. 2560 x 1600. I need a magnifying glass to read the screen. ....
Have you tried the 2x scaling function in:
https://docs.xfce.org/xfce/xfce4-settings/appearance
Window Scaling
You can switch between factor 1x (normal default) and 2x for HiDPI displays. It is advised to restart your session after altering this setting as not all applications may succeed in doing a live-reload.
Why not test it and give your comments/opinion on it in this thread.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 12:26 am
by jj1j1
Why not test it and give your comments/opinion on it in this thread.
I tried it in my dell precision. The display is set to 3840x2160. Initially when I set it to 2x half of the Appearance dialog box blinks out. Bring up another dialog box and it comes back to normal. The xfce panel seems traumatize too. Some icons superimpose over them self, and the whisker menu disappears. If I go to panel preferences, and jiggle the Row Size a bit the icons correct themselves, and whisker menu re appears.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 1:05 am
by asqwerth
Did you log out and in again? That's the advice given in the XFCE page I quoted and linked to.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 1:11 am
by asqwerth
dolphin_oracle wrote: Sun Sep 01, 2019 1:32 pm
asqwerth wrote: Sun Sep 01, 2019 10:41 am
...But in MX19 Beta, my flatpak app totally ignores my desktop's Arc theme, and shows up in the gnome default Adwaita (light) theme, which I really dislike.
In comparison, flatpak greybird theme is applied if I am using greybird on my desktop....
...I can't speak for the flatpak stuff though. the arc themes in use are from debian's archive.
**edit*** testing with abiword flatpak, if the flatpaks themes for arc and arc-dark are installed, abiword follows the respective theme ok.
Yeah, I only tested with flatpak Lollypop.
I'm now suspecting that because Lollypop is very actively updated, it's using a Gnome runtime so far in advance of the runtime version for the flatpak arc themes that they aren't really compatible.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 1:49 am
by mbiba77
I have tested Beta 1. Everything works fine on my Dell Latitude E6500 although it is necessary to setup lot of thinks manually because GUI settings dialogs is unfunctional in couple of cases. For example region and language section is not working correctly yet. This is beta :-)
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 2:21 am
by chrispop99
mbiba77 wrote: Wed Sep 04, 2019 1:49 am
For example region and language section is not working correctly yet. This is beta :-)
Welcome to the forum.
Do you have th region and language problem during installation, or after it is installed?
Chris
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 3:40 am
by mbiba77
During installation the proper region was not set and I have to set it manually in installation. When change manually during install, the default region keyboard layout was not chosen. I had to do it after the boot manually.
Also settings GUI dialogs looks strange, so to set something up is a case with mixing the gui usage and terminal.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 5:28 am
by mxer
So far, I have it installed on a Toshiba Chromebook 16GB eMMC, (presently no sound, not sure why just yet), an Acer AO722 320GB HDD & an Acer AO532 50GB SSD notebooks, plus running it from an 8GB SDHC card in my old Toshiba Satellite, all fitted with just 2GB ram.
Other than the Chromebook, everything seems to be working fine for what I use these machines for, mainly online browsing, forums, email, & playing music.
I did get the problem of the automount causing problems with one of the installs though, not sure why, I didn't do anything differently, as far as I can remember.
Definately looking good.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 8:49 am
by Parnikkapore
Tried installing Budgie (all Budgie packages in the buster repo) and GNOME Tweaks, and then the theming broke and Budgie crashed on login from the second time forward...?
I really need to track down the logs.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 9:05 am
by asqwerth
Doesn't Budgie have its own Budgie-desktop-settings tool now, forked from Gnome-tweaks?
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 11:01 am
by smilliken
I will and report back.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 11:41 am
by masinick
Just downloaded and put on a removable USB stick. So far early testing is perfect. This hardware has always worked well with Debian, antiX, MEPIS, and MX Linux.
Code: Select all
inxi -Fxz
System: Host: mx1 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.14.1 Distro: MX-19beta-1_x64 patito feo August 25 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: Dell product: Inspiron 5558 v: 01 serial: <filter>
Mobo: Dell model: 086DKN v: A00 serial: <filter> UEFI: Dell v: A04 date: 08/06/2015
Battery: ID-1: BAT0 charge: 37.7 Wh condition: 37.7/41.4 Wh (91%)
model: Samsung SDI DELL 07G07587587 status: Full
CPU: Topology: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP arch: Broadwell
rev: 4 L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156
Speed: 798 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798
Graphics: Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
Device-2: NVIDIA GK208M [GeForce 920M] vendor: Dell GK208BM driver: nouveau v: kernel
bus ID: 08:00.0
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) v: 4.5 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel v: kernel
bus ID: 00:03.0
Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: f040 bus ID: 06:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet
vendor: Dell RTL810xE driver: r8169 v: kernel port: e000 bus ID: 07:00.0
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 946.42 GiB used: 943.8 MiB (0.1%)
ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB
temp: 29 C
ID-2: /dev/sdb type: USB vendor: Corsair model: Voyager 3.0 size: 14.91 GiB
Partition: ID-1: / size: 6.11 GiB used: 943.8 MiB (15.1%) fs: overlay source: ERR-102
ID-2: swap-1 size: 7.91 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 57.0 C mobo: N/A sodimm: 39.0 C gpu: nouveau temp: 25 C
Fan Speeds (RPM): cpu: 0 fan-2: 0 fan-3: 0
Info: Processes: 204 Uptime: 18m Memory: 7.70 GiB used: 1.22 GiB (15.8%) Init: SysVinit
runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33
demo@mx1:~
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 12:51 pm
by pato_acevedo
I m testing MX-19 Beta in my dell Lattitude. I need R &R-Studio for my work.
This resources make the magic!!
https://kevcaz.github.io/notes/r/updatingtor3_6_0/
Add cran repository for most new R vertion.
And for R-studio just a reported dependence. Rstudio wants libssl1.0.2 but Debian 10 have libssl1.1
https://github.com/rstudio/rstudio/issues/4670
Solution: Download libssl1.0.2 from stretch.
https://i.postimg.cc/DyPkpTpN/mx.jpg
mod note: image changed to link. Please be mindful of remote image sizes: viewtopic.php?f=133&t=48374
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 1:08 pm
by Jerry3904
Thanks.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 1:38 pm
by rej
Hi-
19 looks nice!
When attempting to change the panel opacity to transparent, found that it looks like the "Alpha" slider bar is missing, and it won't function properly without it.
Attachments are Debian 10, antiX 19 B3 [these both work], and MX19 B1.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 1:58 pm
by Eadwine Rose
rej wrote: Wed Sep 04, 2019 1:38 pm
Hi-
19 looks nice!
When attempting to change the panel opacity to transparent, found that it looks like the "Alpha" slider bar is missing, and it won't function properly without it.
Yes, that looks like what I saw.. Alpha is gone. I can change the in and out, but there is no making it transparent just like that.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 2:04 pm
by asqwerth
Debian 10 is still using XFCE 4.12. Probably antiX beta as well.
MX19 is using XFCE 4.14. It's the gtk3 toolkit, I think. Just like you no longer get colour droppers to help you choose a colour from anywhere in your desktop.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 2:36 pm
by gordonthegopher84
First of all, thanks to the devs for an excellent release! I'm on a real potato, an Acer Cloudbook 14 AO1-431 with a terrible Celeron N3060, 2GB of un-upgradable soldered on RAM and a 32GB soldered on and un-upgradeabe eMMC drive. I tried a minimal installation of Kubuntu 18.04 first, since there was lots of talk of Plasma's low RAM and CPU usage in this thread; in my testing this was also true at first (about 350Mb used and minimal CPU usage), and MX-19 Beta 1 was more like 400-450Mb, but MX-19 seems a lot better at memory management once I open a few tabs of Firefox (I setup zram on both the Kubuntu and MX19 installs - one device per CPU core (so two), each one being about 700Mb, which is using the default SysV /etc/init.d/zram config as detailed in the Debian Wiki:
https://wiki.debian.org/ZRam). Kubuntu just locked up after a while, and I had to force power off as I couldn't even get a tty1 to pkill the session. While MX19 chugs if I
really push it, it has a lot more mileage for me compared to Kubuntu.
One problem: when I suspend this machine, it often crashes on wakeup after I've put my password in. As others have noted, the default on MX19 Beta 1 is that "Enable Lock Screen" under "Whisker Menu>XFCE4 Screensaver>Lock Screen tab" is
not selected. At first, when suspending and resuming, there was no lock screen at all! I've enabled it, along with "Lock Screen with Screensaver" and "Lock Screen with System Sleep". It doesn't always crash after I put my password in after resuming from suspend, but it does often enough to be a little bit annoying. I have to go to tty1 with Ctrl+Alt+F1, login as my user, then select
but obviously this creates a new session, meaning anything I had open on suspend is gone. Not a massive issue, as I usually clean everything up and close every running program before suspending as a rule, but it is annoying. There are some upstream bugs open for xfce4-screensaver (which I know is new for XFCE 4.14) on the XFCE Bugzilla, but people request the output of
which doesn't work as I'm not running systemd. I was under the impression SysV doesn't keep logs in the same way? Happy to pull some out if anyone can give me some pointers...
**EDIT** This actually also happens when the screensaver activates while the machine is still on - I move the mouse, the lock screen (lightdm?) appears, I put my password in, and then everything freezes. Have to tty1 and force a restart of lightdm to get out of it, which starts a new session, losing anything I had open.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 2:52 pm
by richb
Eadwine Rose wrote: Wed Sep 04, 2019 1:58 pm
rej wrote: Wed Sep 04, 2019 1:38 pm
Hi-
19 looks nice!
When attempting to change the panel opacity to transparent, found that it looks like the "Alpha" slider bar is missing, and it won't function properly without it.
Yes, that looks like what I saw.. Alpha is gone. I can change the in and out, but there is no making it transparent just like that.
You can make it transparent.In panel Preferences>Appearance then solid color. click on the color block. Then click on the custom plus, (right under the word "Custom". It will bring up a color dialogue. Move the slider under the color winow all the way to the left, then click Select.. This will give you a transparent panel.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 3:35 pm
by Jerry3904
Keep forgetting to put that in the Manual...thanks.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 4:01 pm
by Ghost67
Eadwine Rose wrote: Wed Sep 04, 2019 1:58 pm
rej wrote: Wed Sep 04, 2019 1:38 pm
Hi-
19 looks nice!
When attempting to change the panel opacity to transparent, found that it looks like the "Alpha" slider bar is missing, and it won't function properly without it.
Yes, that looks like what I saw.. Alpha is gone. I can change the in and out, but there is no making it transparent just like that.
I show how to change panel alpha in my video here:
https://www.youtube.com/watch?v=RgqEa0N9DmU
HTH
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 4:15 pm
by Eadwine Rose
I'll try this out sometime tomorrow. Thanks Rich!
And thank you too Ghost67
That is quite different from the "old" way.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 5:05 pm
by jj1j1
Did you log out and in again?
No. That was without logging out.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 5:24 pm
by richb
Eadwine Rose wrote: Wed Sep 04, 2019 4:15 pm
I'll try this out sometime tomorrow. Thanks Rich!
And thank you too Ghost67
That is quite different from the "old" way.
It is and not obvious at all.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 5:44 pm
by Ghost67
richb wrote: Wed Sep 04, 2019 5:24 pm
Eadwine Rose wrote: Wed Sep 04, 2019 4:15 pm
I'll try this out sometime tomorrow. Thanks Rich!
And thank you too Ghost67
That is quite different from the "old" way.
It is and not obvious at all.
I'm curious as to whether there is still any way ('under the hood' so to speak) to add transparency to a panel that uses the system style for its colouring?
It has to still be there somewhere, right?
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 5:56 pm
by richb
Ghost67 wrote:I'm curious as to whether there is still any way ('under the hood' so to speak) to add transparency to a panel that uses the system style for its colouring?
It has to still be there somewhere, right?
I am not sure it has to be there. The result would be the same. Would it not?
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 6:08 pm
by Ghost67
richb wrote: Wed Sep 04, 2019 5:56 pm
Ghost67 wrote:I'm curious as to whether there is still any way ('under the hood' so to speak) to add transparency to a panel that uses the system style for its colouring?
It has to still be there somewhere, right?
I am not sure it has to be there. The result would be the same. Would it not?
I guess so. Using the eyedropper tool and transparency slider.
(I've edited here): Originally I suggested that 4.12 could add transparency to the panel if an image was used for the background, but testing on MX-18 says I was wrong :)
So I guess we pretty much have the same functionality in 4.14 that we had in 4.12 - just a different GUI.
Cheers Richb.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 6:23 pm
by dreamer
Ghost67 wrote: Wed Sep 04, 2019 5:44 pm
richb wrote: Wed Sep 04, 2019 5:24 pm
Eadwine Rose wrote: Wed Sep 04, 2019 4:15 pm
I'll try this out sometime tomorrow. Thanks Rich!
And thank you too Ghost67
That is quite different from the "old" way.
It is and not obvious at all.
I'm curious as to whether there is still any way ('under the hood' so to speak) to add transparency to a panel that uses the system style for its colouring?
It has to still be there somewhere, right?
I don't think so. If there was it wouldn't have been removed from Settings Manager? Maybe it's possible to achieve a similar result by using Solid Color option and Alpha Slider in Color chooser. Maybe Xfce devs thought it was redundant?
You found one of the very few regressions in Xfce 4.14.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 7:26 pm
by richb
Not a regression. Just a different way to do it.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 7:42 pm
by dreamer
richb wrote: Wed Sep 04, 2019 7:26 pm
Not a regression. Just a different way to do it.
Alpha slider has been removed from "system style".
System Style - Alpha present in 4.12 but NOT in 4.14
Solid Color - Alpha present in both 4.12 and 4.14
Panel background - Alpha was never an option, transparency dictated by the image file.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 7:58 pm
by richb
Post #367. Gives the same effect as alpha.If the end result is the same I do not see it as a regression. But whatever.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 8:17 pm
by dolphin_oracle
BTW since the color and transparency are specified together as a color, it's possible for gtk themes to provide a panel that has some transparency, as it does with greybird, without messing with the panel settings themselves.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 9:05 pm
by JayM
richb wrote: Wed Sep 04, 2019 2:52 pm
Eadwine Rose wrote: Wed Sep 04, 2019 1:58 pm
rej wrote: Wed Sep 04, 2019 1:38 pm
Hi-
19 looks nice!
When attempting to change the panel opacity to transparent, found that it looks like the "Alpha" slider bar is missing, and it won't function properly without it.
Yes, that looks like what I saw.. Alpha is gone. I can change the in and out, but there is no making it transparent just like that.
You can make it transparent.In panel Preferences>Appearance then solid color. click on the color block. Then click on the custom plus, (right under the word "Custom". It will bring up a color dialogue. Move the slider under the color winow all the way to the left, then click Select.. This will give you a transparent panel.
Maybe this can be added to the manual or wiki. I foresee a lot of questions about this after 19 is released.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 9:18 pm
by smilliken
smilliken wrote: Wed Sep 04, 2019 11:01 am
I will and report back.
That does make a difference. Things were a bit screwed up, like the taskbar continued to be small and the icons were missing at the lower left. Time was unreadable in the upper left.
I'm sure if I was able to reboot the system and keep the state, this would have made a difference.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 9:41 pm
by Jerry3904
JayM wrote: Wed Sep 04, 2019 9:05 pm
richb wrote: Wed Sep 04, 2019 2:52 pm
Eadwine Rose wrote: Wed Sep 04, 2019 1:58 pm
Yes, that looks like what I saw.. Alpha is gone. I can change the in and out, but there is no making it transparent just like that.
You can make it transparent.In panel Preferences>Appearance then solid color. click on the color block. Then click on the custom plus, (right under the word "Custom". It will bring up a color dialogue. Move the slider under the color winow all the way to the left, then click Select.. This will give you a transparent panel.
Maybe this can be added to the manual or wiki. I foresee a lot of questions about this after 19 is released.
Yup, on my list for the next round.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 11:05 pm
by SwampRabbit
@dolphinoracle ... I've updated and it seems I still have and issue trying to use Debian Backports from MXPI. The issue just might be on my end, but mxpi.log only has:
Code: Select all
2019-09-04 22:54:22-- ftp://ftp.us.debian.org/debian/dists/buster-backports/main/binary-amd64/Packages.xz
=> ‘mainPackages.xz’
Resolving ftp.us.debian.org (ftp.us.debian.org)... 64.50.236.52, 64.50.233.100, 208.80.154.15, ...
Connecting to ftp.us.debian.org (ftp.us.debian.org)|64.50.236.52|:21... failed: Connection timed out.
Connecting to ftp.us.debian.org (ftp.us.debian.org)|64.50.233.100|:21... failed: Connection timed out.
Connecting to ftp.us.debian.org (ftp.us.debian.org)|208.80.154.15|:21... failed: Connection timed out.
Connecting to ftp.us.debian.org (ftp.us.debian.org)|2600:3404:200:237::2|:21... failed: Network is unreachable.
Connecting to ftp.us.debian.org (ftp.us.debian.org)|2620:0:861:1:208:80:154:15|:21... failed: Network is unreachable.
Connecting to ftp.us.debian.org (ftp.us.debian.org)|2600:3402:200:227::2|:21... failed: Network is unreachable.
Oddly enough I can get to ftp.us.debian.org just fine through Firefox.
I'll reinstall this VM tomorrow just in case I screwed something up at some point.
Re: MX-19 Beta 1 Feedback
Posted: Wed Sep 04, 2019 11:46 pm
by JayM
That sounds like an internal problem with whatever server at Debian is being used for the buster backports repo, or with a router or LAN issue in their datacenter. Maybe it will work later if you wait awhile.
Re: MX-19 Beta 1 Feedback
Posted: Thu Sep 05, 2019 1:31 am
by SwampRabbit
You know what Jay, you just sparked something.... IP address:21....
I forgot I am dropping everything outbound except what’s on my whitelist not only at my border router/firewall but also the default UFW config I load.... forgot some repos sometimes still use FTP!
In other words... issue is between chair and keyboard.
Re: MX-19 Beta 1 Feedback
Posted: Thu Sep 05, 2019 3:16 am
by JayM
Ah, good old PEBCAK.
Re: MX-19 Beta 1 Feedback
Posted: Thu Sep 05, 2019 3:19 am
by Eadwine Rose
Transparent panel, issue (rather.. how to) sorted indeed.
Also.. I have Orage in the panel, I believe that one also had issues with its (not showing) transparency. That looks to be sorted as well:
snapshot.png
Re: MX-19 Beta 1 Feedback
Posted: Thu Sep 05, 2019 8:01 am
by CaputAlista
one idea: auto check update notification show if there is a new version of mx
thanks.
Re: MX-19 Beta 1 Feedback
Posted: Thu Sep 05, 2019 4:27 pm
by rpcm
dolphin_oracle wrote: Sat Aug 31, 2019 8:05 am
so the plymouth login box isn't really a box. its a graphic that looks like a box. as such it doesn't dynamically expand. I can make it bigger (I think), but the question is....when is too big or not big enough?
How does Fedora handle this? The Plymouth box there hides any dots that go beyond the 'fake box'.
Re: MX-19 Beta 1 Feedback
Posted: Thu Sep 05, 2019 4:56 pm
by davemx
I have a problem with the MX19Beta, I'm not sure it is a bug, or just a way that the new version of the underlying code reacts to a USB item being plugged in. In any case, the upshot is that my One4All Remote URC6440 does not mount under MX19 though it does under MX18.
Because I'm not sure if it's a bug, I've posted under Hardware as well. I would be grateful to find out if anyone knows the answer to this. Link to other post:
viewtopic.php?f=107&t=52525
Stuck on formatting swap on the new beta
Posted: Fri Sep 06, 2019 4:50 am
by blindside
I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap. Have there been any reported issues with this?
D
Re: Stuck on formatting swap on the new beta
Posted: Fri Sep 06, 2019 4:59 am
by JayM
blindside wrote: Fri Sep 06, 2019 4:50 am
I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap. Have there been any reported issues with this?
D
Not that I've seen, but you can find out yourself by reading the MX-19 Beta 1 Feedback topic (to which this post should probably be moved?)
viewtopic.php?f=94&t=52318
Re: MX-19 Beta 1 Feedback
Posted: Fri Sep 06, 2019 5:44 am
by Eadwine Rose
Topics merged. I hope I did that right..
Re: Stuck on formatting swap on the new beta
Posted: Fri Sep 06, 2019 6:04 am
by mxer
blindside wrote: Fri Sep 06, 2019 4:50 am
I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap. Have there been any reported issues with this?
D
Sounds like it may be in use by the installer - I had to unmount & use swapoff on one of my 4 installs - this is the one usage that shouldn't have automount activated.
Re: MX-19 Beta 1 Feedback
Posted: Fri Sep 06, 2019 6:26 am
by Eadwine Rose
Actually now that you mention that.. I saw something like that too sometime. I don't remember if it was during the actual install or during the assigning of the partitions though.
*note to self: pay attention on the next beta install!*
Re: MX-19 Beta 1 Feedback
Posted: Fri Sep 06, 2019 6:33 am
by JayM
I thought the latest version of the installer which should be part of the beta did a swapoff already.
@blindside: It would be nice if you could open a terminal and run
then copy everything in the terminal and paste it here
inside of code tags.
Re: MX-19 Beta 1 Feedback
Posted: Fri Sep 06, 2019 11:43 am
by mxer
Eadwine Rose wrote: Fri Sep 06, 2019 6:26 am
Actually now that you mention that.. I saw something like that too ...
*note to self: pay attention on the next beta install!*
In my case it was whilst I was trying to assign the partitioning - but 3 of the 4 installs, I didn't have any bother from it.
Re: MX-19 Beta 1 Feedback
Posted: Fri Sep 06, 2019 2:20 pm
by blindside
JayM wrote: Fri Sep 06, 2019 6:33 am
I thought the latest version of the installer which should be part of the beta did a swapoff already.
@blindside: It would be nice if you could open a terminal and run
then copy everything in the terminal and paste it here
inside of code tags.
I will do that tonight. Just for reference, this is a newly installed nvme drive that was running Debian testing flawlessly. Also, I assume you want me to open a terminal in live?
Re: MX-19 Beta 1 Feedback
Posted: Fri Sep 06, 2019 2:56 pm
by dolphin_oracle
update the installer before trying again. also, "sudo -E" won't work. just run "minstall-pkexec" from the commandline. or just "sudo minstall".
Re: Stuck on formatting swap on the new beta
Posted: Fri Sep 06, 2019 4:40 pm
by Buck Fankers
blindside wrote: Fri Sep 06, 2019 4:50 am
I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap.
As a work around, if you don't plan to use hibernate, but only suspend, then swap file is better solution than swap partition.
You could try to install without swap partition then after installation is completed, run these 4 commands:
Code: Select all
sudo fallocate -l 2G /swapfile <- set the size (4G for 4GB, 8G for 8GB...)
sudo chmod 600 /swapfile <- set correct permission
sudo mkswap /swapfile <- format the swap file
sudo swapon /swapfile <- activate swap file
Re: Stuck on formatting swap on the new beta
Posted: Fri Sep 06, 2019 8:13 pm
by blindside
Thanks so much. Will be working on this after dinner
Re: MX-19 Beta 1 Feedback
Posted: Fri Sep 06, 2019 9:04 pm
by jj1j1
Has anyone got kodi, from mxpi, to install addons in mx19?
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 12:27 am
by Eadwine Rose
I have no idea if it will work, will have to test still and haven't gotten that far, but I always just copy over the existing .kodi folder from install to install.
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 12:52 am
by blindside
I fell like a frickin complete newbie. I have never had issues installing, but maybe if the partition schemes in gparted were broken down to me, I might be successful. Can anyone tell me, in gparted, how they set up this beta and were successful.
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 12:57 am
by Eadwine Rose
Well.. images and thousand words and such.
I do have more than one hard drive, AND a UEFI system, but here are the two hard drives that hold the important info.
18.3 install
sda.jpg
19 beta install
sdc.jpg
That's how I got it all set up.
I don't know who swap on the beta got to be sdc1, I definitely didn't set it up like that, 1 is root, 2 is home and 3 is swap. Maybe I goofed up, or maybe the installer thought it knew better lol. Keeping a close eye when I install the next beta, but this works.
Re: Stuck on formatting swap on the new beta
Posted: Sat Sep 07, 2019 1:10 am
by ChrisUK
Buck Fankers wrote: Fri Sep 06, 2019 4:40 pm
blindside wrote: Fri Sep 06, 2019 4:50 am
I tried to install the new beta that just came out and everything was going great until the install stalled at 2% formatting swap.
As a work around, if you don't plan to use hibernate, but only suspend, then swap file is better solution than swap partition.
You could try to install without swap partition then after installation is completed, run these 4 commands:
Code: Select all
sudo fallocate -l 2G /swapfile <- set the size (4G for 4GB, 8G for 8GB...)
sudo chmod 600 /swapfile <- set correct permission
sudo mkswap /swapfile <- format the swap file
sudo swapon /swapfile <- activate swap file
Unless I've misunderstood - also add
to /etc/fstab
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 1:13 am
by blindside
JayM wrote: Fri Sep 06, 2019 6:33 am
I thought the latest version of the installer which should be part of the beta did a swapoff already.
@blindside: It would be nice if you could open a terminal and run
then copy everything in the terminal and paste it here
inside of code tags.
Code: Select all
$ sudo minstall -E
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Installer version: 19.8.06
+++ void MInstall::startup() +++
Exec #1: "uname -m | grep -q i686"
Exit #1: 1 QProcess::ExitStatus(NormalExit)
Exec #2: "test -d /sys/firmware/efi"
Exit #2: 0 QProcess::ExitStatus(NormalExit)
uefi = true
Exec #3: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled'"
Exit #3: 0 QProcess::ExitStatus(NormalExit)
Exec #4: "command -v xfconf-query >/dev/null && su $(logname) -c 'xfconf-query --channel thunar-volman --property /automount-drives/enabled --set false'"
Exit #4: 0 QProcess::ExitStatus(NormalExit)
Exec #5: "ps -aux |grep -v grep | grep devmon"
Exit #5: 1 QProcess::ExitStatus(NormalExit)
Exec #6: "grep space /home/$(logname)/.desktop-session/desktop-code.*"
SErr #6: "grep: /home/demo/.desktop-session/desktop-code.*: No such file or directory\n"
Exit #6: 2 QProcess::ExitStatus(NormalExit)
+++ void MInstall::setupkeyboardbutton() +++
Exec #7: "locale -a | grep -Ev '^(C|POSIX)\\.?' | grep -E 'utf8|UTF-8'"
Exit #7: 0 QProcess::ExitStatus(NormalExit)
Exec #8: "grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus"
Exit #8: 1 QProcess::ExitStatus(NormalExit)
Exec #9: "/bin/ls -1 /home | grep -Ev '(lost\\+found|demo|snapshot)' | grep -q [a-zA-Z0-9]"
Exit #9: 1 QProcess::ExitStatus(NormalExit)
Exec #10: "test -d /live/linux/home/demo"
Exit #10: 1 QProcess::ExitStatus(NormalExit)
Exec #11: "dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'"
Exit #11: 0 QProcess::ExitStatus(NormalExit)
+++ void MInstall::buildServiceList() +++
+++ void MInstall::updatePartitionWidgets() +++
Exec #12: "/sbin/partprobe"
SErr #12: "Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.\n"
Exit #12: 1 QProcess::ExitStatus(NormalExit)
Exec #13: "blkid -c /dev/null"
SOut #13: "/dev/nvme0n1: PTUUID=\"327faf03-b588-452e-a9d0-835a95aef2d7\" PTTYPE=\"gpt\"\n/dev/sda1: UUID=\"2019-08-25-19-38-05-00\" LABEL=\"MX-Live\" TYPE=\"iso9660\" PTUUID=\"5d95e9ad\" PTTYPE=\"dos\" PARTUUID=\"5d95e9ad-01\"\n/dev/sda2: SEC_TYPE=\"msdos\" LABEL_FATBOOT=\"EFI-LIVE\" LABEL=\"EFI-LIVE\" UUID=\"6CFD-B910\" TYPE=\"vfat\" PARTUUID=\"5d95e9ad-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
Exit #13: 0 QProcess::ExitStatus(NormalExit)
Exec #14: "fdisk -l -o DEVICE,TYPE |grep 'EFI System' |cut -d\\ -f1 | cut -d/ -f3"
Exit #14: 0 QProcess::ExitStatus(NormalExit)
Exec #15: "lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL |sed 's/├─//' |sed 's/└─//' | grep -E '^(disk|part)'"
Exit #15: 0 QProcess::ExitStatus(NormalExit)
Exec #16: "blkid /dev/sda | grep -q PTTYPE=\\\"gpt\\\""
Exit #16: 1 QProcess::ExitStatus(NormalExit)
Exec #17: "blkid /dev/nvme0n1 | grep -q PTTYPE=\\\"gpt\\\""
Exit #17: 0 QProcess::ExitStatus(NormalExit)
Name Size Model FS | isDisk isGPT isBoot isESP isNative isSwap
"sda" 31010586624 "USB_3.0_FD" "iso9660" | true false false false false false
"sda1" 1441792000 "" "iso9660" | false false false false false false
"sda2" 3284992 "" "vfat" | false false false true false false
"nvme0n1" 500107862016 "Samsung SSD 970 EVO 500GB" "" | true true false false false false
"nvme0n1p1" 268435456 "" "ext4" | false true false false true false
"nvme0n1p2" 497658363904 "" "" | false true false false true false
"nvme0n1p3" 2147483648 "" "ext4" | false true false false true false
Exec #18: "[ -f /usr/sbin/gparted ] && /usr/sbin/gparted || /usr/bin/partitionmanager"
SOut #18: "======================\nlibparted : 3.2\n======================\n"
SErr #18: "System has not been booted with systemd as init system (PID 1). Can't operate.\nFailed to connect to bus: Host is down\nToo few arguments.\nToo few arguments.\n/bin/bash: /usr/bin/partitionmanager: No such file or directory\n"
Exit #18: 127 QProcess::ExitStatus(NormalExit)
+++ void MInstall::updatePartitionWidgets() +++
Exec #19: "/sbin/partprobe"
SErr #19: "Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.\n"
Exit #19: 1 QProcess::ExitStatus(NormalExit)
Exec #20: "blkid -c /dev/null"
SOut #20: "/dev/nvme0n1: PTUUID=\"60443ed4-f97b-4d6b-85b7-7d4eb15da25b\" PTTYPE=\"gpt\"\n/dev/sda1: UUID=\"2019-08-25-19-38-05-00\" LABEL=\"MX-Live\" TYPE=\"iso9660\" PTUUID=\"5d95e9ad\" PTTYPE=\"dos\" PARTUUID=\"5d95e9ad-01\"\n/dev/sda2: SEC_TYPE=\"msdos\" LABEL_FATBOOT=\"EFI-LIVE\" LABEL=\"EFI-LIVE\" UUID=\"6CFD-B910\" TYPE=\"vfat\" PARTUUID=\"5d95e9ad-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
Exit #20: 0 QProcess::ExitStatus(NormalExit)
Exec #21: "fdisk -l -o DEVICE,TYPE |grep 'EFI System' |cut -d\\ -f1 | cut -d/ -f3"
Exit #21: 0 QProcess::ExitStatus(NormalExit)
Exec #22: "lsblk -brno TYPE,NAME,UUID,SIZE,PARTTYPE,FSTYPE,LABEL,MODEL |sed 's/├─//' |sed 's/└─//' | grep -E '^(disk|part)'"
Exit #22: 0 QProcess::ExitStatus(NormalExit)
Exec #23: "blkid /dev/sda | grep -q PTTYPE=\\\"gpt\\\""
Exit #23: 1 QProcess::ExitStatus(NormalExit)
Exec #24: "blkid /dev/nvme0n1 | grep -q PTTYPE=\\\"gpt\\\""
Exit #24: 0 QProcess::ExitStatus(NormalExit)
Name Size Model FS | isDisk isGPT isBoot isESP isNative isSwap
"sda" 31010586624 "USB_3.0_FD" "iso9660" | true false false false false false
"sda1" 1441792000 "" "iso9660" | false false false false false false
"sda2" 3284992 "" "vfat" | false false false true false false
"nvme0n1" 500107862016 "Samsung SSD 970 EVO 500GB" "" | true true false false false false
"nvme0n1p1" 314572800 "" "vfat" | false true false true false false
"nvme0n1p2" 16106127360 "" "ext4" | false true false false true false
"nvme0n1p3" 8589934592 "" "swap" | false true false false true true
+++ bool MInstall::validateChosenPartitions() +++
+++ bool MInstall::saveHomeBasic() +++
+++ bool MInstall::checkTargetDrivesOK() +++
+++ void MInstall::cleanup(bool) +++
Exec #25: "/bin/umount -l /mnt/antiX/boot/efi"
SErr #25: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
Exit #25: 32 QProcess::ExitStatus(NormalExit)
Exec #26: "/bin/umount -l /mnt/antiX/proc"
SErr #26: "umount: /mnt/antiX/proc: no mount point specified.\n"
Exit #26: 32 QProcess::ExitStatus(NormalExit)
Exec #27: "/bin/umount -l /mnt/antiX/sys"
SErr #27: "umount: /mnt/antiX/sys: no mount point specified.\n"
Exit #27: 32 QProcess::ExitStatus(NormalExit)
Exec #28: "/bin/umount -l /mnt/antiX/dev/shm"
SErr #28: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
Exit #28: 32 QProcess::ExitStatus(NormalExit)
Exec #29: "/bin/umount -l /mnt/antiX/dev"
SErr #29: "umount: /mnt/antiX/dev: no mount point specified.\n"
Exit #29: 32 QProcess::ExitStatus(NormalExit)
Exec #30: "/bin/umount -l /mnt/antiX/home"
SErr #30: "umount: /mnt/antiX/home: no mount point specified.\n"
Exit #30: 32 QProcess::ExitStatus(NormalExit)
Exec #31: "/bin/umount -lR /mnt/antiX"
SErr #31: "umount: /mnt/antiX: not found\n"
Exit #31: 1 QProcess::ExitStatus(NormalExit)
+++ bool MInstall::makePartitions() +++
Exec #32: "swapoff /dev/nvme0n1p2"
SErr #32: "swapoff: /dev/nvme0n1p2: swapoff failed: Invalid argument\n"
Exit #32: 255 QProcess::ExitStatus(NormalExit)
Exec #33: "/bin/umount /dev/nvme0n1p2"
SErr #33: "umount: /dev/nvme0n1p2: not mounted.\n"
Exit #33: 32 QProcess::ExitStatus(NormalExit)
---- PARTITION FORMAT SCHEDULE ----
Root: "/dev/nvme0n1p2" -1
Home: "/dev/nvme0n1p2" 0
Swap: "/dev/nvme0n1p3" 0
Boot: "/dev/nvme0n1p2" 0
ESP: "" 0
BIOS-GRUB: ""
Exec #34: "/sbin/sgdisk /dev/nvme0n1 --typecode=2:8303"
SOut #34: "The operation has completed successfully.\n"
Exit #34: 0 QProcess::ExitStatus(NormalExit)
Exec #35: "partprobe"
SErr #35: "Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.\n"
Exit #35: 1 QProcess::ExitStatus(NormalExit)
+++ bool MInstall::formatPartitions() +++
+++ bool MInstall::makeLinuxPartition(const QString&, const QString&, bool, const QString&) +++
Exec #36: "mkfs.ext4 -F /dev/nvme0n1p2 -L \"rootMX19\""
SErr #36: "mke2fs 1.44.5 (15-Dec-2018)\nThe file /dev/nvme0n1p2 does not exist and no size was specified.\n"
Exit #36: 1 QProcess::ExitStatus(NormalExit)
+++ void MInstall::cleanup(bool) +++
Exec #37: "/bin/umount -l /mnt/antiX/boot/efi"
SErr #37: "umount: /mnt/antiX/boot/efi: no mount point specified.\n"
Exit #37: 32 QProcess::ExitStatus(NormalExit)
Exec #38: "/bin/umount -l /mnt/antiX/proc"
SErr #38: "umount: /mnt/antiX/proc: no mount point specified.\n"
Exit #38: 32 QProcess::ExitStatus(NormalExit)
Exec #39: "/bin/umount -l /mnt/antiX/sys"
SErr #39: "umount: /mnt/antiX/sys: no mount point specified.\n"
Exit #39: 32 QProcess::ExitStatus(NormalExit)
Exec #40: "/bin/umount -l /mnt/antiX/dev/shm"
SErr #40: "umount: /mnt/antiX/dev/shm: no mount point specified.\n"
Exit #40: 32 QProcess::ExitStatus(NormalExit)
Exec #41: "/bin/umount -l /mnt/antiX/dev"
SErr #41: "umount: /mnt/antiX/dev: no mount point specified.\n"
Exit #41: 32 QProcess::ExitStatus(NormalExit)
Exec #42: "/bin/umount -l /mnt/antiX/home"
SErr #42: "umount: /mnt/antiX/home: no mount point specified.\n"
Exit #42: 32 QProcess::ExitStatus(NormalExit)
Exec #43: "/bin/umount -lR /mnt/antiX"
SErr #43: "umount: /mnt/antiX: not found\n"
Exit #43: 1 QProcess::ExitStatus(NormalExit)
Re: Stuck on formatting swap on the new beta
Posted: Sat Sep 07, 2019 2:14 am
by Buck Fankers
ChrisUK wrote: Sat Sep 07, 2019 1:10 am
Unless I've misunderstood - also add
to /etc/fstab
Oh, yes, how did I miss this line, it was late, sorry and thanks for correction!
All together:
Code: Select all
sudo fallocate -l 2G /swapfile <- set the size
sudo chmod 600 /swapfile <- set correct permission
sudo mkswap /swapfile <- format the swap file
sudo swapon /swapfile <- activate swap file
/swapfile none swap defaults 0 0 <- add this line to /etc/fstab
To add last line to fstab, you can highlight last line with mouse, copy, run in the terminal:
Move cursor to the bottom of the text in new line and paste it there then save changes with: Ctrl-X
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 3:50 am
by chrispop99
I've just tried the new MX Date and Time application from the latest updates. It's very slick!
Presumably the MX Time Settings application will be removed in the future?
Chris
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 5:15 am
by Jerry3904
That was my first thought too. (I already deleted it from the beta Manual.)
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 5:52 am
by asqwerth
Conky issue:
The conky known as MX-GeekyTowerLogo is supposed to execute a script in $HOME/.conky/MX-Asq/MX-GeekyTowerLogo/conky-harddisks.sh .
However, that conky-harddisks.sh file as found in the Beta1 not been given permission to run as a program, so it does not do its job of displaying all the mounted media in the conky, and the portion of the conky just under "Media" remains empty.
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 6:23 am
by Jerry3904
I didn't change that (maybe copying it from the laptop to the desktop did that?), but will correct it.
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 6:28 am
by asqwerth
Jerry3904 wrote: Sat Sep 07, 2019 6:23 am
I didn't change that (maybe copying it from the laptop to the desktop did that?), but will correct it.
Can't the script file be packaged as executable?
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 6:38 am
by Jerry3904
Out of my league, but others will know. My hatchet idea was just to make it executable in my local GitHub repo and upload it.
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 9:04 am
by AK-47
chrispop99 wrote: Sat Sep 07, 2019 3:50 am
I've just tried the new MX Date and Time application from the latest updates. It's very slick!
Thanks, I'm glad you like it! There are some bug fixes in the pipeline, so check for updates within the next 1-2 days.
chrispop99 wrote: Sat Sep 07, 2019 3:50 amPresumably the MX Time Settings application will be removed in the future?
Chris
That's the intention. MX Date & Time was written as a complete replacement for MX Time Settings that's easy to use.
Re: MX-19 Beta 1 Feedback
Posted: Sat Sep 07, 2019 9:15 am
by Jerry3904
It's gone in b2
Re: MX-19 Beta 1 Feedback
Posted: Sun Sep 08, 2019 8:13 am
by Eadwine Rose
Beta 2.1 is out now, this thread is closed.
Announcement:
viewtopic.php?f=131&p=526126#p526126
Feedback:
viewtopic.php?f=94&t=52591
