Re: Multi-user VNC on F23 and later

On 07/13/17 02:13, CLOSE Dave wrote: > Ed Greshko wrote: > >> Oh, and since I think you said you're not using IPv6 for anything you >> can disable it completely and try again. >> >> Adding ipv6.disable=1 to the boot parameters seems to work the best. >> That way it is disabled from boot time. >

Re: Multi-user VNC on F23 and later

Ed Greshko wrote: > Oh, and since I think you said you're not using IPv6 for anything you > can disable it completely and try again. > > Adding ipv6.disable=1 to the boot parameters seems to work the best. > That way it is disabled from boot time. That did it! The greeting screen now appears as

Re: Multi-user VNC on F23 and later

On 07/11/17 08:18, CLOSE Dave wrote: > And when I try to connect, > > Jul 10 17:05:49 server kdm: fe80::3617:ebff:feeb:6b02:1[7472]: Cannot > connect to fe80::3617:ebff:feeb:6b02:1, giving up > Jul 10 17:05:49 server kdm[1676]: Display fe80::3617:ebff:feeb:6b02:1 > cannot be opened Oh, and since

Re: Multi-user VNC on F23 and later

On 07/11/17 08:46, CLOSE Dave wrote: > Ed Greshko wrote: > >> I found that if I have ListenStream=192.168.1.198:5901 in my >> xvnc.socket file I also get a failure on boot. I thought it could >> have been due to my using DHCP on that VM. I changed it back to >> ListenStream=5901. Can you try

Re: Multi-user VNC on F23 and later

On 07/10/2017 05:42 PM, CLOSE Dave wrote: > On 07/10/17 17:32, Ed Greshko wrote: > >> Odd that you're getting an IPV6 error message. I don't have a global >> IPv6 address and only show >> >> [egreshko@f25f system]$ ip address show enp0s3 >> 2: enp0s3: mtu

Re: Multi-user VNC on F23 and later

Ed Greshko wrote: > I found that if I have ListenStream=192.168.1.198:5901 in my > xvnc.socket file I also get a failure on boot. I thought it could > have been due to my using DHCP on that VM. I changed it back to > ListenStream=5901. Can you try just having that? The socket now reports that

Re: Multi-user VNC on F23 and later

On 07/11/17 08:42, CLOSE Dave wrote: > On 07/10/17 17:32, Ed Greshko wrote: > >> Odd that you're getting an IPV6 error message. I don't have a global >> IPv6 address and only show >> >> [egreshko@f25f system]$ ip address show enp0s3 >> 2: enp0s3: mtu 1500

Re: Multi-user VNC on F23 and later

On 07/10/17 17:32, Ed Greshko wrote: > Odd that you're getting an IPV6 error message. I don't have a global > IPv6 address and only show > > [egreshko@f25f system]$ ip address show enp0s3 > 2: enp0s3: mtu 1500 qdisc fq_codel state UP > group > default qlen

Re: Multi-user VNC on F23 and later

Ed Greshko wrote: > You have a line in the Service segment of "Type". I do not have that > and it isn't in the original file in /lib/systemd/system. Did you > add that? Rick Stevens wrote: > I believe "Type=simple" is the default if you have "ExecStart=" > defined, but it wouldn't hurt to add

Re: Multi-user VNC on F23 and later

On 07/11/17 08:18, CLOSE Dave wrote: > Ed Greshko wrote: > >>> HOWEVER, when I connect with "vncviewer server::5901", I get a blank >>> screen with a momentary F8 prompt. I do not see the normal greeting >>> screen. Something is still missing. >> Then I noticed one thing which seems off or odd do

Re: Multi-user VNC on F23 and later

On 07/10/2017 04:38 PM, Ed Greshko wrote: > On 07/11/17 05:42, CLOSE Dave wrote: >> >> # cat /etc/systemd/system/xvnc@.service >> [Unit] >> Description=XVNC per Connection Daemon >> After=syslog.target >> >> [Service] >> Type=simple >> ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry

Re: Multi-user VNC on F23 and later

