Re: The continuous crippling of Fedora LiveCDs by removing usefull stuff for no apparent reason

[R. G. Newbury]

On 12/18/2015 09:30 PM, users-requ...@lists.fedoraproject.org wrote:
 On Fri, Dec 18, 2015 at 05:58:55PM -0500,

Fernando Cassia wrote:

>Will check it out. Wasn't aware of such Scientific spin. Does the "labs"
>subdomain mean it is somewhat different from other Fedora respins?

We've split it so the "spins" are focused on presenting desktop
environments (KDE, Xfce, etc.), while "labs" are collections of
software for a given purpose.


>Since I run this on a netbook with low resources (Intel Atom, 32-bit CPU,
>only 2 GB RAM), I'd prefer if I could get openJDK retrofitted into the
>somewhat lightweight Mate-Compiz spin. (I tried Fedora XFCE but hate its
>browser, Midori).

With these needs, it seems like you're really_way_  into "making your
own custom Fedora Remix". See
https://fedoraproject.org/wiki/Remix


A faster and much more useful route is to install isomaster on your main 
computer and use it to edit the iso image.
I have used to to remove unused packages and to add packages. It is 
extremely easy to use. It's been around since 2007 or Fedora 7 so I 
would suspect that it's stable and it works!


R. Geoffrey Newbury 

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: X server dies on startup with kernel-4.2.7-300.fc23.x86_64

[Ed Greshko]

On 12/20/15 05:55, R. G. Newbury wrote:
> Ed Greshko wrote
>
>> On 12/18/15 20:14, Patrick O'Callaghan wrote:
>>> >After rebooting I get the login screen but Plasma segfaults and Gnome
>>> >gives an oops and sad face so I've had to fall back to LxQT until I can
>>> >figure out what's going on.
>> FWIW, I can confirm that akmod-nvidia-358.16-1.fc23.x86_64 breaks my system 
>> with the
>> GeForce 8600M GS card (a rather old card in a laptop).
>>
>> Falling back to akmod-nvidia-340xx.x86_64 got things working again.  You may 
>> want to
>> consider giving that a try after checking and confirming 340xx is supposed 
>> to support your
>> card.
>
> The 8600 series cards are classified like the 9600 series and 9300 series 
> cards , as
> "Legacy" and *require* the 340-xxx series drivers.

I suppose you missed the part in this thread where I came to realize, at the 
prompting of
Ralf, that I consulted the wrong README file?

>
> I am using the 340.96 with a 9300 chipset on my main box, and with a 9600 
> chipset on the
> mythbox. Both running well on F22. Using the wrong driver might the problem, 
> not F23.
>
The OP's card is supposedly supported by the nvidia-358 driver.


-- 
In reality, some people should stick to running Windows and others should stay 
away from
computers altogether.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: X server dies on startup with kernel-4.2.7-300.fc23.x86_64

[R. G. Newbury]

Ed Greshko wrote


On 12/18/15 20:14, Patrick O'Callaghan wrote:

>After rebooting I get the login screen but Plasma segfaults and Gnome
>gives an oops and sad face so I've had to fall back to LxQT until I can
>figure out what's going on.

FWIW, I can confirm that akmod-nvidia-358.16-1.fc23.x86_64 breaks my system 
with the
GeForce 8600M GS card (a rather old card in a laptop).

Falling back to akmod-nvidia-340xx.x86_64 got things working again.  You may 
want to
consider giving that a try after checking and confirming 340xx is supposed to 
support your
card.


The 8600 series cards are classified like the 9600 series and 9300 
series cards , as "Legacy" and *require* the 340-xxx series drivers.


I am using the 340.96 with a 9300 chipset on my main box, and with a 
9600 chipset on the mythbox. Both running well on F22. Using the wrong 
driver might the problem, not F23.


Geoff

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Rex Dieter]

Andrej Podzimek wrote:

> Hello!
> 
> After a Fedora 23 installation, users can't log in with sddm. A "login
> failed" message is displayed by sddm, sometimes preceded by a short switch
> to the tty and back.

Anything recorded in these users' ~/.xsession-errors ?

-- Rex


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Andrej Podzimek]

After a Fedora 23 installation, users can't log in with sddm. A "login
failed" message is displayed by sddm, sometimes preceded by a short switch
to the tty and back.


Anything recorded in these users' ~/.xsession-errors ?


No. :-( Nothing at all, it's empty. (Yeah, that was the first thing I checked.) Also 
"audit2allow -b" doesn't show anything related to sddm. But KDE works and 
starts just fine using startx.


I've just tried Plasma 5 Wayland, but the outcome was even worse, because I 
ended up with a black screen and no way to switch consoles. The log messages 
are still the same, sddm-helper exits with error codes 2 or 15. Running sddm 
with --test-mode doesn't work at all, it just hanges right away.

So sddm is unusable on Fedora 23. (That's odd, because it works just fine for 
me on Arch.) What alternatives could I try? Is there a working display manager 
compatible with KDE 5?

Andrej
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Joe Zeff]

On 12/19/2015 11:30 AM, Andrej Podzimek wrote:


I got a bit closer to the root cause of the problem: SDDM works and logs
me in when I start it by simply running 'sddm' from a root shell. But it
fails (with the symptoms described in this thread) when started using
systemd.

In what way can systemd be hurting sddm so that it can't log users in?


Two thoughts: first, after it fails, log into a CLI and run this:

systemctl status sddm

because that may well answer your question.  Second, try disabling the 
sddm.service and running sddm from rc.local instead.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Andrej Podzimek]

After a Fedora 23 installation, users can't log in with sddm. A "login
failed" message is displayed by sddm, sometimes preceded by a short switch
to the tty and back.


Anything recorded in these users' ~/.xsession-errors ?


No. :-( Nothing at all, it's empty. (Yeah, that was the first thing I checked.) Also 
"audit2allow -b" doesn't show anything related to sddm. But KDE works and 
starts just fine using startx.

Andrej
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Lester M Petrie]

On 12/19/2015 2:05 PM, Andrej Podzimek wrote:

After a Fedora 23 installation, users can't log in with sddm. A "login
failed" message is displayed by sddm, sometimes preceded by a short
switch
to the tty and back.


Anything recorded in these users' ~/.xsession-errors ?


No. :-( Nothing at all, it's empty. (Yeah, that was the first thing I
checked.) Also "audit2allow -b" doesn't show anything related to sddm.
But KDE works and starts just fine using startx.


I've just tried Plasma 5 Wayland, but the outcome was even worse,
because I ended up with a black screen and no way to switch consoles.
The log messages are still the same, sddm-helper exits with error codes
2 or 15. Running sddm with --test-mode doesn't work at all, it just
hanges right away.

So sddm is unusable on Fedora 23. (That's odd, because it works just
fine for me on Arch.) What alternatives could I try? Is there a working
display manager compatible with KDE 5?

Andrej


KDM is still available in KDE F23. I use it because I have to be able to 
configure the login screen, and I didn't find anyway of doing that with 
SDDM.



--
Lester M Petrie
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Firefox does not play Rutube videos

[Heinz Diehl]

On 19.12.2015, Ralf Corsepius wrote: 

> And indeed, they ship 11.2.202.554:
> # rpm -q adobe-release-x86_64 flash-plugin
> adobe-release-x86_64-1.0-1.noarch
> flash-plugin-11.2.202.554-release.x86_64

Remove all flash rpms from your distribution. Donwload the plugin
directly from Adobe. All you need to do is to copy libflashplayer.so
into ~/.mozilla/plugins.

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Andrej Podzimek]

After a Fedora 23 installation, users can't log in with sddm. A "login
failed" message is displayed by sddm, sometimes preceded by a short switch
to the tty and back.


Anything recorded in these users' ~/.xsession-errors ?


