root authorization to mount CD-ROM, USB-stick and shutdown and no SB Audigy Alsa Mixer in SuSE12.3

Hi!

I’ve noticed a strange “instability” in openSuse 12.3_x86-64. A fresh install on a some six year old stationary Desktop with AMD Athlon 3000+ on A8NSLI DeLuxe Mobo.
(Creative Audigy 2 PCI).

My first 8-10 bootups after the installation I could get no sound though every snd-module were at hand and active, the Alsa Mixer just found a “Dummy Output”, the system demanded root authorization for mounting an USB-stick or even a CD-ROM and when I finally tried to shut down the system demanded root authorization for letting me.

I looked for permission problems without finding any. After the first some 10 bootups the problems suddenly disappeared, all worked as it should, sound, mixer no root authorization for this and that. -Until today? Now it’s all back and seems stable in that way!

I’ve never met anything like it in any OpenSuse since 8.2. On this same machine I’ve been installing OpenSuse since 11.1. And today parallell with OpenSuse 12.3 I have got Windows 7, OpenSuse 12.2_x86-64 and Slackware 14.0_x86-64 installed, all of them working well.

Does anyone have a clue or can help me search for the problem and possibly solve it?

Regards
Lars

Do you have a common home partition? Did you do the fresh install and keep an old home (KDE?)

Do you have a common home partition? Did you do the fresh install and keep an old home (KDE?)

No on both. Sorry I didn’t mention: It’s a complete fresh install with both Gnome and Xfce Desktop environments, share new home with no one, and all root directories are on the same partition.
I remember some conflicts between Gnome and Xfce in 12.1 but none of this kind! All gone in 12.2.

-The only change I had made before the return of these “permission problems” was that I added my user to dialout group. I’m not at all certain that this anything to do with the problem-return because they didn’t return immediately, but a couple of hours later. It remained after the first 2-4 boots today, but disapperade the 5th?
Today there were 2 yast2 security bugfixes concerning group encryption and last login (or similar). Thought there was a chance it had anything to do with my problems, installed it and the problems were back next boot after. I’m certain the update had nothing to do with that since the problems “were there” immediately after my installation and it took a considerable amount of reboots during the first two days (but only one single update: of Firefox and Thunderbird) before the problems without explanation disapperared

…till yesterday evening…

Additionally: The described problems seem to be affected if I change my users groups (using Yast2), but not in a stable way.

If the root-authorization problem occurs after a boot-up, I seem to be able to get rid of it logging out and the in again? I’m not certain though…

The replies and suggestions really haven’t been overwhelming;)
The updates during these last two weeks has not affected the root-authorization-demands in any way, though there was one yesterday concerning udisk.

Perhaps I’ve found a solution to both the sound problems and the demand for root-authorization for mounting USB, CD-ROM and Shutting down?
**Sound: **After I added my user to audio group the problems concerning sound, sound card and Alsa Mixer seem to be gone.

**root-authorization-demand: **I looked in the Debian-side of the world and found Ubuntu and Mint (perhaps even Archlinux?) have had similiar problems during the last 2-3 years, perhaps related mostly to Xfce(?). -The solutions described concern the /usr/share/polkit-1/actions/.

USB and CD-ROM et c: In org.freedesktop.udisk2.policy Section: <action id=“org.freedesktop.udisks2.filesystem-mount-other-seat”>
Change:
<allow_active>auth_admin_keep</allow_active>
to:
<allow_active>yes</allow_active>

Shutting down: In org.freedesktop.consolekit.policy Section: <action id=“org.freedesktop.consolekit.system.stop-multiple-users”>
Change:
<allow_active>auth_admin_keep</allow_active>
to:
<allow_active>yes</allow_active>

After these changes the demands for root authorizations for mounting ordinary USB-units CD-ROM and shutting down seem to have disappeared in a stable way. (If not I’ll get back and report it.)

-The way to solve this seeem to indicate that the OpenSuse 12.3 Xfce might “experience” one ordinary user + root as** 2** users of the same system and want to prevent changing the system when more than one are logged in?

As I’ve written before: I’ve since v. 8.2 never experienced anything similar in OpenSuse!

Hi,

I had the same problems after upgrading from 12.2 to 12.3. No working sound, mounting of external drives in kde resulted in error messages, no cd nor cdrw drive recognized in k3b and so on.

Adding my user to the audio group enabled sound again. Adding my user to cdrom group made k3b recognizing my cdrw drive. BUT: This only helps your particular user and will not work for other users you might have adminstrated.

The following (found it in Re: [opensuse] OpenSuse 12.3: cannot mount USB key as user) was the solution for me:

