Re: [gentoo-user] [NEWBIE] emerge blocked

2005-06-06 Thread Juan Ignacio Sánchez Lara
I always solve it by unmerging (emerge -C) the blocker one
(x11-themes/gnome-themes) and reemerging it afterwards.

On 6/6/05, Jules Colding [EMAIL PROTECTED] wrote:
 Hi all,
 
 I tried to do an sync/update but emerge is complaining. What should I do
 about this error if I want to run gnome? Should I unmerge something?
 
 ###
 omc-1 root # emerge --update --deep --pretend world
 
 These are the packages that I would merge, in order:
 
 Calculating world dependencies ...done!
 [blocks B ] =x11-themes/gnome-themes-2.8.2 (is blocking 
 x11-themes/gtk-engines-2.6.3)
 [blocks B ] app-admin/gnome-system-tools-1.1.91 (is blocking 
 app-admin/system-tools-backends-1.2.0)
 ###
 
 
 Thanks,
   jules
 
 
 --
 Jules Colding
 PGP Public Key: 6266E7B7
 
 --
 gentoo-user@gentoo.org mailing list
 
 


-- 
Juan Ignacio Sánchez Lara
Ingeniero Técnico en Informática de Sistemas

-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] Entrance (enlightenment) problem

2005-06-06 Thread Juan Ignacio Sánchez Lara
Hello,

I've followed the instructions at
http://gentoo-wiki.com/HOWTO_emerge_e17 to install Enlightenment and
Entrance, but I can't open a desktop session. xdm opens Entrance, but
when I input my user and pass it goes black for a moment (as if it
were changing the resolution) and goes back to entrance login without
prompting a word.

What can go wrong?

Thanks
-- 
Juan Ignacio Sánchez Lara
Ingeniero Técnico en Informática de Sistemas

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Entrance (enlightenment) problem

2005-06-06 Thread Juan Ignacio Sánchez Lara
:
#
# Gnome - will start gnome-session
# kde-version - will start startkde (ex: kde-3.0.2)
# Xsession - will start a terminal and a few other nice apps

XSESSION=kde-3.3.2







 
 
 --
 gentoo-user@gentoo.org mailing list
 
 


-- 
Juan Ignacio Sánchez Lara
Ingeniero Técnico en Informática de Sistemas

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Entrance (enlightenment) problem [SOLVED]

2005-06-06 Thread Juan Ignacio Sánchez Lara
I must admit it's quite embarrasing, but now it works... I changed
XSESSION to kde-3.4 and now it works, not only kde but also
enlightenment I can't realize why it has made it to work, but the
fact it's the only thing I've touched...

Thanks everybody

On 6/6/05, Juan Ignacio Sánchez Lara [EMAIL PROTECTED] wrote:
  Several questions:
 
  Are you selecting a specific WM from the drop-down menu, or are you just
  using Default? I am not certain that Entrance has/uses a Default
  setting, wherever it may come from. You'd think from /etc/rc.conf, but
  heck, GDM doesn't use that to set its default (it asks you, so it has
  its own config for this somewhere), so maybe Entrance doesn't either
  (although it never asked me about setting anything as default).
 
  Do you have any other WMs installed and listed, and have you tried
  logging into them instead? Do any of them work, and which ones do not?
 I've tried not only default but enlightenment and kde (the WMs I
 have). None worked. I've checked that the database entries correspond
 with /etc/X11/Session files.
 
 
  If Enlightenment itself is the one that doesn't work, did you previously
  have e16 installed? I did, and even though e17 very kindly moved the
  previous enlightenment.desktop item in /etc/X11/Sessions to e16.desktop,
  neither the e16 entry appeared in the list, nor did choosing
  Enlightenment start e17.
 e17 is the first Enlightenment release I install.
 
 
  This turned out to be because the exec line in the Enlightenment.desktop
  entry was still pointing to /usr/bin/enlightenment, whereas the binary
  for e17 is named something like enlightenment-0.17 (to distinguish it
  from the e16 binary). So I changed the exec line in the script, and then
  it was fine.
 
  However I uninstalled both e16 and e17 (I may reinstall e16, which I
  liked much better), and switched to fvwm anyway. But e17 sure is pretty,
  can't argue with that.
 
  Hope this helps,
 
  Holly
 
 Thanks for the reply, anyway...
 
 
 
 
 
 
 Here's my rc.conf (someone asked for it):
 
 # /etc/rc.conf: Global startup script configuration settings
 # $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/rc.conf,v 1.22
 2003/10/21 06:09:42 vapier Exp $
 
 # Use KEYMAP to specify the default console keymap.  There is a complete tree
 # of keymaps in /usr/share/keymaps to choose from.  This setting is used by 
 the
 # /etc/init.d/keymaps script.
 
 KEYMAP=es
 
 # Should we first load the 'windowkeys' console keymap?  Most x86 users will
 # say yes here.  Note that non-x86 users should leave it as no.
 
 SET_WINDOWKEYS=yes
 
 # The maps to load for extended keyboards.  Most users will leave this as is.
 
 EXTENDED_KEYMAPS=
 #EXTENDED_KEYMAPS=backspace keypad
 
 # CONSOLEFONT specifies the default font that you'd like Linux to use on the
 # console.  You can find a good selection of fonts in /usr/share/consolefonts;
 # you shouldn't specify the trailing .psf.gz, just the font name below.
 # To use the default console font, comment out the CONSOLEFONT setting below.
 # This setting is used by the /etc/init.d/consolefont script (NOTE: if you do
 # not want to use it, run rc-update del consolefont as root).
 
 #CONSOLEFONT=default8x16
 CONSOLEFONT=lat9w-16
 
 # CONSOLETRANSALTION is the charset map file to use.  Leave commented to use
 # the default one.  Have a look in /usr/share/consoletrans for a selection of
 # map files you can use.
 
 #CONSOLETRANSLATION=8859-1_to_uni
 CONSOLETRANSLATION=8859-15_to_uni
 
 # Set CLOCK to UTC if your system clock is set to UTC (also known as
 # Greenwich Mean Time).  If your clock is set to the local time, then set 
 CLOCK
 # to local.  This setting is used by the /etc/init.d/clock script.
 
 CLOCK=local
 
 # Set EDITOR to your preferred editor.
 
 #EDITOR=/bin/nano
 EDITOR=/usr/bin/vim
 #EDITOR=/usr/bin/emacs
 
 # Set PROTOCOLS to the protocols that you plan to use.  Gentoo Linux will only
 # enable module auto-loading for these protocols, eliminating annoying module
 # not found errors.
 #
 # NOTE: Do NOT uncomment the next lines, but add them to 'PROTOCOLS=...' 
 line!!
 #
 # Num   Protocol
 # 1:Unix
 # 2:IPv4
 # 3:Amateur Radio AX.25
 # 4:IPX
 # 5:DDP / appletalk
 # 6:Amateur Radio NET/ROM
 # 9:X.25
 # 10:   IPv6
 # 11:   ROSE / Amateur Radio X.25 PLP
 # 19:   Acorn Econet
 
 # Most users want this:
 PROTOCOLS=1 2
 
 #For IPv6 support:
 #PROTOCOLS=1 2 10
 
 # What display manager do you use ?  [ xdm | gdm | kdm | entrance ]
 DISPLAYMANAGER=kdm
 #DISPLAYMANAGER=entrance
 
 # XSESSION is a new variable to control what window manager to start
 # default with X if run with xdm, startx or xinit.  The default behavior
 # is to look in /etc/X11/Sessions/ and run the script in matching the
 # value that XSESSION is set to.  The support scripts is smart enouth to
 # look in all bin directories if it cant find a match in /etc/X11/Sessions/,
 # so setting it to enligtenment can also work.  This is basically used
 # as a way

