Not sure, where or who to report this to; I'm sure this would concern
the seperate /usr filesystem loving types.
kde4-filesystem-4.6.4-4.1.i586
kdm-4.6.4-5.1.i586
polkit-0.101-7.1.i586
After returning to Tumbleweed PC, running a KDE desktop (but with X
screen saver) I was surprised to see a pop-up; which wished me to
authenticate as root, via entering the root password into a posh
official looking dialogue :
System policies prevent you from getting the brighness level.
An application is attempting to perform an action that requires
privileges. Authentication is req'd ..
Password for root:
[ ] Remember authorization
Application :
Action: Get brighness
Vendor: KDE
polkit.subject.pid: 3226
polkit.caller.pid: 3971
Details OK Cancel
------
ladm@oak:~> ps aux |grep 3971
root 3971 0.0 0.7 38152 7428 ? Sl 11:37 0:00
/usr/lib/kde4/libexec/backlighthelper
Now whilst this is obviously a bug, it concerns me that polkit & KDE
even have it implemented to request Authentication by root password
like this. This should be handled by an error pop up, if the
privileges of a "helper" program are insufficient for it to operate,
configuration error.
OK this reminds me of Windows UAC where ironically the screen dims,
but far better the end user clicks to permit application to proceed,
rather than authenticate to some random bit of software that throws up
a pop up.
We have signed rpm's, surely if KDE4 backlighthelper needs the
capability there's better ways (like checking signature) of it's
legitimacy. Whilst su or kdesu, do require authentication of user as
"root" to run programs that require root privileges & change the
computer configuration; that authentication is checking who you are,
not a "please give me the root password" so I can get elevated
privileges.
Design Error?
Asking a user to enter root password to pop-ups at unpredictable
times, would be a bad habit to get into! Not to mention the end users
would hate it even more than Windows ppl dislike the confirmation
clicks of UAC.
A confirmation requestion of a granted might be reasonable, but then
the user needs better information than the 'caller pid' to go on.
Hopefully there's a way to disable these pop ups, they're IMO a
mis-feature.
Rob
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Kernel's been updated, but the preload-kmp packages for i586 don't
seem to be (x86_64 looks OK) which causes zypper dup to "confusingly"
want to downgrade to 11.4 with vendor change as 2.6.39.1-33 kernels
are no longer present.
x86_64 - As expected
kernel-default-2.6.39.2-34.1.x86_64.rpm
28-Jun-2011 20:58 36M
kernel-desktop-2.6.39.2-34.1.x86_64.rpm
28-Jun-2011 20:03 37M
preload-kmp-default-1.2_k2.6.39.2_34-67.29.x86_64.rpm
28-Jun-2011 21:27 39K
preload-kmp-desktop-1.2_k2.6.39.2_34-67.29.x86_64.rpm
28-Jun-2011 21:27 40K
i586 - Not
kernel-default-2.6.39.2-34.1.i586.rpm
28-Jun-2011 20:46 35M
kernel-desktop-2.6.39.2-34.1.i586.rpm
28-Jun-2011 19:42 36M
preload-kmp-default-1.2_k2.6.39.1_33-67.28.i586.rpm
27-Jun-2011 19:49 40K
preload-kmp-desktop-1.2_k2.6.39.1_33-67.28.i586.rpm
27-Jun-2011 19:49 40K
I presume this is just a slip & the preload-kmp's on i586 fell into
the bit bucket.
Regards Rob
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi list,
I would like to introduce vorbisgain to factory. Vorbisgain allows an enduser
to have the gain value for a vorbis file calculated so that media players like
Amarok can automatically adjust the playback volume. The package has been
available for quite some time in Contrib and is now in multimedia:apps.
The only drawback of the package is that does not really have an active
upstream as it is feature complete. It is however a small program and I have
maintained it in Contrib without any issues for several releases now.
Below you'll find some additional information.
Regards,
Matthias
What is vorbisgain?
===========
VorbisGain is a utility that uses a psychoacoustic method to correct the
volume of an Ogg Vorbis file to a predefined standardized loudness.
It is meant as a replacement for the normalization that is commonly used
before encoding. Although normalization will ensure that each song has the
same peak volume, this unfortunately does not say anything about the apparent
loudness of the music, with the end result being that many normalized files
still don't sound equally loud. VorbisGain uses psychoacoustics to address
this deficiency. Moreover, unlike normalization, it's a lossless procedure
which works by adding tags to the file. Additionally, it will add hints that
can be used to prevent clipping on playback. It is based upon the ReplayGain
technology.
The end result is that playback is both more convenient and of higher quality
compared to a non-VorbisGain'ed file.
License
=====
LGPL 2.1
Homepage
======
http://sjeng.org/vorbisgain.html
Authors
=====
Gian-Carlo Pascutto and Magnus Holmgren
--
Matthias Bach
www.marix.org
„Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig
über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke
Hi all!
In 3 days, the voting for the openSUSE strategy has to be done. We've
had only about 1/5th of our members vote and that's not a lot. Now I
know we don't have any way to check if members are still very active so
maybe most are not. But if you are, please, vote!
Find the last article from news.o.o here: http://bit.ly/iB2Dzh
And a direct link to voting: http://bit.ly/kZaAC2
You just have to log in with your connect account and VOTE!
For 2 years people have been asking 'what does openSUSE want'. We tried
to put that in the strategy. Ok, it is not perfect, but that is because
we didn't appoint someone to tell us what we want but because we
*asked*. And then, yes, you get compromise. Anything bad in there is
there either because you didn't speak up (tssss bad bad) or the majority
disagreed with you.
And that is how it SHOULD work. It is what sets us apart from the other
major distributions - we have no dictator or 'steering group'. But
democracy also comes with responsibilities - voting!
Now, enact your democratic duty, here: http://bit.ly/kZaAC2
Cheers,
Jos
Hi all,
I sent the groff-1.21 update together with SUSEConfig.groff removal as
requested by FATE#311297 [1]. That means the value /etc/papersize will
no longer be rewritten on change of RC_LC_PAPER in
/etc/sysconfig/language. This makes UPDATE_GROFF_CONF and GROFF_PAGESIZE
variables in /etc/sysconfig/suseconfig pointless, which is not a problem
as they are now obsoleted, so removal is just a next step.
Users wants to have a letter as default papersize for groff would just
type
echo "letter" > /etc/papersize
For details, please consult man 5 groff_font and 'papersize string'
definition.
[1] https://features.opensuse.org/311297
Regards
Michal Vyskocil
-------- Original Message --------
Subject: [opensuse-factory] Latest Nvidia blob installation appears error free
but Nvidia module does not load in openSUSE 12.1 M2 --64-bit
Date: Mon, 27 Jun 2011 15:59:28 -0400
From: Roman Bysh <rb03884(a)gmail.com>
To: opensuse-factory(a)opensuse.org
On 06/27/2011 07:24 AM, Bruno Friedmann wrote:
> On 06/27/2011 02:02 AM, Sid Boyce wrote:
>> On 25/06/11 18:51, Cristian Rodríguez wrote:
>>> El 24/06/11 23:05, Roman Bysh escribió:
>>>> Hello all,
>>>>
>>>> I installed the latest Nvidia blob on openSUSE 12.1 M2. However, the
>>>> "nvidia module" fails to load.
>>>>
>>>> I installed using the x86_64 DVD. I have attached Xorg.0.log
>>>>
>>>> Has anyone else experienced this with the 64-bit installation?
>>>>
>>>> Cheers!
>>>>
>>>> Roman
>>>
>>> You have to blacklist the NOUVEAU driver first.
>>>
>> The newer NVidia drivers include a script to do that - the latest is
>> 275.09.07, as far as I can see the latest openSUSE version is 270.41. May
>> be it's time to upgrade and lay the problem to rest. # cat
>> /usr/lib/nvidia/pre-install #!/bin/sh
>>
>> echo "blacklist nouveau" > /etc/modprobe.d/nvidia.conf
>>
>> # recreate initrd without KMS, if the use of KMS is enabled in initrd if
>> grep -q NO_KMS_IN_INITRD=\"no\" /etc/sysconfig/kernel; then sed -i
>> 's/NO_KMS_IN_INITRD.*/NO_KMS_IN_INITRD="yes"/g' /etc/sysconfig/kernel
>> mkinitrd fi
>>
>> Regards Sid.
>>
>
> Unfortunately, for factory actually the NO_KMS_IN_INITRD has become
> KMS_IN_INITRD with a switch of the value. before yes, now = no
>
> Roman, after an installation, the safest way to get nvidia blob installed is
> to reboot adding on grub line nomodset blacklist=nouveau 3 Then process to
> the nvidia_installer....sh and reboot a new time.
>
>
Thanks guys but....
I discovered on my 64-bit machine that the kernel sources were slightly different.
Maybe slightly incomplete to previous versions of < or = openSUSE 11.3.
However, the installation left me with an "unloaded nvidia module" after the reboot.
This was after blacklisting nouveau with:
echo "blacklist nouveau >> /etc/modprobe.d/50-blacklist.conf
The only things that saved me was:
<snip------------------------snip>
su -
cd /usr/src/linux
make oldconfig
make prepare
init 5
<snip------------------------snip>
I found that "init 5" finally took me to a desktop that supported openGL &
But why is this kernel so different from others. Is there a missing file in
kernel-source?
--
Cheers!
Roman
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi all!
In 3 days, the voting for the openSUSE strategy has to be done. We've
had only about 1/5th of our members vote and that's not a lot. Now I
know we don't have any way to check if members are still very active so
maybe most are not. But if you are, please, vote!
Find the last article from news.o.o here: http://bit.ly/iB2Dzh
And a direct link to voting: http://bit.ly/kZaAC2
You just have to log in with your connect account and VOTE!
For 2 years people have been asking 'what does openSUSE want'. We tried
to put that in the strategy. Ok, it is not perfect, but that is because
we didn't appoint someone to tell us what we want but because we
*asked*. And then, yes, you get compromise. Anything bad in there is
there either because you didn't speak up (tssss bad bad) or the majority
disagreed with you.
And that is how it SHOULD work. It is what sets us apart from the other
major distributions - we have no dictator or 'steering group'. But
democracy also comes with responsibilities - voting!
Now, enact your democratic duty, here: http://bit.ly/kZaAC2
Cheers,
Jos
Hello all,
I installed the latest Nvidia blob on openSUSE 12.1 M2.
However, the "nvidia module" fails to load.
I installed using the x86_64 DVD.
I have attached Xorg.0.log
Has anyone else experienced this with the 64-bit installation?
Cheers!
Roman
Hi All;
After installing OS 12.1-M2 today, I find that krusader won't start in root
mode. The cli message says $(dbus-launch) must be exported first.
This was posted to bugzilla as Bug 702247 - in OS 12.1M2, root mode krusader
fails to load with error about exporting $(dbus-launch).
Tom
--
Tom Taylor - retired penguin
openSuSE 11.3 x86_64 openSUSE 11.4 x86_64 openSUSE 12.1-M2
KDE 4.4.4, FF 3.6.8 KDE 4.6.00, FF 4.0 KDE 4.6.1, FF 4.0.1
claws-mail 3.7.9
registered linux user 263467
linxt-At-comcast-DoT-net
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
The next Mesa release (7.11) is expected in July.
This release will require LLVM to build r300g driver : some r300 supported gfx card did not ship with hardware TnL functionnalities, so these functionnalities are emulated by cpu.
From the 7.11 release, this emulation will require LLVM (and thus, is likely to show performance improvement over Mesa 7.10.x)
As llvm is now part of standard packages list, and is a build dependency of future Mesa, might it be possible to enable the llvm-pipe driver instead of swrast ?
This driver (which enables OpenGL feature on system which have no supported 3D acceleration device) is faster than the latter and should not bring major regression.
At least having it enabled at the Factory stage would allow to test its reliability before release.
Regards,
Vincent
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org