Page 12 of 44
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 12:09 pm
by dolphin_oracle
Eadwine Rose wrote: Sun Oct 06, 2019 11:15 am
Setting the preferences in root thunar, gives me this in the screen:
Screenshot.png
Clicking on gvfs tells me:
Failed to execute default Web Browser.
input/output error.
doesn't surprise me. a lot of things are locked down these days with the root accounts. for one thing at a minimum firefox *can't* launch as root.
the gvfs dameons also launch as a regular user, so an error in the root account doesn't shock me.
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 12:10 pm
by Buck Fankers
MAYBL8 wrote: Sun Oct 06, 2019 10:47 am
If we already running Beta 2 and doing updates does that mean we are on Beta 3 or do I have to download and install to test Beta3?
As far as I understand you are still on Beta2. Besides, idea of new iso is, that we delete old beta and install new beta. That way, we can test everything, installer included.
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 12:13 pm
by dolphin_oracle
not that anywone reads the entrie release statement but
The beta will receive updates over time through the repositories, but certain items, such as the live system and some user settings defaults, will not be obvious without some user intervention. Beta isos will always report themselves as beta versions in quick-system-info and inxi.
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 12:16 pm
by Buck Fankers
dolphin_oracle wrote: Sun Oct 06, 2019 12:13 pm
not that anywone reads the entrie release statement but
The beta will receive updates over time through the repositories, but certain items, such as the live system and some user settings defaults, will not be obvious without some user intervention. Beta isos will always report themselves as beta versions in quick-system-info and inxi.
Well, I probably didn't express myself correctly, but inxi would still show beta2.
This is what I was getting at with my response. Plus new install is desirable testing anyway
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 12:16 pm
by Eadwine Rose
dolphin_oracle wrote: Sun Oct 06, 2019 12:09 pm
Eadwine Rose wrote: Sun Oct 06, 2019 11:15 am
Setting the preferences in root thunar, gives me this in the screen:
Screenshot.png
Clicking on gvfs tells me:
Failed to execute default Web Browser.
input/output error.
doesn't surprise me. a lot of things are locked down these days with the root accounts. for one thing at a minimum firefox *can't* launch as root.
the gvfs dameons also launch as a regular user, so an error in the root account doesn't shock me.
Ah.. that explains it, thanks.
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 12:18 pm
by dolphin_oracle
Buck Fankers wrote: Sun Oct 06, 2019 12:16 pm
dolphin_oracle wrote: Sun Oct 06, 2019 12:13 pm
not that anywone reads the entrie release statement but
The beta will receive updates over time through the repositories, but certain items, such as the live system and some user settings defaults, will not be obvious without some user intervention. Beta isos will always report themselves as beta versions in quick-system-info and inxi.
Well, I probably didn't express myself correctly, but inxi would still show beta2.
This is what I was getting at with my response. Plus new install is desirable testing anyway
ah, I see what you are saying. Yes you are right, betas will report as whatever iso you start with. That's an important distinction, thank you.
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 12:31 pm
by Eadwine Rose
Got a kernel message in syslog:
Code: Select all
Oct 6 18:20:49 eadwineMX19beta3 ntpd[2890]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
I set up the clock and all on the install, time is showing as correct. Anyway, figured I'd report it.
Then some code I have never seen in mx18.3
Code: Select all
Oct 6 18:25:00 eadwineMX19beta3 kernel: [ 688.288263] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 6 18:25:00 eadwineMX19beta3 wpa_supplicant[3053]: wlan0: Reject scan trigger since one is already pending
Connecting to wireless works just fine, so.. just reporting for "letting you know".
Re: MX-19 Beta 3 Feedback, Dutch keyboard
Posted: Sun Oct 06, 2019 2:24 pm
by gsm
fehlix wrote: Sat Oct 05, 2019 6:40 pm
If that "US international, with € at 5" the proper keyboard which shall be the default for Netherland?.
I think that English (US), English (US, international, with Euro sign at 5) is the best choice as the default keyboard for The Netherlands.
Or else the default US keyboard would in a live system also be acceptable to work with.
With most distributions the Dutch keyboard (or even the Dutch language) is not available for the live system and the default keyboard is US, or US International (without the € sign).
Manjaro lets you choose both the system language and the keyboard language, but they simply don't offer the Dutch keyboard or let you select the correct layout.
I selected Dutch (Nederland) and kept the default keyboard US. The € sign is missing but the layout is correct or at least usable with the Manjaro live system.
Code: Select all
setxkbmap -query
rules: evdev
model: pc105+inet
layout: us
options: terminate:ctrl_alt_bksp
After opening the Control panel, Keyboard and the selection of English (US, international with € sign at 5), i get this on the live Manjaro system:
Code: Select all
setxkbmap -query
rules: evdev
model: pc105+inet
layout: us
variant: euro
options: terminate:ctrl_alt_bksp
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 2:27 pm
by Eadwine Rose
So.. when you press shift F5 you don't get a %?
Re: MX-19 Beta 3 Feedback
Posted: Sun Oct 06, 2019 2:30 pm
by Jerry3904
Found how to move conkies again, though don't know why: open the script and change
to
Can someone write me a (sed?) command to do that to the whole collection? I could probably do it, but it would take me a while and I might screw it up.
EDIT: only thing I can think of is that
no_buffers yes may cancel the line supposed to stop flickering:
double_buffers yes, and somehow also froze the conky.