Ed Greshko wrote: >> HOWEVER, when I connect with "vncviewer server::5901", I get a blank >> screen with a momentary F8 prompt. I do not see the normal greeting >> screen. Something is still missing. > Then I noticed one thing which seems off or odd do me. > > When you do "systemctl -l status

Re: Multi-user VNC on F23 and later

On 07/11/17 05:42, CLOSE Dave wrote: > > # cat /etc/systemd/system/xvnc@.service > [Unit] > Description=XVNC per Connection Daemon > After=syslog.target > > [Service] > Type=simple > ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768 > -depth 24 -once -SecurityTypes=None -fp

Re: Multi-user VNC on F23 and later

On 07/11/17 05:42, CLOSE Dave wrote: > > This was caused because the old service, vncserver@:1, was still > running. After I stopped it (and deleted the files, just to be sure), > status looks correct. > > --- > > # systemctl -l status xvnc.socket > xvnc.socket - XVNC Server >Loaded: loaded

Re: Multi-user VNC on F23 and later

Ed Greshko wrote: > You actually don't want xvnc@.service to be enabled or started. The > connection to the socket triggers starting of Xvnc I realized that a while ago but forgot. It is presently not enabled. > I find it odd that you get this "Listen: 10.76.185.91:5901" when > your file

Re: Multi-user VNC on F23 and later

On 07/08/17 09:40, CLOSE Dave wrote: > Here's my files. Just to clarify a bit more... > > # cd /etc/systemd/system > # cat xvnc@.service > [Unit] > Description=XVNC per Connection Daemon > After=syslog.target > > [Service] > Type=simple > ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry

Re: Multi-user VNC on F23 and later

On 07/08/17 10:22, Ed Greshko wrote: > That is 5901 v.s. 5901 Of course I wanted to type 5901 v.s. 5900 -- Fedora Users List - The place to go to speculate endlessly signature.asc Description: OpenPGP digital signature ___ users mailing list --

Re: Multi-user VNC on F23 and later

On 07/08/17 09:40, CLOSE Dave wrote: > Almost. But the service isn't starting. > > # systemctl status -l xvnc@:.service > xvnc@:.service - XVNC per Connection Daemon >Loaded: loaded (/etc/systemd/system/xvnc@.service; enabled; vendor > preset: disabled) >Active: failed (Result:

Re: Multi-user VNC on F23 and later

Ed Greshko wrote: > OK. Sorry to have misunderstood precisely what you want to do. I > now have it working as I suspect you need it. Great. Thanks. > 1. Yes, you need KDM. So, if you've not installed it do so. > > 2. Edit /etc/kde/kdm/kdmrc the [Xdmcp] section Enable=true. > > 3. Go to

Re: Multi-user VNC on F23 and later

On 07/08/17 08:32, Ed Greshko wrote: > 7. If you've not already done it "systemctl --force enable kdm" > > 8. Reboot. > > Your console should now be showing KDM as your login screen. > > And you now should be able to connect with something like remmina using VNC > protocol > and get presented

Re: Multi-user VNC on F23 and later

On 07/08/17 01:50, CLOSE Dave wrote: > Unfortunately, no, that doesn't help. I already have a one-user setup > working and I understand how to extend it to additional users -- so long > as the list of users is finite and known to me in advance. But the > extension technique involves using

Re: Multi-user VNC on F23 and later

I wrote: > I'm trying to setup a multi-user VNC server on recent versions of > Fedora without success thus far. I understand that doing so requires > a display manager with XDMCP support. The current default DM is SDDM > which does not include such support (at least so far as I've found). > That

Re: Multi-user VNC on F23 and later

On 07/07/17 09:26, CLOSE Dave wrote: > I'm trying to setup a multi-user VNC server on recent versions of Fedora > without success thus far. I understand that doing so requires a display > manager with XDMCP support. The current default DM is SDDM which does > not include such support (at least

Re: Multi-user VNC on F23 and later

On 07/07/17 09:26, CLOSE Dave wrote: > I'm trying to setup a multi-user VNC server on recent versions of Fedora > without success thus far. I understand that doing so requires a display > manager with XDMCP support. The current default DM is SDDM which does > not include such support (at least

Multi-user VNC on F23 and later

I'm trying to setup a multi-user VNC server on recent versions of Fedora without success thus far. I understand that doing so requires a display manager with XDMCP support. The current default DM is SDDM which does not include such support (at least so far as I've found). That means I need to

Re: f23 :: kde and qt updates broken

On 12/11/2016 08:55 PM, Michael Schwendt wrote: On Sun, 11 Dec 2016 17:11:51 +0200, Adrian Sevcenco wrote: No. That's not the same package I mentioned. Notice the extra ".2" behind ".fc23". That's a minor release update in the least-significant right-most part of the package "Release" tag.

Re: f23 :: kde and qt updates broken

On Sun, 11 Dec 2016 17:11:51 +0200, Adrian Sevcenco wrote: > > No. That's not the same package I mentioned. Notice the extra ".2" behind > > ".fc23". That's a minor release update in the least-significant > > right-most part of the package "Release" tag. > > yes, you're right, i did not see it

f23 :: openvpn 2.3.14-1 :: Failed running command (--up/--down)

Hi! Did anyone succeeded to run openvpn server in fedora >= 23 ? (this is 2.3.14 version - f25 srpm rebuilt on f23) Even if i have all the needed configuration and permissions of the script i have a message like : WARNING: Failed running command (--up/--down): could not execute exter

Re: f23 :: kde and qt updates broken

On 12/11/2016 02:42 PM, Michael Schwendt wrote: On Sat, 10 Dec 2016 17:34:26 +0200, Adrian Sevcenco wrote: Just based on what you've quoted, I would guess the explicit dependency found in kf5-frameworkintegration on an older Qt 5 version blocks the update. There should be are rebuild in the

Re: f23 :: kde and qt updates broken

On Sat, 10 Dec 2016 17:34:26 +0200, Adrian Sevcenco wrote: > > Just based on what you've quoted, I would guess the explicit dependency > > found in kf5-frameworkintegration on an older Qt 5 version blocks the > > update. There should be are rebuild in the updates repo, however: > >

Re: f23 :: kde and qt updates broken

On 12/10/2016 07:18 PM, Rex Dieter wrote: Adrian Sevcenco wrote: Hi! It would seem that the configs for the qt and kde updates were broken .. trying to update i have this : Should be fixed by: https://bodhi.fedoraproject.org/updates/FEDORA-2016-22b09070a2 Thanks a lot! it worked :) Adrian

Re: f23 :: kde and qt updates broken

Adrian Sevcenco wrote: > Hi! It would seem that the configs for the qt and kde updates were broken > .. trying to update i have this : Should be fixed by: https://bodhi.fedoraproject.org/updates/FEDORA-2016-22b09070a2 -- Rex ___ users mailing list --

Re: f23 :: kde and qt updates broken

On 12/10/2016 04:19 PM, Michael Schwendt wrote: On Sat, 10 Dec 2016 12:52:27 +0200, Adrian Sevcenco wrote: Hi! It would seem that the configs for the qt and kde updates were broken .. trying to update i have this : Error: package kf5-frameworkintegration-5.27.0-1.fc23.x86_64 requires

Re: f23 :: kde and qt updates broken

On Sat, 10 Dec 2016 12:52:27 +0200, Adrian Sevcenco wrote: > Hi! It would seem that the configs for the qt and kde updates were broken .. > trying to update i have this : > > Error: package kf5-frameworkintegration-5.27.0-1.fc23.x86_64 requires > qt5-qtbase(x86-64) = 5.6.1, but none of the

f23 :: kde and qt updates broken

Hi! It would seem that the configs for the qt and kde updates were broken .. trying to update i have this : Error: package kf5-frameworkintegration-5.27.0-1.fc23.x86_64 requires qt5-qtbase(x86-64) = 5.6.1, but none of the providers can be installed. ... and so on but if i try only qt5

Re: Today's F23 Qt5 update

On 12/07/16 19:13, Ed Greshko wrote: > > > On 12/08/16 06:08, Kevin Cummings wrote: >> What is wrong with the dependencies? What can I do to fix it? > > Not really running F23 since it will go EOL soon. But I had a VM and tested > and verified > the issue you're s

Re: Today's F23 Qt5 update

