Mailinglist Archive: yast-devel (81 mails)

< Previous Next >
Re: [yast-devel] About catching exceptions
  • From: Josef Reidinger <jreidinger@xxxxxxx>
  • Date: Thu, 22 Apr 2010 16:26:11 +0200
  • Message-id: <201004221626.11879.jreidinger@xxxxxxx>
Klaus Kaempf write:
* Josef Reidinger <jreidinger@xxxxxxx> [Apr 22. 2010 15:25]:

I try to simulate it now and it works as expected. Show red flash with
report of insufficient permissions.

Right, I read "Permission to allow
is not available for user yastws"

Funny thing is that
sudo polkit-auth --user yastws --grant
fails with
polkit-auth: AuthorizationAlreadyExists: An authorization for uid 423 for
the action org.opensuse.yast.modules.yapi.users.groupsget with constraint ''
already exists

So we still have a policykit problem hidden somewhere ?!

No, it is well known issue if you run webyast as other user then yastws. I
hardcoded yastws user if policyKit throw missing permission, because only
yastws run it in production.

I check rest-service code of groups and I find different code when
DBus::Error occure so I report it.

I fixed GroupsController and ApplicationController meanwhile to catch
and report DBus::Error once.

But I cannot find why your problem is not at least logged.

Yeah, thats actually the core of bnc#598794

If it him global exception catch, then it must be logged. So something between
catch it and return response without logging content.

SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)

Josef Reidinger
YaST team
maintainer of perl-Bootloader, YaST2-Repair, parts of webyast
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups