Bug 23770 - After update blueman ask twice for root access, due missing polkit rule
Summary: After update blueman ask twice for root access, due missing polkit rule
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-27 20:20 CEST by katnatek
Modified: 2020-08-16 21:52 CEST (History)
4 users (show)

See Also:
Source RPM: blueman-2.0.6-1
CVE:
Status comment:


Attachments

Description katnatek 2018-10-27 20:20:55 CEST
Description of problem:

After update to blueman-2.0.6.1, blueman asks twice for authentication. First with the message "Networking requires privileges" and then with the message "Setting Rf Kill State requires privileges".

Version-Release number of selected component (if applicable):

blueman-2.0.6.1

How reproducible:


Steps to Reproduce:
1. If you are logged in , logout the sesion
2. Login in Xfce
3. blueman ask twice for root access

For workaround follow this indications https://www.linuxquestions.org/questions/fedora-35/blueman-requires-authentication-twice-when-logging-into-account-4175626708/#post5839201
Comment 1 Marja Van Waes 2018-10-27 21:20:36 CEST
Assigning to all packagers collectively, since there is no registered maintainer for this package.
CC'ing bcornec, who recently pushed blueman.

Assignee: bugsquad => pkg-bugs
CC: (none) => bruno, marja11
Source RPM: blueman => blueman-2.0.6-1

Comment 2 katnatek 2018-10-31 18:45:14 CET
Same report by other user in dev mail list
https://ml.mageia.org/l/arc/dev/2018-10/msg00366.html
katnatek 2018-11-09 19:43:59 CET

Keywords: (none) => IN_ERRATA6

Alain Choucroot 2018-11-21 20:12:21 CET

CC: (none) => choucroot

Comment 3 Aurelien Oudelet 2020-08-16 21:52:07 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.