[akregator] [Bug 304247] Akregator crashed after closing a tab

[Charles T Bell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=304247

--- Comment #2 from Charles T Bell  ---
This time there was a file named "crashed" that I had to delete to get
Akregator back without the "demo.jso" tab.  Once I closed Akregator and delete
the "crashed" file everything was back to normal without the "demo.jso" tab.
I have yet to figure where the "demo.jso" tab is opened; it just seems to
appear, making life difficult.
Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 304247] Akregator crashed after closing a tab

[Charles T Bell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=304247

Charles T Bell  changed:

   What|Removed |Added

 CC||cbel...@cfl.rr.com

--- Comment #1 from Charles T Bell  ---
"Do not restore" did not work at restarting without the tab until I did this.
When Akregator crashed, I went into: "cd
/home/tommy/.kde/share/apps/akregator/"
and did: rm -f autosave
Then I started Akregator and all was well again.  
Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 361607] New: Screen went down when changing settings on widget CWP.

[Charles T Bell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361607

Bug ID: 361607
   Summary: Screen went down when changing settings on widget CWP.
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: cbel...@cfl.rr.com

Application: plasma-desktop (4.11.14)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 3.13.0-85-generic x86_64
Distribution: Ubuntu 14.04.4 LTS

-- Information about the crash:
I was attempting to change the settings on a widget, CWP, when suddenly the
screen went blank.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0a5f9e17c0 (LWP 4937))]

Thread 19 (Thread 0x7f0a3531a700 (LWP 4939)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0a58655ffb in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f0a58953f00 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f0a58656039 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f0a53168182 in start_thread (arg=0x7f0a3531a700) at
pthread_create.c:312
#4  0x7f0a5f2da47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 18 (Thread 0x7f09aefc7700 (LWP 4940)):
#0  0x7f0a52a9261a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f0a52a929a9 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0a52a50a59 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0a52a50f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f0a52a510ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f0a5be7a7be in QEventDispatcherGlib::processEvents
(this=0x7f09a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f0a5be4c0af in QEventLoop::processEvents
(this=this@entry=0x7f09aefc6de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f0a5be4c3a5 in QEventLoop::exec (this=this@entry=0x7f09aefc6de0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f0a5bd48c5f in QThread::exec (this=this@entry=0x1c064a0) at
thread/qthread.cpp:537
#9  0x7f0a5be2d823 in QInotifyFileSystemWatcherEngine::run (this=0x1c064a0)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f0a5bd4b32f in QThreadPrivate::start (arg=0x1c064a0) at
thread/qthread_unix.cpp:349
#11 0x7f0a53168182 in start_thread (arg=0x7f09aefc7700) at
pthread_create.c:312
#12 0x7f0a5f2da47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 17 (Thread 0x7f09a19cf700 (LWP 4945)):
#0  0x7f0a5f2cd12d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0a52a50fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0a52a510ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0a5be7a7be in QEventDispatcherGlib::processEvents
(this=0x7f099c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f0a5be4c0af in QEventLoop::processEvents
(this=this@entry=0x7f09a19cede0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f0a5be4c3a5 in QEventLoop::exec (this=this@entry=0x7f09a19cede0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f0a5bd48c5f in QThread::exec (this=) at
thread/qthread.cpp:537
#7  0x7f09a4c86fe7 in KCupsConnection::run() () from
/usr/lib/libkcupslib.so
#8  0x7f0a5bd4b32f in QThreadPrivate::start (arg=0x248c550) at
thread/qthread_unix.cpp:349
#9  0x7f0a53168182 in start_thread (arg=0x7f09a19cf700) at
pthread_create.c:312
#10 0x7f0a5f2da47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 16 (Thread 0x7f0998e3f700 (LWP 9372)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0a5bd4b816 in wait (time=18446744073709551615, this=0x1c85830) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1dc2268, mutex=0x1c511b0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7f0a578c1e6c in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1dc2240,
th=0x661f8f0) at ../../../threadweaver/Weaver/WeaverImpl.cpp:370
#4  0x7f0a578c4903 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1c7b590, th=0x661f8f0, previous=0x0) at
../../../threadweaver/Weaver/WorkingHardState.cpp:68
#5  0x7f0a578c491c in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1c7b590, th=0x661f8f0, previous=0x0) at
../../../threadweaver/Weaver/WorkingHardState.cpp:71
#6  0x7f0a578

[ksysguard] [Bug 357906] New: ksysguard does not show eth3 in network graph

[Charles T Bell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357906

Bug ID: 357906
   Summary: ksysguard does not show eth3 in network graph
   Product: ksysguard
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: cbel...@cfl.rr.com

For some reason my new m/b has only one ethernet port that is locked at eth3. 
For some reason ksysguard does not show any network activity when
down/uploading.
I have an AMD64-8 (as in 8-cpus on the cpu chip) and it shows all of them just
fine.
I am using 14.04 LTS Kubuntu.

Reproducible: Always

Steps to Reproduce:
1. Run Ksysguard
2. Download any file or website
3. Watch network graph

Actual Results:  
The network line remained flat-lined.

Expected Results:  
It should have shown some network activity on the graph, you know a squiggly
line from left to right.

I could not find a resource/config file to add the eth3 port, nor anything in
the "configure ksysguard" menu.

-- 
You are receiving this mail because:
You are watching all bug changes.