general protection fault in libgobect-2.0 #105
Comments
|
I don't use |
|
Like I said, there are other actions that lead to this behavior. Heck, I just did a |
Coredumps are in |
|
Right-o, though I suspect you probably want all the debug symbols installed. I'm almost there. |
Just what comes after |
|
Well, Ubuntu has to be different, you know. We use Apport which apparently conflicts with |
|
Hm... actually the PR may definitely help... as in the polkitqt1's Session destructor: Session::~Session()
{
if (d->polkitAgentSession)
g_object_unref(d->polkitAgentSession);
delete d;
}and in the code after emitting void Session::Private::completed(PolkitAgentSession *s, gboolean gained_authorization, gpointer user_data)
{
qDebug() << "COMPLETED";
Session *session = (Session *)user_data;
Q_EMIT(session)->completed(gained_authorization);
//free session here as polkit documentation asks
g_object_unref(session->d->polkitAgentSession);
session->d->polkitAgentSession = nullptr;
}In the destructor the |
|
If anything crashes, I save its backtrace in a file to check it later. About a month ago, I intentionally entered a wrong password in lxqt-policykit's dialog several times, while working on pcmanfm-qt's admin mode. That resulted in a crash in lxqt-policykit (no debug symbol): @palinek's patch may be related to and fix it, although it isn't something I can reproduce. |
|
So I did get this to break once before adding all the symbol files, after which I seemed to have more problems with gdb than anything. Anyways. Here's a trace of the running |
This was found when trying to add a second user with lxqt-admin-user in the sudo group and then trying to use it again to remove the group membership. It appears that during this process, lxqt-policykit crashes, causing the change to fail.
Expected Behavior
lxqt-policykit doesn't crash.
Current Behavior
lxqt-policykit crashes. Example message (note this is a little old, but I've tested it with even earlier version as well as git master and the result is the same, with version numbers changed, obviously):
Steps to Reproduce (for bugs)
System Information
I'm just going to clip all this because it seems to affect versions new and old, so the version information really doesn't seem to matter at all. I did verify this in the Lubuntu CI builds of Git master, so I'm confident the problem still exists.
That said, I only checked Lubuntu systems. It's possible there is some underlying issue here that may be specific to our project. Using pkexec (but not sudo) seems to fail similarly as lxqt-admin-user.
Original bug here BTW.
The text was updated successfully, but these errors were encountered: