Nabble - konversation-devel

[Bug 218985] more irc nicks for one contact in adressbook

2009-12-18T16:06:45Z

https://bugs.kde.org/show_bug.cgi?id=218985

Aleksander Balicki <all3@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 218985] New: more irc nicks for one contact in adressbook

2009-12-16T12:49:54Z

https://bugs.kde.org/show_bug.cgi?id=218985

Summary: more irc nicks for one contact in adressbook
Product: konversation
Version: 1.2.1
Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
AssignedTo: konversation-devel@...
ReportedBy: all3@...

Version: 1.2.1 (using KDE 4.3.4)
Compiler: gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5)
OS: Linux
Installed from: Gentoo Packages

When I click rmb on friend's nick on IRC channel, there's an option to assign
adressbook contact to a nick. Usually some people have more than one client
connected to server, but konversation can connect one contact with only one
nick.

I would like the option to connect more than one nick to a contact.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

Re: Information on Gitorious setup

2009-12-16T12:01:25Z

Here's an update on how things are currently set up, as there
have been some changes.

First of, a short overview over the Gitorious permission model.
Every repository has a list of "collaborators". A collaborator
can be an individuum or a team. Any collaborator can have any
combination of three flags: commit, review, admin. "Commit"
allows commit access (i.e. pushing up new commits), those with
"Review" receive email notifications about merge requests (pro-
vided merge requests are enabled for the repository, and also
the sending of merge request emails) and can change the status
of merge requests, and those with "Admin" can edit the reposi-
tory settings and its list of collaborators.

The "Konversation" project is owned by the "kde-developers"
team, and by extension so is the "konversation" repository,
which means the repository started out with "kde-developers"
in its collaborators list, with all three flags.

Then a "konversation-reviewers" team was created (with me and
Peter as admins), added as a collaborator, and it got the
"Review" flag (and only that flag). In turn, the "Review"
flag was removed from kde-developers, leaving it with only
"Commit" and "Admin".

Since then, a new "kde-sysadmin" group was created which the
KDE system administrators are members of. This group was add-
ed to the "konversation" repository as a collaborator with
the "Admin" flag, and the "Admin" flag was removed from "kde-
developers".

Which is sensible in principle, but has the problem that it
left no one in the Konversation team with the ability to
edit the repository. Being able to edit the repository is
important to be able to toggle the "Deny force push" check-
box in the repository settings: In order to add a new re-
lease tag, you need to be able to force push. Yes, this is
clumsy, but that's how it works on Gitorious at the moment.

To fix this problem, I was now added to the "konversation"
repository as a collaborator with the "Admin" flag, and ha-
ve since added Peter as a collaborator with the admin flag
as well.

So to sum up the current list of collaborators on the repos:

kde-sysadmin: Admin
Eike Hein: Admin
Peter Simonsson: Admin
kde-developers: Commit
konversation-reviewers: Review

konversation-reviewers admins: Eike Hein, Peter Simonsson.

--
Best regards,
Eike Hein
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 214258] Commands like /op and /deop cause an invalid MODE command to be send preceding a correct one

2009-12-15T14:08:35Z

https://bugs.kde.org/show_bug.cgi?id=214258

Travis McHenry <wordsizzle@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED

--- Comment #3 from Travis McHenry <wordsizzle gmail com> 2009-12-15 23:08:33 ---
commit 446b3bc892090221aa37b6a2c83901c0ea7b92a7
Author: Travis McHenry <wordsizzle@...>
Date: Tue Dec 15 14:58:24 2009 -0700

Fix the number of mode chars sent in op/deop

Previously the modes portion would fill up for all the nicks
so if you had 5 nicks, that would split into two lines with 3
on the first and 2 on the second. But on both you would have 5
mode chars. Now we add one mode per nick at the same time the
nick is added.
BUG:214258

diff --git a/src/irc/outputfilter.cpp b/src/irc/outputfilter.cpp
index fc43d69..fd9cb8b 100644
--- a/src/irc/outputfilter.cpp
+++ b/src/irc/outputfilter.cpp
@@ -1866,25 +1866,30 @@ namespace Konversation
// Only continue if there was no error
if(token.length())
{
- unsigned int modeCount = nickList.count();
- QString modes;
- modes.fill(mode, modeCount);
+ QString modeToken;
+ QString nickToken;
+
+ modeToken = QString(" ") + QChar(giveTake);

- token += QString(" ") + QChar(giveTake) + modes;
tmpToken = token;

- for(unsigned int index = 0; index < modeCount; index++)
+ for(int index = 0; index < nickList.count(); index++)
{
if(index != 0 && (index % 3) == 0)
{
+ token += modeToken + nickToken;
result.toServerList.append(token);
token = tmpToken;
+ nickToken = QString();
+ modeToken = QString(" ") + QChar(giveTake);
}
- token += ' ' + nickList[index];
+ nickToken += ' ' + nickList[index];
+ modeToken += mode;
}

- if(token != tmpToken)
+ if(!nickToken.isEmpty())
{
+ token += modeToken + nickToken;
result.toServerList.append(token);
}
}

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 218784] New: Server list dialog doesn't remember network order as established by DND

