Xorg 7 broke amsn

_Gandalf_ · 2006-02-20 19:47:42

hello,

I've been running Xorg 7 since a month also i always used amsn, it was great, but after the last update of Xorg 7, my amsn turned out to be broken

[wael@nasreddine ~]$ amsn
Application initialization failed: this isn't a Tk applicationinvalid color name "#f0f0f0 "

Xorg.conf -> http://pastebin.ca/42279

GCN · 2006-02-20 19:58:05

I have a similar problem but when trying to run NexTView EPG:

$ nxtvepg 
Failed to initialise the Tk library at '/usr/lib/tk8.4' - exiting.
Tk error message: this isn't a Tk applicationinvalid color name "#dcdcdc "
$ wish
Application initialization failed: this isn't a Tk applicationinvalid color name "#dcdcdc "

Everything was working nice before I upgrade du Xorg 7 :s !

whargoul · 2006-02-20 20:27:43

It works fine here. Strange..

_Gandalf_ · 2006-02-20 20:28:51

Lucky u :S

lessthanjake · 2006-02-20 20:31:10

I have the same with emacs and xpdf, maybe it is a gtk1 thing?

kozaki · 2006-02-21 10:02:08

xpdf & all other apps I started since (xorg7 shift) yesterday started fine but not Amsn :
$ amsn
Application initialization failed: this isn't a Tk applicationinvalid color name "#efefef "

Cerebral · 2006-02-21 13:59:26

The problem I'm noticing is there's always an extra space after the colour name... I had this problem after upgrading urxvt once; one of the colours in my ~/.Xresources file had a space, and wouldn't parse correctly.

eg.

urxvt*colour0:       white 
                          ^ SPACE! zomg :P

Then I got: invalid colour "white " just like you guys are getting. Suggestion: check ~/.Xresources, and make sure every colour name ends immediately in a newline.

If that's not the problem, check where colours are defined in your amsn config files (if such a place exists) and check those colours.

If neither of the above helps, then I'd say it's an application problem that probably needs to be fixed upstream.

_Gandalf_ · 2006-02-21 14:59:34

Well first aMSN haven't a problem with the dummy xorg package, the problem came right after the "split-up" I'm using Xorg 7 since Jan 20th (AFAIR) and it stoped working right after the upgarde when it was still in Testing
now following ur suggestion i don't have any file called ~/.Xresources so i am not sure the problem comes from this file...
Tonight a bug will be filled if no other suggestions, hope the devels will have better view of it...

rafal · 2006-02-21 16:52:30

_Gandalf_ wrote:

now following ur suggestion i don't have any file called ~/.Xresources so i am not sure the problem comes from this file...
Tonight a bug will be filled if no other suggestions, hope the devels will have better view of it...

I have .Xresources file but the problems still exist even if I rename .Xresources to .Xresources.bak

It is also surprising that

xrdb -merge .Xresources

gives errors

Predefined macro file
'/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include/mcpp_gcc40_predef_old.h' is not found
Predefined macro file
'/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include/mcpp_gcc40_predef_std.h' is not found

and before upgrading to xorg7 it was ok.

jinn · 2006-02-21 17:09:42

Im having the same problems.. I just bought a new laptop MSI s260 12" (*gloating ), and installed xorg 7.0 and I get this problem trying to run amsn:

[root@estergon jinn]# amsn
Application initialization failed: this isn't a Tk applicationinvalid color name "#eeeee0 "

_Gandalf_ · 2006-02-21 17:25:18

Ok a bug has been filed, please refer to it -> http://bugs.archlinux.org/task/4034

n3olynx · 2006-02-21 17:38:57

I want to confirm the same problem with amsn.
I also get the same error when trying to run modelSim.
Also, when I run xspim I get the following warnings:

Warning: Color name "#efefef " is not defined
Warning: Color name "#ffffff " is not defined
Warning: Color name "#000000 " is not defined

I suspect the extra space at the end is the problem, but these problems never occurred before the xorg split.

Hope this bug gets resolved quickly.

Pierluigi · 2006-02-21 18:35:36

had the same.

reinstall every xorg related package (pacman -Qs xorg).

Cerebral · 2006-02-21 18:40:38

Pierluigi wrote:

reinstall every xorg related package (pacman -Qs xorg).

Meaning.. you've fixed it, and that's how? Or that's what you've tried, but it didn't work?

