[kde-linux] Re: Kpatience not closing correctly when logging out.

Dale rdalek1967 at gmail.com
Mon Apr 25 06:56:35 UTC 2011


Duncan wrote:
> Dale posted on Sun, 24 Apr 2011 18:11:20 -0500 as excerpted:
>
>    
>> Duncan wrote:
>>      
>>>
>>> Yes, an open kpat at kde shutdown results in a segfault here, as well.
>>> =:^(
>>>
>>> That's a definite bug as it should handle X shutdown gracefully.  I'd
>>> suggest filing it as such, with kde.
>>>        
>    
>> https://bugs.kde.org/show_bug.cgi?id=271655
>>
>> Let me know if I need to change something or need to add more info.  I'm
>> not a bug filing guru.  I sort of hate filing them really.  :/
>>      
> Yeah, I think most people, expecially those that file bugs, have a bit of
> a love/hate thing going on with bug-trackers.  While I sort of enjoy the
> process of tracking down a bug and in theory, reporting it, the actual
> reporting is a chore I'd love to be able to avoid, were it possible.
> Definitely one of the hates is searching for dups, as it always seems
> either way too many or no results are returned, with the result being that
> one often has little idea if this is the 100th time the bug has been filed
> or the first.
>
> Another hate is knowing exactly what info to include.  There, I believe I
> tend to error on the side of too much, most of the time, my thinking being
> that it's easy to ignore info of little or no value, but much more costly
> to repeatedly round-trip for info that could have been included as
> reasonably related, but wasn't, forcing an ask/reply round trip to get the
> info.  But of course my writing seems to be at a near permanent -vvv(vv)
> verbosity level anyway, and I know that.  One dev remarked at all the
> "dancing mongooses" I tend to include.  What could I respond with but
> something to the effect of, "Oh, about the mongooses, they're yellow with
> purple polka-dots!"
>
> Meanwhile, looks good to me, save that I'd have probably linked to this
> thread for context, should anyone be interested.  With bugs resulting from
> list discussions, I always like to have a link both ways, from the bug to
> the discussion, and from the discussion to the bug.  It's a lot easier
> than trying to repost interesting user reaction to the bug, and google
> indexes lists but not bug reports, so that way, anyone searching either
> the bug database or google later, will hopefully get the benefit of both,
> including any temporary workaround that might be useful, found on the list
> thread.
>
> Of course that's reasonably easy for me to do since I follow the list on
> gmane's list2news resource anyway, and gmane includes in the news article
> a link to one of its http versions of the same.  So all I have to do is
> look at the headers for the thread starter to find a gmane web link to
> post to the bug.  So I'll do just that, as a comment, and CC myself at the
> same time. =:^)
>
> ... Done. =:^)
>
>    

Thanks for posting on the bug that it is not just me.  I mentioned it 
but having it posted there by someone else should let them know it is 
not a figment of my imagination.  lol

My first bug was filed on b.g.o.  It wasn't a good experience.  I can't 
recall the details but that was back when the dev mailing list was like 
dodging knives.  If you wasn't a dev, you got scolded a bit.  Anyway, I 
just haven't been much into it since.

Funny thing is, I wanted to learn and be dev of some kind and help 
Gentoo.  While the dev mailing list has improved HUGELY, I still don't 
have much interest in it.  I offered to help wrangle bugs once but they 
didn't seem interested, even tho the bug cue got behind a good bit there 
for a while.  I'm disabled so I got some time I could spend on it.  Oh 
well.  This is life.  I'm happy using Gentoo.  ;-)

Dale

:-)  :-)



More information about the kde-linux mailing list