On 12/08/16 06:08, Kevin Cummings wrote: > What is wrong with the dependencies? What can I do to fix it? Not really running F23 since it will go EOL soon. But I had a VM and tested and verified the issue you're seeing. You can do "dnf --best update" to determine what the brok

Today's F23 Qt5 update

Am I the only person seeing the following: > v = 18.487/19.290/20.489/0.863 ms > [root@kjclap4 ~]# dnf update > Last metadata expiration check: 1:27:15 ago on Wed Dec 7 15:39:19 2016. > Dependencies resolved. >

Re: Botched fedup F23 -> F24 with nvidia

On Mon, Nov 7, 2016 at 7:33 AM, joev.8450 wrote: > doesn't the nVidia installer uninstall everything nvidia before it > installs the version in the invoked installer run file? I wouldn't know as I always install everything from packages, and that's what Mark is doing as

Re: Botched fedup F23 -> F24 with nvidia

On Mon, 2016-11-07 at 09:33 -0500, joev.8450 wrote: > doesn't the nVidia installer uninstall everything nvidia before it > installs the version in the invoked installer run file?  I mean is > there > something else I should invoke or do to make sure I've uninstalled > everything nvidia?  I'm

Re: Botched fedup F23 -> F24 with nvidia

doesn't the nVidia installer uninstall everything nvidia before it installs the version in the invoked installer run file? I mean is there something else I should invoke or do to make sure I've uninstalled everything nvidia? I'm having somewhat of a similar problem but re-running the installer

Re: After fedup F23 -> F24 no more left-handed mouse

On Fri, 04 Nov 2016 17:17:09 +0100 Mark <mark2...@openmailbox.org> wrote: > Hi > > I just upgraded my desktop from F23 to F24 via fedup and after that > the setting to have the right mouse button as the primary one has no > effect. That is I go to All Settings -> Mou

After fedup F23 -> F24 no more left-handed mouse

Hi I just upgraded my desktop from F23 to F24 via fedup and after that the setting to have the right mouse button as the primary one has no effect. That is I go to All Settings -> Mouse & Touchpad and select Right as the primary button. But it has no effect at all. Even when I go to Te

Re: Botched fedup F23 -> F24 with nvidia

On Thu, 2016-11-03 at 12:28 -0600, Greg Woods wrote: > On Thu, Nov 3, 2016 at 11:30 AM, Mark > wrote: > > > > > All I got was a grey page with the text "Oh no! Something has > > gone wrong. > > > > When using the Nvidia proprietary driver, when I have this happen, >

Re: Botched fedup F23 -> F24 with nvidia

On Thu, Nov 3, 2016 at 11:30 AM, Mark wrote: > All I got was a grey page with the text "Oh no! Something has > gone wrong. > When using the Nvidia proprietary driver, when I have this happen, the only way I have successfully recovered is to uninstall everything

Botched fedup F23 -> F24 with nvidia

o boot one of the F23 kernels. I tried to disconnect the second monitor if that would make any difference. All got was that grey page telling me that something was wrong. dmesg didn't provide any message that I though would be directly suspicious. The graphics card is a Nvidia Quadro 600 (GF108GL) How

Re: How to access the "Packages" directory on the f23 and f24 Workstation iso image?

On 11/03/16 09:33, Rick Stevens wrote: > On 11/02/2016 06:30 PM, fred roller wrote: >> Mount -o loop file.iso ./somedirectory/you/made >> >> I believe will mount your image >> >> Most archive managers will open an iso file as well. Booting a live >> usb/dvd would allow for exploring. > To be

Re: How to access the "Packages" directory on the f23 and f24 Workstation iso image?

On 11/02/2016 06:30 PM, fred roller wrote: > Mount -o loop file.iso ./somedirectory/you/made > > I believe will mount your image > > Most archive managers will open an iso file as well. Booting a live > usb/dvd would allow for exploring. To be certain: mount -o loop -t iso9660

Re: How to access the "Packages" directory on the f23 and f24 Workstation iso image?

Mount -o loop file.iso ./somedirectory/you/made I believe will mount your image Most archive managers will open an iso file as well. Booting a live usb/dvd would allow for exploring. Fred Roller On Nov 2, 2016 7:13 PM, "jd1008" wrote: > >

