I just went through the UP4 installation (1400+ files, 90 minutes), and it went fine except for 2 very minor things:
I didn't get the 3.2 kernel, though it looked like I got some of the header files. I'm still at 2.6.39-2-686-pae, and while this doesn't really bother me, I am curious as to why my machine (which is an HP HDX16, Centrino2 with 4gig of RAM) refuses to apply it. I only have 1 package on the Ignore list in Mint-Debian-Update and it has nothing to do with the kernel (nvidia-installer-cleanup, which does bad things to my manually installed NVIDIA drivers).
The SAMBA Guest account now shows up on the initial login screen. I turned this up:
https://bugs.launchpad.net/ubuntu/+sour ... bug/814139
But since this is LMDE, this is either coming from Debian, or something else is going on.
And on a better footnote: they finally fixed the annoying bug in the Mint-X themes that make the right-click menus not persist in Thunar items, which is good because whatever they did to the Clearlooks theme (what I was using previously) makes it look hideous.
Obviously, any input would be appreciated.
MikeC
[PARTIAL SOLVE] No 3.2 kernel & SAMBA Guest acct on gdm3 scr
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
-
mikecz
[PARTIAL SOLVE] No 3.2 kernel & SAMBA Guest acct on gdm3 scr
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
zerozero
Re: LMDE XFCE UP4: No 3.2 kernel & SAMBA Guest Account on l
MikeC,
regarding the kernel, i think that when you installed the pae, somehow the system missed the meta-pkgs (there's 2, one for the headers and one for the image) >>of course this is an amd64 output (look in synaptic according)
regarding the kernel, i think that when you installed the pae, somehow the system missed the meta-pkgs (there's 2, one for the headers and one for the image) >>of course this is an amd64 output (look in synaptic according)
Code: Select all
amadeu@amadeu:~$ dpkg --list | egrep '(linux-image*)|(linux-headers*)'
ii linux-headers-2.6-amd64 3.2+44 Header files for Linux amd64 configuration (dummy package)
ii linux-headers-2.6.32-5-common 2.6.32-31 Common header files for Linux 2.6.32-5
ii linux-headers-2.6.38-2-amd64 2.6.38-5 Header files for Linux 2.6.38-2-amd64
ii linux-headers-2.6.38-2-common 2.6.38-5 Common header files for Linux 2.6.38-2
ii linux-headers-2.6.39-2-amd64 2.6.39-3 Header files for Linux 2.6.39-2-amd64
ii linux-headers-2.6.39-2-common 2.6.39-3 Common header files for Linux 2.6.39-2
ii linux-headers-3.0.0-1-amd64 3.0.0-3 Header files for Linux 3.0.0-1-amd64
ii linux-headers-3.0.0-1-common 3.0.0-3 Common header files for Linux 3.0.0-1
ii linux-headers-3.1.0-1-amd64 3.1.8-2 Header files for Linux 3.1.0-1-amd64
ii linux-headers-3.1.0-1-common 3.1.8-2 Common header files for Linux 3.1.0-1
ii linux-headers-3.2.0-1-amd64 3.2.6-1 Header files for Linux 3.2.0-1-amd64
ii linux-headers-3.2.0-1-common 3.2.6-1 Common header files for Linux 3.2.0-1
ii linux-headers-3.2.0-2-amd64 3.2.12-1 Header files for Linux 3.2.0-2-amd64
ii linux-headers-3.2.0-2-common 3.2.12-1 Common header files for Linux 3.2.0-2
ii linux-headers-amd64 3.2+44 Header files for Linux amd64 configuration (meta-package)
ii linux-image-2.6-amd64 3.2+44 Linux for 64-bit PCs (dummy package)
ii linux-image-2.6.32-5-amd64 2.6.32-31 Linux 2.6.32 for 64-bit PCs
ii linux-image-2.6.38-2-amd64 2.6.38-5 Linux 2.6.38 for 64-bit PCs
ii linux-image-2.6.39-2-amd64 2.6.39-3 Linux 2.6.39 for 64-bit PCs
ii linux-image-3.0.0-1-amd64 3.0.0-3 Linux 3.0.0 for 64-bit PCs
ii linux-image-3.1.0-1-amd64 3.1.8-2 Linux 3.1 for 64-bit PCs
ii linux-image-3.2.0-1-amd64 3.2.6-1 Linux 3.2 for 64-bit PCs
ii linux-image-3.2.0-2-amd64 3.2.12-1 Linux 3.2 for 64-bit PCs
ii linux-image-amd64 3.2+44 Linux for 64-bit PCs (meta-package)
amadeu@amadeu:~$
-
mikecz
Re: LMDE XFCE UP4: No 3.2 kernel & SAMBA Guest Account on l
A quick look in synaptic shows that I have several 3.x linux-headers packages installed, which I knew and which is why I had expected to get 3.2 in this UP.zerozero wrote:MikeC,
regarding the kernel, i think that when you installed the pae, somehow the system missed the meta-pkgs (there's 2, one for the headers and one for the image) >>of course this is an amd64 output (look in synaptic according)Code: Select all
amadeu@amadeu:~$ dpkg --list | egrep '(linux-image*)|(linux-headers*)' ii linux-headers-2.6-amd64 3.2+44 Header files for Linux amd64 configuration (dummy package) ii linux-headers-2.6.32-5-common 2.6.32-31 Common header files for Linux 2.6.32-5 ii linux-headers-2.6.38-2-amd64 2.6.38-5 Header files for Linux 2.6.38-2-amd64 ii linux-headers-2.6.38-2-common 2.6.38-5 Common header files for Linux 2.6.38-2 ii linux-headers-2.6.39-2-amd64 2.6.39-3 Header files for Linux 2.6.39-2-amd64 ii linux-headers-2.6.39-2-common 2.6.39-3 Common header files for Linux 2.6.39-2 ii linux-headers-3.0.0-1-amd64 3.0.0-3 Header files for Linux 3.0.0-1-amd64 ii linux-headers-3.0.0-1-common 3.0.0-3 Common header files for Linux 3.0.0-1 ii linux-headers-3.1.0-1-amd64 3.1.8-2 Header files for Linux 3.1.0-1-amd64 ii linux-headers-3.1.0-1-common 3.1.8-2 Common header files for Linux 3.1.0-1 ii linux-headers-3.2.0-1-amd64 3.2.6-1 Header files for Linux 3.2.0-1-amd64 ii linux-headers-3.2.0-1-common 3.2.6-1 Common header files for Linux 3.2.0-1 ii linux-headers-3.2.0-2-amd64 3.2.12-1 Header files for Linux 3.2.0-2-amd64 ii linux-headers-3.2.0-2-common 3.2.12-1 Common header files for Linux 3.2.0-2 ii linux-headers-amd64 3.2+44 Header files for Linux amd64 configuration (meta-package) ii linux-image-2.6-amd64 3.2+44 Linux for 64-bit PCs (dummy package) ii linux-image-2.6.32-5-amd64 2.6.32-31 Linux 2.6.32 for 64-bit PCs ii linux-image-2.6.38-2-amd64 2.6.38-5 Linux 2.6.38 for 64-bit PCs ii linux-image-2.6.39-2-amd64 2.6.39-3 Linux 2.6.39 for 64-bit PCs ii linux-image-3.0.0-1-amd64 3.0.0-3 Linux 3.0.0 for 64-bit PCs ii linux-image-3.1.0-1-amd64 3.1.8-2 Linux 3.1 for 64-bit PCs ii linux-image-3.2.0-1-amd64 3.2.6-1 Linux 3.2 for 64-bit PCs ii linux-image-3.2.0-2-amd64 3.2.12-1 Linux 3.2 for 64-bit PCs ii linux-image-amd64 3.2+44 Linux for 64-bit PCs (meta-package) amadeu@amadeu:~$
I'm rather tempted to just snapshot my home director, wipe and re-install, but that defeats the purpose of why I went with LMDE XFCE in the first place: to get off the wipe-and-reinstall every X months treadmill. If I get to that point, I may as well go to another distro.
MikeC, is rather disappointed with LMDE XFCE at this point.
-
zerozero
Re: LMDE XFCE UP4: No 3.2 kernel & SAMBA Guest Account on l
it's about those 2 that i was talking about
Code: Select all
ii linux-headers-amd64 3.2+44 Header files for Linux amd64 configuration (meta-package)Code: Select all
ii linux-image-amd64 3.2+44 Linux for 64-bit PCs (meta-package)Linux for 64-bit PCs (meta-package)
This package depends on the latest Linux kernel and modules for use on PCs
with AMD64 or Intel 64 processors.
This kernel also runs on a Xen hypervisor. It supports both privileged
(dom0) and unprivileged (domU) operation.
Header files for Linux amd64 configuration (meta-package)
This package depends on the architecture-specific header files for the
latest Linux kernel amd64 configuration.
-
mikecz
Re: LMDE XFCE UP4: No 3.2 kernel & SAMBA Guest Account on l
I manually installed the proper linux-image file for the 3.2 kernel, and everything went fine, though I am still puzzled as to why mint-debian-update didn't do this given that it had grabbed all the linux-header packages.
I'll have to live with the SAMBA Guest account coming up on the gdm3 screen I suppose.
MikeC
I'll have to live with the SAMBA Guest account coming up on the gdm3 screen I suppose.
MikeC
Re: [PARTIAL SOLVE] No 3.2 kernel & SAMBA Guest acct on gdm3
Are you talking about the built in "nobody" account or any user you define with a "guest account =" parameter in smb.conf?
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
-
mikecz
Re: [PARTIAL SOLVE] No 3.2 kernel & SAMBA Guest acct on gdm3
It is listed as "SAMBA Guest Account", username smbguest, member of nobody group. smb.conf does allow the guest account, but I haven't changed it from the default or from what it was prior to UP4.altair4 wrote:Are you talking about the built in "nobody" account or any user you define with a "guest account =" parameter in smb.conf?
MikeC
Re: [PARTIAL SOLVE] No 3.2 kernel & SAMBA Guest acct on gdm3
That's odd. I have LMDE XFCE running in VBox. It has not been updated to UP4.
There is no smbguest account added by default. There is a "nobody:nogroup" account by default but it's set up for this sort of thing so it has no local login password nor does it have a home directory. In fact the guest account in samba is automatically set to nobody:
There is no smbguest account added by default. There is a "nobody:nogroup" account by default but it's set up for this sort of thing so it has no local login password nor does it have a home directory. In fact the guest account in samba is automatically set to nobody:
Does the smb.conf file actually override this default with a "guest account = smbguest" or is it something you added.> testparm -sv /dev/null | grep "guest account"
guest account = nobody
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
-
mikecz
Re: [PARTIAL SOLVE] No 3.2 kernel & SAMBA Guest acct on gdm3
Like I said, its whatever the default is since i didn't change anything. smbconf says guest account=ok but I never specifically added it.altair4 wrote:That's odd. I have LMDE XFCE running in VBox. It has not been updated to UP4.
There is no smbguest account added by default. There is a "nobody:nogroup" account by default but it's set up for this sort of thing so it has no local login password nor does it have a home directory. In fact the guest account in samba is automatically set to nobody:Does the smb.conf file actually override this default with a "guest account = smbguest" or is it something you added.> testparm -sv /dev/null | grep "guest account"
guest account = nobody
MikeC