I'm trying to understand how mount --move can be used. Whenever I use it, I
get an error "mount: wrong fs type, bad option, bad superblock..."
for example (something I found that supposed to work):
mkdir foo bar
mount --bind foo foo
mount --move foo bar
mount: wrong fs type, bad option, bad superblock on foo,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
What is wrong with it?
P.S. I'm using F17, with kernel 3.8.3
How to record via ctrl+alt+shift+r, video and audio together ?
I have fount this trick:
But the command for set the "org.gnome.shell.recorder pipeline" key:
> gsettings set org.gnome.shell.recorder pipeline "queue ! \
> videorate ! vp8enc quality=10 speed=2 ! mux. pulsesrc ! \
> audio/x-raw-int ! queue ! audioconvert ! vorbisenc ! \
> mux. webmmux name=mux"
... do not work, and break the recording, likely this setting is for
gstreamer-0.10, bud f18 use gstreamer1-1.x, true?.
This is home page of shell recorder, but there is nothing for enable
Someone have suggest?
Dario Lesca - sip:email@example.com
(Inviato dal mio Linux Fedora18+Gnome3)
I wanted to give fedora 18 a try so I created a new virtual machine in
virtualbox (host is Windows 7 enterprise 64bit).
I'm using the 32bit live CD but no matter what options I try after the
fedora 18 progress bar I get a black screen followed by the blue
background for a short while and then a window displaying "oh no
something has gone wrong please contact your system administrator".
I've checked the media (troubleshoot check media and start fedora 18)
and it reported no errors.
I tried adding xdriver=vesa and troubleshooting > start with basic
vide driver but I get the same result.
I opened one of the virtual terminals and I'm able to log on as root
so some system is running, but I'm unable to tell if this is the live
system or some anaconda or other installer shell.
/var/log/messages contains reports that gnome-shell core dumped and an
abrt trace has been created.
The only report I found that resembles what I see is
https://bugzilla.redhat.com/show_bug.cgi?id=919669. In the abrt
report I also see "Process /usr/bin/gnome-shell was killed by signal 4
(SIGILL)" in the reason file.
Is there any other boot option I can try? Is there a way to recover
from the gnome-shell crash? Perhaps force fallback mode?
Thanks in advance.
I have a Linksys WVC54GCA camera in a remote site,
which I access at http://xyz.com:8080 on one of my Fedora-18 laptops.
For some reason there is now a delay of an hour or so
in getting the image on my laptop.
This occurs on both my Fedora-18/KDE laptops,
whether connected by WiFi or ethernet,
and whether using Firefox, Chrome or Konqueror.
But it does not occur - I get an immediate view -
running Windows XP on the same laptops,
or on my server running CentOS-6.4.
With Firefox I get the message "Connecting to ..."
and then (endlessly) "Transferring data from ...".
Any enlightenment gratefully received.
My wife's machine downstairs (built for us by a friend who speaks
hardware; I do not) has been hitting the Diagonal Screen of Death (DSoD);
it brings up the login screen with both our names, and lets you choose
one. You type in userid and password, and whammo : DSoD.
In that condition it does however let me login over ssh and
become root. I did so, ran yum update (no trouble with that), and did a
reboot. No joy.
I tried startx.
[root@Msgv2 ~]# startx
xauth: file /root/.serverauth.1267 does not exist
Fatal server error:
xf86OpenConsole: VT_ACTIVATE failed: No such device or address
It referred me to wiki.x.org, where I found only discussions well
over my head. But the directions there recommended trying to configure,
and I tried :
[root@Msgv2 log]# X -configure
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
It said :
Please also check the log file at "/var/log/Xorg.1.log" for additional
I did that :
[root@Msgv2 tmp]# rm .X0-lock
rm: remove regular file `.X0-lock'? y
[root@Msgv2 tmp]# cd
[root@Msgv2 ~]# X -configure
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
At this point, it looks to me like a catch-22 -- wie man's auch
macht, is' es verkehrt.
Can anybody spare me a clue?
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
Upgraded F17 kernel to 3.8.8-100. Now it goes boots though udevd, i.e.
"Welcome" seems to find the devices, though it's hard to tell since
everything goes so fast.
/var/log/messages has no messages from these boot loops.
3.8.4-102, but now dies with an fb message that nouveaufb conflicts with
vesa vga, so it's removing the generic driver. But it just hangs there.
Any help appreciated.
Does anyone care to help me change the negative connotation that the
outside world has of this term, one step at a time? The CBC just used the
term with a negative frame on the Tuesday, 23 April 2013 30-minute radio
news at about the half-way point. Everyone ought to go to this link and
suggest that they should quit abusing the term.
to listen to her abuse of the term, go to the link with "contact" removed /
deleted - before Wednesday, 25 April at UTC 01:00 (PDT 18:00, in case I did
the math wrong).
Of course, the media are infamous for abusing scientific terms, such as
calling the Higgs boson the god particle - a term scientists loathe - so I
out not lose too much sleep over it.
After upgrade from 17 to 18 with fedup and installing all the updates I was
unable to login as any user other than root. When I tried I was greeted with
the message: "System is booting up".
After beating my head against the wall I finally tried booting to runlevel
5 instead of 3. That fixed the issue. But booting to runlevel 3 and switching
to 5 doesn't work.
Possibly a problem with systemd?
I am running f18 on HP laptop envy dv7, during one the previous update
it left a message, "one of important update did not got installed" and
now i get that message every time I reboot, and actually it try to
install on every boot. Is the a way to clean this?
I will appreciate help, and thank you.
I've got a Dell Precision M4600 laptop, running Fedora 17. Sometime after kernel 3.7.9-104, the external VGA output no longer works.
If I boot with 3.7.9-104,with my projector attached, it is recognized. If I boot with 3.8.4-102, external VGA devices are not recognized.
01:00.0 VGA compatible controller: nVidia Corporation GF108 [Quadro 1000M] (rev a1)
(I've tried running the driver from nVidia, but that has screen rendering problems, with blocks of random data instead of my normal background pic)