How to access the "Packages" directory on the f23 and f24 Workstation iso image?

___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org

Can't suspend F23 due to mate-settings-daemon and mate-multiload-applet

Have anyone else noticed this? If I boot any of the recent 4.7 kernels, I can immediately suspend my laptop without incident. If I leave the system up for some reasonable amount of time, then everytime I try to suspend, it fails. journalctl shows that 2 Mate daemons refuse to Freeze: Here is

Re: F23 rsnapshot log timestamps funny

On 20 October 2016 at 11:31, Patrick O'Callaghan wrote: > On Thu, 2016-10-20 at 10:13 +0100, Christopher Ross wrote: >> Since yesterday's update of rsnapshot to >> rsnapshot-1.4.2-1.fc23.noarch >> >> The format of the date/time field in the rsnapshot.log has gone funny, >>

Re: F23 rsnapshot log timestamps funny

On Thu, 2016-10-20 at 10:13 +0100, Christopher Ross wrote: > Since yesterday's update of rsnapshot to > rsnapshot-1.4.2-1.fc23.noarch > > The format of the date/time field in the rsnapshot.log has gone funny, > as per the following examples... > > [19/Oct/2016:11:53:42] /usr/bin/rsnapshot

F23 rsnapshot log timestamps funny

Since yesterday's update of rsnapshot to rsnapshot-1.4.2-1.fc23.noarch The format of the date/time field in the rsnapshot.log has gone funny, as per the following examples... [19/Oct/2016:11:53:42] /usr/bin/rsnapshot daily: completed successfully [19/Oct/2016:12:04:15] /usr/bin/rsnapshot

what creates /dev/watchdog and /dev/watchdog0 on my f23 system?

poking around in watchdog support for the first time, and i see these special device files: crw---. 1 root root 10, 130 Oct 15 04:55 /dev/watchdog crw---. 1 root root 250, 0 Oct 15 04:55 /dev/watchdog0 can someone tell me what part of the boot process creates those special

Re: F23: KDE menu launch SSH inside konsole fails after update

On Thu, 2016-10-13 at 10:36 +0100, Gary Stainburn wrote: > On Thursday 13 October 2016 10:05:56 Gary Stainburn wrote: > > Unfortunately, I cannot convert this into a usable solution in the KDE menu > > Editor > > I've been totally unable to get this working properly within KDE Menu Editor. This

Re: F23: KDE menu launch SSH inside konsole fails after update

On Thursday 13 October 2016 10:05:56 Gary Stainburn wrote: > Unfortunately, I cannot convert this into a usable solution in the KDE menu > Editor I've been totally unable to get this working properly within KDE Menu Editor. Instead I've had to modify my root BASH script to cope. Not pretty, but

Re: F23: KDE menu launch SSH inside konsole fails after update

On Thursday 13 October 2016 09:48:31 Gary Stainburn wrote: > On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote: > > That looks similar to this upstream bug: > > https://bugs.kde.org/show_bug.cgi?id=366793 > > Interestingly, I now have two problems. > > This is indeed the problem on the PC I

Re: F23: KDE menu launch SSH inside konsole fails after update

On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote: > That looks similar to this upstream bug: > https://bugs.kde.org/show_bug.cgi?id=366793 Interestingly, I now have two problems. This is indeed the problem on the PC I initially experienced the problem on. As suggested in the bug report,

Re: F23: KDE menu launch SSH inside konsole fails after update

On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote: > On 7 October 2016 at 16:05, Gary Stainburn > > wrote: > > I don't know when it stopped working working, but it was recently. > > Unfortunately, with almost daily updates I don't know what's caused it. > > > >

Re: F23: KDE menu launch SSH inside konsole fails after update

On 7 October 2016 at 16:05, Gary Stainburn wrote: > I don't know when it stopped working working, but it was recently. > Unfortunately, with almost daily updates I don't know what's caused it. > > I have menu entried within my KDE which start a ssh command inside a

F23: KDE menu launch SSH inside konsole fails after update