No. :-( Nothing at all, it's empty. (Yeah, that was the first thing I checked.) Also 
"audit2allow -b" doesn't show anything related to sddm. But KDE works and 
starts just fine using startx.


I've just tried Plasma 5 Wayland, but the outcome was even worse, because I 
ended up with a black screen and no way to switch consoles. The log messages 
are still the same, sddm-helper exits with error codes 2 or 15. Running sddm 
with --test-mode doesn't work at all, it just hanges right away.

So sddm is unusable on Fedora 23. (That's odd, because it works just fine for 
me on Arch.) What alternatives could I try? Is there a working display manager 
compatible with KDE 5?


I got a bit closer to the root cause of the problem: SDDM works and logs me in 
when I start it by simply running 'sddm' from a root shell. But it fails (with 
the symptoms described in this thread) when started using systemd.

In what way can systemd be hurting sddm so that it can't log users in?

Andrej
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Andrej Podzimek]

I got a bit closer to the root cause of the problem: SDDM works and logs
me in when I start it by simply running 'sddm' from a root shell. But it
fails (with the symptoms described in this thread) when started using
systemd.

In what way can systemd be hurting sddm so that it can't log users in?


Two thoughts: first, after it fails, log into a CLI and run this:

systemctl status sddm


Compared to the strace wrapper I tried, combined with a careful inspection of 
logs from journalctl, status doesn't say too much:

Dec 19 21:41:25 prdell.localdomain systemd[1]: Started Simple Desktop 
Display Manager.
Dec 19 21:41:25 prdell.localdomain systemd[1]: Starting Simple Desktop 
Display Manager...
Dec 19 21:41:27 prdell.localdomain sddm-helper[1893]: 
pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Dec 19 21:41:31 prdell.localdomain sddm-helper[1945]: 
pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Dec 19 21:41:31 prdell.localdomain sddm-helper[1945]: 
pam_kwallet(sddm:auth): (null): pam_sm_authenticate
Dec 19 21:41:31 prdell.localdomain sddm[1880]: Oops, secure memory pool 
already initialized
Dec 19 21:41:31 prdell.localdomain sddm-helper[1945]: 
pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Dec 19 21:41:31 prdell.localdomain sddm-helper[1945]: 
pam_kwallet(sddm:setcred): pam_kwallet: pam_sm_setcred
Dec 19 21:41:31 prdell.localdomain sddm[1880]: Auth: sddm-helper exited 
with 2
Dec 19 21:41:32 prdell.localdomain sddm-helper[1970]: 
pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)

The sddm-helper exits with error code 2, quite likely due to the EPERM I saw in 
the strace logs. And as already mentioned, setting SELinux to permissive makes 
sddm just hang silently.


Second, try disabling the sddm.service and running sddm from rc.local instead.


That fails exactly the same way, which is no surprise, because rc.local is just 
yet another systemd service. There's indeed something in the environment set up 
by systemd that sddm just can't tolerate. I'm still not sure what this could be.

What extra restrictions does systemd impose, when compared to running stuff from a root 
shell? It has its own ulimit settings in /etc/systemd/system.conf, but sddm still fails 
the same way, with "vanilla" ulimit settings as well as with a relaxed vesion 
thereof.

Also tried to set PrivateTmp=true in sddm's unit file, just to check this out, 
but no, still the same problem. :-(

Andrej
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Rex Dieter]

Andrej Podzimek wrote:

 After a Fedora 23 installation, users can't log in with sddm. A "login
 failed" message is displayed by sddm, sometimes preceded by a short
 switch to the tty and back.
>>>
>>> Anything recorded in these users' ~/.xsession-errors ?
>>
>> No. :-( Nothing at all, it's empty. (Yeah, that was the first thing I
>> checked.) Also "audit2allow -b" doesn't show anything related to sddm.
>> But KDE works and starts just fine using startx.
> 
> I've just tried Plasma 5 Wayland, 

