Mailing List Archive

kooky kde behaviour
it would seem that from time to time, dns just stops working in all of my kde
apps. for example, in order to send this email, i'm going to have to restart
kde since kmail won't be able to locate my mailserver.

konqueror's the same way too, even though mozilla can locate hosts just fine,
so can lynx, ping, wget etc. etc. the only kde app exception seems to be kate
and it's use of fish to connect to another box.

it was working this morning and i haven't changed any configuration
options... is there a kde daemon that handles this sort of thing that i can
just kill/reset without having to restart kde completely? if this is indeed
a bug, what is it a bug IN?


--
If wishes were horses, we'd all be eatin' steak.
- Jayne, Firefly, "Objects in Space"

--
gentoo-user@gentoo.org mailing list
Re: kooky kde behaviour [ In reply to ]
On Tue, 12 Oct 2004 19:44:43 -0400, daniel wrote:

> it would seem that from time to time, dns just stops working in all of
> my kde apps.

I get the same thing occasionally, it happened yesterday. Suddenly no
KDE apps can resolve addresses, yet other apps work fine.

I haven't got a clue what causes it, but I can confirm you aren't alone.


--
Neil Bothwick

SUBLIMINALsendmoneyTAGLINE
Re: kooky kde behaviour [ In reply to ]
On Wednesday 13 October 2004 00:44, daniel wrote:
> it would seem that from time to time, dns just stops working in all of my
> kde apps. for example, in order to send this email, i'm going to have to
> restart kde since kmail won't be able to locate my mailserver.
>
> konqueror's the same way too, even though mozilla can locate hosts just
> fine, so can lynx, ping, wget etc. etc. the only kde app exception seems
> to be kate and it's use of fish to connect to another box.
>
> it was working this morning and i haven't changed any configuration
> options... is there a kde daemon that handles this sort of thing that i
> can just kill/reset without having to restart kde completely? if this is
> indeed a bug, what is it a bug IN?

http://bugs.kde.org/show_bug.cgi?id=91239

--
Mike Williams
Re: kooky kde behaviour [ In reply to ]
daniel wrote:
> it would seem that from time to time, dns just stops working in all of my
> kde apps. for example, in order to send this email, i'm going to have to
> restart kde since kmail won't be able to locate my mailserver.

It happend to me a couple of times after glibc upgrade (inside a KDE session)

Regards,
Norberto

--
gentoo-user@gentoo.org mailing list
Re: kooky kde behaviour [ In reply to ]
On Wednesday 13 October 2004 01:44, daniel wrote:
> it would seem that from time to time, dns just stops working in all of my
> kde apps. for example, in order to send this email, i'm going to have to
> restart kde since kmail won't be able to locate my mailserver.
>
> konqueror's the same way too, even though mozilla can locate hosts just
> fine, so can lynx, ping, wget etc. etc. the only kde app exception seems
> to be kate and it's use of fish to connect to another box.
>
> it was working this morning and i haven't changed any configuration
> options... is there a kde daemon that handles this sort of thing that i
> can just kill/reset without having to restart kde completely? if this is
> indeed a bug, what is it a bug IN?

I only had this once, two days ago, when I upgraded glibc. After restarting
kde everything was fine. Like always.

Glück Auf
Volker

--
gentoo-user@gentoo.org mailing list
Re: kooky kde behaviour [ In reply to ]
Thus spake Volker Armin Hemmann:

>On Wednesday 13 October 2004 01:44, daniel wrote:
>> it would seem that from time to time, dns just stops working in all of my
>> kde apps. for example, in order to send this email, i'm going to have to
>> restart kde since kmail won't be able to locate my mailserver.
>>
>> konqueror's the same way too, even though mozilla can locate hosts just
>> fine, so can lynx, ping, wget etc. etc. the only kde app exception seems
>> to be kate and it's use of fish to connect to another box.
>>
>> it was working this morning and i haven't changed any configuration
>> options... is there a kde daemon that handles this sort of thing that i
>> can just kill/reset without having to restart kde completely? if this is
>> indeed a bug, what is it a bug IN?
>
>I only had this once, two days ago, when I upgraded glibc. After restarting
>kde everything was fine. Like always.

This too happened to me two days ago when I upgraded glibc, exactly as
described. Does anyone know why upgrading glibc would cause this to happen?
Is this normal behaviour?

Cheers,
Ed

>Glück Auf
>Volker
>
>--
>gentoo-user@gentoo.org mailing list

--

"It has been said that man is a rational animal. All my life I have
been searching for evidence which could support this."
--Bertrand Russell.

"The American empire is ideological, not territorial. We are the most
ideological people in the world, and we are so united in our view that we
don't understand there can be other views."
--Lt. Gen. William Odom, ret. (Former Director of NSA).

"When I was in school, I cheated on my metaphysics exam: I looked into the
soul of the boy sitting next to me.
--Woody Allen

"Nothing takes the taste out of peanut butter quite like unrequited love."
--Charlie Brown

--
gentoo-user@gentoo.org mailing list
Re: kooky kde behaviour [ In reply to ]
On October 13, 2004 04:04 pm, Edward Epstein wrote:
> Thus spake Volker Armin Hemmann:
> >On Wednesday 13 October 2004 01:44, daniel wrote:
> >> it would seem that from time to time, dns just stops working in all of
> >> my kde apps. for example, in order to send this email, i'm going to
> >> have to restart kde since kmail won't be able to locate my mailserver.
> >>
> >> konqueror's the same way too, even though mozilla can locate hosts just
> >> fine, so can lynx, ping, wget etc. etc. the only kde app exception
> >> seems to be kate and it's use of fish to connect to another box.
> >>
> >> it was working this morning and i haven't changed any configuration
> >> options... is there a kde daemon that handles this sort of thing that i
> >> can just kill/reset without having to restart kde completely? if this
> >> is indeed a bug, what is it a bug IN?
> >
> >I only had this once, two days ago, when I upgraded glibc. After
> > restarting kde everything was fine. Like always.
>
> This too happened to me two days ago when I upgraded glibc, exactly as
> described. Does anyone know why upgrading glibc would cause this to happen?
> Is this normal behaviour?

is instability a natural outcome of upgrading glibc? if this is the case, is
a reboot needed to get back that stability? i only ask because some other
things appeared flakey the other day (ssh logins w/ keys were failing etc.)
on my webserver just after upgrading glibc. do i have to reboot the box now?

--
Jubel Early: Where'd (River) go?
Simon: I can't keep track of her when she's not incorporeally possessing
a spaceship - don't look at me.
- Jubel Early and Simon, Firefly, "Objects in Space"

--
gentoo-user@gentoo.org mailing list
Re: kooky kde behaviour [ In reply to ]
On Friday 15 October 2004 01:18, daniel wrote:

> is instability a natural outcome of upgrading glibc? if this is the case,
> is a reboot needed to get back that stability? i only ask because some
> other things appeared flakey the other day (ssh logins w/ keys were failing
> etc.) on my webserver just after upgrading glibc. do i have to reboot the
> box now?

you do not have to, but it is the easiest way.

--
gentoo-user@gentoo.org mailing list
Re: kooky kde behaviour [ In reply to ]
On Wed, 13 Oct 2004 13:04:03 -0700, Edward Epstein wrote:

> This too happened to me two days ago when I upgraded glibc, exactly as
> described. Does anyone know why upgrading glibc would cause this to
> happen? Is this normal behaviour?

No, but I can confirm that upgrading (or downgrading) glibc causes it.


--
Neil Bothwick

We are upping our standards - so up yours.
Re: kooky kde behaviour [ In reply to ]
Thus spake Neil Bothwick:

>On Wed, 13 Oct 2004 13:04:03 -0700, Edward Epstein wrote:
>> This too happened to me two days ago when I upgraded glibc, exactly as
>> described. Does anyone know why upgrading glibc would cause this to
>> happen? Is this normal behaviour?
>
>No, but I can confirm that upgrading (or downgrading) glibc causes it.

So I don't know much about how all this stuff works but am I to assume that
the cause of this is that, for example, things that might be compiled against
glibc (such as the library which handles DNS queries for for KDE) would
expect data structures in the library to have changed, but, when the file on
disk is changed and a new call (after a certain period of inactivity, say for
the disk cache to flush itself so the library's oringial file handle is
closed) from the resolver results in a slightly different structure to be
loaded? Does this sound somewhat like what is going on? I'm notquite sure how
all of this library linking stuff works but I have been meaning to learn a
bit more about it.

Thanks for your response,
Ed

--

"It has been said that man is a rational animal. All my life I have
been searching for evidence which could support this."
--Bertrand Russell.

"The American empire is ideological, not territorial. We are the most
ideological people in the world, and we are so united in our view that we
don't understand there can be other views."
--Lt. Gen. William Odom, ret. (Former Director of NSA).

"When I was in school, I cheated on my metaphysics exam: I looked into the
soul of the boy sitting next to me.
--Woody Allen

"Nothing takes the taste out of peanut butter quite like unrequited love."
--Charlie Brown

--
gentoo-user@gentoo.org mailing list
Re: kooky kde behaviour [ In reply to ]
Thus spake Edward Epstein:

>Thus spake Neil Bothwick:
>>On Wed, 13 Oct 2004 13:04:03 -0700, Edward Epstein wrote:
>>> This too happened to me two days ago when I upgraded glibc, exactly as
>>> described. Does anyone know why upgrading glibc would cause this to
>>> happen? Is this normal behaviour?
>>
>>No, but I can confirm that upgrading (or downgrading) glibc causes it.
>
>So I don't know much about how all this stuff works but am I to assume that
>the cause of this is that, for example, things that might be compiled
> against glibc (such as the library which handles DNS queries for for KDE)
> would expect data structures in the library to have changed, but, when the
> file on disk is changed and a new call (after a certain period of
> inactivity, say for the disk cache to flush itself so the library's
> oringial file handle is closed) from the resolver results in a slightly
> different structure to be loaded? Does this sound somewhat like what is
> going on? I'm notquite sure how all of this library linking stuff works but
> I have been meaning to learn a bit more about it.

Sorry, I meant "things that might be compiled against glibc would expect data
structures in the library to not have changed, ie stayed the same".

I didn't get much sleep last night.

Thanks,
Ed


>Thanks for your response,
>Ed

--

"It has been said that man is a rational animal. All my life I have
been searching for evidence which could support this."
--Bertrand Russell.

"The American empire is ideological, not territorial. We are the most
ideological people in the world, and we are so united in our view that we
don't understand there can be other views."
--Lt. Gen. William Odom, ret. (Former Director of NSA).

"When I was in school, I cheated on my metaphysics exam: I looked into the
soul of the boy sitting next to me.
--Woody Allen

"Nothing takes the taste out of peanut butter quite like unrequited love."
--Charlie Brown

--
gentoo-user@gentoo.org mailing list
Re: kooky kde behaviour [ In reply to ]
Thus spake Edward Epstein:

>Thus spake Edward Epstein:
>>Thus spake Neil Bothwick:
>>>On Wed, 13 Oct 2004 13:04:03 -0700, Edward Epstein wrote:
>>>> This too happened to me two days ago when I upgraded glibc, exactly as
>>>> described. Does anyone know why upgrading glibc would cause this to
>>>> happen? Is this normal behaviour?
>>>
>>>No, but I can confirm that upgrading (or downgrading) glibc causes it.
>>
>>So I don't know much about how all this stuff works but am I to assume that
>>the cause of this is that, for example, things that might be compiled
>> against glibc (such as the library which handles DNS queries for for KDE)
>> would expect data structures in the library to have changed, but, when the
>> file on disk is changed and a new call (after a certain period of
>> inactivity, say for the disk cache to flush itself so the library's

It occurs to me that the cache would flush itself when it has writes to commit
to the disk, which wouldn't be what is going on this case, would it? I'd
really like to know the technical explanation for what causes such behaviour
from KDE.

Thanks,
Ed


>> oringial file handle is closed) from the resolver results in a slightly
>> different structure to be loaded? Does this sound somewhat like what is
>> going on? I'm notquite sure how all of this library linking stuff works
>> but I have been meaning to learn a bit more about it.
>
>Sorry, I meant "things that might be compiled against glibc would expect
> data structures in the library to not have changed, ie stayed the same".
>
>I didn't get much sleep last night.
>
>Thanks,
>Ed
>
>>Thanks for your response,
>>Ed

--

"It has been said that man is a rational animal. All my life I have
been searching for evidence which could support this."
--Bertrand Russell.

"The American empire is ideological, not territorial. We are the most
ideological people in the world, and we are so united in our view that we
don't understand there can be other views."
--Lt. Gen. William Odom, ret. (Former Director of NSA).

"When I was in school, I cheated on my metaphysics exam: I looked into the
soul of the boy sitting next to me.
--Woody Allen

"Nothing takes the taste out of peanut butter quite like unrequited love."
--Charlie Brown

--
gentoo-user@gentoo.org mailing list