Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #183420 > unrolled thread

How to gain control over the system?

Back to article view | Back to linux.debian.user

Contents

  How to gain control over the system? Kaj Persson <70147persson@telia.com> - 2017-07-09 00:10 +0200
    Re: How to gain control over the system? Oflameo <oflameo2@gmail.com> - 2017-07-09 00:30 +0200
      Re: How to gain control over the system? Fungi4All <fungilife@protonmail.com> - 2017-07-09 01:00 +0200
        Re: How to gain control over the system? Anders Andersson <pipatron@gmail.com> - 2017-07-09 11:30 +0200
          Re: How to gain control over the system? Dejan Jocic <jodejka@gmail.com> - 2017-07-09 12:00 +0200
    Re: How to gain control over the system? davidson@freevolt.org - 2017-07-09 01:30 +0200
      Re: How to gain control over the system? Fungi4All <fungilife@protonmail.com> - 2017-07-09 12:10 +0200
        Re: How to gain control over the system? Richard Owlett <rowlett@cloud85.net> - 2017-07-09 13:50 +0200
    Re: How to gain control over the system? Kaj Persson <70147persson@telia.com> - 2017-07-09 15:10 +0200
      Re: How to gain control over the system? [a security-side-note] Eike Lantzsch <zp6cge@gmx.net> - 2017-07-09 16:00 +0200
        Re: How to gain control over the system? [a security-side-note] Dejan Jocic <jodejka@gmail.com> - 2017-07-09 16:20 +0200
      Re: How to gain control over the system? Fungi4All <fungilife@protonmail.com> - 2017-07-09 19:00 +0200
        Re: How to gain control over the system? Kaj Persson <70147persson@telia.com> - 2017-07-09 19:10 +0200
          Re: How to gain control over the system? Kaj Persson <70147persson@telia.com> - 2017-07-09 23:40 +0200
      Re: How to gain control over the system? Felix Miata <mrmazda@earthlink.net> - 2017-07-10 01:40 +0200
        Re: How to gain control over the system? Kaj Persson <70147persson@telia.com> - 2017-07-11 22:40 +0200
          Re: How to gain control over the system? David Wright <deblis@lionunicorn.co.uk> - 2017-07-11 23:00 +0200
            Re: How to gain control over the system? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-07-11 23:10 +0200
          Re: How to gain control over the system? Felix Miata <mrmazda@earthlink.net> - 2017-07-12 03:50 +0200
            Re: How to gain control over the system? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-07-12 14:30 +0200
            Re: How to gain control over the system? Kaj Persson <kape_fin@algonet.se> - 2017-07-13 12:30 +0200
              Re: How to gain control over the system? <tomas@tuxteam.de> - 2017-07-13 13:20 +0200
                Re: How to gain control over the system? Fungi4All <fungilife@protonmail.com> - 2017-07-13 14:20 +0200
                  Re: How to gain control over the system? <tomas@tuxteam.de> - 2017-07-13 15:20 +0200
                Re: How to gain control over the system? tomas@tuxteam.de - 2017-07-13 15:20 +0200
                  Re: How to gain control over the system? David Wright <deblis@lionunicorn.co.uk> - 2017-07-13 16:30 +0200
    Re: How to gain control over the system? Jimmy Johnson <field.engineer@gmail.com> - 2017-07-09 22:30 +0200
      Re: How to gain control over the system? Kaj Persson <kape_fin@algonet.se> - 2017-07-10 00:40 +0200
        Re: How to gain control over the system? Jimmy Johnson <field.engineer@gmail.com> - 2017-07-10 00:50 +0200
        Re: How to gain control over the system? Joel Rees <joel.rees@gmail.com> - 2017-07-10 03:10 +0200
        Re: How to gain control over the system? Dejan Jocic <jodejka@gmail.com> - 2017-07-10 10:00 +0200
        Re: How to gain control over the system? RavenLX <ravenlx@sitesplace.net> - 2017-07-12 14:40 +0200
          Re: How to gain control over the system? <tomas@tuxteam.de> - 2017-07-12 15:30 +0200
            Re: How to gain control over the system? RavenLX <ravenlx@sitesplace.net> - 2017-07-16 15:50 +0200
              Re: How to gain control over the system? <tomas@tuxteam.de> - 2017-07-16 16:50 +0200

Page 1 of 2  [1] 2  Next page →

#183420 — How to gain control over the system?

Hi all,

Anyone having an idea how to get back the command over my desktop, 
including the panels? Until two weeks ago I ran Debian 8 ("jessie"), but 
after a unsuccessful clean-up operation the whole system became totally 
corrupted, and I decided to to a complete new install of the new Debian 
9 ("stretch") and Mate (which I was using in jessie too). I was using 
the live DVD put on a memory stick. All went fine, and the system 
started without problems. I was happy to notice that I could now use the 
Nouveau driver for the screen. Until now I have had to use the nVidia 
driver certainly without problems, but it is good being able to use free 
software.