I don't know when it stopped working working, but it was recently. Unfortunately, with almost daily updates I don't know what's caused it. I have menu entried within my KDE which start a ssh command inside a konsole. This has worked fine for as long as I can remember (F9 or before) However,

Re: Upgrade to F23 breaks Adobe Reader

On 17/09/16 03:07, Samuel Sieb wrote: dnf repoquery --whatprovides libgdk_pixbuf_xlib-2.0.so.0 Thanks for that. I'm still coming to grips with dnf syntax Your suggestion gives: dnf repoquery --whatprovides libgdk_pixbuf_xlib-2.0.so.0 Last metadata expiration check: 1:56:03 ago on Sat Sep 17

Re: Upgrade to F23 breaks Adobe Reader

I was about to recommend an uninstall and re-install. When I realized? This ain't Windows!! On Sep 16, 2016 1:34 PM, Samuel Sieb <sam...@sieb.net> wrote: > > On 09/16/2016 01:04 AM, Stephen Davies wrote: > > Following last night's upgrade to F23, Adobe Reader now gives: > >

Re: Upgrade to F23 breaks Adobe Reader

On 09/16/2016 10:34 AM, Samuel Sieb wrote: On 09/16/2016 01:04 AM, Stephen Davies wrote: Following last night's upgrade to F23, Adobe Reader now gives: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading shared libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared

Re: Upgrade to F23 breaks Adobe Reader

On 09/16/2016 01:04 AM, Stephen Davies wrote: Following last night's upgrade to F23, Adobe Reader now gives: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading shared libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared object file: No such file or directory Needless

Re: Upgrade to F23 breaks Adobe Reader

welll, Adobe Reader for Linux hasn't been supported for at least two years... https://forums.adobe.com/thread/1597058 FC On Fri, Sep 16, 2016 at 8:04 AM, Stephen Davies <sdav...@sdc.com.au> wrote: > Following last night's upgrade to F23, Adobe Reader now gives: > > /opt/Adobe

Upgrade to F23 breaks Adobe Reader

Following last night's upgrade to F23, Adobe Reader now gives: /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading shared libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared object file: No such file or directory Needless to say, acroread worked perfectly before

Re: Upgrade to F23 breaks PERL

On 09/16/2016 12:10 AM, Stephen Davies wrote: I take it from your comment that CPAN puts things into /usr/local. Yes. Can I just blow away all things PERL in /usr/local and then install any modules that go missing using dnf? Assuming the module is packaged, you can do, for example: dnf

Re: Upgrade to F23 breaks PERL

On 16/09/16 15:32, Samuel Sieb wrote: On 09/15/2016 06:04 PM, Stephen Davies wrote: -- /usr/bin/perl: symbol lookup error: /usr/local/lib64/perl5/auto/Unix/Syslog/Syslog.so: undefined symbol: Perl_xs_version_bootcheck I understand from other posts that this is probably caused by my having two

Re: Upgrade to F23 breaks PERL

On 09/15/2016 06:04 PM, Stephen Davies wrote: -- /usr/bin/perl: symbol lookup error: /usr/local/lib64/perl5/auto/Unix/Syslog/Syslog.so: undefined symbol: Perl_xs_version_bootcheck I understand from other posts that this is probably caused by my having two PERL installations but: a. I have no

Upgrade to F23 breaks PERL

I have seen many posts relating to this type of issue but no canonical way to fix it properly. Since updating to F23 (from F22) using dnf last night, many/all PERL programs are broken and give errors such as: fetch_modules: error loading required module Compress/Zlib.pm: Can't load '/usr

Re: F23: Seems sshd service not accepting connections

On 09/08/2016 11:43 AM, Ron Leach wrote: > Running F23/XFCE, with firewalld, and having commanded: > # systemctl start sshd.service > > /var/log/secure > > shows that sshd is opening port 22, and listening on 0.0.0.0 . > There is no entry suggesting a login attempt is recei

Re: F23: Seems sshd service not accepting connections

<ronle...@tesco.net> wrote: > Running F23/XFCE, with firewalld, and having commanded: > # systemctl start sshd.service > > /var/log/secure > > shows that sshd is opening port 22, and listening on 0.0.0.0 . > There is no entry suggesting a login attempt is received. > &

