Description of problem: if kaccessible is loaded; kde do not work properly: for example klaucher konqueror and Dolphin do not work, but error. notice root can lauch . Version-Release number of selected component (if applicable): How reproducible: on my cauldron 64 bits Steps to Reproduce: 1.install kaccessible ( without jovie ?) 2.reboot 3.clik (dolphin or konqueror...) Reproducible: Steps to Reproduce:
CC: (none) => balcaen.johnAssignee: bugsquad => nicolas.lecureuil
i can't reproduce here. dolphin is starting (slower as expected according to the README available in /usr/share/doc/kaccessible/README ). dolphin start as root because it's not using the same dbus session so probably not affected by kaccessible.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
Hello Without kasseccible my Mageia4 Cauldron + updates work werry well. start and stop are quick, KDE4 is good. Il use konqueror, firefox and y load with mcc kaccessible and reboot Errors on desktop KDE4 :: Exécutable : krunner PID : 2364 Signal : Segmentation fault (11) Temps : 12/10/2013 17:52:40 Konqueror : Exécutable : konqueror PID : 2542 Signal : Segmentation fault (11) Temps : 12/10/2013 17:52:41 Exécutable : systemsettings PID : 4349 Signal : Segmentation fault (11) Temps : 12/10/2013 17:53:06 mcc libreoffice ..work fine trying konqueror for my home : error Exécutable : konqueror PID : 19716 Signal : Segmentation fault (11) Temps : 12/10/2013 18:10:24 Widh Konsole , root can use konqueror and Dolphin. ( computer : CM A75M-HVS socket FM1; processor âAMD A4-3400 APU with Radeon(tm) HD Graphics , disk static: âATA OCZ-VERTEX PLUS , + disk wd classic : âWestern Digital Corp. WD1600JS-60N + Asus âDRW-24B5ST and WiFi âNETGEAR âWNA1100 ) now y reboot
Reboot with kaccessible : errors in kde4 (idem) Root do : # urpme kaccessible and reboot : All work fine for user !
it would be nice to have a backtrace of konqueror/dolphin crash[1]. Could you also attached your ~/.xsession-errors ? [1] https://wiki.mageia.org/en/Debugging_software_crashes
After doing some tests it seems it's my change (for onboard) that is causing this. My testing did not show this issue. Onboard uses qtatspi-plugin which looks for QT_ACCESSIBILITY which is now set to 1 by /etc/X11/xinit.d/90qt-a11y if: "gsettings get org.gnome.desktop.interface toolkit-accessibility" returns true This enables onboard's auto-show to work correctly in KDE applications. 90qt-a11y is installed by at-spi2-core, which is the way that Ubuntu does it.
CC: (none) => zen25000
Created attachment 4433 [details] backtrace This now seems to be happening without kaccessible installed in a test installation, but not in my main system (cauldron) with onboard running all the time. Attached bt from test system.
Application: Interface d'exécution de commandes (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faacdb39780 (LWP 2528))] Thread 2 (Thread 0x7faab157d700 (LWP 2546)): #0 0x00007faac82c326c in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x00007faac8283646 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #2 0x00007faacc79f8a6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4 #3 0x00007faacc771a1f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4 #4 0x00007faacc771d15 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4 #5 0x00007faacc67076f in QThread::exec() () from /lib64/libQtCore.so.4 #6 0x00007faacc753283 in QInotifyFileSystemWatcherEngine::run() () from /lib64/libQtCore.so.4 #7 0x00007faacc672e0f in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #8 0x00007faacc3e2fab in start_thread () from /lib64/libpthread.so.0 #9 0x00007faacb16960d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7faacdb39780 (LWP 2528)): [KCrash Handler] #5 0x00007faacbdf4cf0 in QAbstractItemView::reset() () from /lib64/libQtGui.so.4 #6 0x00007faacbe1659c in QListView::reset() () from /lib64/libQtGui.so.4 #7 0x00007faacbcc1fb6 in QComboBoxPrivate::viewContainer() () from /lib64/libQtGui.so.4 #8 0x00007faacbcc20ad in QComboBoxPrivate::adjustComboBoxSize() () from /lib64/libQtGui.so.4 #9 0x00007faacbcc385f in QComboBox::setSizeAdjustPolicy(QComboBox::SizeAdjustPolicy) () from /lib64/libQtGui.so.4 #10 0x00007faab6e67f48 in KrunnerHistoryComboBox::KrunnerHistoryComboBox(bool, QWidget*) () from /usr/lib64/libkdeinit4_krunner.so #11 0x00007faab6e60b8d in Interface::Interface(Plasma::RunnerManager*, QWidget*) () from /usr/lib64/libkdeinit4_krunner.so #12 0x00007faab6e5d9b1 in KRunnerApp::initialize() () from /usr/lib64/libkdeinit4_krunner.so #13 0x00007faab6e5dfce in KRunnerApp::KRunnerApp() () from /usr/lib64/libkdeinit4_krunner.so #14 0x00007faab6e5e025 in KRunnerApp::self() () from /usr/lib64/libkdeinit4_krunner.so #15 0x00007faab6e5e4d5 in kdemain () from /usr/lib64/libkdeinit4_krunner.so #16 0x000000000040821f in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #17 0x00000000004090fb in handle_launcher_request(int, char const*) [clone .isra.13] () #18 0x000000000040978a in handle_requests(int) () #19 0x00000000004052ba in main ()
(In reply to christian fischer from comment #7) Christian, you can workaround this issue for now by running: su mv /etc/X11/xinit.d/90qt-a11y /etc/X11/xinit.d/90qt-a11y_old ...and re-boot.
(In reply to Barry Jackson from comment #8) > (In reply to christian fischer from comment #7) > Christian, you can workaround this issue for now by running: > su > mv /etc/X11/xinit.d/90qt-a11y /etc/X11/xinit.d/90qt-a11y_old > ...and re-boot. Ignore that ^^ if you did it already revert it then ... Just install qt4-accessibility-plugin - it's a missing require.
(In reply to Barry Jackson from comment #9) > (In reply to Barry Jackson from comment #8) > > (In reply to christian fischer from comment #7) > > Christian, you can workaround this issue for now by running: > > su > > mv /etc/X11/xinit.d/90qt-a11y /etc/X11/xinit.d/90qt-a11y_old > > ...and re-boot. > > Ignore that ^^ if you did it already revert it then ... > > Just install qt4-accessibility-plugin - it's a missing require. on kaccessible ? It's not installed here & i don't have any crash while kacessible is installed.
(In reply to John Balcaen from comment #10) > on kaccessible ? > It's not installed here & i don't have any crash while kacessible is > installed. No not on kaccessible - it is required when and if 90qt-a11y sets QT_ACCESSIBILITY=1 - without it kde apps segfault. Check if you have /etc/X11/xinit.d/90qt-a11y - and that it has set QT_ACCESSIBILITY=1 if so, problem will occur after a reboot IIANM, *if* qt4-accessibility-plugin is not installed. I have split 90qt-a11y into a separate at-spi-core-qt package with requires on the main package and qt4-accessibility-plugin, so that the main package does not pull qt into gnome when it is installed. This should now be fixed after update to at-spi2-core-2.10.0-3
OK " Just install qt4-accessibility-plugin - it's a missing require." With urpmi Just qt4-accessibility-plugin and reboot : no error , kde and dolphin are good.
The KDE app crashing problem appears to be fixed since updates. However, there does seem to be an unrelated problem with kaccessible, in that for me the speech does not work at all. Tested only in x86_64 (real and VM) Does it work for you?
Kaccessible work vor my, and read the screen ! (clik vor valid ) but in english only.
OK closing then. Thanks.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => FIXED
(In reply to Barry Jackson from comment #13) > The KDE app crashing problem appears to be fixed since updates. > > However, there does seem to be an unrelated problem with kaccessible, in > that for me the speech does not work at all. Tested only in x86_64 (real and > VM) > > Does it work for you? Did you configure it ?
That is very strange: On Mageia4 Cauldron 64b y have: Kaccessible and Jovie. Jovie speek fr : it is very easy to configure ( espeak ). Screen-reader was english : i do not find to configure in french. I do : export QT_ACCESSIBILITY=1 ( no change ) with spd-conf in root y choose fr for all users. Y reboot : jovie is not actived ? Y click for active. reboot : Kde4 and Linux crask : no command. reset ...reboot and .. KDE4 work and screen reader speak French ! Jovie is stopped but i click to active and jovie speak french too.
(In reply to John Balcaen from comment #16) > (In reply to Barry Jackson from comment #13) > > The KDE app crashing problem appears to be fixed since updates. > > > > However, there does seem to be an unrelated problem with kaccessible, in > > that for me the speech does not work at all. Tested only in x86_64 (real and > > VM) > > > > Does it work for you? > > Did you configure it ? Easier said than done. I think the problems (excluding the language barrier ;) that Christian is explaining demonstrate the difficulty. There is no GUI configuration option and no real explanation of requirements. The Url in the spec which is linked in rpmdrake is less than useless. I have been attempting to test it on and off for a few days now and thought it required jovie, as installing jovie finally got it working. Since then I now have it working (on my main real machine) without jovie. I guess jovie pulled in speech-dispatcher. (which I eventually did configure with spd-conf) Maybe it should suggest/require speech-dispatcher, and offer a README.urpmi to explain that speech-dispatcher needs configuring. Having said all that a fresh install in a test cauldron VM does not display the tray icon at all with or without speech-dispatcher running. Tried in two different VMs (32 and 64 bit) No errors in journal that I could see.