F15: LXDE install, OpenBox not running
I installed the LXDE spin of Fedora 15 via a live usb stick on my Acer Netbook. The install went through without errors but when starting up LXDE, the Openbox window manager isn't running. Starting it by hand works though I'm not sure how to correctly set it up that it starts up every time. Any hints? Thanks, Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F15: LXDE install, OpenBox not running
2011/6/5 Richard Shaw : > Take a look at: > https://bugzilla.redhat.com/show_bug.cgi?id=704403 > > The fix is probably to update and then remove and add your user. > > An alternative might be to update than then "rm -f > ~/.config/lxsession" and relogin. Thanks, deleting the ~/.config/lxsession/LXDE as recommended in the Bugzilla entry did the trick. Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: gnome 3 doesn't start any more
2011/6/25 Kevin Fenzi : > Please test and provide feedback: > > https://admin.fedoraproject.org/updates/gnome-shell-3.0.2-4.fc15 > > This seems to have affected nvidia binary only video driver users. This one fixes the issue. Great to see how fast fixes are coming. :) Thanks, Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Steam on Fedora
2012/12/21 Konstantin Svist : > In case you missed it (I did), Steam linux beta client is now available for > everyone, and there's a way to get it running on Fedora: > > # cd /etc/yum.repos.d > # wget http://spot.fedorapeople.org/steam/steam.repo > # yum install steam > > > Million thanks to Spot! And thanks for pointing out the repo. Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Steam on Fedora
2012/12/22 Konstantin Svist : > Update: looks like Spot's repo is now gone, but there's another one here: > http://software.opensuse.org/package/steam > Thanks to Olorin on steamcommunity.com Thanks, that even has the 1.0.0.18 version but only the steam package, not the dependencies. Does anyone know whether spots repo will come back up? Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Steam on Fedora
2013/1/4 Konstantin Svist : > On 01/03/2013 06:01 AM, Sergio Augusto Vladisauskis wrote: > > Repository http://spot.fedorapeople.org/steam/steam.repo no more exists? > > > Correct, instead use http://software.opensuse.org/package/steam So, now that is gone as well. And steam tells me, my package is outdated, I should get a newer one from where I got the older one. Has anyone got a new location? Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Steam on Fedora
2013/1/12 Kevin Fenzi : > Spot's repo is back up. > > I'd advise using that: > http://spot.fedorapeople.org/steam/ That is very helpful, thank you. Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Steam on Fedora
2013/1/12 Niels Weber : > 2013/1/12 Kevin Fenzi : >> Spot's repo is back up. >> >> I'd advise using that: >> http://spot.fedorapeople.org/steam/ > > That is very helpful, thank you. Sadly it doesn't seem to be updated with newer steam versions. Does anyone know the status? Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
unlock screen?
Hi,
I'm experimenting around with blueproximity (on F21). The default
commands it uses to lock and unlock the screen use the
gnome-screensaver-command tool, that doesn't exist any more. I already
found out that I can lock the screen by sending a dbus command:
dbus-send --type=method_call --dest=org.gnome.ScreenSaver
/org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock
But there doesn't seem to be anything for unlocking the screen?
("gnome-screensaver-command -d")
Is there any way that I missed so far? Or is it simply not possible?
Thanks,
Niels
--
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: unlock screen?
Am Dienstag, den 17.03.2015, 15:49 +0800 schrieb Ed Greshko:
> On 03/17/15 15:08, Niels Weber wrote:
> > I'm experimenting around with blueproximity (on F21). The default
> > commands it uses to lock and unlock the screen use the
> > gnome-screensaver-command tool, that doesn't exist any more. I already
> > found out that I can lock the screen by sending a dbus command:
> >
> > dbus-send --type=method_call --dest=org.gnome.ScreenSaver
> > /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock
> >
> > But there doesn't seem to be anything for unlocking the screen?
> > ("gnome-screensaver-command -d")
> > Is there any way that I missed so far? Or is it simply not possible?
>
> [root@meimei ~]# which gnome-screensaver-command
> /bin/gnome-screensaver-command
>
> [root@meimei ~]# yum whatprovides /bin/gnome-screensaver-command
> Loaded plugins: langpacks
> gnome-screensaver-3.6.1-9.fc21.x86_64 : GNOME Screensaver
> Repo: installed
> Matched from:
> Filename: /bin/gnome-screensaver-command
>
> So, unless I read your post incorrectly, it seems to be there
Thanks. So yes it is still there (just not by default) and works. This
solves my immediate problem. :)
Anyway, I understand that it is deprecated and my go away or stop
working soon. It still being at 3.6 certainly also points in that
direction. Will there be a replacement? Or is it not going away soon
after all?
Thanks,
Niels
--
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: F16--Something went wrong in Gnome...
Hi, I have a similar issue. 2011/11/9 Daniel J Walsh : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 11/08/2011 07:15 PM, Joe Zeff wrote: >> On 11/08/2011 04:10 PM, antonio montagnani wrote: >>> I rebooted disabling Selinux on the command line and I could use >>> Gnome, then I restarted and system relabeled all files and I >>> could login in Gnome. No idea what was going on, but that's it >> >> I'm glad you found it. The reason I asked was that I've seen >> people blame SELinux for random problems so often without the >> slightest evidence that it's involved that I tend to be skeptical >> about such claims unless there are alerts. BTW, when you were >> using KDE did you check the troubleshooter for alerts? I'm not >> sure if they'd still be there at this point, but it would be nice >> to know if there were any and what they were. > If you have a problem with SELinux please boot in permissive mode and > not disabled, to report what SELinux is complaining about. That way > we can figure out what the problem is and hopefully fix it for others. > Usually it is a minor labeling problem. If you turn SELinux back on, > the system should relabel itself, and the problem will be fixed. the login screen didn't work, switching to runlevel 3 and startx worked though. Setting selinux to permissive allowed the login screen to run. Relabelling the file system didn't help at all. > If you still have the auditlogs availabel could you email me the > compressed output of > > ausearch -m avc There is nothing in the timeframe in the output. Any ideas? Thanks, Niels -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F16--Something went wrong in Gnome...
2011/11/9 Antonio M : > 2011/11/9 Niels Weber : >> Hi, >> >> I have a similar issue. >> >> 2011/11/9 Daniel J Walsh : >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> On 11/08/2011 07:15 PM, Joe Zeff wrote: >>>> On 11/08/2011 04:10 PM, antonio montagnani wrote: >>>>> I rebooted disabling Selinux on the command line and I could use >>>>> Gnome, then I restarted and system relabeled all files and I >>>>> could login in Gnome. No idea what was going on, but that's it >>>> >>>> I'm glad you found it. The reason I asked was that I've seen >>>> people blame SELinux for random problems so often without the >>>> slightest evidence that it's involved that I tend to be skeptical >>>> about such claims unless there are alerts. BTW, when you were >>>> using KDE did you check the troubleshooter for alerts? I'm not >>>> sure if they'd still be there at this point, but it would be nice >>>> to know if there were any and what they were. >>> If you have a problem with SELinux please boot in permissive mode and >>> not disabled, to report what SELinux is complaining about. That way >>> we can figure out what the problem is and hopefully fix it for others. >>> Usually it is a minor labeling problem. If you turn SELinux back on, >>> the system should relabel itself, and the problem will be fixed. >> >> the login screen didn't work, switching to runlevel 3 and startx worked >> though. >> Setting selinux to permissive allowed the login screen to run. >> Relabelling the file system didn't help at all. >> >>> If you still have the auditlogs availabel could you email me the >>> compressed output of >>> >>> ausearch -m avc >> >> There is nothing in the timeframe in the output. >> >> Any ideas? >> >> Thanks, >> Niels >> -- >> users mailing list >> users@lists.fedoraproject.org >> To unsubscribe or change subscription options: >> https://admin.fedoraproject.org/mailman/listinfo/users >> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines >> > > Are you sure to have relabeled ?? or did you switch from permissive to > targeted??? > Just to clear I did a touch /.autorelabel and rebooted. I think it said something about rebuilding the targeted setup and it took quite some time. Niels -- Ama-Gi! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F16--Something went wrong in Gnome...
2011/11/9 Daniel J Walsh :
> On 11/09/2011 11:26 AM, Antonio M wrote:
>> 2011/11/9 Niels Weber :
>>> 2011/11/9 Antonio M :
>>>> 2011/11/9 Niels Weber :
>>>>> I have a similar issue.
>>>>>
>>>>> the login screen didn't work, switching to runlevel 3 and
>>>>> startx worked though. Setting selinux to permissive allowed
>>>>> the login screen to run. Relabelling the file system didn't
>>>>> help at all.
>>>>>
>>>>>> If you still have the auditlogs availabel could you email
>>>>>> me the compressed output of
>>>>>>
>>>>>> ausearch -m avc
>>>>>
>>>>> There is nothing in the timeframe in the output.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Thanks, Niels -- users mailing list
>>>>> users@lists.fedoraproject.org To unsubscribe or change
>>>>> subscription options:
>>>>> https://admin.fedoraproject.org/mailman/listinfo/users
>>>>> Guidelines:
>>>>> http://fedoraproject.org/wiki/Mailing_list_guidelines
>>>>>
>>>>
>>>> Are you sure to have relabeled ?? or did you switch from
>>>> permissive to targeted??? Just to clear
>>>
>>> I did a touch /.autorelabel and rebooted. I think it said
>>> something about rebuilding the targeted setup and it took quite
>>> some time.
>>>
>>> Niels -- Ama-Gi! -- users mailing list
>>> users@lists.fedoraproject.org To unsubscribe or change
>>> subscription options:
>>> https://admin.fedoraproject.org/mailman/listinfo/users
>>> Guidelines:
>>> http://fedoraproject.org/wiki/Mailing_list_guidelines
>>>
>>
>> I would disable (not permissive) Selinux, boot, then enable again
>> and reboot again, in order to have labeling at boot-time. Just a
>> shot in the dark (but it is what I did)
>>
>> Antonio Montagnani Skype : amontag52 SIP: antoniomon...@ekiga.net
>> Linux Fedora 15 Lovelock
>
>
> You should not need to do this. What avc messages are you seeing in
> the audit.log?
The only thing I see that happens at the right time is this entry in
/var/log/messages:
Nov 10 13:25:53 numenor kernel: [20888.947632] type=1400
audit(1320927953.340:27): avc: denied { ioctl } for pid=12966
comm="gnome-shell" path="/dev/nvidiactl" dev=devtmpfs ino=18101
scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
I remember that there was a similar problem with the last release.
What am I to do? Relabelling didn't help so far.
Niels
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
