switching to kubunto first impressions and few questions

[Emanoil Kotsev]

Hi, thank you for answering

--- On Fri, 9/26/08, Derek Broughton <news at pointerstop.ca> wrote:

> Emanoil Kotsev wrote:
> 
> > 1) dhclient
> > 
> > When I did network restart
> >     sudo /etc/init.d/networking restart
> > it said permission denied on
> /lib/dhcp3-client/call-dhclient-script.
> > 
> > I did ls -al /lib/dhcp3-client/call-dhclient-script
> > 
> > -rwsr-xr-- 1 root ssh 2960 2008-04-02 15:38
> > /lib/dhcp3-client/call-dhclient-script
> > 
> > Why the h* it has permissions root:ssh
> 
> You didn't actually install Kubuntu, fresh, did you? 
> You've upgraded from
> Debian, which is likely to result in a fair number of
> problems. 

False asumption - I did install clean kubuntu. I just said that I'm switching to kubuntu from debian - keeping my home-data and stuff - but I _did_ clean install

> Particularly, your /etc/shadow and /etc/passwd and probably
> /etc/group
> & /etc/gpasswd are out of sync.

this is based on the wrong assumption made above. It's there for not true.

> 
> > 2. wlan
> > After installation wireless worked fine. I've
> installed a bunch of
> > programs and now I can not activate the wlan trough
> knetworkmanager. Why?
> >
> > I was previously able to switch on/off by the hardware
> kill switch. What
> > should I do to make it work I've been using the
> old ipw3945 with ipw3945d,
> > I don't know much about iwl*. I read that few
> problems regarding this on
> > dell notebooks will be solved in 2.6.27.
> > 
> > When I use the software or hardware kill switch (and I
> do this because I
> > don't like wave transmissions around me) I have
> permanent syslog messages
> > like
> > 
> > Sep 23 22:14:01 maistor kernel: iwl3945: Radio
> disabled by HW RF Kill
> > switch Sep 23 22:14:01 maistor kernel: ACPI: PCI
> interrupt for device
> > 0000:0c:00.0 disabled
> > 
> > It seems that there is link missing to ACPI. How can I
> get rid of it?
> 
> No, it says that you disabled the device.  That seems
> perfectly reasonable.

Hm, ok, but it's flooding my syslog. I don't want to see there this - may be I should reconfigure syslogd, though.
What I mean is that the system should be knowing that I've disabled the device on purpose.

>  
> > There are few systems that seem not to work smoothly
> together like
> > dbus/hal/acpi/ifplug(udev). So I  think I am
> over-challenged with this.
> > Any help is appreciated.
> > 
> > 3) shutdown/reboot
> > When I reboot the system says sending TERM/KILL signal
> and it stays so for
> > about a minute. Why?
> 
> Incorrectly written DSDT in the BIOS.  Sorry, I don't
> recall the fix but
> it's an ACPI parameter in the grub boot settings.

What is to be done? Which paramter?

> 
> > 4) dual monitor layout
> > Appart the fact that intel 945 has a stupid 3d
> limitation of screen size
> > and when using two monitors there is no 3d
> acceleration I observed
> > following. 
> 
> Cheap hardware gives cheap results.  I can live with those
> limitations.  I
> don't even know if the Intel graphics can do that in
> Vista, but certainly
> not in X.

Well, where is this magic kde setting written, so that new user gets monitors automatically configured and old users do not?

> 
> > Who is responsible to extend the functionallity of the
> krandrtray, so a
> > user can say use two desktops - I'm really missing
> it. Also a feature for
> > screen A left/right of screen B would be fine. Screen
> here is monitor of
> > course.
> 
> I have that with my laptop and a 945 graphics card.  System
> Settings -
> Monitor and Display.

How do you proceed there? I'm command line user and do it with xrandr as I said, what I'm looking for is a setting to make it permanentloy working.

Thanks for the response again.

I would be glad to have definite answers that can help me fix the things I don't like

regards