MX Linux Forum

Posted: **Mon Dec 17, 2018 6:47 am**

Place your feedback here:

Known issue: conky display may be corrupted on live media boots, especially in Virtual Box or slower hardware. use the conky-toggle in the favorites menu to stop and restart the conky.

If posting hardware issues, please post the output of the terminal command "inxi -Fxrz" or use our "Quick-system-info" from the menu, 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 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).

Posted: **Mon Dec 17, 2018 8:07 am**

I detected this problem in the Conky

Posted: **Mon Dec 17, 2018 8:09 am**

Gerson wrote: Mon Dec 17, 2018 8:07 am I detected this problem in the Conky

Look at the first known issue in the announcement.

Posted: **Mon Dec 17, 2018 8:12 am**

dolphin_oracle wrote: Mon Dec 17, 2018 6:47 am Place your feedback here:

Known issue: conky display may be corrupted on live media boots, especially in Virtual Box or slower hardware. use the conky-toggle in the favorites menu to stop and restart the conky.

Posted: **Mon Dec 17, 2018 9:15 am**

Does someone know how to use the sourceforge delta ?

Posted: **Mon Dec 17, 2018 9:18 am**

Wiki>xdelta:

https://mxlinux.org/search/node/xdelta

If not a regular terminal user, remember that you can use the Tab key to complete long file names.

Chris

Posted: **Mon Dec 17, 2018 9:18 am**

Patch an iso with a delta file

Code: Select all

xdelta3 -d -s fromfile patchname.delta tofile

Oh haha Chrispop beat me to it :)

Posted: **Mon Dec 17, 2018 9:19 am**

what is the upgrade path from MX-18b1 - if any ?
ie: to avoid having to download, again .. ..

Posted: **Mon Dec 17, 2018 9:25 am**

@pierre just the normal upgrade path install. Install and save /home. Be a bit cautious or things could go 'south' on you. I managed without problem.... nothing much destroyed besides having to reinstall my software changes. Now I'm testing to see how Timeshift might work on the transition from RC1 to whatever is next.

Posted: **Mon Dec 17, 2018 9:26 am**

Stupendous!
New graphic images, conky, etc. just beautiful!!!
And it took less than 5 minutes to install! Wow!
Boot up time (haven't timed yet) seems to be less than a minute too.

Wonderful Christmas present guys (and gals)! :)

Thanks!

Posted: **Mon Dec 17, 2018 9:30 am**

manyroads wrote: Mon Dec 17, 2018 9:25 am @pierre just the normal upgrade path install. Install and save /home. Be a bit cautious or things could go 'south' on you. I managed without problem.... nothing much destroyed besides having to reinstall my software changes. Now I'm testing to see how Timeshift might work on the transition from RC1 to whatever is next.

Pierre is asking for an upgrade path without a download. There is no official upgrade path from beta to RC. Best to download. And a smaller download is to use the delta and generate the new full iso.

Code: Select all

xdelta3 -d -s fromfile patchname.delta tofile

Posted: **Mon Dec 17, 2018 9:31 am**

Tx, Chris & Rose, that worked.

I installed MX-18RC1_386.iso to the same rather low-end HP110/AMD6-5200 system I used to test MX18b1.
Went even smoother, the generated grub.cfg has a windows entry this time. Nothing odd noticed so far.
Looks like a nice refresh, before next year's edition hopefully based on buster.
But thanks to the mx test repo and its updated packages, i am not that impatient to get there.

Posted: **Mon Dec 17, 2018 9:56 am**

Thanks Danielson. Remember this is a release candidate, so it is not the final release yet :)

Posted: **Mon Dec 17, 2018 11:26 am**

Very trivial - README file in .conky mentions MX-17. Suggest change to MX-Linux to cover all bases.

Chris

Posted: **Mon Dec 17, 2018 12:40 pm**

@richb
But this situation of the Conky never happened to me neither live nor when installing MX 17; 17.1 and beta MX 18. only with MX 17 beta.
The installation is very fast, faster than MX 17.1 and all the programs I use are installed without problems from the test repo and Debian. It may be my impression but it seems to me that this RC flows much better.

Posted: **Mon Dec 17, 2018 12:45 pm**

Gerson wrote: Mon Dec 17, 2018 12:40 pm @richb
But this situation of the Conky never happened to me neither live nor when installing MX 17; 17.1 and beta MX 18. only with MX 17 beta.
<snip>

Different conky, different systems. We are aware of the situation and looking for a solution.

Posted: **Mon Dec 17, 2018 2:07 pm**

When was RC released please ? Getting a string of 404's on the NZ repeater.

Posted: **Mon Dec 17, 2018 2:17 pm**

This morning. You might want to change mirrors, however--have looked at the 70 mirrors listed in Repo Manager? Or, have you used the button to find the fastest repo?

Posted: **Mon Dec 17, 2018 2:21 pm**

NZ is often half a day behind, will try later in day. NZ should be fastest fo me it's only about 6 kilometres away and all this area has had copper replaced by glass fibre.

Posted: **Mon Dec 17, 2018 2:24 pm**

The distance between "should be" and "is" could be pretty great--what would it hurt to run that button?

Posted: **Mon Dec 17, 2018 2:26 pm**

Jerry3904 wrote: Mon Dec 17, 2018 2:17 pm This morning. You might want to change mirrors, however--have looked at the 70 mirrors listed in Repo Manager? Or, have you used the button to find the fastest repo?

How do you use the Repo Manager to choose a different download mirror for an RC iso found on sourceforge Test folder?

Posted: **Mon Dec 17, 2018 2:36 pm**

Ha! Was led astray by Gordon's talking about the NZ mirror.

Posted: **Mon Dec 17, 2018 3:02 pm**

Sorry for the confusion. I did think that notification of the RC1 release would come via the forum. I have just checked mirror speeds and find that Freemont CA is fastest. Strange.

Posted: **Mon Dec 17, 2018 3:17 pm**

https://forum.mxlinux.org/viewtopic.php?f=131&t=47408

It did.

Posted: **Mon Dec 17, 2018 3:30 pm**

I'll try and get them up to archive.org soon, too.

Did anyone manage to get the zsync working from sourceforge? I tried the old syntax command, but it didn't seem to work..."no control file" or something.

Code: Select all

zsync -i <input_file> $(wget -nv --spider <URL_of_zsync_file>/download 2>&1 | grep -Eo https.*iso.zsync | sed 's/https/http/')

Posted: **Mon Dec 17, 2018 3:31 pm**

richb wrote: Mon Dec 17, 2018 9:30 am Pierre is asking for an upgrade path without a download. There is no official upgrade path from beta to RC. Best to download.

I'm not quite understanding. Sorry if the answer's obvious or already stated somewhere.
I upgraded from 17.1 to 18 beta.
If I just continue with normal upgrades, will I have the complete MX18?
If not, what will be missing?
Thanks.

Posted: **Mon Dec 17, 2018 3:39 pm**

Redacted wrote: Mon Dec 17, 2018 3:31 pm
richb wrote: Mon Dec 17, 2018 9:30 am Pierre is asking for an upgrade path without a download. There is no official upgrade path from beta to RC. Best to download.
I'm not quite understanding. Sorry if the answer's obvious or already stated somewhere.
I upgraded from 17.1 to 18 beta.
If I just continue with normal upgrades, will I have the complete MX18?
If not, what will be missing?
Thanks.

Probably differences with some of the graphic elements, grub screen, and splash. They are still being discussed. Also I am not sure what kernel is in beta 1, that may be different. Also some internal coding details. There will be a migration policy stated on the community web site blog when final is released. It has always been that with previous versions of MX there is no migration from a beta to final while there is from an RC to final. I expect that still to be the case.

Posted: **Mon Dec 17, 2018 3:56 pm**

OK. Thank you.

Posted: **Mon Dec 17, 2018 4:01 pm**

If you did have the first 4.19 kernel, the current version would be seen as a normal upgrade.

Posted: **Mon Dec 17, 2018 4:04 pm**

Yes, I do have the 4.19.0-1 kernel on the 18 beta.

Posted: **Mon Dec 17, 2018 4:09 pm**

asqwerth wrote: Mon Dec 17, 2018 3:17 pm https://forum.mxlinux.org/viewtopic.php?f=131&t=47408

It did.

Thanks. I have it now but was not on the NZ mirror earlier at 2000GMT.

Posted: **Mon Dec 17, 2018 5:58 pm**

I have the 64-bit files up at archive.org now, including the automatic torrent: https://archive.org/details/MX18RC1X64

32-bit are uploading now--I just found a switch for this upload that I flipped so they are a "test", and will be removed automatically after 30 days.

Update: 32-bit uploaded: https://archive.org/details/MX-18RC1386

Posted: **Mon Dec 17, 2018 6:07 pm**

Thank you Stevo... an excellent move, using archive.org!

Posted: **Mon Dec 17, 2018 6:50 pm**

Since we are shipping tlp by default, any thoughts about adding tlpui (thanks for the package suggestion, manyroads) to the ISO to make it easy to configure? It's quite a tiny package. I tested it, and it worked fine for a few changes I made. That would also be one more bullet point we could add to the final release announcement.

Posted: **Mon Dec 17, 2018 6:55 pm**

I like the idea. But it's not in the repos so there would be no automatic update. And the website says: "TLPUI is considered to be beta software."

Posted: **Mon Dec 17, 2018 7:14 pm**

I have to say the TLPUI is very useful. It really makes tuning your PC heat burn (energy burn) quite easy. But on the otherhand, it is not very hard to install manually for those of us with excess geek genes....

Posted: **Mon Dec 17, 2018 7:15 pm**

Thinkpad 600x (2000)

Same issues as MX18b1: Color Inversion and Sound Card not found. Same manual fixes required.

Posted: **Mon Dec 17, 2018 7:17 pm**

palemoon-nonsse2 (in MXPI Stable repo) gets error for dependency fonts-symbola but works after it is installed (from MXPI MX Test repo) before trying to install palemoon .

Posted: **Mon Dec 17, 2018 8:12 pm**

"Suspend" mode isn't doing it for me.
Default screen image shows up when trying to wake, but that's as far as it goes.
No response to keyboard.
Must manually shut-down.

- - - - -
Btw, does anyone know how to change xflock4 lockscreen command?
Would like to set it to same as Windows (super key + L).

Posted: **Mon Dec 17, 2018 8:19 pm**

In testing we have found that success in using suspend depends on a weird interaction between GPU and other factors. Can you post the output of this command as regular user:

Code: Select all

inxi -G

Posted: **Mon Dec 17, 2018 8:23 pm**

Jerry3904 wrote: Mon Dec 17, 2018 6:55 pm I like the idea. But it's not in the repos so there would be no automatic update. And the website says: "TLPUI is considered to be beta software."

It's in our test repo for now...https://repology.org/metapackage/tlpui/versions

Posted: **Mon Dec 17, 2018 8:29 pm**

MX Package Installer > Popular Applications > Kernel > antiX 4.19 lists 4.19.7 but 4.19.8-antix.1 (2018-12-09) ... is in stable repo and seems to be working just fine.

Posted: **Mon Dec 17, 2018 8:34 pm**

Hierax_ca wrote: Mon Dec 17, 2018 8:29 pm MX Package Installer > Popular Applications > Kernel > antiX 4.19 lists 4.19.7 but 4.19.8-antix.1 (2018-12-09) ... is in stable repo and seems to be working just fine.

thanks for pointing that out.

Posted: **Mon Dec 17, 2018 8:42 pm**

I have actually had issues with 4.19.7-antix locking on trying to come back from suspend. No error message but a small annoyance.

Posted: **Mon Dec 17, 2018 9:02 pm**

Installed dolphin from the test repo. When starting dolphin this error:

could not start process Cannot talk to klauncher: The name org.kde.klauncher5 was not provided by any .service files. this message:

Probably the same in MX 17

Posted: **Mon Dec 17, 2018 9:18 pm**

Thank you Jerry.
Appreciate it!

Graphics: Device-1: AMD Seymour [Radeon HD 6400M/7400M Series] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1600x900~60Hz, 1680x1050~60Hz
OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.19.0-1-amd64 LLVM 7.0.0)
v: 3.3 Mesa 18.2.6

Posted: **Mon Dec 17, 2018 10:24 pm**

I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.

Posted: **Mon Dec 17, 2018 10:45 pm**

j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.

it should be just your user password.

Posted: **Mon Dec 17, 2018 11:13 pm**

j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.

This is odd. I'm using MX 16, and I've got Opera, Slimjet & Vivaldi browsers installed. When they were initially installed they opened without fuss. I'm now getting "Choose password for new keyring" when I open any of them for no particular reason.

Has something happened to Chromium based browsers?

Posted: **Mon Dec 17, 2018 11:16 pm**

If you save stuff in browsers (like passwords) it needs to be encrypted that's why they ask for the keyring...

Posted: **Mon Dec 17, 2018 11:24 pm**

dolphin_oracle wrote:

it should be just your user password.

It wouldn't accept it. In any event, I reinstalled RC1 and chose Chromium instead of Chrome and declined Google's offer to sync all my devices. I want to see if the problem recurs.

Posted: **Mon Dec 17, 2018 11:36 pm**

So far looking very good. I will keep using this as a daily driver, so far no obstacles to that. If I have time, I can try installing on an older amd system.

I downloaded from sourceforge, md5 was good, and burned to USB from the beta using the MX live USB creator.
Booted quickly, and I at once installed to the 4th partition on the nvme drive, as with the beta.

This time no problems finding the root, grub installed and the install went fine. Rebooted, installed nvidia with the MX nvidia installer, rebooted again, no problems.

Did a bunch of desk-top and firefox tweaks, enabled sda1, the data drive, used synaptic after a reload to take all 6 updates, then installed 108 new packages. Suspend works.

Reboot to check stability, from grub to log-in is about 14 seconds.

Code: Select all

:    Host: Ryzen Kernel: 4.19.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-18RC1_x64 Continuum December 17  2018 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: <root required> 
           UEFI [Legacy]: American Megatrends v: 4024 date: 09/07/2018 
CPU:       Topology: 6-Core model: AMD Ryzen 5 1600X bits: 64 type: MT MCP L2 cache: 3072 KiB 
           Speed: 2130 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 1898 2: 2069 3: 1843 
           4: 1846 5: 1881 6: 1879 7: 1879 8: 1881 9: 2963 10: 2972 11: 1827 12: 1837 
Graphics:  Device-1: NVIDIA GK208 [GeForce GT 710B] driver: nvidia v: 390.87 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87 
Audio:     Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel 
           Device-2: AMD driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           IF: eth0 state: up speed: 100 Mbps duplex: 
