Notification area audio widget suddenly invisible on Fedora LXDE spin
by Someone
My sound abruptly stopped working, and the notification area widget
stopped appearing. It hasn't been working for a couple of weeks, at this
point, though it had been working fine before that. (Before it stopped
working, the notification area widget had been displaying, as well.
I can run pavucontrol manually, and the only output device that is shown
in the relevant tab is "Dummy Output".
I really wish I could listen to music, but neither my laptop's built in
speakers, nor the stereo system plugged into the side audio jack work at
all.
As per the wiki sound troubleshooting page, I removed the
alsa-plugins-pulseaudio package, but that, alas, that didn't help, either.
Any suggestions would be appreciated.
Thanks.
10 years
Autofs startup
by Chris Kottaridis
I had autofs working in an older Fedora Release, 14 I know it's very
old. I am now trying to get the same autofs to work on my Fedora 19
host. The man page on the Fedora 19 host for autofs says there should be
a /etc/rc.d/init.d/autofs file. While this does exist in Fedora 14 it
does not in Fedora 19. The /usr/bin/automount file is installed on the
F19 host, along with the autofs man pages.
I assume this all has to do with the switchover to systemctl. When I
look at the services application, "Services Configuration", it doesn't
show autofs or automount anywhere.
How do I get autofs/automount to start up at boot time in Fedora 19 ?
Thanks
Chris Kottaridis
10 years
replacing /dev/sda- am I missing anything?
by Paul Cartwright
ok, well my error count went to 31 sectors on /dev/sda the other day..
I've been rcping /home over to a partition on sdb, so this morning,
before I opened email, I edited /etc/fstab, commented out /home, moved
my partition on /dev/sdb to /home and.... rebooted. SO, I didn't get
that error I have been getting where it always drops me to that enter
password or Control-D to continue, it just flat booted:)
so now I have an /dev/sda with .. nothing mounted . /dev/sda3 is my
windows 7 partition, sda2 I think is the Dell recovery partition, I
forget what sda1 is..
Yesterday I did a clonezilla disk copy of /sda to a spare partition on
sdb. It errored on my /dev/sda5 /home but copied the other partitions.
I also have a nice new 2TB drive sitting here in a box. If I just
replace the old 1TB drive with the new 2TB drive and do a clonezilla
restore, will I be able to boot to grub menu? does it copy the MBR?
suggestions/comments?? am I missing something??
running fedora 20 AMD_64, now sda 1TB, sdb 2TB.
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
10 years
Dual Boot System
by Javier Perez
Hi
I need some advice here regarding partitioning my home system.
My home system is a triple boot system: Windows 2K, Fedora 20 and Ubuntu
12.04 LTS
I have three disks, one devoted to each operating system.
The first disk has two partitions, one for the OS (win2k), the rest for
data to be shared while on the other OSs including my personal directory
The second disk has like 4 partitions (Fedora /, /boot, /home, /swap)
The third disk has only three partitions (Ubuntu /, /boot, /swap)
My plan is to get one SSD to keep the OS (both Fedora and Ubuntu). Instead
of keeping Win2k on a drive that I rarely use (just for some games), I plan
to virtualize the disk under VirtualBox.
Given that both Fedora 20 and Ubuntu 12.04 LTS use grub2, my idea for
partitioning is
1. One largish /boot partition, about 1 GB, to hold both the Fedora and
Ubuntu boot images.
2. Separate / partitions, one for Fedora, the other for Ubuntu, about 25 to
30G each
3. Keep a /home subdirectory on each of the partitions on (2), but link a
"My Data" subdirectory to the filesystem under /home/myusername/ through
fstab. "My Data" would come from another HDD (like 1 TB aprox). The idea is
to keep the /home/myusername subdirectories apart and not let them mix
because Fedora and Ubuntu save diferent data on the home directories, then
have a subdirectory with my real data common to both systems.
Is this setup workable? Is there a better solution? I'd rather not have to
buy two SSDs
because the OS take just about 50G and I still have a lot of free space in
that partition
--
------------------------------
/\_/\
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
10 years
Fedora Present and Future: a Fedora.next 2014 Update (Part I, “Why?”)
by Matthew Miller
I promised a while ago that I would provide a text version of my talk at
DevConf, for people who couldn't make it and because sitting through a video
of me standing up there going on and on doesn't really make for good
followup discussion.
Because it grew rather long, I think it works best as a web article, which
you can find on Fedora Magazine at <http://fedoramagazine.org/?p=1236>.
Also because of the length, I'm posting it installments. This part is the
background, next part is some of the things we are doing, followed by the
panel discussion, followed by Q&A. Whew; that's a lot.
I can post the text here if people think it'd be really helpful to do so,
(although I'm inclined to think that would be unwieldy), and in any case I
will take questions, comments, complaints, in any media including replies
here, on the article, on the social media, or at any bar or coffee shop
within walking distance of Boston's MBTA.
--
Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
10 years
systemctl versus service
by Robert Moskowitz
So for a number of versions, 'service' has been a front end to
'systemctl'. I have a service I am testing the Host Identity Protocol,
and the HIPL implementation: http://infrahip.hiit.fi/ that is still
built around 'service'. And they maintain binaries for a number of
distros, including Centos that do not yet (if ever?) use 'systemctl'.
Now I amy not have all the terms right, but that is pretty close to the
challenge.
On my Fedora 20 system, the services come up real slow. In fact I get
errors that they failed, even though they are working! Or at least they
are testing out properly. For example, when I start the HIP firewall I get:
# service hipfw start
Starting hipfw (via systemctl): Job for hipfw.service failed. See
'systemctl status hipfw.service' and 'journalctl -xn' for details.
[FAILED]
This takes a LONG time until the failed message appears. 'ps axu|grep
hip' shows the service is running. but status shows:
hipfw.service - SYSV: HIPL firewall daemon
Loaded: loaded (/etc/rc.d/init.d/hipfw)
Active: failed (Result: timeout) since Thu 2014-04-17 12:51:05 EDT; 1h
0min ago
Process: 2029 ExecStart=/etc/rc.d/init.d/hipfw start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/hipfw.service
└─2031 /usr/sbin/hipfw -bklpF
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(hipfw/helpers.c:97@system_print) $ ip6tables -I HIPFW-FORWARD -p
139 -j DROP -> 0
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(hipfw/helpers.c:97@system_print) $ iptables -I INPUT -j
HIPFW-INPUT -> 0
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(hipfw/helpers.c:97@system_print) $ iptables -I OUTPUT -j
HIPFW-OUTPUT -> 0
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(hipfw/helpers.c:97@system_print) $ iptables -I FORWARD -j
HIPFW-FORWARD -> 0
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(hipfw/helpers.c:97@system_print) $ ip6tables -I INPUT -j
HIPFW-INPUT -> 0
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(hipfw/helpers.c:97@system_print) $ ip6tables -I OUTPUT -j
HIPFW-OUTPUT -> 0
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(hipfw/helpers.c:97@system_print) $ ip6tables -I FORWARD -j
HIPFW-FORWARD -> 0
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(libcore/message.c:319@sendto_hipd) Sending user message 16 to HIPD
on socket 4
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(libcore/message.c:323@sendto_hipd) Sent 40 bytes
Apr 17 12:46:05 ee900.htt-consult.com hipfw[2031]:
debug(libcore/message.c:400@send_recv_info_internal) Waiting to receive
daemon info.
Apr 17 12:51:05 ee900.htt-consult.com systemd[1]: hipfw.service
operation timed out. Terminating.
Apr 17 12:51:05 ee900.htt-consult.com systemd[1]: Failed to start SYSV:
HIPL firewall daemon.
Apr 17 12:51:05 ee900.htt-consult.com systemd[1]: Unit hipfw.service
entered failed state.
Well the HIPL developers are looking into supporting systemctl method,
but for the present, I need the start not to take so long (and I am
talking minutes here, not a few extra seconds until the failed message).
So is there some option I could use in 'systemctl start hipfw.service'
that will cut down the start time, even if there are some warnings?
thanks
10 years
How to put boot into interactive mode
by Robert Moskowitz
Long ago I knew a way to get the boot process to require a keystroke at
each step. This was important when you were trying to read the screen
to figure out what is happening, typically wrong.
But long ago I lost my notes on this, and I believe i need before my
next reboot.
Can someone point me to howto do this? My search foo is weak....
10 years
F20 Yum Transaction Error
by Tim Evans
Since yesterday, F20 yum update reports:
Transaction check error:
file /usr/include/ImageMagick-6/magick/magick-baseconfig.h conflicts
between attempted installs of ImageMagick-devel-6.8.6.3-4.fc20.i686 and
ImageMagick-devel-6.8.6.3-4.fc20.x86_64
--skip-broken will not ignore this.
I see a lot of "conflicts between attempted installs of..." reports in
bugzilla, but not this specific one.
Suggestions? Thanks.
--
Tim Evans | 5 Chestnut Court
Linux/UNIX Consulting | Owings Mills, MD 21117
http://www.tkevans.com/ | 443-394-3864
10 years
CUPS service seems to have suddenly stopped working
by Claude Jones
running the following:
systemctl status cups service
cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: failed (Result: start-limit) since Tue 2014-04-15 16:46:29
EDT; 1min 19s ago
Process: 674 ExecStart=/usr/sbin/cupsd -f (code=killed, signal=TERM)
Main PID: 674 (code=killed, signal=TERM)
CGroup: /system.slice/cups.service
Not sure where to go with this and google isn't helping so far... Can
someone point in the right diagnostic direction?
--
Claude Jones Brunswick, MD, USA
10 years
