[plasmashell] [Bug 446961] Add option to select screen in custom notification positioning UI
https://bugs.kde.org/show_bug.cgi?id=446961 brainpower changed: What|Removed |Added CC||brainpo...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472950] New: Kate crashes when displaying any konsole / terminal
https://bugs.kde.org/show_bug.cgi?id=472950
Bug ID: 472950
Summary: Kate crashes when displaying any konsole / terminal
Classification: Applications
Product: kate
Version: 23.07.80
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: brainpo...@mailbox.org
Target Milestone: ---
Application: kate (23.07.80)
Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.4.7-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.6 [KCrashBackend]
-- Information about the crash:
When Kate resumes a session where the terminal was open, it crashes
immediately.
Else it crashes whenever the terminal shoud get rendered.
I reproduced the latter with `kate --startanon` to avoid this being related to
a corrupt session.
Konsole started standalone (e.g. not embedded) seems fine.
Also tried with rebuilt packages, but that did not help.
I see a null pointer deref about to happen at #9 in the backtrace, where
this=0x0.
% pacman -Q konsole kate qt5-base
konsole 23.07.80-1
kate 23.07.80-1
qt5-base 5.15.10+kde+r145-1
The crash can be reproduced every time.
-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f7e69b7197b in QScopedPointer >::operator->() const (this=)
at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#7 qGetPtrHelper > >(QScopedPointer >&) (ptr=) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1149
#8 QAction::d_func() (this=) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#9 QAction::setVisible(bool) (this=0x0, b=true) at kernel/qaction.cpp:1051
#10 0x7f7e3eed20a4 in Konsole::Screen::setReplMode(int) () at
/usr/lib/libkonsoleprivate.so.1
#11 0x7f7e3eeed025 in
Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int) ()
at /usr/lib/libkonsoleprivate.so.1
#12 0x7f7e3eede220 in
Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates,
unsigned int) () at /usr/lib/libkonsoleprivate.so.1
#13 0x7f7e3eede5ac in
Konsole::Vt102Emulation::receiveChars(QVector const&) () at
/usr/lib/libkonsoleprivate.so.1
#14 0x7f7e3eeb8b8a in Konsole::Emulation::receiveData(char const*, int) ()
at /usr/lib/libkonsoleprivate.so.1
#15 0x7f7e68ed15a7 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd6b376dc0, r=, this=0x55c3c287b4f0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x55c3c2878930,
signal_index=17, argv=0x7ffd6b376dc0) at kernel/qobject.cpp:3925
#17 0x7f7e3eea68cb in Konsole::Pty::receivedData(char const*, int) () at
/usr/lib/libkonsoleprivate.so.1
#18 0x7f7e3eebe769 in Konsole::Pty::dataReceived() () at
/usr/lib/libkonsoleprivate.so.1
#19 0x7f7e68ed15a7 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd6b376e90, r=, this=0x55c3c287b3b0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate(QObject*, int, void**) (sender=0x55c3c2878b60,
signal_index=3, argv=0x7ffd6b376e90) at kernel/qobject.cpp:3925
#21 0x7f7e4c07b0c7 in KPtyDevicePrivate::_k_canRead() (this=0x55c3c286b170)
at /usr/src/debug/kpty/kpty-5.108.0/src/kptydevice.cpp:291
#22 0x7f7e4c07b369 in KPtyDevice::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_c=, _a=0x7ffd6b377020,
_id=, _o=) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:84
#23 KPtyDevice::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)
(_o=, _c=, _id=,
_a=0x7ffd6b377020) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:77
#24 0x7f7e68ed1763 in doActivate(QObject*, int, void**)
(sender=0x55c3c287acd0, signal_index=5, argv=0x7ffd6b377020) at
kernel/qobject.cpp:3937
#25 0x7f7e68ed2e19 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x55c3c287acd0,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:185
#26 0x7f7e68ed2f0b in QSocketNotifier::event(QEvent*) (this=0x55c3c287acd0,
e=) at kernel/qsocketnotifier.h:115
#27 0x7f7e69b7893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55c3c287acd0, e=0x7ffd6b377130) at
kernel/qapplication.cpp:3640
#28 0x7f7e68e9c668 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55c3c287acd0, event=0x7ffd6b377130) at
kernel/qcoreapplication.cpp:1064
#29 0x7f7e68eea236 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x55c3c096dfb0) at kernel/qeventdispatcher_glib.cpp:107
#30 0x7f7e6670fa31 in g_main_dispatch (context=0x7f7e5c000ee0) at
../glib/glib/gmain.c:3460
#31 g_main_context_dispatch
[kalendar] [Bug 472793] merkuro-calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=472793 --- Comment #3 from brainpower --- oh, I overlooked the LANGUAGE var was set (and relevant) on my system and only overwrote LANG. with LANGUAGE unset or set analogous to LANG the en_* locales work for me too. And locales with no corresponding *.qm files installed, do not crash, but the app is not fully translated of course. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 472793] merkuro-calendar crashes on startup (binding loop)
https://bugs.kde.org/show_bug.cgi?id=472793 brainpower changed: What|Removed |Added CC||brainpo...@mailbox.org --- Comment #1 from brainpower --- Any "LANG" which is not empty or C, does produce a crash: no crash: LANG= merkuro-calendar LANG=C merkuro-calendar crash: LANG=C.UTF-8 merkuro-calendar LANG=de_DE.UTF-8 merkuro-calendar LANG=fr_FR.UTF-8 merkuro-calendar LANG=en_US.UTF-8 merkuro-calendar LANG=en_US merkuro-calendar The bind loop message seems irrelevant, since it also appears when it does not crash. >From the backtrace it seems to try to look up a qml property and fails doing that. I've got no idea how to debug this further, though: (gdb) bt #0 0x7709f452 in QV4::QQmlValueTypeWrapper::create(QV4::ExecutionEngine*, QObject*, int, QMetaObject const*, int) (engine=0x55cd8870, object=0x567c3e80, property=13, metaObject=0x77d11de0 , typeId=67) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlvaluetypewrapper.cpp:187 #1 0x76f74476 in loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0x55cd8870, object=0x567c3e80, property=...) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:186 #2 0x76f7535d in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (property=0x0, hasProperty=0x0, revisionMode=QV4::QObjectWrapper::IgnoreRevision, name=0x7fffbc3c05b0, object=0x567c3e80, qmlContext=0x58478de0, engine=0x55cd8870) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:388 #3 QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (engine=0x55cd8870, qmlContext=0x58478de0, object=0x567c3e80, name=0x7fffbc3c05b0, revisionMode=QV4::QObjectWrapper::IgnoreRevision, hasProperty=0x0, property=0x0) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:358 #4 0x770a50bf in QV4::QQmlTypeWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) (m=0x7fffbc3c05a0, id=..., receiver=0x7fffbc3c05a0, hasProperty=0x0) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypewrapper.cpp:268 #5 0x76f1f301 in QV4::Lookup::getterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) (l=0x56516920, engine=0x55cd8870, object=) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4lookup.cpp:231 #6 0x7fffa53b6828 in () #7 0x7f7ff4e0 in () #8 0x in () -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468077] It's now harder to draw an unfilled circle/ellipse/square/rectangle
https://bugs.kde.org/show_bug.cgi?id=468077 brainpower changed: What|Removed |Added CC||brainpo...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 452048] Remote File Previews are not shown when Limit is set to 4096MiB or more
https://bugs.kde.org/show_bug.cgi?id=452048 --- Comment #2 from brainpower --- I was able to fork and create a MR now, so here it is: https://invent.kde.org/frameworks/kio/-/merge_requests/800 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 452048] New: Remote File Previews are not shown when Limit is set to 4096MiB or more
https://bugs.kde.org/show_bug.cgi?id=452048 Bug ID: 452048 Summary: Remote File Previews are not shown when Limit is set to 4096MiB or more Product: frameworks-kio Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: brainpo...@mailbox.org CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 147826 --> https://bugs.kde.org/attachment.cgi?id=147826&action=edit path to fix the issue SUMMARY I noticed that dolphin did not show previews of videos on my nfs filesystem anymore since one of the latest updates, probably Frameworks 5.92. STEPS TO REPRODUCE 1. Set remote file preview limit to 4096 MiB or more in dolphin settings (General -> Previews) 2. Navigate to a remote FS with previewable files, nfs with video files in my case OBSERVED RESULT No previews. Even for files smaller than 4 GiB, 1.3 GiB video files for example. EXPECTED RESULT Previews being loaded or generated and shown, if the file is smaller than 4 GiB (or however the limit is set). SOFTWARE/OS VERSIONS Operating System: Arch Linux Dolphin Version: 22.03.80 (also tried git master) KDE Frameworks Version: 5.92.0 (also tried git master) Qt Version: 5.15.3 Kernel Version: 5.17.0-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I traced this setting to ~/.config/kdeglobals where it is stored as MaximumRemoteSize in Group "PreviewSettings". When set to 4096 MiB in dolphin, the value in the config file becomes 4294967296 . When set to 4095 MiB, the value becomes 4293918720 . This number looked suspiciously like UINT_MAX, so I looked that up: 4294967295 And behold, 4294967296 == UINT_MAX + 1. So I went searching for the place where some code uses an uint instead of a size_t or something like that. I compiled from source, did some "printf-Debugging" in previewjob.cpp [1] and found that the "MaximumRemoteSize" setting was indeed not read correctly. [1]: https://invent.kde.org/frameworks/kio/-/blob/a474739fc0eb714ac5230514f2af5ab397c1613a/src/widgets/previewjob.cpp#L415 MaximumRemoteSize=4293918720 (4095 MiB) was read as 18446744073708503040 MaximumRemoteSize=4294967296 (4096 MiB) was read as 0 MaximumRemoteSize=4296015872 (4097 MiB) was read as 1048576 I'm not sure which kind of combination of overflowing and/or misinterpreting would produce these values. 4293918720 does not even overflow an uint but produces a garbage 64 bit value somehow. Anyway, indicating the correct integer type to KConfig's readEntry() by casting the default value seems to be enough to solve this. I've attached a git format-patch which does that. I wanted to do a Merge Request directly, but Gitlab refuses to let me fork KIO. When trying to do that manually, it shows these errors from the remote's pre-receive hook: ``` [...] remote: Resolving deltas: 100% (42286/42286), done. remote: Audit failure - Commit d2aeab0987959fe3f250a2b0afa866215f82f94a - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit d2aeab0987959fe3f250a2b0afa866215f82f94a - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit c5e008e1af7a0cd7f4ca1acada4131443c468478 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit c5e008e1af7a0cd7f4ca1acada4131443c468478 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit c09634935294dbdea0839541bb620254581b5b65 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit c09634935294dbdea0839541bb620254581b5b65 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit ba6dd58ae76903c1802d8ee80cb4711abc5ef79f - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit ba6dd58ae76903c1802d8ee80cb4711abc5ef79f - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit fdba4bb168b64c3a9c89c62ace088bf19a7bced6 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit fdba4bb168b64c3a9c89c62ace088bf19a7bced6 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit 872a8be0e64225b39629514c475b93d9b14649d9 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit 872a8be0e64225b39629514c475b93d9b14649d9 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit 9063654daa5af4e3c846db9488c202cf3313a536 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Audit failure - Commit 9063654daa5af4e3c846db9488c202cf3313a536 - Email address has an invalid domain : k...@randomguy3.me.uk remote: Push declined - commits failed audit re
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 brainpower changed: What|Removed |Added CC||brainpo...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 439991] akonadi_imap_resource crashes when I open the account settings
https://bugs.kde.org/show_bug.cgi?id=439991 brainpower changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||kdepim-runtime/commit/d47c2 ||9c4d6d48688eed665ff4a2837db ||6bce70bb --- Comment #3 from brainpower --- Git commit d47c29c4d6d48688eed665ff4a2837db6bce70bb by Franz Baumgärtner. Committed on 29/07/2021 at 08:03. Pushed by mlaurent into branch 'master'. fix UI elements being used before initialization commit 18bc7e43 introduced calls to setRevealPasswordAvailable() on password fields. those calls happened before m_ui->password and m_ui->customPassword were initialized by the call to m_ui->setupUI(), and led to a crash when trying to open the settings of an IMAP account. M +2-2resources/imap/setupserver.cpp https://invent.kde.org/pim/kdepim-runtime/commit/d47c29c4d6d48688eed665ff4a2837db6bce70bb -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 439991] akonadi_imap_resource crashes when I open the account settings
https://bugs.kde.org/show_bug.cgi?id=439991 brainpower changed: What|Removed |Added CC||brainpo...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430942] Rectangular Region mode produces black rectangles with 3 screens
https://bugs.kde.org/show_bug.cgi?id=430942 --- Comment #16 from brainpower --- Insertion order seems to matter: https://invent.kde.org/brainpower/spectacle/-/snippets/1456 So question is: Is this a bug in QMap or wrong usage of QMap? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430942] Rectangular Region mode produces black rectangles with 3 screens
https://bugs.kde.org/show_bug.cgi?id=430942
--- Comment #15 from brainpower ---
Found the issue:
If I add a few qDebug:
--- a/src/QuickEditor/QuickEditor.cpp
+++ b/src/QuickEditor/QuickEditor.cpp
@@ -116,8 +116,12 @@ QuickEditor::QuickEditor(const QMap &images, KWayland:
input.insert(pos, QPair(screenImage.width() /
static_cast(screen->size().width()), screenImage.size()));
}
const auto pointsTranslationMap = computeCoordinatesAfterScaling(input);
+qDebug() << "pointsTranslationMap: " << pointsTranslationMap;
+qDebug() << "pointsTranslationMap.keys():" << pointsTranslationMap.keys();
QPainter painter(&mPixmap);
for (auto it = mImages.constBegin(); it != mImages.constEnd(); it ++) {
+qDebug() << "it.key() == QPoint(1680,0) ->" << (it.key() ==
ComparableQPoint(QPoint(1680,0)));
+qDebug() << "it.key():" << it.key() << "\t translated:" <<
pointsTranslationMap.value(it.key());
painter.drawImage(pointsTranslationMap.value(it.key()), it.value());
}
painter.end();
I get:
% build/bin/spectacle
pointsTranslationMap:QMap((QPoint(1680,0),
QPoint(1680,0))(QPoint(0,195), QPoint(0,195))(QPoint(4240,0), QPoint(4240,0)))
pointsTranslationMap.keys(): (QPoint(1680,0), QPoint(0,195), QPoint(4240,0))
it.key() == QPoint(1680,0) -> true
it.key(): QPoint(1680,0) translated: QPoint(0,0)
it.key() == QPoint(1680,0) -> false
it.key(): QPoint(0,195) translated: QPoint(0,195)
it.key() == QPoint(1680,0) -> false
it.key(): QPoint(4240,0) translated: QPoint(4240,0)
But it should be
it.key(): QPoint(1680,0) translated: QPoint(1680,0)
instad of
it.key(): QPoint(1680,0) translated: QPoint(0,0)
I have no idea why the QMap::value() returns the defaultValue here instead of
the value the key should map to...
it seems to exist correctly in the pointsTranslationMap after all...
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 430942] Rectangular Region mode produces black rectangles with 3 screens
https://bugs.kde.org/show_bug.cgi?id=430942 --- Comment #14 from brainpower --- Reverting https://invent.kde.org/graphics/spectacle/-/commit/4a3cb5140cc58d73b1f0f0083d7f24f9f3a40b2a fixes the issue, so it's something that changed with that commit... which is a lot... :S -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430942] Rectangular Region mode produces black rectangles with 3 screens
https://bugs.kde.org/show_bug.cgi?id=430942 brainpower changed: What|Removed |Added Attachment #134891|0 |1 is obsolete|| --- Comment #13 from brainpower --- Created attachment 134892 --> https://bugs.kde.org/attachment.cgi?id=134892&action=edit The whole middle screen (jpg for smaller size) with xrandr output -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430942] Rectangular Region mode produces black rectangles with 3 screens
https://bugs.kde.org/show_bug.cgi?id=430942 --- Comment #12 from brainpower --- Oh, and the bug only happens with the middle screen. There is no problem with capturing a rectangle the leftmost or rightmost screen. Only the capture of the middle screnn is "off" ;) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430942] Rectangular Region mode produces black rectangles with 3 screens
https://bugs.kde.org/show_bug.cgi?id=430942 --- Comment #11 from brainpower --- This seems like som kind of offset issue. I've added 2 files, the jpg shows the whole middle screen of mine, the png shows a selection of the *left* half of the screen, which should show the background, but it shows the Konsole window instead! So the content seems moved to the left, by about the amount the leftmost screens width. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430942] Rectangular Region mode produces black rectangles with 3 screens
https://bugs.kde.org/show_bug.cgi?id=430942 --- Comment #10 from brainpower --- Created attachment 134891 --> https://bugs.kde.org/attachment.cgi?id=134891&action=edit The whole middle screen (jpg for smaller size) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430942] Rectangular Region mode produces black rectangles with 3 screens
https://bugs.kde.org/show_bug.cgi?id=430942 brainpower changed: What|Removed |Added CC||brainpo...@mailbox.org --- Comment #9 from brainpower --- Created attachment 134890 --> https://bugs.kde.org/attachment.cgi?id=134890&action=edit The left half of my middle screen -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 417722] Cannot Drag/Drop Screenshot Due To Subfolder in Filename
https://bugs.kde.org/show_bug.cgi?id=417722 --- Comment #6 from brainpower --- Did I do it right? https://phabricator.kde.org/D28702 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 417722] Cannot Drag/Drop Screenshot Due To Subfolder in Filename
https://bugs.kde.org/show_bug.cgi?id=417722 --- Comment #5 from brainpower --- oh, I thought that was for dev's only not for "casual patch posting". Sorry. Will try submitting to phabricator soon. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 417722] Cannot Drag/Drop Screenshot Due To Subfolder in Filename
https://bugs.kde.org/show_bug.cgi?id=417722 brainpower changed: What|Removed |Added Attachment #127406|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 417722] Cannot Drag/Drop Screenshot Due To Subfolder in Filename
https://bugs.kde.org/show_bug.cgi?id=417722 --- Comment #3 from brainpower --- Created attachment 127407 --> https://bugs.kde.org/attachment.cgi?id=127407&action=edit correct patch for creating subdirs in tmp dir Sorry, wrong patch file, this is the correct one. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 417722] Cannot Drag/Drop Screenshot Due To Subfolder in Filename
https://bugs.kde.org/show_bug.cgi?id=417722 --- Comment #2 from brainpower --- Created attachment 127406 --> https://bugs.kde.org/attachment.cgi?id=127406&action=edit patch for creating subdirs in tmp dir I've been using this patch for a while now with 0.03.90 and 0.03.80. Worked fine for me, but I'm not sure if that's the way to properly do it. localSave() uses similar code, though. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 417722] Cannot Drag/Drop Screenshot Due To Subfolder in Filename
https://bugs.kde.org/show_bug.cgi?id=417722 brainpower changed: What|Removed |Added CC||brainpo...@mailbox.org --- Comment #1 from brainpower --- I have the same Problem. I've also configured Subfolders based on date. My save filename is set to to "%Y/%M/screen-%2d". Ran spectacle in strace and saw it try to open a file in /tmp without mkdir-ing the subfolders first, thus failing. openat(AT_FDCWD, "/tmp/Spectacle.MIzolT/2020/02/screen-01.png", O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = -1 ENOENT (No such file or directory) The temporary dir exists, the subfolders do not: % tree /tmp/Spectacle.MIzolT /tmp/Spectacle.MIzolT 0 directories, 0 files After that I ran mkdir -p /tmp/Spectacle.MIzolT/2020/02/ and tried again, no error occurred then and the screenshot was saved correctly: % tree /tmp/Spectacle.MIzolT /tmp/Spectacle.MIzolT └── 2020 └── 02 └── screen-01.png 2 directories, 1 file So spectacle should do either of: 1. Create the subdirs if they do not exist, as it does when savong normally 2. Strip the subdirs when saving temporarily VERSION INFORMATION % spectacle --version spectacle 19.12.2 Operating System: Arch Linux KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.15.0 Kernel Version: 5.5.6-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