Drives:    Local Storage: total: 1.14 TiB used: 471.04 GiB (40.5%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB 
           ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB 
Partition: ID-1: / size: 100.88 GiB used: 6.14 GiB (6.1%) fs: ext4 dev: /dev/nvme0n1p4 
           ID-2: swap-1 size: 16.60 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 34.0 C mobo: N/A gpu: nvidia temp: 40 C 
           Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 50% 
Info:      Processes: 255 Uptime: 32m Memory: 15.66 GiB used: 2.37 GiB (15.2%) Shell: bash 
           inxi: 3.0.25

Posted: **Tue Dec 18, 2018 3:06 am**

mentioned for the benefit of Windows emigrants:
The rufus utility (https://rufus.ie) at default settings (mbr)(isohybrid mode) can successfully create an MX18 LiveUSB

Posted: **Tue Dec 18, 2018 3:08 am**

noticed in ~/.xsession-errors
. . .
xfce4-session-Message: 20:37:58.155: SSH authentication agent is already running
gpg-agent[7436]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent[7437]: gpg-agent (GnuPG) 2.1.18 started
. . .
conky: Syntax error (/home/demo/.conky/MX-Elementary/MX-Elementary_sys:1: '=' expected near 'yes') while reading config file.
conky: Assuming it's in old syntax and attempting conversion.
. . .
(xfce4-session:7429): xfce4-session-WARNING **: 01:52:00.355: ICE connection 0x5615be156770 rejected
Failed to connect to session manager: Failed to connect to the session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

/var/log/syslog :
avahi-daemon[6947]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
. . .
usb_common: module verification failed: signature and/or required key missing - tainting kernel
. . .
[pulseaudio[7507]: [pulseaudio] authkey.c: Failed to open cookie file '/home/demo/.config/pulse/cookie': No such file or directory
[pulseaudio] authkey.c: Failed to load authentication key '/home/demo/.config/pulse/cookie': No such file or directory

/var/log/lightdm/lightdm.log :
WARNING: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file or directory

^----- the directory does exist. Permissions of its parent ( /var/lib/lightdm/ ) drwxr-x---

Posted: **Tue Dec 18, 2018 3:35 am**

synaptic :
toward aiding discoverability, recommend "Show package properties in main window" enabled per the default preferences

Posted: **Tue Dec 18, 2018 3:44 am**

Regarding the installer's new interface for the root/home/swap/boot partition settings, I suggest that the "none" option in the swap dropdown menu be changed to "none or use existing".

As I recall, this was the original description in the previous interface, so that users understood that they could choose this "none" option if they already had a swap partition created and formatted on the system, perhaps by another distro.

Otherwise, a user who is not so familiar might either backtrack to Gparted to create a completely new swap partition or they might click on an existing swap partition thinking to reuse it.

But doing the latter step will reformat the swap partition, changing its UUID. If the other distro is a systemd distro, this will cause that distro to go into a 90 sec check mode because it can't find the swap partition under the old UUID.

Posted: **Tue Dec 18, 2018 4:03 am**

Tonight I cannot remember howto view/edit the Xfce global keybinds.
No luck from searching whiskerMenu: "keyb", "shortc", "hotk"... and didn't find it in "MX Tools" nor "Xfce Settings"
-=-
During the process of hunting, I noticed a usability issue with the default whiskerMenu theme:
insufficient contrast between its scrollbar and the scrollbar background color

Not as the default wallpaper, and not necessarily bearing phrases in 30 languages, one of the preinstalled wallpapers (exploring novice will discover) might mention howto access/change global hotkeys. Another probably welcome notation on such wallpaper would be
"tip: You can Alt+rightMouseButton and drag to resize an application window"

Posted: **Tue Dec 18, 2018 4:45 am**

When a "save persistence" operation is launched, the initial dialog looks like this:

The intent of of this "opening screen" hasn't been fully realized ~~ to provide a place to remind/recommend
"close any running applications, especially web browser, before proceeding".

ANY running applications?
Well... in addition to risking loss of unsaved changes to WIP documents currently opened in text/graphics editors, it might not be widely understood that many applications rely on @exit clean shutdown to perform housekeeping (e.g. save changed preferences, save RecentlyUsed documents list).

If firefox is (still) running when an on-demand persist save operation is performed, this scenario invites loss of state (open tabs, history) for the current browsing session as well as potential loss of recent bookmark entries. At next launch it will recognize that its @exit SessionManager files are missing and prompt "your last session crashed. Restore the previous (next-to-last) session?"

Posted: **Tue Dec 18, 2018 4:53 am**

skidoo wrote: Tue Dec 18, 2018 4:03 am Tonight I cannot remember howto view/edit the Xfce global keybinds.
No luck from searching whiskerMenu: "keyb", "shortc", "hotk"... and didn't find it in "MX Tools" nor "Xfce Settings"

Do you mean.. open the menu, in the search field on top enter keyboard, click that, then go to the tab application shortcuts?

Posted: **Tue Dec 18, 2018 6:30 am**

colin_b wrote: Mon Dec 17, 2018 11:13 pm
j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.
This is odd. I'm using MX 16, and I've got Opera, Slimjet & Vivaldi browsers installed. When they were initially installed they opened without fuss. I'm now getting "Choose password for new keyring" when I open any of them for no particular reason.

Has something happened to Chromium based browsers?

Yes. On linux the chrome based browsers if you use encrypted password storage (the default). I think the chrome based stuff stores other stuff in encrypted storage too

Posted: **Tue Dec 18, 2018 8:55 am**

I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)

Posted: **Tue Dec 18, 2018 9:05 am**

Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)

On first opening with Google Chrome, I am always asked for the keyring password.

Posted: **Tue Dec 18, 2018 9:09 am**

j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.

When you log-in the first time with your normal username and password, during the log-in process a new login-keyring is (shall be) generated automatically by "libpam-gnomekeyring", if not already existing. As protecting password used for this keyring the user's password is used. After login this keyring is automatically unlocked. You can check this by doing the following:
- close all programs like Chrome etc
- clear/remove all existing keyrings

Code: Select all

rm ~/.local/share/keyrings/*

- logout and login
- dont' start Chrome
- open Password and Keys from the Menu
and you'll find a unlocked login-keyring as indicated by the unlocked symbol:

Password-and-keys-login-keyring.png

When you now open Chromium or any other app requiring access to use the keyring,
you will/shall not see any prompt.

If this showing of a password-prompt for unlocking thy keyring happens again, we might have a timing issues during the log-in process.
In that case please do this:
First clear again as described above the keyring.
Next do open Settings -> Application Autostart and click to enable on "Secret Storage Service "GNOME-keyring"
This might fix the timing related issue, if not please report back here.

Posted: **Tue Dec 18, 2018 9:09 am**

richb wrote: Tue Dec 18, 2018 9:05 am
Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)
On first opening with Google Chrome, I am always asked for the keyring password.

Not here.. *shrug*

Posted: **Tue Dec 18, 2018 9:11 am**

I like the extra security.

Posted: **Tue Dec 18, 2018 9:12 am**

Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)

B/c you used an empty password for the keyring, I assume. (Which we shall not advocate to the user, but instead use (and fix if not working) a more secure solution)

Posted: **Tue Dec 18, 2018 9:16 am**

I cannot even remember EVER getting a keyring question for Chrome. I have gotten the question for skype IIRC, but Chrome? Never.

Posted: **Tue Dec 18, 2018 10:16 am**

j2mcgreg wrote: Mon Dec 17, 2018 11:24 pm dolphin_oracle wrote:

it should be just your user password.
It wouldn't accept it. In any event, I reinstalled RC1 and chose Chromium instead of Chrome and declined Google's offer to sync all my devices. I want to see if the problem recurs.

Immediately after the reinstall, chromium worked fine with no appearance of the key ring prompt. However, it did reappear after these two packages:

Code: Select all

ecryptfs-utils (111-4), and, libecryptfs1 (111-4)

were installed after an update. So far, the prompt is accepting my normal password.

Posted: **Tue Dec 18, 2018 10:24 am**

j2mcgreg wrote: Tue Dec 18, 2018 10:16 am
j2mcgreg wrote: Mon Dec 17, 2018 11:24 pm dolphin_oracle wrote:

it should be just your user password.
It wouldn't accept it. In any event, I reinstalled RC1 and chose Chromium instead of Chrome and declined Google's offer to sync all my devices. I want to see if the problem recurs.
Immediately after the reinstall, chromium worked fine with no appearance of the key ring prompt. However, it did reappear after these two packages:
Code: Select all
ecryptfs-utils (111-4), and, libecryptfs1 (111-4)
were installed after an update. So far, the prompt is accepting my normal password.

Would enabling "Secret Storage Service GNOME-keyring" in autostart, as mentioned in the prvious post solve password prompt issue.

Posted: **Tue Dec 18, 2018 10:53 am**

Not sure what this means so do not blindly change. In Google Chrome, "chrome://flags/", invoked by typing in address bar, There is this entry:

Migrate passwords to "Login Data"
Performs a one-off irreversible migration of passwords from the gnome-keyring or kwallet into the profile directory. – Linux

The options are default, enable, disable with default as installed choice.

Posted: **Tue Dec 18, 2018 11:11 am**

richb wrote: Tue Dec 18, 2018 10:53 am Not sure what this means so do not blindly change. In Google Chrome, "chrome://flags/", invoked by typing in address bar, There is this entry:

Migrate passwords to "Login Data"
Performs a one-off irreversible migration of passwords from the gnome-keyring or kwallet into the profile directory. – Linux
The options are default, enable, disable with default as installed choice.

good found.
It means for any saved password within Chrome to transfer those credentials into the "old" "plaintext-alike" password-store format within the profile folder of chrome/ium. Highly not recommended as plaintext-alike insecure migration.

Posted: **Tue Dec 18, 2018 11:18 am**

In the next iteration of MX 18, could ecryptfs-utils be linked to the initial log on? That way the password(s) would still be encrypted be default but the users would not be hassled by a secondary prompt.

Posted: **Tue Dec 18, 2018 11:20 am**

Haven't seen it yet. In MX 17 I've missed thunar-media-tags-plugin. Is this included in MX 18?

Posted: **Tue Dec 18, 2018 11:41 am**

fehlix wrote: Tue Dec 18, 2018 11:11 am
richb wrote: Tue Dec 18, 2018 10:53 am Not sure what this means so do not blindly change. In Google Chrome, "chrome://flags/", invoked by typing in address bar, There is this entry:

Migrate passwords to "Login Data"
Performs a one-off irreversible migration of passwords from the gnome-keyring or kwallet into the profile directory. – Linux
The options are default, enable, disable with default as installed choice.
good found.
It means for any saved password within Chrome to transfer those credentials into the "old" "plaintext-alike" password-store format within the profile folder of chrome/ium. Highly not recommended as plaintext-alike insecure migration.

Thanks for the explanation. Upon reading it again with your clarification, it made perfect sense to me. And I agree, I would not recommend it as it would forego the extra security.
By the way, there are many tweaks in about:config. For example I used one to increase the size of the extension icon display. But use with caution as they could really muck up the browser.

Posted: **Tue Dec 18, 2018 12:26 pm**

asqwerth wrote: Tue Dec 18, 2018 3:44 am Regarding the installer's new interface for the root/home/swap/boot partition settings, I suggest that the "none" option in the swap dropdown menu be changed to "none or use existing".

As I recall, this was the original description in the previous interface, so that users understood that they could choose this "none" option if they already had a swap partition created and formatted on the system, perhaps by another distro.

Otherwise, a user who is not so familiar might either backtrack to Gparted to create a completely new swap partition or they might click on an existing swap partition thinking to reuse it.

But doing the latter step will reformat the swap partition, changing its UUID. If the other distro is a systemd distro, this will cause that distro to go into a 90 sec check mode because it can't find the swap partition under the old UUID.

Since I always select an existing swap partition when installing an OS, I guess I've just been lucky that I don't use systemd. Is it necessary to format it?

Posted: **Tue Dec 18, 2018 12:39 pm**

asqwerth wrote: Tue Dec 18, 2018 3:44 am Regarding the installer's new interface for the root/home/swap/boot partition settings, I suggest that the "none" option in the swap dropdown menu be changed to "none or use existing".

As I recall, this was the original description in the previous interface, so that users understood that they could choose this "none" option if they already had a swap partition created and formatted on the system, perhaps by another distro.

Otherwise, a user who is not so familiar might either backtrack to Gparted to create a completely new swap partition or they might click on an existing swap partition thinking to reuse it.

But doing the latter step will reformat the swap partition, changing its UUID. If the other distro is a systemd distro, this will cause that distro to go into a 90 sec check mode because it can't find the swap partition under the old UUID.

actually, this is a delibrate change. "none" means none.

if you choose a partition that is already formatted swap, it will not be reformated unless you are also using encryption.

Posted: **Tue Dec 18, 2018 1:12 pm**

Eadwine Rose wrote: Tue Dec 18, 2018 4:53 am
skidoo wrote: Tue Dec 18, 2018 4:03 am Tonight I cannot remember howto view/edit the Xfce global keybinds.
No luck from searching whiskerMenu: "keyb", "shortc", "hotk"... and didn't find it in "MX Tools" nor "Xfce Settings"
Do you mean.. open the menu, in the search field on top enter keyboard, click that, then go to the tab application shortcuts?

global, as in, Alt+F1 launches MX User Manual viewer, Alt+F4 kills the application in the currently focused window (?), Alt+F6 does "something" (i don't know what -- accessibility related? Causes cursor to change to a "hand")...

I jogged my memory by performing a websearch, but the stumble led me to mention it as a usability issue.
A novice may not not easily find -----v

Posted: **Tue Dec 18, 2018 1:28 pm**

No fair using websearches!

;-)

Posted: **Tue Dec 18, 2018 1:39 pm**

skidoo wrote: Tue Dec 18, 2018 4:03 am Tonight I cannot remember howto view/edit the Xfce global keybinds.

What? You can't remember this?

Code: Select all

 xfconf-query -c xfce4-keyboard-shortcuts -l -v

Code: Select all

xfconf-query -c xfce4-keyboard-shortcuts -l -v
/commands/custom/<Alt>F1                   mx-manual
/commands/custom/<Alt>F2                   xfce4-appfinder --collapsed
/commands/custom/<Alt>F3                   xfce4-appfinder
/commands/custom/Menu                      xfce4-popup-whiskermenu
/commands/custom/override                  true
/commands/custom/<Primary><Alt>Delete      xflock4
/commands/custom/<Primary><Alt>Escape      xkill
/commands/custom/<Primary>Escape           xfdesktop --menu
/commands/custom/Print                     xfce4-screenshooter
/commands/custom/<Shift>F4                 xfce4-terminal --hide-menubar --hide-borders --drop-down
/commands/custom/<Shift>Scroll_Lock        sh -c 'xfdesktop --reload; xfce4-panel --restart'
/commands/custom/<Super>p                  xfce4-display-settings --minimal
/commands/custom/XF86Display               xfce4-display-settings --minimal
/commands/custom/XF86Mail                  exo-open --launch MailReader
/commands/custom/XF86WWW                   exo-open --launch WebBrowser
/commands/default/<Alt>F1                  xfce4-popup-applicationsmenu
/commands/default/<Alt>F2                  xfce4-appfinder --collapsed
/commands/default/<Alt>F2/startup-notify   true
/commands/default/<Alt>F3                  xfce4-appfinder
/commands/default/<Alt>F3/startup-notify   true
/commands/default/<Primary><Alt>Delete     xflock4
/commands/default/<Primary><Alt>l          xflock4
/commands/default/<Primary>Escape          xfdesktop --menu
/commands/default/<Super>p                 xfce4-display-settings --minimal
/commands/default/XF86Display              xfce4-display-settings --minimal
/commands/default/XF86Mail                 exo-open --launch MailReader
/commands/default/XF86WWW                  exo-open --launch WebBrowser
/providers                                 <<UNSUPPORTED>>
/xfwm4/custom/<Alt><Control>End            move_window_next_workspace_key
/xfwm4/custom/<Alt><Control>Home           move_window_prev_workspace_key
/xfwm4/custom/<Alt><Control>KP_1           move_window_workspace_1_key
/xfwm4/custom/<Alt><Control>KP_2           move_window_workspace_2_key
/xfwm4/custom/<Alt><Control>KP_3           move_window_workspace_3_key
/xfwm4/custom/<Alt><Control>KP_4           move_window_workspace_4_key
/xfwm4/custom/<Alt><Control>KP_5           move_window_workspace_5_key
/xfwm4/custom/<Alt><Control>KP_6           move_window_workspace_6_key
/xfwm4/custom/<Alt><Control>KP_7           move_window_workspace_7_key
/xfwm4/custom/<Alt><Control>KP_8           move_window_workspace_8_key
/xfwm4/custom/<Alt><Control>KP_9           move_window_workspace_9_key
/xfwm4/custom/<Alt>Delete                  del_workspace_key
/xfwm4/custom/<Alt>F10                     maximize_window_key
/xfwm4/custom/<Alt>F11                     fullscreen_key
/xfwm4/custom/<Alt>F12                     above_key
/xfwm4/custom/<Alt>F4                      close_window_key
/xfwm4/custom/<Alt>F6                      stick_window_key
/xfwm4/custom/<Alt>F7                      move_window_key
/xfwm4/custom/<Alt>F8                      resize_window_key
/xfwm4/custom/<Alt>F9                      hide_window_key
/xfwm4/custom/<Alt>Insert                  add_workspace_key
/xfwm4/custom/<Alt><Shift>Tab              cycle_reverse_windows_key
/xfwm4/custom/<Alt>space                   popup_menu_key
/xfwm4/custom/<Alt>Tab                     cycle_windows_key
/xfwm4/custom/<Control><Alt>d              show_desktop_key
/xfwm4/custom/<Control><Alt>Down           down_workspace_key
/xfwm4/custom/<Control><Alt>Left           left_workspace_key
/xfwm4/custom/<Control><Alt>Right          right_workspace_key
/xfwm4/custom/<Control><Alt>Up             up_workspace_key
/xfwm4/custom/<Control>F1                  workspace_1_key
/xfwm4/custom/<Control>F10                 workspace_10_key
/xfwm4/custom/<Control>F11                 workspace_11_key
/xfwm4/custom/<Control>F12                 workspace_12_key
/xfwm4/custom/<Control>F2                  workspace_2_key
/xfwm4/custom/<Control>F3                  workspace_3_key
/xfwm4/custom/<Control>F4                  workspace_4_key
/xfwm4/custom/<Control>F5                  workspace_5_key
/xfwm4/custom/<Control>F6                  workspace_6_key
/xfwm4/custom/<Control>F7                  workspace_7_key
/xfwm4/custom/<Control>F8                  workspace_8_key
/xfwm4/custom/<Control>F9                  workspace_9_key
/xfwm4/custom/<Control><Shift><Alt>Left    move_window_left_key
/xfwm4/custom/<Control><Shift><Alt>Right   move_window_right_key
/xfwm4/custom/<Control><Shift><Alt>Up      move_window_up_key
/xfwm4/custom/Down                         down_key
/xfwm4/custom/Escape                       cancel_key
/xfwm4/custom/Left                         left_key
/xfwm4/custom/override                     true
/xfwm4/custom/Right                        right_key
/xfwm4/custom/<Shift><Alt>Page_Down        lower_window_key
/xfwm4/custom/<Shift><Alt>Page_Up          raise_window_key
/xfwm4/custom/<Super>Tab                   switch_window_key
/xfwm4/custom/Up                           up_key
/xfwm4/default/<Alt>Delete                 del_workspace_key
/xfwm4/default/<Alt>F10                    maximize_window_key
/xfwm4/default/<Alt>F11                    fullscreen_key
/xfwm4/default/<Alt>F12                    above_key
/xfwm4/default/<Alt>F4                     close_window_key
/xfwm4/default/<Alt>F6                     stick_window_key
/xfwm4/default/<Alt>F7                     move_window_key
/xfwm4/default/<Alt>F8                     resize_window_key
/xfwm4/default/<Alt>F9                     hide_window_key
/xfwm4/default/<Alt>Insert                 add_workspace_key
/xfwm4/default/<Alt><Shift>Tab             cycle_reverse_windows_key
/xfwm4/default/<Alt>space                  popup_menu_key
/xfwm4/default/<Alt>Tab                    cycle_windows_key
/xfwm4/default/Down                        down_key
/xfwm4/default/Escape                      cancel_key
/xfwm4/default/Left                        left_key
/xfwm4/default/<Primary><Alt>d             show_desktop_key
/xfwm4/default/<Primary><Alt>Down          down_workspace_key
/xfwm4/default/<Primary><Alt>End           move_window_next_workspace_key
/xfwm4/default/<Primary><Alt>Home          move_window_prev_workspace_key
/xfwm4/default/<Primary><Alt>KP_1          move_window_workspace_1_key
/xfwm4/default/<Primary><Alt>KP_2          move_window_workspace_2_key
/xfwm4/default/<Primary><Alt>KP_3          move_window_workspace_3_key
/xfwm4/default/<Primary><Alt>KP_4          move_window_workspace_4_key
/xfwm4/default/<Primary><Alt>KP_5          move_window_workspace_5_key
/xfwm4/default/<Primary><Alt>KP_6          move_window_workspace_6_key
/xfwm4/default/<Primary><Alt>KP_7          move_window_workspace_7_key
/xfwm4/default/<Primary><Alt>KP_8          move_window_workspace_8_key
/xfwm4/default/<Primary><Alt>KP_9          move_window_workspace_9_key
/xfwm4/default/<Primary><Alt>Left          left_workspace_key
/xfwm4/default/<Primary><Alt>Right         right_workspace_key
/xfwm4/default/<Primary><Alt>Up            up_workspace_key
/xfwm4/default/<Primary>F1                 workspace_1_key
/xfwm4/default/<Primary>F10                workspace_10_key
/xfwm4/default/<Primary>F11                workspace_11_key
/xfwm4/default/<Primary>F12                workspace_12_key
/xfwm4/default/<Primary>F2                 workspace_2_key
/xfwm4/default/<Primary>F3                 workspace_3_key
/xfwm4/default/<Primary>F4                 workspace_4_key
/xfwm4/default/<Primary>F5                 workspace_5_key
/xfwm4/default/<Primary>F6                 workspace_6_key
/xfwm4/default/<Primary>F7                 workspace_7_key
/xfwm4/default/<Primary>F8                 workspace_8_key
/xfwm4/default/<Primary>F9                 workspace_9_key
/xfwm4/default/<Primary><Shift><Alt>Left   move_window_left_key
/xfwm4/default/<Primary><Shift><Alt>Right  move_window_right_key
/xfwm4/default/<Primary><Shift><Alt>Up     move_window_up_key
/xfwm4/default/Right                       right_key
/xfwm4/default/<Shift><Alt>Page_Down       lower_window_key
/xfwm4/default/<Shift><Alt>Page_Up         raise_window_key
/xfwm4/default/<Super>Tab                  switch_window_key
/xfwm4/default/Up                          up_key

Posted: **Tue Dec 18, 2018 1:55 pm**

That is why we have an Xfce section in the Wiki, where the xfconf-query commands are listed:

https://mxlinux.org/wiki/xfce/xfce-comm ... 20settings

Posted: **Tue Dec 18, 2018 2:01 pm**

Testing methodology:
1) no coffee past 8pm. Stay awake past midnight, test during zeepy wee hours
2) alter the usual lighting (desklamp dimmed, or angled to shine glare into muh face).
4) set Miley Cyrus - We Can't Stop or Hannah Montana - Who Said or The Hamster Dance to looping autoplay at 70%+ volume...

Posted: **Tue Dec 18, 2018 2:06 pm**

That is why we have an Xfce section in the Wiki, where the xfconf-query commands are listed

So, inclusion of an additional wallpaper displaying "tips" would be moot, because "we already got a wiki page for that"?
Okay, got it.
Not really, but... whatever.

Posted: **Tue Dec 18, 2018 2:13 pm**

Nope, just thought it be useful in the future for everybody to know that we have that info.

Posted: **Tue Dec 18, 2018 2:20 pm**

Thank you for changing out the locales screens! I had to cursor down and hit the spacebar every time I wanted something removed. This nice GUI way of clicking with the mouse works SO much better!

Posted: **Tue Dec 18, 2018 2:56 pm**

I know I am deaf, might have gone blind as well.. where has the screensaver gone and all the options to set it up with it?

Posted: **Tue Dec 18, 2018 2:58 pm**

Eadwine Rose wrote: Tue Dec 18, 2018 2:56 pm I know I am deaf, might have gone blind as well.. where has the screensaver gone and all the options to set it up with it?

its gone. we replaced with light-locker.

if you want it, install from mx-packagesinstaller -> popular apps- screensavers

Posted: **Tue Dec 18, 2018 2:59 pm**

Eadwine Rose wrote: Tue Dec 18, 2018 2:56 pm I know I am deaf, might have gone blind as well ..

MXPI

Posted: **Tue Dec 18, 2018 3:02 pm**

richb wrote: Mon Dec 17, 2018 9:02 pm Installed dolphin from the test repo. When starting dolphin this error:
could not start process Cannot talk to klauncher: The name org.kde.klauncher5 was not provided by any .service files. this message:
Probably the same in MX 17

Got that too, but brute-forced-fixed that by installing kde-standard in MXPI.

Posted: **Tue Dec 18, 2018 3:08 pm**

dphn wrote: Tue Dec 18, 2018 11:20 am Haven't seen it yet. In MX 17 I've missed thunar-media-tags-plugin. Is this included in MX 18?

Not if nobody's asked for it. I see it in the repo, does it work when installed?

I'm having some thoughts about tlpui, too. We have to check on its localization--if it's only in English, that's not good for everyone.

Posted: **Tue Dec 18, 2018 3:17 pm**

fehlix wrote: Tue Dec 18, 2018 2:59 pm
Eadwine Rose wrote: Tue Dec 18, 2018 2:56 pm I know I am deaf, might have gone blind as well ..
MXPI

Was in there.. didn't think to look for screensavers

Sorted.

Posted: **Tue Dec 18, 2018 3:23 pm**

Stevo wrote: Tue Dec 18, 2018 3:02 pm
richb wrote: Mon Dec 17, 2018 9:02 pm Installed dolphin from the test repo. When starting dolphin this error:
could not start process Cannot talk to klauncher: The name org.kde.klauncher5 was not provided by any .service files. this message:
Probably the same in MX 17
Got that too, but brute-forced-fixed that by installing kde-standard in MXPI.

LOL. I did the same 5 minutes after I got the error. Easier than trying to figure out what is missing.

Posted: **Tue Dec 18, 2018 3:26 pm**

its kinit

Posted: **Tue Dec 18, 2018 6:39 pm**

Hopefully not too late to be just in time before Final, could the freshly released antiX LTS Kernels 4.9.146 and 4.19.10 ( https://www.antixforum.com/forums/topic ... available/ ) be included in the MXPI Popular Applications?

Posted: **Tue Dec 18, 2018 6:43 pm**

Eadwine Rose wrote: Tue Dec 18, 2018 3:17 pm
fehlix wrote: Tue Dec 18, 2018 2:59 pm
Eadwine Rose wrote: Tue Dec 18, 2018 2:56 pm I know I am deaf, might have gone blind as well ..
MXPI
Was in there.. didn't think to look for screensavers

Sorted.

We just added that section when we moved them from MX 18, so no shame about that!

Posted: **Tue Dec 18, 2018 6:47 pm**

Hierax_ca wrote: Tue Dec 18, 2018 6:39 pm Hopefully not too late to be just in time before Final, could the freshly released antiX LTS Kernels 4.9.146 and 4.19.10 ( https://www.antixforum.com/forums/topic ... available/ ) be included in the MXPI Popular Applications?

It's on the list.

Posted: **Wed Dec 19, 2018 1:24 am**

Stevo wrote: Tue Dec 18, 2018 3:08 pm
dphn wrote: Tue Dec 18, 2018 11:20 am Haven't seen it yet. In MX 17 I've missed thunar-media-tags-plugin. Is this included in MX 18?
Not if nobody's asked for it. I see it in the repo, does it work when installed?

I'm having some thoughts about tlpui, too. We have to check on its localization--if it's only in English, that's not good for everyone.

Have installed this. It's multilingual I think. I'm from Germany and I've got an additional tab in thunar for editing meta-tags of audio-files (id3, id3v2). It's also in my prefered language. (German)

Posted: **Wed Dec 19, 2018 4:58 am**

I'm the only user. Now in the "Login" screen ask for username and password, MX 17 beta up to MX18b1 only asked for password to be the only user.

Posted: **Wed Dec 19, 2018 5:18 am**

Weird. Not here--works normally for me.

Posted: **Wed Dec 19, 2018 9:00 am**

fehlix wrote: Tue Dec 18, 2018 9:09 am
j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.
When you log-in the first time with your normal username and password, during the log-in process a new login-keyring is (shall be) generated automatically by "libpam-gnomekeyring", if not already existing. As protecting password used for this keyring the user's password is used. After login this keyring is automatically unlocked. You can check this by doing the following:
- close all programs like Chrome etc
- clear/remove all existing keyrings
Code: Select all
rm ~/.local/share/keyrings/*
- logout and login
- dont' start Chrome
- open Password and Keys from the Menu
and you'll find a unlocked login-keyring as indicated by the unlocked symbol:
Password-and-keys-login-keyring.png

When you now open Chromium or any other app requiring access to use the keyring,
you will/shall not see any prompt.

If this showing of a password-prompt for unlocking thy keyring happens again, we might have a timing issues during the log-in process.
In that case please do this:
First clear again as described above the keyring.
Next do open Settings -> Application Autostart and click to enable on "Secret Storage Service "GNOME-keyring"
This might fix the timing related issue, if not please report back here.

Thanks!
This has solved the issue with Slimjet here.

Posted: **Wed Dec 19, 2018 9:04 am**

The computer is a Lenovo YOGA 730-15ikb. Intel Core i7-8550U, both Intel and nVidia graphics, 16 GB ram, 4K display.

No flavor of MX-17 will run correctly on it. None of the monthlys. The wireless (rtl8822be) simply does not work.

So, I downloaded the MX-18 beta 1 to make a live USB (UEFI) with persistence Wireless would sometime work but as I booted more often it began to not work. It sees networks but won't connect. Also with the beta the touchpad (synaptic) would freeze and I would have to use my bluetooth mouse just to operate. Bluetooth worked when it felt like it. Changing screen resolution sometimes results in black screen.

On to MX-18 RC1 with anticipation. Virtually the same result except the touchpad seems more reliable. Everything else the same.

Now I travel a lot and generally have no access to an ethernet connection - I have to do wireless always. With older computers MX-17 was flawless in that regard. The wireless always worked right out of the bag. Was one of the main reasons I switched from Ubuntu to MX. And I generally love MX. But this new computer is testing my patience.

Windows 10 works absolutely fine on it with nary a hiccup.

And I have discovered a significant clue about the wireless. If you are connecting to a public network like the wireless in a hotel or at a business, you generally get a login screen, i.e. the wireless code makes a call to the default browser and presents a login screen.

This does not happen with MX-18. And that is a problem. Opening Firefox at that point generally results no visible browser with the message that Firefox is already running when you try again. Once this happens, you can never connect to that network again even though it shows up on the list. The connection attempt at that point will not even show the revolving circle indicating you are connecting. Then it is reboot time. With the same result.

Developers please review this post and work on this. I love MX and want to use the new one on this laptop. But at this time I can't. But you are in good company - Ubuntu doesn't work either and actually locks up the computer.

Be the first in the Linux community to get to the bottom of this.

Thank you.

Posted: **Wed Dec 19, 2018 9:10 am**

Kindly pointing you to this as we cannot guess:

If posting hardware issues, please post the output of the terminal command "inxi -Fxrz" or use our "Quick-system-info" from the menu, 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 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).

Posted: **Wed Dec 19, 2018 9:15 am**

I see a recent Torvalds item in GitHub:

https://github.com/torvalds/linux/tree/ ... /rtl8822be

Looks like it was merged into the kernel 4.18. Have you tried to modprobe it on MX-18rc1?

Posted: **Wed Dec 19, 2018 9:19 am**

Just checked, it's not there.

Posted: **Wed Dec 19, 2018 9:21 am**

It's in "staging" I don't think those are enabled by default, it might require a kernel recompile

Posted: **Wed Dec 19, 2018 9:23 am**

Just checked, it's not there.

Just saw Adrian's post, so there's some hope perhaps.

Posted: **Wed Dec 19, 2018 9:36 am**

fehlix wrote: Tue Dec 18, 2018 9:09 am
j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.
When you log-in the first time with your normal username and password, during the log-in process a new login-keyring is (shall be) generated automatically by "libpam-gnomekeyring", if not already existing. As protecting password used for this keyring the user's password is used. After login this keyring is automatically unlocked. You can check this by doing the following:
- close all programs like Chrome etc
- clear/remove all existing keyrings
Code: Select all
rm ~/.local/share/keyrings/*
- logout and login
- dont' start Chrome
- open Password and Keys from the Menu
and you'll find a unlocked login-keyring as indicated by the unlocked symbol:
Password-and-keys-login-keyring.png

When you now open Chromium or any other app requiring access to use the keyring,
you will/shall not see any prompt.

If this showing of a password-prompt for unlocking thy keyring happens again, we might have a timing issues during the log-in process.
In that case please do this:
First clear again as described above the keyring.
Next do open Settings -> Application Autostart and click to enable on "Secret Storage Service "GNOME-keyring"
This might fix the timing related issue, if not please report back here.

Thanks for this fehlix. Unfortunately life intervened and I had to put some things on hold. I'll try to get to it tonight and report back.

Posted: **Wed Dec 19, 2018 9:49 am**

MX Linux is a very nice distribution. I use MX17 32-bit on a HP Mini netbook.
All other distributions, i tried are slower than MX Linux and some have windows that are to big for a 1024x600 display.

I have installed the latest MX Linux beta 64-bit on a HP m8000 (m8189.nl-a).
Everything running fine.

I have however two remarks:

1) In the Netherlands the Dutch keyboard is hardly used. Almost everybody has a United States Intl 105 key board, often with the Euro sign at key 5.
Under Windows one can type the Euro sign by pressing Ctrl + Alt + 5.
So during installation it would be better, when Dutch language is choosen, to default to a US keyboard, instead of a NL keyboard.
This is also the case with Ubuntu and Mint, i believe.

2) It would be fine if it were possible to install Grub MBR at a disk where the /boot partition is.
I have /root on a SSD drive and would like to have /boot and /Home at another drive, booting from the MBR on this other drive.
With Ubuntu, Mint, Manjaro, Deepin etc this is possible
MX Linux can only install Grub at the disk, where the /root partition is.
In my case this is the SSD, where the Windows boot loader is on. So i cannot install Grub to MBR, without overwriting the Windows 10 boot loader.
The only bypass i have is to install grub at /root, instead of MBR.
I can than use Manjaro Grub to find and run MX Linux.

Posted: **Wed Dec 19, 2018 9:59 am**

1. Do other Dutch users agree? If so, easy to change
2. You also have the option to not install grub at all.

Posted: **Wed Dec 19, 2018 10:11 am**

Jerry3904 wrote: Wed Dec 19, 2018 9:23 am Just checked, it's not there.

Just saw Adrian's post, so there's some hope perhaps.

Even on a 4.20 kernel (where it's still in staging) I'm unable to modinfo or modprobe a rt8822be or rtl8822be module, r8822be does work though

Code: Select all

kent@mx1:~
$ modinfo rt882be
modinfo: ERROR: Module rt882be not found.
kent@mx1:~
$ modinfo rtl882be
modinfo: ERROR: Module rtl882be not found.
kent@mx1:~
$ modinfo r8822be 
filename:       /lib/modules/4.20.0-042000rc6-lowlatency/kernel/drivers/staging/rtlwifi/r8822be.ko
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
author:         lizhaoming	<chaoming_li@realsil.com.cn>
description:    PCI basic driver for rtlwifi
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
author:         lizhaoming	<chaoming_li@realsil.com.cn>
firmware:       rtlwifi/rtl8822befw.bin
description:    Realtek 8822BE 802.11n PCI wireless
license:        GPL
author:         Larry Finger	<Larry.Finger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
srcversion:     75FBE534E42ABFB3D9F1570
alias:          pci:v000010ECd0000B822sv*sd*bc*sc*i*
depends:        mac80211,cfg80211
staging:        Y
intree:         Y
name:           r8822be
vermagic:       4.20.0-042000rc6-lowlatency SMP preempt mod_unload 
parm:           debug_level:int
parm:           swenc:Set to 1 for software crypto (default 0)
 (bool)
parm:           ips:Set to 0 to not use link power save (default 1)
 (bool)
parm:           swlps:Set to 1 to use SW control power save (default 0)
 (bool)
parm:           fwlps:Set to 1 to use FW control power save (default 1)
 (bool)
parm:           msi:Set to 1 to use MSI interrupts mode (default 1)
 (bool)
parm:           dma64:Set to 1 to use DMA 64 (default 0)
 (bool)
parm:           aspm:Set to 1 to enable ASPM (default 1)
 (int)
parm:           debug:Set debug level (0-5) (default 0)
parm:           debug_mask:Set debug mask (default 0) (ullong)
parm:           disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)
kent@mx1:~
$ sudo modprobe r8822be 
[sudo] password for kent: 
kent@mx1:~

Posted: **Wed Dec 19, 2018 10:20 am**

MX Linux can only install Grub at the disk, where the /root partition is.

I don't think there's true, you can select the drive from "System boot disk" dropdown menu. I just tried and was able to install on a sdb disk with I used for /boot while / was on sda.

Actually the opposite was true I was not able to install on sda MBR but maybe it was because I use GPT

Code: Select all

"grub-install --target=i386-pc --recheck --no-floppy --force --boot-directory=/mnt/antiX/boot /dev/sda"
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for cross-disk install.

Posted: **Wed Dec 19, 2018 10:44 am**

Adrian wrote: Wed Dec 19, 2018 10:20 am
MX Linux can only install Grub at the disk, where the /root partition is.
I don't think there's true, you can select the drive from "System boot disk" dropdown menu. I just tried and was able to install on a sdb disk with I used for /boot while / was on sda.

Actually the opposite was true I was not able to install on sda MBR but maybe it was because I use GPT
Code: Select all
"grub-install --target=i386-pc --recheck --no-floppy --force --boot-directory=/mnt/antiX/boot /dev/sda"
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for cross-disk install. 

@Adrin, you can install BIOS/i386-pc Grub onto GPT disk. I usually install both UEFI and BIOS Grub's,
so I can boot in either mode using the identical grub.cfg.
To enable a GPT partition to accept MBR-grub-installs, I do this:
- shrink existing ESP/EFI-partition by about 5MB
- create a new "unformated" partition within that 5MB empty space
- mark the unformated partition as "bios-grub" (or "grub-bios" ?)
And now you can install with the above commmand grub-i386 onto this GPT partition.
And next time you boot in BIOS/MBR bios will boot into grub-i386, using the same grub.cfg as in UEFI-mode.

Posted: **Wed Dec 19, 2018 11:40 am**

Eadwine Rose wrote: Wed Dec 19, 2018 9:10 am Kindly pointing you to this as we cannot guess:

If posting hardware issues, please post the output of the terminal command "inxi -Fxrz" or use our "Quick-system-info" from the menu, 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 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).

I will post the results of terminal command "inxi -Fxrz" later. At work right now and booted up in Windows...

Posted: **Wed Dec 19, 2018 11:47 am**

kmathern wrote: Wed Dec 19, 2018 10:11 am

Jerry3904 wrote: Wed Dec 19, 2018 9:23 am Just checked, it's not there.

Just saw Adrian's post, so there's some hope perhaps.

Even on a 4.20 kernel (where it's still in staging) I'm unable to modinfo or modprobe a rt8822be or rtl8822be module, r8822be does work though

Code: Select all

kent@mx1:~
$ modinfo rt882be
modinfo: ERROR: Module rt882be not found.
kent@mx1:~
$ modinfo rtl882be
modinfo: ERROR: Module rtl882be not found.
kent@mx1:~
$ modinfo r8822be 
filename:       /lib/modules/4.20.0-042000rc6-lowlatency/kernel/drivers/staging/rtlwifi/r8822be.ko
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
author:         lizhaoming	<chaoming_li@realsil.com.cn>
description:    PCI basic driver for rtlwifi
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
author:         lizhaoming	<chaoming_li@realsil.com.cn>
firmware:       rtlwifi/rtl8822befw.bin
description:    Realtek 8822BE 802.11n PCI wireless
license:        GPL
author:         Larry Finger	<Larry.Finger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
srcversion:     75FBE534E42ABFB3D9F1570
alias:          pci:v000010ECd0000B822sv*sd*bc*sc*i*
depends:        mac80211,cfg80211
staging:        Y
intree:         Y
name:           r8822be
vermagic:       4.20.0-042000rc6-lowlatency SMP preempt mod_unload 
parm:           debug_level:int
parm:           swenc:Set to 1 for software crypto (default 0)
 (bool)
parm:           ips:Set to 0 to not use link power save (default 1)
 (bool)
parm:           swlps:Set to 1 to use SW control power save (default 0)
 (bool)
parm:           fwlps:Set to 1 to use FW control power save (default 1)
 (bool)
parm:           msi:Set to 1 to use MSI interrupts mode (default 1)
 (bool)
parm:           dma64:Set to 1 to use DMA 64 (default 0)
 (bool)
parm:           aspm:Set to 1 to enable ASPM (default 1)
 (int)
parm:           debug:Set debug level (0-5) (default 0)
parm:           debug_mask:Set debug mask (default 0) (ullong)
parm:           disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)
kent@mx1:~
$ sudo modprobe r8822be 
[sudo] password for kent: 
kent@mx1:~

Yes it works. Just not on public networks needing a login. I will also check it when I return to my home this weekend. Should work just fine there unless it doesn't give me the login screen...

Posted: **Wed Dec 19, 2018 11:51 am**

fehlix wrote: Wed Dec 19, 2018 10:44 am @Adrin, you can install BIOS/i386-pc Grub onto GPT disk. I usually install both UEFI and BIOS Grub's,

Are you sure it works on 2 disks, see the "is required for cross-disk install" message

Code: Select all

grub-install: error: embedding is not possible, but this is required for cross-disk install.

Posted: **Wed Dec 19, 2018 12:13 pm**

Adrian wrote: Wed Dec 19, 2018 11:51 am
fehlix wrote: Wed Dec 19, 2018 10:44 am @Adrin, you can install BIOS/i386-pc Grub onto GPT disk. I usually install both UEFI and BIOS Grub's,
Are you sure it works on 2 disks, see the "is required for cross-disk install" message
Code: Select all
grub-install: error: embedding is not possible, but this is required for cross-disk install.

My note, was only a comment about installing BIOS-grub onto GPT disk - nothing more ...

Posted: **Wed Dec 19, 2018 12:15 pm**

I don't have a problem installing BIOS GRUB on GPT disk in general the problem is when installing on two disks with separate /boot.

Posted: **Wed Dec 19, 2018 12:43 pm**

Adrian wrote: Wed Dec 19, 2018 12:15 pm I don't have a problem installing BIOS GRUB on GPT disk in general the problem is when installing on two disks with separate /boot.

Ah, ok I see.
There are two: ways of having Grub-installed into the MBR: embedded or not-embedded.
In the embedded case: The full grub core.img is placed into the post-MBR gab before partition-table-fs block.
in this case grub is fine with finding the grub.cfg and related modules from another disk by using it's filesystem modules.
In the non-embedded case where embedding into MBR-gap is not possible, grub cannot yet see the filesystem, but requires
BIOS-alike block-jumps to the core.img saved into a fixed block of the disk. Those jumps
are made with help of BIOS-function calls and are only possible within the same disk.
HTH

Posted: **Wed Dec 19, 2018 12:50 pm**

Not sure if anyone has reported this but on new install I moved the deskbar to the bottom of the screen and then configured another panel to be vertical and never hide but it still hides.

Posted: **Wed Dec 19, 2018 1:17 pm**

RichardTS wrote: Wed Dec 19, 2018 11:47 am Yes it works. Just not on public networks needing a login. I will also check it when I return to my home this weekend. Should work just fine there unless it doesn't give me the login screen...

I can load (modprobe) the r8822be module but I don't have the hardware so don't know if it actually works or not.

Have you seen or tried this: https://ubuntuforums.org/showthread.php ... st13748726 ?

Posted: **Wed Dec 19, 2018 8:25 pm**

kmathern wrote: Wed Dec 19, 2018 1:17 pm
RichardTS wrote: Wed Dec 19, 2018 11:47 am Yes it works. Just not on public networks needing a login. I will also check it when I return to my home this weekend. Should work just fine there unless it doesn't give me the login screen...

I can load (modprobe) the r8822be module but I don't have the hardware so don't know if it actually works or not.

Have you seen or tried this: https://ubuntuforums.org/showthread.php ... st13748726 ?

I followed the Ubuntu link. r8822be.conf created with the option inserted. Then the conf file generates a parse error when I modprobe r8822be. Deleting r8822be.conf makes modprobe work.

Then the first time I tried to connect it went round and round and then said “network disconnected” in the upper right corner. Never got a login screen. So I tried again. This time it connected. Still never gave me the hotel login page.

Posted: **Wed Dec 19, 2018 8:29 pm**

I usually only get the hotel login page when I click on a browser page. Note that once connected you can right-click the NM icon in the Notification Area > Edit Connections.... There you can highlight the AP you are connected to, click the Edit button > Proxy tab.

Posted: **Wed Dec 19, 2018 8:34 pm**

Eadwine Rose wrote: Wed Dec 19, 2018 9:10 am Kindly pointing you to this as we cannot guess:

If posting hardware issues, please post the output of the terminal command "inxi -Fxrz" or use our "Quick-system-info" from the menu, 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 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).

inxi -Fxrz command result:

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18RC1_x64 Continuum December 17  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: N/A System: LENOVO product: 81CU v: Lenovo YOGA 730-15IKB serial: <filter> 
           Mobo: LENOVO model: LNVNB161216 v: SDK0R32862 WIN serial: <filter> UEFI: LENOVO 
           v: 7KCN25WW(V1.06) date: 06/19/2018 
Battery:   ID-1: BAT1 charge: 53.8 Wh condition: 53.8/51.6 Wh (104%) 
           model: 43 65 6C 78 70 65 72 74 00 31 PABAS0241231 status: Full 
CPU:       Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Kaby Lake 
           rev: A L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31872 
           Speed: 800 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 801 2: 800 3: 800 4: 800 
           5: 800 6: 800 7: 802 8: 800 
Graphics:  Device-1: Intel driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: NVIDIA driver: nouveau v: kernel bus ID: 3b:00.0 
           Display: x11 server: X.Org 1.19.2 driver: modesetting,nouveau unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.2.6 
           direct render: Yes 
Audio:     Device-1: Intel driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Realtek driver: r8822be v: kernel port: 4000 bus ID: 3a:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 484.15 GiB used: 74.6 MiB (0.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000L2 size: 476.94 GiB 
           ID-2: /dev/sda type: USB vendor: Patriot model: Memory size: 7.21 GiB 
Partition: ID-1: / size: 12.25 GiB used: 74.6 MiB (0.6%) fs: overlay dev: ERR-102 
Sensors:   System Temperatures: cpu: 45.0 C mobo: N/A gpu: nouveau temp: 511 C 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 221 Uptime: 34m Memory: 15.39 GiB used: 1.07 GiB (7.0%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25

Posted: **Wed Dec 19, 2018 8:37 pm**

Posted: **Wed Dec 19, 2018 8:42 pm**

kmathern wrote: Wed Dec 19, 2018 10:11 am

Jerry3904 wrote: Wed Dec 19, 2018 9:23 am Just checked, it's not there.

Just saw Adrian's post, so there's some hope perhaps.

Even on a 4.20 kernel (where it's still in staging) I'm unable to modinfo or modprobe a rt8822be or rtl8822be module, r8822be does work though

Code: Select all

kent@mx1:~
$ modinfo rt882be
modinfo: ERROR: Module rt882be not found.
kent@mx1:~
$ modinfo rtl882be
modinfo: ERROR: Module rtl882be not found.
kent@mx1:~
$ modinfo r8822be 
filename:       /lib/modules/4.20.0-042000rc6-lowlatency/kernel/drivers/staging/rtlwifi/r8822be.ko
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
author:         lizhaoming	<chaoming_li@realsil.com.cn>
description:    PCI basic driver for rtlwifi
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
author:         lizhaoming	<chaoming_li@realsil.com.cn>
firmware:       rtlwifi/rtl8822befw.bin
description:    Realtek 8822BE 802.11n PCI wireless
license:        GPL
author:         Larry Finger	<Larry.Finger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
srcversion:     75FBE534E42ABFB3D9F1570
alias:          pci:v000010ECd0000B822sv*sd*bc*sc*i*
depends:        mac80211,cfg80211
staging:        Y
intree:         Y
name:           r8822be
vermagic:       4.20.0-042000rc6-lowlatency SMP preempt mod_unload 
parm:           debug_level:int
parm:           swenc:Set to 1 for software crypto (default 0)
 (bool)
parm:           ips:Set to 0 to not use link power save (default 1)
 (bool)
parm:           swlps:Set to 1 to use SW control power save (default 0)
 (bool)
parm:           fwlps:Set to 1 to use FW control power save (default 1)
 (bool)
parm:           msi:Set to 1 to use MSI interrupts mode (default 1)
 (bool)
parm:           dma64:Set to 1 to use DMA 64 (default 0)
 (bool)
parm:           aspm:Set to 1 to enable ASPM (default 1)
 (int)
parm:           debug:Set debug level (0-5) (default 0)
parm:           debug_mask:Set debug mask (default 0) (ullong)
parm:           disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)
kent@mx1:~
$ sudo modprobe r8822be 
[sudo] password for kent: 
kent@mx1:~

When I modinfo r8822be I get the same result

I did also do a modprobe r8822be and it is working for right now.

Thanks guys! I really appreciate the help. I set the live USB up with both root and home persistence. Let's hope it stays. Screen resolution setting does not persist.

Posted: **Wed Dec 19, 2018 8:48 pm**

Jerry3904 wrote: Wed Dec 19, 2018 8:29 pm I usually only get the hotel login page when I click on a browser page. Note that once connected you can right-click the NM icon in the Notification Area > Edit Connections.... There you can highlight the AP you are connected to, click the Edit button > Proxy tab.

Maybe you are correct. I go back and forth from Windows all the time so sometimes I get confused. And I have been trying to make MX work for about 3 weeks so I don't remember what normally happens with an MX machine.

It seems to be working right now. Thanks for all the help!

Posted: **Wed Dec 19, 2018 9:38 pm**

j2mcgreg wrote: Wed Dec 19, 2018 9:36 am
fehlix wrote: Tue Dec 18, 2018 9:09 am
j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.
When you log-in the first time with your normal username and password, during the log-in process a new login-keyring is (shall be) generated automatically by "libpam-gnomekeyring", if not already existing. As protecting password used for this keyring the user's password is used. After login this keyring is automatically unlocked. You can check this by doing the following:
- close all programs like Chrome etc
- clear/remove all existing keyrings
Code: Select all
rm ~/.local/share/keyrings/*
- logout and login
- dont' start Chrome
- open Password and Keys from the Menu
and you'll find a unlocked login-keyring as indicated by the unlocked symbol:
Password-and-keys-login-keyring.png

When you now open Chromium or any other app requiring access to use the keyring,
you will/shall not see any prompt.

If this showing of a password-prompt for unlocking thy keyring happens again, we might have a timing issues during the log-in process.
In that case please do this:
First clear again as described above the keyring.
Next do open Settings -> Application Autostart and click to enable on "Secret Storage Service "GNOME-keyring"
This might fix the timing related issue, if not please report back here.
Thanks for this fehlix. Unfortunately life intervened and I had to put some things on hold. I'll try to get to it tonight and report back.

Unfortunately, it didn't work. I ran your code to remove all existing keyrings, then went to Passwords and Keys and there was no login-keyring visible unlocked or otherwise.

Also, under Settings, there is no entry for Application Autostart, so I couldn't try the second set of instructions.

Edit:

Mark this solved. It bothered me that the "Application Autostart" entry was missing so I reinstalled but this time I used a usb stick rather than a DVD. Since the MD5 sum for the DVD was correct, I wondered if the DVD drive on this old computer was faulty. Also, this time I waited for all the updates to be installed and then I rebooted. Only then did I install Chromium and launch it. No prompts for a password occurred.

Posted: **Wed Dec 19, 2018 11:15 pm**

RichardTS wrote: Wed Dec 19, 2018 9:04 am The computer is a Lenovo YOGA 730-15ikb. Intel Core i7-8550U, both Intel and nVidia graphics, 16 GB ram, 4K display.

No flavor of MX-17 will run correctly on it. None of the monthlys. The wireless (rtl8822be) simply does not work.

Richard, I had the same problem as you with my brand new Lenovo Y7000P-1060 (i7-8750H, Nvidia 1060, and the same wireless card) -- in my case the problem is the ideapad_laptop kernel module -- if it's enabled, the wireless won't be seen at all, even though it works just fine in Windows (which also explains why the same problem is seen in other distros). Running a simple:

Code: Select all

sudo modprobe -r ideapad_laptop

allowed the wireless to show up correctly, so I just added a blacklist to modprobe.d for the ideapad_laptop module and it's been smooth sailing since.

Posted: **Wed Dec 19, 2018 11:46 pm**

derrotmax wrote: Wed Dec 19, 2018 11:15 pm
RichardTS wrote: Wed Dec 19, 2018 9:04 am The computer is a Lenovo YOGA 730-15ikb. Intel Core i7-8550U, both Intel and nVidia graphics, 16 GB ram, 4K display.

No flavor of MX-17 will run correctly on it. None of the monthlys. The wireless (rtl8822be) simply does not work.
Richard, I had the same problem as you with my brand new Lenovo Y7000P-1060 (i7-8750H, Nvidia 1060, and the same wireless card) -- in my case the problem is the ideapad_laptop kernel module -- if it's enabled, the wireless won't be seen at all, even though it works just fine in Windows (which also explains why the same problem is seen in other distros). Running a simple:
Code: Select all
sudo modprobe -r ideapad_laptop
allowed the wireless to show up correctly, so I just added a blacklist to modprobe.d for the ideapad_laptop module and it's been smooth sailing since.

Very interesting! Earlier with MX-17 I was getting things called ideapad_laptop this and ideapad_laptop that. Particularly when running rfkill.

I am going to try your suggestion. Did you stumble on this or was it an educated guess?

Posted: **Thu Dec 20, 2018 3:48 pm**

RichardTS wrote: Wed Dec 19, 2018 11:46 pm
Very interesting! Earlier with MX-17 I was getting things called ideapad_laptop this and ideapad_laptop that. Particularly when running rfkill.

I am going to try your suggestion. Did you stumble on this or was it an educated guess?

An educated guess got me going in the right direction. I looked at the rfkill list too (which is where I initially saw the ideapad_laptop entries), and no matter what, my realtek adapter was hardblocked and would never enter an enabled state, even when running rfkill unblock. I then swapped the Realtek card out for an Intel one that ran fine in another MX laptop, but the behavior was the exact same -- at that point I knew that I should be looking for a kernel-level solution (especially since Windows had no issue) -- adding the "ideapad_laptop" module and "disabled wireless" to that search returned all sorts of people that are seeing the same issue regardless of Linux distro. Disabling the ideapad_laptop module and eventually blacklisting it allows the Realtek adapter to start up properly and work without issue.

Posted: **Thu Dec 20, 2018 4:14 pm**

I am going to lock this thread, since Final is out and these comments need to be seen against a current version.

Thanks to everybody for the input!

MX Linux Forum

MX-18 RC1 Feedback

MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback

Re: MX-18 RC1 Feedback