F23: Seems sshd service not accepting connections

Running F23/XFCE, with firewalld, and having commanded: # systemctl start sshd.service /var/log/secure shows that sshd is opening port 22, and listening on 0.0.0.0 . There is no entry suggesting a login attempt is received. In the XFCE GUI for firewalld, everything is running in zone labelled

Re: F22 -> F23 -> F24 ?

On Fri, 2016-08-12 at 18:03 -0400, Jon LaBadie wrote: > Love it!! First three responses are: > > 1. Yes, designed to work that way > 2. Not recommended > 3. Better do a fresh install What's wrong with that? It contains all the answers that different people want to hear. ;-) -- All mail

Re: F22 -> F23 -> F24 ?

On Fri, Aug 12, 2016 at 4:03 PM, Jon LaBadie wrote: > On Fri, Aug 12, 2016 at 02:59:49PM -0400, Jon LaBadie wrote: >> Planning on taking my F22 desktop to F24 soon. >> >> Just want to confirm that trying to skip a >> release ist verboten. :( >> > Love it!! First three responses

Re: F22 -> F23 -> F24 ?

next best bet is to: F22->F23 "dnf --refresh upgrade" F23->F24 I haven't used the dnf upgrade mechanism to skip a release, but the old fedup often times had issues doing that. Hence my reticence to recommend it. fedup (dnf system-upgrade) is supposed to handle

Re: F22 -> F23 -> F24 ?

responses are: 1. Yes, designed to work that way 2. Not recommended 3. Better do a fresh install :) I think the real concensus is "F22->F24 is probably doable, but not recommended". The safest way is to back up and do a fresh install. The next best bet is to: F22->

Re: F22 -> F23 -> F24 ?

esponses are: > > 1. Yes, designed to work that way > 2. Not recommended > 3. Better do a fresh install > > :) I think the real concensus is "F22->F24 is probably doable, but not recommended". The safest way is to back up and do a fresh install. The ne

Re: F22 -> F23 -> F24 ?