2009-12-15T03:04:16Z

https://bugs.kde.org/show_bug.cgi?id=218784

Summary: Server list dialog doesn't remember network order as
established by DND
Product: konversation
Version: Git
Platform: Unlisted Binaries
OS/Version: Linux
Status: NEW
Severity: normal
Priority: NOR
Component: general
AssignedTo: konversation-devel@...
ReportedBy: hein@...
CC: wordsizzle@...

Title says it all - drag reordering some networks, quitting Konvi and
restarting it doesn't recreate the order correctly.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 214258] Commands like /op and /deop cause an invalid MODE command to be send preceding a correct one

2009-12-15T02:57:50Z

https://bugs.kde.org/show_bug.cgi?id=214258

Eike Hein <hein@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |

--- Comment #2 from Eike Hein <hein kde org> 2009-12-15 11:57:49 ---
That got rid of the empty MODE, but there's this problem now:

/deop foo foo foo foo

leads to:

[11:54] << MODE #konvi-test2 -oooo foo foo foo
[11:55] << MODE #konvi-test2 -oooo foo

I.e. while it's correctly wrapping after three destinations, it has as many
mode chars as it has destinations on both lines, unnecessarily.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 214258] Commands like /op and /deop cause an invalid MODE command to be send preceding a correct one

2009-12-15T02:17:37Z

[Bug 218332] No way to output '%1' in autoreplace

2009-12-14T23:47:52Z

https://bugs.kde.org/show_bug.cgi?id=218332

Travis McHenry <wordsizzle@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED

--- Comment #1 from Travis McHenry <wordsizzle gmail com> 2009-12-15 08:47:50 ---
commit a54b8543fa24de3bf6fe6993724b588a9e48a1b4
Author: Travis McHenry <wordsizzle@...>
Date: Tue Dec 15 00:44:23 2009 -0700

Fix an autoreplace bug and enable escaping

Make it so we can do multiple replaces in a single line again by
not replacing the content of the 'global' replace variable
BUG:211632

Make it so we can support %# in replacements without it getting
lost in regex land by allowing escaping (with %%#).If you're so
inclined please review the big comment explaining why we can't
just not remove the leftover %# to make sure I'm not shooting hot
air.
BUG:218332

diff --git a/src/application.cpp b/src/application.cpp
index cf61af5..79c7730 100644
--- a/src/application.cpp
+++ b/src/application.cpp
@@ -1007,18 +1007,27 @@ QString Application::doAutoreplace(const QString&
text,bool output)
{
// remember captured patterns
QStringList captures = needleReg.capturedTexts();
+ QString replaceWith = replacement;

- // replace %0 - %9 in regex groups
+ replaceWith.replace("%%","%\x01"); // escape double %
+ // replace %0-9 in regex groups
for (int capture=0;capture<captures.count();capture++)
{
-
replacement.replace(QString("%%1").arg(capture),captures[capture]);
+ QString search = QString("%%1").arg(capture);
+ replaceWith.replace(search, captures[capture]);
}
- replacement.remove(QRegExp("%[0-9]"));
+ //Explanation why this is important so we don't
forget:
+ //If somebody has a regex that say has a replacement
of url.com/%1/%2 and the
+ //regex can either match one or two patterns, if the
2nd pattern match is left,
+ //the url is invalid (url.com/match/%2). This is
expected regex behavior I'd assume.
+ replaceWith.remove(QRegExp("%[0-9]"));
+
+ replaceWith.replace("%\x01","%"); // return escaped %
to normal
// allow for var expansion in autoreplace
- replacement =
Konversation::doVarExpansion(replacement);
+ replaceWith =
Konversation::doVarExpansion(replaceWith);
// replace input with replacement
- line.replace(index, captures[0].length(),
replacement);
- index += replacement.length();
+ line.replace(index, captures[0].length(),
replaceWith);
+ index += replaceWith.length();
}
} while (index >= 0 && index < (int)line.length());
}

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 211632] Autoreplace doesn't handle multiple replacements in the same line properly

2009-12-14T23:47:50Z

https://bugs.kde.org/show_bug.cgi?id=211632

Travis McHenry <wordsizzle@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED

--- Comment #1 from Travis McHenry <wordsizzle gmail com> 2009-12-15 08:47:50 ---
commit a54b8543fa24de3bf6fe6993724b588a9e48a1b4
Author: Travis McHenry <wordsizzle@...>
Date: Tue Dec 15 00:44:23 2009 -0700

Fix an autoreplace bug and enable escaping

Make it so we can do multiple replaces in a single line again by
not replacing the content of the 'global' replace variable
BUG:211632

