[kdevelop] [Bug 370311] New: KDevelop crashed during quit
https://bugs.kde.org/show_bug.cgi?id=370311 Bug ID: 370311 Summary: KDevelop crashed during quit Product: kdevelop Version: 5.0.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Application: kdevelop (5.0.1) Qt Version: 5.6.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.1-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: I run application and got message that run is not possible. After that I wanted quit KDevelop and it crashed. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef60f05800 (LWP 17331))] Thread 5 (Thread 0x7feef37fe700 (LWP 19260)): #0 0x7fef71796c4f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fef6cd4d234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fef6cd4d279 in () at /lib64/libQt5Script.so.5 #3 0x7fef7179166d in start_thread () at /lib64/libpthread.so.0 #4 0x7fef77910ded in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fef1bfff700 (LWP 17541)): #0 0x7fef77904f9d in poll () at /lib64/libc.so.6 #1 0x7fef70901a54 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fef70901b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fef7820d3ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fef781b8c9a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fef77ff237c in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fef7179166d in start_thread () at /lib64/libpthread.so.0 #8 0x7fef77910ded in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fef52efd700 (LWP 17338)): #0 0x7fef71796ff8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fef77ff7d06 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fef75a16568 in KDevelop::DUChainPrivate::CleanupThread::run() (this=0x2acb150) at /usr/src/debug/kdevplatform-5.0.1/language/duchain/duchain.cpp:282 #3 0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7fef7179166d in start_thread () at /lib64/libpthread.so.0 #5 0x7fef77910ded in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fef5af91700 (LWP 17334)): #0 0x7fef77904f9d in poll () at /lib64/libc.so.6 #1 0x7fef70901a54 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fef70901b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fef7820d3ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fef781b8c9a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fef77ff237c in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fef7a337615 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fef77ff6fb9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fef7179166d in start_thread () at /lib64/libpthread.so.0 #9 0x7fef77910ded in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fef60f05800 (LWP 17331)): [KCrash Handler] #6 0x057ae1c0 in () #7 0x7fef752c1376 in NotifyByAudio::~NotifyByAudio() () at /lib64/libKF5Notifications.so.5 #8 0x7fef752c1409 in NotifyByAudio::~NotifyByAudio() () at /lib64/libKF5Notifications.so.5 #9 0x7fef781e45f3 in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #10 0x7fef781ed1a4 in QObject::~QObject() () at /lib64/libQt5Core.so.5 #11 0x7fef752a4bf9 in (anonymous namespace)::Q_QGS_s_self::innerFunction()::Holder::~Holder() () at /lib64/libKF5Notifications.so.5 #12 0x7fef77851478 in __run_exit_handlers () at /lib64/libc.so.6 #13 0x7fef778514c5 in () at /lib64/libc.so.6 #14 0x7fef7783b607 in __libc_start_main () at /lib64/libc.so.6 #15 0x0040c0f9 in _start () at ../sysdeps/x86_64/start.S:118 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration
https://bugs.kde.org/show_bug.cgi?id=368420 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #2 from Piotr Mierzwinski --- Sorry. This was what produced by DrKonqi when I wanted close working in background KDevelop process. Before KDevelop only closed itself. I wasn't be able to run it again, because in background I had working KDevelop. I killed this process and this triggered DrKonqi. Today I tried to reproduce crash running KDevelop in dbg, but again KDevelop just closed its main window. I had to send couple times signal "CONT" (from System activity tool - invoked by Ctrl+Esc), to get prompt of dbg. After that I run command "cont" and again no prompt and nothing happened. I repeat this couple of time. Finally I run "kill -CONT kdevelop_pid" from konsole and after "cont" command in dbg returned: "Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault.". In backtrace I noticed that this is again crash in MainWindow: #8 0x77a8701b in KDevelop::MainWindow::~MainWindow() (this=this@entry=0x8e4f50, __in_chrg=, __vtt_parm=) at /home/piotra/build-repos/kdevplatform-git/src/kdevplatform/shell/mainwindow.cpp:158 I attach dbg output. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration
https://bugs.kde.org/show_bug.cgi?id=368420 --- Comment #3 from Piotr Mierzwinski --- In dbg output I got also message like this: Launch Configuration: "qtcmd2" "No environment group specified, looks like a broken configuration, please check run configuration 'qtcmd2'. Using default environment group." -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration
https://bugs.kde.org/show_bug.cgi?id=368420 --- Comment #4 from Piotr Mierzwinski --- Created attachment 101575 --> https://bugs.kde.org/attachment.cgi?id=101575&action=edit KDevelop dbg session -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration
https://bugs.kde.org/show_bug.cgi?id=368420 --- Comment #5 from Piotr Mierzwinski --- Sorry. Errata about sending signal. As you can check in attached dbg output I send also SIGTERM. Sending CONT and command "cont" in dbg leads to never ending loop. I repeated it couple times after that. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368420] KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration
https://bugs.kde.org/show_bug.cgi?id=368420
--- Comment #7 from Piotr Mierzwinski ---
OK. Sorry for not clear report. I didn't get a crash in result my activities
only main window of KDevelop disappears. Crash happens later.
Main windows of KDevelop disappears, but I can see working process in list of
processes. I'm not able to restore it (main window). I kill it and I get crash,
what is result of killing I suppose.
I can reproduce it every time. My steps are following:
1. To dependencies I add some subdirectory (main->sub1->sub2->sub3) of my
project ("Launch configuration", Action: Build)
2. I modify any file from this directory
3. I invoke "Run -> Execute Launch" (with selected top directory of project).
In this moment main window of KDevelop may disappears, if not I can see message
like below.
This is output from Build view:
/run/media/piotra/FreeAgent/piotr/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build>
make -j8 zipsubsystem.o
*** Killed process ***
Seems like KDevelop think that something is running, because both tool buttons
related with stopping running jobs are enabled. In first "Menu allowing to stop
individual jobs" I can see: "my_project_name, changed_file_name: build"
4. Again I invoke "Run -> Execute Launch"
In this moment main window of KDevelop disappears.
When I select as target binary file (I mean entry with the same icon like
already put by default executable file) also main window of KDevelop
disappears.
When I run it from konsole I can see such output in last lines:
Launch Configuration: "qtcmd2" "No environment group specified, looks like a
broken configuration, please check run configuration 'qtcmd2'. Using default
environment group."
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
The X11 connection broke: No error (code 0)
XIO: fatal IO error 13 (Brak dostępu) on X server ":0"
after 6882 requests (6882 known processed) with 0 events remaining.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 371018] New: CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018
Bug ID: 371018
Summary: CPP parser responds very slow after user action
Product: kdevelop
Version: 5.0.2
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
CPP parser responds in couple seconds for helper tool or for simple commenting
line.
For example
applying comment:for one line in file (~30kb) from:
- my project takes about 3 seconds
- kdevelop takes about 4 seconds
Similar time I get for helper tool. I need to wait couple seconds! This is not
much comfortable behavior comparing to my hardware (check end this report).
In my opinion this is serious regression comparing to kdevelop-4.7.x, where
application responds in less than 1 second.
I tested kdevelp-4.7.3 on Mageia 5 distribution where all are working on Sandy
Bridge i5-2410M
Reproducible: Always
Steps to Reproduce:
1. Open project kdevelop
2. Wait till kdevduchain cache finishes its building
3. Open file following file:
kdevelop-git/src/kdevelop/projectmanagers/cmake/cmakemanager.cpp
4. Jump to line: 193
In my version of kdevelop source this points to inside of loop for function:
CMakeManager::targets(). Please check below all function:
QList CMakeManager::targets() const
{
QList ret;
foreach(IProject* p, m_projects.keys())
{
ret+=p->projectItem()->targetList();
}
return ret;
}
I comment line starting with: "ret+="
Actual Results:
need to wait at least 3 seconds for applying comment (changing color this line)
Expected Results:
applying comment (changing color this line) should take less than 1 seconds (at
least on processor compared to i5 Sandy Bridge / Ivy Bridge).
My hardware is following: SkyLake i7-6700 + SSD m4 Crucial 128GB. I observe the
same behavior (the need of waiting couple seconds on respond) on Sandy Bridge
i5-2410M + HDD.
My settings for "Background parser" are following:
- checked: "Enabled Background Parser"
- Delay: 500ms
- Maximum Number of threads
My settings for "Clang Language Support" are following:
all checked, so:
- Add macros to code-completion
- Enable Look-ahead code-completion
- Forward declare assistant
I tested on version (day of build: 2016/10/17):
kdevplatform-git-debug-5.0.2.r13464
kdevelop-git-debug-5.0.2.r23476
Running environment: Plasma 5.8.1, Qt-5.7.0, KF-5.27, kernel 4.7.6-1-ARCH
x86_64
Distribution Antergos (up-to-date).
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 Piotr Mierzwinski changed: What|Removed |Added Platform|Other |Archlinux Packages CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #3 from Piotr Mierzwinski --- @Ian Haber I think parser working in background is required to properly update the "Problems". I mean update on a regular basis. I wonder why parser running for kdev-clang is such slow, even on strong hardware? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #6 from Piotr Mierzwinski --- Parser must be run automatically after every change. This is obvious. So I repeat the question: "Why the parser running for kdev-clang is such slow, even on strong hardware?" @Sven. You said: "we explicitly added a longer delay for some edit". Is this delay hard coded? Is this delay can't depend on power of processor? Is not possible to create bigger cache and hold it in memory? I think IDE is not the application running couple times a day. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #9 from Piotr Mierzwinski --- Sorry I'm not sure I got you fully :/. Parser is not slow, only delay(s) make it works slow :/. I understand that parser has to finish its work before I can generate completion list or helper content. So how to decrease this delay? I observe similar delays on i5 Sandy Bridge and i7 SkyLake (~3 sec.) and for sure there is big difference in power between both CPUs, so why this delay is so similar? I don't understand why processor speed can't help here. So what will help? I don't type super fast. Sometimes faster, sometimes slower. Function completer is due to helps me in completing code. Waiting on parser till it finish its work discourages of using completing or helper tool :-/. For me parser is slow, because simple commenting makes I have to wait couple seconds. Looking at I my example, what parser has to make analysis? This is couple lines of function and loop with one line body :/. I'm not aware how this parser works, but this is very uncomfortable during work on code :-(. > The parser is slow because parsing C++ correctly is complicated. Parser in KDevelop 4.7.x works much faster. For me it looks like some issue related with clang. I suppose that in previous KDevelop parser didn't base on clang. I don't know maybe its parsing wan't enough correctly :/. Some times ago Milian made some optimizations in parser. I was hope that parser thanks that will speed up, but this didn't happen :(. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #12 from Piotr Mierzwinski --- @Sven. Thanks for clear explanation. I hope Milian will find some solution on this annoying issue :/. @Ian. I set it on 4500 ms, but it doesn't help. Still after comment one line I have to wait couple seconds. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake
https://bugs.kde.org/show_bug.cgi?id=354143 Piotr Mierzwinski changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Piotr Mierzwinski --- Sorry, but for me this is not fixed. I expected quite different output. I mean output like this generated by KDevelop4 - attachment: "qtcmd2_build_kdevelop4_output (pretty output generated by KDevelop4" or same like is produced in terminal: attachment "kate_build_terminal_make_-j2". Other are wrong. Thus such output where in almost every lines I get percentage indicator. After this fix I get periodically percentage indicator. I made the tests with my project (qtcmd2) and with yours: kdevelop. I tested building with 2, 4, and 8 jobs. Before building I've checked only one plugin referring to build: * Settings -> Plugins: "Build project by CMake" In option "Loaded plugins" also there was visible "Building by make" despite in "Configure plugins" is unchecked. The most likely one is dependent on the second, so that's mean lack of consistency or minor bug. * Project configuration: Default cmake executable: /usr/bin/cmake (but after pressing OK it has been reset to empty value - It doesn't matter because cmake works) Generator: Unix Makefile Configure cmake settings: QT_QMAKE_EXECUTABLE /usr/bin/qmake-qt4 Configure Make settings: - test1: "Number of simultaneous jobs:" 8 - test2: "Number of simultaneous jobs:" 4 - test3: "Number of simultaneous jobs:" 2 Make executable: make Active environment profile: default In kdevelop case percentage indicator appeared only with only following lines: [ 6%] Automatic moc for target test_gdb [ 52%] Linking CXX executable debugeeqt In my project [ 37%] Scanning dependencies of target qtcmd2tarsubsystem [ 61%] Linking CXX shared library When I built using 2 jobs then there wasn't no one percentage indicator (despite there were "Scanning dependencies..." strings in output). And if you check attachments you will see that not everyone matching (to above template) lines have percentage indicator :/. So it means that this is randomly :(. Second issue is that sometimes lines are starting with a capital letter and sometimes not. Building in terminal I didn't notice it. This test I've made on Kubuntu 15.10 with following tools: # cmake --version cmake version 3.2.2 # make --version GNU Make 4.0 # gcc --version gcc (Ubuntu 5.2.1-22ubuntu2) 5.2.1 20151010 On the end I built my project being in terminal - attachment: "qtcmd2_build_j4_terminal_output". Thanks that I found where is the bug. It turned out that percentage indicator is displayed with lines where should not be displayed. There is in "Scanning dependencies" and should be for example in "Building ...". There is in every place where should not be. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake
https://bugs.kde.org/show_bug.cgi?id=354143 --- Comment #13 from Piotr Mierzwinski --- kdevelop and kdevplatform cloned at 30/11/2015 (branch 5.0). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake
https://bugs.kde.org/show_bug.cgi?id=354143 --- Comment #14 from Piotr Mierzwinski --- Created attachment 95831 --> https://bugs.kde.org/attachment.cgi?id=95831&action=edit qtcmd_build (jobs: 2, 4, 8) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake
https://bugs.kde.org/show_bug.cgi?id=354143 --- Comment #15 from Piotr Mierzwinski --- Created attachment 95832 --> https://bugs.kde.org/attachment.cgi?id=95832&action=edit kdevelop build output (jobs: 2, 4, 8) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake
https://bugs.kde.org/show_bug.cgi?id=354143 --- Comment #16 from Piotr Mierzwinski --- Created attachment 95833 --> https://bugs.kde.org/attachment.cgi?id=95833&action=edit qtcmd2_build_j4_terminal_output -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake
https://bugs.kde.org/show_bug.cgi?id=354143 --- Comment #18 from Piotr Mierzwinski --- To avoid misunderstanding. We are talking here about view called: "Build". And I wasn't in mind any filtering - meaning putting something in edit box placed on top of this view. > ... the filterting system is flawed I'm not sure what filtering your are talking about :/. I would like to get pretty output during build the project. The same like in KDevelop4. The same like I can see in terminal when I run make command. I attached examples. In KDevelop5 this still (after your last fix) doesn't work correct. If you want to "get rid off it completely" filtering described by me on top of this message then I don't mind. I don't use it at all. Very often I use filtering placed in "Run" view. And by the way it still doesn't work well. Soon I will report the bug. And back to the problem. For me this bug looks like mistake in some condition using in code to producing this output. Considering my description in previous post, I think enough would be just reversing some condition and all would be fine. Sorry, I'm not aware of code, so this is only guess. Similar like the further thinking. I'm not sure what you mean when you are talking "rewrite". I think compiler/make command returns its output somewhere (maybe to some QString buffer if you are using QProcess to run compiler/make command) and KDevelop just filters and prints it. So it is just sending not rewriting. What is the problem in the correct return of output produced by make command (in KDevelop5)? In my opinion - "fixing by removing" not always is good approach to solve the problem. This is limiting the functionality what was working before. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364906] New: Adapt signature breaks code if in declaration of function there is no parameter name
https://bugs.kde.org/show_bug.cgi?id=364906
Bug ID: 364906
Summary: Adapt signature breaks code if in declaration of
function there is no parameter name
Product: kdevelop
Version: git master
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
There is following code:
declaration (header file):
void slotUrlActivated(const QUrl&);
definition (cpp file):
void MainWindow::slotUrlActivated( const QUrl &u )
{
qDebug() << "MainWindow::slotUrlActivated" << u.path();
}
Being in header file.
In above declaration I insert single space before "const" and after ampersand.
Appears helper: "Adapt signature 1. Update definition signature 0. Hide". I
choose 1
In result code becomes broken - a bit in declaration, and more in definition.
Reproducible: Always
Actual Results:
header:
void MainWindow::slotUrlActivated ( const QUrl & )
;
definition:
void MainWindow::slotUrlActivated( const QUrl &u )
{
qDebug() << "MainWindow::slotUrlActivated" << .path();
}
Expected Results:
header:
void MainWindow::slotUrlActivated ( const QUrl & );
definition:
void MainWindow::slotUrlActivated( const QUrl &u )
{
qDebug() << "MainWindow::slotUrlActivated" << u.path();
}
KDevelop and KDevplatform cloned and built at Jun 13, 2016. Branch 5.0.
Plasma 5.6.5, KF-5.23 built with Qt-5.6.0
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 364906] Adapt signature breaks code if in declaration of function there is no parameter name
https://bugs.kde.org/show_bug.cgi?id=364906 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Sorry for mistake. Expected Results: header: void slotUrlActivated ( const QUrl & ); -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 365420] New: Use of "Adapt signature" for rename argument in constructor inserts keyword void in declaration
https://bugs.kde.org/show_bug.cgi?id=365420
Bug ID: 365420
Summary: Use of "Adapt signature" for rename argument in
constructor inserts keyword void in declaration
Product: kdevelop
Version: git master
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
I rename argument in constructor definition (cpp file). After choosing "Update
declaration signature" in "Adapt Signature" helper I get constructor as void
type in declaration (header).
There is code
cpp file:
MyClass::MyClass( int *pointer, const QString &string )
{
}
header file:
MyClass( int *pointer, const QString &string );
For example I rename string to string2 and chose "Update declaration
signature" in "Adapt Signature".
Reproducible: Always
Steps to Reproduce:
1. Rename one of parameter in constructor
2. Choose "Update declaration signature" in "Adapt Signature"
3. Check header file
Actual Results:
MyClass::MyClass( int *pointer, const QString &string2 )
{
}
header file:
void MyClass ( int *pointer, const QString &string2 );
Expected Results:
MyClass::MyClass( int *pointer, const QString &string2 )
{
}
header file:
MyClass ( int *pointer, const QString &string );
KDevelop and KDevPlatform cloned and built from branch 5.0, at 08-07-2016
Plasma 5.7.0, KFrameworks 5.23, Qt-5.7
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 358799] Use of "Update definition signature" in "Adapt Signature" breaks declaration of function if its argument has default value
https://bugs.kde.org/show_bug.cgi?id=358799
Piotr Mierzwinski changed:
What|Removed |Added
Version|4.90.91 |git master
Summary|Function "Update|Use of "Update definition
|declaration signature" |signature" in "Adapt
|breaks declaration if |Signature" breaks
|inside there is default set |declaration of function if
|parameter |its argument has default
||value
Platform|Kubuntu Packages|Archlinux Packages
--- Comment #3 from Piotr Mierzwinski ---
Below please fine example for the version of KDevelop and KDevPlatform cloned
and built from branch 5.0, at 08-07.2016.
There is simple function:
declaration:
void foo( bool param = true );
definition:
void MyClass::foo( bool param )
{
}
In declaration of function I rename param to param2. And now choosing "Update
definition signature" from "Adapt Signature" helper breaks declaration. I get
code like this:
declaration
void MyClass::foo ( bool param2 )
;
definition (no change):
void MyClass::foo( bool param )
{
}
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 365437] New: Rename local variable using "Rename" assistant breaks code
https://bugs.kde.org/show_bug.cgi?id=365437
Bug ID: 365437
Summary: Rename local variable using "Rename" assistant breaks
code
Product: kdevelop
Version: git master
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
There is following code:
void MyClass::foo( bool param )
{
bool stat;
QString string;
if (param) {
if (string.isEmpty())
stat = true;
else
stat = false;
}
}
I rename "stat" variable to "stat2". Choosing "Rename stat to stat2" makes that
in code are inserted two (opening) curly brackets.
Reproducible: Always
Steps to Reproduce:
1. Rename local variable what is used inside of block of code like above
2. Choose "Rename old_name to new_name"
3.
Actual Results:
void MyClass::foo( bool param )
{
bool stat2;
QString string;
if (param) {
if (string.isEmpty())
{
stat2 = true;
else
{
stat2 = false;
}
}
Expected Results:
void MyClass::foo( bool param )
{
bool stat2;
QString string;
if (param) {
if (string.isEmpty())
stat2 = true;
else
stat2 = false;
}
}
KDevelop and KDevPlatform cloned and built from branch 5.0, at 08-07.2016.
Plasma 5.7.0, KFrameworks 5.23, Qt-5.7.0
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 365437] Rename local variable using "Rename" assistant breaks code
https://bugs.kde.org/show_bug.cgi?id=365437
Piotr Mierzwinski changed:
What|Removed |Added
CC||piotr.mierzwin...@gmail.com
--- Comment #1 from Piotr Mierzwinski ---
Second example:
The same, as described above, is happened when I try to rename argument "e" in
below function to "e2"
void MyClass::foo2( QEvent *e )
{
bool stat = true;
int a = 1;
if (stat) {
if (a == 1)
e->accept();
else
e->ignore();
}
}
After using Rename assistant I get following code:
void MyClass::foo2( QEvent *e2 )
{
bool stat = true;
int a = 1;
if (stat) {
if (a == 1)
{
e2->accept();
else
{
e2->ignore();
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 365413] Session restore of Konsole does not work if a tab's shell was in a folder not yet re-mounted
https://bugs.kde.org/show_bug.cgi?id=365413 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #3 from Piotr Mierzwinski --- >From my end I can confirm this issue. I experienced randomly not restored session of konsole. I wondered what is wrong, but one day I discovered the issue. Very often I run konsole with pure bash shell and two mc sessions. Sometimes I mount (manually - using tool from taskbar) external hard disk and open in mc some directory from this disk. I shut down system not changing this directory. Next day I power on computer and login into Plasma. Konsole is not restored. To be sure I did some tests with automatically mounted my external hard disk. In this case konsole was restored. In this moment this is my work around for this issue. I use Antergos, with: Plasma 5.7.1, KF 5.24, KApplications 16.04.3, Qt-5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 353343] CRASH in AssistantPopup::executeHideAction - assistantpopup.cpp:351
https://bugs.kde.org/show_bug.cgi?id=353343 --- Comment #3 from Piotr Mierzwinski --- No problem. Some time ago I switched to 5.0. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368415] New: KDevelop crashes during logging out or shutting down Plasma
https://bugs.kde.org/show_bug.cgi?id=368415 Bug ID: 368415 Summary: KDevelop crashes during logging out or shutting down Plasma Product: kdevelop Version: 5.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Almost every time when I logout/shutdown from Plasma KDevelop crashes. DrKoqi shows info about crash and after that all is quickly closing (Plasma is closing). Sometime in KDevelop I run build, and sometime nothing (work in idle mode). I don't modify any opened document. I logout from Plasma and KDevelop crashes. Sorry for missing debug backtrace but I don't know how to could I catch it. I click in DrKonqi and it is automatically closed. KDevelop is restored in every start of Plasma. Cache: kdevduchain is regenerated every start. It happens in 95% cases when I finish work in Plasma. Reproducible: Sometimes Steps to Reproduce: 1. Run KDevelop with some project and opened couple documents. 2. Run buid or wait about 10 min. 3. Logout of shutdown Plasma Actual Results: KDevelop crashes Expected Results: KDevelop should not crash. This issue might be related with: "Bug 364437 - kdevelop crash when logging out too quickly." https://bugs.kde.org/show_bug.cgi?id=364437 KF-5.25, Qt-5.7.0 Packages built from git (at 2016/09/05), brach 5.0. kdevelop-git-debug-5.0.0.r23429.f5cf3c6 kdevplatform-git-debug-5.0.0.r13375.d5aa9f3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368420] New: KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration
https://bugs.kde.org/show_bug.cgi?id=368420 Bug ID: 368420 Summary: KDevelop crashes when invoking Execute Launch after adding dependencies in Launch Configuration Product: kdevelop Version: 5.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Application: kdevelop (5.0.0) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I added detepdency as subdirectory of my project. I modified file inside this directory, saved. And invoked "Run -> Execute Launch" (with selected top directory of project). Unfortunately I got error in Build view. Sorry, I don't remember what. OK. So I run build and when finished again I invoked "Run -> Execute Launch". After this, KDevelop crashed and didn't want to run again. This backtrace is generated after I wanted finish the process in tool (called Ctrl+Esc). -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8fcd2e7800 (LWP 3405))] Thread 18 (Thread 0x7f8f3effd700 (LWP 4536)): #0 0x7f8fc39bf10f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8fbe28fac4 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f8fbe28fb09 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f8fc39b9454 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8fca0e97df in clone () from /usr/lib/libc.so.6 Thread 17 (Thread 0x7f8f5dffb700 (LWP 3710)): #0 0x7f8fca0e048d in poll () from /usr/lib/libc.so.6 #1 0x7f8fc19b7066 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8fc19b717c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f8fcaa0259b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f8fca9ac0da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f8fca7cf0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f8fca7d3d78 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f8fc39b9454 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f8fca0e97df in clone () from /usr/lib/libc.so.6 Thread 16 (Thread 0x7f8f5e7fc700 (LWP 3439)): #0 0x7f8fca0e048d in poll () from /usr/lib/libc.so.6 #1 0x7f8fc19b7066 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8fc19b717c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f8fcaa0259b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f8fca9ac0da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f8fca7cf0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f8fca7d3d78 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f8fc39b9454 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f8fca0e97df in clone () from /usr/lib/libc.so.6 Thread 15 (Thread 0x7f8f5f7fe700 (LWP 3434)): #0 0x7f8fc39bf10f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8fca7d4c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f8fbf0c236b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () from /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f8fbf0c7d30 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f8fbf0c2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f8fbf0c2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f8fbf0c2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f8fbf0c2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f8fbf0c2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f8fbf0c79d2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f8fbf0c2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f8fbf0c51f9 in ThreadWeaver::Thread::run() () from /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f8fca7d3
[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)
https://bugs.kde.org/show_bug.cgi?id=350675 --- Comment #5 from Piotr Mierzwinski --- The issue still persist in current version of KDevelop (app.built at 2016/09/05, from branch 5.0). In this moment my "Launch Configuration" is default (no dependencies skipping main binary/executable file suggested by KDevelop). In my structure of directories, invoking of F8 (with selected top directory) made building files in whole project. I mean all files including subdirectories. Proper rules are defined in CMakeLists.txt, so I think this is currect result. Unfortunately when I invoke "Run -> Execute Launch" or "Run -> Debug Launch" only changed files which are located in main directory are built. Others (in subdirectories) don't. So after change some file in subdirectory I need to remember to invoke build (F8) and then "Execute Launch". OK. Maybe this is because I don't have defined any dependencies for subdirectories. So I added this: "qtcmd2/plugins/preview/textviewer". I modified file inside this directory, saved. And invoked "Run -> Execute Launch" (with selected top directory). Unfortunately I got error in Build view. Sorry, I don't remember what. OK. So I run build and when finished again I invoked "Run -> Execute Launch". After this, KDevelop crashed and didn't want to run again :(. I reported this bug as Bug 368420. Below please find directories structure of my project (located here: git://git.qtcmd.org/qtcmd2.git). qtcmd2 qtcmd2/templates qtcmd2/libs qtcmd2/libs/xdgmime qtcmd2/libs/widgets qtcmd2/libs/utils qtcmd2/plugins qtcmd2/plugins/preview qtcmd2/plugins/preview/archiveviewer qtcmd2/plugins/preview/videoviewer qtcmd2/plugins/preview/audioviewer qtcmd2/plugins/preview/textviewer qtcmd2/plugins/preview/imageviewer qtcmd2/plugins/vfs qtcmd2/plugins/vfs/rarsubsystem qtcmd2/plugins/vfs/zipsubsystem qtcmd2/plugins/vfs/localsubsystem qtcmd2/plugins/vfs/ftpsubsystem qtcmd2/plugins/vfs/tarsubsystem qtcmd2/src qtcmd2/src/ui qtcmd2/src/preview qtcmd2/src/vfs Below rules from CMakeLists.txt: add_subdirectory(libs/widgets) add_subdirectory(libs/utils) add_subdirectory(libs/xdgmime) add_subdirectory(src) add_subdirectory(plugins/vfs/localsubsystem) add_subdirectory(plugins/vfs/rarsubsystem) add_subdirectory(plugins/vfs/tarsubsystem) add_subdirectory(plugins/vfs/zipsubsystem) add_subdirectory(plugins/vfs/ftpsubsystem) add_subdirectory(plugins/preview/textviewer) add_subdirectory(plugins/preview/imageviewer) add_subdirectory(plugins/preview/videoviewer) add_subdirectory(plugins/preview/audioviewer) add_subdirectory(plugins/preview/archiveviewer) In any case I attach my main CMakeLists.txt. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)
https://bugs.kde.org/show_bug.cgi?id=350675 --- Comment #6 from Piotr Mierzwinski --- Created attachment 100977 --> https://bugs.kde.org/attachment.cgi?id=100977&action=edit CMakeLists.txt from main directory -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)
https://bugs.kde.org/show_bug.cgi?id=350675 Piotr Mierzwinski changed: What|Removed |Added Platform|Other |Archlinux Packages Version|git master |5.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)
https://bugs.kde.org/show_bug.cgi?id=350675 --- Comment #7 from Piotr Mierzwinski --- Below please find "error" what I can see after "Run -> Execute Launch" (with adding one dependency) /run/media/piotra/FreeAgent/piotr/Projekty/Qt/qtcmd_work/qtcmd_git/qtcmd2/build> make -j8 *** Killed process *** -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 350675] Invoking debug or execute doesn't rebuild changed files (set in dependencies)
https://bugs.kde.org/show_bug.cgi?id=350675 --- Comment #8 from Piotr Mierzwinski --- I realized that the reason of "KDevelop crashed and didn't want to run again" was working kdevelop process in background. When I finish it I was able to report bug by Konqi. After that I was able to run KDevelop again. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 368423] New: After back from "Review patch" document gets title "Overview" instead of file name, and document becomes "Read only"
https://bugs.kde.org/show_bug.cgi?id=368423 Bug ID: 368423 Summary: After back from "Review patch" document gets title "Overview" instead of file name, and document becomes "Read only" Product: kdevplatform Version: 5.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: patchreview Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: david.nolden@art-master.de As in title "Review patch" option makes that after back to "Code" context document lose title on tab and becomes read only. Refresh doesn't help. There is need to close and open file again. Reproducible: Always Steps to Reproduce: 1. Open KDevelop with some (versioned) project (I use git). 2. Open some document 3. Make some changes, save file 4. Use "Git -> Show differences" 5. Back from "Review" using "Finish review" 6. Clicking RMB in document should be visible "Patch review" option - click into it 7. In this view click "Update" and "Finish review" 8. Being in "Code" context check title of changed document and try modify it Actual Results: Title on tab gets name "Overview" instead of actual file name and this document becomes read only. Expected Results: Title on tab should has the same name as original file. Should be possible to edit this document. KF-5.25, Qt-5.7.0 Packages built from git (at 2016/09/05), branch 5.0. kdevelop-git-debug-5.0.0.r23429.f5cf3c6 kdevplatform-git-debug-5.0.0.r13375.d5aa9f3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 365437] Rename local variable using "Rename" assistant breaks code
https://bugs.kde.org/show_bug.cgi?id=365437 Piotr Mierzwinski changed: What|Removed |Added Version|git master |5.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 343124] Use "Close all other output views" is breaking filtered Output in not closed view
https://bugs.kde.org/show_bug.cgi?id=343124
Piotr Mierzwinski changed:
What|Removed |Added
Resolution|FIXED |---
Platform|Mageia RPMs |Archlinux Packages
Status|RESOLVED|REOPENED
Version|1.7.0 |5.0.0
--- Comment #5 from Piotr Mierzwinski ---
In KDevelop 5 this bug still persist.
Below I remind the steps to reproduce this bug.
1. Run ("Execute Launch") your application in KDevelop what produce some
output. Close it
2. Run again your application
Now there is two Run outputs.
3. Put something in filter what matches to some string in Run output
You should receive some result, for example couple matching lines instead
of 100 (original output)
4. Click button on Run output with description "Close all other output views"
In result:
- filter filed is cleaned
- we are no able to restore original content of "Run" output
--
You are receiving this mail because:
You are watching all bug changes.
[kdevplatform] [Bug 343124] Use "Close all other output views" is breaking filtered Output in not closed view
https://bugs.kde.org/show_bug.cgi?id=343124 --- Comment #6 from Piotr Mierzwinski --- My system. Linux 4.7.2-1-ARCH KF-5.25, Qt-5.7.0 Packages built from git (at 2016/09/05), brach 5.0. kdevelop-git-debug-5.0.0.r23429.f5cf3c6 kdevplatform-git-debug-5.0.0.r13375.d5aa9f3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368659] New: Possibility of selecting (raising) window from list of windows placed on tool tip shown by Pager
https://bugs.kde.org/show_bug.cgi?id=368659 Bug ID: 368659 Summary: Possibility of selecting (raising) window from list of windows placed on tool tip shown by Pager Product: plasmashell Version: 5.7.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com In my opinion would be good to be able select and raise any window from Pager windows list. Current behavior is following. When we move mouse cursor over Pager, it shows tool tip contains list of applications placed on specified desktop. And now when we move cursor placed over Pager to its tool tip, it just disappears. Would be nice to just click on any of window title and raise it. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368659] Possibility of selecting (raising) window from list of windows placed on tool tip shown by Pager
https://bugs.kde.org/show_bug.cgi?id=368659 Piotr Mierzwinski changed: What|Removed |Added Severity|normal |wishlist CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367690] New: Git option in RMB is not available when I click in any place of versioned file
https://bugs.kde.org/show_bug.cgi?id=367690 Bug ID: 367690 Summary: Git option in RMB is not available when I click in any place of versioned file Product: kdevelop Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Several weeks ago after click by RMB in any place in versioned (by GIT) document was available option "Git". Recently this option is only available when we click in function name or member name or type of member. Click in other place shows menu without this option. For me it looks like regression. I don't know is this feature or bug. Reproducible: Always Steps to Reproduce: 1. open any project versioned with git 2. click RMB in any place of document, skipping function name, member name, member type 3. check availability of "Git" option" Actual Results: missing "Git" option in popping up menu invoked by RMB Expected Results: "Git" option should be placed in this menu no matter where user click (by RMB) in document kdevelop 5.0.0.r23419.7314e99 (built 22/08/2016, branch: 5.0) kdevplatform 5.0.0.r13346.09a1848 (built 22/08/2016, branch: 5.0) KFrameworks 5.25, Qt-5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367690] Git option in RMB is not available after click in any place of versioned file
https://bugs.kde.org/show_bug.cgi?id=367690 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Summary|Git option in RMB is not|Git option in RMB is not |available when I click in |available after click in |any place of versioned file |any place of versioned file -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367735] New: Problem in semantic analysis - cannot rename all variables after click in usage this variable
https://bugs.kde.org/show_bug.cgi?id=367735
Bug ID: 367735
Summary: Problem in semantic analysis - cannot rename all
variables after click in usage this variable
Product: kdevelop
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
There is an example of code:
foo()
{
QString sFileName = QFileDialog::getSaveFileName(this, tr("Save as"),
m_InitialPath);
if (! sFileName.isEmpty()) {
if (QFileInfo(sFileName).exists()) {
// file already exists
}
else
saveFile(sFileName);
}
}
I rename declaration of sFileName to sFileName2, so now first line looks like
this:
QString sFileName2 = QFileDialog::getSaveFileName(this, tr("Save as"),
m_InitialPath);
All occurrences for not declared variable are underlined. OK. I move cursor
over declaration and I get: Solution (1): Rename "sFileName" to "sFileName2".
But wait. In this place variable is already renamed :/. OK. Nevermind. I click
"Solution (1)" and all occurrences are renamed. Great. This is what I wanted.
I undo all changes, and again rename declaration in the same way. Now I move
cursor over first usage. This is mentioned line:
if (! sFileName.isEmpty())
I get the same tool tip, so again I click in "Solution (1)". After that only
occurrence under cursor is renamed. This is happen on every next usages of
variable. Why?
I'm not sure, but I think it was working before change with tool tip: "Problem
in semantic analysis". I mean all occurrences were always renamed.
Reproducible: Always
Steps to Reproduce:
1. Rename declaration of local variable
2. Try to use "Semantic analysis helper" for any usage of variable not for
declaration
3. Click "Solution (1)"
Actual Results:
Only occurrence under cursor is renamed
Expected Results:
All occurrences for selected variable should be renamed.
Thanks that kdevelop will avoid forcing an user to go back to declaration and
again back to current code.
kdevelop 5.0.0.r23419.7314e99 (built 22/08/2016, branch: 5.0)
kdevplatform 5.0.0.r13346.09a1848 (built 22/08/2016, branch: 5.0)
KFrameworks 5.25, Qt-5.7.0
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 355421] Konsole crashed on login
https://bugs.kde.org/show_bug.cgi?id=355421 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 355421] Konsole crashed on login
https://bugs.kde.org/show_bug.cgi?id=355421 --- Comment #9 from Piotr Mierzwinski --- Created attachment 100810 --> https://bugs.kde.org/attachment.cgi?id=100810&action=edit New crash information added by DrKonqi konsole (16.04.3) using Qt 5.7.0 - What I was doing when the application crashed: Situation the same as reported by Fedora users. Powered on the machine, logged in, and konsole cashed during Plasma session was restoring. Used componenets: Plasma 5.7.3, KF-5.25, Qt-5.7.0 -- Backtrace (Reduced): #5 0x7ff0309d9970 in Konsole::Session::sessionId() const () from /usr/lib/libkonsoleprivate.so.16 #6 0x7ff030a0fb48 in Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) () from /usr/lib/libkonsoleprivate.so.16 #7 0x7ff030a11bdf in Konsole::ViewManager::createView(Konsole::Session*, Konsole::ViewContainer*, int) () from /usr/lib/libkonsoleprivate.so.16 #8 0x7ff030a16150 in Konsole::ViewManager::createView(Konsole::Session*) () from /usr/lib/libkonsoleprivate.so.16 #9 0x7ff030a16c71 in Konsole::ViewManager::restoreSessions(KConfigGroup const&) () from /usr/lib/libkonsoleprivate.so.16 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367905] New: Breakpoint marker disappears from bar in editor after stopping application in debug mode
https://bugs.kde.org/show_bug.cgi?id=367905 Bug ID: 367905 Summary: Breakpoint marker disappears from bar in editor after stopping application in debug mode Product: kdevelop Version: 5.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: niko.s...@gmail.com As in title. After click in breakpoint in Breakpoints view is highlighted proper line in editor but on left bar there is no breakpoint marker (icon). Looks like something wasn't redraw. Uses icons style: Breeze. Reproducible: Always Steps to Reproduce: 1. Open at least two documents in KDevelop. 2. In first document set breakpoint (clicking in left bar in editor) and switch to second document 3. Run application in debug mode and make that application will stop on breakpoint (meet some conditions causing that falls into the trap) 4. Stop debugging by clicking button: "Stop all currently running jobs" 5. Open "Breakpoints" view and click into proper breakpoint (referring to previously set) Actual Results: In editor is highlighted correct line with breakpoint, but on left bar is missing breakpoint marker (icon) Expected Results: In editor is highlighted correct line with breakpoint, and on left bar is preset breakpoint marker (icon) kdevelop 5.0.0.r23419.7314e99 (built 22/08/2016, branch: 5.0) kdevplatform 5.0.0.r13346.09a1848 (built 22/08/2016, branch: 5.0) KFrameworks 5.25, Qt-5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359970] Methods of QSettings (Qt4) class are not parsed
https://bugs.kde.org/show_bug.cgi?id=359970 Piotr Mierzwinski changed: What|Removed |Added Resolution|--- |INVALID CC||piotr.mierzwin...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Piotr Mierzwinski --- Sorry. I close bug report due to my fault :(. When I added proper paths into "Project Configuration -> Language support -> Includes/Imports" parsing started work in mini test project, but I don't know why in big project (even after rebuild of cache) issue still persists :(. Probably some different parsing bugs block parsing these members :/. Neither refresh nor reopen file doesn't help. I observed that every methods which are inherited from QWidget (i.e.: setEnabled, setFocus) are correctly parsed, other don't. It refers also to other classes (like QLabel, QTimer, QPushButton) not only mentioned QSettings. Saying "proper paths" I meant paths to headers instead of paths to files contains bunch of headers inside. Proper paths for Kubuntu 15.10. /usr/include/qt4/QtCore/ /usr/include/qt4/QtGui/ /usr/include/qt4/QtNetwork/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360130] New: Crash after open System Settings adn selectin "Look of workspace"
https://bugs.kde.org/show_bug.cgi?id=360130 Bug ID: 360130 Summary: Crash after open System Settings adn selectin "Look of workspace" Product: systemsettings Version: 5.5.95 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Application: systemsettings5 (5.5.95) Qt Version: 5.6.0 Frameworks Version: Unknown Operating System: Linux 4.4.4-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: I've opened System Settings, selected "Look of workspace" and after ~2 sec. it crashed. -- Backtrace: Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb96587e800 (LWP 21579))] Thread 4 (Thread 0x7fb954336700 (LWP 21580)): #0 0x7fb961f4ff5d in poll () at /lib64/libc.so.6 #1 0x7fb95ff03ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fb95ff05697 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fb956866809 in QXcbEventReader::run() (this=0xb103c0) at qxcbconnection.cpp:1313 #4 0x7fb962641649 in QThreadPrivate::start(void*) (arg=0xb103c0) at thread/qthread_unix.cpp:340 #5 0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0 #6 0x7fb961f5bdad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb94bfff700 (LWP 21581)): #0 0x7fb95f1b3a64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7fb95f170409 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fb95f17051c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fb962856a4b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fb9440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fb96280234a in QEventLoop::exec(QFlags) (this=this@entry=0x7fb94bffeda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fb96263ca3c in QThread::exec() (this=this@entry=0x7fb965a2dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #6 0x7fb9659bd3e5 in QDBusConnectionManager::run() (this=0x7fb965a2dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:181 #7 0x7fb962641649 in QThreadPrivate::start(void*) (arg=0x7fb965a2dd40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #8 0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0 #9 0x7fb961f5bdad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fb942e7a700 (LWP 21586)): #0 0x7fb95f1b3a64 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7fb95f16fa30 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7fb95f170343 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7fb95f17051c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7fb962856a4b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fb93c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7fb96280234a in QEventLoop::exec(QFlags) (this=this@entry=0x7fb942e79db0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb96263ca3c in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x7fb960fda835 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7fb962641649 in QThreadPrivate::start(void*) (arg=0xf3b5e0) at thread/qthread_unix.cpp:340 #9 0x7fb95f69065d in start_thread () at /lib64/libpthread.so.0 #10 0x7fb961f5bdad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fb96587e800 (LWP 21579)): [KCrash Handler] #6 0x7fb941dd9eb2 in QQuickStyleItem::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) (this=) at /usr/lib64/qt5/include/QtQuick/5.6.0/QtQuick/private/qquickitem_p.h:877 #7 0x7fb941dd9eb2 in QQuickStyleItem::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) (this=0x10a2050, node=0x0) at Private/qquickstyleitem.cpp:1830 #8 0x7fb96129f460 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () at /lib64/libQt5Quick.so.5 #9 0x7fb96129fc50 in QQuickWindowPrivate::updateDirtyNodes() () at /lib64/libQt5Quick.so.5 #10 0x7fb9612a0bee in QQuickWindowPrivate::syncSceneGraph() () at /lib64/libQt5Quick.so.5 #11 0x7fb961270e56 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #12 0x7fb961272420 in QSGGuiThreadRenderLoop::exposureChanged(QQuickWindow*) () at /lib64/libQt5Quick.so.5 #13 0x7fb963746c5b in QWindow::event(QEvent*) (this=0x102f0a0, ev=) at kernel/qwindow.cpp:2096 #14 0x7fb9612a9c65 in QQuickWindow::event(QEvent*) () at /lib64/libQt5Quick.so.5 #15 0x7fb963d5440c in QAppli
[systemsettings] [Bug 360130] System Settings crashing after opening "Look of workspace"
https://bugs.kde.org/show_bug.cgi?id=360130 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Summary|Crash after open System |System Settings crashing |Settings adn selectin "Look |after opening "Look of |of workspace" |workspace" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360130] System Settings crashes after opening "Look of workspace"
https://bugs.kde.org/show_bug.cgi?id=360130 Piotr Mierzwinski changed: What|Removed |Added Summary|System Settings crashing|System Settings crashes |after opening "Look of |after opening "Look of |workspace" |workspace" -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358799] Function "Update declaration signature" breaks declaration if inside there is default set parameter
https://bugs.kde.org/show_bug.cgi?id=358799
Piotr Mierzwinski changed:
What|Removed |Added
CC||piotr.mierzwin...@gmail.com
--- Comment #1 from Piotr Mierzwinski ---
And the second example (met today):
I have declaration of method like in below code:
namespace MyNameSpace {
..
class MyClass : public AnotherClass
{
Q_OBJECT
public:
void init( QSettings *pSettings, QWidget *pParent );
...
Definition looks like this:
void MyClass::init( QSettings *pSettings, QWidget *pParent )
{
..
}
In declaration I insert on end of parameter list following string: ", bool
bInvokeDetection=false", and then declaration looks like this:
void init( QSettings *pSettings, QWidget *pParent, bool
bInvokeDetection=false );
I get helper "Adapt signature: Adapt definition signature" and I select "1".
Actual Results:
In result in definition file I get following change:
void MyNameSpace::MyNameSpace::MyClass::init(QSettings* pSettings, QWidget*
pParent, bool bInvokeDetection)
// body
}
As you can see. Definition has been totally broken. Even opening brace
disappeared.
Skipping that Source Formatter doesn't work (in attachment my setting).
Expected Results:
In result I expected something like this:
void MyClass::init( QSettings *pSettings, QWidget *pParent, bool
bInvokeDetection )
{
// body
}
Tested with KDevelop and KDevplatform cloned at February 28th, 2016 after 10pm
(branch 5.0).
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 358799] Function "Update declaration signature" breaks declaration if inside there is default set parameter
https://bugs.kde.org/show_bug.cgi?id=358799 --- Comment #2 from Piotr Mierzwinski --- Created attachment 97806 --> https://bugs.kde.org/attachment.cgi?id=97806&action=edit Settings of "Source Formatter" - tab Other -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518
--- Comment #61 from Piotr Mierzwinski ---
As I said earlier I'm working on Antergos (on this day) with the newest Plasma
(5.6.5), with the newest KF (5.23), the newest Qt 5 (5.6.1) and KDE
Applications 16.04.2.
I use konsole very often with running couple of cards (for example: pure
terminal, couple mc, and sometime mc run with root privileges - executed like
this: "sudo mc %s"). Konsole is opened every time when I work in Plasma desk.,
so I expect that after rerun of the system it will be restored. Unfortunately
doesn't. Recently I observed that sometimes is happened that konsole is not
restored when I run systemem next day. I suppose that this is related with
running root session ("sudo mc %s" session) in moment of system close or even
run and closed root session. As I remember, almost every time when I run such
session, konsole will be not restored, at all. This is a bit annoying, because
konsole has no option "Load saved/recent session/cards". Issue seems to be
happen randomly.
In my every Plasma session I run always one or more KWrite application(s), and
they are restored every time.
--
You are receiving this mail because:
You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 --- Comment #63 from Piotr Mierzwinski --- I don't think that good idea is blamed konsole for this. As I said this happens randomly. Today, after your post, I made couple of tests (several relogin and restarts) and every time all tabs were restored. In the same time I'm not sure that when I run computer tomorrow then konsole will be restored. This is happens sometimes. And I observed it couple of times within month. Today was last time when run computer fist time after back from work. Issue is a bit similar to this one placed in Qt 5.5.x. In this moment I'm not able to replicate the issue. I don't know why kwrite is restoring properly every time. I think that both are using the same XSMP protocol, what is probably built in KF libraries. I know that konsole does not restore running application after its restart. In my opinion it's shame. For me enough would be only run tabs with defined profile, so for example with pure terminal, mc, other defined profiles running in moment of closing. If automatically restoration is not possible then useful would be option what force running of saved tabs. I know, this is wish for konsole. I'm aware that this option option is not really needed if konsole is properly restored after relogin or restart. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 --- Comment #66 from Piotr Mierzwinski --- @Wolfgang Bauer Thanks for explanation. On begin I can say that happened what I supposed. So today after first login to Plasma, konsole has not been restored, at all. Maybe this is some bug in konsole. Yesterday, before shutting down the system I also run okular, and kate. Today all of them have been restored. > restoring them should work (or not) the same for both > But in the end it's the client's (i.e. the application's) job to save its > state correctly I know that in the moment of closing application its destructor are calling, actually QApplication/KApplication. So what is the difference in type of shutting (by server). When I log off (calling log off in Plasma) or shut down system (calling "turn of" in Plasma) then shutting should work the same. in This is my suspicion. The only one job what can do application in shutting down moment is saving it's state into some configuration file. Every other actions are managed by Qt/KF/ksmsever. As I suppose. And this is doing correct for login off and restart. For me it should just work for both (konsole and kwrite) the same. Sorry I repeat my self. Yesterday I reloged couple of times, also I restarted system. And konsole was restored every time. When yesterday I shut down the system and run it today, konsole has not been restored. I don't understand this. I don't know how exactly Plasma closing/shutting down its session, I suppose is using some qdbus command (example of shutting down: "qdbus org.kde.ksmserver /KSMServer logout 0 2 2"). Is this implemented by distribution or in K menu? And on end. You are comparing two Qt versions. Why openSuse doesn't use the newest Qt version, only its developers backported some fixes? Maybe in last Qt still persists some bug related with closing applications. @Chris I don't know what situation you meant, saying "konsole never ever get restored for me."? If this is just rerun of konsole thats OK. For me either konsole wasn't restored. If this is relogin/restart/shut down and run then in my opinion konsole should be restored every times when Plasma session is starting and proper option is turned on in Plasma setting (for example: "Restore previous session" in System settings). Maybe this is distro related. I don know. :/. I'll try to report it. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #62 from Piotr Mierzwinski --- (In reply to Storm Engineer from comment #58) > (In reply to Thomas Lübking from comment #57) > > Firefox or cairo-dock were certainly not targetted or affected by the > > related patches. > > I did some more testing, and indeed Qt apps (or at least most of them) seem > to get restored properly now. The following get restored: > - Dolphin > - Konversation > - Konsole > - Ksysguard > - KDE system settings > > The following do NOT get restored: > - Firefox > - Google Chrome > - VLC Media Player > - Cairo-Dock > > Isn't Chrome using Qt tho? I don't know. > > And I have no idea what may lie beneath this issue, I'm just a noob and all > I can do is telling what I experience. > > I have another issue which may be related, but the two are spanning across > different time frames so it doesn't seem likely. This issue is shutdown > being halt with "A stop job is running for session c2 of user" with a 1:30 > timeout counter. However, session restore was broken ever since I use > Plasma/KDE 5, which is more than a year I think, while this issue only > started 1-2 months ago. Also, the "stop job is running" issue appears > randomly, while session restore always failed consistently. The problem not restored GTK+ applications in Plasma 5.6.x (built with Qt 5.6.x) was cased removing support for XSM protocol: https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=5f0ca1305db4a925dbdbf927f541497be334feff https://bugs.kde.org/show_bug.cgi?id=362671 I reported bug related with restoring GTK+ applications, and before couple of days it has been restored. Check this report: https://bugs.kde.org/show_bug.cgi?id=362671 (fix applied in branch 5.6, branch 5.7 and master). -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #63 from Piotr Mierzwinski --- (In reply to Leslie Zhai from comment #61) > Yup also worked for ArchLinux now ;-) I use Antergos (Arch based distro) and I observed next problem. I mean that konsole is not restored in such case. One day I shut down system (calling proper option in K menu) and when next day I login konsole is not restored, wheras kwrite, kate, dolphin, okular are restored. This issue not happens when I shut down computer and run it again the same day. Additionally I tried shut down using qdbus command like this: "qdbus org.kde.ksmserver /KSMServer logout 0 2 2", but with the same result. So I wonder if this issue is related only for Arch based distributions or this is some bug in konsole :/. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 --- Comment #67 from Piotr Mierzwinski --- I think I found reason why konsole is not restored. Very often in konsole in run pure bash shell and two mc sessions. Sometimes I mount (manually - using tool from taskbar) external hard disk and open in mc some directory from this disk. I shut down system didn't changed directory. Next day I power on computer and login into Plasma. Konsole is not restored. To be sure I did some tests with automatically mounted my external hard disk. In this case konsole was restored. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362485] After refresh editor (F5) already set breakpoint(s) are disappearing
https://bugs.kde.org/show_bug.cgi?id=362485 Piotr Mierzwinski changed: What|Removed |Added Summary|Debug mode. After refresh |After refresh editor (F5) |editor (F5) already set |already set breakpoint(s) |breakpoint(s) are |are disappearing |disappearing| --- Comment #2 from Piotr Mierzwinski --- I happens also in Code perspective. Tested with KDevelop and KDevplatform cloned from 5.0 branch at 14.05.2016 Steps to Reproduce: 1. Open any cpp file 2. Set breakpoint 3. Refresh editor (press F5) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't expand automatically vertically
https://bugs.kde.org/show_bug.cgi?id=356211 Piotr Mierzwinski changed: What|Removed |Added Summary|In debug session "Variable |In debug session "Variable |ToolTip" doesn't resize |ToolTip" doesn't expand |vertically |automatically vertically -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 --- Comment #50 from Piotr Mierzwinski --- (In reply to Wolfgang Bauer from comment #48) > (In reply to Piotr Mierzwinski from comment #47) > > None of the tested by me applications are not restored after > > relogin/restart. > > Where's the problem then? Problem is that applications mentioned in next sentence are not restored after relogin. > I suppose there is a typo in there... ;-) Sorry for typo. English grammar is not my strength, se better would be when "are" has been replaced with "were" or usage: "there are not restored". > > I tested: Firefox, Thunderbird and new Opera. I think all > > of them are based on GTK2. > > Actually not. > At least Firefox can be build against GTK3 since a while and I think at > least some distributions do that (openSUSE not, yet). OK. About Firefox you are right. I retested it again and I can say that in Antergos Firefox is built using GTK3. > So this might just be your point of regression... The regression is that none of GTK2 and GTK3 applications there are not restored. This is regression comparing to previous Plasma, because In ver. 5.5.x it was working. I tested Kubuntu 16.04. BTW in Plasma 5 provided by this distribution applications based on KF are not restored. I'm not going to evolve this topic. Anyway they plan update to Plasma 5.6.x. > No idea about the others though. But I'm sure that the last two were built using GTK2. My test was following. I changed "Style of GNOME application" in "System Settings" and just restarted all tested applications. > > All tested by me KF applications (konsole, > > kwrite, dolphin) are restored correctly (including virtual desktop number). > > This proves IMHO that your problem is unrelated to *this* bug report, or the > other one I marked this as duplicate of, which is about a problem in Qt5 as > explained. Subject is "Plasma doesn't restore everything after a reboot". So maybe is too general. Author reported this bug wrote about problem with Konsole, Dolphin, Kate and restoring them including their opened tabs. After several posts someone started typing about most general problems with restoring other applications. Never mind. So maybe my problem is only partially related to reported problem. > > In Plasma 5.5.4 (ksmserver probably has the same version) Firefox and > > Thunderbird were restored correctly. > > There has been no change to ksmserver (except see above), so another prove > that this is not the same bug. So where is placed the bug? In Plasma 5.5.4 GTK applications are restored correctly and in 5.6.4 don't. >From my perspective it looks like some informations necessary to restore GTK based applications are not saved into ksmserverrc. Even after hardcoded them in this file, they exist only till first relogin/restart. After that they disappear. How it might be explained? > > Looking what you are saying: 'I have heard of other users having problems > > with Firefox in this regard since upgrading Plasma to 5.6 (or the beta).". I > > also other persons also saying about problems, so maybe this is plasma 5.6.x > > (ksmserver) bug. > > As mentioned, ksmserver hasn't been changed between 5.5 and 5.6. > Except for this: > https://quickgit.kde.org/?p=plasma-workspace. > git&a=commit&h=5f0ca1305db4a925dbdbf927f541497be334feff So I'm asking again. What happened? Developers of couple distributions made some mistake? In the past I tested also KaOS with Plasma 5.4.x and later after update to Plasma 5.6.x. Testing the newest KaOS I observe the same issue like in Antergos. KaOS doesn't base on Arch packages instead of Antergos. I wonder what will bring Plasma 5.6.4 (currently tested) in Kubuntu 16.04. I mean of course issue of restoring GTK and KF5 applications. > According to the commit message it shouldn't be a problem though... For me it is hard to say if XSM technology could affect on restoring GTK applications. I don't know what testes made author this fix after applying it in code. I mean simple test: whether GTK and KF applications are restored or not. I and others can say only that it stopped work. > If you are able to build plasma/ksmserver from source, I would recommend to > do so with this patch reverted and see if it works then. This is the easiest way to prove/not prove that author of this patch didn't retest your fix properly. Yes. I'm able to build plasma-workspace package, what contains ksmserver. Maybe I will make such test in the future. > > And if for you and for Paolo Carlini it is working then to who should to > > report the bug? > > Good question, I don't know really. > Maybe GTK3, or the applications affected. As I mentioned issue is related to GTK2 (new Opera, thunderbird) and GTK3 (Firefox). > Or, as it might be a ksmserver bug after all (I never ruled that out), file > a *new* bug report here. Some time ago (May 4th) I just reported it here in bug: 362671 (no answer). I reported it also in Antergos forum (with no answer). I'm going to report it
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 --- Comment #53 from Piotr Mierzwinski --- (In reply to Wolfgang Bauer from comment #52) > PS: there's another thing you could try to possibly narrow down the issue: > Switch to "Start with a previously saved session" in > systemsettings5->Startup and Shutdown->Session Management, manually save the > session (a corresponding entry should appear in the application menu in the > "Leave" tab or in "Powermanagement/Session" if using Kicker after you > logged out and in again), and see whether your applications are > saved/restored correctly then. > OK. I switched from "Restore previous session" to "Restore manually saved session" (in Plasma eng. version options might be call a bit different, I translated from polish). And in "Leave" tab I found option "Save session". I clicked it and checked ksmserverrc file - last modification date was changed. Unfortunately turned out that neither Thunderbird nor Opera is not saved. After that I run Firefox and repeated procedure. And again in ksmserverrc file there wasn't nothing about Firefox, Thunderbird and Opera :(. Nothing about any GTK application has been saved. I don't how it's possible that restoring Firefox is working in openSUSE :/. You or someone else told about it. Is it possible that they somehow patched plasma-workspace? If you are using openSUSE then could you please check at least new Opera, if it will be restore after relogin. > This worked even with Qt5/KF5 applications before the problem was solved > there. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 363237] New: Breakpoints (Breakpoints View) are not updated after removing/adding couple lines of code
https://bugs.kde.org/show_bug.cgi?id=363237 Bug ID: 363237 Summary: Breakpoints (Breakpoints View) are not updated after removing/adding couple lines of code Product: kdevelop Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: niko.s...@gmail.com I have set breakpoint on begin, in the middle and on end of some C/C++ file. Being in the middle of code I remove/add couple lines of code. Now I check breakpoints view and I can see that breakpoint(s) placed after removed/added code still points to the same row number. I click into it and as I expect I'm moving to wrong line. Whereas breakpoint icon placed on left bar is set next to correct row. In this moment changing breakpoint(s) by clicking in correct place sometimes might provide to CRASH. Reproducible: Always Steps to Reproduce: 1. Open C/C++ file 2. Set couple of breakpoints 3. Delete couple of lines of code placed before any breakpoint(s) Actual Results: All breakpoints placed after removed code now indicate invalid lines. Expected Results: Number of row for all breakpoints placed after removed code should be properly updated (in Breakpoints view). KDevelop and KDevplatform cloned at 14.05.2016 from brach 5.0 Bug is related with #353101, but it refers to old KDevelop line (in this case 4.7.1) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 363237] Breakpoints (Breakpoints View) are not updated after removing/adding couple lines of code
https://bugs.kde.org/show_bug.cgi?id=363237 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- I made next test. Being in System Settings I switched from "Restore previous session" to "Restore manually saved session" (in Plasma eng. version options might be call a bit different, I translated from polish). After that in K menu in "Leave" tab I found option "Save session". I clicked it and checked ksmserverrc file - last modification date was changed. Unfortunately turned out that neither Thunderbird nor Opera is not saved. After that I run Firefox and repeated procedure. And again in ksmserverrc file there wasn't nothing about Firefox, Thunderbird and Opera :(. Nothing about any GTK application has been saved. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 --- Comment #55 from Piotr Mierzwinski --- (In reply to Wolfgang Bauer from comment #54) > > I don't how it's possible that restoring Firefox is working in openSUSE :/. > > You or someone else told about it. > > Is it possible that they somehow patched plasma-workspace? > > No. > > But now that I come to think of it, openSUSE's Firefox (and Thunderbird) > packages include some custom KDE(4) integration. This *might* make the > difference between it being restored in openSUSE but not in other > distributions... > Though I'm not sure if that detail is really relevant here, the integration > is more about using the KDE file dialog and certain KDE settings (like > preferred applications and proxy settings), things like that. Yes. I agree. It seems to be not related. So my question still remains opened :/.. > > If you are using openSUSE then could you please check at least new Opera, if > > it will be restore after relogin. > > Well, I did install Opera now (37.0.2178.32), and indeed it is not restored > (nor saved to ksmserverrc). > > But I tried with KDE4 too, and it isn't restored/saved there as well. I can confirm. I tested it in Mageia 5 and new Opera is not restored as well. BTW. Recently, using Antergos I observed that konsole is restored randomly. Every few running (of Plasma) is not restored. It looks similar to behavior Kubuntu 15.x with Plasma 5.4.x -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363375] New: Spelling call causes drawing over status bar - incorrect words are not highlighted
https://bugs.kde.org/show_bug.cgi?id=363375 Bug ID: 363375 Summary: Spelling call causes drawing over status bar - incorrect words are not highlighted Product: kate Version: Git Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com I open kwrite or kate. I have selected default language. I wrote couple incorrect words and called spelling. Automatic Spell Checking is turned on and nothing is highlighted. Calling... 1. Option: Tools -> Spelling -> Spelling... - nothing happened after first use in case of next is showing dialog "Check spelling" with OK button and on status bar is drawing message about unknown word overlapping existing information. Please check attached screen. 2. Option: Tools -> Spelling -> Spelling (from cursor) - message about unknown word is drawing on status bar overlapping existing information. Please check attached screen. Change of dictionary doesn't help at all. Reproducible: Always Steps to Reproduce: 1. run kate/kwrite 2. write something incorrect in editor 3. call any Spelling option Actual Results: drawing error messages over statusbar Expected Results: incorrect words should be highlighted and in moment of calling Spelling should be appeared some helper dialog KWrite/Kate ver. 16.04.1; KFrameworks 5.22; Plasma 5.6.4 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363375] Spelling call causes drawing over status bar - incorrect words are not highlighted
https://bugs.kde.org/show_bug.cgi?id=363375 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 99121 --> https://bugs.kde.org/attachment.cgi?id=99121&action=edit status bar after use Spelling option -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake
https://bugs.kde.org/show_bug.cgi?id=354143 --- Comment #20 from Piotr Mierzwinski --- Thanks for explanation. Now "filtering" is clear :). I don't remember that you faced with that in KDevelop4. Do I understand that this mechanism has been introduced in KDevelop 5? And If yes then why? What was the goal of it? As far as I know in eclipse there is plugin which allow to define filtering rules (coloring, bold, etc.). Is this was your intention? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356178] New: Completion helper removes default values in function declaration
https://bugs.kde.org/show_bug.cgi?id=356178
Bug ID: 356178
Summary: Completion helper removes default values in function
declaration
Product: kdevelop
Version: 4.90.90
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
In class MyClass there is...
Declaration (header file):
QString getText( QWidget *pParent, const QString &sInInitText, bool &bParam,
const QString &sInLabel = QString::null, unsigned int par = 2, const QString
&sInWndTitle = QString::null );
Definition (cpp file):
QString MyClass::getText( QWidget *pParent, const QString &sInInitText, bool
&bParam, const QString &sInLabel, unsigned int par, const QString &sInWndTitle
)
{
...
}
Being in cpp file try to remove "unsigned" from "par" argument (second counting
from end). Choose "Update declaration signature" (pressing Alt+1) on "Adapt
signature" helper window.
Reproducible: Always
Actual Results:
QString getText(QWidget *pParent, GetTextMode getMode, const QString
&sInInitText, bool &bParam, const QString &sInLabel, int par, const QString
&sInWndTitle = QString::null);
As you can see disappeared default values from second and third arguments
(counting from end)
Expected Results:
QString getText( QWidget *pParent, GetTextMode getMode, const QString
&sInInitText, bool &bParam, const QString &sInLabel = QString::null, int par =
2, const QString &sInWndTitle = QString::null );
Removing both default values could make sense if I would have "par" argument as
const and I would removed "const". Then get getting invalid initialization from
compile. Or if I would change the type of second (counting from end) argument.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 356178] Completion helper removes default values in function declaration
https://bugs.kde.org/show_bug.cgi?id=356178 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- kdevelop and kdevplatform cloned at 30.11.2015 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356179] New: Completion helper removes static word from begin of declaration function
https://bugs.kde.org/show_bug.cgi?id=356179
Bug ID: 356179
Summary: Completion helper removes static word from begin of
declaration function
Product: kdevelop
Version: 4.90.90
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
In class MyClass there is...
Declaration (header file):
static QString getText( QWidget *pParent, const QString &sInInitText, bool
&bParam, const QString &sInLabel = QString::null, unsigned int par = 2, const
QString &sInWndTitle = QString::null );
Definition (cpp file):
QString MyClass::getText( QWidget *pParent, const QString &sInInitText, bool
&bParam, const QString &sInLabel, unsigned int par, const QString &sInWndTitle
)
{
...
}
Being in cpp file try to remove entire last argument: ", const QString
&sInWndTitle" and choose "Update declaration signature" (pressing Alt+1) on
"Adapt signature" helper window.
Reproducible: Always
Actual Results:
Declaration (header file):
QString getText( QWidget *pParent, const QString &sInInitText, bool &bParam,
const QString &sInLabel = QString::null, unsigned int par = 2 );
Expected Results:
Declaration (header file):
static QString getText( QWidget *pParent, const QString &sInInitText, bool
&bParam, const QString &sInLabel = QString::null, unsigned int par = 2 );
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 356179] Completion helper removes static word from begin of declaration function
https://bugs.kde.org/show_bug.cgi?id=356179 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- kdevelop and kdevplatform cloned at 30.11.2015 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 355159] CRASH in KDevelop::VariableToolTip::slotLinkActivated(QString const&) ... at /home/piotr/kf5/src/kdevplatform/debugger/variable/variabletooltip.cpp:185
https://bugs.kde.org/show_bug.cgi?id=355159 --- Comment #3 from Piotr Mierzwinski --- Just for reminding... It still happens in fresh KDevelop 5 (kdevelop and kdevplatform cloned at 30.11.2015) This time I reproduced this bug on Kubuntu 15.10 using simple scenario described in "Comment 1". KDevelop still crashed on the same line (184). Check: Thread 1 (Thread 0x7fffdd3c4800 (LWP 6735)): I attached gdb full log. The work around is copying variable name and paste it into Variable view. Could anyone to confirm this issue and at a pinch fix it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 355159] CRASH in KDevelop::VariableToolTip::slotLinkActivated(QString const&) ... at /home/piotr/kf5/src/kdevplatform/debugger/variable/variabletooltip.cpp:185
https://bugs.kde.org/show_bug.cgi?id=355159 --- Comment #4 from Piotr Mierzwinski --- Created attachment 95871 --> https://bugs.kde.org/attachment.cgi?id=95871&action=edit gdb full log for Crash -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356211] New: In debug session variable ToolTip doesn't resizing vertically
https://bugs.kde.org/show_bug.cgi?id=356211 Bug ID: 356211 Summary: In debug session variable ToolTip doesn't resizing vertically Product: kdevelop Version: 4.90.90 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: niko.s...@gmail.com In debug session please check below code. QStringList slStrings; slStrings << "a a a a a b b b b c c c c c c c"; // for checking horizontaly resizing slStrings << "b" << "c"; slStrings << "d"; Please set break point at last line, run code, catch the breakpoint and then move the mouse pointer over the variable. Should be displayed "Variable ToolTip". Now try to unfold the list. Reproducible: Always Actual Results: Variable ToolTip doesn't resizing vertically. Please note that in KDevelop it happened. Expected Results: Variable ToolTip is resizing vertically. To check if horizontally resizing works you can just click on item [0]. It's working correctly. The workaround is unfolding list in Variable view. KDevelop and KDevplatform cloned at 30.11.2015 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't resizing vertically
https://bugs.kde.org/show_bug.cgi?id=356211 Piotr Mierzwinski changed: What|Removed |Added Summary|In debug session variable |In debug session "Variable |ToolTip doesn't resizing|ToolTip" doesn't resizing |vertically |vertically CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356213] New: "Completion Helper" doesn't pop up when I try of making function as const
https://bugs.kde.org/show_bug.cgi?id=356213
Bug ID: 356213
Summary: "Completion Helper" doesn't pop up when I try of
making function as const
Product: kdevelop
Version: 4.90.90
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
In class MyClass there is function:
declaration (header file)
int myFunction();
Definition (cpp file)
int MyClass::myFunction()
{
..,
}
When I add "const" string at end of name the function in definition or
declaration then nothing happen, only function is highlighted by parser as
incorrect. But when the function is const then if I remove const then
"Completion Helper" pops up.
Reproducible: Always
Actual Results:
Nothing happen, only function is highlighted by parser as incorrect.
Expected Results:
"Completion Helper" should pop up and suggest "Update declaration/definition"
with const
KDevelop and KDevplatform cloned at 30.11.2015
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 356213] "Completion Helper" doesn't pop up when I try to make a function as const
https://bugs.kde.org/show_bug.cgi?id=356213 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Summary|"Completion Helper" doesn't |"Completion Helper" doesn't |pop up when I try of making |pop up when I try to make a |function as const |function as const -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356294] New: After clearing, set before shortcut for profile, it still works
https://bugs.kde.org/show_bug.cgi?id=356294 Bug ID: 356294 Summary: After clearing, set before shortcut for profile, it still works Product: konsole Version: 15.08.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: piotr.mierzwin...@gmail.com Accidentally I set shortcut for my "mc" profile - Ctrl+O. I clicked "Close" button. When in running "mc" profile I used above shortcut I got new konsole tab (with running mc). I realized that I set shortcut for it, so I closed it and went to "Profile managing" and cleared it. I clicked "Close" button. After that I tried again use Ctrl+O and I was surprising when again I got new konsole tab, despite it was already unset! Reproducible: Always Steps to Reproduce: 1. Run konsole 2. Go to "Profile managing" 3. Set shortcut for any profile 4. Click "Close" button 5. Use before set shortcut - you got new tab konsole 6. Close newly opened tab 7. Again go to "Profile managing" 8. Clear shortcut for this profile 9. Click "Close" button 10. Use before cleared shortcut Actual Results: Profile opens Expected Results: Profile (new tab) should not be open Tested in Kubuntu 15.10 with all updates. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356294] After clearing, set before shortcut for profile, still works
https://bugs.kde.org/show_bug.cgi?id=356294 Piotr Mierzwinski changed: What|Removed |Added Summary|After clearing, set before |After clearing, set before |shortcut for profile, it|shortcut for profile, still |still works |works CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356294] After clearing, set before shortcut for profile, still works
https://bugs.kde.org/show_bug.cgi?id=356294 --- Comment #1 from Piotr Mierzwinski --- The workaround is close and open konsole again. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487
--- Comment #31 from Piotr Mierzwinski ---
Hmm. I think you told me that in KDevelop 5 there is pretty new parser based on
clang, so I thought this is new code. Never mind. Maybe not all is new.
What do you mean saying "another oldcpp bug"?
Here, in Mageia 5, I have installed "libstdc++6-4.9.2-4.1.mga5" is this
"oldcpp"? Or you mean oldcpp plugin in KDevelop?
Back to test.
OK. I tried to reproduce it again using this time test case from Bug 353905
(marked as duplicate) with KDevelop-4.7.2 on Mageia 5 (on real machine, but it
happen also in VirtualBox 5).
I will say at the outset that my KDevelop cache is placed on the ram disk, so I
have linked "~/.cache/kdevduchain" to /tmp/piotr-kdevduchain. I'm not sure if
this is important, but maybe will help.
Going further.
Before running the test I removed kdevduchain cache (of course KDevelop wasn't
running in this moment) - it was session directory calling:
"kdevelop-{e4d7275a-9f43-4eb0-a9cb-f5cb819a0df5}".
Time for the steps (a bit improved comparing mentioned bug report):
1. Run KDevelop with my project (qtcmd2) and only opened src/filelistview.cpp
2. When cache has been generated. Find (using shortcut Ctrl+Alt+N) following
method: slotOpenSelected
3. Find following line: "m_sLastSelectedItemName = currentFileName();" (the way
of looking doesn't matter)
Note, In this function there are two occurrences such assignment and in my
test I used second one, which is placed couple of lines below first one.
4. Move cursor on the "currentFileName()" (second occurrence)
5. Invoke "Show uses"
KDevelop doesn't crash, but parser does something through for a while and stops
on 25% (see attachment) or 0% (happened when I repeat test). Anyway I was
waiting till finished about 10-15 min. and nothing changed. So I started to
invoked other "Find uses" on other functions located in slotOpenSelected, for
example: "slotBreakCurrentOperation" - no result, "openSelectedItemsWith" - no
result, "numberOfSelectedItems" - no result. Code browser still empty. Only I
can see that KDevelop uses a lot of CPU:
PID USER PRI NI VIRTRES SHR S CPU% MEM% TIME+
Command
1076 piotr 20 0 1476M 1076M 77624 S 69.36.7 12:58.44
/usr/bin/kdevelop
1188 piotr 20 0 1476M 1076M 77624 S 16.46.7 4:04.99
/usr/bin/kdevelop
1097 piotr 20 0 1476M 1076M 77624 S 11.66.7 3:54.56
/usr/bin/kdevelop
1182 piotr 20 0 1476M 1076M 77624 R 40.76.7 3:53.70
/usr/bin/kdevelop
And still allocates more and more memory. Please take a look at the screen
shots. Second one I made several dozen after first one. I have now 16GB ram and
swap, so I will wait a while till free memory finished and then probably
KDevelop crashed. In a moment of original test I had only 4GB, so it happened a
bit faster.
Anyway when I closed KDevelop then I get "KDevelop crash window" - using to
send crash report. I didn't attach report, because it told me that I have not
enough information for programmers (despite I have installed debug packages). I
know that I should to run KDevelop in gdb If I want to get the backtrace from
the crash.
I think it should finish ("Find uses" operation) really quickly, because I have
now quite strong hardware (Core i7-6700 Skylake + 16GB ram). Before (in a
moment of original test) I had AMD Phenom II X4 955 + 4GB and happened the
same. OK. Sometime KDevelop crashed faster.
When I was using 4.7.1 version I didn't observe such behavior. KDevelop either
worked (all were found) or crashed, but didn't parser stop like this and
allocated memory without end.
Because this test based on my project I remind its location:
git://git.qtcmd.org/qtcmd2.git
Sorry, my test is not some simply one-file project. I didn't test this with
other project.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #32 from Piotr Mierzwinski --- Created attachment 95908 --> https://bugs.kde.org/attachment.cgi?id=95908&action=edit "Find uses" hungs with 25% -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #34 from Piotr Mierzwinski --- Created attachment 95910 --> https://bugs.kde.org/attachment.cgi?id=95910&action=edit Find_uses-memory_usage2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #33 from Piotr Mierzwinski --- Created attachment 95909 --> https://bugs.kde.org/attachment.cgi?id=95909&action=edit Find_uses-memory_usage1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]
https://bugs.kde.org/show_bug.cgi?id=334487 --- Comment #35 from Piotr Mierzwinski --- I tried to reproduce it (including cache located on ram disk) using KDevelop 4.90.90 (cloned at 30.11.2015, run on Kubuntu 15.10, Plasma 5 session) and here all is working fine. "Find uses" function found all matching occurrences of "currentFileName()" and finished with success. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356327] New: Cpp parser doesn't act when I remove global member
https://bugs.kde.org/show_bug.cgi?id=356327
Bug ID: 356327
Summary: Cpp parser doesn't act when I remove global member
Product: kdevelop
Version: 4.90.90
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: piotr.mierzwin...@gmail.com
There is following code:
header:
#include
class MyClass
{
public:
/** This function something do.
* @param pointer some pointer
* @param string some string
*/
MyClass( int *pointer, const QString &string );
private:
bool m_bSomeGlobalMember;
};
definition:
#include "myclass.h"
MyClass::MyClass( int *pointer, const QString &string )
{
int *localPointer = pointer;
QString localString = string;
bSomeGlobalMember = true;
}
When I remove member "bSomeGlobalMember" from header file then in cpp properly
line(s) are not marked as incorrect only changes color to dark red. Problem
view doesn't report any problem.
Case 1:
When I back to header and restore just removed member pressing Ctrl+Z then
switching to cpp I will have correct color of member.
Please note that in bigger (then 2 files) project it might take more time or
doesn't work properly just leaving wrong coloring. I experienced it in my own
project. It was really annoying. I had to close KDevelop, remove cache and
start KDevelop again to have correctly parsed file :-/.
Case 2:
I don't restore member in header, but I'm starting write something, for
example, in last empty line of constructor. Parser wakes up and I get marks
line where is used removed member.
Reproducible: Always
Steps to Reproduce:
1. Being in header please remove member "bSomeGlobalMember" just pressing
Ctrl+K (remove line) on this line.
2. Please switch to cpp file and look at removed in header member.
Actual Results:
Member changes color to dark red.
There is no reported error in Problem view.
Expected Results:
Every use of member should be marked as error.
In Problem view should be reported such problem.
KDevelop and KDevplatform cloned at December 5-th 2015. Branch "5.0".
I attach package containing simple project.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 356327] Cpp parser doesn't act when I remove global member
https://bugs.kde.org/show_bug.cgi?id=356327 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 95911 --> https://bugs.kde.org/attachment.cgi?id=95911&action=edit simple test project -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356832] New: Plasma crashed when I try to use settings for Activities
https://bugs.kde.org/show_bug.cgi?id=356832 Bug ID: 356832 Summary: Plasma crashed when I try to use settings for Activities Product: plasmashell Version: 5.5.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.1) Qt Version: 5.5.1 Operating System: Linux 4.3.2-desktop-2.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: 1. Right Mouse Button on desktop 2. Select Activities 3. In left edge I have only one scaled empty desktop. When I move mouse pointer over it then I can see on bottom of it yellow/green bar 4. click settings icon localized on above bar Plasma crashed Plasma ver.5.1.1 The crash can be reproduced every time. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f715a49f800 (LWP 8980))] Thread 9 (Thread 0x7f7145d00700 (LWP 8983)): #0 0x7f7154bdbdbd in poll () at /lib64/libc.so.6 #1 0x7f7158c64ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f7158c66697 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f7147e27cc9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f71552c601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f71543d865d in start_thread () at /lib64/libpthread.so.0 #6 0x7f7154be7bfd in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f713f3ea700 (LWP 8991)): #0 0x7f7151e43d03 in g_main_context_query () at /lib64/libglib-2.0.so.0 #1 0x7f7151e443af in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f7151e4453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f71554e992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f715549380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f71552c11bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f7157b4dcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f71552c601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f71543d865d in start_thread () at /lib64/libpthread.so.0 #9 0x7f7154be7bfd in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f7136b84700 (LWP 8998)): #0 0x7f7151e87a99 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f7151e435e4 in g_main_context_release () at /lib64/libglib-2.0.so.0 #2 0x7f7151e443ee in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f7151e4453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f71554e992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f715549380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f71552c11bc in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f7157b4dcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f71552c601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f71543d865d in start_thread () at /lib64/libpthread.so.0 #10 0x7f7154be7bfd in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f7135426700 (LWP 8999)): #0 0x7f7154bd76dd in read () at /lib64/libc.so.6 #1 0x7f7151e867d0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f7151e43f64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f7151e443d8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f7151e4453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f71554e992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f715549380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f71552c11bc in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f7157b4dcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7f71552c601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f71543d865d in start_thread () at /lib64/libpthread.so.0 #11 0x7f7154be7bfd in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f712f3a7700 (LWP 9000)): #0 0x7f71543ddc3f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7159ee0fd4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f7159ee1019 in () at /lib64/libQt5Script.so.5 #3 0x7f71543d865d in start_thread () at /lib64/libpthread.so.0 #4 0x7f7154be7bfd in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f712c833700 (LWP 9001)): #0 0x7f7154bd76dd in read () at /lib64/libc.
[konsole] [Bug 356836] New: Change of default profile is not saved in configuration file
https://bugs.kde.org/show_bug.cgi?id=356836
Bug ID: 356836
Summary: Change of default profile is not saved in
configuration file
Product: konsole
Version: master
Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: history
Assignee: konsole-de...@kde.org
Reporter: piotr.mierzwin...@gmail.com
I've prepared couple of profiles and all are located in ~/.local/share/konsole
mc.profile
root mc.profile
shell.profile
On begin default is built profile: "Profile 1", so in configuration file
("~/.config/konsolerc") I have on begin following content:
[Desktop Entry]
DefaultProfile=Profile 1.profile
[Favorite Profiles]
Favorites=root mc.profile,shell.profile,mc.profile
Using "Manage profiles" option I changed default profile to "shell". I
restarted konsole and I got profile same as I very first time run konsole. When
I check configuration file here I can't see any changes. OK. I change again
and default profile let be "mc". Again after restart of konsole I get very
first default profile, and configuration file is the same.
Reproducible: Always
Actual Results:
Changed default profile is not saved in configuration file.
Expected Results:
Newly selected default profile should be saved in configuration file.
This is refers to version: 15.11.80 (unavailable in this form).
KFrameworks 5.17.0. Plasma 5.5.1. Qt-5.5.1
Packages are coming from Mageia 6 Cauldron.
--
You are receiving this mail because:
You are watching all bug changes.
[klipper] [Bug 356837] New: One cannot clear history when first time is not confirmed
https://bugs.kde.org/show_bug.cgi?id=356837 Bug ID: 356837 Summary: One cannot clear history when first time is not confirmed Product: klipper Version: 5.5.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: piotr.mierzwin...@gmail.com I copied to clipboard several text strings, let it be 5. I open clipboard and click "Clear history" icon. On question "Are you sure?" I reply "No". So I have still full clipboard. Again I open clipboard and try to click "Clear history" icon. Unfortunately I can't. Probably icon is disabled and clipboard "is thinking" that is empty, whereas I can see all my copied text strings. OK. I copy another text strings: - using copy option from context menu, - using Ctrl+C, - highlighting text in konsole I have several new strings in clipboard (I see them when I open it). Again I try clear history using properly button. Unfortunately without success. It does not respond. The workaround is remove entry one by one - clicking for every one "Remove from history". Reproducible: Always Steps to Reproduce: 1. Copy couple of text strings 2. Try to clear history, but reply "No" for confirmation 3. Try to clear history again Actual Results: Button "Clear history" doesn't respond, so there is not possible to clear history. One cannot clear history even after copying new text strings. Expected Results: Button "Clear history" should clear history. Plasma 5.5.1. KFrameworks 5.17.0. Qt-5.5.1 Packages coming from Mageia 6 Cauldron. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] New: Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 Bug ID: 356843 Summary: Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box Product: kwin Version: 5.5.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Windows compositor is turned on. I change wallpaper to different than default. I press Alt+F2 and put any letter in edit box, for example "k" and I can see like desktop is sliding left and I get again default wallpaper. This is not happen when Windows compositor is turned off. Additionally it makes that plasmoids/widgets newly added to the desktop (here: cpu stat and network stat) are disappearing. Reproducible: Always Steps to Reproduce: 1. turn on compositor (with setting like described in Additional Information) 2. change wallpaper 3. use Alt+F2 and put any letter in edit box Actual Results: Newly chose wallpaper is replaced with default one. Additionally it makes that plasmoids/widgets (cpu stat and network stat) added to the desktop disappearing. Expected Results: Newly selected wallpaper should not be replaced. Plasmoids/Widgets should not be disappear. Compositor settings: - Scale method: Accurate - Rendering backend: OpenGL 2.0 - OpenGL interface: GLX - Tearing prevention: Automatic - Keep windows thumbnails: Only for shown windows unchecked: Suspend compositor for full screen windows unchecked: Enable color correction My hardware platform is following Intel Core i7 Skylake. I'm using only integrated HD 530 graphics. Output from lspci: 00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: ASUSTeK Computer Inc. Device 8694 Flags: bus master, fast devsel, latency 0, IRQ 122 Memory at de00 (64-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at [disabled] Capabilities: [40] Vendor Specific Information: Len=0c Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] #1b Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] #13 Kernel driver in use: i915 Kernel modules: i915 lshw output: *-display description: VGA compatible controller product: Sky Lake Integrated Graphics vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:122 memory:de00-deff memory:c000-cfff ioport:f000(size=64) lsmod output: # lsmod | grep i9 i915 1122304 18 video 36864 2 i915,asus_wmi button 16384 1 i915 i2c_algo_bit 16384 1 i915 drm_kms_helper126976 1 i915 drm 352256 12 i915,drm_kms_helper Parameters set for i915 Module: i915 Parameter: disable_display --> N Parameter: disable_power_well --> 1 Parameter: disable_vtd_wa --> N Parameter: edp_vswing --> 0 Parameter: enable_cmd_parser --> 1 Parameter: enable_execlists --> 1 Parameter: enable_fbc --> -1 Parameter: enable_guc_submission --> N Parameter: enable_hangcheck --> Y Parameter: enable_ips --> 1 Parameter: enable_ppgtt --> 2 Parameter: enable_psr --> 0 Parameter: enable_rc6 --> 1 Parameter: fastboot --> N Parameter: guc_log_level --> -1 Parameter: invert_brightness --> 0 Parameter: load_detect_test --> N Parameter: lvds_channel_mode --> 0 Parameter: lvds_use_ssc --> -1 Parameter: mmio_debug --> 0 Parameter: modeset --> -1 Parameter: panel_ignore_lid --> 1 Parameter: prefault_disable --> N Parameter: preliminary_hw_support --> 0 Parameter: reset --> Y Parameter: semaphores --> -1 Parameter: use_mmio_flip --> 0 Parameter: vbt_sdvo_panel_type --> -1 Parameter: verbose_state_checks --> Y dmesg output: # dmesg | grep i9 [1.562538] [drm] Initialized i915 1.6.0 20150731 for :00:02.0 on minor 0 [1.641839] i915 :00:02.0: fb0: inteldrmfb frame buffer device [4.019392] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Xorg version is 1.18 (x11-server-xorg-1.18.0-10.mga6). Attached Xorg log. Kernel version is 4.3.2 (kernel-desktop-4.3.2-2.mga6-1-1.mga6). Including the latest firmware (kernel-firmware-n
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 96145 --> https://bugs.kde.org/attachment.cgi?id=96145&action=edit Xorg log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #2 from Piotr Mierzwinski --- Created attachment 96146 --> https://bugs.kde.org/attachment.cgi?id=96146&action=edit glxinfo output -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843
--- Comment #4 from Piotr Mierzwinski ---
Maybe "plasmashell" process crash/restart but I can't see any window message
only desktop is sliding
When I have turned off compositor and I change wallpaper then it remains. The
same with plasmoids. When I again turn on compositor (Alt+Shift+F12) then all
is fine - nothing like described above is not happens.
I had checked ("Enable compositor on starup") and then it happened when I
changed wallpaper and added plasmoids.
I try to log off and log in again with working (on startup) compositor.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #5 from Piotr Mierzwinski --- After relogin. Again I get default wallpaper and plasmoids disappeared. And when I invoked Alt+F2 and put k letter desktop again was slidding in the left side, but already has default wallpaper so it not changed :/. And one more curiosity. When I invoked "Plasma Widget Explorer" and found previously added plasmoids then I saw them with status "added". I mean I saw number 1 which was displayed in left top corner. Please note I have write permission for configuration directories (~/.config and ~/.local). Are you able to reproduce it? -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 356837] One cannot clear history when first time is not confirmed
https://bugs.kde.org/show_bug.cgi?id=356837 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #2 from Piotr Mierzwinski --- Strangely. My "Clear history" button passed in state "readonly" and I can't use it even after relogin and even after restart the system. Only I can remove items one by one :-(. The only one configuration what I found is located in ~/.local/share/klipper and this is history: "history2.lst". I'm not aware about other configuration maybe there is another? Anyway. When I removed this configuration, and removed plasmoid and added it again, still I can't use "Clear history" button. It is locked for me :-(. How could I restore it properly? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356856] New: plasmashell crashes after double click on klipboard icon
https://bugs.kde.org/show_bug.cgi?id=356856 Bug ID: 356856 Summary: plasmashell crashes after double click on klipboard icon Product: plasmashell Version: 5.5.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.1) Qt Version: 5.5.1 Operating System: Linux 4.3.2-desktop-2.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: plasmashell crashes after double click on klipboard icon. When I try to reproduce this nothing bad happened. Before double click I have in clipboard only one text entry, which was entered to the clipboard by clickng double in string (become highlighted) in Opera browser. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fca2274f800 (LWP 10954))] Thread 7 (Thread 0x7fca0dfb0700 (LWP 10958)): #0 0x7fca1ce8bdbd in poll () at /lib64/libc.so.6 #1 0x7fca20f14ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fca20f16697 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fca100d7cc9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7fca1d57601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #6 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fca075ef700 (LWP 10971)): #0 0x7fca1ce876dd in read () at /lib64/libc.so.6 #1 0x7fca1a1367d0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7fca1a0f3f64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fca1a0f43d8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fca1a0f453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fca1d79992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fca1d74380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fca1d5711bc in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fca1fdfdcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7fca1d57601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #11 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc9fed8d700 (LWP 11013)): #0 0x7fca1ce8bdbd in poll () at /lib64/libc.so.6 #1 0x7fca1a0f4434 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fca1a0f453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fca1d79992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fca1d74380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fca1d5711bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fca1fdfdcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fca1d57601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #9 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc9fd62f700 (LWP 11018)): #0 0x7fca1a137ab4 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7fca1a0f43ee in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fca1a0f453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fca1d79992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fca1d74380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fca1d5711bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fca1fdfdcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fca1d57601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #9 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fc9f75c6700 (LWP 11039)): #0 0x7fca1c68dc3f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fca22190fd4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fca22191019 in () at /lib64/libQt5Script.so.5 #3 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #4 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fc9f4ae3700 (LWP 11040)): #0 0x7fca1ce8bdbd in poll () at /lib64/libc.so.6 #1 0x7fca1a0f4434 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fca1a0f453c in g_main_context_i
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #7 from Piotr Mierzwinski --- Replying to your question. There is no change. I can see on desktop only default empty wallpaper. I checked the list of processes after that - using Ctrl+Esc looking for plasmashell. After desktop was sliding to the right side (and as I got default wallpaper) I noticed that in the list of process I have two plasmashell processes. First one, looking on top (primary I guess), takes ~120MB (in other simplest test had 105MB) and in "Window Title" "Plazma" value. Second one (slipping I guess) has state "stopped" in "CPU" column and empty value in "Window Title". I think the numbers here not matter only saying that primary process takes more memory and is working. After that I was looking for the simplest test to reproduce this issue and I found one :). 1. Compositor must be on (I have it "on" from default, so I don't need to change nothing in configuration). Here I have default configuration (you can find in top post). Therefore my test I started from the second point. 2. Being on login screen switch to any text terminal and... Remove or rename cache and configuration directories rm .cashe .kde .kde4 mv .config .config.bak mv .local .local.bak 3. Log in to Plasma and set two virtual desktops 4. Change wallpaper (no matter which one, might be even first one) Note. Wallpaper window has default settings as following: Desktop, Picture, Scaled (sorry if the names doesn't match accurately I translate them from my local language) I have also installed couple additional wallpapers, but I'm not sure is it important here. 5. Invoke Alt+F2, and put "k" letter in edit box Result: wallpaper sliding including plasmoids if any there are placed on the desktop Using in this moment SHIFT+Alt+F12 nothing change. Even second "stopped" plasmashell process still exists on the processes list. Ah. OK. Only (bottom) panel a bit changes (there is no artefacts only it changes a bit its look). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #8 from Piotr Mierzwinski --- And one more thing. When I killed both plasmashell procesess (first one was "stopped" one and after that nothing happened) and started again plasmashell (from konsole) then I got my changed desktop including wallpaper and plasmoids. -- You are receiving this mail because: You are watching all bug changes.
