Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31634 - [polkit] Unable to login using GDM after upgrade to version 0.107-2

Attached to Project: Arch Linux
Opened by Smith Dhumbumroong (zodmaner) - Friday, 21 September 2012, 15:49 GMT
Last edited by Jan de Groot (JGC) - Monday, 21 April 2014, 15:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After upgraded polkit package from version 0.105-1 to 0.107-2, GDM fails to execute correctly and a user is unable to login.
Other display managers, such as SLiM, also has the same problem.

I have attached the section of the log file that I think contained the relevant information.

After I downgraded polkit package to version 0.105-1, I'm able to login once again.

Additional info:
* package version(s)
- polkit 0.107-2

* config and/or log files etc.


Steps to reproduce:
1. Upgrade polkit package to version 0.107-2
2. Try logging in to the system via a display manager
   snipped_everything.log (2.4 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 21 April 2014, 15:09 GMT
Reason for closing:  Won't fix
Additional comments about closing:  polkit user/group has been reserved in the developer wiki and will not be changed.

uids and gids below 1000 are for system usage, everything below 500 is for static allocation, everything between 500-1000 is for adduser/group --system.
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 19:54 GMT
I have found out that the cause of the problem is that the install script of the package failed to create the group "polkitd" because I already have the group with the same GID (102). Changing the group GID allows the install script to work properly and fix the problem.
Comment by Armin (armin) - Wednesday, 31 October 2012, 21:55 GMT
I triggered the same issue after a -Suy today, as the GID in polkit.install is explicitly set to 102, which in my case was already taken by another package (from the AUR, not that it's relevant unless Arch has a policy of reserved GID ranges that I don't know about)

Edit: this issue was raised in  FS#11589  before
Comment by Greg (dolby) - Wednesday, 31 October 2012, 21:58 GMT
https://wiki.archlinux.org/index.php/DeveloperWiki:UID_/_GID_Database
Comment by Armin (armin) - Wednesday, 31 October 2012, 22:17 GMT
Thanks Greg, I added a comment to that specific AUR package.

I guess this task can be closed as a wontfix :)

Edit: probably not, just checked my logs and found different messages from above. Might just be a coincidence.
Comment by Milos Kaurin (Kaurin) - Saturday, 03 November 2012, 10:19 GMT
Not sure if I have the same bug. XFCE/GDM here. I get the GDM shell. When I enter my password, and click "Log In", XFCE does not get loaded. I just get stuck on GDM with my username selected, password field gone, and only one option left: to click "Cancel". Trying again does not work. I have to restart gdm (systemctl restart gdm) from another tty.

If this is your problem, too. I will help with troubleshooting!
Comment by Greg (dolby) - Saturday, 17 November 2012, 14:38 GMT
If this was changed from 102 in  FS#11589  why was it reintroduced?
Comment by Jan de Groot (JGC) - Saturday, 17 November 2012, 15:00 GMT
Probably because policykit is not polkit...
Comment by Doug Newgard (Scimmia) - Monday, 30 September 2013, 09:09 GMT
Status? There have been a lot of changes in Arch/polkit/DMs since this was filed, I'm guessing it's no longer relevant?
Comment by Jan de Groot (JGC) - Monday, 30 September 2013, 09:23 GMT
The issue here is that we use a static gid/uid combination for polkit which could be used by others on the system they're installing on. When that issue is hit, polkit will be installed with incorrect permissions and won't work. This issue won't go away by itself and won't be "no longer relevant" until action is taken.
Comment by Doug Newgard (Scimmia) - Monday, 30 September 2013, 09:29 GMT
Ah, I misread what was going on. Sorry.

Loading...