On Fri, Aug 12, 2016 at 02:59:49PM -0400, Jon LaBadie wrote: > Planning on taking my F22 desktop to F24 soon. > > Just want to confirm that trying to skip a > release ist verboten. :( > Love it!! First three responses are: 1. Yes, designed to work that way 2. Not recommended 3. Better do a

Re: F22 -> F23 -> F24 ?

Upgrades are ultimately non-deterministic, for all sorts of reasons, so at some point it makes more sense to just clean install and suffer redoing customizations. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options:

Re: F22 -> F23 -> F24 ?

On 08/12/2016 11:59 AM, Jon LaBadie wrote: > Planning on taking my F22 desktop to F24 soon. > > Just want to confirm that trying to skip a > release ist verboten. :( I don't think it's verboten, but it's not a great idea. Ideally you'd upgrade to F23, do a full-boat update, then mo

Re: F22 -> F23 -> F24 ?

On 08/12/2016 11:59 AM, Jon LaBadie wrote: Planning on taking my F22 desktop to F24 soon. Just want to confirm that trying to skip a release ist verboten. :( I believe that with F24 it was intended that going from F22 to F24 should work. -- users mailing list users@lists.fedoraproject.org To

F22 -> F23 -> F24 ?

Planning on taking my F22 desktop to F24 soon. Just want to confirm that trying to skip a release ist verboten. :( Jon -- Jon H. LaBadie jo...@jgcomp.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options:

Re: F23 : DBus.Error.NoReply: can't enable bluetooth.

ssue. Also, BT and wireless share the same hw switch. Wireless works fine under F23, only BT fails. sean -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Con

Re: F23 : DBus.Error.NoReply: can't enable bluetooth.

On Sat, Aug 06, 2016 at 03:07:49PM -0400, sean darcy wrote: > On a dual boot lenovo laptop, bluetooth works on windows, but not fedora. > > The kernel finds bluetooth: > > dmesg | grep Bluet > [ 16.369045] Bluetooth: Core ver 2.21 > [ 16.372683] Bluetooth: HCI device and connection manager

F23 : DBus.Error.NoReply: can't enable bluetooth.

On a dual boot lenovo laptop, bluetooth works on windows, but not fedora. The kernel finds bluetooth: dmesg | grep Bluet [ 16.369045] Bluetooth: Core ver 2.21 [ 16.372683] Bluetooth: HCI device and connection manager initialized [ 16.373928] Bluetooth: HCI socket layer initialized [

Re: F23, Nouveau, and GeForce 750 Ti

Allegedly, on or about 02 August 2016, Justin Moore sent: > Rebooting into single user and re-doing the install process for the > video drivers would work, but it was a real pain to do that every time > (the power in our neighborhood is ... finicky, so reboots are sadly a > frequent-ish

Re: F23, Nouveau, and GeForce 750 Ti

veau can't do things like hardware acceleration on a two year-old card then I might have to switch back to the NVidia drivers. -jdm The only issue I have had with the latest F23/24 is in F24 and the latest kernel without signed drivers. akmods-nvidia wouldn't allow the module to be loaded if

Re: F23, Nouveau, and GeForce 750 Ti

> > > Can anyone help me understand whether VDPAU is even supported on my > > hardware/kernel/driver combination, and if so, what I need to do to get > it > > to work? > > I don't know about that, but I do know that on F24 the nouveau > driver would freeze up solid as a rock once every few days >

Re: F23, Nouveau, and GeForce 750 Ti

On Tue, 2 Aug 2016 08:35:40 -0400 Justin Moore wrote: > Can anyone help me understand whether VDPAU is even supported on my > hardware/kernel/driver combination, and if so, what I need to do to get it > to work? I don't know about that, but I do know that on F24 the nouveau driver would freeze

F23, Nouveau, and GeForce 750 Ti

I have a GeForce 750 Ti card and I'm having issues with stability and features with the nouveau driver on Fedora 23. Per lspci, I have NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) and kernel 4.6.4-201.fc23.x86_64. It appears that I'm running into the same (or a similar) issue as here:

Re: captive portal SSL certificate issue on F23

On 07/09/2016 03:55 PM, Fernando Cassia wrote: > > On Fri, Jul 8, 2016 at 5:20 AM, Frederic Muller <f...@cm17.com > <mailto:f...@cm17.com>> wrote: > > I am on F23 at the moment > > > You dont say which browser you use, and Fedora flavor. > For instan

Re: captive portal SSL certificate issue on F23

On Fri, Jul 8, 2016 at 5:20 AM, Frederic Muller <f...@cm17.com> wrote: > I am on F23 at the moment You dont say which browser you use, and Fedora flavor. For instance, on Fedora XFCE, the default browser is Midori. On more vanila Fedora versions, its usually Firefox FC -- Dur

Re: captive portal SSL certificate issue on F23

on that connection. Any idea what this could be and how to > "clean it up" to go back to the working mode ;-) > > I am on F23 at the moment. > > Thank you. > > Fred > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change

captive portal SSL certificate issue on F23

it up" to go back to the working mode ;-) I am on F23 at the moment. Thank you. Fred -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedorap

Re: Strange messages from sudo dnf repoquery --unsatisfied after upgrade from F23 to F24.

ld list the installed one from "@@commandline" and under "Available Packages" the ones available from Negativo17 and rpmfusion. I'm not running akmod-nvidia on my F23 box, but searching for any "akmod*" stuff: [root@prophead ~]# dnf list akmod* Last metadata expirati

Re: Strange messages from sudo dnf repoquery --unsatisfied after upgrade from F23 to F24.

tivo17 repository and an > uninstalled version in the Rpmfusion repository? I would think under "Installed Packages" it would list the installed one from "@@commandline" and under "Available Packages" the ones available from Negativo17 and rpmfusion. I'm not running akmo

Re: Strange messages from sudo dnf repoquery --unsatisfied after upgrade from F23 to F24.

On 07/07/16 09:49, Ed Greshko wrote: On 07/07/16 06:10, Stephen Morris wrote: Thanks Ed. I issued the command and got back Packager: None. I then tried the same command on a package that I know only exists in the Negativo17 repositories and that gave the same response of Packager : None.

  1   2   3   4   5   >