HE to Jessie upgrade

Important informations about SolydXK including releases notes, forum rules and other anouncements
User avatar
Arjen Balfoort
Site Admin
Posts: 9422
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: HE to Jessie upgrade

Postby Arjen Balfoort » 22 Dec 2014 22:43

ulusu wrote:Just ran those upgrades on my production SolydK and SolydX 64bit.

With SolydK I had an issue because I had systemd starting from the kernel line in /etc/default/grub and at the first boot the system hanged. After booting into an older kernel I edited /etc/default/grub and off it went.

Both systems are running without any problems.

Regards,
ulusu
How was that line in grub looking and would one have to remove the systemd part from that line before upgrading?


SolydXK needs you!
Development | Testing | Translations

User avatar
ulusu
Posts: 82
Joined: 12 Nov 2013 23:06
Location: Dreiländereck (Germany, Luxemburg and France)

Re: HE to Jessie upgrade

Postby ulusu » 08 Jan 2015 04:05

With SolydK I had an issue because I had systemd starting from the kernel line in /etc/default/grub

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash init=/bin/systemd"
and at the first boot the system hanged.

After booting into an older kernel I edited /etc/default/grub and took out the systemd part. From there on everything worked normaly.

Regards,
ulusu

Mac OS X Mavericks, Kubuntu 14.04 LTS, SolydK64_201407, Windows 7 Ultimate, Windows 8.1 pro

User avatar
palimmo
Posts: 824
Joined: 19 Nov 2013 19:44
Contact:

Re: HE to Jessie upgrade

Postby palimmo » 10 Jan 2015 11:24

I did a few hours ago the upgrade (SolydK 64bit HE to Jessie).
It took long time. But everything went smooth and perfect ;)

Just one thing: in order to boot, I have to edit (e) the grub entry and remove the splash term.
How can I edit it permanently, avoiding to do to it at each boot?
Editing this
sudo kate /etc/default/grub
will affect each entry of grub? Not only SolydK64?


Thanks!
Proud user of SolydK!

Dai diamanti non nasce niente, dal letame nascono i fior. http://aquilone.wordpress.com/

c.monty
Posts: 58
Joined: 10 Dec 2013 01:11

[moved] root authorization required for shutdown, scanner,

Postby c.monty » 10 Jan 2015 11:53

Hello!

Since the latest upgrade in combination with migration to systemd the usage of the system is very limited.
This means, only users with root authorization are allowed to

Code: Select all

user@pc1-asus:~$ inxi -Fxz
System:    Host: pc1-asus Kernel: 3.16-2-686-pae i686 (32 bit gcc: 4.8.3) 
           Console: tty 2 Distro: SolydXK 1 solydxk 
Machine:   Mobo: ASUSTeK model: A7N8X2.0 v: REV 2.xx
           Bios: Phoenix v: ASUS A7N8X2.0 Deluxe Rev 1007 date: 10/06/2003
CPU:       Single core AMD Athlon XP 2600+ (-UP-) cache: 512 KB
           flags: (pae sse) bmips: 3826 clocked at 1913 MHz
Graphics:  Card: NVIDIA NV15 [GeForce2 GTS/Pro] bus-ID: 03:00.0
           Display Server: X.org 1.16.2.901 driver: nouveau
           tty size: 80x32 Advanced Data: N/A out of X
Audio:     Card-1 NVIDIA nForce2 AC97 Audio Controler (MCP) 
           driver: snd_intel8x0 ports: d000 d400 bus-ID: 00:06.0 
           Card-2 NVIDIA nForce Audio Processing Unit bus-ID: 00:05.0 
           Sound: Advanced Linux Sound Architecture v: k3.16-2-686-pae
Network:   Card-1: 3Com 3C920B-EMB Integrated Fast Ethernet Controller [Tornado]
           driver: 3c59x port: c000 bus-ID: 02:01.0
           IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: <filter>
           Card-2: AVM Fritz!PCI v2.0 ISDN
           driver: fcpci port: a000 bus-ID: 01:07.0
           IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
           Card-3: NVIDIA nForce2 Ethernet Controller
           driver: forcedeth port: e400 bus-ID: 00:04.0
           IF: eth1 state: down mac: <filter>
Drives:    HDD Total Size: 250.1GB (11.6% used)
           ID-1: /dev/sda model: SAMSUNG_SP2514N size: 250.1GB temp: 30C
