RC2 feedback
Re: RC2 feedback
@JimC, I can't work on this any more ATM. I am very interested but I have a bunch of other stuff to get ready for the final MX release.
Re: RC2 feedback
The /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf file that forces the pkexec authentications to ask for the root password instead of the user's password is missing. It was included in the Betas.
This is the post in the development team forum: http://forum.mepiscommunity.org/viewtop ... 81#p327181
and the command that creates it:
It creates the following /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf file:
This is the post in the development team forum: http://forum.mepiscommunity.org/viewtop ... 81#p327181
and the command that creates it:
Code: Select all
su -c 'echo -e "[Configuration]\nAdminIdentities=unix-user:0\n" > /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf'
[Configuration]
AdminIdentities=unix-user:0
Re: RC2 feedback
@JimC:BitJam wrote:@JimC, I can't work on this any more ATM. I am very interested but I have a bunch of other stuff to get ready for the final MX release.
I have the same ethernet chipset in my laptop and it works fine (I never had any connect problems with it) when I use a wired connection (I mostly use wireless on this laptop though).
Running MX-14 RC2.
Part of inxi -Fxxx :
Code: Select all
Network: Card: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller
driver: r8169 ver: 2.3LK-NAPI port: d800 bus-ID: 04:00.0 chip-ID: 10ec:8168
IF: eth0 state: down mac: 00:21:85:da:73:46
Card: Ralink RT2790 Wireless 802.11n 1T/2R PCIe driver: rt2800pci ver: 2.3.0 bus-ID: 03:00.0 chip-ID: 1814:0781
IF: wlan0 state: up mac: 00:15:af:da:a8:1a
Ko Bros Linux User #312596. MX14.4, MX14.3, Mepis 12, Debian 7, antiX 15, Peppermint 5...and sometimes Win7
- anticapitalista
- Developer
- Posts: 4166
- Joined: Sat Jul 15, 2006 10:40 am
Re: RC2 feedback
kmathern wrote:The /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf file that forces the pkexec authentications to ask for the root password instead of the user's password is missing. It was included in the Betas.
This is the post in the development team forum: http://forum.mepiscommunity.org/viewtop ... 81#p327181
and the command that creates it:It creates the following /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf file:Code: Select all
su -c 'echo -e "[Configuration]\nAdminIdentities=unix-user:0\n" > /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf'
[Configuration]
AdminIdentities=unix-user:0
It isn't missing on RC2 here.
anticapitalista
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
Re: RC2 feedback
Guys.
My apologies. My reports of a problem using my Realtek RTL8111/8168B chipset for wired ethernet were wrong (previous posts now edited).
This was all a problem with a cable that wasn't pushed in all the way. I thought this was odd when I saw that the problem was supposedly corrected in newer kernel modules on one page about it. Then, when I booted back into Win 8, I noticed my wired network had stopped working there, too.
My wired cable wasn't seated all the way on the PC side causing the issue. A small push on the connector solved it. :-)
BTW, the 8.038 download for installing their newer R8168 driver that I downloaded from this Realtek page also works fine (that's the r8168 driver I have installed in MX-14 now):
http://www.realtek.com.tw/downloads/dow ... wn=false#2
But, so do the newer r8169 drivers that come with MX-14 and other distros like OpenSUSE 13.1.
I also double checked to make sure the stock r8169 in MX-14 works by booting into a USB stick with it on it. No problem -- Wired Ethernet works fine with it. But, since I've already blacklisted the r8169 driver and installed the R8168 driver from Realtek, I'll just leave the hard drive install running using the newer r8168 driver.
My apologies... User error was the problem (cable not seated all the way in). There is no issue using the r8169 driver with the RTL8111/8168B chipsets using the newer drivers. Apparently, that was fixed in newer kernels some time back (so that you don't need the r8168 driver for them to work properly, as the r8169 driver also works with this chipset).
P.S.
After finding page after page about the r8169 driver not working, I wrongly assumed I had a driver issue. For example, this one, and the one I linked to earlier:
http://www.dividebyzero.co.za/blog/2012 ... -in-linux/
But, I also found some newer posts indicating the problem was fixed. For example, this one has an update at the top:
http://www.twm-kd.com/linux/realtek-rtl ... ntu-linux/
Then, when I noticed my wired ethernet had quit working in Windows, too -- I found the loose cable causing it.
Again, my apologies. User error on my part.
My apologies. My reports of a problem using my Realtek RTL8111/8168B chipset for wired ethernet were wrong (previous posts now edited).
This was all a problem with a cable that wasn't pushed in all the way. I thought this was odd when I saw that the problem was supposedly corrected in newer kernel modules on one page about it. Then, when I booted back into Win 8, I noticed my wired network had stopped working there, too.
My wired cable wasn't seated all the way on the PC side causing the issue. A small push on the connector solved it. :-)
BTW, the 8.038 download for installing their newer R8168 driver that I downloaded from this Realtek page also works fine (that's the r8168 driver I have installed in MX-14 now):
http://www.realtek.com.tw/downloads/dow ... wn=false#2
But, so do the newer r8169 drivers that come with MX-14 and other distros like OpenSUSE 13.1.
I also double checked to make sure the stock r8169 in MX-14 works by booting into a USB stick with it on it. No problem -- Wired Ethernet works fine with it. But, since I've already blacklisted the r8169 driver and installed the R8168 driver from Realtek, I'll just leave the hard drive install running using the newer r8168 driver.
My apologies... User error was the problem (cable not seated all the way in). There is no issue using the r8169 driver with the RTL8111/8168B chipsets using the newer drivers. Apparently, that was fixed in newer kernels some time back (so that you don't need the r8168 driver for them to work properly, as the r8169 driver also works with this chipset).
P.S.
After finding page after page about the r8169 driver not working, I wrongly assumed I had a driver issue. For example, this one, and the one I linked to earlier:
http://www.dividebyzero.co.za/blog/2012 ... -in-linux/
But, I also found some newer posts indicating the problem was fixed. For example, this one has an update at the top:
http://www.twm-kd.com/linux/realtek-rtl ... ntu-linux/
Then, when I noticed my wired ethernet had quit working in Windows, too -- I found the loose cable causing it.
Again, my apologies. User error on my part.
Last edited by JimC on Mon Mar 17, 2014 8:59 am, edited 4 times in total.
Re: RC2 feedback
Confirm that it is present in RC2
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: RC2 feedback
That's strange, I see it there now, I didn't earlier.anticapitalista wrote:kmathern wrote:The /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf file that forces the pkexec authentications to ask for the root password instead of the user's password is missing. It was included in the Betas.
This is the post in the development team forum: http://forum.mepiscommunity.org/viewtop ... 81#p327181
and the command that creates it:It creates the following /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf file:Code: Select all
su -c 'echo -e "[Configuration]\nAdminIdentities=unix-user:0\n" > /etc/polkit-1/localauthority.conf.d/52-force-root-for-admin-auth.conf'
[Configuration]
AdminIdentities=unix-user:0
It isn't missing on RC2 here.
Re: RC2 feedback
Dolphin has been weird for me lately, not showing files that I know are there even if I go up a level and back down. Wonder if this is related...
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: RC2 feedback
I was going to blame it on posting at 04:00 AM in morning.Jerry3904 wrote:Dolphin has been weird for me lately, not showing files that I know are there even if I go up a level and back down. Wonder if this is related...
Re: RC2 feedback
It's always been weird for me that way, so I've added the "Reload" button to the toolbar. Searching the web shows it's using libgamin or libfam0 to keep track of changes, but I've tried both and the problem persists.Jerry3904 wrote:Dolphin has been weird for me lately, not showing files that I know are there even if I go up a level and back down. Wonder if this is related...