rafal · 2006-02-21 19:23:33

Pierluigi wrote:

had the same.
reinstall every xorg related package (pacman -Qs xorg).

I followed this advice and did

# pacman -S xorg xorg-apps xorg-clients xorg-font-utils xorg-fonts-alias xorg-fonts-encodings xorg-fonts-misc xorg-res-utils xorg-server xorg-server-utils xorg-twm xorg-utils xorg-xauth xorg-xdm xorg-xfwp xorg-xinit xorg-xkb-utils xorg-xsm

but it didn't help

_Gandalf_ · 2006-02-21 19:50:08

Don't bother reinstalling packages guys, Ive done already 5 fresh reinstalls with gnome 2.12 / gnome 2.13 and another with KDE, but this has nothing to do with it...

lillwad · 2006-02-21 21:29:49

The fix from the bugtracker worked for me.

pacman -Rd mcpp

jinn · 2006-02-21 22:07:14

Yepp, that did the trick. I had to restart to have it work though, just to let you others know.

n3olynx · 2006-02-22 00:10:16

Yeah, that solved xspim warnings.........haven't confirmed with the other apps. But, do any problems occur or will occur because of the removal of mcpp?

*Sorry, just noted the mcpp package update. Discard the question.*

JGC · 2006-02-22 12:23:24

Removing mcpp won't cause any problems, because xrdb uses the cpp binary in the gcc package if mcpp isn't available. This was the default with previous versions. The reason for adding mcpp as dependency instead of using cpp is because the speedup it gives: when you login, the cpp binary is ran two or three times, which is slow when your cpp binary is in fact just a stub that calls the true C/C++ compiler on your system, which is 30MB.

GCN · 2006-02-22 19:06:31

jinn wrote:

Yepp, that did the trick. I had to restart to have it work though, just to let you others know.

Same here, I had to restart but everything's OK after the removal of mcpp.

Many thanks to the guy who found this "fix" .

Cerebral · 2006-03-02 20:27:25

bl44t44p wrote:

I removed the package restarted X and it still doesn't work
Application initialization failed: this isn't a Tk applicationunknown color name "Black"
Note that there isn't a space for me on the end.

I don't think your paths are updated properly in Xorg.conf.
See:
http://wiki.archlinux.org/index.php/Xor … uration.29

n3olynx · 2006-03-03 02:16:29

had the same problem with emacs today. Just make the xorg changes and restart X server. Things should work afterwards

Arch Linux

#1 2006-02-20 19:47:42

Xorg 7 broke amsn

#2 2006-02-20 19:58:05

Re: Xorg 7 broke amsn

#3 2006-02-20 20:27:43

Re: Xorg 7 broke amsn

#4 2006-02-20 20:28:51

Re: Xorg 7 broke amsn

#5 2006-02-20 20:31:10

Re: Xorg 7 broke amsn

#6 2006-02-21 10:02:08

Re: Xorg 7 broke amsn

#7 2006-02-21 13:59:26

Re: Xorg 7 broke amsn

#8 2006-02-21 14:59:34

Re: Xorg 7 broke amsn

#9 2006-02-21 16:52:30

Re: Xorg 7 broke amsn

#10 2006-02-21 17:09:42

Re: Xorg 7 broke amsn

#11 2006-02-21 17:25:18

Re: Xorg 7 broke amsn

#12 2006-02-21 17:38:57

Re: Xorg 7 broke amsn

#13 2006-02-21 18:35:36

Re: Xorg 7 broke amsn

#14 2006-02-21 18:40:38

Re: Xorg 7 broke amsn

#15 2006-02-21 19:23:33

Re: Xorg 7 broke amsn

#16 2006-02-21 19:50:08

Re: Xorg 7 broke amsn

#17 2006-02-21 21:29:49

Re: Xorg 7 broke amsn

#18 2006-02-21 22:07:14

Re: Xorg 7 broke amsn

#19 2006-02-22 00:10:16

Re: Xorg 7 broke amsn

#20 2006-02-22 12:23:24

Re: Xorg 7 broke amsn

#21 2006-02-22 19:06:31

Re: Xorg 7 broke amsn

#22 2006-03-02 20:27:25

Re: Xorg 7 broke amsn

#23 2006-03-03 02:16:29

Re: Xorg 7 broke amsn

Board footer