[plasmashell] [Bug 495949] New: Mystery crash in Plasma shell

2024-11-07 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=495949

Bug ID: 495949
   Summary: Mystery crash in Plasma shell
Classification: Plasma
   Product: plasmashell
   Version: 6.2.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: techok...@holenet.info
  Target Milestone: 1.0

Application: plasmashell (6.2.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.0
Frameworks Version: 6.7.0
Operating System: Linux 6.11.5-300.fc41.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 41 (Forty One)"
DrKonqi: 6.2.2 [CoredumpBackend]

-- Information about the crash:
I was simply playing a game on Steam, when suddenly my desktop proceeded to die
(segmentation fault) and restart three times. It was spontaneous and random. I
have also been having crash errors pop up upon startup, and have sent one of
those crash reports in via the automated tool already. It was not doing this
until recently, so perhaps there was a regression with a recent software
update?

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.fedoraproject.org/>
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.

warning: Can't open file anon_inode:i915.gem which was expanded to
anon_inode:i915.gem during file-backed mapping note processing

warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed
mapping note processing

warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping
note processing

warning: Can't open file /memfd:JITCode:QtQml (deleted) during file-backed
mapping note processing

warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during
file-backed mapping note processing

warning: Can't open file /memfd:kwin-dmabuf-feedback-table (deleted) during
file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/49ada484fc7975261e7c1a6eed7db137394fa294.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/0dc2aa4ab8fb8857abf07d7ce561b170fbd242bf.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/27ccb62863115205a0af1c213216db42ae58ba6c.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/f24ace811f7aa7550935201c8d54593d6e59ba10.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/e1fa90882ebd1f439a5f87d2e7927fea817e8e42.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/b61bba92706f814070c8dc116140eed4e5f54ba1.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/1408c1360a15b2d3f240aeb0574253f1fb956755.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/4adbf3794249d8212164b9fb1861df23f4d88430.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/3bf33d0e44130692145828ba698629488b20f3c8.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/2cd889abf8ca50857f22dbd4a1ffed6202baa09c.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/33c917e773abe4bc3a0103a6068c9216dcb36d95.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/6619bfb40bfbb70d412708498b0fe9d7545c6c4c.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/269d180e0b992c7912c25ac7872ddf08d257f916.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/33e546ee74ab2a9bf470424f8a50bcbb4430d92d.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/home/techokami/.cache/plasmashell/qmlcache/6358abf35463f13e2274beed39bc4fd1200d4410.qmlc
(deleted) during file-backed mapping note processing

warning: Can't 

[kpat] [Bug 495619] First deal has broken animation

2024-11-05 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=495619

--- Comment #13 from Techokami  ---
(In reply to Albert Astals Cid from comment #12)
> Maybe you can try from flathub and see if that one works?
> 
> https://flathub.org/apps/org.kde.kpat

I'd rather not find out what happens when native packages and flatpaks collide,
thanks. šŸ˜¬

-- 
You are receiving this mail because:
You are watching all bug changes.

[kpat] [Bug 495619] First deal has broken animation

2024-11-04 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=495619

--- Comment #9 from Techokami  ---
I should also add that, back on Fedora 39 when I didn't have this problem, I
was also using only Wayland, soo... really unsure why needing to double-check
on X11 was needed

-- 
You are receiving this mail because:
You are watching all bug changes.

[kpat] [Bug 495619] First deal has broken animation

2024-11-03 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=495619

--- Comment #8 from Techokami  ---
(In reply to Neal Gompa from comment #7)
> You can also test it by launching the application in X11 mode. Try this from
> Konsole:
> 
> ```
> $ QT_QPA_PLATFORM="xcb" kpat &
> ```
Oh, I did not know that! Sorry about namedropping you.
The behavior is exactly the same when run this way.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kpat] [Bug 495619] First deal has broken animation

2024-11-03 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=495619

--- Comment #6 from Techokami  ---
(In reply to Albert Astals Cid from comment #5)
> Wow you really have no animations at all.
> 
> I see you're using wayland, can you try in X11?

Considering I'm on Fedora 41, uh, no. There's no longer any option to start
Plasma with X11. For further details about this, please ask Neal Gompa.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kpat] [Bug 495619] First deal has broken animation

2024-11-02 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=495619

--- Comment #4 from Techokami  ---
(In reply to Albert Astals Cid from comment #3)
> Can you record a video?
> 
> Mod3 perfectly animates here want to see what you mean

Alright, here's a quick video showing the bug: https://youtu.be/D5tgR-1JGSc

-- 
You are receiving this mail because:
You are watching all bug changes.

[kpat] [Bug 495619] First deal has broken animation

2024-10-30 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=495619

--- Comment #2 from Techokami  ---
(In reply to Neal Gompa from comment #1)
> Well, it's probably something that happened as part of porting to Qt6, it
> doesn't necessarily mean it's a Qt6 issue *itself*.

That's kind of what I meant by "Qt6-related", probably could have worded it
better

-- 
You are receiving this mail because:
You are watching all bug changes.

[kpat] [Bug 495619] New: First deal has broken animation

2024-10-30 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=495619

Bug ID: 495619
   Summary: First deal has broken animation
Classification: Applications
   Product: kpat
   Version: 24.08.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: techok...@holenet.info
CC: kde-games-b...@kde.org
  Target Milestone: ---

SUMMARY
On the very first deal after KPatience has been launched and a game selected,
the animation is abruptly skipped and auto-playable cards may randomly fail to
be played. This *only* affects the very first deal after the application has
been launched, as subsequent deals (either from the "New Deal" action or
picking a game from "New Game") will correctly play the animation.

STEPS TO REPRODUCE
1. Launch KPatience
2. Select a game
3. Notice that the dealing animation is missing

OBSERVED RESULT
Cards immediately appear without being drawn, aces that should be auto-played
in Mod3 often fail to be auto-played

EXPECTED RESULT
The proper dealing animation and aces being auto-played in Mod3

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
Kernel Version: 6.11.5-300.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 Ɨ 13th Gen IntelĀ® Coreā„¢ i9-13900K
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa IntelĀ® Arc

ADDITIONAL INFORMATION
I had noticed this after recently upgrading from Fedora 39 to Fedora 40, and
was hoping it would go away after upgrading to Fedora 41. It persisted after
upgrading to Fedora 41. I have discussed this with Neal Gompa from the Fedora
Project and we both seem to think this is a Qt6-related issue? So I'm filing
this bug report after he suggested that I do so.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 453795] Kate crashed when opening settings

2022-07-04 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=453795

--- Comment #8 from Techokami  ---
Created attachment 150400
  --> https://bugs.kde.org/attachment.cgi?id=150400&action=edit
New crash information added by DrKonqi

kate (22.04.1) using Qt 5.15.3

- What I was doing when the application crashed:
I was simply going to the Settings menu, and the application completely crashed
and took my work with it.

-- Backtrace (Reduced):
#4  0x7ff57da5fdae in QMapData::findNode(KEntryKey
const&) const () from /lib64/libKF5ConfigCore.so.5
#6  0x7ff57da5f7e2 in KConfigPrivate::lookupData(QByteArray const&, char
const*, QFlags, bool*) const () from
/lib64/libKF5ConfigCore.so.5
#7  0x7ff57da6bf95 in KConfigGroup::readEntry(char const*, QString const&)
const () from /lib64/libKF5ConfigCore.so.5
#8  0x7ff57da6c1af in KConfigGroup::readEntry(char const*, char const*)
const () from /lib64/libKF5ConfigCore.so.5
#9  0x7ff569abd212 in KDirOperator::readConfig(KConfigGroup const&) () from
/lib64/libKF5KIOFileWidgets.so.5

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 453795] Kate crashed when opening settings