Perform as user (not root):
$ loginctl --no-pager list-sessions
Your session (and maybe some other sessions, too) with your username should be listed.

$ loginctl --no-pager show-session -p Active $XDG_SESSION_ID
Your session should be Active.

If both commands don’t show the desired result, check /etc/pam.d/common-session for a line containing “session optional pam_systemd.so”. If it is missing, just add it. After that remove your username from the audio and cdrom entries in /etc/group, if you changed that. Revert any other changes you made to udisks or ConsoleKit policy files.

Reboot and enjoy.

Since adding that line

  • sound is working again (even with pulseaudio enabled, which never worked before)
  • mounting external drives or USB sticks is working again
  • k3b recognizes my dvd burner

So you might just try it.

Have fun,
Andreas

Thank you Andreas! Your solution seems elegant!

The question remains **why on earth we have to do this?

**Best regards

Lars

You should not. pam_systemd should be added automatically when systemd is installed. If it did not happen, there is bug somewhere and no amount of bold font is going to fix it. If you had this problem and still have logs from installation time available, open bug report.

Thank you arvidjaar! Even though i consider myself a fairly good-enough Suse-user I’m not all that skilled. I never studied the installation logs or know where to find them?
When I looked in /var/log I found a compressed file: messages-20130320.xz that contained logs from installation day 20130315 up to 20130320. Could that be the one you mean? I should guess not, because the first logged event is from about 2 hours after the installation, i e first boot.

They should be under /var/log/YaST2. There is command /sbin/save_y2logs that automatically collects them.

On 2013-03-29 11:16, arvidjaar wrote:
>
> Larsed;2542452 Wrote:
>> I never studied the installation logs or know where to find them?
>
> They should be under /var/log/YaST2. There is command /sbin/save_y2logs
> that automatically collects them.

Yes. You just open a bug report and add that archive, if not, they’ll
ask for it. If they take a month or two to respond, the archive will be
obsolete and useless, so attach it in advance.

openSUSE:Report a YaST bug


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Hi,