But now I discovered an issue, I cannot manage my desktop. I have always 
at the previous installations, and they are quite many now, been advised 
to, for security reason, leave the root password unset, which causes the 
root account go passive, and for all tasks where I need root authority I 
go via su/sudo. It has always worked fine, and this using su/sudo still 
does. But I cannot control the panels, I have two of them, one on top 
intended for icons of my most used programs, as a kind of favourite 
menu, and one at bottom where the active programmes appear as buttons. 
The bottom panel is working mostly as I want, but I cannot add new apps 
to it, e.g. the window switch, I used to have. And I cannot add the 
program icons to top panel. Via a right click on a program menu item I 
have the option "Put this to the panel" (well, possibly not the correct 
words, this is a home made translation from my Swedish version), but, 
when trying to select that, nothing happens.

However the related options to save icon to the desktop works fine, and 
I can also sort the icons to what I find useful, but it does not survive 
a cold start. All the icons come back in some kind of default order, 
which I have not been able found out. It is at least not alphabetic.

So can someone help me get the command back, or do I have to make a new 
reinstall, hoping for better luck. Possibly setting a password on the 
Admin, hence activating that account, which I would prefer not having to.

Thank you in advance
Kaj

[toc] | [next] | [standalone]

#183421

Did you remember to reconfigure sudo? What Desktop Environment are you
using?

On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
> Hi all,
> 
> Anyone having an idea how to get back the command over my desktop, 
> including the panels? Until two weeks ago I ran Debian 8 ("jessie"),
> but 
> after a unsuccessful clean-up operation the whole system became
> totally 
> corrupted, and I decided to to a complete new install of the new
> Debian 
> 9 ("stretch") and Mate (which I was using in jessie too). I was
> using 
> the live DVD put on a memory stick. All went fine, and the system 
> started without problems. I was happy to notice that I could now use
> the 
> Nouveau driver for the screen. Until now I have had to use the
> nVidia 
> driver certainly without problems, but it is good being able to use
> free 
> software.
> 
> But now I discovered an issue, I cannot manage my desktop. I have
> always 
> at the previous installations, and they are quite many now, been
> advised 
> to, for security reason, leave the root password unset, which causes
> the 
> root account go passive, and for all tasks where I need root
> authority I 
> go via su/sudo. It has always worked fine, and this using su/sudo
> still 
> does. But I cannot control the panels, I have two of them, one on
> top 
> intended for icons of my most used programs, as a kind of favourite 
> menu, and one at bottom where the active programmes appear as
> buttons. 
> The bottom panel is working mostly as I want, but I cannot add new
> apps 
> to it, e.g. the window switch, I used to have. And I cannot add the 
> program icons to top panel. Via a right click on a program menu item
> I 
> have the option "Put this to the panel" (well, possibly not the
> correct 
> words, this is a home made translation from my Swedish version),
> but, 
> when trying to select that, nothing happens.
> 
> However the related options to save icon to the desktop works fine,
> and 
> I can also sort the icons to what I find useful, but it does not
> survive 
> a cold start. All the icons come back in some kind of default order, 
> which I have not been able found out. It is at least not alphabetic.
> 
> So can someone help me get the command back, or do I have to make a
> new 
> reinstall, hoping for better luck. Possibly setting a password on
> the 
> Admin, hence activating that account, which I would prefer not having
> to.
> 
> Thank you in advance
> Kaj
> 

[toc] | [prev] | [next] | [standalone]

#183424

[Multipart message — attachments visible in raw view] — view raw

> From: oflameo2@gmail.com
> To: Kaj Persson <70147persson@telia.com>, debian-user@lists.debian.org
> Did you remember to reconfigure sudo? What Desktop Environment are you
> using?

He said Mate

> On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
>> But now I discovered an issue, I cannot manage my desktop. I have
>> always at the previous installations, and they are quite many now, been
>> advised to, for security reason, leave the root password unset, which causes
>> the root account go passive, and for all tasks where I need root
>> authority I go via su/sudo.

It is a bad idea despite of what security gurus may advise. You may lose your system
and never get it back.

>> But I cannot control the panels, I have two of them, one on
>> top
>>