Partition: ID-1: / size: 114G used: 15G (14%) fs: ext4 dev: /dev/sda5 
           ID-2: /boot size: 97M used: 38M (41%) fs: ext2 dev: /dev/sda1 
           ID-3: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda6 
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 157 Uptime: 1:05 Memory: 488.8/1515.7MB 
           Init: systemd runlevel: 5 Gcc sys: 4.9.1 
           Client: Shell (bash 4.3.301) inxi: 2.1.28 

Code: Select all

user@pc1-asus:~$ systemctl status udev
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
   Active: active (running) since Fr 2015-01-09 19:49:52 CET; 1h 3min ago
     Docs: man:systemd-udevd.service(8)
           man:udev(7)
 Main PID: 172 (systemd-udevd)
   CGroup: /system.slice/systemd-udevd.service
           └─172 /lib/systemd/systemd-udevd

Jan 09 19:49:52 pc1-asus systemd-udevd[172]: Network interface NamePolicy= d....
Jan 09 19:49:55 pc1-asus mtp-probe[260]: checking bus 2, device 2: "/sys/dev..."
Jan 09 19:49:55 pc1-asus mtp-probe[260]: bus: 2, device: 2 was not an MTP device
Hint: Some lines were ellipsized, use -l to show in full.

Code: Select all

user@pc1-asus:~$ sudo journalctl -a -x |grep udev
Jan 09 19:03:49 pc1-asus systemd-udevd[53]: starting version 215
Jan 09 19:03:49 pc1-asus kernel: random: systemd-udevd urandom read with 0 bits of entropy available
Jan 09 19:03:49 pc1-asus systemd-udevd[171]: starting version 215
Jan 09 19:03:49 pc1-asus systemd-udevd[171]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Jan 09 19:49:51 pc1-asus systemd-udevd[53]: starting version 215
Jan 09 19:49:51 pc1-asus kernel: random: systemd-udevd urandom read with 0 bits of entropy available
Jan 09 19:49:52 pc1-asus systemd-udevd[172]: starting version 215
Jan 09 19:49:52 pc1-asus systemd-udevd[172]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Based on my analyzes I come to the conclusion regarding the root cause: missing authorization
This all occurs for any user account w/o root permission.

After adding this user account to group "sudo" I can fix all problems by executing all commands with root permission, means e.g.

Code: Select all