Make it so we can support %# in replacements without it getting
lost in regex land by allowing escaping (with %%#).If you're so
inclined please review the big comment explaining why we can't
just not remove the leftover %# to make sure I'm not shooting hot
air.
BUG:218332

diff --git a/src/application.cpp b/src/application.cpp
index cf61af5..79c7730 100644
--- a/src/application.cpp
+++ b/src/application.cpp
@@ -1007,18 +1007,27 @@ QString Application::doAutoreplace(const QString&
text,bool output)
{
// remember captured patterns
QStringList captures = needleReg.capturedTexts();
+ QString replaceWith = replacement;

- // replace %0 - %9 in regex groups
+ replaceWith.replace("%%","%\x01"); // escape double %
+ // replace %0-9 in regex groups
for (int capture=0;capture<captures.count();capture++)
{
-
replacement.replace(QString("%%1").arg(capture),captures[capture]);
+ QString search = QString("%%1").arg(capture);
+ replaceWith.replace(search, captures[capture]);
}
- replacement.remove(QRegExp("%[0-9]"));
+ //Explanation why this is important so we don't
forget:
+ //If somebody has a regex that say has a replacement
of url.com/%1/%2 and the
+ //regex can either match one or two patterns, if the
2nd pattern match is left,
+ //the url is invalid (url.com/match/%2). This is
expected regex behavior I'd assume.
+ replaceWith.remove(QRegExp("%[0-9]"));
+
+ replaceWith.replace("%\x01","%"); // return escaped %
to normal
// allow for var expansion in autoreplace
- replacement =
Konversation::doVarExpansion(replacement);
+ replaceWith =
Konversation::doVarExpansion(replaceWith);
// replace input with replacement
- line.replace(index, captures[0].length(),
replacement);
- index += replacement.length();
+ line.replace(index, captures[0].length(),
replaceWith);
+ index += replaceWith.length();
}
} while (index >= 0 && index < (int)line.length());
}

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

Re: Review Request: port tray icon to knotificationitem

2009-12-13T00:00:56Z

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.kde.org/r/1965/#review3413
-----------------------------------------------------------

Ship it!

Merged via http://gitorious.org/konversation/konversation/merge_requests/3

- Eike

On 2009-10-31 00:24:12, xdarklight wrote:

>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviewboard.kde.org/r/1965/
> -----------------------------------------------------------
>
> (Updated 2009-10-31 00:24:12)
>
>
> Review request for konversation.
>
>
> Summary
> -------
>
> this ports the tray icon to knotificationitem
>
> if knotificationitem is not available (on build time) the old implementation (using KSystemTray) will automatically be used as fallback
> -> this means konversation will still compile on every system
>
> note: Sho and I had problems when applying the patch to our svn trees
> it seems that this was some bug in 'patch' (the application ;))
> make sure that after applying the patch the content of trayiconknotificationitem.cpp and trayiconksystemtray.cpp is not multiple times in them.
>
> all items from word's list are done - except #4 (which should be a seperate patch):
> http://pastebin.ca/1613175
>
>
> Diffs
> -----
>
> trunk/extragear/network/konversation/CMakeLists.txt 1042888
> trunk/extragear/network/konversation/cmake/modules/FindLibKNotificationItem-1.cmake PRE-CREATION
> trunk/extragear/network/konversation/config-konversation.h.cmake 1042888
> trunk/extragear/network/konversation/src/CMakeLists.txt 1042888
> trunk/extragear/network/konversation/src/mainwindow.cpp 1042888
> trunk/extragear/network/konversation/src/notificationhandler.cpp 1042888
> trunk/extragear/network/konversation/src/viewer/trayicon.h 1042888
> trunk/extragear/network/konversation/src/viewer/trayicon.cpp 1042888
> trunk/extragear/network/konversation/src/viewer/trayiconknotificationitem.cpp PRE-CREATION
> trunk/extragear/network/konversation/src/viewer/trayiconksystemtray.cpp PRE-CREATION
>
> Diff: http://reviewboard.kde.org/r/1965/diff
>
>
> Testing
> -------
>
> I've been using this patch for some days now ;)
>
>
> Thanks,
>
> xdarklight
>
>

_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

Re: Review Request: port tray icon to knotificationitem

2009-12-13T00:00:36Z

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.kde.org/r/1965/#review3412
-----------------------------------------------------------

Ship it!

Merged via http://gitorious.org/konversation/konversation/merge_requests/3

- Eike

On 2009-10-31 00:24:12, xdarklight wrote:

_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

Information on Gitorious setup

2009-12-11T14:48:14Z

Some notes on the way things are currently set up on
Gitorious:

* As you probably know, commit access to Konversation is
handled through the kde-developers group, which also
has ownership of the project. This keeps KDE's good old
everyone-can-commit-everywhere model intact. A downside
of this used to be that everyone in kde-developers got
merge request mail for every project owned by kde-deve-
lopers, which quickly got annoying. The current solu-
tion implemented for this (for both Amarok and us) is
as follows:

