|
Description
Simon Andric
2014-09-22 01:12:18 UTC
It might be helpful if you provided the .config/plasma* and .config/kactivitymanagerdrc Also, does it happen also with a new account? Simon, can you please provide the information requested by Ivan. Marking as Waiting for Info Created attachment 88806 [details]
/home/myname/.project-neon-kde/config/plasmarc
Created attachment 88807 [details]
/home/myname/.project-neon-kde/config/plasma-localerc
Created attachment 88808 [details]
/home/myname/.project-neon-kde/config/plasma-locale-settings.sh
Created attachment 88809 [details]
/home/myname/.project-neon-kde/config/plasma-org.kde.plasma.desktop-appletsrc
Created attachment 88810 [details]
/home/myname/.project-neon-kde/config/plasmashellrc
Created attachment 88811 [details]
/home/myname/.project-neon-kde/config/kactivitymanagerd-pluginsrc
Created attachment 88812 [details]
/home/myname/.project-neon-kde/config/kactivitymanagerdrc
Created attachment 88813 [details]
/home/myname/.project-neon-kde/config/kactivitymanagerd-resourcelinkingrc
hello! first, sorry for late reply, your requests my gmail saved under spam, so i didnt see them till today... in /home/myname/.config/ ... there are nor files which you requested..i found them under .project-neon5/... i hope they are correct... since i dont have any other anywhere else (not in .kde/... not in /opt/project-neon5/..., ) also... am..with new accoutn... i didnt try yet... maybe in a few days i will, because then i have to set up again everything (panel, widgets, activities, wallpapers, icons (shortcuts)) and right now i dotn have that much time. will report back on how it went though when i get to it... in the meantime if there is anything else, please ask, now ill look my emails more closely...promise :) thank you for your help nice day Simon Created attachment 88867 [details]
kwin.info --- if it helps :)
Created attachment 88868 [details]
my sources.list
Unfortunately, I still can not reproduce the issue. I've installed the neon5-201408290837 under virtualbox, and copied your configuration files. Everything behaves as it should. Does anything change if you (1) log out (2) log into a virtual terminal (3) remove the activities marked with $d from .project-neon-kde/config/kactivitymanagerdrc (4) log back into the workspace? hello! i will do what you ask from me gladly, but if i may - this week im at work a lot so i wont have muh time on m yhome computer...is it ok if i do that after 5.oct? please forgive me, but when it comes to work i dont have a choice :) but srsly, thank you for help...really... so in 1 week ill report back how it went... nice day :) Simon No problem :) hello! ok -- it is like this today after almost 2 weeks i updated the system - and BLINKING doesnt happen anymore...so a very big thanks for the repair (note: i still didnt try the new username or reseting / deleting the preference files yet). Only 1 problem from this context persists: stil leven though i have only 1 activity in my activity manager, i have two separate desktops --- one with widgets and normal mouse cursor and the other without widgets and with "root -- ubuntu" mouse cursor. i would like to remove the latter but i cannot --- when i reboot the system for a few seconds while botting the forist activity with widgets show, and then all of a sudden the other one goes over it. If i click o nthe activity manager icon (after the booting is finished) and then on the *only* activity whihc is there --- twice or so, + sometimes i also press ctrl+esc (to open the system activity) then the desktop which i want (the one with widgets) again shows....i have to do this every time i reboot the computer nice day and thank you :) Simon Created attachment 88985 [details]
the *wrong* desktop (no widgets)
Created attachment 88986 [details]
clicking on the activity manager icon in the lower left part of screen reveals my *right* desktop (with widgets) at the same time as the activity manager panel shows up
clicking on the activity manager icon in the lower left part of screen reveals my *right* desktop (with widgets) at the same time as the activity manager panel shows up
hello! after update now, the problem is the same -- only when i clicked on the activity manager icon twice i managed to somehow crash kwin...not on purpose... im posting the backtrace (manually coz dr. konqi still cannot send the error report to bugs.kde.org) thank you nice daay Simon:) ------------------- Application: kwin_x11 (5.0.95) Qt Version: 5.3.2 Operating System: Linux 3.16.0-21-generic i686 Distribution: Ubuntu Utopic Unicorn (development branch) -- Information about the crash: - What I was doing when the application crashed: kwin crash when clicking on the activity manager icon --- i clicked twice and kwin crashed nice day simon The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb1badac0 (LWP 4254))] Thread 4 (Thread 0xae9ffb40 (LWP 4272)): #0 0xb77c9c7c in __kernel_vsyscall () #1 0xb76d2442 in __GI___clock_gettime (clock_id=1, tp=0xae9ff0f8) at ../sysdeps/unix/clock_gettime.c:115 #2 0xb61cc4e0 in qt_clock_gettime (clock=1, ts=0xae9ff0f8) at tools/qelapsedtimer_unix.cpp:113 #3 0xb61cc5bd in do_gettime (sec=0xae9ff120, frac=0xae9ff128) at tools/qelapsedtimer_unix.cpp:169 #4 0xb61cc5ef in qt_gettime () at tools/qelapsedtimer_unix.cpp:178 #5 0xb63991e7 in QTimerInfoList::updateCurrentTime (this=0x866ffb0) at kernel/qtimerinfo_unix.cpp:92 #6 0xb639999d in QTimerInfoList::timerWait (this=0x866ffb0, tm=...) at kernel/qtimerinfo_unix.cpp:387 #7 0xb639865a in QEventDispatcherUNIX::processEvents (this=0x8625060, flags=...) at kernel/qeventdispatcher_unix.cpp:602 #8 0xb632b4e3 in QEventLoop::processEvents (this=0xae9ff298, flags=...) at kernel/qeventloop.cpp:136 #9 0xb632b7aa in QEventLoop::exec (this=0xae9ff298, flags=...) at kernel/qeventloop.cpp:212 #10 0xb6120bd5 in QThread::exec (this=0x8664118) at thread/qthread.cpp:511 #11 0xb4cb29ee in QQmlThreadPrivate::run (this=0x8664118) at qml/ftw/qqmlthread.cpp:149 #12 0xb612779b in QThreadPrivate::start (arg=0x8664118) at thread/qthread_unix.cpp:345 #13 0xb48f1f16 in start_thread (arg=0xae9ffb40) at pthread_create.c:309 #14 0xb76c49fe in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 3 (Thread 0xad854b40 (LWP 4323)): #0 0xb77c9c7c in __kernel_vsyscall () #1 0xb76bccf1 in select () at ../sysdeps/unix/syscall-template.S:81 #2 0xb6396190 in qt_safe_select (nfds=18, fdread=0xaea01038, fdwrite=0xaea01244, fdexcept=0xaea01450, orig_timeout=0x0) at kernel/qcore_unix.cpp:83 #3 0xb63975a5 in QEventDispatcherUNIX::select (this=0xaea00f48, nfds=18, readfds=0xaea01038, writefds=0xaea01244, exceptfds=0xaea01450, timeout=0x0) at kernel/qeventdispatcher_unix.cpp:328 #4 0xb6396dc8 in QEventDispatcherUNIXPrivate::doSelect (this=0xaea00f58, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:204 #5 0xb63986a7 in QEventDispatcherUNIX::processEvents (this=0xaea00f48, flags=...) at kernel/qeventdispatcher_unix.cpp:615 #6 0xb632b4e3 in QEventLoop::processEvents (this=0xad854298, flags=...) at kernel/qeventloop.cpp:136 #7 0xb632b7aa in QEventLoop::exec (this=0xad854298, flags=...) at kernel/qeventloop.cpp:212 #8 0xb6120bd5 in QThread::exec (this=0x8835290) at thread/qthread.cpp:511 #9 0xb4cb29ee in QQmlThreadPrivate::run (this=0x8835290) at qml/ftw/qqmlthread.cpp:149 #10 0xb612779b in QThreadPrivate::start (arg=0x8835290) at thread/qthread_unix.cpp:345 #11 0xb48f1f16 in start_thread (arg=0xad854b40) at pthread_create.c:309 #12 0xb76c49fe in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 2 (Thread 0xa9ce7b40 (LWP 4327)): #0 0xb77c9c7c in __kernel_vsyscall () #1 0xb48f5cac in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb76d199c in __pthread_cond_wait (cond=0x8811ba4, mutex=0x8811b8c) at forward.c:149 #3 0xac33a79d in ?? () from /usr/lib/i386-linux-gnu/dri/r600_dri.so #4 0xac339d55 in ?? () from /usr/lib/i386-linux-gnu/dri/r600_dri.so #5 0xb48f1f16 in start_thread (arg=0xa9ce7b40) at pthread_create.c:309 #6 0xb76c49fe in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 1 (Thread 0xb1badac0 (LWP 4254)): [KCrash Handler] #7 0xb77c9c7c in __kernel_vsyscall () #8 0xb7607577 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #9 0xb7608cf3 in __GI_abort () at abort.c:89 #10 0xb6115d5a in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1364 #11 0xb6113907 in QMessageLogger::fatal (this=0xbfb21dac, msg=0xb63f3fc8 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:669 #12 0xb610e95b in qt_assert (assertion=0xb6a956c9 "context", file=0xb6a956ad "opengl/qopenglfunctions.cpp", line=201) at global/qglobal.cpp:2127 #13 0xb69a157a in qt_gl_functions (context=0x0) at opengl/qopenglfunctions.cpp:201 #14 0xb69b00a0 in (anonymous namespace)::Resolver<QOpenGLFunctionsPrivate, void (*)(int, unsigned int const*), 3, void>::operator()<int, unsigned int const*> (this=0xbfb21e50, p1=1, p2=0x8cec834) at opengl/qopenglfunctions.cpp:2296 #15 0xb69a502f in qopenglfResolveDeleteRenderbuffers (n=1, renderbuffers=0x8cec834) at opengl/qopenglfunctions.cpp:2754 #16 0xb59de86b in QOpenGLFunctions::glDeleteRenderbuffers (this=0x8cec81c, n=1, renderbuffers=0x8cec834) at /build/buildd/project-neon5-qt5-0.0.git20141004.0322.neon6~4a7f9e8~14.04.1/qtbase/include/QtGui/5.3.2/QtGui/private/../../../../../src/gui/opengl/qopenglfunctions.h:1325 #17 0xb59de48c in QSGDefaultDepthStencilBuffer::free (this=0x8cec818) at scenegraph/util/qsgdepthstencilbuffer.cpp:153 #18 0xb59de52a in QSGDepthStencilBufferManager::~QSGDepthStencilBufferManager (this=0x8cb8398, __in_chrg=<optimized out>) at scenegraph/util/qsgdepthstencilbuffer.cpp:164 #19 0xb59ee76a in QSGRenderContext::invalidate (this=0x8c4da48) at scenegraph/qsgcontext.cpp:502 #20 0xb5a12b71 in QSGGuiThreadRenderLoop::windowDestroyed (this=0x8d289e0, window=0x8bf5860) at scenegraph/qsgrenderloop.cpp:314 #21 0xb5a43352 in QQuickWindow::~QQuickWindow (this=0x8bf5860, __in_chrg=<optimized out>) at items/qquickwindow.cpp:1093 #22 0xb5a43461 in QQuickWindow::~QQuickWindow (this=0x8bf5860, __in_chrg=<optimized out>) at items/qquickwindow.cpp:1103 #23 0xb5f63cb7 in QScopedPointerDeleter<QWindow>::cleanup (pointer=0x8bf5860) at /opt/project-neon5/include/QtCore/qscopedpointer.h:62 #24 0xb5f634d9 in QScopedPointer<QWindow, QScopedPointerDeleter<QWindow> >::~QScopedPointer (this=0x8ca2980, __in_chrg=<optimized out>) at /opt/project-neon5/include/QtCore/qscopedpointer.h:109 #25 0xb5f63346 in KDecorationPrivate::~KDecorationPrivate (this=0x8ca2970, __in_chrg=<optimized out>) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/libkdecorations/kdecoration.cpp:56 #26 0xb5f5fcc3 in KDecoration::~KDecoration (this=0x8cbe608, __in_chrg=<optimized out>) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/libkdecorations/kdecoration.cpp:87 #27 0xaed3127c in Aurorae::AuroraeClient::~AuroraeClient (this=0x8cbe608, __in_chrg=<optimized out>) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/clients/aurorae/src/aurorae.cpp:297 #28 0xaed312b3 in Aurorae::AuroraeClient::~AuroraeClient (this=0x8cbe608, __in_chrg=<optimized out>) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/clients/aurorae/src/aurorae.cpp:300 #29 0xb73bf54b in KWin::Client::destroyDecoration (this=0x8cadc58) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/client.cpp:579 #30 0xb73be1d8 in KWin::Client::releaseWindow (this=0x8cadc58, on_shutdown=false) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/client.cpp:378 #31 0xb73fa92d in KWin::Client::unmapNotifyEvent (this=0x8cadc58, e=0xb0d060c0) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/events.cpp:816 #32 0xb73fa291 in KWin::Client::windowEvent (this=0x8cadc58, e=0xb0d060c0) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/events.cpp:666 #33 0xb73f8fa8 in KWin::Workspace::workspaceEvent (this=0x86607e8, e=0xb0d060c0) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/events.cpp:340 #34 0xb73ecf99 in KWin::XcbEventFilter::nativeEventFilter (this=0x8606600, eventType=..., message=0xb0d060c0, result=0xbfb223b8) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/main.cpp:406 #35 0xb632a1de in QAbstractEventDispatcher::filterNativeEvent (this=0x85ea308, eventType=..., message=0xb0d060c0, result=0xbfb223b8) at kernel/qabstracteventdispatcher.cpp:468 #36 0xb1780dfb in QXcbConnection::handleXcbEvent (this=0x85b86a8, event=0xb0d060c0) at qxcbconnection.cpp:826 #37 0xb1782c37 in QXcbConnection::processXcbEvents (this=0x85b86a8) at qxcbconnection.cpp:1244 #38 0xb17d6932 in QXcbConnection::qt_static_metacall (_o=0x85b86a8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xb0d07698) at .moc/moc_qxcbconnection.cpp:190 #39 0xb6364216 in QMetaCallEvent::placeMetaCall (this=0xb0d06468, object=0x85b86a8) at kernel/qobject.cpp:487 #40 0xb6365053 in QObject::event (this=0x85b86a8, e=0xb0d06468) at kernel/qobject.cpp:1241 #41 0xb6ca3e1e in QApplicationPrivate::notify_helper (this=0x85b4c98, receiver=0x85b86a8, e=0xb0d06468) at kernel/qapplication.cpp:3499 #42 0xb6ca1528 in QApplication::notify (this=0xbfb22c04, receiver=0x85b86a8, e=0xb0d06468) at kernel/qapplication.cpp:2952 #43 0xb73ebc06 in KWin::Application::notify (this=0xbfb22c04, o=0x85b86a8, e=0xb0d06468) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/main.cpp:228 #44 0xb632e651 in QCoreApplication::notifyInternal (this=0xbfb22c04, receiver=0x85b86a8, event=0xb0d06468) at kernel/qcoreapplication.cpp:935 #45 0xb6332045 in QCoreApplication::sendEvent (receiver=0x85b86a8, event=0xb0d06468) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:237 #46 0xb632f7ba in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x85a4fa8) at kernel/qcoreapplication.cpp:1539 #47 0xb639855c in QEventDispatcherUNIX::processEvents (this=0x85ea308, flags=...) at kernel/qeventdispatcher_unix.cpp:587 #48 0xb1812cec in QUnixEventDispatcherQPA::processEvents (this=0x85ea308, flags=...) at eventdispatchers/qunixeventdispatcher.cpp:70 #49 0xb632b4e3 in QEventLoop::processEvents (this=0xbfb22b4c, flags=...) at kernel/qeventloop.cpp:136 #50 0xb632b7aa in QEventLoop::exec (this=0xbfb22b4c, flags=...) at kernel/qeventloop.cpp:212 #51 0xb632ed31 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188 #52 0xb66d1ddc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1483 #53 0xb6ca0db3 in QApplication::exec () at kernel/qapplication.cpp:2744 #54 0xb77c1e44 in kdemain (argc=1, argv=0xbfb22ce4) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/main_x11.cpp:294 #55 0x0804885e in main (argc=3, argv=0xbfb22ce4) at /build/buildd/project-neon5-kwin-0.0+git20141008.0313+neon4~e4b2f14~14.04/obj-i686-linux-gnu/kwin_x11_dummy.cpp:3 Report to https://bugs.kde.org/ Created attachment 89046 [details]
the original bug report / generated by dr. konqi
You ought to report the crash separately. It is a crash in the aurorae decoration, and not really a crash but a debug-mode assert it seems. You can try to invoke kwin from the terminal and reproduce the crash - it should write out an error message (QMessageLogger::fatal) - append it to the bug report for kwin. As for the main issue of this report, it still seems like a problematic install / configuration. hello! i appologize --- i thought this has sth to do with this report -- ok will report it separately... thank you for your advice... as for this bug, i will post again after i reset my configuration - - if the problem still happens or not anymore :) thank you! nice day Simon No need to appologize :) hello! so i tried --- and created a new user, but didnt give it sudo permission (sudoers)... then i tried again and this time i did correcty..then i deleted user 2 and original user (1) and renamed user 3 to user 1 and rebooted... then my new user didnt want to load... that splash screen comes to some point (of loading --- tgat blue horizontal line) and then stops... so amm... since my original user is gone..and my desktop also (no prob, happens from time 2 time -- i do it at least 3 times per year) i will try from scratch --- i reinstall project neon 5 and then report back if the issue still comes up or not --and if so what i did that created this problem... for now im using laptop and kde4 :) when i have time ps. i also found this....problem before it all happened.. *IF* , when the system boots and the desktop first comes you click on activity manager icon (wither once or, twice one after the other) --- id say too fast ---all the panels freeze (i got 2) by freeze i mean, the digital clock in panel stops runnin gand clicking on icons, task manager items or system tray items doesn do anything...its frozen...- and not only panels, right click on the desktop also doesnt produce a menu -- but alt+f2 works... :) ok..till next time nice day :) Simon ok fresh install --- plasma 5 + project neon 5 + vivid packages what i did: first: one monitor an one computer screen overlapped + unified outputs to 1920x1080 + vga-0 is the default monitor then: chose dekstop / slideshow / scaled && cropped / 7 minutes to wait before change wallpaper added 2 dirs: /opt/project-neon5/usr/share/wallpapers and /usr/share/wallpapers apply + close then: created empty panel on left side, center position put 38 icons (dragged from k menu) in it then put analog clock + resize + put on the top right corner + turn on seconds needle and name of time zone. theni add a folder widget -- next to empty panel with icons set up like this: folder, which is /usr/share/applications custom message: ----- (nevermind, personal) :) then i chose the biggest icons and unclicked to put the folders at the begiining apply and THEN in systemsettings5 i added that there are 2 virtual desktops (widget in my default panel immediately after apply showed 2 virtual desktops instead of 1 -- which is what it was suppose to do) i also went from oxygen to breeze theme window decoration i edited the system tray, put some icons as hiden and some as always shown digital clock: added the seconds to it and at last i dragged the ACTIVITY MANAGER on the default panel next to K menu icon then i locked widgets then i clicked activity manager icon and immediately noticed that i already am running TWO activites: one is caleed DEFAULT the other is called DESKTOP.... if i clicked on one my desktop showed, the other one shoed a default desktop with no extra widgets... one i could modify the name but the other one (ddefault) i couldnt... now the funny part...i restarted the computer and all of a sudden if i clicked on a default panel i could edit its name..so i changed the neame and put the new icon, AND i deleted the DESKTOP activity...so im left only with DEFAULT (with a new name) activity... after another reboot.... the sektop is blinking again....and instead of my personalized desktop the one without widgets appear. how to sometimes turn o nblinking (and get back to my perosnalized desktop): 1) i open an application before the linux stopped all the boot preferences loading... 2) if i click on the activity manager icon , then somewhere on the desktop (so that the activity manager closes), then again click o nth activity manager icon, and AGAIN clicking on the ACTIVITY MANAGER icon (NOT on the desktop) /to close activity manager window/... my personalized desktop now appears but its blinking HARD... after each reboot , sometimes it is blinking from the beginning, sometimes not at all, sometimes if i do what i described in steps 1) and 2). ps. another thing...in that empty desktop, you cannot keep and widgets..if you put hem there (for example analog clock and folder) immediately when you want to drag them around they somehow "fall through" the lower (my personalized) desktop. even if i dont drag them after reboot they are gone... but if they fell through with or without reboot i f i can get to MY dekstop, i all of a sudden have two closk or 4 folder or... as many as i created them and they "fell through"... hope i was thorough enough :) nice day Simon :) Created attachment 89389 [details]
my *new* sources.list
I can not reproduce this problem and also project neon5 is deprecated from long time, can you reproduce this problem with latest Plasma 5? hello! currently im out of country and ill be returning around the end of april. after that i plan to reinstall kubuntu again anyway (i left ity in a miserable state when i went for vacation), and if i encounter this problem again i will post here. until then thi bug report can either stay "waiting for info" or you can close it as worksforme and in case if it "doesnt work for me" i will again reopen it. :) or maybe created a new bug coz i reported this as a project neon5 bug, and since it doesnt exist anymore (pn5) the possible related behaviour of the system would then be related to plasma5...not pn5 nice day and thank you Simon:) > you can close it as worksforme and in case if it "doesnt work for me" i will again reopen it. :)
Please do :)
(closing)
|