segfault when opening database

[Jay Zach]

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.

Thanks,

Jay

On 9/27/24 9:22 AM, Robby Stephenson wrote:
> 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:
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
>
> Thanks,
> Robby
>
> On Thu, Sep 26, 2024 at 4:18 PM Jay Zach <jay+tellico at zachfamily.org 
> <mailto:jay%2Btellico at zachfamily.org>> wrote:
>
>     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)...
>
>     Thanks,
>
>     Jay
>
>
>
>     -------- Forwarded Message --------
>     Subject: 	segfault when opening database
>     Date: 	Thu, 26 Sep 2024 11:38:44 -0400
>     From: 	Jay Zach <jay+tellico at zachfamily.org>
>     <mailto:jay+tellico at zachfamily.org>
>     To: 	tellico-users at kde.org
>
>
>
>     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
>
>     ---------------------------
>
>     Tellico: Version 3.5.5
>
>     Operating System: Manjaro Linux
>     KDE Plasma Version: 6.0.5
>     KDE Frameworks Version: 6.5.0
>     Qt Version: 6.7.2
>     Kernel Version: 6.6.47-1-MANJARO (64-bit)
>     Graphics Platform: Wayland
>     Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
>     Memory: 31.2 GiB of RAM
>     Graphics Processor: AMD Radeon RX 580 Series
>
>     ---------------------------
>
>     jay at manjaro1  ~ tellico✔ 1020 10:48:29
>     QPainter::begin: A paint device can only be painted by one painter
>     at a time.
>     QPainter::setCompositionMode: Painter not active
>     QWidget::repaint: Recursive repaint detected
>     QPainter::begin: A paint device can only be painted by one painter
>     at a time.
>     QPainter::setCompositionMode: Painter not active
>     QBackingStore::endPaint() called with active painter; did you
>     forget to destroy it or call QPainter::end() on it?
>     QPainter::begin: A paint device can only be painted by one painter
>     at a time.
>     QPainter::setCompositionMode: Painter not active
>     QBackingStore::endPaint() called with active painter; did you
>     forget to destroy it or call QPainter::end() on it?
>     QPainter::begin: A paint device can only be painted by one painter
>     at a time.
>     QPainter::setCompositionMode: Painter not active
>     QBackingStore::endPaint() called with active painter; did you
>     forget to destroy it or call QPainter::end() on it?
>     QBackingStore::endPaint() called with active painter; did you
>     forget to destroy it or call QPainter::end() on it?
>     [1]    160739 segmentation fault (core dumped)  tellico
>
>     jay at manjaro1  ~ tellico--nofile ✔ 1022 10:48:43
>     qt.qpa.wayland: setGrabPopup called with a parent,
>     QtWaylandClient::QWaylandXdgSurface(0x55b3c0d6d280) which does not
>     match the current topmost grabbing popup, QtWaylandClient::QWayla
>     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
>     pup. Note, however, that this may cause positioning errors and
>     popups closing unxpectedly because xdg-shell mandate that child
>     popups close before parents
>     QPainter::begin: A paint device can only be painted by one painter
>     at a time.
>     QPainter::setCompositionMode: Painter not active
>     QWidget::repaint: Recursive repaint detected
>     QPainter::begin: A paint device can only be painted by one painter
>     at a time.
>     QPainter::setCompositionMode: Painter not active
>     QBackingStore::endPaint() called with active painter; did you
>     forget to destroy it or call QPainter::end() on it?
>     QPainter::begin: A paint device can only be painted by one painter
>     at a time.
>     QPainter::setCompositionMode: Painter not active
>     QBackingStore::endPaint() called with active painter; did you
>     forget to destroy it or call QPainter::end() on it?
>     QBackingStore::endPaint() called with active painter; did you
>     forget to destroy it or call QPainter::end() on it?
>     [1]    161128 segmentation fault (core dumped)  tellico --nofile
>
>
> ------------------------------------------------------------------------
>
> This email has been scanned for spam & viruses. If you believe this 
> email should have been stopped by our filters, click here 
> <https://portal.mailanyone.net/index.html#/outer/reportspam?token=dXNlcj1qYXlAemFjaGZhbWlseS5vcmc7dHM9MTcyNzQ0MzQxMTt1dWlkPTY2RjZCMUQxMDM3MEIxQUVCQTRCNUJDQ0ZCMTVFRjZEO3Rva2VuPTNlZGNhNmRhZjE4OGVmMTdhNjEyMjExNWE2MzdkYjdmNDJiOTQ1ZWQ7> 
> to report it.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/tellico-users/attachments/20241007/e8b5a66a/attachment.htm>