Linux Help

SubTract · January 26, 2015

Hi guys,

So I spent the last couple of days installing arch linux on my computer, I've managed to figure out most of the problems I ran in to (There were so many more than I expected)

Now I've used linux in bits and bobs over the years but mainly in Fedora or Ubuntu where a lot of stuff can be done graphically. This has really been my first full dive experience and I've decided to go all in... no more windows.

Arch Linux 3.18.3-1

Gnome 3.14.0

lxdm

Hardware in sig

Anyway I'm left with 2 problems that I just can't seem to get around.

The first is when I try to run the Amd Catalyst control center

amdcccle

and it returns

(amdcccle:21497): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Trace/breakpoint trap (core dumped)

So then I went to try and find out what's happening. So I used pkg-config to list the gtk libraries.

pkg-config --libs gtk+-2.0 clutter-gtk-1.0 gthread-2.0

and it returned

-lgtk-x11-2.0 -lgdk-x11-2.0 -lpangoft2-1.0 -lfontconfig -lfreetype -lclutter-gtk-1.0 -lclutter-1.0 -lcogl-path -lcogl-pango -lcogl -lgmodule-2.0 -pthread -lwayland-egl -lgbm -ldrm -lEGL -lXrandr -ljson-glib-1.0 -lwayland-cursor -lwayland-client -lxkbcommon -lwayland-server -lX11 -lXext -lXdamage -lXfixes -lXcomposite -lXi -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lgthread-2.0 -pthread -lglib-2.0

Now the problem is. I used yaourt to install CCC, So I didn't compile it. I'm not even sure how this happened.

When I first installed it the drivers worked but I couldn't open CCC. I then fixed my locale and it opened.

My problem is now. I don't really know what to do. I don't know if I can even remove them. But even if I can it will likely break a bunch of other stuff.

Any suggestions??

|

Second problem

When I first installed gnome, I used gdm instead of lxdm

This worked fine until I installed CCC

once I installed the AMD drivers I would no longer get thrown into X It would stay on the terminal.

So I switched to lxdm, all of a sudden I was getting the desktop manager and I could log in again.

So I tried to re-install gdm afterward

$ sudo pacman -S gdm

after the download when it gets to install it outputs

(1/1) installing gdm [##############################################################################] 100%
warning: directory ownership differs on /var/lib/gdm/
filesystem: 120:120 package: 0:0
warning: directory ownership differs on /var/lib/gdm/.local/
filesystem: 120:120 package: 0:0
warning: directory ownership differs on /var/lib/gdm/.local/share/
filesystem: 120:120 package: 0:0
Optional dependencies for gdm
fprintd: fingerprint authentication

Then if I remove

sudo pacman --remove gdm

(1/1) removing gdm [##############################################################################] 100%
error: command failed to execute correctly

it outputs an error.

However it actually works if I try to remove again it says no file or directory.

Now I was considering changing the ownership of the directory /var/lib/gdm

with something like

sudo chown -R root: /var

But I don't think that everything in or down from /var in owned from root, Is this safe?

SubTract · January 26, 2015

I recommend installing Catalyst from a third party repo instead of the AUR so first uninstall you already have with
pacman -Q | grep catalyst | awk '{print $1}' | xargs pacman -Rdd --noc
then
echo -e "\n[catalyst]\nServer = http://catalyst.wirephire.com/repo/catalyst/x86_64" >> /etc/pacman.confpacman-key -r 653C3094 ; pacman-key --lsign-key 653C3094echo "blacklist radeon" > /etc/modprobe.d/radeon.confsed -i 's/quiet/nomodeset/' /etc/default/grubgrub-mkconfig -o /boot/grub/grub.cfgsystemctl enable catalyst-hooktelinit 6
I have never bothered using a login manager because I prefer to do any system maintenance before starting the desktop manually. With a 280X, I actually got better performance with the open source xf86-video-ati driver instead of Catalyst 14.12 in Unigine Valley. Enabling crossfire results in halving the performance. It seems many other people are also having subpar performance with 14.12 in Linux - http://www.phoronix.com/scan.php?page=news_item&px=Interstellar-Marines-Catalyst

Thanks,

would I be installing catalyst again,

Or just leave it removed?

pacman -S catalyst catalyst-utils

?

Also I'm using Grub with EFIbootloader.

Would I continue to modify that grub file or the one in efivarfs?

SubTract · January 26, 2015

"@Name Taken"

Woah, Holy cow. I totally missed half of your post.

This worked... Well mostly :-)

when I initially installed the drivers the repo one didn't work. I had to use the AUR one.

I now realise that is because catalyst-libgl is now split from the catalyst-utils package and you have to install in separately. (Official repo hasn't added it yet)

It will now allow me to run the root access amdcccle however the standard one continues to have the same error. This works for me though at least I use crossfire and manage displays easily.

Thank you very much.

Bonus is too now when there is an upgrade I won't have to rebuild the driver. :-)

As for the display manager, I'm fairly happy with lxdm. Just means I can't use the gnome background change interface to change the background.

Thanks for all you help.

SubTract · January 27, 2015

I realized I forgot to include the Pacman install command in my first post in which case its
pacman -Sy catalyst-hook catalyst-libgl catalyst-utils opencl-catalyst
Catalyst-hook rebuilds the driver module then you do a kernel update and the standard Pacman upgrade command also updates Catalyst.

When you posted it you did say to install catalyst from a third party repo, Which I had already added. I just missed the top line. So I just did this ^^ anyway.

What is really interesting is if I run amdcccle as user $ it outputs

(amdcccle:10039): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported

Trace/breakpoint trap (core dumped)

If I run as root # it outputs

(amdcccle:9915): GConf-WARNING **: Client failed to connect to the D-BUS daemon:

Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(amdcccle:9915): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported

Trace/breakpoint trap (core dumped)

If I run as my user $ sudo amdcccle it outputs

libpng warning: iCCP: known incorrect sRGB profile

but CCC launches.

from what I can gather these warnings are pretty harmless, and my colour looks fine so I'm going to ignore them. I'm just curious as to why I'm not getting caught up on the same Gtk-error as I am with root or standard access.