MX-23 alpha2 feedback thread
- Eadwine Rose
- Administrator
- Posts: 14485
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-23 alpha2 feedback thread
In the alpha one interesting thing happened.
I put the bookworm debian multimedia repo in for dvdstyler. That threw a GPG key on reload. Running Fix GPG fixed it so I could install (even though an error still pops up when you activate the repo, it works).
But yeah.. the interesting thing is, everywhere I have been so far, despite having tried to put the root pass in, it needed the user pass.
EXCEPT for MX Fix GPG! I had to enter the root password for that one to go through. Took me by surprise alright.
I put the bookworm debian multimedia repo in for dvdstyler. That threw a GPG key on reload. Running Fix GPG fixed it so I could install (even though an error still pops up when you activate the repo, it works).
But yeah.. the interesting thing is, everywhere I have been so far, despite having tried to put the root pass in, it needed the user pass.
EXCEPT for MX Fix GPG! I had to enter the root password for that one to go through. Took me by surprise alright.
MX-23.6_x64 July 31 2023 * 6.1.0-35amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-23 alpha2 feedback thread
How nice to see orage come up with a click on the clock. All looks good and seems to work. From the user point of view, I wonder if we might not want to set an innocuous default alarm sound of some sort.
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
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 alpha2 feedback thread
Bash Config: works. The list of default commands won't make sense to many users, and I had to try some to see what they did. Suggestions:
--easy: add some more everyday commands, such as the one I use all the time with the alias "up"
--harder: add a comment column OR a tooltip with a short explanation
--easy: add some more everyday commands, such as the one I use all the time with the alias "up"
Code: Select all
sudo apt update && sudo apt dist-upgrade
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
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
- dolphin_oracle
- Developer
- Posts: 22112
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-23 alpha2 feedback thread
thanks, that one is still using su-to-root as well, so its actually not right.Eadwine Rose wrote: Sat Apr 08, 2023 5:07 pm In the alpha one interesting thing happened.
I put the bookworm debian multimedia repo in for dvdstyler. That threw a GPG key on reload. Running Fix GPG fixed it so I could install (even though an error still pops up when you activate the repo, it works).
But yeah.. the interesting thing is, everywhere I have been so far, despite having tried to put the root pass in, it needed the user pass.
EXCEPT for MX Fix GPG! I had to enter the root password for that one to go through. Took me by surprise alright.
I did fix mx-tweak, although you might have to reset to root again.
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-23 alpha2 feedback thread
For me, the volume, battery, and logout icons are still oversized after latest updates.
After "disabling" these notifications:
$ gsettings list-recursively | grep nm-applet
org.gnome.nm-applet disable-connected-notifications false
org.gnome.nm-applet disable-disconnected-notifications false
org.gnome.nm-applet disable-vpn-notifications false
org.gnome.nm-applet disable-wifi-create false
org.gnome.nm-applet show-applet true
org.gnome.nm-applet stamp 0
org.gnome.nm-applet suppress-wireless-networks-available false
The workaround is to manually set:
gsettings set org.gnome.nm-applet disable-disconnected-notifications true
gsettings set org.gnome.nm-applet disable-connected-notifications true
For Wifi connection and disconnection, the "Don't show this message again" buttons don't do anything. I had the same problem on vanilla Debian 12 alpha 2.After "disabling" these notifications:
$ gsettings list-recursively | grep nm-applet
org.gnome.nm-applet disable-connected-notifications false
org.gnome.nm-applet disable-disconnected-notifications false
org.gnome.nm-applet disable-vpn-notifications false
org.gnome.nm-applet disable-wifi-create false
org.gnome.nm-applet show-applet true
org.gnome.nm-applet stamp 0
org.gnome.nm-applet suppress-wireless-networks-available false
The workaround is to manually set:
gsettings set org.gnome.nm-applet disable-disconnected-notifications true
gsettings set org.gnome.nm-applet disable-connected-notifications true
You do not have the required permissions to view the files attached to this post.
Re: MX-23 alpha2 feedback thread
Just installed the alpha2, on a partition. Installed bootloader in PBR. Works.
3 points for now:
1. very cool plymouth splash from Charles V with the latest Freja MX logo, I can see why @dolphin_oracle likes it.
2. looks like there is no more auto-detect of my Brother network printer in MX23, unlike in MX21
3. when I opened Document scanner (simple-scan), strangely enough an authentication window opened asking for password. Granted, I haven't installed the brother scanner driver yet, but this has never happened before on any previous MX versions, even if the application was opened prior to driver installation. In the past, the application simply indicated that there was no scanner available.
3 points for now:
1. very cool plymouth splash from Charles V with the latest Freja MX logo, I can see why @dolphin_oracle likes it.
2. looks like there is no more auto-detect of my Brother network printer in MX23, unlike in MX21
3. when I opened Document scanner (simple-scan), strangely enough an authentication window opened asking for password. Granted, I haven't installed the brother scanner driver yet, but this has never happened before on any previous MX versions, even if the application was opened prior to driver installation. In the past, the application simply indicated that there was no scanner available.
You do not have the required permissions to view the files attached to this post.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX-23 alpha2 feedback thread
@dolphin_oracle , as previously raised, when you change from mx-comfort to mx-comfort-dark theme, simple-scan and archive-manager (I think these still use libhandy and not libadwaita) display our light comfort theme and not the dark. You still get our mx-comfort title bar but the rest of the window displays the light theme background.
This is unless we use dconf-editor to set "org.gnome.desktop.interface color-scheme" to " prefer-dark", after which these 2 applications show up with the complete mx-comfort-dark theme.
I generated 2 different oomox numix-based dark themes in comparison, and note that 1 theme allowed the 2 apps to automatically change to its themed look without dconf-editor changes, while the other theme behaved even worse than mx-comfort-dark and displayed the 2 apps in the ugly cream adwaita basic theme, even the title bar.
I'm not sure but I believe that we only tweaked the ,css files and not the dark.css files (or the other way around, can't recall) in mx-comfort-dark before you re-generated the xml gresource file. That might possibly be the reason for the partial application of the comfort-dark theme without changing the settings in dconf-editor.
I'm posting it here in the hope that someone knowledgeable in gtk theming or using .css style sheets, etc, could help.
This is unless we use dconf-editor to set "org.gnome.desktop.interface color-scheme" to " prefer-dark", after which these 2 applications show up with the complete mx-comfort-dark theme.
I generated 2 different oomox numix-based dark themes in comparison, and note that 1 theme allowed the 2 apps to automatically change to its themed look without dconf-editor changes, while the other theme behaved even worse than mx-comfort-dark and displayed the 2 apps in the ugly cream adwaita basic theme, even the title bar.
I'm not sure but I believe that we only tweaked the ,css files and not the dark.css files (or the other way around, can't recall) in mx-comfort-dark before you re-generated the xml gresource file. That might possibly be the reason for the partial application of the comfort-dark theme without changing the settings in dconf-editor.
I'm posting it here in the hope that someone knowledgeable in gtk theming or using .css style sheets, etc, could help.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
- Eadwine Rose
- Administrator
- Posts: 14485
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-23 alpha2 feedback thread
Upgraded, reset things to use root, applied. Then remembered to also re-enable mounting by non root users, to which the root password was given and accepted.dolphin_oracle wrote: Sat Apr 08, 2023 5:35 pmthanks, that one is still using su-to-root as well, so its actually not right.Eadwine Rose wrote: Sat Apr 08, 2023 5:07 pm In the alpha one interesting thing happened.
I put the bookworm debian multimedia repo in for dvdstyler. That threw a GPG key on reload. Running Fix GPG fixed it so I could install (even though an error still pops up when you activate the repo, it works).
But yeah.. the interesting thing is, everywhere I have been so far, despite having tried to put the root pass in, it needed the user pass.
EXCEPT for MX Fix GPG! I had to enter the root password for that one to go through. Took me by surprise alright.
I did fix mx-tweak, although you might have to reset to root again.
Disk manager, auto mounting partitions also took the root pass now. Automounted the ntfs data drive, but type was set to ntfs, not ntfs-3g. Changed manually using the dropdown. I vaguely remember this was changed to be ntfs-3g automatically already?
MX-23.6_x64 July 31 2023 * 6.1.0-35amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
- Eadwine Rose
- Administrator
- Posts: 14485
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-23 alpha2 feedback thread
I am slowly plowing through my install sheet, I cannot seem to find hddtemp for my drive temperatures.
/var/log/syslog is no longer there, now that is puzzling. Where did that go?
/etc/smartd.conf same, which I need to put a device scan adjustment line into to scan once every five hours rather than the default five minutes.
/etc/pulse/daemon.conf same.
I adjusted the lines of default-fragments and default-fragment-size-msec to be default-fragments = 5, default-fragment-size-msec = 2.
For the life of me can't remember why anymore, but something to do with the sound that needed adjusting.
/var/log/syslog is no longer there, now that is puzzling. Where did that go?
/etc/smartd.conf same, which I need to put a device scan adjustment line into to scan once every five hours rather than the default five minutes.
/etc/pulse/daemon.conf same.
I adjusted the lines of default-fragments and default-fragment-size-msec to be default-fragments = 5, default-fragment-size-msec = 2.
For the life of me can't remember why anymore, but something to do with the sound that needed adjusting.
MX-23.6_x64 July 31 2023 * 6.1.0-35amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-23 alpha2 feedback thread
Some of the stuff I usually install from MX's own repos, eg qmplay and ksnip, are not there yet, naturally.
I'll only put in a package request after mx23 is released.
I'll only put in a package request after mx23 is released.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400