2022-07-04 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=453795

Techokami  changed:

   What|Removed |Added

 CC||techok...@holenet.info

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 454678] Kalendar immediately crashed upon starting

2022-06-13 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=454678

Techokami  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UNMAINTAINED

--- Comment #7 from Techokami  ---
Well after using those commands and getting scared that everything violently
broke, Kalendar is now functional again! Thank you Max!

I changed the status to reflect that WHY DID THIS EVEN HAPPEN IN THE FIRST
PLACE?! This was a clean install of Kalendar onto a clean install of the KDE
spin of Fedora 36! I was expecting everything to work out of the box, but
instead I had to do a ton of MySQL necromancy using outdated commands (did you
know that the -Q parameter for mysqladmin no longer exists?) which is just...
not good for normal users that aren't comfortable with the terminal. I really
want to know why there wasn't a more graceful failover here, or even why the
Akonadi database wasn't properly initialized. Like, when it tries to do ALTER
TABLE to set up the database, but it's not initialized so the table isn't
there, why not first issue a SQL command to check if the table exists in the
first place, and if it doesn't, make Akonadi initialize the database then try
again?

Welp, now I have a headache, but at least now I got a proper calendar program
to sync my Outlook calendar with, so I can get back all my appointments.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 454678] Kalendar immediately crashed upon starting

2022-06-13 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=454678

--- Comment #5 from Techokami  ---
So I tried running this in the terminal, and I also tried what Max did, but to
no avail. The console output is pretty long so I put it into a pastebin for
convenience: https://pastebin.com/WyyuKmys
Also, here is the contents of ~/.local/share/akonadi/Akonadi.error:

2022-06-13T20:59:44 [INFO ] org.kde.pim.akonadiserver: Starting up the Akonadi
Server...
2022-06-13T20:59:45 [INFO ] org.kde.pim.akonadiserv2022-06-13T20:59:48 [INFO ]
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
i.SchemaVersionTable' doesn't exist QMYSQL: Unable to execute query\nQuery:
ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0"
2022-06-13T20:59:45 [CRITICAL] org.kde.pim.akonadiserver: Unable to initialize
database.
2022-06-13T20:59:48 [INFO ] org.kde.pim.akonadiserver: Shutting down
AkonadiServer...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 454678] Kalendar immediately crashed upon starting

2022-06-10 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=454678

