Re: [gentoo-user] Gnome3 haters: you should try the new cinnamon-1.6.1
On Tue, Oct 16, 2012 at 12:52 AM, m...@trausch.us m...@trausch.us wrote: On 10/15/2012 08:38 AM, Michael Hampicke wrote: Thanks for the heads-up, last time I looked nemo was not in portage. I use gnome3.6 and dislike the new nautilus - still have version 3.4 of it installed. But now I can switch to nemo. GNOME 3.6 landed? I know it was released, but I still don't have it on my system... I'm assuming that it requires more unmasking and modification of the /etc/portage/* stuff? 3.6 is not in the official tree, but it is in the GNOME overlay: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=summary (And yeah, it needs unmasking and modification of the /etc/portage/* stuff). (Incidentally, when will it become stable as a whole? I realize I must be one of the very few dissenters to the subject here, but jhbuild never works for me, and GNOME is the only thing that I don't fully have that I want. That, and I want to check out the GNOME boxes feature...) We are not that few, we just don't scream so loudly ;) I don't know when it will become stable, but at the sooner it will be with 3.8, I reckon. Probably 3.10. However, 3.6 is running pretty much great, but you kinda need to know what are you doing before starting to unmask and keyword stuff. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: [PATCH] Linus breaks nvidia-drivers again
change VM_RESERVERD to VM_DONTDUMP|VM_IO 2012/10/16 walt w41...@gmail.com: On 10/15/2012 11:10 AM, Walter Dnes wrote: On Mon, Oct 15, 2012 at 09:05:27AM -0700, walt wrote Well, this is really a temporary workaround for people who like to run the latest git kernel from Linus, and it's only tested for nvidia-drivers-302.17-r1, and only on ~amd_64. Which kernel version does the breakage start at, so I know not to rush into it when it goes mainstream? Linus committed the breakage to his git repository just last week, so the nvidia people should have it fixed for 3.7. Same goes for virtualbox and ati-drivers, I hope. But to answer your question, the breakage starts with linux-3.7.0-rc1.
Re: [gentoo-user] Heads Up - mesa-9.0 needs media-libs/glu in addition
On Wed, Oct 10, 2012 at 5:09 PM, Robin Atwood robin.atw...@attglobal.net wrote: On Tuesday 09 October 2012, Helmut Jarausch wrote: upgrading from mesa-9.0_pre20120918 to mesa-9.0 broke some package, among them ati-drivers. They have remove glu. Installing media-libs/glu in addition now (never needed it before) restores the essential /usr/include/GL/glu.h file. I found the same problem with KDE. media-libs/glu should become a dependency! -Robin If you don't file a bug it will never be ;) -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
Re: [gentoo-user] Re: Gnome3 haters: you should try the new cinnamon-1.6.1
This was my thread right before switching to lxde http://forums.gentoo.org/viewtopic-t-928750-start-0.html i assume that everything is correct in my system. sometimes i use the one driver, sometimes the other. both have advantages against the other one, but gnome3 experience is always HELL. (fglrx wasnt working at all for months with gnome shell) dont know if this is fixed already On 10/16/2012 01:07 AM, walt wrote: On 10/15/2012 12:40 PM, mindrunner wrote: 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] Are you using the proprietary ati drivers? (x11-drivers/ati-drivers) If yes, does fgl_glxgears run okay? On 10/15/2012 02:23 PM, walt wrote: On 10/15/2012 12:24 AM, mindrunner wrote: Ive had soo many problem with gnome 3 (mainly performance), so i switched to lxde. The performance penalty can be due to old video hardware because both gnome-shell and cinnamon use video compositing for silly and unnecessary stuff like transparent windows.
[gentoo-user] heartbeat problem
Hello, i've tried to use heartbeat (v 3.0.5). It starts, but a bit later it kills himself. I complains that it can not access /var/run/heartbeat/*.pid which is true. The directory /var/run/heartbeat does not exist. Also - as far as i can see /var/run is cleaned at start of a system. So any manually created directory here at install time will get lost. As workaround i placed in /etc/init.d/heartbeat the following code: - cut - if ! [ -d /var/run/heartbeat ] then mkdir /var/run/heartbeat fi - cut - With this change heartbeat starts without problems. I don't know wheter this is the proper solution or the reason for this problem is caused by an other source. Before i place an item in bugzilla i would like to know if you think this 'hack' is the one to use. Otherwise you could point mo to the proper solution of this issue. regards Petric
[gentoo-user] dhcp delays when booting (wicd)
Hi, I've been using wicd for quite awhile on my laptop and it works fine with both wired and wireless interfaces. However I'm using it more lately where I have to boot the machine from scratch. In this case I face a rather long delay once or possibly twice during boot. Basically, the boot scripts say the networking interfaces aren't turned on so it attempts to run dhcpd. I do not enable nor have I even added net.eth0 or net.wlan0 in rc-update. (I think that's correct, and it does work.) Anyway, I'm wondering if this delay is normal behavior for wicd? Everything works fine but I have to wait 30-60 second, once or twice, for dhcpd while booting. I suspect that's not necessary. Getting on the network once I'm up is reasonably fast. The only thing I found Googling delay wicd was people waiting 3 minutes to find wireless networks. I don't have that problem. Not sure what data to provide other than the files below. Cheers, Mark slinky ~ # ls -al /etc/init.d/* | grep net lrwxrwxrwx 1 root root 6 Mar 19 2011 /etc/init.d/net.eth0 - net.lo -rwxr-xr-x 1 root root 16741 Feb 23 2012 /etc/init.d/net.lo lrwxrwxrwx 1 root root 6 Sep 11 2011 /etc/init.d/net.wlan0 - net.lo -rwxr-xr-x 1 root root 2219 Feb 23 2012 /etc/init.d/netmount -rwxr-xr-x 1 root root 6962 Feb 23 2012 /etc/init.d/network slinky ~ # slinky ~ # cat /etc/conf.d/net #config_eth0=192.168.1.55 netmask 255.255.255.0 #routes_eth0=default via 192.168.1.1 #modules=wpa_supplicant #config_wlan0=192.168.1.100 netmask 255.255.255.0 #routes_wlan0=default via 192.168.1.1 slinky ~ # slinky ~ # cat /etc/wicd/manager-settings.conf [Settings] backend = external wireless_interface = wlan0 wired_interface = eth0 wpa_driver = wext always_show_wired_interface = True use_global_dns = False global_dns_1 = None global_dns_2 = None global_dns_3 = None global_dns_dom = None global_search_dom = None auto_reconnect = True debug_mode = 0 wired_connect_mode = 1 signal_display_type = 0 should_verify_ap = 1 dhcp_client = 0 link_detect_tool = 0 flush_tool = 0 sudo_app = 0 prefer_wired = False main_width = 739 main_height = 755 netprop_width = 484 netprop_height = 600 pref_width = 561 pref_height = 540 show_never_connect = True slinky ~ #
Re: [gentoo-user] dhcp delays when booting (wicd)
Mark Knecht markkne...@gmail.com wrote: Hi, I've been using wicd for quite awhile on my laptop and it works fine with both wired and wireless interfaces. However I'm using it more lately where I have to boot the machine from scratch. In this case I face a rather long delay once or possibly twice during boot. Basically, the boot scripts say the networking interfaces aren't turned on so it attempts to run dhcpd. I do not enable nor have I even added net.eth0 or net.wlan0 in rc-update. (I think that's correct, and it does work.) Anyway, I'm wondering if this delay is normal behavior for wicd? Everything works fine but I have to wait 30-60 second, once or twice, for dhcpd while booting. I suspect that's not necessary. Getting on the network once I'm up is reasonably fast. The only thing I found Googling delay wicd was people waiting 3 minutes to find wireless networks. I don't have that problem. Not sure what data to provide other than the files below. Cheers, Mark slinky ~ # ls -al /etc/init.d/* | grep net lrwxrwxrwx 1 root root 6 Mar 19 2011 /etc/init.d/net.eth0 - net.lo -rwxr-xr-x 1 root root 16741 Feb 23 2012 /etc/init.d/net.lo lrwxrwxrwx 1 root root 6 Sep 11 2011 /etc/init.d/net.wlan0 - net.lo -rwxr-xr-x 1 root root 2219 Feb 23 2012 /etc/init.d/netmount -rwxr-xr-x 1 root root 6962 Feb 23 2012 /etc/init.d/network slinky ~ # slinky ~ # cat /etc/conf.d/net #config_eth0=192.168.1.55 netmask 255.255.255.0 #routes_eth0=default via 192.168.1.1 #modules=wpa_supplicant #config_wlan0=192.168.1.100 netmask 255.255.255.0 #routes_wlan0=default via 192.168.1.1 slinky ~ # slinky ~ # cat /etc/wicd/manager-settings.conf [Settings] backend = external wireless_interface = wlan0 wired_interface = eth0 wpa_driver = wext always_show_wired_interface = True use_global_dns = False global_dns_1 = None global_dns_2 = None global_dns_3 = None global_dns_dom = None global_search_dom = None auto_reconnect = True debug_mode = 0 wired_connect_mode = 1 signal_display_type = 0 should_verify_ap = 1 dhcp_client = 0 link_detect_tool = 0 flush_tool = 0 sudo_app = 0 prefer_wired = False main_width = 739 main_height = 755 netprop_width = 484 netprop_height = 600 pref_width = 561 pref_height = 540 show_never_connect = True slinky ~ # Mark. There is a setting with example on how to disable auto-start of the network services in /etc/rc.conf . I can't check for the actual syntax, but I think this is what you are looking for. -- Joost -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] heartbeat problem
There's already a tool to do exactly that: checkpath (see man 8 runscript), for example checkpath -d -m 0770 -o user:group /var/run/heartbeat, but apart from that, your fix seems correct. Regards, Luis signature.asc Description: PGP signature
Re: [gentoo-user] dhcp delays when booting (wicd)
On Tue, 16 Oct 2012 12:38:43 -0700, Mark Knecht wrote: I've been using wicd for quite awhile on my laptop and it works fine with both wired and wireless interfaces. However I'm using it more lately where I have to boot the machine from scratch. In this case I face a rather long delay once or possibly twice during boot. Basically, the boot scripts say the networking interfaces aren't turned on so it attempts to run dhcpd. I do not enable nor have I even added net.eth0 or net.wlan0 in rc-update. (I think that's correct, and it does work.) Do you have this in /etc/rc.conf? rc_hotplug=!net.* Without it, hotplug will try to start the network even if the net.* scripts aren't in your runlevel. -- Neil Bothwick Top Oxymorons Number 41: Good grief signature.asc Description: PGP signature
[gentoo-user] macbook air external monitor causes black screen
Here is a wierd one, I am using macbook air (mid 2012 - 5,2) and its working acceptably finally (still some things to tune), with only one serious problem. If I attach an external monitor/beamer/projector it works as expected, after which I disconnect the cable (one of those display port adaptors), set the resolution back to auto using the LXDE menu and suspend to ram ... back at the office I resume the machine and start using it. If I leave it, it then blanks the screen and nothing Ive tried so far will reactivate it (backlight off) except pressing the power button ... whereupon the screen flicks on, and the machine shuts down - useful! I have not seen it actually blanking so cant see if its screensaver related or not. Its only after I attach/detach an external monitor that this occurs - otherwise no problem. Its a reasonably fresh amd64 install (copied from a dell server I have, and reconfigured), LXDE desktop and xscreensaver, no xinerama, xorg.conf only contains settings for mtouch. Has anyone hints as to where to look? BillK
Re: [gentoo-user] dhcp delays when booting (wicd)
On Tue, Oct 16, 2012 at 2:08 PM, Neil Bothwick n...@digimed.co.uk wrote: On Tue, 16 Oct 2012 12:38:43 -0700, Mark Knecht wrote: I've been using wicd for quite awhile on my laptop and it works fine with both wired and wireless interfaces. However I'm using it more lately where I have to boot the machine from scratch. In this case I face a rather long delay once or possibly twice during boot. Basically, the boot scripts say the networking interfaces aren't turned on so it attempts to run dhcpd. I do not enable nor have I even added net.eth0 or net.wlan0 in rc-update. (I think that's correct, and it does work.) Do you have this in /etc/rc.conf? rc_hotplug=!net.* Without it, hotplug will try to start the network even if the net.* scripts aren't in your runlevel. -- Neil Bothwick Top Oxymorons Number 41: Good grief Ah, is that the one Joost was talking about?!@? Made the change and now I'm booting quickly and networking (wireless anyway as I'm not near a wired connector right now) is fine when I log into KDE. Thanks to both you and Joost. Cheers, Mark
[gentoo-user] sys-boot/plymouth compilation failure
Dear list, I think I've found a bug, so I decided to report it here https://bugs.gentoo.org/show_bug.cgi?id=437728 . But, till the guys solve it, can you think anything I can try? Any of you can compile without problem? thank you, -- João de Matos Linux User #461527
Re: [gentoo-user] dhcp delays when booting (wicd)
Mark Knecht markkne...@gmail.com wrote: On Tue, Oct 16, 2012 at 2:08 PM, Neil Bothwick n...@digimed.co.uk wrote: On Tue, 16 Oct 2012 12:38:43 -0700, Mark Knecht wrote: I've been using wicd for quite awhile on my laptop and it works fine with both wired and wireless interfaces. However I'm using it more lately where I have to boot the machine from scratch. In this case I face a rather long delay once or possibly twice during boot. Basically, the boot scripts say the networking interfaces aren't turned on so it attempts to run dhcpd. I do not enable nor have I even added net.eth0 or net.wlan0 in rc-update. (I think that's correct, and it does work.) Do you have this in /etc/rc.conf? rc_hotplug=!net.* Without it, hotplug will try to start the network even if the net.* scripts aren't in your runlevel. -- Neil Bothwick Top Oxymorons Number 41: Good grief Ah, is that the one Joost was talking about?!@? Made the change and now I'm booting quickly and networking (wireless anyway as I'm not near a wired connector right now) is fine when I log into KDE. Thanks to both you and Joost. Cheers, Mark Mark. Yes. That's the one. Don't have the file on the mobile phone... Glad to hear you got it working. -- Joost -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