Re: [gentoo-user] Kile dependencies after upgrading to kde 3.4 [solved]

2005-05-11 Thread Juan Ignacio Sánchez Lara
I have finally not solved it that way, but thanks anyway... Working
with --tree emerge option an emerging kdegraphics-meta (as well as
kdegraphics software like kgamma and kolourpaint has been enough to
mantain the upgrade.

I have also unmerged 3.3 packages.

Thanks

On 5/11/05, Victor Arguelles [EMAIL PROTECTED] wrote:
 El Tue, 10 May 2005 17:03:26 +
 Juan Ignacio Sánchez Lara [EMAIL PROTECTED] dijo:
 
 This has been discussed before. Look it up in the archives, there's a
 thread with instructions on how to do this started on april 11.
 Basically you need to add the kde packages themselves (not kde-meta)
 to /etc/portage/packages.keywords with ~x86 (or ~amd64 or whatever).
 This is the only way for your kde-3.4.0 to survive a world update. In
 that thread you'll see which packages.
 
 Regards,
 ~vi
 --
 gentoo-user@gentoo.org mailing list
 
 


-- 
Juan Ignacio Sánchez Lara
Ingeniero Técnico en Informática de Sistemas

-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] Kile dependencies after upgrading to kde 3.4

2005-05-10 Thread Juan Ignacio Sánchez Lara
Hi everybody

Finally I couldn't for kde 3.4 to be in the stable branch and I
upgraded. No serious problem until I tried to emerge --update --deep
--newuse world --verbose (the way I always upgrade my system). When I
tried to emerge that way, it replied that kile-1.7.1 had some
dependencies, and since I thought it would be because it's a
before-kde-3.4 version I upgraded to the -unstable- 1.8_beta2. The
problem is that when I tried again to emerge world it replied the
following:


Calculating world dependencies \
!!! All ebuilds that could satisfy ~kde-base/kdebase-3.4.0 have been masked.
!!! One of the following masked packages is required to complete your request:
- kde-base/kdebase-3.4.0 (masked by: ~x86 keyword)

For more information, see MASKED PACKAGES section in the emerge man page or
section 2.2 Software Availability in the Gentoo Handbook.
!!!(dependency required by kde-base/kdegraphics-3.4.0 [ebuild])


!!! Problem with ebuild app-editors/kile-1.8_beta2
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.


AFAIK kdebase and kdegraphics correspond to the old way to emerge kde,
isn't it? What's the problem, then? Are kile dependencies wrong?
Should I emerge/configure something I missed?

Is there any workaround for this?

Thanks in advance.

-- 
Juan Ignacio Sánchez Lara
Ingeniero Técnico en Informática de Sistemas

-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] TV-out with radeon mobility 9700

2005-05-10 Thread Juan Ignacio Sánchez Lara
Hello,

I'm trying to get the TV-out working... In xorg.conf I change two
lines with the following values, according to
http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_tvout:

Option MonitorLayout  NONE, AUTO
Option TVColorAdj 0

When restarting Xorg I get no output at the LCD (as it's supposed to
be), and I get something in the TV: I can see kdm there, but too
flickering (as it had a wrong frequency, it's hard for me to explain
that).

What else must I configure in order to make it work? I have installed
ati-drivers 8.10.19.

Thanks in advance

-- 
Juan Ignacio Sánchez Lara
Ingeniero Técnico en Informática de Sistemas

-- 
gentoo-user@gentoo.org mailing list