[plasma-browser-integration] [Bug 470292] New: Web applications throw an exception when they use navigator.share
https://bugs.kde.org/show_bug.cgi?id=470292 Bug ID: 470292 Summary: Web applications throw an exception when they use navigator.share Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: mart...@saunois.net Target Milestone: --- SUMMARY I use a web application which exposes a button to share content to other users. The app uses the JS API navigator.share to implement that feature. Using it throws an exception in the JS console: Uncaught (in promise) DOMException: navigator.share can only be called in response to user interaction Disabling the extension solves the issue. STEPS TO REPRODUCE 1. Open the JS console of Firefox 2. Use an element in a web app that binds the event on the navigator.share method OBSERVED RESULT The exception is thrown and the content was not shared EXPECTED RESULT The content should have been shared (in the clipboard in my case) SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.5 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Latitude 7490 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 455749] New: White pixels on the panel corners with Breeze dark
https://bugs.kde.org/show_bug.cgi?id=455749 Bug ID: 455749 Summary: White pixels on the panel corners with Breeze dark Product: Breeze Version: 5.25.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mart...@saunois.net CC: uhh...@gmail.com Target Milestone: --- Created attachment 150026 --> https://bugs.kde.org/attachment.cgi?id=150026&action=edit A screenshot of my panel with the white corners SUMMARY Each corner of my panel has a white pixel when I use Breeze dark. I run the Wayland session. The problem occurs with floating and "normal" panels (with non-floating panel the pixels appear when it is not maximized). STEPS TO REPRODUCE 1. Enable Breeze Dark in the settings 2. Reduce the panel to be not maximized or enable floating mode OBSERVED RESULT A white pixel appears on each corner. EXPECTED RESULT The corners should have the same color than the panel. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.5-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 31.3 Gio of RAM Graphics Processor: AMD Radeon RX 5600 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B79 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444419] [wayland] - strange black line divides panel in two halves
https://bugs.kde.org/show_bug.cgi?id=19 Martial changed: What|Removed |Added CC||mart...@saunois.net --- Comment #13 from Martial --- Hello I confirm this bug on Arch. I will take a look tonight on my desktop which has an ATI GPU. Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.5 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444419] [wayland] - strange black line divides panel in two halves
https://bugs.kde.org/show_bug.cgi?id=19 --- Comment #14 from Martial --- Same bugs with my desktop: Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.15-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 31.3 Gio of RAM Graphics Processor: AMD Radeon RX 5600 XT -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444419] [wayland] - strange black line divides panel in two halves
https://bugs.kde.org/show_bug.cgi?id=19 --- Comment #24 from Martial --- I confirm. Their is no line in auto-hide mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365775] When back from a monitor sleep panels and widget migrated between monitors
https://bugs.kde.org/show_bug.cgi?id=365775 Martial changed: What|Removed |Added CC||mart...@saunois.net --- Comment #2 from Martial --- Hello I reproduce this bug on Wayland as well with almost the same hardware and software than Victoria. When my computer wakes-up my widgets and my wallpapers are swapped but the monitor setup itself remains correct. If I close my Plasma session and I login back, my layout is restored as expected. I could not reproduce in an Xorg session. Operating System: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 32 GiB of RAM Graphics Processor: Radeon RX 5600 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451350] Panel creates invisible edges on secondary monitors
https://bugs.kde.org/show_bug.cgi?id=451350 Martial changed: What|Removed |Added CC||mart...@saunois.net --- Comment #1 from Martial --- Created attachment 154751 --> https://bugs.kde.org/attachment.cgi?id=154751&action=edit Invisible panel triggers window maximization -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451350] Panel creates invisible edges on secondary monitors
https://bugs.kde.org/show_bug.cgi?id=451350 --- Comment #2 from Martial --- Created attachment 154752 --> https://bugs.kde.org/attachment.cgi?id=154752&action=edit Expected behavior To take this one I moved my panel at the bottom of my second screen which also remove this invisible top panel on my laptop monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451350] Panel creates invisible edges on secondary monitors
https://bugs.kde.org/show_bug.cgi?id=451350 --- Comment #3 from Martial --- I confirm this issue. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.12-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.5 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Latitude 7490 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401162] New: Kate crash on openning a file
https://bugs.kde.org/show_bug.cgi?id=401162 Bug ID: 401162 Summary: Kate crash on openning a file Product: kate Version: 18.08.0 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: martial.g...@mutech.ch Target Milestone: --- Application: kate (18.08.0) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.0-2-amd64 x86_64 Distribution: Debian GNU/Linux oldoldstable-updates (sid) -- Information about the crash: kate crash from some files not so special. For exemple I can open ESPEasyWiFiEvent.h from src/espeasy git clone (https://github.com/letscontrolit/ESPEasy) but crash with file ESPEasyWiFiEvent.ino The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa4aafeb800 (LWP 24440))] Thread 6 (Thread 0x7fa48bfff700 (LWP 24714)): #0 0x7fa4aeda1e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55cb11478d50) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fa4aeda1e6c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55cb11478d00, cond=0x55cb11478d28) at pthread_cond_wait.c:502 #2 0x7fa4aeda1e6c in __pthread_cond_wait (cond=0x55cb11478d28, mutex=0x55cb11478d00) at pthread_cond_wait.c:655 #3 0x7fa4b083f44b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa4a0a32d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fa4a0a36ae8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fa4a0a31e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fa4a0a34bb9 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fa4b083ec97 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa4aed9bf2a in start_thread (arg=0x7fa48bfff700) at pthread_create.c:463 #10 0x7fa4b0531edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fa49892b700 (LWP 24713)): #0 0x7fa4aeda1e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55cb11478d50) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fa4aeda1e6c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55cb11478d00, cond=0x55cb11478d28) at pthread_cond_wait.c:502 #2 0x7fa4aeda1e6c in __pthread_cond_wait (cond=0x55cb11478d28, mutex=0x55cb11478d00) at pthread_cond_wait.c:655 #3 0x7fa4b083f44b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa4a0a32d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fa4a0a36ae8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fa4a0a31e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fa4a0a34bb9 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fa4b083ec97 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa4aed9bf2a in start_thread (arg=0x7fa49892b700) at pthread_create.c:463 #10 0x7fa4b0531edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fa49912c700 (LWP 24710)): #0 0x7fa4aeda1e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55cb11478d50) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fa4aeda1e6c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55cb11478d00, cond=0x55cb11478d28) at pthread_cond_wait.c:502 #2 0x7fa4aeda1e6c in __pthread_cond_wait (cond=0x55cb11478d28, mutex=0x55cb11478d00) at pthread_cond_wait.c:655 #3 0x7fa4b083f44b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa4a0a32d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fa4a0a36ae8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fa4a0a31e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fa4a0a34bb9 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fa4b083ec97 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa4aed9bf2a in start_thread
[frameworks-syntax-highlighting] [Bug 401480] New: SIGSEGV, Segmentation fault on open aduino file *.ino on kwrite et kate
https://bugs.kde.org/show_bug.cgi?id=401480 Bug ID: 401480 Summary: SIGSEGV, Segmentation fault on open aduino file *.ino on kwrite et kate Product: frameworks-syntax-highlighting Version: 5.51.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: framework Assignee: kwrite-bugs-n...@kde.org Reporter: martial.g...@hb9tuh.org Target Milestone: --- SUMMARY SIGSEGV, Segmentation fault on open aduino file *.ino on kwrite et kate. Debian sid(amd64), libkf5syntaxhighlighting5:amd64 5.51.0-1 STEPS TO REPRODUCE 1. open arduino file with kate or kwrite like https://raw.githubusercontent.com/letscontrolit/ESPEasy/mega/src/ESPEasy.ino OBSERVED RESULT backtrace kwrite - Thread 1 "kwrite" received signal SIGSEGV, Segmentation fault. 0x77c6e66a in ?? () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 (gdb) bt #0 0x77c6e66a in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #1 0x75d3dd19 in KSyntaxHighlighting::AbstractHighlighter::highlightLine(QString const&, KSyntaxHighlighting::State const&) () at /usr/lib/x86_64-linux-gnu/libKF5SyntaxHighlighting.so.5 #2 0x77d43e3d in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #3 0x77ce7ba5 in KateBuffer::doHighlight(int, int, bool) () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #4 0x77cc84b3 in KTextEditor::DocumentPrivate::kateTextLine(int) () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #5 0x77d2c250 in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #6 0x77d24b9f in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #7 0x77d27a21 in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #8 0x77d2954a in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #9 0x77d63c0a in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #10 0x77d63ee4 in () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #11 0x77d4cb16 in KTextEditor::ViewPrivate::updateView(bool) () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #12 0x77ccb464 in KTextEditor::DocumentPrivate::makeAttribs(bool) () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #13 0x77ccb4db in KTextEditor::DocumentPrivate::bufferHlChanged() () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #14 0x77ce79a9 in KateBuffer::setHighlight(int) () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #15 0x77cdad15 in KTextEditor::DocumentPrivate::updateFileType(QString const&, bool) () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #16 0x77cddf79 in KTextEditor::DocumentPrivate::openFile() () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #17 0x77b30a11 in () at /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5 #18 0x77b319a6 in KParts::ReadOnlyPart::openUrl(QUrl const&) () at /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5 #19 0x77cd24e1 in KTextEditor::DocumentPrivate::openUrl(QUrl const&) () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #20 0x5556138a in () #21 0x55563688 in () #22 0x55563812 in () #23 0x7687028b in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x771b6ee2 in QAction::triggered(bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x771b94f0 in QAction::activate(QAction::ActionEvent) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x772a4c8d in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x772a4ec5 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7738ec0a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x771fb7c8 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7738ecb3 in QToolButton::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x771bd491 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x771c4d18 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x76847039 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x771c4019 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x77216304 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x77218e8e in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #37 0x771bd491 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-l
[frameworks-syntax-highlighting] [Bug 401480] SIGSEGV, Segmentation fault on open aduino file *.ino & kwrite et kate
https://bugs.kde.org/show_bug.cgi?id=401480 Martial Guex changed: What|Removed |Added Summary|SIGSEGV, Segmentation fault |SIGSEGV, Segmentation fault |on open aduino file *.ino |on open aduino file *.ino & |on kwrite et kate |kwrite et kate -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 401480] SIGSEGV, Segmentation fault on open aduino file *.ino & kwrite et kate
https://bugs.kde.org/show_bug.cgi?id=401480 --- Comment #2 from Martial Guex --- Created attachment 116548 --> https://bugs.kde.org/attachment.cgi?id=116548&action=edit Custom syntax highlight for arduino making kate crash (memory protect) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 401480] SIGSEGV, Segmentation fault on open aduino file *.ino & kwrite et kate
https://bugs.kde.org/show_bug.cgi?id=401480 --- Comment #3 from Martial Guex --- Created attachment 116549 --> https://bugs.kde.org/attachment.cgi?id=116549&action=edit Custom file for syntax highlight for arduino, it's generate an kate crash (memory protect) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 401480] SIGSEGV, Segmentation fault on open aduino file *.ino & kwrite et kate
https://bugs.kde.org/show_bug.cgi?id=401480 --- Comment #4 from Martial Guex --- Oops -:( I found the same custom highlight file for arduino on two folders ~ / .kde / share / apps / katepart / syntax / and / usr / share / katepart5 / syntax /. I deleted files and the problem is gone. I attached this file to check on your side. Inadvertently I joined the same file twice to improve the definition so if you have a way to remove one, I did not find a way to do it. Sorry for the inconvenience to everyone. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 149372] SCHEMA : add comments and internationalization support for Tags
https://bugs.kde.org/show_bug.cgi?id=149372 --- Comment #18 from Jean-Martial NDOUTOUME NFENGONE --- > confirm that the issue still persists Yes, still no description field for tags in digiKam 7.8.0 :-( -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 357782] New: KDevelop icon is missing under Windows
https://bugs.kde.org/show_bug.cgi?id=357782 Bug ID: 357782 Summary: KDevelop icon is missing under Windows Product: kdevelop Version: 4.90.90 Platform: MS Windows URL: http://www.mirari.fr/lwH4.png OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mdemol...@gmail.com Windows 7 x64. KDEvelop 4.90.90, installed with http://krf.kollide.net/files/work/kdevelop/kdevelop-x64-setup-5.0.0-20160401.exe The KDevelop icon is missing, so Windows use the default application icon : http://www.mirari.fr/lwH4.png Reproducible: Always Steps to Reproduce: 1. Install KDEvelop Actual Results: Windows uses the default application icon Expected Results: Windows uses the KDevelop icon -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359626] New: Project creation: "Get More Templates" broken
https://bugs.kde.org/show_bug.cgi?id=359626 Bug ID: 359626 Summary: Project creation: "Get More Templates" broken Product: kdevelop Version: 4.90.90 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: application templates Assignee: kdevelop-bugs-n...@kde.org Reporter: mdemol...@gmail.com Using: - KDevelop d/l from here : http://krf.kollide.net/files/work/kdevelop/kdevelop-x64-setup-5.0-20160121.exe - Windows 7 x64 When creating a new project, the "Get More Templates" button makes the "Get Hot New Stuff" window to pop, but it won't show any template. Reproducible: Always Steps to Reproduce: 1. Start KDevelop 2. Open the "Create New Project" window 3. Click the "Get More Templates" button Actual Results: The window doesn't show any template. The activity indicator "works" as long as the window is opened. (By the way, I let it "working" a whole night, seems there is actually no timeout) Expected Results: The window showes the online available templates Millian said me that on IRC : >>> [21/02/2016 11:15:21] Folco: afaik its also broken under linux But I didn't try myself. Thanks guys for that great software \o/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359717] New: The tooltip won't disappear if a semantic problem exists
https://bugs.kde.org/show_bug.cgi?id=359717 Bug ID: 359717 Summary: The tooltip won't disappear if a semantic problem exists Product: kdevelop Version: 4.90.90 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: mdemol...@gmail.com OS: Win 7 x64 KDevelop d/l from here : http://krf.kollide.net/files/work/kdevelop/kdevelop-x64-setup-5.0-20160121.exe Two screenshots to explain: - http://www.mirari.fr/frx7.png - http://www.mirari.fr/BMSp.png First screenshot, the tooltip appears normally when "HeapDeref" is hovered. OK. The arrows showes two directions : - if the mouse follows the red arrow, the whole tooltip disappears - if the mouse follows the green arrow, only the top half of the tooltip disappears (second screenshot) Reproducible: Always Steps to Reproduce: Hard to say, sorry. I tried with a simple Hello World project and I couldn't. I get that with a slightly-customized GCC/binutils toolchain, but it's really simple to install (on Windows) or compile (on Linux). If someone wants to test, mail me, I will explain how to setup and reproduce. Actual Results: The tooltip doesn't disappear when unfocused Expected Results: The tooltip disappear when unfocused -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359718] New: The "Problem on semantic" analysis box won't disappear on Alt-Tab
https://bugs.kde.org/show_bug.cgi?id=359718 Bug ID: 359718 Summary: The "Problem on semantic" analysis box won't disappear on Alt-Tab Product: kdevelop Version: 4.90.90 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: mdemol...@gmail.com OS: Win 7 x64 KDevelop d/l here: http://krf.kollide.net/files/work/kdevelop/kdevelop-x64-setup-5.0-20160121.exe Reproducible: Always Steps to Reproduce: 1. Start KDevelop, a new session, and a new terminal project to get a simple C++ Hello World 2. Right under the "#include " line, add this one: void func() __attribute__ ((foobar)); "foobar" should be underlined 3. Put the mouse over "foobar", the box "Problem in semantic analysis" appears 4. Hit Alt-Tab Actual Results: The box is always visible on the top of the new window, and will stay here until you go back to KDevelop Expected Results: The box disappears on Alt-Tab hit. This bug looks like this one : https://bugs.kde.org/show_bug.cgi?id=358499 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359720] New: Wrong question about a deleted session when opening one with the same name
https://bugs.kde.org/show_bug.cgi?id=359720 Bug ID: 359720 Summary: Wrong question about a deleted session when opening one with the same name Product: kdevelop Version: 4.90.90 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: session support Assignee: kdevelop-bugs-n...@kde.org Reporter: mdemol...@gmail.com OS: Win 7 x64 KDevelop from here: http://krf.kollide.net/files/work/kdevelop/kdevelop-x64-setup-5.0-20160121.exe Reproducible: Always Steps to Reproduce: 1. In an already running KDevelop, click "Session -> Start New Session" 2. Create a project at the default location, name it "abc". So it will create a directory "abc" and some files 3. Close the KDevelop instance of "abc", and delete the "abc" folder and its content 4. From the initial KDevelop, click again "Session -> Start New Session". 5. Create a project, same place, same name Actual Results: At project creation, you get a dialog "Project already opened. The project you're trying to open is already open in at least one session ..." Expected Results: The project is created again, without prompting about a non-existing session If you repeat the procedure (steps 1, 2, 3), you will get a dialog with more and more "abc" sessions as on this screenshot : http://www.mirari.fr/yDSZ.png -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359761] New: Invalid rule detection
https://bugs.kde.org/show_bug.cgi?id=359761 Bug ID: 359761 Summary: Invalid rule detection Product: kdevelop Version: 4.90.90 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Build tools: Custom Makefiles Assignee: kdevelop-bugs-n...@kde.org Reporter: mdemol...@gmail.com OS: Win 7 x64 KDevelop from here: http://krf.kollide.net/files/work/kdevelop/kdevelop-x64-setup-5.0-20160121.exe Here a screenshot. You can see the whole Makefile. In the project pane, you can see that a "OBJ=$(SRC" rule has been added. It seems to be a wrong rule detection caused by the semi-colon in the variable definition. Reproducible: Always Steps to Reproduce: 1. Write a makefile with a variable containing a semi-colon Actual Results: An invalid rule is created in the project pane Expected Results: Better Makefile rule detection, no invalid rule created -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359761] Invalid rule detection in Makefile makes the project tree odd
https://bugs.kde.org/show_bug.cgi?id=359761 Martial Demolins changed: What|Removed |Added Summary|Invalid rule detection |Invalid rule detection in ||Makefile makes the project ||tree odd -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359761] Invalid rule detection in Makefile makes the project tree odd
https://bugs.kde.org/show_bug.cgi?id=359761 --- Comment #1 from Martial Demolins --- Created attachment 97543 --> https://bugs.kde.org/attachment.cgi?id=97543&action=edit Invalid projet tree -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359770] New: The parser colorizes commented code
https://bugs.kde.org/show_bug.cgi?id=359770 Bug ID: 359770 Summary: The parser colorizes commented code Product: kdevelop Version: 4.90.90 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: mdemol...@gmail.com I have commented a macro (line 14: see the screenshot: http://www.mirari.fr/xqfZ.png ). But the symbol defined still remains colorized, and the tooltip appears when the mouse is above. Reproducible: Always Steps to Reproduce: I couldn't reproduce with a simple Hello World, so I archived the (tiny) project here : http://www.mirari.fr/zzxe.zip This is the project that you can see in the screenshot. The involved headers, if needed, are here: https://github.com/debrouxl/gcc4ti/tree/next/trunk/tigcc/include/C Actual Results: The commented code is colorized, the tooltip appears Expected Results: The comment code is totally grayed out. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359770] The parser colorizes commented code
https://bugs.kde.org/show_bug.cgi?id=359770 --- Comment #1 from Martial Demolins --- Maybe you noticed that the yellow background of the symbol has an offset of two characters with the real position of the symbol. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359770] The parser colorizes commented code
https://bugs.kde.org/show_bug.cgi?id=359770 --- Comment #2 from Martial Demolins --- More infos: After closing/re-opening KDevelop, I remove the double slash of the comment. Now the whole line is green: http://www.mirari.fr/yegW.png When the mouse is over the macro, the wrong tooltip appears: http://www.mirari.fr/A3Fk.png -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 361286] New: muon close authentication window close too quickly
https://bugs.kde.org/show_bug.cgi?id=361286 Bug ID: 361286 Summary: muon close authentication window close too quickly Product: muon Version: 5.4.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: martial.garch...@gmail.com CC: aleix...@kde.org, sit...@kde.org Cannot install any applications with muon as the window shuts down too quickly, I can't enter my password Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 361286] muon authentication window close too quickly
https://bugs.kde.org/show_bug.cgi?id=361286 martial garchery changed: What|Removed |Added Summary|muon close authentication |muon authentication window |window close too quickly|close too quickly -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 364751] New: Konkeror crash when open url on kmail
https://bugs.kde.org/show_bug.cgi?id=364751 Bug ID: 364751 Summary: Konkeror crash when open url on kmail Product: konqueror Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: martial.g...@mutech.ch Application: konqueror (4.14.20) KDE Platform Version: 4.14.21 Qt Version: 4.8.7 Operating System: Linux 4.6.0-1-amd64 x86_64 Distribution: Debian GNU/Linux 7-updates (n/a) -- Information about the crash: - What I was doing when the application crashed: Open url (https://groups.yahoo.com/neo/groups/N2PK-VNA/files/2N3904_Amp_4_Revision_3.pdf) on mail inside kmail -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f965690f900 (LWP 19461))] Thread 4 (Thread 0x7f962e6bd700 (LWP 19477)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f9655494384 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f9655486fe7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f9655493e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f96518db464 in start_thread (arg=0x7f962e6bd700) at pthread_create.c:334 #5 0x7f96540ede5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f96434d6700 (LWP 19463)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f9655494384 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f9655486fe7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f9655493e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f96518db464 in start_thread (arg=0x7f96434d6700) at pthread_create.c:334 #5 0x7f96540ede5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f9643cd7700 (LWP 19462)): #0 0x7ffdf8ebbc3f in clock_gettime () #1 0x7f96540faa26 in __GI___clock_gettime (clock_id=1, tp=0x7f9643cd69f0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f96554ee635 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f96555d5085 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f96555d394c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f96555d3a15 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f9650fe892d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f9650fe92cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f9650fe94ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f96555d4216 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7f96555a217f in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f96555a24e5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7f9655491549 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x7f964aecf64e in ?? () from /usr/lib/libkio.so.5 #14 0x7f9655493e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x7f96518db464 in start_thread (arg=0x7f9643cd7700) at pthread_create.c:334 #16 0x7f96540ede5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f965690f900 (LWP 19461)): [KCrash Handler] #6 0x7f9654941339 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x7f965494144f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #8 0x7f965494346a in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #9 0x7f9654941387 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x7f965494144f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #11 0x7f965494346a in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #12 0x7f964be5e85c in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_konqueror.so #13 0x004089cc in ?? () #14 0x00409aaf in ?? () #15 0x0040a19e in ?? () #16 0x0040555d in ?? () #17 0x7f96540255f0 in __libc_start_main (main=0x404980, argc=2, argv=0x7ffdf8e9bf88, init=, fini=, rtld_fini=, stack_end=0x7ffdf8e9bf78) at libc-start.c:291 #18 0x004063f9 in _start () Possible duplicates by query: bug 349736. Reported using DrKonqi -- You are receiving this mail because: You are watching all
