Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-04-20 Thread Willi Mann
Hi Maxy, Am 2017-04-06 um 19:24 schrieb Maximiliano Curia: > El 2017-03-31 a las 21:25 +0200, Willi Mann escribió: >> Am 2017-03-31 um 18:25 schrieb Maximiliano Curia: > >>> Do you have another session started as root? Do you have another X >>> session started with your user? > >> There is no

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-04-06 Thread Maximiliano Curia
Control: tag -1 + help ¡Hola Willi! El 2017-03-31 a las 21:25 +0200, Willi Mann escribió: Am 2017-03-31 um 18:25 schrieb Maximiliano Curia: Do you have another session started as root? Do you have another X session started with your user? There is no other session running as root, except

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-03-31 Thread Willi Mann
Hi Maxy, Am 2017-03-31 um 18:25 schrieb Maximiliano Curia: > >> in the SDDM settings window, it tells me the same as when I try it as >> ordinary user (I'm not allowed to save the configuration, transl. from >> German). > >>> The changes made as root weren't applied to the /etc/sddm.conf file?

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-03-31 Thread Maximiliano Curia
¡Hola Willi! El 2017-03-23 a las 18:45 +0100, Willi Mann escribió: % su # export $(dbus-launch) # systemsettings5 in the SDDM settings window, it tells me the same as when I try it as ordinary user (I'm not allowed to save the configuration, transl. from German). The changes made as

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-03-23 Thread Willi Mann
Hi Maxy! > El 2017-03-22 a las 19:52 +0100, Willi Mann escribió: >> Am 2017-03-21 um 10:58 schrieb Maximiliano Curia: >>> El 2017-03-20 a las 19:22 +0100, Willi Mann escribió: the problem still exists. Let me know if you any idea how to track this down. > >>> Sorry, I can't reproduce

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-03-22 Thread Maximiliano Curia
¡Hola Willi! El 2017-03-22 a las 19:52 +0100, Willi Mann escribió: Am 2017-03-21 um 10:58 schrieb Maximiliano Curia: El 2017-03-20 a las 19:22 +0100, Willi Mann escribió: the problem still exists. Let me know if you any idea how to track this down. Sorry, I can't reproduce the issue here,

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-03-22 Thread Willi Mann
Control: tag -1 - moreinfo Am 2017-03-21 um 10:58 schrieb Maximiliano Curia: > > ¡Hola Willi! > > El 2017-03-20 a las 19:22 +0100, Willi Mann escribió: >> the problem still exists. Let me know if you any idea how to track >> this down. > > Sorry, I can't reproduce the issue here, the message

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-03-21 Thread Maximiliano Curia
Control: tag -1 + moreinfo ¡Hola Willi! El 2017-03-20 a las 19:22 +0100, Willi Mann escribió: the problem still exists. Let me know if you any idea how to track this down. Sorry, I can't reproduce the issue here, the message seems to be related to a rule rejecting the request for your

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

2017-03-20 Thread Willi Mann
Control: reopen -1 Hi Maxy, the problem still exists. Let me know if you any idea how to track this down. Willi Am 2017-03-16 um 20:11 schrieb Maximiliano Curia: > ¡Hola Willi! > > El 2015-08-12 a las 20:11 +0200, Willi Mann escribió: >> Package: kde-config-sddm Version: 4:5.3.2-1 Severity:

Bug#795296: You are not allowed to save the configuration (both root and ordinary user)

2015-08-12 Thread Willi Mann
Package: kde-config-sddm Version: 4:5.3.2-1 Severity: normal Hi, I get the message in the subject when I go to the SDDM config unit. It happens both when I go there as ordinary user and as root. Let me know whether I can provide further information to resolve this bug. thanks Willi -- System