9:07 a.m.
This is a screen grab of a weird visual artifact that started appearing in the
upper right of my screen in the past few days. This is on an ASUS laptop
running F10 with all the latest software from testing and kde-redhat-unstable
http://www.eelpotflats.com/files/artifact.jpeg
While this is a static grab, the vertical lines that almost resemble
waveforms, short and green on the lower left side, and tall and gray on the
right side, are actually in motion from left to right, and the number that you
see is constantly changing appearing to vary between 57-62 continuously -- can
anyone think of what this might be? I have gone through all the plasmoids I
have turned on, and tried turning them off, and I've looked through the list of
running programs in system monitor, but nothing jumped off the page...
--
Claude Jones
Brunswick, MD
9:21 a.m.
Claude Jones wrote:
This is a screen grab of a weird visual artifact that started
appearing in the
upper right of my screen in the past few days. This is on an ASUS laptop
running F10 with all the latest software from testing and kde-redhat-unstable
http://www.eelpotflats.com/files/artifact.jpeg
Resembles what another reported recently when using qt-4.5 + ati
drivers. Are you an ati user too?
-- Rex
12:15 p.m.
On Sat February 21 2009 10:21:06 am Rex Dieter wrote:
Claude Jones wrote:
> This is a screen grab of a weird visual artifact that
> started appearing in the upper right of my screen in the
> past few days. This is on an ASUS laptop running F10 with
> all the latest software from testing and kde-redhat-unstable
> http://www.eelpotflats.com/files/artifact.jpeg
Resembles what another reported recently when using qt-4.5 +
ati drivers. Are you an ati user too?
nope - nVidia
--
Claude Jones
Brunswick, MD, USA
1:47 p.m.
Claude Jones wrote:
On Sat February 21 2009 10:21:06 am Rex Dieter wrote:
> Claude Jones wrote:
>> This is a screen grab of a weird visual artifact that
>> started appearing in the upper right of my screen in the
>> past few days. This is on an ASUS laptop running F10 with
>> all the latest software from testing and kde-redhat-unstable
>> http://www.eelpotflats.com/files/artifact.jpeg
> Resembles what another reported recently when using qt-4.5 +
> ati drivers. Are you an ati user too?
>
nope - nVidia
even better! ;)
-- Rex
2:19 p.m.
On Sat February 21 2009 2:47:39 pm Rex Dieter wrote:
>> Resembles what another reported recently when using qt-4.5
>> + ati drivers. Are you an ati user too?
>
> nope - nVidia
even better! ;)
-- Rex
Don't you go off on that jag, Rex!
Believe it or not, we'all (meaning most of us 'blob' users) know
how the wind blows - it's just not as clear-cut a problem as the
know-it-all college kids think; for me, it's simply not in the
economic cards to go out and purchase alternatives for the many
machines I run - besides, depite all the bad-mouthing, I actually
have had very few problems...and yes, there are issues with the
free alternatives - I just ran them on the aforementioned machine
for the past two months.
I saw the smiley, by the way, and I've always appreciated your
approach on the subtext, so, this reply is really directed
elsewhere... "-)
--
Claude Jones
Brunswick, MD, USA
2:57 p.m.
Claude Jones wrote:
On Sat February 21 2009 2:47:39 pm Rex Dieter wrote:
>>> Resembles what another reported recently when using qt-4.5
>>> + ati drivers. Are you an ati user too?
>> nope - nVidia
> even better! ;)
Don't you go off on that jag, Rex!
admonishment taken. I just have to be honest that I can't afford to
take too seriously issues where nvidia drivers are involved. Too much
tasted effort over time, nothing personal.
-- Rex
10:20 p.m.
On Saturday 21 February 2009 15:57:25 Rex Dieter wrote:
>> even better! ;)
>
> Don't you go off on that jag, Rex!
admonishment taken. I just have to be honest that I can't afford to
take too seriously issues where nvidia drivers are involved. Too much
tasted effort over time, nothing personal.
All sort of ailments have been plaguing me, so I'm just now able to reply. I
don't think I have an nVidia problem except for the weird artifact. John and
Tejas hit it - I turned off "Show FPS" and that got rid of it.
However, I was unable to run much of KDE all afternoon, and when I could,
KMail was crashing every few moments, usually when I'd try to highlight a part
of a message; it was also repeatedly refusing to display the preview pane and
I would have to go into settings and uncheck/check that feature; plasma
crashes every time I start - and on and on... I'm writing this message with
KMail but in Gnome, and I'm not experiencing any of the aforementioned
problems...
--
Claude Jones
Brunswick, MD
3:54 a.m.
On Sunday 22 February 2009 04:20:37 Claude Jones wrote:
All sort of ailments have been plaguing me, so I'm just now able
to reply.
I don't think I have an nVidia problem except for the weird artifact. John
and Tejas hit it - I turned off "Show FPS" and that got rid of it.
Like you Claude NV mobo + 7800 GFX card here and no problems,
However, I was unable to run much of KDE all afternoon, and when I
could,
KMail was crashing every few moments, usually when I'd try to highlight a
part of a message; it was also repeatedly refusing to display the preview
pane and I would have to go into settings and uncheck/check that feature;
plasma crashes every time I start - and on and on... I'm writing this
message with KMail but in Gnome, and I'm not experiencing any of the
aforementioned problems...
Did you update qt, akonadi, pim etc?
I did and it caused a terrible amount of problems (yes I know its all in
unstable) but normally things work well.
Kontact crashing on startup (kmail crashing) , kded4 eating up 80% CPU, Kmail
would run outside of Kontact but no preview in Kmails message window, akonadi
failing to start (dbus errors) etc.
Even just updating akonadi caused problems :(
*Sorry* but I cannot debug this as this is my main machine and had to get it
back to how it was, I use akonadi (kabc) so maybe that caused me more grief
than expected.
Rolled back to this now:
qt-4.4.3
akonadi-1.1.1-1
kdepim-4.2.0-2
And all is well again.
Cheers
Colin
--
Fedora 10 (Cambridge)
Registered Linux user number #342953
5:05 a.m.
On Sunday 22 February 2009 09:54:55 Colin J Thomson - G6AVK wrote:
Did you update qt, akonadi, pim etc?
I did and it caused a terrible amount of problems (yes I know its all in
unstable) but normally things work well.
Kontact crashing on startup (kmail crashing) , kded4 eating up 80% CPU,
kded4 eats all the available cpu (~96 % for me right now).
And all is well again.
Cheers
Colin
--
José Abílio
5:23 a.m.
On Sunday 22 February 2009 11:05:50 José Matos wrote:
On Sunday 22 February 2009 09:54:55 Colin J Thomson - G6AVK wrote:
> Did you update qt, akonadi, pim etc?
> I did and it caused a terrible amount of problems (yes I know its all in
> unstable) but normally things work well.
> Kontact crashing on startup (kmail crashing) , kded4 eating up 80% CPU,
kded4 eats all the available cpu (~96 % for me right now).
OK, in one way that's good to know. I first saw this after trying QT-4.5,
maybe roll back to 4.4?
Lets see what Rex/Kevin etc think, as mentioned I cant really do too much
serious debuging on this Box :(
Colin
--
Fedora 10 (Cambridge)
Registered Linux user number #342953
5:46 a.m.
On Sunday 22 February 2009 11:23:12 Colin J Thomson - G6AVK wrote:
OK, in one way that's good to know. I first saw this after trying
QT-4.5,
maybe roll back to 4.4?
Lets see what Rex/Kevin etc think, as mentioned I cant really do too much
serious debuging on this Box :(
After the removal of .local/share/akonadi this problem was fixed as well.
I'm still using qt-4.4 because for me all qt4 applications fonts are garbled
when using kde. :-(
Colin
--
José Abílio
6:47 a.m.
On Sunday 22 February 2009 11:46:16 José Matos wrote:
On Sunday 22 February 2009 11:23:12 Colin J Thomson - G6AVK wrote:
> OK, in one way that's good to know. I first saw this after trying QT-4.5,
> maybe roll back to 4.4?
> Lets see what Rex/Kevin etc think, as mentioned I cant really do too much
> serious debuging on this Box :(
After the removal of .local/share/akonadi this problem was fixed as well.
Confirmed, I have updated all now from unstable *except* qt and everything
seems OK.
So Clive's suggestion of moving .local/share/akonadi/ fixed all the problems.
I'll hold fire on qt until others report in.
Colin
--
Fedora 10 (Cambridge)
Registered Linux user number #342953
7:07 a.m.
On Sunday 22 Feb 2009 12:47:18 Colin J Thomson - G6AVK wrote:
I'll hold fire on qt until others report in.
qt-4.5 works for me! I'll upgrade my laptop with Intel graphics later on
today, but so far my results with f10, kde-unstable and nvidia hardware
(7900GTO, 8800GTX, GTX260) with 180.29 driver from rpmfusion have been
positive. (Excepting the couple of plasma 'gooblies', mentioned in earlier
post, almost certainly due to qt-4.5, but minor.)
Regards
Clive
--
Clive Messer <clive(a)vacuumtube.org.uk>
5:08 a.m.
On Sunday 22 Feb 2009 09:54:55 Colin J Thomson - G6AVK wrote:
Did you update qt, akonadi, pim etc?
I did and it caused a terrible amount of problems (yes I know its all in
unstable) but normally things work well.
Kontact crashing on startup (kmail crashing) , kded4 eating up 80% CPU,
Kmail would run outside of Kontact but no preview in Kmails message window,
akonadi failing to start (dbus errors) etc.
Even just updating akonadi caused problems :(
*Sorry* but I cannot debug this as this is my main machine and had to get
it back to how it was, I use akonadi (kabc) so maybe that caused me more
grief than expected.
Rolled back to this now:
qt-4.4.3
akonadi-1.1.1-1
kdepim-4.2.0-2
Akonadi wouldn't start for me after updating f10 from kde-redhat-unstable. I
think this was due to the change to its mysql db size. Removing it
(.local/share/akonadi/) solved that. It was re-created and has been working
fine since.
Regards
Clive
--
Clive Messer <clive(a)vacuumtube.org.uk>
5:13 a.m.
On Sunday 22 February 2009 11:08:42 Clive Messer wrote:
On Sunday 22 Feb 2009 09:54:55 Colin J Thomson - G6AVK wrote:
> Did you update qt, akonadi, pim etc?
> I did and it caused a terrible amount of problems (yes I know its all in
> unstable) but normally things work well.
> Kontact crashing on startup (kmail crashing) , kded4 eating up 80% CPU,
> Kmail would run outside of Kontact but no preview in Kmails message
> window, akonadi failing to start (dbus errors) etc.
>
> Even just updating akonadi caused problems :(
>
> *Sorry* but I cannot debug this as this is my main machine and had to get
> it back to how it was, I use akonadi (kabc) so maybe that caused me more
> grief than expected.
>
> Rolled back to this now:
>
> qt-4.4.3
> akonadi-1.1.1-1
> kdepim-4.2.0-2
Akonadi wouldn't start for me after updating f10 from kde-redhat-unstable.
I think this was due to the change to its mysql db size. Removing it
(.local/share/akonadi/) solved that. It was re-created and has been working
fine since.
OK thanks Clive, if I get time I'll try the latest Akonadi *only* again after
shifting .local/share/akonadi/ out of the way.
Cheers
Colin
--
Fedora 10 (Cambridge)
Registered Linux user number #342953
5:47 a.m.
On Sunday 22 February 2009 11:13:50 Colin J Thomson - G6AVK wrote:
On Sunday 22 February 2009 11:08:42 Clive Messer wrote:
> On Sunday 22 Feb 2009 09:54:55 Colin J Thomson - G6AVK wrote:
> > Did you update qt, akonadi, pim etc?
> > I did and it caused a terrible amount of problems (yes I know its all
> > in unstable) but normally things work well.
> > Kontact crashing on startup (kmail crashing) , kded4 eating up 80% CPU,
> > Kmail would run outside of Kontact but no preview in Kmails message
> > window, akonadi failing to start (dbus errors) etc.
> >
> > Even just updating akonadi caused problems :(
> >
> > *Sorry* but I cannot debug this as this is my main machine and had to
> > get it back to how it was, I use akonadi (kabc) so maybe that caused me
> > more grief than expected.
> >
> > Rolled back to this now:
> >
> > qt-4.4.3
> > akonadi-1.1.1-1
> > kdepim-4.2.0-2
>
> Akonadi wouldn't start for me after updating f10 from
> kde-redhat-unstable. I think this was due to the change to its mysql db
> size. Removing it (.local/share/akonadi/) solved that. It was re-created
> and has been working fine since.
OK thanks Clive, if I get time I'll try the latest Akonadi *only* again
after shifting .local/share/akonadi/ out of the way.
Update:
I stopped Akonadi and closed down Kontact, moved .local/share/akonadi/ out of
the way then installed the latest akonadi.i386 0:1.1.1-3
Restarted Akonadi (restart most likely not needed) and Kontact and all is well
so far.
Thanks Clive,
Colin
--
Fedora 10 (Cambridge)
Registered Linux user number #342953
5:19 a.m.
On Sunday 22 February 2009 11:08:42 Clive Messer wrote:
>
> Even just updating akonadi caused problems :(
>
> *Sorry* but I cannot debug this as this is my main machine and had to get
> it back to how it was, I use akonadi (kabc) so maybe that caused me more
> grief than expected.
>
> Rolled back to this now:
>
> qt-4.4.3
> akonadi-1.1.1-1
> kdepim-4.2.0-2
Akonadi wouldn't start for me after updating f10 from kde-redhat-unstable.
I think this was due to the change to its mysql db size. Removing it
(.local/share/akonadi/) solved that. It was re-created and has been working
fine since.
Funny, deleting that directory alone and restarting kde brought me the message
display back. :-)
No need to change or revert any other package.
Thanks Clive. :-)
Regards
Clive
--
José Abílio
5:34 a.m.
On Sunday 22 Feb 2009 11:19:33 José Matos wrote:
On Sunday 22 February 2009 11:08:42 Clive Messer wrote:
> Akonadi wouldn't start for me after updating f10 from
> kde-redhat-unstable. I think this was due to the change to its mysql db
> size. Removing it (.local/share/akonadi/) solved that. It was re-created
> and has been working fine since.
Funny, deleting that directory alone and restarting kde brought me the
message display back. :-)
No need to change or revert any other package.
Cool!
On a more general note, I am actually quite surprised how well KDE 4.2 is
working with qt-4.5. It's as stable as it was with with qt-4.4, and appears to
fix the icon background corruption in systray, once and for all. The only thing
I picked up on (other than the akonadi mysql db size change problem) is a
layout problem with the weather applet - cloud picture in the wrong place. And
possibly that the plasma desktop folder applet now has a black border - which
I don't think it had with qt-4.4.
Regards
Clive
--
Clive Messer <clive(a)vacuumtube.org.uk>
10:30 a.m.
New subject: Akonadi backwards compatibility (was: Re: weird artifact appearing in my upper right screen)
Clive Messer wrote:
Akonadi wouldn't start for me after updating f10 from
kde-redhat-unstable.
I think this was due to the change to its mysql db size.
Well, then unfortunately this looks like we have to revert this change and
stay with the original default size forever. Having to delete all your PIM
data is not an acceptable solution.
Kevin Kofler
11:16 a.m.
New subject: Akonadi backwards compatibility
Kevin Kofler wrote:
Clive Messer wrote:
> Akonadi wouldn't start for me after updating f10 from kde-redhat-unstable.
> I think this was due to the change to its mysql db size.
Well, then unfortunately this looks like we have to revert this change and
stay with the original default size forever. Having to delete all your PIM
data is not an acceptable solution.
the change as introduced should only affect *new* akonadi db's, old ones
should be unaffected.
-- Rex
12:09 p.m.
New subject: Akonadi backwards compatibility
On Sunday 22 Feb 2009 17:16:57 Rex Dieter wrote:
Kevin Kofler wrote:
> Clive Messer wrote:
>> Akonadi wouldn't start for me after updating f10 from
>> kde-redhat-unstable. I think this was due to the change to its mysql db
>> size.
>
> Well, then unfortunately this looks like we have to revert this change
> and stay with the original default size forever. Having to delete all
> your PIM data is not an acceptable solution.
the change as introduced should only affect *new* akonadi db's, old ones
should be unaffected.
Rex,
I wish I had made notes but I didn't. I think the problem - akonadi's mysql
instance refusing to start, was because of the discrepancy between the logfile
size, set to 8M in '~/.local/share/akonadi/mysql.conf' after the upgrade, and
the actual existing files on disk being larger. But take that with a pinch of
salt - I was half awake at the time.
Regards
Clive
--
Clive Messer <clive(a)vacuumtube.org.uk>
11:33 a.m.
New subject: Akonadi backwards compatibility
On Sunday 22 Feb 2009 18:09:31 Clive Messer wrote:
On Sunday 22 Feb 2009 17:16:57 Rex Dieter wrote:
I wish I had made notes but I didn't. I think the problem -
akonadi's mysql
instance refusing to start, was because of the discrepancy between the
logfile size, set to 8M in '~/.local/share/akonadi/mysql.conf' after the
upgrade, and the actual existing files on disk being larger. But take that
with a pinch of salt - I was half awake at the time.
> the change as introduced should only affect *new* akonadi
db's, old ones
> should be unaffected.
Rex,
It does affect existing setups.
The next time akonadi is re-started after the upgrade,
'~/.local/share/akonadi/mysql.conf' is modified....
innodb_log_file_size=64M -> innodb_log_file_size=8M
mysql then refuses to start ......
InnoDB: Error: log file ./ib_logfile0 is of different size 0 67108864 bytes
InnoDB: than specified in the .cnf file 0 8388608 bytes!
090223 17:30:44 [ERROR] Default storage engine (InnoDB) is not available
090223 17:30:44 [ERROR] Aborting
Regards
Clive
--
Clive Messer <clive(a)vacuumtube.org.uk>
11:36 a.m.
New subject: Akonadi backwards compatibility
Clive Messer wrote:
On Sunday 22 Feb 2009 18:09:31 Clive Messer wrote:
> On Sunday 22 Feb 2009 17:16:57 Rex Dieter wrote:
> I wish I had made notes but I didn't. I think the problem - akonadi's mysql
> instance refusing to start, was because of the discrepancy between the
> logfile size, set to 8M in '~/.local/share/akonadi/mysql.conf' after the
> upgrade, and the actual existing files on disk being larger. But take that
> with a pinch of salt - I was half awake at the time.
>> the change as introduced should only affect *new* akonadi db's, old ones
>> should be unaffected.
Rex,
It does affect existing setups.
The next time akonadi is re-started after the upgrade,
'~/.local/share/akonadi/mysql.conf' is modified....
eww, that's lame. I'll reask upstream about that undesirable behavior.
-- Rex
1:31 p.m.
New subject: Akonadi backwards compatibility
Rex Dieter wrote:
Clive Messer wrote:
> On Sunday 22 Feb 2009 18:09:31 Clive Messer wrote:
>> On Sunday 22 Feb 2009 17:16:57 Rex Dieter wrote:
>> I wish I had made notes but I didn't. I think the problem - akonadi's
mysql
>> instance refusing to start, was because of the discrepancy between the
>> logfile size, set to 8M in '~/.local/share/akonadi/mysql.conf' after the
>> upgrade, and the actual existing files on disk being larger. But take that
>> with a pinch of salt - I was half awake at the time.
>>> the change as introduced should only affect *new* akonadi db's, old ones
>>> should be unaffected.
> Rex,
>
> It does affect existing setups.
>
> The next time akonadi is re-started after the upgrade,
> '~/.local/share/akonadi/mysql.conf' is modified....
eww, that's lame. I'll reask upstream about that undesirable behavior.
okie dokie,
akonadi-1.1.1-5 pushed to kde-redhat/testing includes a (now upstreamed)
patch that should help address these issues.
users' mysql.conf is updated only of /etc/akonadi/mysql-global.conf (or
mysql-local.conf) is newer, and on update, will automatically remove any
pre-existing ib_logfile's.
-- Rex
1:03 p.m.
New subject: Akonadi backwards compatibility
On Sunday 22 February 2009 17:16:57 Rex Dieter wrote:
Kevin Kofler wrote:
> Clive Messer wrote:
>> Akonadi wouldn't start for me after updating f10 from
>> kde-redhat-unstable. I think this was due to the change to its mysql db
>> size.
>
> Well, then unfortunately this looks like we have to revert this change
> and stay with the original default size forever. Having to delete all
> your PIM data is not an acceptable solution.
the change as introduced should only affect *new* akonadi db's, old ones
should be unaffected.
Rex, today I decided it was time I took a look at this. Akonadi has not been
used before, so should be one of your "new" dbs. I get the same error as
others have reported, I think -
log file .ib_logfile0 is of different size 0 67108664 than specified in the
.cnf file 0 8388608
Anne
1:57 p.m.
New subject: Akonadi backwards compatibility (was: Re: weird artifact appearing in my upper right screen)
On Sunday 22 February 2009 18:30:43 Kevin Kofler wrote:
Clive Messer wrote:
> Akonadi wouldn't start for me after updating f10 from
> kde-redhat-unstable. I think this was due to the change to its mysql db
> size.
Well, then unfortunately this looks like we have to revert this change and
stay with the original default size forever. Having to delete all your PIM
data is not an acceptable solution.
Kevin Kofler
Try this..,
System Settings -> Advanced -> Akondi Configuration -> Akondi Server
Configuration
Uncheck Use Internal MySQL executable.
Click on Restart
Check Use Internal MySQL executable.
Click on Restart
Oh... By the way. Clicking on test produces an warning in the maysql server
log which when selectected and then the hyperlink is opened and openoffice
opens reports
090222 21:48:09 InnoDB: Started; log sequence number 0 148366
090222 21:48:09 [Warning] Can't open and lock time zone table: Table
'mysql.time_zone_leap_second' doesn't exist trying to live without them
090222 21:48:09 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.67-log' socket:
'/home/eli/.local/share/akonadi/db_misc/mysql.socket' port: 0 Source
distribution
Any thoughts.
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
9:24 a.m.
Did you enable the 'Show FPS' desktop effect in PLasma?
On Sat, 21 Feb 2009, Claude Jones sent out 1.0K bytes to say:
This is a screen grab of a weird visual artifact that started
appearing in the
upper right of my screen in the past few days. This is on an ASUS laptop
running F10 with all the latest software from testing and kde-redhat-unstable
http://www.eelpotflats.com/files/artifact.jpeg
While this is a static grab, the vertical lines that almost resemble
waveforms, short and green on the lower left side, and tall and gray on the
right side, are actually in motion from left to right, and the number that you
see is constantly changing appearing to vary between 57-62 continuously -- can
anyone think of what this might be? I have gone through all the plasmoids I
have turned on, and tried turning them off, and I've looked through the list of
running programs in system monitor, but nothing jumped off the page...
--
Claude Jones
Brunswick, MD
_______________________________________________
fedora-kde mailing list
fedora-kde(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/fedora-kde
--
Tejas Dinkar
http://gja.in
2:14 p.m.
2009/2/21 Claude Jones <cjoneslists(a)tehogeeservices.com>
On Sat February 21 2009 10:24:10 am Tejas Dinkar wrote:
> Did you enable the 'Show FPS' desktop effect in PLasma?
I'm not near the machine, but I'll check when I get home
Think i know whats causing things. I tried using the FPS effect a while back
and it didnt work so i disabled it again. Tried it now and it does work and
looks exactly like the screenshot. My guess is that you also enabled it at
some point, it also didnt work but didnt disable it again. Now it suddenly
works and it magically appears and nobody knows what it is.
For the record i am also using nvidia and if i remember right there was an
nvidia driver update a couple of days ago so FPS working could be that or
perhaps a change in kde/update in qt
--
There are 10 kinds of people in the world: Those who understand binary and
those who don't...
5532
days inactive
5535
days old
28 comments
10 participants
participants (10)
-
Anne Wilson -
Claude Jones -
Clive Messer -
Colin J Thomson -
Eli Wapniarski -
John5342 -
José Abílio Matos -
Kevin Kofler -
Rex Dieter -
Tejas Dinkar