There's "konversation-reviewers" team on Gitorious now,
which as its members currently has all of the core Kon-
versation developers. Everyone in this team gets merge
request mail for the konversation repository, and can
also act on it, i.e. modify the status of merge re-
quests. If you want to be added to the team, you need
to ask one of its administrators. The team's adminis-
trators for now are psn and me, i.e. the official main-
tainers of Konversation.

kde-developers, otoh, is no longer tied into the merge
request rewiew process for the konversation repository.

* Merge requests can have multiple different states on
Gitorious. A state has a name and a color, and marks
the request as either open or closed. The preconfigu-
red default states are "Open" (open) and "Closed"
closed).

Amarok otoh went with this:
Open (open)
Closed (closed)
Verifying (open)
Merged (closed)
Rejected (closed)

That's better, but I went a bit beyond that. Our
merge request states as of now are:

Open (open)
Verifying (open)
Merging (closed)
Merged (closed)
Rejected (closed)
Deferred (closed)

* The various commit hooks (taking care of things like
feeding into CIA, commit mails, CCMAIL:, BUG:, etc.)
are currently hosted on Amarok's project server, which
updates a clone of our repository every three minutes.
If there's a problem and I'm not around to relay stuff,
try chatting up eean (Ian Monroe) or morice-net (Jean-
Nicolas Artaud) on IRC. Both are found in #kde-git.
eean administrates Amarok's server and the hook setup;
morice-net wrote some of the hook scripts.

--
Best regards,
Eike Hein
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 218332] New: No way to output '%1' in autoreplace

2009-12-11T13:49:12Z

https://bugs.kde.org/show_bug.cgi?id=218332

Summary: No way to output '%1' in autoreplace
Product: konversation
Version: Git
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: konversation-devel@...
ReportedBy: nicolas.alvarez@...

In a regex autoreplace, it's impossible to output a literal percent sign
followed by a number. If I have a regex "foo-(\S*)" and replacement "bar%23%1",
"foo-x" will output "bar3x", because the %2 is interpreted as a capturing
subpattern, even though the regex only has one subpattern.

The current code is:
// replace %0 - %9 in regex groups
for (int capture=0;capture<captures.count();capture++)
{
replacement.replace(QString("%%1").arg(capture),captures[capture]);
}
replacement.remove(QRegExp("%[0-9]"));

Removing the last line would allow the previous example to work. However, it
still doesn't solve the problem if I *do* have a second subpattern (or if I
want to output %1). What we really need is a way to escape the percent sign.

Instead of using replace(), I propose looping over the characters in the
string. Pseudocode:
foreach (char in string) {
if (char == %) {
look at the following character;
if (char == %) output += '%'; //this lets you escape a % by doubling it
if (char is digit) output += capture[digit];
else output += '%' + char;
} else {
output += char;
}
}
I may implement this myself later.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 218018] New: Fixed background image for the chat window

2009-12-09T10:01:57Z

https://bugs.kde.org/show_bug.cgi?id=218018

Summary: Fixed background image for the chat window
Product: konversation
Version: unspecified
Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
AssignedTo: konversation-devel@...
ReportedBy: pBakhuis@...

Version: (using KDE 4.3.4)
OS: Linux
Installed from: openSUSE RPMs

I don't know if this is intended or not, but the background image of the chat
window that can be set under
Settings > Configure Konversation > Interface > Chat window
scrolls along with the background. It would be nice to have this displayed
fixed in place with the text scrolling over it.
An additional checkbox with a 'fixed' option (off by default) would be nice.

I'm guessing this be archieved with Qts setStyleSheet method? The CSS syntax
and an example of what it does can be found on
[url=http://www.w3schools.com/Css/pr_background-attachment.asp]
w3schools[/url].

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217889] Konversation spamming personal information by default without user consent

2009-12-08T15:12:50Z

https://bugs.kde.org/show_bug.cgi?id=217889

--- Comment #4 from Pascal Bakhuis <pBakhuis Gmail com> 2009-12-09 00:12:46 ---
"and by far the majority of IRC clients
I'm aware of, i.e. it's the established convention - fills in this field with
your system user name by default, which I take to be "Pascal"."
By default yes - without having pointed out this to me beforehand, no.
I consider this to be a rather important difference.
Konversation is the first application that displayed such behavior that I have
used so far, now I can't say I've vast experience with irc clients as
Konversation is most likely only my fourth - but personally I find this
unacceptable for any aplication.
(I wouldn't want my mail client automatically creating a signature based on my
system information without informing me of it either)

Due to the time and wanting to turn in for the night I didn't double check the
information and somehow come to the invalid conclusion that it was displayed
when leaving the channel. So that bit can be ignored.
All I'm asking for is to display the identity window upon running Konversation
for the first time.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217889] Konversation spamming personal information by default without user consent

2009-12-08T14:52:55Z

https://bugs.kde.org/show_bug.cgi?id=217889

