https://bugs.kde.org/show_bug.cgi?id=376537
Christoph Feck changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/ksy
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #22 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #21)
> If everything else fails, install it to /usr and reboot.
>
> cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/usr ..
> make
> sudo make install
omg,
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #21 from Christoph Feck ---
If everything else fails, install it to /usr and reboot.
cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/usr ..
make
sudo make install
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #20 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #19)
> I was referring to the attachment from comment #5. It clearly shows a crash,
> but the symbols are 'n/a' there.
>
> Also, make sure ksysguard actually conne
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #19 from Christoph Feck ---
I was referring to the attachment from comment #5. It clearly shows a crash,
but the symbols are 'n/a' there.
Also, make sure ksysguard actually connects to your compiled version of
ksysguardd, instead of the one
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #18 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #17)
> Yes, but that backtrace has no debug symbols...
i built it using following commands within build directory inside ksysguard
project
[boes@ARCHHOME build]$cm
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #17 from Christoph Feck ---
Yes, but that backtrace has no debug symbols...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #16 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #15)
> The valgrind memcheck log does not show any reason for a crash. The 'invalid
> reads' and 'invalid writes' seem to be gone, so I am wondering if it crashes
>
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #15 from Christoph Feck ---
The valgrind memcheck log does not show any reason for a crash. The 'invalid
reads' and 'invalid writes' seem to be gone, so I am wondering if it crashes at
all.
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #14 from boestari.r...@gmail.com ---
Created attachment 104087
--> https://bugs.kde.org/attachment.cgi?id=104087&action=edit
valgrind ksysguard
here's the valgrind ksysguard output. i'm using flag --leak-check=full
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #13 from Christoph Feck ---
At cmake time, with -DCMAKE_BUILD_TYPE=Debug
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #12 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #10)
> If it still crashes with the patch applied, please add a backtrace with full
> debug symbols, and ideally also a valgrind log (with debug symbols). Note
> th
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #11 from boestari.r...@gmail.com ---
(In reply to Rog131 from comment #8)
> (In reply to boestari.riko from comment #6)
> > Created attachment 104077 [details]
> > screenshot
> >
> > so, i built the latest ksysguard from github and include y
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #10 from Christoph Feck ---
If it still crashes with the patch applied, please add a backtrace with full
debug symbols, and ideally also a valgrind log (with debug symbols). Note that
default packages in Arch do not have debug information, s
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #9 from Rog131 ---
At here: AMD FX-6100 (six core) & Arch Linux. With the Kernel 4.9.8 the core
numbering is 0,3,4,5,6,7 -> The Ksysguard is crashing
Downloading the Arch Ksysguard PKGBUILD:
https://git.archlinux.org/svntogit/packages.
https://bugs.kde.org/show_bug.cgi?id=376537
Rog131 changed:
What|Removed |Added
CC||samrog...@hotmail.com
--- Comment #8 from Rog131 ---
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #7 from boestari.r...@gmail.com ---
and btw on my amd fx-6100, kernel 4.9.8 /sys/devices/system/cpu folder contains
cpu0, cpu3-cpu7 just like in /proc/stat, and files
/sys/devices/system/cpu/cpuX/cpufreq/stats/time_in_state is empty. hope thi
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #6 from boestari.r...@gmail.com ---
Created attachment 104077
--> https://bugs.kde.org/attachment.cgi?id=104077&action=edit
screenshot
so, i built the latest ksysguard from github and include your changes.
running ksysguard, well, nothing
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #5 from boestari.r...@gmail.com ---
Created attachment 104076
--> https://bugs.kde.org/attachment.cgi?id=104076&action=edit
journal ctl output
this is the journalctl output when running ksysguard
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #4 from boestari.r...@gmail.com ---
Created attachment 104075
--> https://bugs.kde.org/attachment.cgi?id=104075&action=edit
ksysguard output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #3 from boestari.r...@gmail.com ---
i'll try it tonight. currently at work now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #2 from Christoph Feck ---
Created attachment 104068
--> https://bugs.kde.org/attachment.cgi?id=104068&action=edit
Proposed patch
Indeed. It counts the number of "cpu" lines, and only allocates that number
of entries. But then, it uses th
https://bugs.kde.org/show_bug.cgi?id=376537
--- Comment #1 from boestari.r...@gmail.com ---
i believe it also related to these bugs report:
https://bugs.kde.org/show_bug.cgi?id=374944
https://bugs.kde.org/show_bug.cgi?id=371942
--
You are receiving this mail because:
You are watching all bug cha
23 matches
Mail list logo