yeah, plasma wayland support through dm's is at best a tech-preview and 
virtually untested.  Not ready for any real use yet (in fedora at least)

-- Rex

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Users cannot log in using sddm on Fedora 23

[Rex Dieter]

Lester M Petrie wrote:

> KDM is still available in KDE F23. I use it because I have to be able to
> configure the login screen, and I didn't find anyway of doing that with
> SDDM.

configure the login screen... how?  See 'man sddm.conf' for what can be 
configured

-- Rex

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: dnf system-upgrade fails with key verification

[Joe Zeff]

On 12/18/2015 06:30 PM, dwoody5654 wrote:



You can do a netinstall. There needs to be one partition that is not
reformatted for this to work.


Correction: I misread the above and it looked like I needed to reformat 
/ before starting the installation.  Still, I'd consider this to be Plan 
Z, to be tried if and only if nothing else works.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: X server dies on startup with kernel-4.2.7-300.fc23.x86_64

[Patrick O'Callaghan]

On Sat, 2015-12-19 at 02:26 +0100, Ralf Corsepius wrote:
> On 12/19/2015 01:44 AM, Ed Greshko wrote:
> > 
> > 
> > On 12/18/15 20:14, Patrick O'Callaghan wrote:
> > > After rebooting I get the login screen but Plasma segfaults and
> > > Gnome
> > > gives an oops and sad face so I've had to fall back to LxQT until
> > > I can
> > > figure out what's going on.
> > 
> > FWIW, I can confirm that akmod-nvidia-358.16-1.fc23.x86_64 breaks
> > my system with the
> > GeForce 8600M GS card (a rather old card in a laptop).
> > 
> > Falling back to akmod-nvidia-340xx.x86_64 got things working
> > again.  You may want to
> > consider giving that a try after checking and confirming 340xx is
> > supposed to support your
> > card.
> That's to be expected.
> 
> One cannot blindly install the latest "akmod-nvidia*". You need to
> find 
> out which of them is supposed to support your GPU on [1] and choose
> the 
> corresponding *kmod-nvidia package.
> 
> According to this page the *-358.* series doesn't support the
> "GeForce 
> 8600M GS" [2]. I have an older desktop with a "GeForce 8600 GT",
> where 
> the same applies.

However it does support the GeForce GT 730, which is my card.

poc
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: X server dies on startup with kernel-4.2.7-300.fc23.x86_64

[Patrick O'Callaghan]

On Sat, 2015-12-19 at 12:28 +, Patrick O'Callaghan wrote:
> On Sat, 2015-12-19 at 02:26 +0100, Ralf Corsepius wrote:
> > On 12/19/2015 01:44 AM, Ed Greshko wrote:
> > > 
> > > 
> > > On 12/18/15 20:14, Patrick O'Callaghan wrote:
> > > > After rebooting I get the login screen but Plasma segfaults and
> > > > Gnome
> > > > gives an oops and sad face so I've had to fall back to LxQT
> > > > until
> > > > I can
> > > > figure out what's going on.
> > > 
> > > FWIW, I can confirm that akmod-nvidia-358.16-1.fc23.x86_64 breaks
> > > my system with the
> > > GeForce 8600M GS card (a rather old card in a laptop).
> > > 
> > > Falling back to akmod-nvidia-340xx.x86_64 got things working
> > > again.  You may want to
> > > consider giving that a try after checking and confirming 340xx is
> > > supposed to support your
> > > card.
> > That's to be expected.
> > 
> > One cannot blindly install the latest "akmod-nvidia*". You need to
> > find 
> > out which of them is supposed to support your GPU on [1] and choose
> > the 
> > corresponding *kmod-nvidia package.
> > 
> > According to this page the *-358.* series doesn't support the
> > "GeForce 
> > 8600M GS" [2]. I have an older desktop with a "GeForce 8600 GT",
> > where 
> > the same applies.
> 
> However it does support the GeForce GT 730, which is my card.

Just to follow up: I reverted to the 340.* driver and it now works (I
see it was updated for the latest X).

poc
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: dnf system-upgrade fails with key verification

[Joe Zeff]

On 12/18/2015 06:30 PM, dwoody5654 wrote:



You can do a netinstall.


Getting the upgrade to work is better, and I think I know how.  And, it 
doesn't require me to start out by reformatting my root partition, or 
booting into Grub when there's no working system and no way to boot from 
any other media.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Firefox does not play Rutube videos

[Ralf Corsepius]

On 12/18/2015 09:56 PM, Paul Smith wrote:

Interestingly, the Adobe website asserts that the current (and last) version of 
the flash player is Version 11.2.202.554, but the rpm that the website delivers 
is adobe-release-x86_64-1.0-1, built in 2011.


adobe-release-x86_64-1.0-1 contains their repository's yum/dnf 
/etc/yum.repos.d/*.repo for x86_64. To get flash going you need to 
install the flash-plugin from their repository via yum.


And indeed, they ship 11.2.202.554:
# rpm -q adobe-release-x86_64 flash-plugin
adobe-release-x86_64-1.0-1.noarch
flash-plugin-11.2.202.554-release.x86_64

cf. 
http://linuxconfig.org/how-to-install-adobe-flash-player-on-fedora-linux-with-firefox


Ralf

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Users cannot log in using sddm on Fedora 23

[Andrej Podzimek]

Hello!

After a Fedora 23 installation, users can't log in with sddm. A "login failed" 
message is displayed by sddm, sometimes preceded by a short switch to the tty and back. 
Users can log into a text console just fine. Also starting a Plasma desktop using startx 
works perfectly fine.

Because sddm's logs report helper failures with codes 2 and 15, I tried this:

# cp -a /usr/libexec/sddm-helper /usr/libexec/sddm-helper-binary
# cat > /usr/libexec/sddm-helper <<-WRAPPER
#!/bin/bash
strace -f /usr/libexec/sddm-helper-binary "$@" 2>/tmp/sddm
WRAPPER

Here's the entire strace output obtained from a login attempt using the wrapper 
above: https://andrej.podzimek.org/dell-strace-0.txt The strace dump shows 
(among other glitches) something like a file descriptor leak. But the most 
important thing seems to be the following:

[pid  1818] execve("/usr/sbin/unix_chkpwd", ["/usr/sbin/unix_chkpwd", "andrej", 
"nullok"], [/* 0 vars */]) = -1 EPERM (Operation not permitted)
[pid  1820] execve("/usr/sbin/unix_chkpwd", ["/usr/sbin/unix_chkpwd", "andrej", 
"nullok"], [/* 0 vars */]) = -1 EPERM (Operation not permitted)

I tried to make /etc/shadow readable, but that didn't help. Also tried to do 
setenforce 0 and that didn't help either. :( Last but not least, rebooting with 
SELinux in permissive mode does away with the EPERM error, but sddm logins hang 
forever, with no chance to retry.

I looked at recent sddm bugs such as this one: 
https://bugzilla.redhat.com/show_bug.cgi?id=1265813 But I don't think other 
sddm issues could be directly related, because the failure pattern is 
different, i.e., I can't see any segfaults here and my user IDs are in the 
correct range (uid 1001 in the attached log). :(

What's wrong here? Why does sddm fail on Fedora 23? The hardware, just if it 
happens to matter:
DMI: Dell Inc. Inspiron 7548/0AM6R0, BIOS A00 11/19/2014

Cheers,
Andrej
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: one click is not enough anymore

[Rex Dieter]

Maurizio Marini wrote:

> after one of last update, sorry I dunno which one, let's say by 2 days and
> I update every day, I have to click more than 1 time on windows on
> kde plasma panel.
> Often double click is enough.
> Am I the only one, here, to have this issue?
> -m

You may want this update:

https://bodhi.fedoraproject.org/updates/FEDORA-2015-f0aa62dc50


-- Rex

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org