[kopete-devel] [Bug 143206] Crash upon loing on to msn network
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=143206 axion axion demon nl changed: What|Removed |Added CC||axion axion demon nl --- Additional Comments From axion axion demon nl 2007-03-19 08:47 --- Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240815936 (LWP 27983)] [KCrash handler] #5 0xb6309d08 in __dynamic_cast () from /usr/lib/libstdc++.so.6 #6 0xb5b37967 in MSNAccount::findContactByGuid () from /opt/kde/lib/libkopete_msn_shared.so.0 #7 0xb5b642c2 in MSNNotifySocket::parseCommand () from /opt/kde/lib/libkopete_msn_shared.so.0 #8 0xb5b48bc1 in MSNSocket::parseLine () from /opt/kde/lib/libkopete_msn_shared.so.0 #9 0xb5b4de14 in MSNSocket::slotReadLine () from /opt/kde/lib/libkopete_msn_shared.so.0 #10 0xb5b4f9f0 in MSNSocket::slotDataReceived () from /opt/kde/lib/libkopete_msn_shared.so.0 #11 0xb5b51e74 in MSNSocket::qt_invoke () from /opt/kde/lib/libkopete_msn_shared.so.0 #12 0xb5b5f80c in MSNNotifySocket::qt_invoke () from /opt/kde/lib/libkopete_msn_shared.so.0 #13 0xb68de004 in QObject::activate_signal () from /usr/lib/qt/lib/libqt-mt.so.3 #14 0xb68de79c in QObject::activate_signal () from /usr/lib/qt/lib/libqt-mt.so.3 #15 0xb7017d0c in KNetwork::KClientSocketBase::readyRead () from /opt/kde/lib/libkdecore.so.4 #16 0xb7017d4a in KNetwork::KClientSocketBase::slotReadActivity () from /opt/kde/lib/libkdecore.so.4 #17 0xb702096d in KNetwork::KBufferedSocket::slotReadActivity () from /opt/kde/lib/libkdecore.so.4 #18 0xb7020e8f in KNetwork::KBufferedSocket::qt_invoke () from /opt/kde/lib/libkdecore.so.4 #19 0xb68de004 in QObject::activate_signal () from /usr/lib/qt/lib/libqt-mt.so.3 #20 0xb68de62b in QObject::activate_signal () from /usr/lib/qt/lib/libqt-mt.so.3 #21 0xb6c1e990 in QSocketNotifier::activated () from /usr/lib/qt/lib/libqt-mt.so.3 #22 0xb68fb070 in QSocketNotifier::event () from /usr/lib/qt/lib/libqt-mt.so.3 #23 0xb687946f in QApplication::internalNotify () from /usr/lib/qt/lib/libqt-mt.so.3 #24 0xb687960c in QApplication::notify () from /usr/lib/qt/lib/libqt-mt.so.3 #25 0xb6ec4ac5 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4 #26 0xb686cb33 in QEventLoop::activateSocketNotifiers () from /usr/lib/qt/lib/libqt-mt.so.3 #27 0xb6825481 in QEventLoop::processEvents () from /usr/lib/qt/lib/libqt-mt.so.3 #28 0xb688fb91 in QEventLoop::enterLoop () from /usr/lib/qt/lib/libqt-mt.so.3 #29 0xb688fae6 in QEventLoop::exec () from /usr/lib/qt/lib/libqt-mt.so.3 #30 0xb68785cf in QApplication::exec () from /usr/lib/qt/lib/libqt-mt.so.3 #31 0x0808000b in main () ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 143206] New: Crash upon loing on to msn network
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=143206 Summary: Crash upon loing on to msn network Product: kopete Version: unspecified Platform: Slackware Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kopete-devel kde org ReportedBy: axion axion demon nl Version: 0.12.4 (using KDE KDE 3.5.4) Installed from:Slackware Packages Compiler: gcc version 3.4.6 OS:Linux I have 2 msn accounts, but only one of the two crashes everytime I try to logon. All other account with other protocols don't crash. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Core/GUI Split in libkopete
On Sunday 18 March 2007 16:09:35 Matt Rogers wrote: > The answer to the question of "Which way should we do it?" lies solely upon > the outcome of "How important is the core/gui split to us really?" > > So, how important is the core/gui split to us really? One of the areas Will is doing some research is using Kopete protocols as Telepathy Connection Managers. In order to do this you have to emulate some way a part of the Kopete API. This is hard if the API exposes the UI too much. I'd consideer it important. Also, we don't know how long we will use our GUI classes, probably in the future the desktop provides 1st class objects and UI items for things like people and presence. Duncan ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Core/GUI Split in libkopete
Le dimanche 18 mars 2007, Ben Aceler a écrit : > Can I press the RMB on an ICQ# to start conversation? No. I need to copy it > to Kopete... I think that clicking on a ICQ link URL open a chat with the contact, yes In KDE4, clicking on a URL of type xmpp: will do the action (as described in the XEP-0147) > Can I split a window in Koffice to see document in the left > side and jabber dialog in the right? No you can't. But you can place your two windows next each other to have the same result. And again, all this feature are not related to a core/gui separation. > Though, I mean the special GUI, not only translation and remote control of > Kopete. The split will make possible not to install whole kopete, when I > need only groupchat in Koffice, for example. Eh, you are not forced to install every Kopete plugins. But yes, you will need the whole Kopete core. And spending lot of times and adding complication to the code just for that is not worth. > Am I wrong? I think that you are just not aware of Kopete and KDE insternals I consider this as close. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 138376] kopete does not list all contacts in my yahoo buddy list groups
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=138376 andre duffeck de changed: What|Removed |Added CC||rrr.junior gmail com --- Additional Comments From andre duffeck de 2007-03-18 21:51 --- *** Bug 143191 has been marked as a duplicate of this bug. *** ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 143191] Kopete does not show all my contacts (Yahoo)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=143191 andre duffeck de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Component|general |Yahoo Plugin Resolution||DUPLICATE --- Additional Comments From andre duffeck de 2007-03-18 21:51 --- *** This bug has been marked as a duplicate of 138376 *** ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 143191] New: Kopete does not show all my contacts (Yahoo)
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=143191 Summary: Kopete does not show all my contacts (Yahoo) Product: kopete Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kopete-devel kde org ReportedBy: rrr.junior gmail com Version:(using KDE KDE 3.5.6) Installed from:Ubuntu Packages OS:Linux I have a problem with kopete showing my contact list. This happens only if I add a couple of yahoo account with quite a large number of contacts (a couple of hundreds). My list gets truncated somehow and the contacts after a letter are not showed (for example my brother used it to login to his account and all his contacts from the letter k and after were not showed). ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Core/GUI Split in libkopete
В сообщении от 18 марта 2007 Olivier Goffart написал(a): > Le dimanche 18 mars 2007, Ben Aceler a écrit : > > В сообщении от 18 марта 2007 Olivier Goffart написал(a): > > > that would require a strong split. But I'm not sure someone will use it > > > (KDE dependencies, ) > > > Using protocol library in our protocols is a better way to share the > > > code. (and telepathy is another) > > > > It will not useful outside KDE, but look at the KDE itself! What about to > > create a message dialog in kadressbook? Or to place "send message" button > > near standard ICQ or Jabber information in Konqueror? Kopete integration > > with Koffice for a share work? I think, it is a tasty possibilities :) > > Moreover, Konversation IRC system is better than Kopete's. Why not use > > the same system with two applications? > > WTF? this already exist in Kopete, and use the same system as > conversation. It use KIMProxy in KDE3, and will probably use Telepathy in > KDE4 > It has nothing to do with a core/gui separation. Can I press the RMB on an ICQ# to start conversation? No. I need to copy it to Kopete... Can I split a window in Koffice to see document in the left side and jabber dialog in the right? Though, I mean the special GUI, not only translation and remote control of Kopete. The split will make possible not to install whole kopete, when I need only groupchat in Koffice, for example. Am I wrong? -- mailto://[EMAIL PROTECTED] jabber://[EMAIL PROTECTED] http://aceler.livejournal.com/ ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Core/GUI Split in libkopete
Le dimanche 18 mars 2007, Ben Aceler a écrit : > В сообщении от 18 марта 2007 Olivier Goffart написал(a): > > that would require a strong split. But I'm not sure someone will use it > > (KDE dependencies, ) > > Using protocol library in our protocols is a better way to share the > > code. (and telepathy is another) > > It will not useful outside KDE, but look at the KDE itself! What about to > create a message dialog in kadressbook? Or to place "send message" button > near standard ICQ or Jabber information in Konqueror? Kopete integration > with Koffice for a share work? I think, it is a tasty possibilities :) > Moreover, Konversation IRC system is better than Kopete's. Why not use the > same system with two applications? WTF? this already exist in Kopete, and use the same system as conversation. It use KIMProxy in KDE3, and will probably use Telepathy in KDE4 It has nothing to do with a core/gui separation. pgp19iIMeZgtb.pgp Description: PGP signature ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Core/GUI Split in libkopete
В сообщении от 18 марта 2007 Olivier Goffart написал(a): > Le dimanche 18 mars 2007, Oleg Girko a écrit : > > Hello! > > > > On Sunday 18 March 2007, Matt Rogers wrote: > > but also have significant impact outside of Kopete. Imagine, > > for example, transports for Jabber server, sharing protocol support with > > Kopete codebase. > > that would require a strong split. But I'm not sure someone will use it > (KDE dependencies, ) > Using protocol library in our protocols is a better way to share the code. > (and telepathy is another) It will not useful outside KDE, but look at the KDE itself! What about to create a message dialog in kadressbook? Or to place "send message" button near standard ICQ or Jabber information in Konqueror? Kopete integration with Koffice for a share work? I think, it is a tasty possibilities :) Moreover, Konversation IRC system is better than Kopete's. Why not use the same system with two applications? -- mailto://[EMAIL PROTECTED] jabber://[EMAIL PROTECTED] http://aceler.livejournal.com/ ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Core/GUI Split in libkopete
Le dimanche 18 mars 2007, Oleg Girko a écrit : > Hello! > > On Sunday 18 March 2007, Matt Rogers wrote: > > The answer to the question of "Which way should we do it?" lies solely > > upon the outcome of "How important is the core/gui split to us really?" > > > > So, how important is the core/gui split to us really? I don't think a strong core/gui split is require. A stronf split will IMO add complexity. (We will have to add wrapper to get UI in plugins, or to show messages or dialogs, ) And i don't think it will add benefit. But of course, when possible, i think we should do the split in the structure, it's a good design, and Kopete is already designed like that, i don't see so much to change. > I'm not an active developer at the moment, but I think, that splitting out > GUI from core may lead not only to cleaner and more maintainable code of > Kopete itself, And I think that the current Kopete design is good for that (regarding core/gui only), and splitting more will not help, and can even be worse. > but also have significant impact outside of Kopete. Imagine, > for example, transports for Jabber server, sharing protocol support with > Kopete codebase. that would require a strong split. But I'm not sure someone will use it (KDE dependencies, ) Using protocol library in our protocols is a better way to share the code. (and telepathy is another) -- Gof pgpu41Yu3iYnN.pgp Description: PGP signature ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
Re: [kopete-devel] Core/GUI Split in libkopete
Hello! On Sunday 18 March 2007, Matt Rogers wrote: > As I've been going through and working on the model/view stuff for the > contactlist, I've come across two ways to do it. > > 1. Make Kopete::ContactListElement a QStandardItem so that Group, > Metacontact, and Contact are all model items. > > 2. Leave as-is and make our current listview items be model items and wrap > the corresponding class. > > The answer to the question of "Which way should we do it?" lies solely upon > the outcome of "How important is the core/gui split to us really?" > > So, how important is the core/gui split to us really? I'm not an active developer at the moment, but I think, that splitting out GUI from core may lead not only to cleaner and more maintainable code of Kopete itself, but also have significant impact outside of Kopete. Imagine, for example, transports for Jabber server, sharing protocol support with Kopete codebase. -- Oleg Girko, http://www.infoserver.ru/~ol/ ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] Core/GUI Split in libkopete
Hi, As I've been going through and working on the model/view stuff for the contactlist, I've come across two ways to do it. 1. Make Kopete::ContactListElement a QStandardItem so that Group, Metacontact, and Contact are all model items. 2. Leave as-is and make our current listview items be model items and wrap the corresponding class. The answer to the question of "Which way should we do it?" lies solely upon the outcome of "How important is the core/gui split to us really?" So, how important is the core/gui split to us really? -- Matt pgpY4YfxD0mIU.pgp Description: PGP signature ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 143158] Can't copy text in chat window after copying text of the conversation
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=143158 --- Additional Comments From gentakojima yahoo es 2007-03-18 13:26 --- It's truth for me too. It's a bit annoying. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 143158] New: Can't copy text in chat window after copying text of the conversation
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=143158 Summary: Can't copy text in chat window after copying text of the conversation Product: kopete Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kopete-devel kde org ReportedBy: kungfoobar gmail com Version: 0.12.4 (using KDE 3.5.6, Kubuntu (edgy) 4:3.5.6-0ubuntu1~edgy1) Compiler: Target: i486-linux-gnu OS:Linux (i686) release 2.6.17-10-generic 1. Copy some text from the conversation, using ctrl+c shortcut 2. Write something in the chat textbox and try to copy it with ctrl+c: won't work The ctrl+c seems to always copy the chat window even if the focus is in the chat textbox. Altough I use the selection clipboard a lot, sometimes I need to use the ctrl+c/v one. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
[kopete-devel] [Bug 143157] New: Scroll goes one line up in some conversations when changing between tabs in a single window
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=143157 Summary: Scroll goes one line up in some conversations when changing between tabs in a single window Product: kopete Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kopete-devel kde org ReportedBy: kungfoobar gmail com Version: 0.12.4 (using KDE 3.5.6, Kubuntu (edgy) 4:3.5.6-0ubuntu1~edgy1) Compiler: Target: i486-linux-gnu OS:Linux (i686) release 2.6.17-10-generic Scroll goes one line up in some conversations when changing between tabs in a single window, needing to scroll down every time I change the tab to see the last message. All conversations fills the window (otherwise it wouldn't scroll). Using kONE skin. ___ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
