Unwanted blinking notice -
by Bob Goodwin
.
In Thunderbird, when I click on a URL in a message it does what I expect
it to and I don't need re-assurance the it has!
It brings up a flashing notification in the top left corner that I would
like to eliminate. Does anyone have a fix for that?
This is an updated F22/64bit system.
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-22/64bit LINUX XFCE
8 years, 9 months
RE: UPS shutdown happens how?
by J.Witvliet@mindef.nl
-----Original Message-----
From: users-bounces(a)lists.fedoraproject.org [mailto:users-bounces@lists.fedoraproject.org] On Behalf Of Tom Horsley
Sent: dinsdag 2 juni 2015 16:54
To: Community support for Fedora users
Subject: UPS shutdown happens how?
I just got a new UPS at work which has a USB cable connection.
If I look at the power settings in gnome-control-center, it claims to know I'm on a UPS, so I guess it knows how to talk to it.
I told it to shutdown when battery power is critical, but I'm wondering who the heck recognizes that. I don't run a gnome session, so is there some daemon that needs to be working for it to actually shutdown cleanly?
-----Original Message-----
As with all in Linux-realm, there are several ways to obtain something.
Not all UPS has a proper working intercase, or have one that is not compatible.
A friend of mine solved it in a different way: On his UPS-protected machine, he pinged every minute a small box that is not UPS-protected.
No reply? Decent shutdown! Also easy to test...
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
8 years, 9 months
Anybody succeful as normal user in F22 with (x)sane together with an USB scanner?
by Joachim Backes
Hi all,
since some days I have problems to scan by using xsane together with my
CANON Lide30 USB scanner: it seems to have access problems. I have to
run xsane together with sudo. Running sane-find-scanner reports access
problems too, but "sudo sane-find-scanner" will not report such access
problems.
I'm running F22 since the Alpha release with all updates applied, and
never had such scanner problems!
Seems not to be a kernel problems because /usr/bin/simple-scan scans
flawlessly!
lsusb:
Bus 002 Device 005: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30
Bus 002 Device 004: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical
Wheel Mouse
Bus 002 Device 003: ID 046d:081d Logitech, Inc. HD Webcam C510
Bus 002 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Anybody has similar problems?
Kind regards
Joachim Backes
--
Fedora release 22 (Twenty Two)
Kernel-4.0.4-303.fc22.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
8 years, 9 months
error trying to enable copr
by William Biggs
When I try to add copr repo . I type sudo dnf copr enable user/project
. and When I get y I get this error . How do I get this to work
Error: [Errno 2] No such file or directory:
'/etc/yum.repos.d/_copr_user-project.repo
8 years, 9 months
RE: I'm shocked, shocked!
by J.Witvliet@mindef.nl
-----Original Message-----
From: users-bounces(a)lists.fedoraproject.org [mailto:users-bounces@lists.fedoraproject.org] On Behalf Of Michael Hennebry
Sent: dinsdag 2 juni 2015 7:20
To: Community support for Fedora users
Subject: RE: I'm shocked, shocked!
On Mon, 1 Jun 2015, J.Witvliet(a)mindef.nl wrote:
> -----Original Message-----
> From: users-bounces(a)lists.fedoraproject.org
> [mailto:users-bounces@lists.fedoraproject.org] On Behalf Of Tom H
> Sent: zondag 31 mei 2015 15:23
> To: Fedora Users
> Subject: Re: I'm shocked, shocked!
>
> On Sat, May 30, 2015 at 1:37 PM, Tom Horsley <horsley1953(a)gmail.com> wrote:
>>
>> To see that the "predictable" network name for my one and only
>> ethernet port has changed once again.
>> On fedora 22 eno1 is what used to be em1.
>
> That's because you've moved from one "predictable" scheme to another...
That is not a good enough excuse.
*By design*, Fedora is a high-turnover distribution.
Changing a naming scheme that security software relies on is a big deal.
I'd suggest two utilities.
One would record the current names and
their mac addresses in a plain text file.
The other would take such a file and update a configuration file to associate the names and mac addresses.
The format of the file should remain constant between releases.
-----Original Message-----
I wasn't looking for an excuse.
And it is not only security related, but more general networking.
At how many places do you have to specify the name of your network device, and perhaps have to differentiate...
Not just iptables, but routing, bridging, monitoring, building virtualized clients, etc etc etc
No progress without change, but changing device-names isn't a trivial thing.
I could write scripts on a test-machine, not needing to know the hardware layout of any intended target machines.
Now I do need to know, or need to script around it. That is still fun, but changing documentation for real-end-users aint. :-)
Hw
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
8 years, 9 months
Fedora22 - run remote graphical program on local display
by Todor Petkov
Hi,
when I log from my workstation (Fedora 22) and I have problems with
running firefox on remote (virtual) machines:
1) Fedora22 - When I start firefox, it says:
(firefox:1345): GLib-GObject-WARNING **: The property
GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore.
It will be removed in a future version.
(firefox:1345): GLib-GObject-WARNING **: The property
GtkSettings:gtk-button-images is deprecated and shouldn't be used
anymore. It will be removed in a future version.
Then a black window appears and I need to press ctrl-c in the shell to
kill the window, since there is no url bar, no menus, nothing.
2) Centos5: it says nothing (returns me to the shell prompt) and firefox
is started on the _local_ machine (?!)
3) Centos7 - no problem so far, firefox is started there and correctly
exported on the local display
Can anyone point me, why it fails in cases 1 and 2? Not to mention case2
- local firefox wtf?
Local ssh version: OpenSSH_6.8p1, OpenSSL 1.0.1k-fips 8 Jan 2015
server versions:
case1: OpenSSH_6.8p1, OpenSSL 1.0.1k-fips 8 Jan 2015
case2: OpenSSH_6.6.1p1, OpenSSL 1.0.1e-fips 11 Feb 2013
case3: OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
Thanks,
8 years, 9 months
RE: I'm shocked, shocked!
by J.Witvliet@mindef.nl
-----Original Message-----
From: users-bounces(a)lists.fedoraproject.org [mailto:users-bounces@lists.fedoraproject.org] On Behalf Of Tom H
Sent: zondag 31 mei 2015 15:23
To: Fedora Users
Subject: Re: I'm shocked, shocked!
On Sat, May 30, 2015 at 1:37 PM, Tom Horsley <horsley1953(a)gmail.com> wrote:
>
> To see that the "predictable" network name for my one and only
> ethernet port has changed once again.
> On fedora 22 eno1 is what used to be em1.
That's because you've moved from one "predictable" scheme to another...
em1 is a name assigned by biosdevname where "em" stands for "embedded"
(although I've seen an "ethernet on motherboard" explanation) and the generic name is "em<port_number>". The other biosdevname option is "p<slot_number>p<port_number> where the first "p" stands for "pci".
eno1 is a name assigned by udev where "en" stands for ethernet and "o"
for onboard. From "man systemd.link":
<<snip>>
-----Original Message-----
So, if you use Ethernet connection, based on the same sort of hardware, but one located on the MOBO, one on a PCI-card and one on a USB-connector, they all got different names. That's bad.
But even worse, it means that scripts designed for totally hardware agnostic configuration, now should determine where a piece of hardware is located. That's the inverse of progress....
I wonder if "old" behavior (like ETHnn) can be retrieved by NamePolicy ="database"
HW.
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
8 years, 9 months
kernel number in dnf
by Antonio M
I switched from yumex to umex-dnf. This morning a new kernel was found, but
I got 4 kernels installed, even if my dnf,conf sounds like:
[main]
gpgcheck=1
installonly_limit=3
clean_requirements_on_remove=true
why??
--
Antonio Montagnani
Skype : amontag52
Linux Fedora 21 (Twenty-one)
inviato da Gmail
8 years, 9 months