Taskbar Panel in Plasma Won't Autohide
by Stephen Morris
Hi,
I am trying to get the Taskbar Panel to autohide, but when I click on
the options button in the panel, the left, right and center options are
permanently highlighted but seem to function in terms of moving the
indicator that reflects which option is active. Also the 'Always
Visible', 'Auto Hide', 'Windows can Cover' and 'Windows go Below'
options are also permanently highlighted but selecting the 2nd or 3rd
option does nothing. It appears these options are highlighted because
the colour scheme I am using, which is forget-me-not thinks they are
push buttons.
Does anyone know why these don't work anymore in Fedora 23? I am using
Breeze for the Windows Style and Windows Decorations themes.
regards,
Steve
7 years, 7 months
F21: Thunderbird insists on calling Fedora list messages junk!
by William Mattison
Good afternoon,
Most messages received from this fedora list are labelled junk by
Thunderbird. This is even though I whitelisted "From" =
"users-request(a)lists.fedoraproject.org". Actually, I have this problem
both in my Fedora-21 and my windows-7 systems. Any ideas? Surely
messages from this list are not junk!
thanks,
Bill.
7 years, 10 months
enp0s8 not configured notification popups every few minutes (annoying)
by Kenneth Wolcott
Hi;
enp0s8 not configured notification popups every few minutes (annoying)
I just installed Fedora Live 64-bit KDE as a VirtualBox Guest OS.
I want to have two VirtualBox ethernet interfaces:
One for the vm to "see" outwards (NAT Network) and
Two for me to ssh into it (Host-only) so that I'm not forced to use
the console.
Every few minutes (it seems like every few seconds), I get a
notification popup that states that enp0s8 is not configured and then
a notification popup that it is being disabled.
How do I configure my outgoing ethernet interface?
I used to edit a file called something like /etc/network*/interface
and then I could change the default DHCP setting to be static and the
default disabled (off) setting to be enabled (on).
How does one do that kind of stuff now?
Is that a systemd thing?
Thanks,
Ken Wolcott
7 years, 10 months
installing via VNC over ipv6
by Chris Murphy
This suggests installation using vnc over ipv6 is supported:
https://fedoraproject.org/wiki/Anaconda/Features/Ipv6OnlyInstallation
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
connect:
vncviewer.desktop[12590]: 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
successfully.
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.
--
Chris Murphy
7 years, 10 months
Balsa -
by Bob Goodwin
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
2.1.11)
** Message: protocol CMS: engine /usr/bin/gpgsm (home (null), version
(null))
** Message: protocol GPGCONF: engine /usr/bin/gpgconf (home (null),
version 2.1.11)
** 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
the problem?
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
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-23/64bit LINUX XFCE POP3
7 years, 11 months
Dual boot
by Celso Viana
Hi all,
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
Thanks!
--
Celso Vianna
BSD User: 51318
http://www.bsdcounter.org
Palmas/TO
7 years, 11 months
Re: Posting to the Fedora message boards
by Tom Horsley
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 :-).
7 years, 11 months
Fedora 23 (4.4.9-300.fc23) ZFS problem after reboot
by Maikel van Leeuwen
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
modprobe zfs
zpool import
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
7 years, 11 months
Re: audio problems
by stan
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 (?)
> https://bugzilla.redhat.com/show_bug.cgi?id=1115762
> https://gil.fedorapeople.org/pulseverbose.log
> regards
> .g
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
http://www.alsa-project.org/main/index.php/Help_To_Debug
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
link.
7 years, 11 months