From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 15 Sep 2015 00:31:43 -0700 (PDT) From: Juan RP To: voidlinux Message-Id: In-Reply-To: References: <2da6d03f-ec11-4c39-8f61-5210d5c643dd@googlegroups.com> <9fc97550-d596-4848-829f-6f91727820b4@googlegroups.com> <047765c9-93b8-4c79-a282-1c34298c3941@googlegroups.com> <970b47dc-53fc-49fa-9305-b20c4082f992@googlegroups.com> <997ed6ab-e8a6-48cb-91bf-12929e6a6316@googlegroups.com> Subject: Re: Random crashes and log-outs of E19 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1547_1090290544.1442302303277" ------=_Part_1547_1090290544.1442302303277 Content-Type: multipart/alternative; boundary="----=_Part_1548_1061931773.1442302303278" ------=_Part_1548_1061931773.1442302303278 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I fear that reinstalling the system won't make the issues go away magically. Note that I'm using udisks/udisks with e19 and never had a single crash. If you are really sure it's udisks2 fault, try to start it manually with debugging and then collect a stack trace with gdb. ------=_Part_1548_1061931773.1442302303278 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit


I fear that reinstalling the system won't make the issues go away magically.

Note that I'm using udisks/udisks with e19 and never had a single crash.

If you are really sure it's udisks2 fault, try to start it manually with debugging and then collect a stack trace with gdb.
------=_Part_1548_1061931773.1442302303278-- ------=_Part_1547_1090290544.1442302303277--