search for: storagep

...an account, XDG_RUNTIME_DIR is set. But! If you `su -` to the account from root, e.g: # su - stack Then XDG_RUNTIME_DIR is *not* set. The problem is a little subtle, because most operations you will perform will work just fine in both cases: you can query for defined but not active guests, storagep pools, volumes, and so forth without a problem and you'll get the same answer. The problem crops up when you start a guest, which results in a persistent libvirtd process. Now, depending on how you got to your account, you will either (a) talk to the persistent process, and you'll be able...

...But! If you `su -` to the account > from root, e.g: > > # su - stack > > Then XDG_RUNTIME_DIR is *not* set. The problem is a little subtle, > because most operations you will perform will work just fine in both > cases: you can query for defined but not active guests, storagep > pools, volumes, and so forth without a problem and you'll get the same > answer. IMHO this is a bug in the pam config. We really expect to see the same environment setup no matter how you login text console vs su vs ssh vs GDM. If that's not happening, its always going to cause b...

...b) bt full #0 fts_backend_deinit (_backend=0xd67ef8) at fts-api.c:84 backend = 0x0 #1 0x00007f168263a8de in fts_mailbox_list_deinit (list=0xd678e8) at fts-storage.c:833 flist = 0xd67e28 #2 0x00007f1683ff705a in mail_namespace_free (ns=0xd69780) at mail-namespace.c:62 storagep = <value optimized out> #3 0x00007f1683ff8045 in mail_namespaces_init_location (user=0xd712f0, location=<value optimized out>, error_r=0x7ffd248bc8d0) at mail-namespace.c:514 inbox_set = 0xd72110 unexpanded_inbox_set = 0xd72170 ns = 0xd69780 ma...