--- Comment #3 from Eike Hein <hein kde org> 2009-12-08 23:52:53 ---
Ok, here's how this works: When you leave an IRC channel (by closing the
channel tab, or the connection, or quit the program - which closes the
connection), the IRC *server* will send a message to other clients attending
that channel, informing them that you have left. The raw format of this
message, as sent by the server to the other's clients under the hood, contains
the hostmask of the client that left:

http://en.wikipedia.org/wiki/Hostmask

... and many clients will include this hostmask in the formatted version of the
message they show to the user.

As you can read on the page linked above, part of an IRC hostmask is the
"ident":

http://en.wikipedia.org/wiki/Ident

Specifically, about IRC:

http://en.wikipedia.org/wiki/Ident#Uses

As explained there, unless you have an actual ident daemon running, the IRC
server will fall back to a value provided by the IRC client.

This corresponds to the "Ident" field on the "Advanced" tab of Konversation's
Identity settings dialog. Konversation - and by far the majority of IRC clients
I'm aware of, i.e. it's the established convention - fills in this field with
your system user name by default, which I take to be "Pascal".

So in fact, the particular "dumping of information as I leave channels" you're
concerned about actually has nothing to do with the system account Full Name
field.

That said, the "Real name" field in the Identity settings is automatically
filled in with the contents of the system account Full Name field, which is
available to other IRC users via the "whois" command.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217889] Konversation spamming personal information by default without user consent

2009-12-08T14:30:23Z

https://bugs.kde.org/show_bug.cgi?id=217889

--- Comment #2 from Pascal Bakhuis <pBakhuis Gmail com> 2009-12-08 23:30:16 ---
Thank you for the elaborate response,

I was informed the full text (slightly garbled)
~Pascal@... * Pascal Bakhuis was available to the
person who pointed this out to me, so looking back it's not the quit message
but non the less the information was available to them.
(was far passed midnight when I created the ticket - so it's a miracle the rest
made sense)

"I think an argument can be made here that if you don't want applications to
make use of real name information you provided the system with, you shouldn't
have entered it."
I don't mind my office suite knowing my name so that Insert field > Author
works.
I do mind when I join some random chat room filled with people I know nothing
about suddenly having access to my name. It's behavior I haven't seen in any
other Internet related program do without displaying some form of dialog first.
This really should be on a per application base rather than assuming that if
the information is provided in one place it can be used in another without
consent.

"2) Being truthful about one's real name is part of established IRC etiquette
(similar to, say, Usenet) -- some networks even have a "network operators may
kill clients using obvious real name forgeries at will" policy."
As a webdeveloper myself I can also inform you that it's considered proper
etiquette for websites to handle userdata with great care and to avoid making
this available to the public, and if it is make that very clear. (Well that's
50% etiquette and 50% avoid getting sued)

"- Getting error dialogs early on certainly makes the first-run experience a
lot
less friendly."
I wasn't asking for an error dialog but an information dialog or some form that
at least informs you the system information has been used. - Popping up the
default "identities" window with the fields already filled in allowing
customization is reasonable?
It's a one time - one click, doesn't seem too much of an inconvenience
considering the privacy benefit.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217889] Konversation spamming personal information by default without user consent

2009-12-08T09:29:25Z

https://bugs.kde.org/show_bug.cgi?id=217889

Eike Hein <hein@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |hein@...

--- Comment #1 from Eike Hein <hein kde org> 2009-12-08 18:29:23 ---
The real name as retrieved from the user's system account settings is not
"dumped into channels when you leave it" -- if that's what happened, then you
probably set that up yourself somehow (if it's a bug, it's not a known one, and
something like that would quickly become apparent in KDE's IRC channels).

That said, the real name is retrieved and written to the Default Identity on
first startup, and when an IRC connection using that identity is attempted, the
name is submitted to the IRC server and can subsequently be read by others
using the "whois" command.

There is a set of assumptions and motivations behind that behavior:
1) System accounts have a Full Name data field precisely to avoid the user
having to re-enter that information redundantly in applications.
2) Being truthful about one's real name is part of established IRC etiquette
(similar to, say, Usenet) -- some networks even have a "network operators may
kill clients using obvious real name forgeries at will" policy.

I think an argument can be made here that if you don't want applications to
make use of real name information you provided the system with, you shouldn't
have entered it.

That said, here's an idea: As submitting a real name to the IRC server is
required by the protocol, we already show error dialogs when attempting to
create a connection with an incomplete identity (e.g. because the system
account had no Full Name set we could retrieve on first startup) or when trying
to save an incomplete identity in the Identity Settings dialog. These dialogs
could try to offer filling in the missing field from the system account. Then
we could leave the real name field empty by default, and give the user this
easy way to opt into retrieving the name from the system account and avoiding
the typing. The Identity Settings dialog itself could also have a button next
to the field for the same purpose.

