MX-17.1-RC1 Release Candidate Feedback
Re: MX-17.1-RC1 Release Candidate Feedback
A bit late in the thread... but Cairo-dock is up and running just fine!
Think software manager hadn't finished inventory before i initially searched for it.
My apologies and congratulations to the MX team on a very decent RC!
Think software manager hadn't finished inventory before i initially searched for it.
My apologies and congratulations to the MX team on a very decent RC!
Re: MX-17.1-RC1 Release Candidate Feedback
legacy bios
posting to report that Rufus (isohybrid mode) is still able to successfully create the LiveUSB
posting to report that Rufus (isohybrid mode) is still able to successfully create the LiveUSB
Re: MX-17.1-RC1 Release Candidate Feedback
menu item: MX Welcome
/usr/share/applications/mx-welcome.desktop
Comment=Display welcome message
^---- It's a fine app & does much more than just display a message. Consider using a more creative comment (yeah, would create a translation chore)
From "MX Welcome" UI, launch "MX Tools".
Note that one of the displayed tools is "MX Welcome". Click "MX Welcome".
From the (unknown to user, but is a new instance of) "MX Welcome" UI, again launch "MX Tools".
{lather, rinse, repeat}
Visit htop and note that NN instances of "MX Welcome" and "MX Tools" are running.
Maybe not harmful, but potentially confusing. Should any of the tools check/enforce a single instance of themselves?
MX Tools ---} Codecs Installer
The app requires authorization.
Click the "About" button. Click the displayed hyperlink. (launches a root-permissioned Firefox instance)
Wheeeee...
Upon closing this web browser, up pops "MX Tools".
Wait, I was using Codecs Installer (yep, it's still running, is hidden behind the other windows).
Ah, apparently some other tool/dialog I'd clicked earlier had -- unknown to me -- launched that browser instance
(and my "About" button click just populated a second browser tab)
MX Tools ---} Codecs Installer ---} Help
confirmed: elevated permissions are dropped when launching mx-viewer
(spot-checked a few of the other MXTools apps which requires authorization & noted results identical
to those reported, above, for Codecs Installer)
/usr/share/applications/mx-welcome.desktop
Comment=Display welcome message
^---- It's a fine app & does much more than just display a message. Consider using a more creative comment (yeah, would create a translation chore)
From "MX Welcome" UI, launch "MX Tools".
Note that one of the displayed tools is "MX Welcome". Click "MX Welcome".
From the (unknown to user, but is a new instance of) "MX Welcome" UI, again launch "MX Tools".
{lather, rinse, repeat}
Visit htop and note that NN instances of "MX Welcome" and "MX Tools" are running.
Maybe not harmful, but potentially confusing. Should any of the tools check/enforce a single instance of themselves?
MX Tools ---} Codecs Installer
The app requires authorization.
Click the "About" button. Click the displayed hyperlink. (launches a root-permissioned Firefox instance)
Wheeeee...
Upon closing this web browser, up pops "MX Tools".
Wait, I was using Codecs Installer (yep, it's still running, is hidden behind the other windows).
Ah, apparently some other tool/dialog I'd clicked earlier had -- unknown to me -- launched that browser instance
(and my "About" button click just populated a second browser tab)
MX Tools ---} Codecs Installer ---} Help
confirmed: elevated permissions are dropped when launching mx-viewer
(spot-checked a few of the other MXTools apps which requires authorization & noted results identical
to those reported, above, for Codecs Installer)
Last edited by skidoo on Thu Mar 08, 2018 3:59 am, edited 2 times in total.
Re: MX-17.1-RC1 Release Candidate Feedback
MX tweak ---} click "Window Manager"
following successful use of the theme selector, MX Tweak window reappears... but the "Panel" tab now (unexpectedly) is displayed.
confirmed: after clicking "Appearance" button and applying a theme change, MX tweak "Theme" tab is (as expected) displayed.
(For now, I'll cease "clicking into all the little corners" of the various tools, hunting papercut bugs.
Any newfound hiccups could be pushed via individual package updates anyhow.)
Just noticed, when I went back and appended my prior post:
~~
^----- I'm getting dashes (yep, not minus sign -- characters) when I press the "tilde" key.
FWIW: I've never previously noticed such a thing (and, no, I haven't selected|changed whatever kb/locale settings are provided as default)
following successful use of the theme selector, MX Tweak window reappears... but the "Panel" tab now (unexpectedly) is displayed.
confirmed: after clicking "Appearance" button and applying a theme change, MX tweak "Theme" tab is (as expected) displayed.
(For now, I'll cease "clicking into all the little corners" of the various tools, hunting papercut bugs.
Any newfound hiccups could be pushed via individual package updates anyhow.)
Just noticed, when I went back and appended my prior post:
~~
^----- I'm getting dashes (yep, not minus sign -- characters) when I press the "tilde" key.
FWIW: I've never previously noticed such a thing (and, no, I haven't selected|changed whatever kb/locale settings are provided as default)
Re: MX-17.1-RC1 Release Candidate Feedback
legacy bios
Rufus-created FAT32 boot partition
root_persistence, semi-automatic mode
Persistence is working as expected but, across several reboots, no "Custom blabblah datetime" menu entry is presented on the boot screen.
The F8 Save has preserved the previously-selected options, but manual removal of "quiet" from the boot line options box is required during each boot (because MenuItem 1 is the only suitable choice).
Rufus-created FAT32 boot partition
root_persistence, semi-automatic mode
Persistence is working as expected but, across several reboots, no "Custom blabblah datetime" menu entry is presented on the boot screen.
The F8 Save has preserved the previously-selected options, but manual removal of "quiet" from the boot line options box is required during each boot (because MenuItem 1 is the only suitable choice).
- dolphin_oracle
- Developer
- Posts: 20024
- Joined: Sun Dec 16, 2007 1:17 pm
Re: MX-17.1-RC1 Release Candidate Feedback
Noted for futureskidoo wrote:menu item: MX Welcome
/usr/share/applications/mx-welcome.desktop
Comment=Display welcome message
^---- It's a fine app & does much more than just display a message. Consider using a more creative comment (yeah, would create a translation chore)
I've actually thought about this one in the past. I kinda decided back then it was better to get 2 windows of welcome than nothing happening when you click it. But maybe we could do something fancier.From "MX Welcome" UI, launch "MX Tools".
Note that one of the displayed tools is "MX Welcome". Click "MX Welcome".
From the (unknown to user, but is a new instance of) "MX Welcome" UI, again launch "MX Tools".
{lather, rinse, repeat}
Visit htop and note that NN instances of "MX Welcome" and "MX Tools" are running.
Maybe not harmful, but potentially confusing. Should any of the tools check/enforce a single instance of themselves?
How did you spot check? Remove mx-viewer and launch from the menu as a regular user or from the cli as a root user?MX Tools ---} Codecs Installer
The app requires authorization.
Click the "About" button. Click the displayed hyperlink. (launches a root-permissioned Firefox instance)
Wheeeee...
Upon closing this web browser, up pops "MX Tools".
Wait, I was using Codecs Installer (yep, it's still running, is hidden behind the other windows).
Ah, apparently some other tool/dialog I'd clicked earlier had -- unknown to me -- launched that browser instance
(and my "About" button click just populated a second browser tab)
MX Tools ---} Codecs Installer ---} Help
confirmed: elevated permissions are dropped when launching mx-viewer
(spot-checked a few of the other MXTools apps which requires authorization & noted results identical
to those reported, above, for Codecs Installer)
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: MX-17.1-RC1 Release Candidate Feedback
Tried to install kmahjongg ( I just like it better than the mahjongg that is installed ). Works fine in MX17, but won't install on RC1.
Get:
Depends: libkf5kdegames7
tried install libkf5kdegames7
Get: Depends: libkf5declarative5
Tried down about 5 levels of DEPENDS - something missing?
Earl
Get:
Depends: libkf5kdegames7
tried install libkf5kdegames7
Get: Depends: libkf5declarative5
Tried down about 5 levels of DEPENDS - something missing?
Earl
Re: MX-17.1-RC1 Release Candidate Feedback
Firefox is not syncing properly for me.
Passwords seem to have made it, but no extensions syncing since yesterday.
A Mozilla issue maybe.
Passwords seem to have made it, but no extensions syncing since yesterday.
A Mozilla issue maybe.
Re: MX-17.1-RC1 Release Candidate Feedback
How did you migrate FF from 17?
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-17.1-RC1 Release Candidate Feedback
Have to update my profile!Jerry3904 wrote:How did you migrate FF from 17?
Did a fresh install with latest RC.
Have disconnected/reconnected user account a couple of times already.
Still no go.
Update: have been trying to sync on LinuxMint Cinnamon as well and it's a no go there too!
So, it is evidently not an MX issue for sure.
Last edited by danielson on Thu Mar 08, 2018 4:51 pm, edited 1 time in total.