Techokami  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 454678] Kalendar immediately crashed upon starting

2022-06-03 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=454678

--- Comment #2 from Techokami  ---
(In reply to Claudio Cambra from comment #1)
> Do you have kdepim-runtime installed? Other users have described similar
> crashes due to this:
> 
> https://bugs.kde.org/show_bug.cgi?id=453016

I do, in fact, have this package installed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 454678] New: Kalendar immediately crashed upon starting

2022-05-31 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=454678

Bug ID: 454678
   Summary: Kalendar immediately crashed upon starting
   Product: kalendar
   Version: 1.0.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: techok...@holenet.info
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: kalendar (1.0.0)

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.17.11-300.fc36.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I was just starting the software. Every single time, it just crashes. I have no
idea why this is occuring, as I am using the KDE spin of Fedora 36 and
installing the official RPMs from Fedora's repositories. I am not compiling any
of KDE or Qt manually from sources here.

The crash can be reproduced every time.

-- Backtrace:
Application: Kalendar (kalendar), signal: Segmentation fault

[KCrash Handler]
#4  0x7fb2c13992e4 in Akonadi::IncidenceChanger::history() const () from
/lib64/libKF5AkonadiCalendar.so.5
#5  0x56129fa1b8c7 in CalendarManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) ()
#6  0x7fb2c0a111ac in loadProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData const&) () from /lib64/libQt5Qml.so.5
#7  0x7fb2c0b67669 in
QV4::QQmlTypeWrapper::lookupSingletonProperty(QV4::Lookup*,
QV4::ExecutionEngine*, QV4::Value const&) () from /lib64/libQt5Qml.so.5
#8  0x7fb2c0b69160 in
QV4::QQmlTypeWrapper::virtualResolveLookupGetter(QV4::Object const*,
QV4::ExecutionEngine*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5
#9  0x7fb2c0a3208a in QV4::Moth::VME::interpret(QV4::CppStackFrame*,
QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5
#10 0x7fb2c0a36a97 in QV4::Moth::VME::exec(QV4::CppStackFrame*,
QV4::ExecutionEngine*) () from /lib64/libQt5Qml.so.5
#11 0x7fb2c09c80f6 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5
#12 0x7fb2c0b55888 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () from /lib64/libQt5Qml.so.5
#13 0x7fb2c0b5bcd8 in QQmlBinding::evaluate(bool*) () from
/lib64/libQt5Qml.so.5
#14 0x7fb2c0b5fee7 in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) () from /lib64/libQt5Qml.so.5
#15 0x7fb2c0b5d9e4 in
QQmlBinding::update(QFlags) () from
/lib64/libQt5Qml.so.5
#16 0x7fb2c0b6b02b in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from
/lib64/libQt5Qml.so.5
#17 0x7fb2c0afa79c in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) () from /lib64/libQt5Qml.so.5
#18 0x7fb2c0afc7a9 in QQmlComponentPrivate::completeCreate() () from
/lib64/libQt5Qml.so.5
#19 0x7fb2c0afc941 in QQmlComponent::create(QQmlContext*) () from
/lib64/libQt5Qml.so.5
#20 0x7fb2c0b61498 in
QQmlApplicationEnginePrivate::finishLoad(QQmlComponent*) () from
/lib64/libQt5Qml.so.5
#21 0x7fb2c0b61b91 in QQmlApplicationEngine::load(QUrl const&) () from
/lib64/libQt5Qml.so.5
#22 0x56129fa17a80 in main ()
[Inferior 1 (process 7040) detached]

The reporter indicates this bug may be a duplicate of or related to bug 446747.

Possible duplicates by query: bug 446747.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 446747] Kalendar crashes at startup

2022-04-04 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=446747

--- Comment #12 from Techokami  ---
Created attachment 147966
  --> https://bugs.kde.org/attachment.cgi?id=147966&action=edit
New crash information added by DrKonqi

kalendar (1.0.0) using Qt 5.15.3

I am also having the same issues with Kalendar, installed from the official
RPMs for Fedora 36.

-- Backtrace (Reduced):
#4  0x7f4d1de442e8 in Akonadi::IncidenceChanger::history() const () from
/lib64/libKF5AkonadiCalendar.so.5
#5  0x55b526ab58c7 in CalendarManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) ()
#6  0x7f4d1d4c21ac in loadProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData const&) () from /lib64/libQt5Qml.so.5
#7  0x7f4d1d618669 in
QV4::QQmlTypeWrapper::lookupSingletonProperty(QV4::Lookup*,
QV4::ExecutionEngine*, QV4::Value const&) () from /lib64/libQt5Qml.so.5
#8  0x7f4d1d61a160 in
QV4::QQmlTypeWrapper::virtualResolveLookupGetter(QV4::Object const*,
QV4::ExecutionEngine*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 446747] Kalendar crashes at startup

2022-04-04 Thread Techokami
https://bugs.kde.org/show_bug.cgi?id=446747

Techokami  changed:

   What|Removed |Added

 CC||techok...@holenet.info

-- 
You are receiving this mail because:
You are watching all bug changes.