Complications:
- Getting error dialogs early on certainly makes the first-run experience a lot
less friendly.
- It makes the "incomplete identity" error dialog system a lot more complex. An
identity may be missing multiple required fields, and currently this is handled
with a single dialog showing a list of the fields that need to be edited.
That's at odds with the dialog having a button to automatically fill in the
real name - it doesn't solve the whole problem, so it'd need to loop back to
another dialog with one less complaint in the list. A solution with multiple
dialogs is equally ugly. Not to mention it should check first whether the
system account has a Full Name set to begin with. The alternative is just going
with a button next to the field in the Identity Settings dialog, shown
depending on whether the system account has a Full Name set or not. But that
might be too hard to discover (assuming it's an icon button with a tooltip for
space reasons).

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217889] New: Konversation spamming personal information by default without user consent

2009-12-08T08:54:23Z

https://bugs.kde.org/show_bug.cgi?id=217889

Summary: Konversation spamming personal information by default
without user consent
Product: konversation
Version: unspecified
Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
AssignedTo: konversation-devel@...
ReportedBy: pBakhuis@...

Version: (using KDE 4.3.4)
OS: Linux
Installed from: openSUSE RPMs

Konversation by default is so 'polite' to to read out the system information
for your username. But it does not inform you of this I for one greatly value
my online privacy and can't say I'm very pleased with the way this works.

ALWAYS when accessing a users data and doing anything with it over a network
the user should be informed of this and be able to prevent this.

There should either be a dialog when it's started for the first time informing
you of exactly your default 'identity' settings are and that his info is dumped
into channel when you leave it... or should it fill in some random bogus
information.

Also, it would be nice to have identities available under config as that's
where I looked for such information before connecting to any server, luckily I
was informed by another person in the channel that I was spamming my name
around so it happened only in a single channel.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217592] mouse cursor disappear when moved to topic, user list or channel tabs in conversation

2009-12-06T06:43:50Z

https://bugs.kde.org/show_bug.cgi?id=217592

--- Comment #3 from Eike Hein <hein kde org> 2009-12-06 15:43:49 ---
Notably it doesn't happen consistently, just intermittently. Started with
4.6rc1 :-(.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217592] mouse cursor disappear when moved to topic, user list or channel tabs in conversation

2009-12-06T06:32:13Z

https://bugs.kde.org/show_bug.cgi?id=217592

--- Comment #2 from Myriam Schweingruber <myriam kde org> 2009-12-06 15:32:12 ---
Can't reproduce it with KDE 4.3.4 and Konversation from SVN

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217592] mouse cursor disappear when moved to topic, user list or channel tabs in conversation

2009-12-06T06:23:48Z

https://bugs.kde.org/show_bug.cgi?id=217592

Eike Hein <hein@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |hein@...
Resolution| |UPSTREAM

--- Comment #1 from Eike Hein <hein kde org> 2009-12-06 15:23:47 ---
It's a Qt 4.6 bug (one of many - the buggiest Qt I remember in years and
years).

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217592] New: mouse cursor disappear when moved to topic, user list or channel tabs in conversation

2009-12-06T06:15:22Z

https://bugs.kde.org/show_bug.cgi?id=217592

Summary: mouse cursor disappear when moved to topic, user list
or channel tabs in conversation
Product: konversation
Version: 1.2.1
Platform: Compiled Sources
OS/Version: unspecified
Status: NEW
Severity: normal
Priority: NOR
Component: general
AssignedTo: konversation-devel@...
ReportedBy: ruchir.brahmbhatt@...

Version: 1.2.1 (using Devel)
Installed from: Compiled sources

Qt: 4.6.0
KDE: 4.3.80 (KDE 4.3.80 (KDE 4.4 Beta1)) "release 9"
Konversation: 1.2.1

When I move mouse over channel topic, user list or channel tabs, mouse cursor
disappears.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 189043] konversation hangs with 100% cpu usage while pasting particular text

2009-12-06T05:44:09Z

https://bugs.kde.org/show_bug.cgi?id=189043

Ruchir Brahmbhatt <ruchir.brahmbhatt@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED

--- Comment #2 from Ruchir Brahmbhatt <ruchir brahmbhatt ecosmob com> 2009-12-06 14:44:07 ---
Appears to be gone in 1.2.1(kde 4.3.80)

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 217233] New: Crash on startup, hitting assert

2009-12-03T09:00:34Z

https://bugs.kde.org/show_bug.cgi?id=217233

Summary: Crash on startup, hitting assert
Product: konversation
Version: SVN
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: konversation-devel@...
ReportedBy: kretschmann@...

When starting up Konversation (SVN trunk build from Dec 1 2009), it crashed by
hitting a Q_ASSERT. Please see below for a backtrace.

Note: I am using a BNC for one network, and also one other network directly,
without BNC. The crash might be related to this setup (not sure).

Thanks :)

Backtrace:

Application: Konversation (konversation), signal: Aborted
The current source language is "auto; currently c".
[Current thread is 1 (Thread 0x7fce9729a750 (LWP 2671))]

