Bug#671944: libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable
Hi, > > reporting this against Virtuoso is wrong (sorry for the multiple bug > > reports caused by this). As a result of virtuoso missing, new > > installations will not be able to get a working Nepomuk, making the > > package unusable. > > Err no, sorry, we're not talking about a daemon or a service, but about > a library, which is linked directly and indirectly by lot of KDE Sorry, I chose the wrong package - I searched for "nepomuk" in the package title, but I actually meant the package containing the daemon, which is kde- runtime as I just found out. I will re-assign the bug there (as soon as I figure out how to do that^^). Sorry for the noise. > > Virtuoso is missing from testing, and without it, Nepomuk does not > > work (also see [1]). As I had to find out the hard way [2], > > The fact that virtuoso is missing from testing is not something related > to us. It is related to you in that it breaks the nepomuk daemon. Admittedly it is not part if this library, that's my fault, I apologize - see above. Kind regardsm Ralf -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205091021.48347.p...@ralfj.de
Bug#671391: Reassign bugs to nepomuk daemon (which sits in kde-runtime)
reassign 671391 kde-runtime 4:4.7.4-2 retitle 671391 kde-runtime: Nepomuk should depend on virtuoso reassign 671944 kde-runtime 4:4.7.4-2 retitle 671944 kde-runtime: Virtuoso entirely missing from testing, making Nepomuk unusable servety 671944 important thanks Re-assigning these bugs to the package the nepomuk daemon lives in (I hope this works). In my eyes, 671944 is RC for kde-runtime since it renders the daemon unusable, but I will let the package maintainers decide about that. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205091027.38708.p...@ralfj.de
Processed (with 2 errors): Reassign bugs to nepomuk daemon (which sits in kde-runtime)
Processing commands for cont...@bugs.debian.org: > reassign 671391 kde-runtime 4:4.7.4-2 Bug #671391 [libnepomuk4] libnepomuk4: Nepomuk should depend on virtuoso Bug reassigned from package 'libnepomuk4' to 'kde-runtime'. No longer marked as found in versions kde4libs/4:4.7.4-4. Ignoring request to alter fixed versions of bug #671391 to the same values previously set Bug #671391 [kde-runtime] libnepomuk4: Nepomuk should depend on virtuoso Marked as found in versions kde-runtime/4:4.7.4-2. > retitle 671391 kde-runtime: Nepomuk should depend on virtuoso Bug #671391 [kde-runtime] libnepomuk4: Nepomuk should depend on virtuoso Changed Bug title to 'kde-runtime: Nepomuk should depend on virtuoso' from 'libnepomuk4: Nepomuk should depend on virtuoso' > reassign 671944 kde-runtime 4:4.7.4-2 Bug #671944 [libnepomuk4] libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable Bug reassigned from package 'libnepomuk4' to 'kde-runtime'. No longer marked as found in versions kde4libs/4:4.7.4-4. Ignoring request to alter fixed versions of bug #671944 to the same values previously set Bug #671944 [kde-runtime] libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable Marked as found in versions kde-runtime/4:4.7.4-2. > retitle 671944 kde-runtime: Virtuoso entirely missing from testing, making Bug #671944 [kde-runtime] libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable Changed Bug title to 'kde-runtime: Virtuoso entirely missing from testing, making' from 'libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable' > Nepomuk unusable Unknown command or malformed arguments to command. > servety 671944 important Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 671391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671391 671944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133655206624269.transcr...@bugs.debian.org
Bug#671944: libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable
Alle mercoledì 9 maggio 2012, Ralf Jung ha scritto: > > > reporting this against Virtuoso is wrong (sorry for the multiple > > > bug reports caused by this). As a result of virtuoso missing, > > > new installations will not be able to get a working Nepomuk, > > > making the package unusable. > > > > Err no, sorry, we're not talking about a daemon or a service, but > > about a library, which is linked directly and indirectly by lot of > > KDE > > Sorry, I chose the wrong package - I searched for "nepomuk" in the > package title, but I actually meant the package containing the > daemon, which is kde- runtime as I just found out. kde-runtime is installed for any KDE application, so what I said earlier for KIO applies likewise to kde-runtime. And kde-runtime has a recommend on virtuoso already, which is more than enough for what it's an optional feature provided by KDE. > > > Virtuoso is missing from testing, and without it, Nepomuk does > > > not work (also see [1]). As I had to find out the hard way [2], > > > > The fact that virtuoso is missing from testing is not something > > related to us. > > It is related to you in that it breaks the nepomuk daemon. So? Anything in the dependency stack below KDE can have bad effects on KDE (say Qt, GNU libc, the kernel, ...). -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Re: Bug#671391: Reassign bugs to nepomuk daemon (which sits in kde-runtime)
forcemerge 671391 671944 tag 671391 + wontfix thanks Hi, Alle mercoledì 9 maggio 2012, Ralf Jung ha scritto: > reassign 671391 kde-runtime 4:4.7.4-2 > retitle 671391 kde-runtime: Nepomuk should depend on virtuoso > reassign 671944 kde-runtime 4:4.7.4-2 > retitle 671944 kde-runtime: Virtuoso entirely missing from testing, > making Nepomuk unusable > servety 671944 important > thanks please do not play with bts like that... > Re-assigning these bugs to the package the nepomuk daemon lives in (I > hope this works). > In my eyes, 671944 is RC for kde-runtime since it renders the daemon > unusable, but I will let the package maintainers decide about that. kde-runtime has already a recommend on virtuoso, and it's more than enough given that a) any KDE application depend on kde-runtime b) the semantic desktop is an *optional* feature So no, an hard dependency will *not* be added. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#671391: Reassign bugs to nepomuk daemon (which sits in kde-runtime)
Processing commands for cont...@bugs.debian.org: > forcemerge 671391 671944 Bug #671391 [kde-runtime] kde-runtime: Nepomuk should depend on virtuoso Bug #671944 [kde-runtime] kde-runtime: Virtuoso entirely missing from testing, making Severity set to 'important' from 'minor' Merged 671391 671944 > tag 671391 + wontfix Bug #671391 [kde-runtime] kde-runtime: Nepomuk should depend on virtuoso Bug #671944 [kde-runtime] kde-runtime: Virtuoso entirely missing from testing, making Added tag(s) wontfix. Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 671391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671391 671944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133655308429766.transcr...@bugs.debian.org
Bug#671893: pykde4: Fails to build from source
kdepimlibs needs to be rebuilt, but I've been asked not to do it quite yet. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1407507.laknjdmdD1@scott-latitude-e6320
Bug#671944: Bug#671391: Reassign bugs to nepomuk daemon (which sits in kde-runtime)
Hi, > kde-runtime has already a recommend on virtuoso, and it's more than > enough given that > a) any KDE application depend on kde-runtime > b) the semantic desktop is an *optional* feature > > So no, an hard dependency will *not* be added. That's unfortunate, but understood. > So? Anything in the dependency stack below KDE can have bad effects on > KDE (say Qt, GNU libc, the kernel, ...). I understand your point, but please consider the following: - There is a problem somewhere, since Nepomuk does not work in Debian currently (unless you download stuff manually from snapshots). - Supposedly, neither virtuoso nor nepomuk is the right place to report the bug. So, what is the right place then? I hope you do not deny that there is a problem which needs to be fixed. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205091224.47277.p...@ralfj.de
Bug#671944: Bug#671391: Reassign bugs to nepomuk daemon (which sits in kde-runtime)
Alle mercoledì 9 maggio 2012, Ralf Jung ha scritto: > > So? Anything in the dependency stack below KDE can have bad effects > > on KDE (say Qt, GNU libc, the kernel, ...). > > I understand your point, but please consider the following: > - There is a problem somewhere, since Nepomuk does not work in Debian > currently (unless you download stuff manually from snapshots). We're talking about testing here, in which temporary breakages usually can happen. If you want to have no such dependency issues, just use stable. > - Supposedly, neither virtuoso nor nepomuk is the right place to > report the bug. > So, what is the right place then? I hope you do not deny that there > is a problem which needs to be fixed. You assume the way to fix things is "reporting a bug somewhere", which isn't. Virtuoso has been removed from testing because it is RC buggy on its own; if you want to get it in testing (and thus in the next stable) again, what you have to do is to *cooperate* with the current maintainer to fix its bugs, possibly provide the latest version of it, and so on. If its maintainer did not act so far, adding a new bug "please get virtuoso to testing" will certainly do nothing more than just adding one more (unuseful) bug to the pile of the virtuoso bugs. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#671944: Bug#671391: Reassign bugs to nepomuk daemon (which sits in kde-runtime)
Hi, > > - Supposedly, neither virtuoso nor nepomuk is the right place to > > report the bug. > > So, what is the right place then? I hope you do not deny that there > > is a problem which needs to be fixed. > > You assume the way to fix things is "reporting a bug somewhere", which > isn't. > Virtuoso has been removed from testing because it is RC buggy on its > own; if you want to get it in testing (and thus in the next stable) > again, what you have to do is to *cooperate* with the current maintainer > to fix its bugs, possibly provide the latest version of it, and so on. I never assumed that reporting a bug magically fixes anything, nor did I say so. If I find a problem in a package and I am pretty sure it is a bug (and not just a configuration issue), I report it if that has not yet been done. Then I know that the developers are aware of the issue, and I get informed when it gets fixed - and maybe if someone or myself can add additional valuable information, it can be added so it's all tracked in one place. I thought about this problem the same way. That's all I wanted to do. I am sorry if I upset you, that was in no way my intention. Also, now that you are aware of the issue, I won't waste your time with more emails after this one. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205091430.27981.p...@ralfj.de
Bug#671932: [plasma-desktop] segmentation fault with python-based plasmoids
Package: plasma-desktop Version: 4:4.7.4-2+b1 --- Please enter the report below this line. --- Plasma-desktop crashes when adding a python-based plasmoid like plasma-widget- veromix (from unstable/Sid repos) (doesn't mind if it goes to desktop, panel, or systray) or other like MyEpisodes and Tail (both of them old-plasmoids from kde-look.org). Without any of these widgets present, plasma-desktop works with no problem. --- System information. --- Architecture: i386 Kernel: Linux 3.2.0-2-686-pae Debian Release: wheezy/sid 900 unstablewww.debian-multimedia.org 900 unstableftp.debian.org 800 experimentalftp.debian.org 101 experimental-snapshots qt-kde.debian.net --- Package information. --- Depends (Version) | Installed ===-+-=== kde-runtime | 4:4.7.4-2 libc6 (>= 2.4) | 2.13-32 libkcmutils4 (>= 4:4.7) | 4:4.7.4-4 libkdecore5 (>= 4:4.7) | 4:4.7.4-4 libkdeui5(>= 4:4.7) | 4:4.7.4-4 libkephal4abi1 (= 4:4.7.4-2+b1) | 4:4.7.4-2+b1 libkfile4(>= 4:4.7) | 4:4.7.4-4 libkidletime4(>= 4:4.7) | 4:4.7.4-4 libkio5 (>= 4:4.7) | 4:4.7.4-4 libknewstuff3-4 (>= 4:4.7) | 4:4.7.4-4 libktexteditor4 (>= 4:4.7) | 4:4.7.4-4 libkworkspace4 (= 4:4.7.4-2+b1) | 4:4.7.4-2+b1 libplasma3 (>= 4:4.7.0) | 4:4.7.4-4 libplasmagenericshell4 (= 4:4.7.4-2+b1) | 4:4.7.4-2+b1 libqt4-dbus(>= 4:4.6.1) | 4:4.8.1-1 libqt4-xml (>= 4:4.5.3) | 4:4.8.1-1 libqtcore4 (>= 4:4.7.0~beta1) | 4:4.8.1-1 libqtgui4 (>= 4:4.6.1) | 4:4.8.1-1 libsolid4(>= 4:4.7) | 4:4.7.4-4 libstdc++6 (>= 4.1.1) | 4.7.0-7 libtaskmanager4abi2(= 4:4.7.4-2+b1) | 4:4.7.4-2+b1 libx11-6| 2:1.4.99.901-2 libxext6| 2:1.3.1-2 plasma-widgets-workspace (= 4:4.7.4-2+b1) | 4:4.7.4-2+b1 kde-wallpapers-default | 4:4.7.4-2 Recommends (Version) | Installed -+-=== kde-workspace| Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part.
Bug#671932: [plasma-desktop] [plasma-desktop] segmentation fault with python-based plasmoids
Package: plasma-desktop Version: 4:4.7.4-2+b1 --- Please enter the report below this line. --- oops! forgot attach crash report... Here it is. Application: Àrea de treball de l'escriptori Plasma (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". [Current thread is 1 (Thread 0xafdd6730 (LWP 9348))] Thread 2 (Thread 0xace2bb70 (LWP 9349)): #0 0xb7772424 in __kernel_vsyscall () #1 0xb7622a26 in poll () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #2 0xb2b7968b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb2b6bc6e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb2b6bdc1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb63d8647 in QEventDispatcherGlib::processEvents (this=0x9f50500, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb63a404d in QEventLoop::processEvents (this=0xace2b1d0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb63a42e9 in QEventLoop::exec (this=0xace2b1d0, flags=...) at kernel/qeventloop.cpp:204 #8 0xb628ce1c in QThread::exec (this=0x9f8d850) at thread/qthread.cpp:501 #9 0xb63815cd in QInotifyFileSystemWatcherEngine::run (this=0x9f8d850) at io/qfilesystemwatcher_inotify.cpp:248 #10 0xb6290300 in QThreadPrivate::start (arg=0x9f8d850) at thread/qthread_unix.cpp:298 #11 0xb22ada11 in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1 #12 0x5c8b0824 in ?? () #13 0xbab80424 in ?? () #14 0x6500 in ?? () #15 0x001015ff in ?? () #16 0xd389 in ?? () #17 0xfff0013d in ?? () #18 0xc30173ff in ?? () #19 0x0def95e8 in ?? () #20 0xcfc18100 in ?? () #21 0x8b0012dd in ?? () #22 0x0889 in ?? () #23 0x29d231ff in ?? () #24 0x118965c2 in ?? () #25 0xebffc883 in ?? () #26 0x909090e2 in ?? () #27 0x81e58955 in ?? () #28 0xa4ec in ?? () #29 0xf45d8900 in ?? () #30 0x0def65e8 in ?? () #31 0xa3c38100 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 1 (Thread 0xafdd6730 (LWP 9348)): [KCrash Handler] #7 createClassType (client=0x9ad92740, ctd=0x9ad9a740, mod_dict=) at /tmp/buildd/sip4-4.13.2/siplib/siplib.c:5502 #8 0xa49eac64 in sip_api_init_module (client=0x9ad92740, mod_dict=) at /tmp/buildd/sip4-4.13.2/siplib/siplib.c:1418 #9 0x9ac21977 in initkdecore () at sip/kdecore/sipkdecorepart0.cpp:5361 #10 0x9e35253c in _PyImport_LoadDynamicModule () from /usr/lib/libpython2.7.so.1.0 #11 0x9e408370 in load_module.39532 () from /usr/lib/libpython2.7.so.1.0 #12 0x9e4085d9 in import_submodule.39551 () from /usr/lib/libpython2.7.so.1.0 #13 0x9e3eee59 in load_next.39556 () from /usr/lib/libpython2.7.so.1.0 #14 0x9e408c1e in import_module_level.isra.9 () from /usr/lib/libpython2.7.so.1.0 #15 0x9e402597 in PyImport_ImportModuleLevel () from /usr/lib/libpython2.7.so.1.0 #16 0x9e313e33 in builtin___import__ () from /usr/lib/libpython2.7.so.1.0 #17 0x9e41a2fd in PyCFunction_Call () from /usr/lib/libpython2.7.so.1.0 #18 0x9e418dd4 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0 #19 0x9e419a1f in call_function_tail () from /usr/lib/libpython2.7.so.1.0 #20 0x9e3b82b0 in PyObject_CallFunction () from /usr/lib/libpython2.7.so.1.0 #21 0x9e352c8f in PyImport_Import () from /usr/lib/libpython2.7.so.1.0 #22 0x9e353ff2 in PyImport_ImportModule () from /usr/lib/libpython2.7.so.1.0 #23 0xa49e3198 in sip_api_export_module (client=0x9b1fada0, api_major=8, api_minor=1, unused=0x0) at /tmp/buildd/sip4-4.13.2/siplib/siplib.c:1242 #24 0x9af62579 in initplasma () at sip/plasma/sipplasmapart0.cpp:3012 #25 0x9e35253c in _PyImport_LoadDynamicModule () from /usr/lib/libpython2.7.so.1.0 #26 0x9e408370 in load_module.39532 () from /usr/lib/libpython2.7.so.1.0 #27 0x9e4085d9 in import_submodule.39551 () from /usr/lib/libpython2.7.so.1.0 #28 0x9e3eee59 in load_next.39556 () from /usr/lib/libpython2.7.so.1.0 #29 0x9e408c1e in import_module_level.isra.9 () from /usr/lib/libpython2.7.so.1.0 #30 0x9e402597 in PyImport_ImportModuleLevel () from /usr/lib/libpython2.7.so.1.0 #31 0x9e313e33 in builtin___import__ () from /usr/lib/libpython2.7.so.1.0 #32 0x9e41a2fd in PyCFunction_Call () from /usr/lib/libpython2.7.so.1.0 #33 0x9e418dd4 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0 #34 0x9e4197bb in PyEval_CallObjectWithKeywords () from /usr/lib/libpython2.7.so.1.0 #35 0x9e35f3b8 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #36 0x9e317c34 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #37 0x9e317f83 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0 #38 0x9e319792 in PyImport_ExecCodeModuleEx () from /usr/lib/libpython2.7.so.1.0 #39 0x9e407e7c in load_source_module.39493 () from /usr/lib/libpython2.7.so.1.0 #40 0x9e4085d9 in import_submodule.39551 () from /usr/lib/libpython2.7.so.1.0 #41 0x9e3eee59 in load_next.39556 () from /usr/lib/libpython2.7.so.1.0 #42 0x9e408bdd in import_module_level.isra.9 () from /usr/lib/libpython2.7.so.1.0 #43 0x9e402597 in PyImport_ImportModuleLevel () from /usr/lib/libpython2.7.s
Bug#580706: kmail crashes with akonadi
I seem to be experiencing the same bug in debian unstable (amd64) after upgrading to: akonadi-backend-sqlite 1.6.2-2+b1 akonadi-backend-mysql 1.6.2-2 mysql-common 5.5.23-2 mysql-server-core 5.1.62-1 libmysqlclient18 5.5.23-2 I also have libmysqlclient16 5.1.62-1 installed. Even after running 'akonadictl stop && rm -r ~/.local/share/akonadi' I am unable to start either kmail or akonadiconsole; see attached log files. Hopefully the bug Erik found in mysql will solve this frustrating problem with akonadi and kmail! akonadi-server.log Description: Binary data akonadiconsole.log Description: Binary data akonadi-kmail.log Description: Binary data
Bug#580706: kmail crashes with akonadi
Looks like it can't find the mysqld executable. What does which mysqld say for you? Cheers, Kevin signature.asc Description: This is a digitally signed message part.
Bug#580706: kmail crashes with akonadi
> Looks like it can't find the mysqld executable. > What does which mysqld say for you? mysql-server is not installed, so there is no mysqld available. However I am using akonadi-backend-sqlite, so mysqld should not be required for akonadi to work. If it is, then there is either a bug in akonadi-backend-sqlite or a missing dependency in akonadi-server. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/53bee1d14dd9b58997edd4f8272bfe03.squir...@www.benkay.net
Bug#580706: kmail crashes with akonadi
please unsubscribe -Original Message- From: benja...@benkay.net Sent: Wednesday, May 09, 2012 6:50 PM To: Kevin Krammer ; 580...@bugs.debian.org Subject: Bug#580706: kmail crashes with akonadi Looks like it can't find the mysqld executable. What does which mysqld say for you? mysql-server is not installed, so there is no mysqld available. However I am using akonadi-backend-sqlite, so mysqld should not be required for akonadi to work. If it is, then there is either a bug in akonadi-backend-sqlite or a missing dependency in akonadi-server. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5EBA8B3967F943418CD022A9C429FDF4@workPC
Bug#580706: kmail crashes with akonadi
Hello, On trečiadienis 09 Gegužė 2012 19:50:30 benja...@benkay.net wrote: > > Looks like it can't find the mysqld executable. > > What does which mysqld say for you? > > mysql-server is not installed, so there is no mysqld available. However I > am using akonadi-backend-sqlite, so mysqld should not be required for > akonadi to work. If it is, then there is either a bug in > akonadi-backend-sqlite or a missing dependency in akonadi-server. You still need to edit akonadi configuration after switching the backed. See /usr/share/doc/akonadi-server/README.Debian.gz -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Bug#580706: kmail crashes with akonadi
> You still need to edit akonadi configuration after switching the backed. Thank you! Although this was probably unrelated to this bug, editing akonadiserverrc gets kmail working again for me. However, has anyone tested the directions in the README.Debian recently? To make akonadi use the SQLITE3 driver, it appears that one needs to use: [%General] Driver=QSQLITE3 [SQLITE3] Name=/full/path/to/akonadi/db/file Instead of : [General] Driver=QSQLITE3 [SQLITE3] Name= Should I submit a bug against akonadi-backend-sqlite? -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2facb35724663db8a741de574d7fad7f.squir...@www.benkay.net
