[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #2 from Lukas Jirkovsky --- The home directory is on a SSD, so the speed is decent. Also, I forgot to mention the versions: kdevplatform 6cf05bdad48f093dcf9efad4f78d8275ce44f7a6 kdevelop cbe05bc0d8218744cc30a0e0241f8c3f25497049 clang 3.9.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] New: KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 Bug ID: 372040 Summary: KDevelop editor become unresponsive when clicking into a problem Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: l.jirkov...@gmail.com Target Milestone: --- Created attachment 102016 --> https://bugs.kde.org/attachment.cgi?id=102016&action=edit perf record output If I click on an underlined identifier, the editor becomes unresponsive for several seconds. I noticed that when I navigate to the identifier in the editor using keyboard arrows, there is no slowdown and KDevelop is perfectly resnposive the whole time. This problem happens with a work-related project that can be considered somewhat peculiar. There are about 6000 includes in ~500 subdirectories in the include path. The project itself is only a small subset of sources - the problem occurs even with a small test project that consists only of a single file that includes only few of the includes, though it becomes worse with larger projects. The sources are mounted using samba from a locally running virtual machine. Attached is a profile generated using the linux perf utility with the following command: perf record -g -p sleep 3 which I executed just before clicking on a problem in the editor. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #4 from Lukas Jirkovsky --- There must be something different in how the reparse (if it's the reparse) is invoked. I just did few more experiments: Test #1 1. rename a variable 2. move to a previous use of the variable using arrow keys 3. in the meantime, the project is reparsed and all previous uses are now marked "Use of undeclared identifier" The whole time KDevelop is responsive. Another test 1. rename a variable 2. quickly click on a use before it gets marked as a problem KDevelop stays responsive Test #2 1. rename a variable 2. wait for the reparse to finish 3. click on a use that is now underlined The whole KDevelop UI (I didn't realize it wasn't just the editor before) freezes for about 5 seconds. In fact, any click on the problem freezes the UI. Maybe I should have emphasized that the UI freezes every time I click on a problem, even when the project is fully parsed, so the parser may not be the problem after all. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #5 from Lukas Jirkovsky --- Another bunch of tests: Test #1 The project sources are in tmpfs, includes are on the samba share => same behaviour Test #2 All sources, including includes are in tmpfs => everything's fine -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #7 from Lukas Jirkovsky --- I just got an idea, though I may be completely wrong. Is it possible that it's related to the Clang Fix-its? They don't show when navigating using keyboard. I'll try to get backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372040] KDevelop editor become unresponsive when clicking into a problem
https://bugs.kde.org/show_bug.cgi?id=372040 --- Comment #8 from Lukas Jirkovsky --- I hope I sent interrupt at the right time... #0 0x74cc4c9b in __getdents64 () at /usr/lib/libc.so.6 #1 0x74cc4a10 in readdir_r () at /usr/lib/libc.so.6 #2 0x75556773 in () at /usr/lib/libQt5Core.so.5 #3 0x754dcc8c in () at /usr/lib/libQt5Core.so.5 #4 0x754dd4dd in () at /usr/lib/libQt5Core.so.5 #5 0x754ddd5c in QDirIterator::QDirIterator(QString const&, QStringList const&, QFlags, QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x754d6dcc in QDir::entryList(QStringList const&, QFlags, QFlags) const () at /usr/lib/libQt5Core.so.5 #7 0x7fffbdb12bf5 in (anonymous namespace)::scanIncludePaths(QString const&, QDir const&, int) (identifier=..., dir=..., maxDepth=maxDepth@entry=2) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:95 #8 0x7fffbdb12fbc in (anonymous namespace)::scanIncludePaths(QString const&, QDir const&, int) (identifier=..., dir=..., maxDepth=2, maxDepth@entry=3) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:105 #9 0x7fffbdb16ae3 in (anonymous namespace)::scanIncludePaths (includes=..., identifier=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:118 #10 0x7fffbdb16ae3 in (anonymous namespace)::includeFiles (file=..., declarations=..., identifier=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:390 #11 0x7fffbdb16ae3 in (anonymous namespace)::fixUnknownDeclaration(KDevelop::QualifiedIdentifier const&, KDevelop::Path const&, KDevelop::DocumentRange const&) (identifier=..., file=..., docrange=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:466 #12 0x7fffbdb172b6 in UnknownDeclarationProblem::solutionAssistant() const (this=0x7fff8d2e60f0) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/clang/duchain/unknowndeclarationproblem.cpp:520 #13 0x72e9a6f7 in KDevelop::ProblemNavigationContext::html(bool) (this=0x2601e40, shorten=) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/problemnavigationcontext.cpp:172 #14 0x72e9fc16 in KDevelop::AbstractNavigationWidget::update() (this=this@entry=0x2821c50) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:148 #15 0x72ea0800 in KDevelop::AbstractNavigationWidget::setContext(QExplicitlySharedDataPointer, int) (this=this@entry=0x2821c50, context=..., initBrows=initBrows@entry=400) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:116 #16 0x7fffc22c04ba in ContextBrowserPlugin::navigationWidgetForPosition(KTextEditor::View*, KTextEditor::Cursor) (this=this@entry=0x118bef0, view=view@entry=0xe91640, position=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:539 #17 0x7fffc22c20b2 in ContextBrowserPlugin::showToolTip(KTextEditor::View*, KTextEditor::Cursor) (this=0x118bef0, view=0xe91640, position=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:585 #18 0x7fffc22c3e4f in ContextBrowserHintProvider::textHint(KTextEditor::View*, KTextEditor::Cursor const&) (this=0x118c068, view=, cursor=...) at /home/stativ/aurbuild/kdevplatform-git/src/kdevplatform/plugins/contextbrowser/contextbrowser.cpp:407 #19 0x71a4ffbf in () at /usr/lib/libKF5TextEditor.so.5 #20 0x71b518a5 in () at /usr/lib/libKF5TextEditor.so.5 #21 0x755e9659 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #22 0x755f66d8 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #23 0x755ea473 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7629de0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x762a5581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x755bdde0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #27 0x756116ae in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #28 0x75611bd1 in () at /usr/lib/libQt5Core.so.5 #29 0x7fffec611587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #30 0x7fffec6117f0 in () at /usr/lib/libglib-2.0.so.0 #31 0x7fffec61189c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #32 0x7561270f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x755bc23a in QEventLoop::exe
[digikam] [Bug 438317] Annoying download binary message at startup
https://bugs.kde.org/show_bug.cgi?id=438317 --- Comment #15 from Lukas Jirkovsky --- What about solution similar to how wine handles it's gecko and mono packages? They can be installed system-wide using package manager, or automatically during first startup. The face recognition data can be released separately from digiKam. * the face recognition data would be released separately from digiKam, so they don't have to be updated with every digiKam release * digikam would have to check both system folder and user folder * nice to have: have the notification less obtrusive, something like the notifications in kate eg. when you reload a file. * nice to have #2: if the files are not available, disable the affected functionality and notify user that they need the data when they try to use it. This would improve at least the following use cases: * users that manage multiple computers would download the system-wide package once and install it everywhere * shared computers - the system-wide package would need to be installed only once rather than for every user * users of linux distros that prefer to use packages to download&install stuff * windows users and any other users that doesn't care about downloading data separately would download the data on startup if they wanted to * in the system-wide install scenarios, digiKam updates would not require re-downloading the data, because they would be released separately -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444442] Conversion from Sony ARW to DNG loses pixels on the right side of the image
https://bugs.kde.org/show_bug.cgi?id=42 --- Comment #6 from Lukas Jirkovsky --- (In reply to caulier.gilles from comment #5) > @lukas, > > digiKam 8.0.0 is out. This entry still valid with this release ? > > Best regards > > Gilles Caulier It's the same with 8.0.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460208] New: brush resizing using shift + drag is sticky (kxkb settings related)
https://bugs.kde.org/show_bug.cgi?id=460208 Bug ID: 460208 Summary: brush resizing using shift + drag is sticky (kxkb settings related) Classification: Applications Product: krita Version: 5.1.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: l.jirkov...@gmail.com Target Milestone: --- I don't know whether this is a problem with Krita or kxkb, but Krita is the only application that's experiencing some kind of problems, so I'm reporting here. SUMMARY When I resize brush using shift + drag, the resizing mode is not deactivated until I click on some menu/tool/layer. After a lot of experimentation I found out that it's related to kxkb setting "Switching to another layout -> Both Shifts together" STEPS TO REPRODUCE 1. Open "System Settings" 2. Go to Input Devices" -> "Keyboard" 3. In the "Layouts tab" in "Shortcuts for switching layout" group set "Both Shifts together" as the "Main shortcuts" (alternatively this can be changed in the "Advanced" tab) 4. Open Krita 5. Try to resize brush using Shift + drag OBSERVED RESULT The brush is kept being resized even when Shift is no longer pressed. EXPECTED RESULT The brush stops being resized. SOFTWARE/OS VERSIONS Note: this has been bugging me for a long time (at least over a year), so it's not specific to any KDE/krita version. Only now I tried to debug it by starting with a clean profile and then iteratively adding old config files until the problem reappeared. Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.13-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460208] brush resizing using shift + drag is sticky (kxkb settings related)
https://bugs.kde.org/show_bug.cgi?id=460208 --- Comment #1 from Lukas Jirkovsky --- I just noticed that if I change the layout switching to "both ctrls", ctrl will become "stuck" in krita, giving me the "sample color" tool whenever I touch ctrl. So it's not limited to shift only. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439135] Color management on Wayland
https://bugs.kde.org/show_bug.cgi?id=439135 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444442] Conversion from Sony ARW to DNG loses pixels on the right side of the image
https://bugs.kde.org/show_bug.cgi?id=42 --- Comment #9 from Lukas Jirkovsky --- Sorry it took me so long to test it. I'm afraid the behavior is the same, dng width is still 32 pixels less than ARW -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444442] New: Conversion from Sony ARW to DNG loses pixels on the right side of the image
https://bugs.kde.org/show_bug.cgi?id=42 Bug ID: 42 Summary: Conversion from Sony ARW to DNG loses pixels on the right side of the image Product: digikam Version: 7.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Bqm-DngConverter Assignee: digikam-bugs-n...@kde.org Reporter: l.jirkov...@gmail.com Target Milestone: --- SUMMARY The converted DNG files are missing the rightmost 32 pixels (grid lines?). This happens with ARW files from Sony A7RM3. I don't know whether other cameras are affected. The good folk at https://discuss.pixls.us/t/dng-output-slightly-cropped/27582/10 helped tremendously to identify the problem where I noticed that RawTherapee output is slightly cropped when using digiKam DNG compared to ARW. STEPS TO REPRODUCE 1. Convert Sony ARW file to DNG using digiKam's batch queue 2. Examine both files using rawpy[1] OBSERVED RESULT DNG output is missing 32 rightmost pixels. EXPECTED RESULT DNG contains the same data SOFTWARE/OS VERSIONS Arch Linux KDE Frameworks 5.87.0 Qt 5.15.2 ADDITIONAL INFORMATION I uploaded example DNG and ARW to my google drive (warning, large files): https://drive.google.com/file/d/14JYTnuSHCix3FEEzNrMugY1fRlwLyDPW/view?usp=sharing https://drive.google.com/file/d/1RHYFqE8gj0gXjG6SP539WfZVs1MlSvi1/view?usp=sharing [1] I used the following script to obtain the RAW data: ``` import rawpy import imageio import sys import os.path path = sys.argv[1] with rawpy.imread(path) as raw: imageio.imsave(os.path.basename(path)+'.tiff', raw.raw_image) ``` -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444442] Conversion from Sony ARW to DNG loses pixels on the right side of the image
https://bugs.kde.org/show_bug.cgi?id=42 --- Comment #1 from Lukas Jirkovsky --- I checked the conversion with old Canon EOS 400D CR2 files and the problem is not present. After comparing CR2 data and the DNG file, DNG is cropped to exclude left and top part of the RAW data that doesn't contain any image data. No useful data are excluded when converting Canon CR2. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444442] Conversion from Sony ARW to DNG loses pixels on the right side of the image
https://bugs.kde.org/show_bug.cgi?id=42 --- Comment #3 from Lukas Jirkovsky --- I'm not saying RawTherapee is not doing some funky business – I don't have good enough understanding of the format. However looking at the embedded raw data using rawpy I see that there are some usable data which are missing in DNG. The only explanation I can think of (with my zero knowledge of the format) is that these data are outside of region of interest defined in EXIF so digiKam throws them away assuming they are not usable. That's what I'm seeing with the Canon CR2 – with CR2 a different crop is present but the cropped area is empty, ie. no Bayer filter. So no data lost. To show the difference – this is how the raw data extracted from ARW look like: https://drive.google.com/file/d/1fivJ0q8Lc-ZDZbZLkRUKmg5lrJ0ljOyh/view?usp=sharing And this is how the raw data from DNG look like: https://drive.google.com/file/d/1rHQ6GQ5dls1xmIV8ZfCqIPC8Ks0aOrQj/view?usp=sharing I just bumped the exposure on both files so that they are not pitch black, no other changes. If you examine the right border you will see that there are more usable data in the ARW file. It seems a shame to throw useful data away. If my theory of these data being outside of the crop defined in EXIF, maybe digiKam could have an option to preserve these data? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438317] Annoying download binary message at startup
https://bugs.kde.org/show_bug.cgi?id=438317 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440365] New: digikam geolocation editor decimal separator broken in some locales
https://bugs.kde.org/show_bug.cgi?id=440365
Bug ID: 440365
Summary: digikam geolocation editor decimal separator broken in
some locales
Product: digikam
Version: 7.2.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Geolocation
Assignee: digikam-bugs-n...@kde.org
Reporter: l.jirkov...@gmail.com
Target Milestone: ---
SUMMARY
When entering a location in the geolocation editor, the decimal separator
doesn't work as expected when the locale uses decimal separator different from
'.'.
STEPS TO REPRODUCE
* Change to a locale that uses a different decimal separator. I'm using Czech
locale (uses ',' to separate decimals).
* When I try to input location as "49.68", the editor won't allow me to write
'.'.
* When I try to input location as "49,68", the editor will allow to enter the
location, but as soon as the changes are applied, the whole input field is
reset.
WORKAROUNDS
I found two workarounds.
One is to write only "49" first and then apply. Next select only the part after
'.' an overwrite it with the desired value ("68") here and apply.
The other one is to run digikam in eg. "C" locale.
SOFTWARE/OS VERSIONS
Digikam 7.2.0
OS: Arch Linux
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 440365] digikam geolocation editor decimal separator broken in some locales
https://bugs.kde.org/show_bug.cgi?id=440365 --- Comment #1 from Lukas Jirkovsky --- The problem also occurs in Digikam 7.3.0, KDE Frameworks 5.84.0, Qt 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 473757] New: Crash when opening a fits file
https://bugs.kde.org/show_bug.cgi?id=473757
Bug ID: 473757
Summary: Crash when opening a fits file
Classification: Applications
Product: kstars
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: l.jirkov...@gmail.com
Target Milestone: ---
Application: kstars (3.6.6 Stable)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.12-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
When opening the attached fits file, kstars always crash.
The crash can be reproduced every time.
-- Backtrace:
Application: KStars (kstars), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 musable (mem=) at malloc.c:3426
#7 __GI___libc_realloc (oldmem=0x2, bytes=57600) at malloc.c:3433
#8 0x7fd424c31514 in mem_truncate (handle=0, filesize=57600) at
/usr/src/debug/cfitsio/cfitsio-4.3.0/drvrmem.c:263
#9 0x7fd424c23325 in fftrun (status=0x7fff02a77354, filesize=57600,
fptr=0x7fd3dc001a00) at /usr/src/debug/cfitsio/cfitsio-4.3.0/cfileio.c:7698
#10 fftrun (fptr=0x7fd3dc001a00, filesize=57600, status=0x7fff02a77354) at
/usr/src/debug/cfitsio/cfitsio-4.3.0/cfileio.c:7682
#11 0x7fd424c7835e in ffrhdu (fptr=0x7fd3dc001a00, hdutype=0x7fff02a7712c,
status=0x7fff02a77354) at /usr/src/debug/cfitsio/cfitsio-4.3.0/fitscore.c:4469
#12 0x7fd424c6dc01 in ffrdef (fptr=fptr@entry=0x7fd3dc001a00,
status=status@entry=0x7fff02a77354) at
/usr/src/debug/cfitsio/cfitsio-4.3.0/fitscore.c:6865
#13 0x7fd424c6d11f in ffchdu (fptr=0x7fd3dc001a00, status=0x7fff02a77354)
at /usr/src/debug/cfitsio/cfitsio-4.3.0/fitscore.c:6658
#14 0x7fd424c24733 in ffflus (status=0x7fff02a77354, fptr=0x7fd3dc001a00)
at /usr/src/debug/cfitsio/cfitsio-4.3.0/buffers.c:578
#15 ffflus (fptr=0x7fd3dc001a00, status=0x7fff02a77354) at
/usr/src/debug/cfitsio/cfitsio-4.3.0/buffers.c:564
#16 0x55c2e63150e7 in FITSData::~FITSData() (this=0x55c2eac9db40,
this=) at
/usr/src/debug/kstars/kstars-3.6.6/kstars/fitsviewer/fitsdata.cpp:126
#17 0x55c2e6315641 in FITSData::~FITSData() (this=0x55c2eac9db40,
this=) at
/usr/src/debug/kstars/kstars-3.6.6/kstars/fitsviewer/fitsdata.cpp:132
#18 0x7fd4238c3f9e in QObject::event(QEvent*) (this=0x55c2eac9db40,
e=0x55c2ec5ebbc0) at kernel/qobject.cpp:1334
#19 0x7fd42457893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55c2eac9db40, e=0x55c2ec5ebbc0) at
kernel/qapplication.cpp:3640
#20 0x7fd42389c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55c2eac9db40, event=0x55c2ec5ebbc0) at
kernel/qcoreapplication.cpp:1064
#21 0x7fd4238a165b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55c2e8824580) at
kernel/qcoreapplication.cpp:1821
#22 0x7fd4238e76d8 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55c2e89b64c0) at kernel/qeventdispatcher_glib.cpp:277
#23 0x7fd42268da31 in g_main_dispatch (context=0x7fd418000ee0) at
../glib/glib/gmain.c:3460
#24 g_main_context_dispatch (context=0x7fd418000ee0) at
../glib/glib/gmain.c:4200
#25 0x7fd4226eacc9 in g_main_context_iterate.isra.0
(context=context@entry=0x7fd418000ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#26 0x7fd42268b0e2 in g_main_context_iteration (context=0x7fd418000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#27 0x7fd4238eb51c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55c2e89bb7d0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x7fd42389b404 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fff02a77800, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x7fd42389c8a3 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x7fd423d3bef2 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#31 0x7fd424576cda in QApplication::exec() () at
kernel/qapplication.cpp:2832
#32 0x55c2e6093830 in main(int, char**) (argc=,
argv=) at /usr/src/debug/kstars/kstars-3.6.6/kstars/main.cpp:386
[Inferior 1 (process 2947) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 473757] Crash when opening a fits file
https://bugs.kde.org/show_bug.cgi?id=473757 --- Comment #1 from Lukas Jirkovsky --- Created attachment 161186 --> https://bugs.kde.org/attachment.cgi?id=161186&action=edit the file that causes the crash -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 473757] Crash when opening a fits file
https://bugs.kde.org/show_bug.cgi?id=473757 --- Comment #3 from Lukas Jirkovsky --- Created attachment 161200 --> https://bugs.kde.org/attachment.cgi?id=161200&action=edit file that doesn't crash The interesting thing is that it doesn't crash with other 1D files. Eg. the attached axy.fits correctly complains that 1D files are not supported. Just that wcs.fits causes the crash. I've cfitsio 4.3.0 installed, which is the latest version. If you have a different version, I guess it might be bug in the cfitsio library. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 413682] New: Show gender on flash cards
https://bugs.kde.org/show_bug.cgi?id=413682 Bug ID: 413682 Summary: Show gender on flash cards Product: parley Version: 19.11.70 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: parley-bugs-n...@kde.org Reporter: l.jirkov...@gmail.com Target Milestone: --- It would be nice if it was possible to show gender of nouns on flash cards. It would help tremendously when learning new words using flash cards, and it would boost the practice results, too. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 394551] Connection Fails with no error message if share media '/media' doesn't exist
https://bugs.kde.org/show_bug.cgi?id=394551 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] Plasma Wayland: Mouse cursor huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] Plasma Wayland: Mouse cursor huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 --- Comment #5 from Lukas Jirkovsky --- I have the same problem on Arch Linux: Plasma: 5.11.3 KDE Frameworks 5.40 Wayland 1.14 Qt: 5.9.3 However, I think the problem may not be in Plasma but in Qt. The reason is that anything running XWayland (eg. firefox) or GTK3 has correct cursor size. The cursor also has the correct size when hovering over window decorations as mentioned in the original report. All Qt5-based apps (eg. kwrite, clementine...) have huge cursor size. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] Plasma Wayland: Mouse cursor huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 --- Comment #6 from Lukas Jirkovsky --- I forgot to mention that it happens only with Wayland, X11 is not affected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373766] New: KWin crash after logout from a different session
https://bugs.kde.org/show_bug.cgi?id=373766 Bug ID: 373766 Summary: KWin crash after logout from a different session Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: l.jirkov...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: 0. I was running ordinary Plasma Desktop 1. I selected "switch user" (or whatewer it is called in english localization) 2. logged in as a different user to Plasma 3. then I logged out from the second user and I was dropped back to my original session, but with a notification kwin has crashed -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e4e9d9840 (LWP 4705))] Thread 6 (Thread 0x7f1e1bdb4700 (LWP 8811)): #0 0x7f1e4e415551 in ppoll () at /usr/lib/libc.so.6 #1 0x7f1e4bac2ad9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f1e4bac43c8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f1e4ba7124a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1e4b8940f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f1e4b898d78 in () at /usr/lib/libQt5Core.so.5 #6 0x7f1e476ac454 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f1e4e41e7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1e1aef8700 (LWP 4813)): #0 0x7f1e476b210f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1e4aa08ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7f1e4aa08b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7f1e476ac454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f1e4e41e7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1e27fff700 (LWP 4765)): #0 0x7f1e4e415551 in ppoll () at /usr/lib/libc.so.6 #1 0x7f1e4bac2ad9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f1e4bac43c8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f1e4ba7124a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1e4b8940f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f1e4640a2d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f1e4b898d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f1e476ac454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1e4e41e7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f1e2f110700 (LWP 4724)): #0 0x7f1e4e415551 in ppoll () at /usr/lib/libc.so.6 #1 0x7f1e4bac2ad9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f1e4bac43c8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f1e4ba7124a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1e4b8940f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f1e455d4e55 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f1e4b898d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f1e476ac454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1e4e41e7df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1e35241700 (LWP 4715)): #0 0x7f1e4e41548d in poll () at /usr/lib/libc.so.6 #1 0x7f1e4d5558e0 in () at /usr/lib/libxcb.so.1 #2 0x7f1e4d557679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f1e36119449 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f1e4b898d78 in () at /usr/lib/libQt5Core.so.5 #5 0x7f1e476ac454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1e4e41e7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1e4e9d9840 (LWP 4705)): [KCrash Handler] #6 0x7f1e4e3b9efa in __memmove_sse2_unaligned_erms () at /usr/lib/libc.so.6 #7 0x7f1e472507ee in KWin::GLVertexBuffer::setData(int, int, float const*, float const*) () at /usr/lib/libkwinglutils.so.9 #8 0x7f1e4dfc1abe in () at /usr/lib/libkwin.so.5 #9 0x7f1e4dfc55e5 in KWin::SceneOpenGL::paintBackground(QRegion) () at /usr/lib/libkwin.so.5 #10 0x7f1e4dfad5f8 in KWin::Scene::paintSimpleScreen(int, QRegion) () at /usr/lib/libkwin.so.5 #11 0x7f1e4dfc1a43 in () at /usr/lib/libkwin.so.5 #12 0x7f1e4dfafdc4 in KWin::Scene::finalPaintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #13 0x7f1e4dfdf55f in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib/libkwin.s
[frameworks-kglobalaccel] [Bug 384601] New: regression: Shift+Alt+Arrow shortcuts stopped working
https://bugs.kde.org/show_bug.cgi?id=384601 Bug ID: 384601 Summary: regression: Shift+Alt+Arrow shortcuts stopped working Product: frameworks-kglobalaccel Version: 5.38.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: l.jirkov...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Since update to KDE Frameworks 5.38.0 the global shortcuts with Shift + Alt + Arrow stopped working. Steps to reproduce: 1. Open System Settings, go to Shortcuts -> Global Shortcuts 2. Assign a shortcut Shift + Alt + any arrow to any action. 3. apply the settings 4. try the shortcut Results: after pressing shortcut nothing happens Expected results: the configured action is performed Additional notes: I'm using Shift+Alt+left arrow to switch to desktop on the left and Shift+Alt+right to switch to desktop on the right in kwin group. I also tried to set Alt+Shift+up to increase volume in kmix and it didn't work either. Shortcuts such as Ctrl+Alt+arrow works fine -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 384597] Shift+alt+[arrow keys] and Shift+Meta+[arrow keys] shortcuts broken in 5.38.0
https://bugs.kde.org/show_bug.cgi?id=384597 --- Comment #14 from Lukas Jirkovsky --- Reverting the commit 2c20ddff034e4958bf0536ca91ae9e444955305d indeed fixes the bug. Seems graesslin was right about not trusting this change. Oh, the joys of being a maintainer... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 381277] kdev_includepathsconverter crash
https://bugs.kde.org/show_bug.cgi?id=381277 --- Comment #3 from Lukas Jirkovsky --- I did a quick check in debugger and the problem is in the ICore::self() returning null. Apparently, there's nobody creating an ICore instance in kdev_includepathsconverter. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 381277] New: kdev_includepathsconverter crash
https://bugs.kde.org/show_bug.cgi?id=381277 Bug ID: 381277 Summary: kdev_includepathsconverter crash Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: l.jirkov...@gmail.com Target Milestone: --- kdev_includepathsconverter crashes on use: Starting program: /usr/bin/kdev_includepathsconverter -a foo/bar /home/stativ/development/qux/include [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x0041a4a5 in GccLikeCompiler::GccLikeCompiler (this=0x64cf90, name=..., path=..., editable=, factoryName=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/gcclikecompiler.cpp:221 221 connect(ICore::self()->runtimeController(), &IRuntimeController::currentRuntimeChanged, this, &GccLikeCompiler::invalidateCache); (gdb) bt #0 0x0041a4a5 in GccLikeCompiler::GccLikeCompiler (this=0x64cf90, name=..., path=..., editable=, factoryName=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/gcclikecompiler.cpp:221 #1 0x00418e60 in ClangFactory::createCompiler (this=, name=..., path=..., editable=) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/compilerfactories.cpp:37 #2 0x0041933d in ClangFactory::registerDefaultCompilers (this=0x64bfe0, provider=0x62c960 ) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/compilerfactories.cpp:44 #3 0x00416fbb in CompilerProvider::CompilerProvider (this=0x62c960 , settings=, parent=) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/compilerprovider.cpp:115 #4 0x0040dbfd in SettingsManager::SettingsManager (this=0x62c960 ) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/settingsmanager.cpp:268 #5 SettingsManager::globalInstance () at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/settingsmanager.cpp:277 #6 0x0040b8e6 in IncludePathsConverter::addIncludePaths (this=this@entry=0x7fffe348, includeDirectories=..., projectConfigFile=..., subdirectory=...) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/includepathsconverter.cpp:80 #7 0x0040ae6f in main (argc=, argv=) at /home/stativ/aurbuild/kdevelop-git/src/kdevelop/languages/plugins/custom-definesandincludes/includepathsconverter.cpp:235 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 381277] kdev_includepathsconverter crash
https://bugs.kde.org/show_bug.cgi?id=381277 --- Comment #1 from Lukas Jirkovsky --- It's kdevelop master, 1a113601271917e4d47f42a391a757e25437cfcd -- You are receiving this mail because: You are watching all bug changes.
[markdownpart] [Bug 433619] Images which are referenced using relative routes are not seen
https://bugs.kde.org/show_bug.cgi?id=433619 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356574] New: Panel stays hidden when using auto hide and switch desktop on edge
https://bugs.kde.org/show_bug.cgi?id=356574 Bug ID: 356574 Summary: Panel stays hidden when using auto hide and switch desktop on edge Product: plasmashell Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: l.jirkov...@gmail.com When the switch desktop on edge and auto hide feature of a panel are enabled at the same time, the hidden panel never shows up when touching the edge. Reproducible: Always Steps to Reproduce: 1. Set the panel to "Auto Hide" 2. Go to System Settings -> Desktop Behavior -> Screen Edges and change"Switch desktop on edge" to "Always enabled" 3. move the cursor to the edge where the panel is supposed to show up Actual Results: Panel stays hidden Expected Results: The panel should show up This bug is new to Plasma 5.5, It used to work as expected on Plasma 5.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356574] Panel stays hidden when using auto hide and switch desktop on edge
https://bugs.kde.org/show_bug.cgi?id=356574 --- Comment #2 from Lukas Jirkovsky --- I'm not sure what you mean, so I will try to elaborate how to reproduce it under a new user (ie. clean configuration) and I'll try to add as much details as I can. Hopefully you will find an answer to your question there. After Plasma starts, the panel is on the bottom edge and it's set to always visible. We want to change that, so go to the panel settings and set the "Visibility" to "Auto Hide". Now the panel is hidden and whenever I touch the bottom edge with mouse cursor, the panel shows up. So far so good. Next go to the system settings and enable "Switch desktop on edge". I want to see the panel, so I move the mouse cursor to the bottom edge. But, alas, the panel stays hidden now matter how much I move the cursor to bottom. Instead, the edge is highlighted as active with blue. Some further notes -- This happens with the top edge edge, too. I didn't test it with a vertical panel on left or right edge as I use the left and right edge for desktop switching very often. With Plasma 5.4 and earlier, when I touched the bottom edge, the panel was immediately shown. I think the blue highlight was there, too, but I don't see that as a problem. Finally, what I described before was the simplest case to make the bug show up. My setup is actually more complicated. I don't know how much of a hassle it would be to keep the behaviour exactly the same, but it would be awesome if that behaviour was preserved. What I actually have is a setup with 6 virtual desktops in two rows with no wrap around. The panel is on the top edge. The case when switching desktops horizontally is simple. I just move the cursor over the left or right edge and the desktop switches. The bottom edge switches desktops in a similar manner. What is interesting is the behaviour of the top edge. When I'm in the top row of desktops, moving the cursor up only shows the panel. However, when I'm in the bottom row, moving the cursor up first shows the panel. Only moving it further causes the desktop to switch to the one on top of it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343539] "Draw intense colors in bold font" not respected with a fresh installation
https://bugs.kde.org/show_bug.cgi?id=343539 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 305554] Lyrics applet doesn't display correctly
https://bugs.kde.org/show_bug.cgi?id=305554 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 Lukas Jirkovsky changed: What|Removed |Added CC||l.jirkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