Thread 2 (Thread 0x7fce84812910 (LWP 2672)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1 0x00007fce934844fb in QWaitConditionPrivate::wait (this=<value optimized
out>, mutex=0x21a6fa8, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:87
#2 QWaitCondition::wait (this=<value optimized out>, mutex=0x21a6fa8,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3 0x00007fce94a9f78c in QHostInfoAgent::run (this=0x21a6f90) at
kernel/qhostinfo.cpp:260
#4 0x00007fce93483445 in QThreadPrivate::start (arg=0x21a6f90) at
thread/qthread_unix.cpp:188
#5 0x00007fce90838a04 in start_thread (arg=<value optimized out>) at
pthread_create.c:300
#6 0x00007fce91e367bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fce9729a750 (LWP 2671)):
[KCrash Handler]
#5 0x00007fce91d8a4b5 in *__GI_raise (sig=<value optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6 0x00007fce91d8df50 in *__GI_abort () at abort.c:92
#7 0x00007fce9347b864 in qt_message_output (msgType=QtFatalMsg, buf=<value
optimized out>) at global/qglobal.cpp:2042
#8 0x00007fce9347b9b6 in qFatal (msg=<value optimized out>) at
global/qglobal.cpp:2241
#9 0x00000000004adda3 in NickInfo::setNickname (this=0x3454e40,
newNickname=...) at /home/mark/kde/src/konversation/src/irc/nickinfo.cpp:145
#10 0x00000000004691f5 in Server::addNickToJoinedChannelsList (this=0x209e2a0,
channelName=..., nickname=...) at
/home/mark/kde/src/konversation/src/irc/server.cpp:2558
#11 0x000000000048fe25 in Channel::processPendingNicks (this=0x2b52a60) at
/home/mark/kde/src/konversation/src/irc/channel.cpp:2756
#12 0x0000000000491e53 in Channel::qt_metacall (this=0x2b52a60,
_c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffab7fa5f0) at
/home/mark/kde/build/konversation/src/channel.moc:167
#13 0x00007fce9357eddc in QMetaObject::activate (sender=0x2bc5fb0,
from_signal_index=<value optimized out>, to_signal_index=<value optimized out>,
argv=0xffffffffffffffff) at kernel/qobject.cpp:3113
#14 0x00007fce93578d83 in QObject::event (this=0x2bc5fb0, e=0xa6f) at
kernel/qobject.cpp:1075
#15 0x00007fce92a11efc in QApplicationPrivate::notify_helper (this=0x1bfe690,
receiver=0x2bc5fb0, e=0x7fffab7fabf0) at kernel/qapplication.cpp:4056
#16 0x00007fce92a191ce in QApplication::notify (this=0x7fffab7faf20,
receiver=0x2bc5fb0, e=0x7fffab7fabf0) at kernel/qapplication.cpp:4021
#17 0x00007fce943d9e56 in KApplication::notify (this=0x7fffab7faf20,
receiver=0x2bc5fb0, event=0x7fffab7fabf0) at
../../kdeui/kernel/kapplication.cpp:302
#18 0x00007fce93569c2c in QCoreApplication::notifyInternal
(this=0x7fffab7faf20, receiver=0x2bc5fb0, event=0x7fffab7fabf0) at
kernel/qcoreapplication.cpp:610
#19 0x00007fce93594862 in QCoreApplication::sendEvent (this=0x1c00ae0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 QTimerInfoList::activateTimers (this=0x1c00ae0) at
kernel/qeventdispatcher_unix.cpp:572
#21 0x00007fce9359225d in timerSourceDispatch (source=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:165
#22 0x00007fce8f0eebbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x00007fce8f0f2588 in ?? () from /lib/libglib-2.0.so.0
#24 0x00007fce8f0f26b0 in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#25 0x00007fce935921a6 in QEventDispatcherGlib::processEvents (this=0x1bc5cb0,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#26 0x00007fce92aa64be in QGuiEventDispatcherGlib::processEvents (this=0xa6f,
flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#27 0x00007fce93568532 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#28 0x00007fce93568904 in QEventLoop::exec (this=0x7fffab7fae90, flags=) at
kernel/qeventloop.cpp:201
#29 0x00007fce9356aab9 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#30 0x000000000042bfed in main (argc=1, argv=0x7fffab7fbc48) at
/home/mark/kde/src/konversation/src/main.cpp:101
The current source language is "auto; currently asm".
The current source language is "auto; currently c".

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 215256] Konversations use 100% cpu doing nothing special.

2009-11-30T14:01:32Z

https://bugs.kde.org/show_bug.cgi?id=215256

--- Comment #8 from Eike Hein <hein kde org> 2009-11-30 23:01:30 ---
Note from TZander on the callgrind dump:

[22:58] <TZander> Sho_: looking at the valgrind; the scrollbars might be
toggled on/off all the time.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 215256] Konversations use 100% cpu doing nothing special.

2009-11-27T00:21:29Z

https://bugs.kde.org/show_bug.cgi?id=215256

--- Comment #7 from Martin Gräßlin <ubuntu martin-graesslin com> 2009-11-27 09:21:28 ---
As I am the one who had success with subpixel hinting - here are my settings:

