gphoto2 only as root -

[poma]

On 24.01.2014 17:16, Bob Goodwin - Zuni, Virginia, USA wrote:
> On 23/01/14 17:26, poma wrote:
>> On 23.01.2014 22:14, poma wrote:
>>> On 22.01.2014 18:55, Bob Goodwin - Zuni, Virginia, USA wrote:
>>>> Now I have another problem where user  "bobg" is not authorized!
>>> …
>>>
>>> If I correctly understood,
>>> - systemd-204-18.fc19 - No problemos!
>>> - systemd-208-9.fc20 - Hi-ho Silver!
>>> plus,
>>> - Your way:
>>> multi-user.target -> 'startxfce4'
>>> - Standard way:
>>> graphical.target -> display-manager.service -> "Xfce Session"
> 
> Yes, I have been doing [from my notes]:
> 
> "2013-07-10 Fedora-19
> 
>    How do I change the default run level?
> 
> systemd uses symlinks to point to the default runlevel.  You have to 
> delete the existing symlink first before creating a new one
> 
>   rm /etc/systemd/system/default.target
> 
> Switch to runlevel 3 by default
>   ln -sf /lib/systemd/system/multi-user.target 
> /etc/systemd/system/default.target  "
> 
> I'm struggling with your explanation but not sure if you are suggesting 
> a fix or offering a few thoughts, in other words, I am still lost!
> 
> F-20 in the VM developed the same authorization symptoms after I made 
> the above change. Obviously I have created the problem. It has worked 
> until now. :-[
> 
> So, from the F-20 VM displaying the problem this is what I get:
> 
> [root at localhost bobg]# ll /etc/systemd/system/display-manager.service
> lrwxrwxrwx. 1 root root 35 Jan 23 16:25 
> /etc/systemd/system/display-manager.service -> 
> /usr/lib/systemd/system/gdm.service

1.
Log in

2.
Print the file name of the terminal:
$ tty
/dev/tty1

3.
Log in as root:
$ su -

4.
Set the default target to boot into:
# systemctl set-default multi-user.target

5.
Check the default target:
# systemctl get-default
multi-user.target

6.
If you haven't already,
Switch to/Start the multi-user.target(systemd) pka "runlevel 3" (SysV):
# systemctl isolate multi-user.target

7.
Make a copy of the 'startxfce4' script:
# cp /usr/bin/startxfce4 /usr/bin/startxfce4-from-non-graphical

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
8.
Edit the 'startxfce4-from-non-graphical' script:
at the end of the line 118, add the following expression:
" -- vt01"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

9.
The difference between these two scripts:
# diff /usr/bin/startxfce4 /usr/bin/startxfce4-from-non-graphical
118c118
<-   exec $prog /etc/xdg/xfce4/xinitrc $CLIENTRC $SERVERRC
---
->   exec $prog /etc/xdg/xfce4/xinitrc $CLIENTRC $SERVERRC -- vt01

10.
Log out from root

11.
Start the Xfce session:
$ startxfce4-from-non-graphical

12.
You are now logged in the Xfce session,
with a significant difference from before, …

$ loginctl list-sessions
   SESSION        UID USER             SEAT
         1       1000 poma             seat0

1 sessions listed.

Now (via 'startxfce4-from-non-graphical' script):
$ loginctl -p Active -p State show-session 1
Active=yes    <--
State=active  <--

Before (via 'startxfce4' script):
$ loginctl -p Active -p State show-session 1
Active=no     <--
State=online  <--

In this way you start the Xfce session outside the domain of the display
manager, like you did before and your concern regarding the handling of
authorization(polkit) should be resolved. ;)

Certain steps of the whole process can be done differently, but what is
certainly the most important, is the eighth(8.) step!


poma


In addition;

Essential elements of the configuration:
tty1 -> vt01
tty2 -> vt02
etc.

X - vtXX  use the specified VT number
i.e. use the "same" VT number as is the terminal you logged in(tty1).