Re: Happy 2010++

Re: LXDE packets

It adding on ~/.xinit.rc this lines:

## test for an existing bus daemon, just to be safe
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval "$(dbus-launch --sh-syntax --exit-with-session)"
fi

May be it's not useful, but i told, sometimes findes, that d-bus
daemon for current user not start :( That's sounding imposible, but
i'm seen it.

1 января 2011 г. 2:50 пользователь Ahmad Samir
<ahmadsamir3891 <at> gmail.com> написал:
> 2011/1/1 Александр Казанцев <kazancas <at> mandriva.ru>:
>> Ahmad thanks.  <at>  is not needed :) But for xinitrc_dbus - on 2010.1
>> sometimes dbus is stoped - it's my bad practice. May be in 2011 is not
>> useful, but in 2010.1/2 this script works fine.
>>
>
> Where is xinitrc_dbus? I can't find it. What does it do exactly?
>
> If it launches a dbus session when you login then this is already done
> by the mandriva xinitrc scripts see: /etc/X11/xinit.d/30dbus ; and
> /usr/bin/startlxde checks if a dbus session is already started and
> launches one if not.
>
> --
> Ahmad Samir
>
>

--

-- 
С уважением руководитель образовательных программ Mandriva.Ru
(www.edumandriva.ru)
к.т.н., доцент Казанцев Александр Сергеевич

Re: LXDE packets

