Bug#638573: kontact freezes, akonadi restart
Halo again, sometimes it works if I make a restart akonadictl restart. Last Time as it works I get the following messages: -snip- Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) search paths: (/usr/local/bin, /usr/bin, /bin, /usr/bin/X11, /usr/games, /usr/sbin, /usr/local/sbin, /usr/local/libexec, /usr/libexec, /opt/mysql/libexec, /opt/local/lib/mysql5/bin, /opt/mysql/sbin) Found mysql_install_db: Found mysqlcheck: Database akonadi opened using driver QMYSQL DbInitializer::run() checking table SchemaVersionTable checking table ResourceTable checking table CollectionTable checking table MimeTypeTable checking table PimItemTable checking table FlagTable checking table PartTable checking table CollectionAttributeTable checking relation PimItemFlagRelation checking relation CollectionMimeTypeRelation checking relation CollectionPimItemRelation DbInitializer::run() done skipping update 2 skipping update 3 skipping update 4 skipping update 8 skipping update 10 skipping update 12 skipping update 13 skipping update 14 skipping update 15 skipping update 16 skipping update 17 skipping update 18 skipping update 19 Akonadi::NepomukSearchEngine(0x9bc7e28) QObject(0x0) Database akonadi opened using driver QMYSQL Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) DataStore::unhideAllPimItems() Database akonadi opened using driver QMYSQL PLUGINS: /usr/share/akonadi/agents PLUGINS: (birthdaysresource.desktop, contactsresource.desktop, icalresource.desktop, imapresource.desktop, kabcresource.desktop, kcalresource.desktop, knutresource.desktop, kolabproxyresource.desktop, localbookmarksresource.desktop, maildirresource.desktop, maildispatcheragent.desktop, mboxresource.desktop, microblog.desktop, mtdummyresource.desktop, nepomukcalendarfeeder.desktop, nepomukcontactfeeder.desktop, nepomuktagresource.desktop, nntpresource.desktop, notesresource.desktop, pop3resource.desktop, vcarddirresource.desktop, vcardresource.desktop) search paths: (/usr/local/bin, /usr/bin, /bin, /usr/bin/X11, /usr/games) PLUGINS inserting: akonadi_birthdays_resource 1 (Resource) PLUGINS inserting: akonadi_contacts_resource 1 (Resource) PLUGINS inserting: akonadi_ical_resource 2 (Resource) PLUGINS inserting: akonadi_imap_resource 0 (Resource) PLUGINS inserting: akonadi_kabc_resource 2 (Resource) PLUGINS inserting: akonadi_kcal_resource 1 (Resource) PLUGINS inserting: akonadi_knut_resource 0 (Resource) PLUGINS inserting: akonadi_kolabproxy_resource 0 (Resource, Unique, NoConfig) PLUGINS inserting: akonadi_localbookmarks_resource 0 (Resource) PLUGINS inserting: akonadi_maildir_resource 1 (Resource) PLUGINS inserting: akonadi_maildispatcher_agent 0 (Unique, Autostart, NoConfig) PLUGINS inserting: akonadi_mbox_resource 0 (Resource) PLUGINS inserting: akonadi_microblog_resource 0 (Resource) PLUGINS inserting: akonadi_mailtransport_dummy_resource 0 (Resource, MailTransport) PLUGINS inserting: akonadi_nepomuk_calendar_feeder 0 (Unique, NoConfig) PLUGINS inserting: akonadi_nepomuk_contact_feeder 0 (Unique, Autostart, NoConfig) PLUGINS inserting: akonadi_nepomuktag_resource 0 (Resource, Virtual, Unique, NoConfig) PLUGINS inserting: akonadi_nntp_resource 0 (Resource) PLUGINS inserting: akonadi_notes_resource 0 (Resource) PLUGINS inserting: akonadi_pop3_resource 0 (Resource) PLUGINS inserting: akonadi_vcarddir_resource 0 (Resource) PLUGINS inserting: akonadi_vcard_resource 3 (Resource) Akonadi server is now operational. Database akonadi opened using driver QMYSQL void Nepomuk::Query::QueryServiceClient::close() Known subscriber akonadi_birthdays_resource_0 subscribes again Database akonadi opened using driver QMYSQL Database akonadi opened using driver QMYSQL Database akonadi opened using driver QMYSQL akonadi_contacts_resource_0(4198)/libkdepim Akonadi::PluginLoader::scan: missing or empty X-KDE-ClassName value in /usr/share/kde4/apps/akonadi/plugins/serializer/akonadi_serializer_microblog.desktop akonadi_contacts_resource_0(4198)/libkdepim Akonadi::PluginLoader::scan: missing or empty X-KDE-ClassName value in /usr/share/kde4/apps/akonadi/plugins/serializer/akonadi_serializer_mail.desktop akonadi_contacts_resource_0(4198)/libkdepim Akonadi::PluginLoader::scan: missing or empty X-KDE-ClassName value in /usr/share/kde4/apps/akonadi/plugins/serializer/akonadi_serializer_bookmark.desktop akonadi_contacts_resource_0(4198)/libkdepim Akonadi::PluginLoader::scan: missing or empty X-KDE-ClassName value in /usr/share/kde4/apps/akonadi/plugins/serializer/akonadi_serializer_contactgroup.desktop akonadi_contacts_resource_0(4198)/libkdepim Akonadi::PluginLoader::scan: missing or empty X-KDE-ClassName value in /usr/share/kde4/apps/akonadi/plugins/serializer/akonadi_serializer_kcalcore.desktop
Re: odbc-postgresql: can't be installed together with KDE any more
reassign 639300 soprano retitle 639300 please build against unixodbc-dev instead of libiodbc2-dev thanks Hi folks, This week with Christoph Berg's help, unixodbc has been converted for multiarch in unstable along with the common drivers: libmyodbc, tdsodbc, and odbc-postgresql. The converted drivers are now all installed in /usr/lib/arch/odbc, and the /etc/odbcinst.ini config has been updated to use relative paths instead of absolute ones. libiodbc2, which has been orphaned for nearly three years, has *not* been updated for multiarch, and so libiodbc will fail to locate these drivers on disk. As a result, these drivers declare a Breaks: against libiodbc2. I do not intend to update libiodbc2 for multiarch. Instead, I would like to propose its removal from the archive. Historically, we have carried both unixodbc and libiodbc2 in the archive to avoid a circular build-dependency: Qt build-depends on ODBC for its database support, and UnixODBC build-depends on Qt for its GUI tools. The most recent upstream version of UnixODBC resolves this, because in addition to being updated for Qt4, the latest upstream release also splits the GUI tools into a separate source distribution, which I have just uploaded to unstable. So I am reassigning this bug to soprano. KDE maintainers, please switch soprano to build against unixodbc-dev instead of libiodbc2-dev. (I will file separate bugs against the other reverse-dependencies, but for soprano someone has beaten me to it.) Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Processed: Re: odbc-postgresql: can't be installed together with KDE any more
Processing commands for cont...@bugs.debian.org: reassign 639300 soprano Bug #639300 [odbc-postgresql] odbc-postgresql: can't be installed together with KDE any more Bug reassigned from package 'odbc-postgresql' to 'soprano'. Bug No longer marked as found in versions psqlodbc/1:09.00.0310-2. retitle 639300 please build against unixodbc-dev instead of libiodbc2-dev Bug #639300 [soprano] odbc-postgresql: can't be installed together with KDE any more Changed Bug title to 'please build against unixodbc-dev instead of libiodbc2-dev' from 'odbc-postgresql: can't be installed together with KDE any more' thanks Stopping processing here. Please contact me if you need assistance. -- 639300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639300 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.131434666814161.transcr...@bugs.debian.org
Re: kdepim and akonadi
Le mardi 23 août 2011 16:11:32, Dietz Pröpper a écrit : BasaBuru: On Lunes, 22 de Agosto de 2011 23:38:40 Dietz Pröpper escribió: I don't need one of these. Google sync was a nice try, right now I'm writing a Android sync that relies on something simple and not Google based. No, will never go official, just for personal usage for the moment. I only need a means to sync my phone to my desktop. Nothing more. And *no* remote storage. When you are publication the android sync? Is very interesting. Probably never. Hi all, same problem here with kdepim 4.4 and akonadi_gcal_resource. I find a solution by adding a standard kressource providing CalDAV support in kdepim 4.4. I just install de deb package (kdepim-caldav_1.2.0-1_amd64.deb) availlable on http://code.google.com/p/kcaldav/ and everything works like a charm (in both ways) Ewilly -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108261255.44397.ewi...@free.fr
akonadi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Are people here using akonadi or any of the tools using the akonadi framework, in their regular workflow? (Email, PIM) Also, the same with Nepomuk. Are people using it or is it just sitting disabled in everyone's config? - -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJOV8oeAAoJEKY6WKPy4XVp8aUP/jHFCw7U/MrnD/oGkLsEn6Rr 3nruZ8xPjeFif7bDcxlympMdxjcOw0H/d+m8+0pBtF1X5hiXx3oxX1kO7E/Q++PX lIqJUqEpIlKOhG3Kps30k4OSrr5bv0YSxspJx4BYYDD27lY/jX2rjUB2B13RhNC3 Ypx//4gUvuSd68J0QvI7mDO5glH+PswAOlu2sfUbsOFuiCdkcgFKZmQ+YAHnw402 Adzc0Lo+glBKMy6sRDAOqOWaUOwRhtvuZA56pnNiG0TaTPqh8lM24uNFdWuZTisG QHs0nbRySZ3ZLDgI4wlqA9/ZuG8+Vf9Ij6HtvC79TJjO4ZSrYRYkmdvM+/WMiqBy WydDI8qmZWZpX7JGVRO9CgXaejLdCVD4spvFb8ne0UzN/rmdT4E+/vCoXMQ7axPl 8dmgRvHnCA9H4xFFcRnkEWXtb2n7eRIH6MqkZQk81hY1ehq6tSjaN2s13xUBDiV+ MUzg/4Fexou4Uwr0mkWNKEP9zbOwDVOTDE6u6XSOXKjnhbBZDaEAyQGes/zEkHHW DlD1ctlmgucebaf7/ql6Q3TBiBYxNyZP1G38FTsU1bdR5WyidUm6iWpuhio1iCuS SVb7sPGFQgciu2InGsCq8ctak8J81AHssXO4I/9FEkEdQ7MP6m1hPPMcx6mm5hGg z8ZIpCA1Rt4FJAD47w6Q =Hqf9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/u9uki8-reo@news.researchut.com
Re: kdebug defaults/build options
Am Friday, 19. August 2011 schrieb Bruce Sass: How about using logrotate for .xsession-errors? Sure, it is more of a bandage than anything else though, eh. Frankly, no. IMHO that would be a sensible thing to do. .xsession-errors can grow indefinitely when people are using suspend-to-* and keep their session running until some package update needs a reboot. So there's no difference to the logfiles in /var/log. That doesn't legitimate apps to produce so many log entries, though. Why is Debian's KDE so verbose? Is it a concious decision by KDE and individual users are expected to use kdebugdialog if they don't like it? Is there a system wide setting so the admin of a multi-user box can set the debug/warn/error messaging behaviour for everyone? Is Debian neglecting to set a flag somewhere which would quiet things down? Should we be talking to the developers of individual apps because it is not really a KDE problem? I have no idea what Debian's policy is, so I can only pass my very own opinion. Apps and libs should be as quiet as possible by default. They should only log assertion failures, i.e. critical problems. It should be possible to launch an app in a terminal (in the background) and keep working in the same terminal. Everything other than critical problems should be made available on demand, e.g. through kdebugdialog. Cheers, Carsten signature.asc Description: This is a digitally signed message part.
Re: akonadi
On August 26, 2011 10:30:22 AM Ritesh Raj Sarraf wrote: Are people here using akonadi or any of the tools using the akonadi framework, in their regular workflow? (Email, PIM) Maybe, but not because I want to... at this point I see my options for that box as: check if KDE-4 can be built without akonadi; Oldstable with KDE-3.5.10; Stable + Trinity's KDE-3.5.12; not-KDE Also, the same with Nepomuk. Are people using it or is it just sitting disabled in everyone's config? Disabled as a service in itself, but it still gets started by akonadi. :( AFAICT, ATM: I have no use for the nepomuk/strigi semantic desktop stuff; Akonadi is just simply overkill for me, and it doesn't help that the box I currently use for email can't afford the extra/unnecessary overhead (even if it didn't leave soprano and nepomuk processes lying around after a ssh -X host kmail). - Bruce -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108261528.09688.bms...@shaw.ca
Re: akonadi
On August 26, 2011 03:28:09 PM Bruce Sass wrote: if it didn't leave soprano and nepomuk processes lying around after a hmm, make that, virtuoso and nepomuk... PID PPID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 25283 1 user 20 0 45388 5772 5364 S 0.0 1.1 0:00.30 /usr/bin/nepomukserver 25293 1 user 39 19 50004 33m 6272 S 0.0 6.7 1:04.17 /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_X25288.ini +wait -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108261543.14835.bms...@shaw.ca
Re: kdebug defaults/build options
On August 26, 2011 03:06:58 PM Carsten Pfeiffer wrote: Am Friday, 19. August 2011 schrieb Bruce Sass: How about using logrotate for .xsession-errors? Sure, it is more of a bandage than anything else though, eh. Frankly, no. IMHO that would be a sensible thing to do. .xsession-errors can grow indefinitely when people are using suspend-to-* and keep their session running until some package update needs a reboot. So there's no difference to the logfiles in /var/log. That doesn't legitimate apps to produce so many log entries, though. OK, bandage was directed at the specific case of using logrotate to deal with overly verbose software. Why is Debian's KDE so verbose? Is it a concious decision by KDE and individual users are expected to use kdebugdialog if they don't like it? Is there a system wide setting so the admin of a multi-user box can set the debug/warn/error messaging behaviour for everyone? Is Debian neglecting to set a flag somewhere which would quiet things down? Should we be talking to the developers of individual apps because it is not really a KDE problem? I have no idea what Debian's policy is, so I can only pass my very own opinion. Apps and libs should be as quiet as possible by default. They should only log assertion failures, i.e. critical problems. It should be possible to launch an app in a terminal (in the background) and keep working in the same terminal. Everything other than critical problems should be made available on demand, e.g. through kdebugdialog. Thanks! -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108261546.29761.bms...@shaw.ca
