Unpriviledge User --> Access Denied

Bug #1826674 reported by JP Lord
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Timekpr-nExT
Won't Fix
Undecided
Eduards Bezverhijs

Bug Description

Per the instructions, I added my user to the "timekpr" group, I logged off and back on again.

When using the regular launcher, the one for the active user, the status bar shows "Command FAILED: access denied" next to "Connected".

NOTE --> for this bug report and all the previous one, my configuration is:

System: Host: SRVJPLMTL Kernel: 4.15.0-47-generic x86_64 bits: 64 Desktop: Cinnamon 4.0.10 Distro: Linux Mint 19.1 Tessa
Machine: Type: Desktop Mobo: ASUSTeK model: P6T DELUXE v: Rev 1.xx serial: <root required> BIOS: American Megatrends v: 2209
           date: 09/21/2010
CPU: Topology: Quad Core model: Intel Core i7 920 bits: 64 type: MT MCP L2 cache: 8192 KiB
           Speed: 2531 MHz min/max: 1600/2668 MHz Core speeds (MHz): 1: 1614 2: 1623 3: 1649 4: 1680 5: 1668 6: 1621 7: 2554
           8: 1661
Graphics: Device-1: NVIDIA G94 [GeForce 9600 GT] driver: nouveau v: kernel
           Display: x11 server: X.Org 1.19.6 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
           OpenGL: renderer: NV94 v: 3.3 Mesa 18.2.8
Audio: Device-1: Creative Labs EMU10k2/CA0100/CA0102/CA10200 [Sound Blaster Audigy Series] driver: snd_emu10k1
           Sound Server: ALSA v: k4.15.0-47-generic
Network: Device-1: Marvell 88E8056 PCI-E Gigabit Ethernet driver: sky2
           IF: enp4s0 state: down mac: 00:24:8c:0a:b5:a5
           Device-2: Marvell 88E8056 PCI-E Gigabit Ethernet driver: sky2
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: 00:24:8c:0a:b5:a6
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
           IF-ID-2: tun1 state: unknown speed: 10 Mbps duplex: full mac: N/A
           IF-ID-3: vboxnet0 state: down mac: 0a:00:27:00:00:00
           IF-ID-4: vboxnet1 state: down mac: 0a:00:27:00:00:01
           IF-ID-5: vboxnet2 state: down mac: 0a:00:27:00:00:02
           IF-ID-6: vboxnet3 state: down mac: 0a:00:27:00:00:03
Drives: Local Storage: total: 6.37 TiB used: 2.72 TiB (42.8%)
           ID-1: /dev/sda vendor: Western Digital model: WD1001FALS-00J7B0 size: 931.51 GiB
           ID-2: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB
           ID-3: /dev/sdc type: USB vendor: Western Digital model: WD20EADS-11R6B1 size: 1.82 TiB
Partition: ID-1: / size: 28.71 GiB used: 13.81 GiB (48.1%) fs: ext4 dev: /dev/sda2
           ID-2: /home size: 768.74 GiB used: 574.95 GiB (74.8%) fs: ext4 dev: /dev/sda4
           ID-3: swap-1 size: 23.44 GiB used: 842.8 MiB (3.5%) fs: swap dev: /dev/sda3
Sensors: System Temperatures: cpu: 65.0 C mobo: N/A gpu: nouveau temp: 92 C
           Fan Speeds (RPM): N/A
Info: Processes: 333 Uptime: 9d 19h 16m Memory: 11.72 GiB used: 2.60 GiB (22.2%) Shell: bash inxi: 3.0.27

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

It seems that dbus rules are not picked up, You need to restart the computer or reload dbus rules.

Changed in timekpr-next:
status: New → Incomplete
assignee: nobody → Eduards Bezverhijs (mjasnik)
Changed in timekpr-next:
importance: Undecided → Low
Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

Forgot to add a command: sudo systemctl reload dbus

This is needed when You just added Yourself to timekpr group and did not restart the computer.
The explanation - when timekpr is installed, it adds some rules for DBUS to limit access to Timekpr-nExT server. When You add Yourself to timekpr group, DBUS does not know that unless You restart computer or reload the rules.

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

Please post here if You still have this problem.

Revision history for this message
JP Lord (jplord) wrote :

Good morning!

Just reloaded the dbus per your instruction. It now works. Great! Thanks!

Changed in timekpr-next:
status: Incomplete → Won't Fix
Changed in timekpr-next:
importance: Low → Undecided
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.