sudo nmcli connection up uuid <uuid>
sudo simple-scan
sudo scanimage -L
device `plustek:libusb:003:002' is a Canon CanoScan N670U/N676U/LiDE20 flatbed scanner
etc.

This raises the question:
How can I fix the issue?
I don't intend to give all user account root permission, because this was not required before the upgrade.

THX

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: root authorization required for shutdown, scanner, VPN,

Postby Zill » 10 Jan 2015 12:22

I understand that the OP is using the new sources.list for Jessie, rather than the standard SolydXK sources.list. As such, I suggest that this post is moved to the "HE to Jessie upgrade" thread.

c.monty
Posts: 58
Joined: 10 Dec 2013 01:11

Re: root authorization required for shutdown, scanner, VPN,

Postby c.monty » 10 Jan 2015 12:39

Well... I agree that this could be related to Jessie, however comparable issues occured with previous debian-based releases, too.

I'm convident that the root cause is related to PolicyKit Local Authority that is documented here http://www.freedesktop.org/software/pol ... ity.8.html.

Any support to fix this is highly appreciated.

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: root authorization required for shutdown, scanner, VPN,

Postby Zill » 10 Jan 2015 12:50

c.monty wrote:Well... I agree that this could be related to Jessie, however comparable issues occured with previous debian-based releases, too...
My point is simply that this problem does not appear to exist with a "normal" SolydXK HE installation using the standard SolydXK repos. Your post indicates that you have only experienced this since upgrading to the Jessie development repos.

c.monty
Posts: 58
Joined: 10 Dec 2013 01:11

Re: root authorization required for shutdown, scanner, VPN,

Postby c.monty » 10 Jan 2015 13:00

Agree... how can I move the post to the best suitable thread?
Or should I simply copy and paste?

c.monty
Posts: 58
Joined: 10 Dec 2013 01:11

Re: HE to Jessie upgrade

Postby c.monty » 10 Jan 2015 13:03

root authorization required for shutdown, scanner, VPN, etc.

Hello!

Since the latest upgrade in combination with migration to systemd the usage of the system is very limited.
This means, only users with root authorization are allowed to

Code: Select all

user@pc1-asus:~$ inxi -Fxz
System:    Host: pc1-asus Kernel: 3.16-2-686-pae i686 (32 bit gcc: 4.8.3) 
           Console: tty 2 Distro: SolydXK 1 solydxk 
Machine:   Mobo: ASUSTeK model: A7N8X2.0 v: REV 2.xx
           Bios: Phoenix v: ASUS A7N8X2.0 Deluxe Rev 1007 date: 10/06/2003
CPU:       Single core AMD Athlon XP 2600+ (-UP-) cache: 512 KB
           flags: (pae sse) bmips: 3826 clocked at 1913 MHz
Graphics:  Card: NVIDIA NV15 [GeForce2 GTS/Pro] bus-ID: 03:00.0
           Display Server: X.org 1.16.2.901 driver: nouveau
           tty size: 80x32 Advanced Data: N/A out of X
Audio:     Card-1 NVIDIA nForce2 AC97 Audio Controler (MCP) 
           driver: snd_intel8x0 ports: d000 d400 bus-ID: 00:06.0 
           Card-2 NVIDIA nForce Audio Processing Unit bus-ID: 00:05.0 
           Sound: Advanced Linux Sound Architecture v: k3.16-2-686-pae
Network:   Card-1: 3Com 3C920B-EMB Integrated Fast Ethernet Controller [Tornado]
           driver: 3c59x port: c000 bus-ID: 02:01.0
           IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: <filter>
           Card-2: AVM Fritz!PCI v2.0 ISDN
           driver: fcpci port: a000 bus-ID: 01:07.0
           IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
           Card-3: NVIDIA nForce2 Ethernet Controller
           driver: forcedeth port: e400 bus-ID: 00:04.0
           IF: eth1 state: down mac: <filter>
Drives:    HDD Total Size: 250.1GB (11.6% used)
           ID-1: /dev/sda model: SAMSUNG_SP2514N size: 250.1GB temp: 30C
Partition: ID-1: / size: 114G used: 15G (14%) fs: ext4 dev: /dev/sda5 
           ID-2: /boot size: 97M used: 38M (41%) fs: ext2 dev: /dev/sda1 
           ID-3: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda6 
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 157 Uptime: 1:05 Memory: 488.8/1515.7MB 
           Init: systemd runlevel: 5 Gcc sys: 4.9.1 
           Client: Shell (bash 4.3.301) inxi: 2.1.28 

Code: Select all

user@pc1-asus:~$ systemctl status udev
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
   Active: active (running) since Fr 2015-01-09 19:49:52 CET; 1h 3min ago
     Docs: man:systemd-udevd.service(8)
           man:udev(7)
 Main PID: 172 (systemd-udevd)
   CGroup: /system.slice/systemd-udevd.service
           └─172 /lib/systemd/systemd-udevd

Jan 09 19:49:52 pc1-asus systemd-udevd[172]: Network interface NamePolicy= d....
Jan 09 19:49:55 pc1-asus mtp-probe[260]: checking bus 2, device 2: "/sys/dev..."
Jan 09 19:49:55 pc1-asus mtp-probe[260]: bus: 2, device: 2 was not an MTP device
Hint: Some lines were ellipsized, use -l to show in full.

Code: Select all

user@pc1-asus:~$ sudo journalctl -a -x |grep udev
Jan 09 19:03:49 pc1-asus systemd-udevd[53]: starting version 215
Jan 09 19:03:49 pc1-asus kernel: random: systemd-udevd urandom read with 0 bits of entropy available
Jan 09 19:03:49 pc1-asus systemd-udevd[171]: starting version 215
Jan 09 19:03:49 pc1-asus systemd-udevd[171]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Jan 09 19:49:51 pc1-asus systemd-udevd[53]: starting version 215
Jan 09 19:49:51 pc1-asus kernel: random: systemd-udevd urandom read with 0 bits of entropy available
Jan 09 19:49:52 pc1-asus systemd-udevd[172]: starting version 215
Jan 09 19:49:52 pc1-asus systemd-udevd[172]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Based on my analyzes I come to the conclusion regarding the root cause: missing authorization
This all occurs for any user account w/o root permission.

After adding this user account to group "sudo" I can fix all problems by executing all commands with root permission, means e.g.

Code: Select all

sudo nmcli connection up uuid <uuid>
sudo simple-scan
sudo scanimage -L
device `plustek:libusb:003:002' is a Canon CanoScan N670U/N676U/LiDE20 flatbed scanner
etc.

