Many of us need akmods for our hardware.
But when the kernel crashes or ooops'es,
we are unable to send the crash report.
Since none of the crashes occur in the modules
inserted via akmods, why is the fedora abrt not
allowing thes ending of such reports?
At least provide a way for us to send them to
the place we got them from, namely rpmfusion
in this case, or other repos in other cases.
All abrt has to do is ask for the user's login
id and password and have it submit the report there.
I am at my wits end with this, so I thought I would post here to see if anyone had any thoughts. The only connection with F21 (updated in all installed components) is that everything is on a F21 machine.
So, I have a cifs share mounted onto /mnt/space using the usual mount.cifs option with sec=ntlmv2.
I wanted to copy the following directory (kmeans) onto /mnt/space -- because I wanted to preserve permissions and structure, I tried rsync:
rsync -avSz --delete --progress kmeans/. /mnt/space/kmnsinit
So here is the problem:
The original directory has size:
% du -sh kmeans
But the copying has continued on and on with no sign of ending (and we are at 378GB).
% du -sh kmnsinit
I also tried without the . after the kmeans/ in the rsync command (though not sure why it would matter) but to no avail. (Same story, and note that it is not ending at 378G but going on, and chances are will go on for some more.)
Is it possible that since all things Windoze are bad, the cifs puts stuff all over the place and represents large files differently. Is it possible to however make it behave?
Does anyone have an explanation and solution for the above? I apologize again for the largely OT nature of this post.
Many thanks and best wishes,
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 EARTH SCREENSAVER - Watch the Earth right on your desktop!
Check it out at http://www.inbox.com/earth
And yet another problem with Fedora-21...
When I press my Shift keys quickly a few times (which I often
do unconsciously while thinking about what to type), I get a
notification that "sticky keys have been enabled". I then
get a lot of odd keyboard effects such as every word typed
being capitalized or the keyboard acting like the control key
is permanently pressed.
Googling seems to indicate this is an old problem going back
to the mid-2000's.
I tried one of the solutions I found: install xkbset and run
"xkbset -a" at login time via Application Autostart tab in
the Settings and Startup dialog (this is Xfce).
That seemed to work for a while but the problem's come back.
The auto-startup setting is still there, still enabled.
While I was typing this, something called "slow keys became
enabled making it impossible to continue typing this message
until I logged out and back in again.
None of the options in the accessibility applet are enabled
(I'm pretty sure, having worked around the problem of dialogs
not showing checkmarks).
What do I need to do to permanently put a stake in the throat
of this nasty little Sticky Keys virus?
I seldom rant in public but I've got to say that installing
Fedotra-21 was the worst experience I have ever had installing
Linux (in terms of the endless amount of brokeness) -- and I
have been using Redhat going back to the 3.x days (that's *Redhat*,
not Redhat Enterprise; not Fedora). I don't think it is me. I
did a pretty plain vanilla install and except for some of the
usual audio/video stuff from rpmfusion, am using packages straight
out of the Fedora-21 repo. Plain vanilla hardware that ran
Fedora-15 fine for several years. Has Fedora become too focused
on release schedules and lost interest in quality control?
Or are all these problems coming from xfce?
I am learning Linux and, just in order to do exercises, I wanted to monitor
the functioning of services that, I thing, should run on fedora.
So, with the command : service *smartd* status
I got :
Redirecting to /bin/systemctl status *smartd.service*
● smartd.service - Self Monitoring and Reporting Technology (SMART) Daemon
Loaded: loaded (/usr/lib/systemd/system/smartd.service; enabled)
Active: active (running) since Tue 2015-03-31 07:48:18 IDT; 10h ago
Main PID: 701 (smartd)
└─701 /usr/sbin/smartd -n -q never
the same for *cups*....
● cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: active (running) since Tue 2015-03-31 07:48:51 IDT; 10h ago
but I was wonder that services as :
*DHCP, SAMBA*, ..... was not working.... :
the command : sudo service *samba* status
give me :
Redirecting to /bin/systemctl status samba.service
Loaded: not-found (Reason:* No such file or directory*)
Active: inactive (dead)
for *SAMBA* I give a look to check if it is installed, and I found:
sudo yum list installed | grep samba
samba-winbind-modules.x86_64 2:4.1.17-1.fc21 @updates
after this test I am confuse .......
What is the reason why some important services are not running by default
on Fedora 21?
Could I have an explanation ?
Xfce gives you the option to save your session on logout.
In earlier versions, all of my tabbed sessions of Gedit and Gnome-Terminal
would be restored.
Now, with an F21 setup, only Firefox comes up restored. At best, Gedit is
opened, but in a new document setting.
Any pointers on whether or not this can be changed so that Gedit and
Gnome-Terminal sessions are restored?
Or is this a new, undocumented feature?
I just moved from Fedora-15 to Fedora-21 and another breakage
that occurs is using Emacs with Ibus. I've been using Emacs
since the dark ages and I also need to enter and edit Japanese
This worked fine through many versions of Fedora and Ibus (or
its predecessors) up to Fedora-15 when I had to start running
Emacs with a command like "LC_TYPE=ja_JP.utf8 emacs" to get it
to accept Japanese characters.
Now in Fedora-21, the above command now longer works and I can't
find any way of getting Emacs to input Japanese characters other
than its own very awkward and poor built-in IME. It appears the
migration to a completely broken combination has been completed
Googling has not turned up much beyond a bunch of non-working,
contradictory or old information.
Is there any way to get Emacs to work with Ibus?
Sometimes, I want to view a youtube vid in full screen, which hides
the desktop and the panels.
In such cases, how can I take a screenshot of the workspace where I
am playing the youtube vid in full screen mode?
> "warn" isn't valid.
I know that now; looks like I mistook the Apache logging level names for
the Linux ones. I don't understand why an invalid log level would
generate an 'access denied' message instead of something more sensible,
like 'invalid log level'.
> Have you restarted systemd either by sending it a SIGHUP or doing
Yes, and rebooted the machine. Multiple times. No effect - I'm still
getting the "Invalid log level'warn'" message during boot even though
'warn' is no longer in system.conf.
Not sure if it's at all related, but the error message is in a section
of log/messages with bogus timestamps - 4 hours before the real time.
(Boot logs start off with the right time, says "Journal stopped", then
"journal: Runtime journal is using 4.0M (max allowed..." with the bogus
time, couple of pages of log entries with the bogus time, then repeats
"Journal stopped" w/ bogus time, then "journal: Runtime..." with the
correct one again.)
1. Why isn't systemd using the current version of the config file - even
systemctl daemon-reload, systemctl daemon-reexec, and reboots?
2. How do I get systemd to stop filling my log files with
Reached target Paths.
Reached target Timers.
Reached target Socket
I've been running reposync successfully for Fedora 20 for months. Now
I'd like to repeat the process for Fedora 21 while continuing to take
updates for F20 on the same machine. But it isn't working for me.
/usr/bin/reposync -n -a x86_64 -r fedora21 -p /data/yum-mirrors/x86_64
Error setting up repositories: no such table: packages
The exact same command works perfectly if I substitute fedora20. Both
are described in my .repo files exactly the same way.
Looking around, I see that most references to this error, not for
reposync but for other YUM commands, state that the solution is to clean
the RPM data base. I've done that. I've even re-created it from scratch.
I still get the same error.
Any other ideas?