This suggests installation using vnc over ipv6 is supported:
But when I use inst.vnc boot option, I get an text screen that says to
connect to an ipv4 address, an ipv6 address isn't listed. When I go to
a shell and use 'ip addr' there is a global ipv6 address, but no
formatting for tigervnc I've come up with will connect, it won't
vncviewer.desktop: CConn: unable connect to socket:
Invalid argument (22)
If I boot Fedora 23 Server on this same hardware, the 'ip addr'
address can be used successfully to ssh into the server, and also
point a browser to https://[ipv6]:9090 to reach the Cockpit interface
root 1744 0.0 0.9 251060 36468 pts/0 Sl+ 03:29 0:00 Xvnc
:1 -depth 16 -br IdleTimeout=0 -auth /dev/null -once
DisconnectClients=false desktop=Fedora rawhide installation on host
10.0.0.15 SecurityTypes=None rfbauth=0
I can't tell if -InTransports needs to explicitly specify ipv6 for it
to work. But at this point I'm stumped and can't tell if it's user
error or a bug. And netstat isn't on non-live media apparently so I
don't have access to that while xvnc is running to see if it's
listening over something other than just an ipv4 address.
I have installed Balsa in this updated Fedora 23 computer, it runs but
will not connect to the mail server.
I can click on "check" and it appears to be checking for mail but
produces an error message ending in "ERR Invalid Command." I've been
through the account set up process again thinking I may have had a typo,
but still no luck.
Also after having run Balsa from a terminal I see the following:
(balsa:22220): Gtk-WARNING **: Failed to register client:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
** Message: init gpgme version 1.4.3
** Message: protocol OpenPGP: engine /usr/bin/gpg2 (home (null), version
** Message: protocol CMS: engine /usr/bin/gpgsm (home (null), version
** Message: protocol GPGCONF: engine /usr/bin/gpgconf (home (null),
** Message: protocol Assuan: engine /home/bobg/.gnupg/S.gpg-agent (home
!GPG_AGENT, version 1.0)
** Message: protocol UIServer: engine /home/bobg/.gnupg/S.uiserver (home
(null), version 1.0)
** Message: OpenPGP protocol supported
** Message: CMS protocol not supported, S/MIME will not work!
Network is available (Tue May 10 16:31:42 2016)
So "** Message: CMS protocol not supported, S/MIME will not work!" is
Can I fix that? If so what must I do ...
I've tried this running both xfce and gnome in Fedora 23 and in a VM
with Fedora 24b, the result is always the same, I can't collect any mail
with balsa ... Same error message.
Any thoughts appreciated,
Bob Goodwin - Zuni, Virginia, USA
box10 FEDORA-23/64bit LINUX XFCE POP3
You know if you can dual boot with GPT and BIOS disks on the same machine?
/dev/sdb GPT -> Windows 10
/dev/sda BIOS -> Fedora 23 x64
The machine only starts with Windows; not appear the boot menu
BSD User: 51318
On Tue, 31 May 2016 12:11:40 -0400
Paul W. Frields wrote:
> You might want to file an enhancement request for Hyperkitty to add a
> feature for this.
I would have thought it was just css setup by whoever runs the
hyperkitty web site to make it looks like whatever they want.
If it is hard coded and not css, then hyperkitty needs a much
much bigger enhancement request :-).
Yesterday I upgraded a Fedora server to 4.4.9-300.fc23.x86_64, after the
reboot all my ZFS pools where
gone. After some fiddling and testing I created these set of steps to
solve the problem:
dnf remove zfs
dnf install zfs
zpool import -D
zpool import raid1
zfs mount -a
Can somebody acknowledge the same problem and is this to be more expected in the future?
ZFS version: zfs-0.6.5.7-1.fc23.x86_64
On Tue, 31 May 2016 00:50:48 +0200
gil <puntogil(a)libero.it> wrote:
> Il 30/05/2016 16:30, stan ha scritto:
> > At least, you now know what the issue is. If you need an older
> > kernel, and don't have one installed, you can go here,
> > http://koji.fedoraproject.org/koji/packageinfo?packageID=8
> > and pick up older kernel packages for your OS version, and install
> > them using
> > dnf -C install [kernel rpm package names here]
> > You could edit /etc/dnf/dnf.conf to up the number of kernels you
> > keep by 1 to provide space without removing an existing kernel
> > install.
> also alsa-lib (1.1.1) "seem" affected (?)
I think I cannot help you further with this. It's into serious
coding territory, rather than configuration help. But, I recommend that
you go here
and download the alsa-info.sh script, and run it.
Then post to the user or developer mailing list for alsa, attaching
or with a link to the output of that script, describing your problem.
They are experts in alsa, and will be more familiar with any issues.
The links to those mailing lists are on the same page as the script
-------- Messaggio Inoltrato --------
Oggetto: Re: audio problems
Data: Mon, 23 May 2016 10:14:00 +0200
Mittente: gil <puntogil(a)libero.it>
Rispondi-a: Development discussions related to Fedora
Il 23/05/2016 09:41, Samuel Sieb ha scritto:
> On 05/22/2016 03:06 AM, gil wrote:
>> Internal Audio Stereo analogic
>> GK208 HDMI/DP Audio Controller Digital stereo
> Is the internal audio output and not the HDMI selected?
sorry what you do mean?
"GK208 HDMI/DP Audio Controller Digital stereo" is the audio device in
my video card
04:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller
Subsystem: ASUSTeK Computer Inc. Device 8576
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
i must use the
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00
Azalia (Intel HDA) (rev 40)
Subsystem: ASRock Incorporation Device 0892
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
but is not listed in kde pannel control ...
>> aplay -l
>> **** List of PLAYBACK Hardware Devices ****
>> card 0: SB [HDA ATI SB], device 0: ALC892 Analog [ALC892 Analog]
>> Subdevices: 1/1
>> Subdevice #0: subdevice #0
> This shows that alsa knows about your hardware.
> Run alsamixer in a terminal. You should get a single volume control
> for the pulseaudio output. Make sure that it is up and not muted.
> Press F6 to select a different device and select 0, your HDA device.
> Check that the volume controls and switches are set correctly.
> Normally, pulseaudio should manage it, but this gives you a chance to
> verify and test.
already done but dont solve anythings
> devel mailing list
devel mailing list
I've used linux on my desktop in the past with great joy and I would like to start using it again, but I'm running into some accessibility problems. I'm visually impaired, and I need some aids to use a computer. The two things that I absolutely depend on are the ability to invert screen colors (black becomes white and vice versa) and some way to make the mouse cursor more visible.
I currently use Mac OS, which has a builtin option to invert screen colors, and I use a third party application called Pin Point to draw a blue circle around the mouse pointer.
As far as I can tell Gnome 3 does not have a builtin option to invert screen colors, I have solved this in the past by just using Gnome 2 with Compiz, which has a plugin to invert the colors. Also KDE has this feature, so it should be no problem to get this working properly.
However, I cannot find a way to make the cursor more visible. I tried to write a little c program that can draw a circle around the cursor but I can't get it to properly work. On OS X my mouse looks like this , the cursor would be inside the blue circle, but is not visible in the screenshot.
Anyway, I'm looking for suggestions to solve this problem so I can use Linux on my desktop once again.
I would like to install texmaker, but dnf wants to install a full
texlive.... I have already installed texlive from CTAN and I don't want
to have two texlive on may machine.
How can I get rid of dependencies?
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
I have a Samsung S Action Mouse ET-MP900D that I'm trying to connect from
my laptop: Asus U36SD with Fedora 23.
I can pair and connect to the mouse both from a Samsung S2 phone and from a
Samsung Pro 12.2 tablet.
I remember in the past on the same PC with Fedora 21 I was able to connect
to this mouse.
But now on fedora 23 I get:
[root@ope46 ~]# bluetoothctl
[NEW] Controller 74:2F:68:83:D4:3F ChromeLinux_D1F5 [default]
[NEW] Device E4:B0:21:98:DB:CA GT-I9100
[NEW] Device F0:65:DD:80:A3:0E Samsung S Action Mouse ET-MP900D
[bluetooth]# info F0:65:DD:80:A3:0E
Name: Samsung S Action Mouse ET-MP900D
Alias: Samsung S Action Mouse ET-MP900D
UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
[bluetooth]# connect F0:65:DD:80:A3:0E
Attempting to connect to F0:65:DD:80:A3:0E
Failed to connect: org.bluez.Error.Failed
[root@ope46 ~]# systemctl status bluetooth -l
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled;
vendor preset: enabled)
Active: active (running) since Thu 2016-05-26 12:43:46 CEST; 20min ago
Main PID: 789 (bluetoothd)
May 26 12:44:37 ope46 bluetoothd: Can't get HIDP connection info
May 26 12:44:37 ope46 bluetoothd: connect error: Connection refused
May 26 12:44:57 ope46 bluetoothd: Can't get HIDP connection info
May 26 12:44:57 ope46 bluetoothd: connect error: Connection refused
May 26 12:58:41 ope46 bluetoothd: Can't get HIDP connection info
May 26 12:58:46 ope46 bluetoothd: connect error: Host is down (112)
May 26 12:59:26 ope46 bluetoothd: Can't get HIDP connection info
May 26 12:59:31 ope46 bluetoothd: connect error: Host is down (112)
May 26 13:03:07 ope46 bluetoothd: Can't get HIDP connection info
May 26 13:03:12 ope46 bluetoothd: connect error: Host is down (112)
Tried also from mate and from kde sessio s with same results.
Device added successfully, but failed to connect
Connection Failed: blueman.bluez.errors.DBusFailedError: Input/output error
I also found some reference to create file /etc/sysconfig/bluetooth and
But after done and reboot same behavior.
How to debug further?
Thanks in advance.