A user should not need sudo rights to edit the conf files in the desktop.
It is all stored in the /home/*user* subdirectory, while as root your home
is /root. Chances are the access rights in your home directory have been
restricted, so you need to give yourself as a user the rights back.
As a su you should not be able to alter the /home/user directories.
What I suspect you've done is copy the /home from an old system
which transfered the rights of that system and from a different user.
Let's say in that system your username was mate99 and so it is in the
new system. But the user id in that system was user 1003 and now
you are user 1001. 1001 will not be able to adjust conf. files for user
1003. If you open the filemanager and your desktop folder is owned
by a user 1003 (or some number) then you need to switch the rights
of all your home/user stuff to be owned by mate99

[toc] | [prev] | [next] | [standalone]

#183432

[Multipart message — attachments visible in raw view] — view raw

On Sun, Jul 9, 2017 at 12:51 AM, Fungi4All <fungilife@protonmail.com> wrote:

> On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
>
> > But now I discovered an issue, I cannot manage my desktop. I have
> > always at the previous installations, and they are quite many now, been
> > advised to, for security reason, leave the root password unset, which
> causes
> > the root account go passive, and for all tasks where I need root
> > authority I  go via su/sudo.
>
>
> It is a bad idea despite of what security gurus may advise.  You may lose
> your system
> and never get it back.
>


It's an even worse idea to listen to people on the internet who ignore
"security gurus" based on rumours. You can easily restore or change the
root password if it's lost or unset.

[toc] | [prev] | [next] | [standalone]

#183439

On 09-07-17, Anders Andersson wrote:
> On Sun, Jul 9, 2017 at 12:51 AM, Fungi4All <fungilife@protonmail.com> wrote:
> 
> > On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
> >
> > > But now I discovered an issue, I cannot manage my desktop. I have
> > > always at the previous installations, and they are quite many now, been
> > > advised to, for security reason, leave the root password unset, which
> > causes
> > > the root account go passive, and for all tasks where I need root
> > > authority I  go via su/sudo.
> >
> >
> > It is a bad idea despite of what security gurus may advise.  You may lose
> > your system
> > and never get it back.
> >
> 
> 
> It's an even worse idea to listen to people on the internet who ignore
> "security gurus" based on rumours. You can easily restore or change the
> root password if it's lost or unset.

Leaving root password unassigned for "security" reasons is silly.
Heaving, or not heaving root account assigned does not make your system
any more secure. For some things you do need root account. Those systems
that use sudo only approach ( read Ubuntu and derivates ) have sulogin
patched to allow single user mode, for example. And it is made so on
Ubuntu out of fear that new users attracted to Linux will mess up things
more if they have access to root account. Not that it stopped people to
be people and to mess things up equally successful with sudo account. As
for those "security gurus", who are they? Real gurus? Or just people
repeating what they've read somewhere with little to no understanding
what they've read?

[toc] | [prev] | [next] | [standalone]

#183425

On Sat, 8 Jul 2017, Kaj Persson wrote:

> Hi all,
>
> Anyone having an idea how to get back the command over my desktop,
> including the panels? Until two weeks ago I ran Debian 8 ("jessie"),
> but after a unsuccessful clean-up operation the whole system became
> totally corrupted, and I decided to to a complete new install of the
> new Debian 9 ("stretch") and Mate (which I was using in jessie
> too). I was using the live DVD put on a memory stick.

As they say[1],[2],[3], do not use a live image for installs.

1. https://lists.debian.org/debian-user/2017/06/msg00723.html
2. https://lists.debian.org/debian-user/2017/06/msg00740.html
3. https://lists.debian.org/debian-user/2017/06/msg00755.html

-- 
"Jesus! Where will it end? How low do you have to stoop in this country to be President?"
Hunter S Thompson, 1972

[toc] | [prev] | [next] | [standalone]

#183441

[Multipart message — attachments visible in raw view] — view raw

> From: davidson@freevolt.org
> To: debian-user@lists.debian.org
> As they say[1],[2],[3], do not use a live image for installs.
> 1. https://lists.debian.org/debian-user/2017/06/msg00723.html
> 2. https://lists.debian.org/debian-user/2017/06/msg00740.html
> 3. https://lists.debian.org/debian-user/2017/06/msg00755.html

My experience with live images is that they include the installer and
a live image. The gui within the live system most usually runs into
errors, while the installer from the initial grub-like menu works just like the
netinstall system. I suspect the installer without booting the live
system has maximum resources available, while the live system
even as idle requires 15-20% of resources to run the installation
gui.

[toc] | [prev] | [next] | [standalone]

#183451

On 07/09/2017 05:08 AM, Fungi4All wrote:
>> From: davidson@freevolt.org
>> To: debian-user@lists.debian.org
>> As they say[1],[2],[3], do not use a live image for installs.
>> 1. https://lists.debian.org/debian-user/2017/06/msg00723.html
>> 2. https://lists.debian.org/debian-user/2017/06/msg00740.html
>> 3. https://lists.debian.org/debian-user/2017/06/msg00755.html
>
> My experience with live images is that they include the installer and
> a live image. The gui within the live system most usually runs into
> errors, while the installer from the initial grub-like menu works just like the
> netinstall system. I suspect the installer without booting the live
> system has maximum resources available, while the live system
> even as idle requires 15-20% of resources to run the installation
> gui.
>

I see you can't be bothered reading relevant info before posting.
There *WAS* a bug in the live version of 9.0.
It was fixed in a 9.01 release of the live edition.

[toc] | [prev] | [next] | [standalone]

#183455

Thank you all for thoughts and viewpoints on what can be wrong in my 
installation of Debian 9. I have looked through places I might expect 
can contain some explanation, but so far I have not been able to exclaim 
an "Ah, that's it!". Here are some of my observations:

* First source of install: Well, I do know I wrote that used the live 
image, but to be honest, for now I am not sure, I do not remember. I had 
downloaded the live image as well as the install image, and most 
probable choice would be the later. But I do not know. Anyway the 
install process itself went without any problems.

* At the install I made it fully new from the bottom. The only directory 
I kept unchanged was my home directory. This is situated on an own 
partition. All the others were reformatted: /, /boot, /usr, /var and 
/tmp. All these are on individual partitions while e.g. /etc is 
contained in the root partition. At earlier installations I have noticed 
that the home directory can contain wrong configuration files, so as a 
test I moved all hidden files i.e. files starting with a dot to a new 
created directory "hidden". This was however after the install. So at a 
subsequent cold start the system had no configuration files there but 
created new ones with default values. This however had no positive 
impact on my problem.

* Configuring sudo? No I have not done that explicitly, not more than 
what the install program did itself. I have looked at /etc/sudoers and 
what I think the important lines are:

     # User privilege specification
     root    ALL=(ALL:ALL) ALL

     # Allow members of group sudo to execute any command
     %sudo   ALL=(ALL:ALL) ALL

     #includedir /etc/sudoers.d

In /etc/sudoers.d there are no more files than README.

There is no /etc/sudo.conf file.

* Regarding access to my user directory: During my search I did in fact 
find some files and directories owned by user root or group root. These 
are changed to be owned by my user id and group id, but this did not 
help. By the way, On this computer I have always had just one user, 
mine, and hence got the user id 1000 and group id 1000. This is the case 
now too.

uid 1000 is a member of the sudo group.

* As I wrote I have always used this method of not setting any password 
to the root account, and this is for quite many years now. My Linux path 
has gone via Ubuntu, well to be honest a couple of years after the 
Microsoft era I ran in Suse, but was not fully satisfied. And when 
Ubuntu and Canonical introduced Unity, I left that ship for Linux Mint 
Debian edition (LMDE) until I took the last(?) step into Debian a couple 
of years ago where the entrance point was jessie. The empty root 
password has always worked fine until now. Possibly Ubuntu has patched 
the sudologin but should LMDE? And jessie? I do not think so.


Hope someone can find something significant in this and give a hint on 
what to do.

Kaj

[toc] | [prev] | [next] | [standalone]

#183457 — Re: How to gain control over the system? [a security-side-note]

On Sunday, 9 July 2017 14:54:02 -04 Kaj Persson wrote:
> Thank you all for thoughts and viewpoints on what can be wrong in my
> installation of Debian 9. I have looked through places I might expect
> can contain some explanation, but so far I have not been able to exclaim
> an "Ah, that's it!". Here are some of my observations:
> 
> * First source of install: Well, I do know I wrote that used the live
> image, but to be honest, for now I am not sure, I do not remember. I had
> downloaded the live image as well as the install image, and most
> probable choice would be the later. But I do not know. Anyway the
> install process itself went without any problems.
> 
> * At the install I made it fully new from the bottom. The only directory
> I kept unchanged was my home directory. This is situated on an own
> partition. All the others were reformatted: /, /boot, /usr, /var and
> /tmp. All these are on individual partitions while e.g. /etc is
> contained in the root partition. At earlier installations I have noticed
> that the home directory can contain wrong configuration files, so as a
> test I moved all hidden files i.e. files starting with a dot to a new
> created directory "hidden". This was however after the install. So at a
> subsequent cold start the system had no configuration files there but
> created new ones with default values. This however had no positive
> impact on my problem.
> 
> * Configuring sudo? No I have not done that explicitly, not more than
> what the install program did itself. I have looked at /etc/sudoers and
> what I think the important lines are:
> 
>      # User privilege specification
>      root    ALL=(ALL:ALL) ALL
> 
>      # Allow members of group sudo to execute any command
>      %sudo   ALL=(ALL:ALL) ALL
There the "security" went out of the building ...
Please have a look here:
https://blather.michaelwlucas.com/archives/2266
> 
>      #includedir /etc/sudoers.d
> 
> In /etc/sudoers.d there are no more files than README.
> 
> There is no /etc/sudo.conf file.
> 
> * Regarding access to my user directory: During my search I did in fact
> find some files and directories owned by user root or group root. These
> are changed to be owned by my user id and group id, but this did not
> help. By the way, On this computer I have always had just one user,
> mine, and hence got the user id 1000 and group id 1000. This is the case
> now too.
> 
> uid 1000 is a member of the sudo group.
> 
> * As I wrote I have always used this method of not setting any password
> to the root account, and this is for quite many years now. My Linux path
> has gone via Ubuntu, well to be honest a couple of years after the
> Microsoft era I ran in Suse, but was not fully satisfied. And when
> Ubuntu and Canonical introduced Unity, I left that ship for Linux Mint
> Debian edition (LMDE) until I took the last(?) step into Debian a couple
> of years ago where the entrance point was jessie. The empty root
> password has always worked fine until now. Possibly Ubuntu has patched
> the sudologin but should LMDE? And jessie? I do not think so.
> 
I didn't try this myself (didn't ever have to) but this might help for now:
https://unix.stackexchange.com/questions/205799/how-to-create-root-user-account-in-debian
> 
> Hope someone can find something significant in this and give a hint on
> what to do.
I'd first try to go through the installation with the netinstall and without 
reusing any home partition in a virtual machine. See if the problem is there 
too.
If yes: place a bug-report.
If not: take a snapshot for later
put back the home partition, see if the problem is there or not.
If yes: restore the snapshot. And start putting back the config files for LMDE.
...
gradually testing out what can be reused and what not.
...
on second thought: I wouldn't invest the time ...
If the install in the virtual machine is doing allright, I'd just do the exact 
same install on the real hardware and be happy.
Have a nice day
Eike

[toc] | [prev] | [next] | [standalone]

#183458 — Re: How to gain control over the system? [a security-side-note]

On 09-07-17, Eike Lantzsch wrote:
> On Sunday, 9 July 2017 14:54:02 -04 Kaj Persson wrote:
> > 
> > * Configuring sudo? No I have not done that explicitly, not more than
> > what the install program did itself. I have looked at /etc/sudoers and
> > what I think the important lines are:
> > 
> >      # User privilege specification
> >      root    ALL=(ALL:ALL) ALL
> > 
> >      # Allow members of group sudo to execute any command
> >      %sudo   ALL=(ALL:ALL) ALL
> There the "security" went out of the building ...
> Please have a look here:
> https://blather.michaelwlucas.com/archives/2266

It does not matter really ( though it is really nice lecture about sudo
), because it is personal machine. Settings like that on personal
machine are really fine. 

> > 
> >      #includedir /etc/sudoers.d
> > 
> > In /etc/sudoers.d there are no more files than README.
> > 

[toc] | [prev] | [next] | [standalone]

#183464

[Multipart message — attachments visible in raw view] — view raw

Again, did you copy your /home from a previous system or is it a new
configuration that locked your panels?

> UTC Time: July 9, 2017 12:54 PM
> From: 70147persson@telia.com
> To: debian-user@lists.debian.org
> Thank you all for thoughts and viewpoints on what can be wrong in my
> installation of Debian 9. I have looked through places I might expect
> can contain some explanation, but so far I have not been able to exclaim
> an "Ah, that"s it!". Here are some of my observations:
> * First source of install: Well, I do know I wrote that used the live
> image, but to be honest, for now I am not sure, I do not remember. I had
> downloaded the live image as well as the install image, and most
> probable choice would be the later. But I do not know. Anyway the
> install process itself went without any problems.
> * At the install I made it fully new from the bottom. The only directory
> I kept unchanged was my home directory. This is situated on an own
> partition. All the others were reformatted: /, /boot, /usr, /var and
> /tmp. All these are on individual partitions while e.g. /etc is
> contained in the root partition. At earlier installations I have noticed
> that the home directory can contain wrong configuration files, so as a
> test I moved all hidden files i.e. files starting with a dot to a new
> created directory "hidden". This was however after the install. So at a
> subsequent cold start the system had no configuration files there but
> created new ones with default values. This however had no positive
> impact on my problem.
> * Configuring sudo? No I have not done that explicitly, not more than
> what the install program did itself. I have looked at /etc/sudoers and
> what I think the important lines are:
> # User privilege specification
> root ALL=(ALL:ALL) ALL
> # Allow members of group sudo to execute any command
> %sudo ALL=(ALL:ALL) ALL
> #includedir /etc/sudoers.d
> In /etc/sudoers.d there are no more files than README.
> There is no /etc/sudo.conf file.
> * Regarding access to my user directory: During my search I did in fact
> find some files and directories owned by user root or group root. These
> are changed to be owned by my user id and group id, but this did not
> help. By the way, On this computer I have always had just one user,
> mine, and hence got the user id 1000 and group id 1000. This is the case
> now too.
> uid 1000 is a member of the sudo group.
> * As I wrote I have always used this method of not setting any password
> to the root account, and this is for quite many years now. My Linux path
> has gone via Ubuntu, well to be honest a couple of years after the
> Microsoft era I ran in Suse, but was not fully satisfied. And when
> Ubuntu and Canonical introduced Unity, I left that ship for Linux Mint
> Debian edition (LMDE) until I took the last(?) step into Debian a couple
> of years ago where the entrance point was jessie. The empty root
> password has always worked fine until now. Possibly Ubuntu has patched
> the sudologin but should LMDE? And jessie? I do not think so.
> Hope someone can find something significant in this and give a hint on
> what to do.
> Kaj

[toc] | [prev] | [next] | [standalone]

#183465

[Multipart message — attachments visible in raw view] — view raw

Well, as I wrote my /home is an own partition, and so it has been for a 
long time. So it is not a new copy but a new mount. Certainly it 
therefore contains old config files that maybe ought to be removed. But 
on the other hand almost all of them are reused, since many  of them 
belong to applications which I want to install also in the new system.

Also, as I wrote, I did a test by moving all these config files into a 
new directory "hidden", itself not hidden despite the name, inside the 
home directory (and partition).
/Kaj


On 2017-07-09 at 15:38, Fungi4All wrote:
> Again, did you copy your /home from a previous system or is it a new
> configuration that locked your panels?
>
>> UTC Time: July 9, 2017 12:54 PM
>> From: 70147persson@telia.com
>> To: debian-user@lists.debian.org
>>
>> Thank you all for thoughts and viewpoints on what can be wrong in my
>> installation of Debian 9. I have looked through places I might expect
>> can contain some explanation, but so far I have not been able to exclaim
>> an "Ah, that"s it!". Here are some of my observations:
>>
>> * First source of install: Well, I do know I wrote that used the live
>> image, but to be honest, for now I am not sure, I do not remember. I had
>> downloaded the live image as well as the install image, and most
>> probable choice would be the later. But I do not know. Anyway the
>> install process itself went without any problems.
>>
>> * At the install I made it fully new from the bottom. The only directory
>> I kept unchanged was my home directory. This is situated on an own
>> partition. All the others were reformatted: /, /boot, /usr, /var and
>> /tmp. All these are on individual partitions while e.g. /etc is
>> contained in the root partition. At earlier installations I have noticed
>> that the home directory can contain wrong configuration files, so as a
>> test I moved all hidden files i.e. files starting with a dot to a new
>> created directory "hidden". This was however after the install. So at a
>> subsequent cold start the system had no configuration files there but
>> created new ones with default values. This however had no positive
>> impact on my problem.
>>
>> * Configuring sudo? No I have not done that explicitly, not more than
>> what the install program did itself. I have looked at /etc/sudoers and
>> what I think the important lines are:
>>
>> # User privilege specification
>> root ALL=(ALL:ALL) ALL
>>
>> # Allow members of group sudo to execute any command
>> %sudo ALL=(ALL:ALL) ALL
>>
>> #includedir /etc/sudoers.d
>>
>> In /etc/sudoers.d there are no more files than README.
>>
>> There is no /etc/sudo.conf file.
>>
>> * Regarding access to my user directory: During my search I did in fact
>> find some files and directories owned by user root or group root. These
>> are changed to be owned by my user id and group id, but this did not
>> help. By the way, On this computer I have always had just one user,
>> mine, and hence got the user id 1000 and group id 1000. This is the case
>> now too.
>>
>> uid 1000 is a member of the sudo group.
>>
>> * As I wrote I have always used this method of not setting any password
>> to the root account, and this is for quite many years now. My Linux path
>> has gone via Ubuntu, well to be honest a couple of years after the
>> Microsoft era I ran in Suse, but was not fully satisfied. And when
>> Ubuntu and Canonical introduced Unity, I left that ship for Linux Mint
>> Debian edition (LMDE) until I took the last(?) step into Debian a couple
>> of years ago where the entrance point was jessie. The empty root
>> password has always worked fine until now. Possibly Ubuntu has patched
>> the sudologin but should LMDE? And jessie? I do not think so.
>>
>>
>> Hope someone can find something significant in this and give a hint on
>> what to do.
>>
>> Kaj
>>
>>
>>
>

[toc] | [prev] | [next] | [standalone]

#183476

[Multipart message — attachments visible in raw view] — view raw

Yes, a good try, but ...
Owner and group for /home is root resp. root,
and for /home/cookoo (to use your example) is the correct user name 
resp. group.
I have also looked one level further, hence /home/cookoo/subdir/, and 
all directories on this level have the same ownership (=user name - group).

Thank you for your efforts to help.
/Kaj


On 2017-07-09 at 19:21, Fungi4All wrote:
> I am interested in the owner of the file structure of /home/user
> Let's say your username is cookoo  Is the owner of
> and its subdirectories and contents also cookoo?
> With your filemanager r-click properties and permissions to see owner
> and file access rights.  If you see a number like 1008 instead of the
> username that is the problem.
>
>> From: 70147persson@telia.com
>> To: debian-user@lists.debian.org
>>
>>
>> Well, as I wrote my /home is an own partition, and so it has been for 
>> a long time. So it is not a new copy but a new mount. Certainly it 
>> therefore contains old config files that maybe ought to be removed. 
>> But on the other hand almost all of them are reused, since many  of 
>> them belong to applications which I want to install also in the new 
>> system.
>>
>> Also, as I wrote, I did a test by moving all these config files into 
>> a new directory "hidden", itself not hidden despite the name, inside 
>> the home directory (and partition).
>> /Kaj
>>
>>
>> On 2017-07-09 at 15:38, Fungi4All wrote:
>>> Again, did you copy your /home from a previous system or is it a new
>>> configuration that locked your panels?
>>>
>>>> UTC Time: July 9, 2017 12:54 PM
>>>> From: 70147persson@telia.com
>>>> To: debian-user@lists.debian.org
>>>>
>>>> Thank you all for thoughts and viewpoints on what can be wrong in my
>>>> installation of Debian 9. I have looked through places I might expect
>>>> can contain some explanation, but so far I have not been able to 
>>>> exclaim
>>>> an "Ah, that"s it!". Here are some of my observations:
>>>>
>>>> * First source of install: Well, I do know I wrote that used the live
>>>> image, but to be honest, for now I am not sure, I do not remember. 
>>>> I had
>>>> downloaded the live image as well as the install image, and most
>>>> probable choice would be the later. But I do not know. Anyway the
>>>> install process itself went without any problems.
>>>>
>>>> * At the install I made it fully new from the bottom. The only 
>>>> directory
>>>> I kept unchanged was my home directory. This is situated on an own
>>>> partition. All the others were reformatted: /, /boot, /usr, /var and
>>>> /tmp. All these are on individual partitions while e.g. /etc is
>>>> contained in the root partition. At earlier installations I have 
>>>> noticed
>>>> that the home directory can contain wrong configuration files, so as a
>>>> test I moved all hidden files i.e. files starting with a dot to a new
>>>> created directory "hidden". This was however after the install. So 
>>>> at a
>>>> subsequent cold start the system had no configuration files there but
>>>> created new ones with default values. This however had no positive
>>>> impact on my problem.
>>>>
>>>> * Configuring sudo? No I have not done that explicitly, not more than
>>>> what the install program did itself. I have looked at /etc/sudoers and
>>>> what I think the important lines are:
>>>>
>>>> # User privilege specification
>>>> root ALL=(ALL:ALL) ALL
>>>>
>>>> # Allow members of group sudo to execute any command
>>>> %sudo ALL=(ALL:ALL) ALL
>>>>
>>>> #includedir /etc/sudoers.d
>>>>
>>>> In /etc/sudoers.d there are no more files than README.
>>>>
>>>> There is no /etc/sudo.conf file.
>>>>
>>>> * Regarding access to my user directory: During my search I did in 
>>>> fact
>>>> find some files and directories owned by user root or group root. 
>>>> These
>>>> are changed to be owned by my user id and group id, but this did not
>>>> help. By the way, On this computer I have always had just one user,
>>>> mine, and hence got the user id 1000 and group id 1000. This is the 
>>>> case
>>>> now too.
>>>>
>>>> uid 1000 is a member of the sudo group.
>>>>
>>>> * As I wrote I have always used this method of not setting any 
>>>> password
>>>> to the root account, and this is for quite many years now. My Linux 
>>>> path
>>>> has gone via Ubuntu, well to be honest a couple of years after the
>>>> Microsoft era I ran in Suse, but was not fully satisfied. And when
>>>> Ubuntu and Canonical introduced Unity, I left that ship for Linux Mint
>>>> Debian edition (LMDE) until I took the last(?) step into Debian a 
>>>> couple
>>>> of years ago where the entrance point was jessie. The empty root
>>>> password has always worked fine until now. Possibly Ubuntu has patched
>>>> the sudologin but should LMDE? And jessie? I do not think so.
>>>>
>>>>
>>>> Hope someone can find something significant in this and give a hint on
>>>> what to do.
>>>>
>>>> Kaj
>>>>
>>>>
>>>>
>>>
>>
>

[toc] | [prev] | [next] | [standalone]

#183480

Kaj Persson composed on 2017-07-09 14:54 (UTC+0200):

> * Regarding access to my user directory: During my search I did in fact 
> find some files and directories owned by user root or group root. These 
> are changed to be owned by my user id and group id, but this did not 
> help. By the way, On this computer I have always had just one user, 
> mine, and hence got the user id 1000 and group id 1000. This is the case 
> now too.
Are you 100% sure you found and corrected 100% of bad ones? Does 1000:1000 own
$HOME? X session settings not saved is virtually always bad file permissions or
errant ownership. Anything that got stolen by root:root via errant sudo or su
will almost certainly have to be fixed as root, exception being via a
superwizard who would unlikely ever have gotten into this trouble in the first
place.

You really don't need to hunt for any that are bad unless you care to know which
are causing the trouble. Simply do as root:

	chown -R 1000:1000 /home/kaj/

using whatever your actual username is rather than kaj.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#183574

On 2017-07-10 at 01:36, Felix Miata wrote:
> Kaj Persson composed on 2017-07-09 14:54 (UTC+0200):
>
>> * Regarding access to my user directory: During my search I did in fact
>> find some files and directories owned by user root or group root. These
>> are changed to be owned by my user id and group id, but this did not
>> help. By the way, On this computer I have always had just one user,
>> mine, and hence got the user id 1000 and group id 1000. This is the case
>> now too.
> Are you 100% sure you found and corrected 100% of bad ones? Does 1000:1000 own
> $HOME? X session settings not saved is virtually always bad file permissions or
> errant ownership. Anything that got stolen by root:root via errant sudo or su
> will almost certainly have to be fixed as root, exception being via a
> superwizard who would unlikely ever have gotten into this trouble in the first
> place.
>
> You really don't need to hunt for any that are bad unless you care to know which
> are causing the trouble. Simply do as root:
>
> 	chown -R 1000:1000 /home/kaj/
>
> using whatever your actual username is rather than kaj.

Yes, I think so. Shouldn't I?

All the commands in the following are given as user root.
This is the output from the command
ls -Al /home:

drwxr-xr-x 39 kaj  kaj  16384 jul 11 17:23 kaj
drwx------  2 root root 16384 sep 28  2016 lost+found
drwx------  4 root root  4096 okt 26  2016 .Trash-0

and from the command
tree -qpadxugL 2 /home:

/home
├── [drwxr-xr-x kaj      kaj     ]  kaj
│   ├── [drwx------ kaj      kaj     ]  .alsaplayer
│   ├── [drwxr-xr-x kaj      kaj     ]  Bilder
│   ├── [drwxr-xr-x kaj      kaj     ]  bin
│   ├── [drwx------ kaj      kaj     ]  .cache
│   ├── [drwxr-xr-x kaj      kaj     ]  .config
│   ├── [drwxrwx--- root     kaj     ]  DATA
│   ├── [drwxr-xr-x kaj      kaj     ]  Dokument
│   ├── [drwxr-xr-x kaj      kaj     ]  dwhelper
│   ├── [drwx------ kaj      kaj     ]  .gconf
│   ├── [drwx------ kaj      kaj     ]  .gnome2
│   ├── [drwx------ kaj      kaj     ]  .gnome2_private
│   ├── [drwx------ kaj      kaj     ]  .gnupg
│   ├── [drwxrwx--- root     kaj     ]  Hämtningar
│   ├── [drwx------ kaj      kaj     ]  .local
│   ├── [drwx------ kaj      kaj     ]  Mail
│   ├── [drwxr-xr-x kaj      kaj     ]  Mallar
│   ├── [drwx------ kaj      kaj     ]  .mozc
│   ├── [drwx------ kaj      kaj     ]  .mozilla
│   ├── [drwxrwx--- root     kaj     ]  Musik
│   ├── [drwxrwx--- root     kaj     ]  Nedladd
│   ├── [drwxr-xr-x kaj      kaj     ]  Publikt
│   ├── [drwxr-xr-x kaj      kaj     ]  Skrivbord
│   ├── [drwx------ kaj      kaj     ]  .thunderbird
│   ├── [drwxr-xr-x kaj      kaj     ]  Video
├── [drwx------ root     root    ]  lost+found
└── [drwx------ root     root    ]  .Trash-0
     ├── [drwx------ root     root    ]  files
     └── [drwx------ root     root    ]  info


and from
tree -qpadxugL 3 /home/kaj/.config:

/home/kaj/.config
├── [drwxr-xr-x kaj      kaj     ]  caja
│   └── [drwxr-xr-x kaj      kaj     ]  scripts
├── [drwx------ kaj      kaj     ]  enchant
├── [drwx------ kaj      kaj     ]  gtk-2.0
├── [drwx------ kaj      kaj     ]  gtk-3.0
├── [drwx------ kaj      kaj     ]  ibus
│   └── [drwx------ kaj      kaj     ]  bus
├── [drwxr-xr-x kaj      kaj     ]  libreoffice
│   └── [drwx------ kaj      kaj     ]  4
│       ├── [drwxr-xr-x kaj      kaj     ]  cache
│       └── [drwxr-xr-x kaj      kaj     ]  user
├── [drwx------ kaj      kaj     ]  mate
│   ├── [drwx------ kaj      kaj     ]  eom
│   └── [drwx------ kaj      kaj     ]  panel2.d
│       └── [drwx------ kaj      kaj     ]  default
├── [drwxr-xr-x kaj      kaj     ]  mate-session
│   └── [drwxr-xr-x kaj      kaj     ]  saved-session
├── [drwx------ kaj      kaj     ]  mc
├── [drwxr-xr-x kaj      kaj     ]  pluma
└── [drwxr-xr-x kaj      kaj     ]  rncbc.org


A few explanations:
The names are partly in Swedish, but you might never the less understand 
them, I think. "Hämtningar" and "Nedladd" is Swedish for "Downloads". 
Those few directories owned by user root and group kaj are mounted file 
systems (FAT32) containing only user data. I have removed a few lines 
regarding installed programmes.

I see nothing which gives me an idea of what is wrong. Are there any 
more files or directories to look at? In /etc perhaps?

/Kaj

[toc] | [prev] | [next] | [standalone]

#183576

On Tue 11 Jul 2017 at 22:29:45 (+0200), Kaj Persson wrote:
[...]
> I see nothing which gives me an idea of what is wrong. Are there any
> more files or directories to look at? In /etc perhaps?

I don't know whether this would be useful, but

# find / -mount -not -group 0 -exec ls -ld {} \; -o -not -user 0 -exec ls -ld {} \; | less

or

$ find ~ -mount -not -group 1000 -exec ls -ld {} \; -o -not -user 1000 -exec ls -ld {} \;

might be useful (where 1000 is the typical UID of the First User).
The latter would usually be expected to produce no output, the former
will produce some, depending on where /var, /tmp etc are mounted.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#183577

On Tue, Jul 11, 2017 at 03:54:21PM -0500, David Wright wrote:
> $ find ~ -mount -not -group 1000 -exec ls -ld {} \; -o -not -user 1000 -exec ls -ld {} \;

find ~ -mount \( ! -group 1000 -o ! -user 1000 \) -ls

(You could also use DeMorgan's laws to factor out the "!", but this
way seems a little clearer.)

[toc] | [prev] | [next] | [standalone]

#183580

Kaj Persson composed on 2017-07-11 22:29 (UTC+0200):
...
> ls -Al /home:

> drwxr-xr-x 39 kaj  kaj  16384 jul 11 17:23 kaj

OK...

> and from the command
> tree -qpadxugL 2 /home:

> /home
...
> │   ├── [drwxrwx--- root     kaj     ]  DATA
...
> │   ├── [drwxrwx--- root     kaj     ]  Hämtningar
...
> │   ├── [drwxrwx--- root     kaj     ]  Musik
> │   ├── [drwxrwx--- root     kaj     ]  Nedladd
...
Definitely not OK, making one wonder what lurks deeper or elsewhere.

> and from
> tree -qpadxugL 3 /home/kaj/.config:

OK only as deep as you went.

...
> I see nothing which gives me an idea of what is wrong. Are there any 
> more files or directories to look at? In /etc perhaps?

You're not done looking. Until you get all the way to the bottom, you can't know
what else is wrong. You apparently need depth of at least 3 in the other hidden
directories, at least 4 in .config, and probabliy 4 or more in all.

Again:

	chown -R 1000:1000 /home/kaj/

as root should fix them all. If it doesn't, chown would seem to be broken.

Maybe this in addition?

	chown -R 1000:1000 /home/kaj/.*


Try MC in fullscreen mode. That way every listing you can see will display
ownership.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#183599

On Tue, Jul 11, 2017 at 09:49:15PM -0400, Felix Miata wrote:
> Again:
> 
> 	chown -R 1000:1000 /home/kaj/
> 
> as root should fix them all. If it doesn't, chown would seem to be broken.

Looks correct.

> Maybe this in addition?
> 
> 	chown -R 1000:1000 /home/kaj/.*

No, NOT correct.  Do not do this.  .* will expand to .. which will mean
you end up chowning all of /home.

The chown -R rooted in /home/kaj will include all of the dot files,
so you don't need a second step at all.  Especially not this one.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web