I filed a bug report “pam_systemd.so missing in common-session after zypper dup to to 12.3” (https://bugzilla.novell.com/show_bug.cgi?id=812462)

Bye,
Andreas

Thank you arvidjaar and robin_listas for your descriptions of howto! and Josh as well for your filed report.

Perhaps I should try to formulate a bug report myself since my installation differed from Josh’s being a fresh install.

A memory makes me hesitate though, I once filed a bugreport to Debian. And my mailaccount got so spammed down after that report so I finally had to close it! I think it had nothing to do with the Debian-community but perhaps the reporters mailadresses were published in some website or something like that? Anyway, it was quite inconvenient since it was my personal adress…

Best regards

Lars

Before I filed any bug report claiming that I knew the cause of my problem I decided to look in to the suggestion made by Josh385/Andreas:

Before I did any change except removing my user from the ‘audio’ group and returning to the initial setup of /usr/share/polkit-1/actions/ and rebooting
-I found /lib64/security/pam_systemd.so (as I perhaps misunderstood arvidjar, the module was not missing in my install)
-I found the line “session optional pam_systemd.so” in /etc/pam.d/common-session → common-session-pc
-I performed Josh385’s suggestion:
$ loginctl --no-pager list-sessions
SESSION UID USER SEAT
2 1000 <myuser> seat0
$ loginctl --no-pager show-session -p Active $XDG_SESSION_ID
Active=yes

Rebooted and all problems described in my initial thread description returned.
Same for the next 5 boots.

After that I returned to my own solution (above).

It seems that the problems described by Josh385/Andreas have another cause than mine? Even if they “on the surface” looked alike.

Now, if you excuse, I feel I must make a comment concerning OpenSuse. I’ve been thinking about it for some years now but never said it.
I think I should rather say it before I definitely abandon OpenSuse than just do it silently. And this thread is a good opportunity as any!

First I must state that I indeed appreciate the tremendous work of the developers to keep OpenSuse as much ‘at the edge’ as possible. And this in a furious pace. And in no meaning I intend to be offensive!

With so much said: I’ve been a dedicated OpenSuse user since version 8. I really have liked it, it’s stability and it’s possibilitiy to either use configurations in the “graphical” YaST2 or from console. But I’ve wondered about the release “speed” during the last years? Especially as I’ve found the released versions after 10.3 prematurely released. In fact, after 10.3 the first version I’ve found usable from start is OpenSuse12.2 (with 11.2 as a possible exception).

Why not slow down the release frequency a bit to the benefit of more mature, less buggy releases?

Now I hope no one gets offended by this! I wouldn’t have written this if I didn’t really like OpenSuse and wanted to stay with it!

Again, thank you arvidjaar robin_listas and Josh385 for your kind interest, suggestions and help with my initial sound-root-authorization problem!

Regards!

Lars

On 03/30/2013 09:56 AM, Larsed wrote:
> Why not slow down the release frequency a bit to the benefit of more
> mature, less buggy releases?

i would vote for that…but, the only folks who can vote must apply
to be a member of the community, provide details of why they should
be accepted, and then finally be approved in some totally closed
and secret process (conducted, i hear, in slow motion) by the
“openSUSE Membership officials team”…

http://en.opensuse.org/openSUSE:Membership_officials


dd

On 2013-03-30 11:00, dd wrote:
> On 03/30/2013 09:56 AM, Larsed wrote:
>> Why not slow down the release frequency a bit to the benefit of more
>> mature, less buggy releases?
>
> i would vote for that…but, the only folks who can vote must apply to
> be a member of the community, provide details of why they should be
> accepted, and then finally be approved in some totally closed and
> secret process (conducted, i hear, in slow motion) by the “openSUSE
> Membership officials team”…

I would also vote for that… But as I happen to be a “member”, I can
tell you that we have no influence at all. We don’t vote on such things.

(I have in fact proposed such a slowdown more than once)

The last vote we were called to do was elect the board, last
November/December. And the previous vote was the same thing in 2011. We
don’t vote on anything, even less anything of importance.

The only thing we voted upon once, that I can remember, was the second
round that decided how the openSUSE releases were to be numbered. You
know: 12.1, 12.2, etc.

Right now, the board has proposed a new category of bugzillas with
automatically assigned major level: accessibility bugs (a11y). For
example, if the login screen doesn’t “speak”, a sight impaired person
can simply not even login. For him, that bug is a stop gag.

But the board has no power on that!

The board has simply asked, in public, that the developers, and
specifically SUSE, discuss and maybe implement that feature in bugzilla
and its processing.

It is actually SUSE who has the power of decision on the release cycle,
because it is they who pay and maintain the infrastructure, and pay the
majority of the developers that work full time or a major part of their
time, on openSUSE things.

Another type of example: systemd. Who decides that this goes into
openSUSE? I don’t know. Developers… as an abstract body. Even some
SUSE employees strongly object to it. Apparently no one wants to work or
subsidize work on the classic systemv that works fine, that is
understandable by everybody (sysadmins worldwide), etc, etc. We are
openSUSE are the guinea pigs suffering, er… using it. When it is
finally made then perhaps it will go into SLES. I guess.

The community has no power of decision at all on whether we want systemd
or systemv. We have not been asked to vote upon it. We are simply
opposed by facts: systemd is here because developers want it.

Their supporters say: who is going to support systemv? The obvious
answer is “the same people that are developing systemd”. But they do not
want to… so they don’t. They prefer a new toy.

There is no organized body that decides how openSUSE is going to be. No
board of direction. No decision voting. It is a bazaar… as long as it
is subsidizes or somebody does the work gratis.

So you see, some ramblings from an openSUSE member, that doesn’t know
what he is a member for. :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Well, I am astonished and glad!

…to have got that kind of replies from two persons I have learnt to respect very much! DenverD and robil_listas.

My very best regards
and Thanks!

Lars

One little detail though

Carlos, you wrote

It took me years to understand that the cooperation between Novel SuSE (System- und Software Entwicklung GmbH) had ended. In fact I still spell SuSE.
When you say SUSE, is it possibly the Novell business you mean?

Besides I absolutely agree with what you write about systemd:)!

Lars

On 2013-03-30 20:36, Larsed wrote:
>
> One little detail though

> It took me years to understand that the cooperation between Novel SuSE
> (System- und Software Entwicklung GmbH) had ended. In fact I still spell
> SuSE.

:-))

I have a black tee-shirt with SuSE on it :wink:

> When you say SUSE, is it possibly the Novell business you mean?

No, I mean SUSE, Novell is irrelevant on this now - or so they say.

Novell bought SUSE. Names were migrated, Novell employees suported
openSUSE, etc. Then Attachmate bought Novell. As I understand, what was
SUSE was to be separated from Novell and be called SUSE again.

I don’t really know what part Novell plays now. Everything related to
openSUSE should now come from SUSE, not Novell.

And all employees changed again their @novell addresses to @suse.

> Besides I absolutely agree with what you write about systemd:)!

We will be assimilated. Resistance is futile. >;-)


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)