This raises the question:
How can I fix the issue?
I don't intend to give all user account root permission, because this was not required before the upgrade.

I think that the root cause is related to PolicyKit Local Authority that is documented here http://www.freedesktop.org/software/pol ... ity.8.html.

Any support to fix this is highly appreciated.

THX

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: [moved] root authorization required for shutdown, scanne

Postby Zill » 10 Jan 2015 13:07

No need to do anything. I am sure Schoelje will move it if appropriate.

c.monty
Posts: 58
Joined: 10 Dec 2013 01:11

Re: HE to Jessie upgrade

Postby c.monty » 10 Jan 2015 14:02

Update:
I fixed the issue with shutdown / reboot executed by unprivileged user.

The issue is related to PolicyKit Local Authority, and in this case to file

Code: Select all

/usr/share/polkit-1/actions/org.freedesktop.login1.policy


The attached screenshot document the root cause.

I created the following file to adapt to this policy:

Code: Select all

pc1-asus  # cat /etc/polkit-1/localauthority/50-local.d/98-usershutdown.pkla 
[Allow Shutdown]
Identity=unix-user:*
Action=org.freedesktop.login1.power-off-multiple-sessions
ResultAny=yes
ResultInactive=yes
ResultActive=yes

[Allow Restart]
Identity=unix-user:*
Action=org.freedesktop.login1.reboot-multiple-sessions
ResultAny=yes
ResultInactive=yes
ResultActive=yes
So, I think this confirmes my assumption of the root cause related to PolicyKit Local Authority.
Now, I need to fix the other issues
  • - automount USB stick
    - using USB scanner
    - using NetworkManager
Any support to fix these issues is highly appreciated.
The challenge now is to identify the relevant policy for the above listed issues.
Attachments
Auswahl_053.png
Reboot
Auswahl_052.png
Shutdown

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: HE to Jessie upgrade

Postby Zill » 10 Jan 2015 16:29

c.monty: FWIW, my standard SolydX HE installation has the following two files in "/etc/polkit-1/localauthority/50-local.d/":

Code: Select all

dino 50-local.d # ls -l
-rw-r--r-- 1 root root 166 Jul 16 07:45 90-configure-printers.pkla
-rw-r--r-- 1 root root 385 Jul 16 07:45 99-mount-partitions.pkla
File contents are as follows:

Code: Select all

dino 50-local.d # cat 90-configure-printers.pkla 
[Password-less configuration of printers]
Identity=unix-group:lpadmin
Action=org.opensuse.cupspkhelper.mechanism.*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

----------------------------------------------------------------------

dino 50-local.d # cat 99-mount-partitions.pkla 
[Password-less mounting of local partitions]
Identity=unix-group:users
Action=org.freedesktop.udisks2.filesystem-mount-system
ResultAny=yes
ResultInactive=yes
ResultActive=yes

Action=org.freedesktop.udisks2.filesystem-mount
ResultAny=yes
ResultInactive=yes
ResultActive=yes

Action=org.freedesktop.udisks2.filesystem-mount-other-seat
ResultAny=yes
ResultInactive=yes
ResultActive=yes
Hope this helps!

c.monty
Posts: 58
Joined: 10 Dec 2013 01:11

Re: HE to Jessie upgrade

Postby c.monty » 10 Jan 2015 16:44

Confirmed... I have the same files in
/etc/polkit-1/localauthority/50-local.d/
plus the recently created 98-usershutdown.pkla.

The content of files
90-configure-printers.pkla
99-mount-partitions.pkla
is the same.

There's a question regarding 99-mount-partitions.pkla though:
Identity=unix-group:users
defines that this rule applies for users that are member of group "users".
However, none of the user account is a member of "users".

Did you check if automount works with your installation with a user account that has no root privileges?

THX

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: HE to Jessie upgrade

Postby Zill » 10 Jan 2015 17:46

c.monty wrote:There's a question regarding 99-mount-partitions.pkla though:
Identity=unix-group:users
defines that this rule applies for users that are member of group "users".
However, none of the user account is a member of "users".

Did you check if automount works with your installation with a user account that has no root privileges?
My users do have sudo privileges and, to assist file sharing, I also configure them to have a GID of 100, meaning that they are members of the "users" group. I don't have any "non-sudo" accounts on this system and do not really want to add new users as this is a working system.