[] Exclude range
[x] Use sub-pixel rendering: RGB
Hinting style: Medium

Before it was on System default and I have no idea what exactly it was. The
system became useable again when i deselected the exclude range. So in fact I
fixed it by enabling sub pixel hinting and not by disabling

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 215256] Konversations use 100% cpu doing nothing special.

2009-11-26T15:43:19Z

https://bugs.kde.org/show_bug.cgi?id=215256

--- Comment #6 from Eike Hein <hein kde org> 2009-11-27 00:43:18 ---
It appears that temporary work arounds for this problem can include swithing to
a monospace font (two successful reports), fiddling with the font size and
disabling subpixel hinting (one successful report).

I've filed this issue upstream with Nokia:
http://bugreports.qt.nokia.com/browse/QTBUG-6281

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 215256] Konversations use 100% cpu doing nothing special.

2009-11-26T09:49:06Z

https://bugs.kde.org/show_bug.cgi?id=215256

Martin Gräßlin <ubuntu@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |ubuntu@...

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 215256] Konversations use 100% cpu doing nothing special.

2009-11-26T09:39:34Z

https://bugs.kde.org/show_bug.cgi?id=215256

--- Comment #5 from Eike Hein <hein kde org> 2009-11-26 18:39:32 ---
Created an attachment (id=38613)
--> (http://bugs.kde.org/attachment.cgi?id=38613)
Backtrace of 100% CPU usage problem.

A new backtrace by mgraesslin of kwin fame.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 215256] Konversations use 100% cpu doing nothing special.

2009-11-24T22:52:17Z

https://bugs.kde.org/show_bug.cgi?id=215256

Eike Hein <hein@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |alinm.elena@...

--- Comment #4 from Eike Hein <hein kde org> 2009-11-25 07:52:14 ---
*** Bug 216016 has been marked as a duplicate of this bug. ***

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 216016] konversation high cpu usage

2009-11-24T22:52:16Z

https://bugs.kde.org/show_bug.cgi?id=216016

Eike Hein <hein@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |hein@...
Resolution| |DUPLICATE

--- Comment #1 from Eike Hein <hein kde org> 2009-11-25 07:52:14 ---

*** This bug has been marked as a duplicate of bug 215256 ***

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 216016] New: konversation high cpu usage

2009-11-24T14:05:18Z

https://bugs.kde.org/show_bug.cgi?id=216016

Summary: konversation high cpu usage
Product: konversation
Version: 1.2.1
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: konversation-devel@...
ReportedBy: alinm.elena@...

Version: 1.2.1 (using 4.3.75 (KDE 4.3.75 (KDE 4.4 >= 20091113))
"release 8", KDE:KDE4:UNSTABLE:Desktop / openSUSE_11.2)
Compiler: gcc
OS: Linux (x86_64) release 2.6.31.5-0.1-desktop

konversation usage high cpu.

I did a ltrace on the process and found this going on forever

<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf7cac0, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0x88fa40, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa552e0, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa53750, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf7cac0, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0x88fa40, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa552e0, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa53750, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf7cac0, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0x88fa40, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa552e0, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa53750, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf7cac0, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0x88fa40, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa552e0, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa53750, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf7cac0, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0x88fa40, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa552e0, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa53750, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf7cac0, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0x88fa40, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa552e0, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa53750, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf7cac0, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0x88fa40, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa552e0, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa53750, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf7cac0, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0x88fa40, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa552e0, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xa53750, 8, 0,
0x7f8db6a97cb8, 0Error: call nesting too deep!
<unfinished ...>
<... _ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE resumed> ) = 112
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf964c0, 8, 0,
0x7f8db6a97cb8, 0 <unfinished ...>
_ZNK7QWidget6metricEN12QPaintDevice17PaintDeviceMetricE(0xf88060, 8, 5,
0x7f8db6a97cb8, 0Error: call nesting too deep!

Alin

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 198404] notifications don't expire, have to be dismissed manually

2009-11-23T23:44:22Z

https://bugs.kde.org/show_bug.cgi?id=198404

Bengt Gördén <bengan@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |bengan@...

--- Comment #4 from Bengt Gördén <bengan kthnoc net> 2009-11-24 08:44:20 ---
I also have the same problem. But it seems to be a problem only when there is
lots of notifications. Typical seems to be when I have more than ruffly 100.

konversation 1.2.0
kde 4.3.1
opensuse 11.2

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel

[Bug 215403] Crash on Identity Window

2009-11-21T02:06:22Z

https://bugs.kde.org/show_bug.cgi?id=215403

Eren <eren@...> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID

--- Comment #2 from Eren <eren pardus org tr> 2009-11-21 11:06:20 ---
Hmm, you're right. I re-compiled konvi with 4.2 and it works without problems.
I think there is something in our repositories. I'll check it.

I'm closing this bug as invalid. Thank you for your interest :)

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konversation-devel mailing list
Konversation-devel@...
https://mail.kde.org/mailman/listinfo/konversation-devel