USB Wireless Card Support in Linux
by Stephen Morris
Hi,
I have just upgraded my USB Wireless Adapter from a Dlink DWA182 to
a Dlink DWA192. The DWA192 appears to be natively supported in the
kernel, but the kernel appears to only provide access to the 2.4MHz
channel and not the 5MHz channel. Is this by design or is there
something I need to do to get access to the 5MHz channel?
regards,
Steve
8 years, 2 months
Movie playback from smb shares
by Anca Tibor Attila
Hi,
is there a simple way to play movies from a smb share? I use KDE,
Dragonplayer is not willing to play anything beyond local.
Thanks in advance!
--
Tibor
I use OpenSource
Scanned by ClamAV
8 years, 2 months
Firefox 44 removes privacy feature.
by Robin Laing
For those that like to control how sites track you, you may want to
think again about using Firefox 44.
As of now, the cookies settings don't have the option to "Ask Me Every Time"
Choice is to accept or deny all cookies from a site.
I for one, like to know if I am being asked for cookies or not from a
site and accept at my preference.
This is the "bug" discussing this change. If this is important to you,
then please add your comments.
https://bugzilla.mozilla.org/process_bug.cgi
8 years, 2 months
Fw: Re: Fwd: Re: Xounal PDF Quality
by Patrick Dupre
Hello,
I am passing you this email exchange.
You may consider to update xournal at the end.
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
> Sent: Sunday, February 07, 2016 at 7:52 PM
> From: "Denis Auroux" <auroux(a)math.berkeley.edu>
> To: "Patrick Dupre" <pdupre(a)gmx.com>
> Subject: Re: Fwd: Re: Xounal PDF Quality
>
> Hi Patrick,
>
> Glad to hear that "legacy PDF export" solves the issue for you. The
> official Fedora package is likely to be based on official 0.4.8 (hence,
> a year old and not correcting all the bugs), though I don't know what
> exactly they might or might not have fixed in the -4 package iteration.
> So you'd need to uninstall it and compile manually instead from
> GIT/CVS if you really wanted to -- but it sounds like you don't need to...
> Best,
> Denis
>
>
> On 02/07/2016 10:49 AM, Patrick Dupre wrote:
> >>
> >> Hi Andreas + Patrick,
> >>
> >> Very strange and surprising. Two comments:
> >>
> >> 1. are you using the plain official 0.4.8 release, or a more recent
> >> version compiled from the GIT or CVS repositories on sourceforge ?
> > xournal-0.4.8-3.fc22.x86_64
> > The
> >> GIT/CVS version corrects a bug in PDF export that most visibly resulted
> >> in loss of quality of scanned images inside PDFs, but might also affect
> >> other aspects of PDFs as well. So: if you are using the 'normal' 0.4.8
> >> release, please try upgrading to the latest cvs/git version and see if
> >> it fixes the issue.
> > This is the version of the distribution
> > I do not think that the last update:
> > xournal-0.4.8-4.fc23.x86_64.rpm would be different.
> >
> >> 2. in 0.4.8 there are two methods of exporting PDFs, the new one is used
> >> by default and should be better (apart from the serious loss of image
> >> resolution bug that was fixed in GIT/CVS and perhaps also the issue you
> >> just reported?), but you can also try the older one by selecting Options
> >> -> Legacy PDF export.
> >> When selected, the exported PDF should be much more faithful to the
> >> original whenever possible (but export will fail with certain PDF
> >> files), so I imagine the problem you report will certainly go away.
> > Yes you are right
> >
> >>
> >> The default ("new") PDF export option loads the existing PDF using
> >> poppler/cairo -- same libraries used by evince and other PDF viewers --
> >> and prints it to a new PDF with the annotations on top. (The bug
> >> corrected in cvs/git was that we forgot to specify optimal print quality
> >> settings when doing this printing, which caused some quality loss in
> >> some cases). The old ('legacy') PDF export hacks into the existing PDF
> >> code and adds the annotations to the existing pages, without any
> >> modification or "re-distilling" of the existing PDF, so it is more
> >> faithful when it works, but it fails for various kinds of
> >> encrypted/compressed PDF files.)
> >>
> >> Denis
> >>
> >>
> >>
> >>
> >> On 02/07/2016 08:16 AM, Andreas Butti wrote:
> >>> Hi Denis
> >>>
> >>> Patrick Dupre wrote me a mail, there is a Bug in the PDF export in
> >>> Xournal. It seems there is a problem with the stroken width.
> >>>
> >>> Do you know this problem?
> >>> Do you may have a look at it?
> >>>
> >>> Thank you.
> >>>
> >>>
> >>> Andreas
> >>>
> >>> -------- Weitergeleitete Nachricht --------
> >>> Betreff: Re: Xounal PDF Quality
> >>> Datum: Sat, 6 Feb 2016 21:32:04 +0100
> >>> Von: Patrick Dupre <pdupre(a)gmx.com>
> >>> An: andreasb123(a)users.sf.net
> >>>
> >>>
> >>>
> >>> Hello,
> >>> I am attaching 2 files demonstrating the issue.
> >>>
> >>> ===========================================================================
> >>> Patrick DUPRÉ | | email: pdupre(a)gmx.com
> >>> Laboratoire de Physico-Chimie de l'Atmosphère | |
> >>> Université du Littoral-Côte d'Opale | |
> >>> Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
> >>> 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
> >>> ===========================================================================
> >>> *Sent:* Saturday, February 06, 2016 at 8:34 PM
> >>> *From:* andreasb123(a)users.sf.net
> >>> *To:* patdupre(a)users.sf.net
> >>> *Subject:* Xounal PDF Quality
> >>>
> >>> Hi
> >>>
> >>> First: I couldn’t answer to your mail, because SF was down...
> >>>
> >>> Xournal shouldn't change the Image quality...
> >>>
> >>> I cannot help you now, you may write to the mailing list:
> >>> https://sourceforge.net/p/xournal/mailman/xournal-devel/
> >>>
> >>> You may also would like to try out Xournal++, it's a rewrite of Xournal,
> >>> it can open your .xoj files.
> >>> https://github.com/xournalpp/xournalpp
> >>>
> >>> But I cannot guaranty that this will work better for your case.
> >>>
> >>> Only one idea: If you print your existing PDf to a PDF printer, it may
> >>> fix the problem. (If the PDF was faulty, you never know...)
> >>>
> >>> ------------------------------------------------------------------------
> >>>
> >>> This message was sent to you via the SourceForge web mail form.
> >>> You may reply to this message directly, or at
> >>> <http://sourceforge.net/u/andreasb123/profile/send_message>http://sourceforge.net/u/andreasb123/profile/send_message
> >>>
> >>>
> >>>
> >>
> >> --
> >> Denis Auroux
> >> University of California, Berkeley auroux(a)math.berkeley.edu
> >> Department of Mathematics Tel: 510-642-4367
> >> 817 Evans Hall # 3840 Fax: 510-642-8204
> >> Berkeley, CA 94720-3840
> >>
>
> --
> Denis Auroux
> UC Berkeley, Department of Mathematics
> 817 Evans Hall, Berkeley CA 94720-3840, USA
> auroux(a)math.berkeley.edu
>
8 years, 2 months
Is there something like denyhosts for sasl dictionary attacks?
by William Oliver
Is there something like denyhosts for sasl attacks? I'm getting tired
of stuff like this:
Jan 31 04:52:38 hope saslauthd[1333]: do_auth : auth failure:
[user=abby] [service=smtp] [realm=billoblog.com] [mech=pam] [reason=PAM
auth error]
Jan 31 04:57:35 hope saslauthd[1335]: do_auth : auth failure:
[user=abby] [service=smtp] [realm=billoblog.com] [mech=pam] [reason=PAM
auth error]
Jan 31 05:22:05 hope saslauthd[1334]: do_auth : auth failure:
[user=abby] [service=smtp] [realm=billoblog.com] [mech=pam] [reason=PAM
auth error]
Jan 31 06:40:05 hope saslauthd[1337]: do_auth : auth failure:
[user=info] [service=smtp] [realm=billoblog.com] [mech=pam] [reason=PAM
auth error]
Jan 31 06:40:07 hope saslauthd[1336]: do_auth : auth failure:
[user=info] [service=smtp] [realm=billoblog.com] [mech=pam] [reason=PAM
auth error]
Jan 31 06:40:09 hope saslauthd[1333]: do_auth : auth failure:
[user=info] [service=smtp] [realm=billoblog.com] [mech=pam] [reason=PAM
auth error]
etc.
8 years, 2 months
sending data to usb port
by Hiisi
Hi!
Imagine I have some device connected to USB port. Is it possible to send
some code directly to that port?
Here's what I'm trying:
# echo "0" > /dev/bus/usb/004/010
-bash: echo: write error: Invalid argument
--
Hiisi.
Registered Linux User #487982. Be counted at: https://linuxcounter.net/
--
Spandex is a privilege, not a right.
8 years, 2 months
OT: A suggestion for smplayer
by JD
TO be able to select a particluar sequence of tracks to play
without having to re-arrange the displayed playlist.
8 years, 2 months
PXE Fedora 23 with Anaconda 20?
by Dave Close
I've been trying to get a new working PXE installation for F23 and it
isn't working. I just noticed what might be the problem. Although
I downloaded the vmlinuz and initrd.img from the F23 server
version archive, when the installation starts it shows F20 in the
upper-right and checking via Alt-F2 shows that it is Anaconda v20
that's running. What could be responsible for that? What part of my
PXE configuration might be wrong?
--
Dave Close
8 years, 2 months
error setting up base repository
by CLOSE Dave
The subject message sometimes appears on the installation source entry
from anaconda. But I have never been able to find a good way to learn
just what the error is. Sure, sometimes it's obvious: the URL is wrong.
But other times everything seems to be correct but still the error
persists. I'm looking for a checklist of possible causes or a log entry
that corresponds to the problem.
In my present effort, I'm attempting to use a local mirror of the
fedora-updates repository (in addition to local mirrors of the fedora
and other repositories). I believe the mirror is correct and complete.
The machine being installed has no trouble accessing the repo from an F2
shell while anaconda is running. Looking through the anaconda logs, I
find lots of references to the update repository but no errors.
What can cause this error message? And how do I find out what caused it
in this instance?
--
Dave Close
8 years, 2 months
Failed to start IPv4 firewall with iptables
by GUNA
Hello,
I have updated Fedora core 16 Kernel from 3.4.2 to 4.4.0. Once the
system is rebooted with new kernel 4.4.0, the iptables loaded but not
started.
// logs
Failed to start IPv4 firewall with iptables [FAILED]
See 'systemctl status iptables.service' for details.
Started IPv6 firewall with ip6tables [ OK ]
[root@localhost grub2]# systemctl status iptables.service
iptables.service - IPv4 firewall with iptables
Loaded: loaded (/lib/systemd/system/iptables.service; enabled)
Active: failed since Wed, 27 Jan 2016 09:20:39 -0500; 5h 7min ago
Process: 936 ExecStart=/usr/libexec/iptables.init start (code=exited,
status=1/FAILURE)
CGroup: name=systemd:/system/iptables.service
After started the service manually, then the iptables started as follows:
systemctl start iptables.service
systemctl status iptables.service
iptables.service - IPv4 firewall with iptables
Loaded: loaded (/lib/systemd/system/iptables.service; enabled)
Active: active (exited) since Fri, 01 Jan 2010 14:52:20 -0500; 1s ago
Process: 18474 ExecStart=/usr/libexec/iptables.init start
(code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/iptables.service
Here are the rules:
more /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-I FORWARD -m physdev --physdev-is-bridged -j ACCEPT
COMMIT
I rebuilt the kernel and tested with all of the Netfilter options on,
but issue remains same.
Please confirm iptables v1.4.12 is compatible with latest Kernel 4.4.0 as well.
Is there any changes in sequence of starting services (during boot) in
latest Kernel?
Note, the ip6_tables loaded and started without any issue.
Any help is appreciated.
Thank you,
Guna
8 years, 2 months
