enabling keybindings for brightness/volume, etc on laptop (F21 LXDE)
by Ranjan Maitra
Hi,
I am running a fully-updated F21 LXDE installed from the official spin. How does one enable the laptop keybindings for brightness, volume, etc? Do I need an additional package, etc?
Many thanks,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
____________________________________________________________
FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop!
Check it out at http://www.inbox.com/marineaquarium
9 years, 1 month
Raid vs rsync -
by Bob Goodwin
I had a mainboard fail in a box I use as a server, I moved the hard
drive into old computer and carried on from there. Now I've replaced the
board and intended to set it up using Raid to mirror two drives. However
I have been wondering if it wouldn't work just as well to periodically
rsync the drive in use with a second drive?
That seems a more direct approach and I could easily check to make
certain that the second drive was a usable copy, insurance against loss
of data.
Am I going wrong somewhere in my thinking?
Bob
--
http://www.qrz.com/db/W2BOD
box10 Fedora-21/64bit Linux/XFCE
9 years, 1 month
F21: Gnome doesn't work on i686 Dell Laptop
by Max Pyziur
Greetings,
Recently, I "fresh installed" F21 on a Dell i686 Inspiron Laptop.
I had been running F18 on it, and just wanted to jump to the newest
release w/o stepping through F19 and F20. I kept the /home partition, and
wiped everything else out.
Xfce and Mate Desktops start and are very functional.
Any variant of Gnome (new version and Classic) reports an equivalent
screen-of-death with the message reading "A problem has occurred, and the
system can't recover."
The /var/log/messages file is very extensive; it begins with:
Mar 18 19:06:49 MercToo systemd-logind: New session 14 of user pyz.
Mar 18 19:06:50 MercToo org.a11y.Bus: g_dbus_connection_real_closed:
Remote peer vanished with error: Underlying GIOStream returned 0 bytes on
an async read (g-io-error-quark, 0). Exiting.
Mar 18 19:06:50 MercToo org.a11y.atspi.Registry:
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0).
Exiting.
Mar 18 19:06:50 MercToo gdm: Child process 1024 was already dead.
Mar 18 19:06:50 MercToo gdm: Unable to kill session worker process
Mar 18 19:06:50 MercToo org.gtk.vfs.Daemon: A connection to the bus can't
be made
Mar 18 19:06:50 MercToo org.gtk.vfs.Daemon: g_dbus_connection_real_closed:
Remote peer vanished with error: Underlying GIOStream returned 0 bytes on
an async read (g-io-error-quark, 0). Exiting.
Mar 18 19:06:50 MercToo ca.desrt.dconf: g_dbus_connection_real_closed:
Remote peer vanished with error: Underlying GIOStream returned 0 bytes on
an async read (g-io-error-quark, 0). Exiting.
Mar 18 19:06:50 MercToo gnome-session: ** (gnome-settings-daemon:1136):
WARNING **: Name taken or bus went away - shutting down
...
and goes on like that.
I've done various "yum groupinstalls" hoping to get all of the various
missing dependencies and missing libraries. Obviously, I'm missing
something.
I noticed that someone (on a similar Gnome problem) said to check for a
list of services using systemctl to see if they are enabled; I did that,
and everything seems to be correctly enabled.
Is this problem resolvable on an i686 system? I'd like to resolve this
first, before upgrading my x86_64-based machines.
I have no loyalties to Gnome; I'd just like to function close to their
intended design. And take it as a sign of possible other problems in the
even that they don't.
Max Pyziur
pyz(a)brama.com
9 years, 1 month
F21 SSH sends TCP keep-alive - server RSTs
by Robert Moskowitz
For some reason, after LOTS of idle chatter between my F21 SSH client
and the server (I am assuming these are SSH application keep-alives), my
F21 SSH client sends a TCP keep-alive. This is after some long time of
the client NOT sending an SSH idle packet.
As soon as the server receives this TCP keep-alive, it sends a TCP RST
and that 'breaks the pipe'.
So what in the client determines the rate of SSH keep-alives and for how
long inactive?
Then with the app level inactive, why the TCP keep-alive?
Or do I take this question to the OpenSSH list?
9 years, 1 month
Cannot umount ntfs-36 with umount command
by dabicho
Hello
I am having a problem with umountint an ntfs-3g mounted filesystem
This is the output I get from the commands
[siirfe@010121 ~]$ mount /mnt/mac/
[siirfe@010121 ~]$ mount |grep mac
/dev/sdb1 on /mnt/mac type fuseblk
(rw,nosuid,nodev,noexec,relatime,user_id=1002,group_id=1002,allow_other,blksize=4096)
[siirfe@010121 ~]$ umount /mnt/mac/
umount: /mnt/mac: umount failed: Operation not permitted
[siirfe@010121 ~]$ grep mac /etc/fstab
/dev/disk/by-label/SIIRFE_MAC /mnt/mac auto
iocharset=utf8,noauto,user 0 0
[siirfe@010121 ~]$ grep mac /etc/mtab
/dev/sdb1 /mnt/mac fuseblk
rw,nosuid,nodev,noexec,relatime,user_id=1002,group_id=1002,allow_other,blksize=4096
0 0
[siirfe@010121 ~]$ fusermount -u /mnt/mac/
fusermount -u works correctly
What is going on here? what am I missing?
I don't use gnome nor kde
I appreciate any input. Thank you
9 years, 1 month
Re: Crashes of tainted kernels
by Chris Murphy
On Tue, Mar 17, 2015 at 10:57 PM, Tim <ignored_mailbox(a)yahoo.com.au> wrote:
> On Tue, 2015-03-17 at 21:22 -0600, Chris Murphy wrote:
>> Sounds like a UI bug.
>
> Agreed. And, it would appear, that becomes a "don't really care about
> fixing it" issue, as sound still works, even if the controls are
> backwards.
>
>> Are you talking about tainted kernels (3rd party, out of tree kernel
>> modules)? Or are you talking about something completely different?
>
> Standard Fedora install, out of the box.
>
> But I was just using that as an example of an experience with making bug
> reports.
OK no offense but that's close to hijacking the thread because it's
really that unrelated to tainted kernels. An ignored bug for package A
does not mean other bugs for other packages will be ignored. The
relationship between Fedora and upstreams is highly varied. The degree
to which Fedora packagers can manipulate upstream code is highly
varied. This is non-obvious, but it's an inevitable outcome to all
distro models. All of them have this problem to varying degrees.
A big quandry I think all Linux distros face is to what degree they
are, or can be, an OS, rather than merely a collection of packages.
The unwillingness, or inability, of distros to merely recommend let
alone insist, on upstream features or bug priorities really limits the
total end goal cohesiveness any Linux distro can get to in becoming
more of an OS. It's a huge challenge.
A big part of how Google has made Android an OS is essentially by
kicking out upstreams and replacing packages with those of their own
making. Windows and OS X are even more extreme examples. All video
drivers are all supplied by Apple with OS X, there is no such thing as
a 3rd party download.
The widening gap between developer and user continues to be a problem,
and self rewarding, and to some degree Linux distros are all accepting
this. Systems are getting a lot more capable, and a lot more
complicated, but the development environments are not scaling to users
the way they are for developers. The user as the developer is
increasingly left behind.
That's a big part of the Xerox PARC and early Apple story that was
fairly quickly abandoned by Apple - the idea of the user being the
developer, and everything being discoverable, understandable, and the
user had the source for all of it right in front of them on their
device by default.
How do you convince OSS developers to create the DE they've always
wanted for themselves that also makes them obsolete (or superfluous)?
And are those really the contradiction they seem to be?
--
Chris Murphy
9 years, 1 month