2011/1/1 Александр Казанцев <kazancas <at> mandriva.ru>:
> It adding on ~/.xinit.rc this lines:
>
> ## test for an existing bus daemon, just to be safe
> if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
> eval "$(dbus-launch --sh-syntax --exit-with-session)"
> fi
>
> May be it's not useful, but i told, sometimes findes, that d-bus
> daemon for current user not start :( That's sounding imposible, but
> i'm seen it.
>
>

IMHO, you should fix that installation, or use xinitrc_dbus as a local
hack for your installations, but it shouldn't be used by default for
all the mdv LXDE users out there.

(Again) a dbus session is launched correctly via the mdv xinitrc,
nothing else is needed. And /usr/bin/startlxde does check for dbus and
launch it if it's not initialised. xinitrc_dbus isn't useful here
AFAICS.

Just my 0.1 EURO worth.

--

-- 
Ahmad Samir

Re: LXDE packets

On 01/01/2011 01:55 PM, Ahmad Samir wrote:
> 2011/1/1 Александр Казанцев<kazancas <at> mandriva.ru>:
>> It adding on ~/.xinit.rc this lines:
>>
>> ## test for an existing bus daemon, just to be safe
>> if which dbus-launch>/dev/null&&  test -z "$DBUS_SESSION_BUS_ADDRESS"; then
>> eval "$(dbus-launch --sh-syntax --exit-with-session)"
>> fi
>>
>> May be it's not useful, but i told, sometimes findes, that d-bus
>> daemon for current user not start :( That's sounding imposible, but
>> i'm seen it.
>>
>>
>
> IMHO, you should fix that installation, or use xinitrc_dbus as a local
> hack for your installations, but it shouldn't be used by default for
> all the mdv LXDE users out there.
>
> (Again) a dbus session is launched correctly via the mdv xinitrc,
> nothing else is needed. And /usr/bin/startlxde does check for dbus and
> launch it if it's not initialised. xinitrc_dbus isn't useful here
> AFAICS.
>
> Just my 0.1 EURO worth.

Under 2010.1 I had intermittent problems with dbus.  It did not 
happen often, and I was never able to find even a clue as to what 
the problem was, but one did exist.

Searching alt.os.linux.mandriva for dbus and maybe d-bus over the 
past year should turn up a fair number of posts attesting to such 
problems.

If it is critical that dbus is running, a check to make sure is 
in order.

Cheers!

jim b.

--

-- 
UNIX is not user unfriendly; it merely
      expects users to be computer-friendly.

Re: LXDE packets

2011/1/1 Jim Beard <jdbeard <at> patriot.net>:
> On 01/01/2011 01:55 PM, Ahmad Samir wrote:
>>
>> 2011/1/1 Александр Казанцев<kazancas <at> mandriva.ru>:
>>>
>>> It adding on ~/.xinit.rc this lines:
>>>
>>> ## test for an existing bus daemon, just to be safe
>>> if which dbus-launch>/dev/null&&  test -z "$DBUS_SESSION_BUS_ADDRESS";
>>> then
>>> eval "$(dbus-launch --sh-syntax --exit-with-session)"
>>> fi
>>>
>>> May be it's not useful, but i told, sometimes findes, that d-bus
>>> daemon for current user not start :( That's sounding imposible, but
>>> i'm seen it.
>>>
>>>
>>
>> IMHO, you should fix that installation, or use xinitrc_dbus as a local
>> hack for your installations, but it shouldn't be used by default for
>> all the mdv LXDE users out there.
>>
>> (Again) a dbus session is launched correctly via the mdv xinitrc,
>> nothing else is needed. And /usr/bin/startlxde does check for dbus and
>> launch it if it's not initialised. xinitrc_dbus isn't useful here
>> AFAICS.
>>
>> Just my 0.1 EURO worth.
>
> Under 2010.1 I had intermittent problems with dbus.  It did not happen
> often, and I was never able to find even a clue as to what the problem was,
> but one did exist.
>
> Searching alt.os.linux.mandriva for dbus and maybe d-bus over the past year
> should turn up a fair number of posts attesting to such problems.
>
> If it is critical that dbus is running, a check to make sure is in order.
>
> Cheers!
>
> jim b.
>
> --
> UNIX is not user unfriendly; it merely
>     expects users to be computer-friendly.
>

I've wrote the same thing three separate times, I don't think a fourth
time will do any good...  :)

It's not ultimately my decision, I am not the distro manager nor LXDE
maintainer, so I can just go back to the audience stands and see how
this unfolds.

--

-- 
Ahmad Samir

Re: Linux issues with WD 'green drives. was: Re: problems using hd with sectors of 4096 bytes ?

On 30 December 2010 14:54, Morgoth Evil <morgoth.evil <at> gmail.com> wrote:
>  Hi.
> Mandriva still can't handle this type of disks. Mdv installer doesn't align
> partitions so performance of disk is decreased.
> Solution to solved this problem is to create partitions with parted and
> "--align optimal" option and then use this partition for mdv.
> I think that 1TB drivers will be more common and Mandriva should handle
> those disks with proper align.
> Is it possible with diskdrake ?

Patching is needed...

Re: Where do Cooker <-> SELinux meet-up?

On 29 December 2010 00:18, Per Øyvind Karlsen <peroyvind <at> mandriva.org> wrote:
>> Apologies for not knowing an issue that has likely been discussed.
>>
>> Where do Mandriva Cooker <-> SELinux meet up?
> There's never been a plan of meeting up yet AFAIK, we've went from
> RSBAC to AppArmor and then landed on Tomoyo since 2010.0.

The reality is : we never enable any of those technology and never
provide configuration.
Basically we're naked...

>>> I'm just looking for a pointer to historical info, not advocating
>>> SELinux or anything else. SELinux _IS_ here to stay afaict even
>>> though SELinux is perhaps still not a useful feature for most desktops.
> I guess the complexity of SELinux scared us away quite early on, leaving us too
> comfortable chasing the alternatives since..
> I'm feeling warm and fuzzy enough inside about it myself though not
> having to care.. ;)

There was political opposition from management at that time.

Too bad we never jumped in the selinux wagoon.

Amarok fails to start since recent updates

[rfox <at> foxbase cooker]$ amarok
KGlobal::locale::Warning your global KLocale is being recreated with a
valid main component instead of a fake component, this usually means you
tried to call i18n related functions before your main component was
created. You should not do that since it most likely will not work 
amarok(16283)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to
open ksycoca from "/var/tmp/kdecache-rfox/ksycoca4"
amarok(16283) Phonon::KdePlatformPlugin::createBackend: using backend:
"GStreamer"
unnamed app(16282): Communication problem with  "amarok" , it probably
crashed. 
Error message was:  "org.freedesktop.DBus.Error.ServiceUnknown" : " "The
name org.kde.amarok was not provided by any .service files" " 

Happy to create a bug report if someone would confirm it for me . .

HAPPY NEW YEAR TO ALL!

Thx,
R.Fox

Re: Mandriva 2010.2

On 28 December 2010 16:19, Colin Guthrie <cguthrie <at> mandriva.org> wrote:
> The symlink is just to allow certain automatic things inside URPMI work
> without breaking thinks totally (as the version is set to 2010.2, it
> looks for a folder of that name).
>
> As the ISOs contained rolled up versions of the RPMs from updates,
> installing via ISO will result in an up-to-date system, but installing
> directly from FTP or similar will still result in old RPMs being
> installed from main/release and later updated to main/updates

Wrong.

> (unless > the FTP install configures update sources immediately, in which
> case it makes no difference).

Of course the network install make use of both */release and */updates!
For years.

Re: Amarok fails to start since recent updates

Hi Robert,

On Monday 03 Jan 2011 13:03:03 Robert Fox wrote:
> [rfox <at> foxbase cooker]$ amarok
> KGlobal::locale::Warning your global KLocale is being recreated with a
> valid main component instead of a fake component, this usually means you
> tried to call i18n related functions before your main component was
> created. You should not do that since it most likely will not work
> amarok(16283)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to
> open ksycoca from "/var/tmp/kdecache-rfox/ksycoca4"
> amarok(16283) Phonon::KdePlatformPlugin::createBackend: using backend:
> "GStreamer"
> unnamed app(16282): Communication problem with  "amarok" , it probably
> crashed.
> Error message was:  "org.freedesktop.DBus.Error.ServiceUnknown" : " "The
> name org.kde.amarok was not provided by any .service files" "
> 
> Happy to create a bug report if someone would confirm it for me . .
> 

This is a known problem that was previously reported to this list here:

http://lists.mandriva.com/cooker/2010-12/msg00451.php

Ahmad refered us to this upstream bug:

https://bugs.kde.org/show_bug.cgi?id=252424

> HAPPY NEW YEAR TO ALL!
> 

Happy new year.

Regards,

	Shlomi Fish

--

-- 
-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
http://www.shlomifish.org/humour/ways_to_do_it.html

Chuck Norris can make the statement "This statement is false" a true one.

Please reply to list if it's a mailing list post - http://shlom.in/reply .