User avatar
palimmo
Posts: 824
Joined: 19 Nov 2013 19:44
Contact:

Re: HE to Jessie upgrade

Postby palimmo » 10 Jan 2015 20:52

One question:
with the new system upgrated to Jessie should we still use

Code: Select all

sudo apt-get update && sudo apt-get dist-upgrade
or prefer

Code: Select all

sudo apt-get update && sudo apt-get upgrade
?
Proud user of SolydK!

Dai diamanti non nasce niente, dal letame nascono i fior. http://aquilone.wordpress.com/

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: HE to Jessie upgrade

Postby Zill » 11 Jan 2015 11:29

palimmo: You may get different opinions on this but, from my experience, I prefer to use "dist-upgrade", rather than "upgrade", for both static and (semi) rolling distributions. While "upgrade" should be suitable for static distros (such as the new SolydXK), I have sometimes had difficulty with certain packages (using other static distros) that could best be resolved by running "dist-upgrade". On this basis, "dist-upgrade" is my default choice unless I have specific reason to use only "upgrade". Of course, always fully monitor the process of upgrading to make sure you only get the changes you want! ;-)

From "man apt-get":
upgrade
upgrade is used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list. Packages currently installed with new versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. An update must be performed first so that apt-get knows that new versions of packages are available.

dist-upgrade
dist-upgrade in addition to performing the function of upgrade, also intelligently handles changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones if necessary. The dist-upgrade command may therefore remove some packages.

User avatar
palimmo
Posts: 824
Joined: 19 Nov 2013 19:44
Contact:

Re: HE to Jessie upgrade

Postby palimmo » 11 Jan 2015 11:39

thanks Zill.
So, if the user has any doubt, dist-upgrade is the best choice :D
Proud user of SolydK!

Dai diamanti non nasce niente, dal letame nascono i fior. http://aquilone.wordpress.com/

kurotsugi
Posts: 2260
Joined: 09 Jan 2014 00:17

Re: HE to Jessie upgrade

Postby kurotsugi » 13 Jan 2015 19:48

@ulusu: you can install systemd-sysv to avoid that issue. with the recent changes on systemd and debian systemd-sysv is mandatory if you want to use systemd.

@c.monty: if you really sure that it was polkit issue you can try to compare the content of /usr/share/polkit-1/actions with other system. here's mine https://www.dropbox.com/sh/gkazvl2o4fkr ... DLRjeLsnya

User avatar
MAYBL8
Posts: 1487
Joined: 10 Mar 2013 18:41
Location: Maryland Heights, MO USA
Contact:

Re: HE to Jessie upgrade

Postby MAYBL8 » 14 Jan 2015 14:21

Problem this morning.
Have a feeling I just need for it to solve itself.

Code: Select all

Fetched 145 kB in 1s (81.1 kB/s)
W: Failed to fetch http://packages.solydxk.com/testing/dists/solydxk/main/binary-i386/Packages  Hash Sum mismatch

E: Some index files failed to download. They have been ignored, or old ones used instead.
danc@danc-e535 ~ $ inxi -r
Repos:     Active apt sources in file: /etc/apt/sources.list
           deb http://packages.solydxk.com/testing/ solydxk main upstream import
           deb http://community.solydxk.com/testing/ solydxk main
           deb http://ftp.debian.org/debian testing main contrib non-free
           deb http://security.debian.org/ testing/updates main contrib non-free
           deb http://www.deb-multimedia.org testing main non-free
           deb-src http://ftp.us.debian.org/debian/ sid main
Update:
Yea I just needed to wait.
Ran it again and it updated some firefox and thunderbird packages and all is fine.


User avatar
ulusu
Posts: 82
Joined: 12 Nov 2013 23:06
Location: Dreiländereck (Germany, Luxemburg and France)

Re: HE to Jessie upgrade

Postby ulusu » 19 Jan 2015 22:19

kurotsugi wrote:@ulusu: you can install systemd-sysv to avoid that issue. with the recent changes on systemd and debian systemd-sysv is mandatory if you want to use systemd.
Thanks kurotsugi

I'll try this out.

Regards,
ulusu

Mac OS X Mavericks, Kubuntu 14.04 LTS, SolydK64_201407, Windows 7 Ultimate, Windows 8.1 pro


Return to “News & Anouncements”

Who is online

Users browsing this forum: No registered users and 3 guests