vlc
by Patrick Dupre
Hello,
vlc-core-2.0.2-1.fc17.x86_64
When I try to load vlc, I get:
VLC media player 2.0.2 Twoflower (revision 2.0.1-453-g40d9fef)
[0x1800e28] main interface error: no suitable interface module
[0x1737108] main libvlc error: interface "globalhotkeys,none"
initialization failed
[0x1737108] main libvlc: Running vlc with the default interface. Use
'cvlc' to use vlc without interface.
[0x1800e28] [cli] lua interface: Listening on host "*console".
VLC media player 2.0.2 Twoflower
Command Line Interface initialized. Type `help' for help.
I cannot find information about this issue!
--
======================================================================
Patrick DUPRÉ | | email: pdupre(a)kegtux.org
======================================================================
11 years, 8 months
Debugging a system freeze?
by Christopher Svanefalk
Recently I have been having problems with my machine completely freezing up
seemingly randomly. The display freezes in its current frame, and all I/O
is completely unresponsive. It is not possible to SSH into it at this stage
(ssh fails with a Host Unreachable error). The only remedy is a manual
reset.
I was wondering how I could go about trying to figure out what is going on?
What log files can I look at to figure out what happened just before the
reset etc? Would be grateful for any help.
My specs are the following:
Fedora 17 standard desktop version, completely updated as of June 17, 2012.
i7-3930K clocked at 4.2Ghz with 1.240 vcore (stable)
Gigabyte X79-UD7
Nvidia GTX285 (main suspect, since it is provably broken. However, I have
not had these problems earlier)
SATA HDD from Seagate.
--
Best,
Christopher Svanefalk
11 years, 8 months
view, list always?
by Jack Craig
Hi Folks,
Running F16/Gnome3 and want a global configuration change.
The default list mode is icon and i don't care for it.
How can i configure a high level default view to list all the time?
TIZ, jackc...
11 years, 8 months
Re: Check your /etc/default/grub, if you use raid 1.
by Tom Killian
On Sun, Jul 29, 2012 at 10:02 AM, Sam Varshavchik
<mrsam(a)courier-mta.com> wrote:
> To: For users of Fedora Core releases <users(a)lists.fedoraproject.org>
> Subject: Check your /etc/default/grub, if you use raid 1.
> Message-ID: <cone.1343570520.888812.3982.1000(a)monster.email-scan.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed";
> DelSp="yes"
>
> There's a long standing combination of two bugs: the list of rd.md.uuid boot
> parameters generated by anaconda for /etc/default/grub may not include the
> raid uuid of non-stock partitions like /home; and although the ramfs
> initscript autodiscovers all raid volumes present, sometimes (not always,
> I'll estimate 5% of the time) if a uuid is not enumerated in the boot
> parameters, one of the drives in the raid 1 volume may not get assembled at
> boot.
>
> There's probably a third bug in here: mdmonitor should've mailed me when an
> array came up degraded at boot (I suspect that because mdmonitor gets
> started so early in the boot process, not all the moving pieces are there
> for mail delivery to happen). Eventually, you'll boot again with both drives
> in the array somehow, except they'll be out of sync, resulting in massive
> corruption. If you're lucky, you'll boot just with the other drive, and
> discover that your filesystem's contents are weeks/months out of date, and
> maybe you'll be lucky enough to figure out what happen, and switch back to
> the other drive and resync. But, not everyone's so lucky.
>
> This first started happening in F16. It took me a while to figure out the
> cause for an occasionally raid assembly failure at boot. Fixed it, and
> forgot about it. Well, looks like the F17 anaconda brought back the broken
> /etc/default/grub, which found its way into my grub.cfg, and I just lost a
> full day, cleaning up this mess.
>
> So, if you use raid 1 and upgraded to F17, you may need to fix this before
> it's too late: put back the missing uuid into /etc/default/grub, and into
> every entry in grub.cfg
>
> Pissed.
Thanks for the explanation and fix/workaround, Sam. This happened to
me as well. I ran fsck on the two mirrors independently and was able
to recover most of the data from the lost+found's. But I had been
brooding over the root cause until now.
11 years, 8 months
Configuring graphics(resolution) on Dell Vostro 460 i5
by Oscar Vidal
Hello,
I'm new with fedora, I has been Ubuntu user during last years. Now I'm
facing a problem with my workstation when I installed Fedora 17. I'm not
able to configure the right resolution for the system, I'm using a Dell
Vostro 460 i5. Im wondering if someone else had instaled Fedora 17 in this
same computer and had solved already this problem. Any advice is welcome.
Thanks
Oscar
11 years, 8 months
External disk problem.
by Erik P. Olsen
I have an external 1 TB harddisk e-sata attached used for backups. The problem
is that I have few times lost connection to it. I have taken up the habit of
suspending (to RAM) when I leave the machine for a while and the problem seems
to happen when I reactivate the system though not every time. After a power
cycle the disk attaches correctly again. There is no trace of the problem in the
various logs so I am tempted to believe that it is caused by the suspend process
rather than a disk failure but since it is my backup device I would like to be
sure.
System: Fedora 16 with xfce 4.10
Kernel: 3.4.6-1.fc16.x86_64
Question: How can I run diagnose on the disk to see if it is about to fail
permanently?
--
Erik.
11 years, 8 months
installation fails
by Patrick Dupre
Hello,
I failed several times to install fedora.
It seems to be caused by the sleeping of the DVD reader.
How can I awake it up?
It stops to run typically during the configuration of the installation.
Thank.
--
======================================================================
Patrick DUPRÉ | | email: pdupre(a)kegtux.org
======================================================================
11 years, 8 months
Reg: Fedora 16
by Prashanth Kasula
HI all,
Can any one suggest for compatbaility of various browsers in fedora 16
--
Prashanth Kasula
11 years, 8 months
