<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Sorry, I just saw this direct email (although I saw the response
in the summary last week, I didn't have a lot of time, and I don't
think I can reply to those directly from the summary that I get..
I can't change my mailing list options because the page to manage
them doesn't like the + in my email name IIRC). In any case, I
apologize because I was apparently so excited about getting it
working that I deleted the bad copy of the database. If it
happens again, I'll be sure to keep hold of it for troubleshooting
purposes.</p>
<p>Thanks,</p>
<p>Jay<br>
</p>
<div class="moz-cite-prefix">On 9/27/24 9:22 AM, Robby Stephenson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACFDV67H55bhJbfDrWoKpoQHcaLkEishJ38pRoEdBxstYxgCyg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Yes, I definitely agree with you that Tellico
shouldn't crash. Are you able to share with me directly the
database file that caused it? It doesn't look like the output
you shared is enough for me to figure out the cause. Ideally, a
crash report could help me fix it, if you were able to get a
backtrace:
<div><a
href="https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports"
moz-do-not-send="true" class="moz-txt-link-freetext">https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports</a><br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Robby</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Sep 26, 2024 at
4:18 PM Jay Zach <<a
href="mailto:jay%2Btellico@zachfamily.org"
moz-do-not-send="true">jay+tellico@zachfamily.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>I restored the database and it works fine now....
(although it seems like the application should do some
error-handling and throw an error for the database instead
of segfaulting, so I reckon its still a 'bug' of some
sort)...<br>
</p>
<p>Thanks,</p>
<p>Jay<br>
</p>
<div><br>
<br>
-------- Forwarded Message --------
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
</th>
<td>segfault when opening database</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date:
</th>
<td>Thu, 26 Sep 2024 11:38:44 -0400</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">From:
</th>
<td>Jay Zach <a
href="mailto:jay+tellico@zachfamily.org"
target="_blank" moz-do-not-send="true"><jay+tellico@zachfamily.org></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">To:
</th>
<td><a href="mailto:tellico-users@kde.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">tellico-users@kde.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<p>Segfaulting when opening my database... It will open
fine when I open with --nofile, but as soon as I open
the database in question, it crashes... Any ideas? If
not, just consider this as a bug report... :D<br>
</p>
<p>---------------------------<br>
</p>
<p>Tellico: Version 3.5.5<br>
</p>
<p>Operating System: Manjaro Linux <br>
KDE Plasma Version: 6.0.5<br>
KDE Frameworks Version: 6.5.0<br>
Qt Version: 6.7.2<br>
Kernel Version: 6.6.47-1-MANJARO (64-bit)<br>
Graphics Platform: Wayland<br>
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics<br>
Memory: 31.2 GiB of RAM<br>
Graphics Processor: AMD Radeon RX 580 Series<br>
</p>
<p>---------------------------</p>
<p><span style="font-family:monospace"><span
style="color:rgb(178,104,24);background-color:rgb(0,0,0)">jay@manjaro1 </span><span
style="color:rgb(0,0,0);background-color:rgb(24,24,178)"> ~ </span><span
style="color:rgb(24,24,178);background-color:rgb(255,255,255)"></span><span
style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> </span><span
style="color:rgb(24,178,24);background-color:rgb(255,255,255)">tellico</span><span
style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><span
style="color:rgb(0,0,0);background-color:rgb(255,255,255)"></span><span
style="color:rgb(24,178,24);background-color:rgb(0,0,0)"> ✔ </span><span
style="color:rgb(128,128,128);background-color:rgb(0,0,0)"></span><span
style="color:rgb(0,0,0);background-color:rgb(128,128,128)"> 1020 </span><span
style="color:rgb(178,178,178);background-color:rgb(128,128,128)"></span><span
style="color:rgb(0,0,0);background-color:rgb(178,178,178)"> 10:48:29</span><span
style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> </span><br>
QPainter::begin: A paint device can only be painted by
one painter at a time. <br>
QPainter::setCompositionMode: Painter not active <br>
QWidget::repaint: Recursive repaint detected <br>
QPainter::begin: A paint device can only be painted by
one painter at a time. <br>
QPainter::setCompositionMode: Painter not active <br>
QBackingStore::endPaint() called with active painter;
did you forget to destroy it or call QPainter::end()
on it? <br>
QPainter::begin: A paint device can only be painted by
one painter at a time. <br>
QPainter::setCompositionMode: Painter not active <br>
QBackingStore::endPaint() called with active painter;
did you forget to destroy it or call QPainter::end()
on it? <br>
QPainter::begin: A paint device can only be painted by
one painter at a time. <br>
QPainter::setCompositionMode: Painter not active <br>
QBackingStore::endPaint() called with active painter;
did you forget to destroy it or call QPainter::end()
on it? <br>
QBackingStore::endPaint() called with active painter;
did you forget to destroy it or call QPainter::end()
on it? <br>
[1] 160739 segmentation fault (core dumped)
tellico <br>
<span
style="color:rgb(0,0,0);background-color:rgb(0,0,0)">
</span><br>
<span
style="color:rgb(0,0,0);background-color:rgb(0,0,0)">
</span><span
style="color:rgb(178,104,24);background-color:rgb(0,0,0)">jay@manjaro1 </span><span
style="color:rgb(0,0,0);background-color:rgb(24,24,178)"> ~ </span><span
style="color:rgb(24,24,178);background-color:rgb(255,255,255)"></span><span
style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> </span><span
style="color:rgb(24,178,24);background-color:rgb(255,255,255)">tellico</span><span
style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> --nofile
</span><span
style="color:rgb(0,0,0);background-color:rgb(255,255,255)"></span><span
style="color:rgb(24,178,24);background-color:rgb(0,0,0)"> ✔ </span><span
style="color:rgb(128,128,128);background-color:rgb(0,0,0)"></span><span
style="color:rgb(0,0,0);background-color:rgb(128,128,128)"> 1022 </span><span
style="color:rgb(178,178,178);background-color:rgb(128,128,128)"></span><span
style="color:rgb(0,0,0);background-color:rgb(178,178,178)"> 10:48:43</span><span
style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> </span><br>
qt.qpa.wayland: setGrabPopup called with a parent,
QtWaylandClient::QWaylandXdgSurface(0x55b3c0d6d280)
which does not match the current topmost grabbing
popup, QtWaylandClient::QWayla<br>
ndXdgSurface(0x55b3c1501ae0) According to the
xdg-shell protocol, this is not allowed. The wayland
QPA plugin is currently handling it by setting the
parent to the topmost grabbing po<br>
pup. Note, however, that this may cause positioning
errors and popups closing unxpectedly because
xdg-shell mandate that child popups close before
parents <br>
QPainter::begin: A paint device can only be painted by
one painter at a time. <br>
QPainter::setCompositionMode: Painter not active <br>
QWidget::repaint: Recursive repaint detected <br>
QPainter::begin: A paint device can only be painted by
one painter at a time. <br>
QPainter::setCompositionMode: Painter not active <br>
QBackingStore::endPaint() called with active painter;
did you forget to destroy it or call QPainter::end()
on it? <br>
QPainter::begin: A paint device can only be painted by
one painter at a time. <br>
QPainter::setCompositionMode: Painter not active <br>
QBackingStore::endPaint() called with active painter;
did you forget to destroy it or call QPainter::end()
on it? <br>
QBackingStore::endPaint() called with active painter;
did you forget to destroy it or call QPainter::end()
on it? <br>
[1] 161128 segmentation fault (core dumped)
tellico --nofile<br>
<br>
<br>
</span></p>
</div>
</div>
</blockquote>
</div>
<hr>
<p>This email has been scanned for spam & viruses. If you
believe this email should have been stopped by our filters, <a
href="https://portal.mailanyone.net/index.html#/outer/reportspam?token=dXNlcj1qYXlAemFjaGZhbWlseS5vcmc7dHM9MTcyNzQ0MzQxMTt1dWlkPTY2RjZCMUQxMDM3MEIxQUVCQTRCNUJDQ0ZCMTVFRjZEO3Rva2VuPTNlZGNhNmRhZjE4OGVmMTdhNjEyMjExNWE2MzdkYjdmNDJiOTQ1ZWQ7"
moz-do-not-send="true">click here</a> to report it.</p>
</blockquote>
</body>
</html>