Reboot/Restart Jargon
by Rahul Sundaram
Hi
It seems that we are using reboot/restart inconsistently in the
interface. GDM has a restart button with provides a message on
"reboot"ing the system. Pirut, GNOME and KDE menus mention restart and
reboot in a seemingly random fashion. Also without using KDM, KDE
wouldnt provide a restart and shutdown option.
--
Rahul
Fedora Bug Triaging - http://fedoraproject.org/wiki/BugZappers
18 years, 2 months
Howto do Notification from python.
by Tim Lauridsen
Hi,
Anybody knows how to use libnotify / notify-daemon from python.
It can be done by using the Python DBus bindings, but how ??
Tim Lauridsen
18 years, 2 months
Problems with RAID1 && LogicVol...
by casimiro barreto
BTW,
Besides the problem with gnome, I detected a very weird behaviour on
RAID1 and logic volumes. Consider the same box (ASUS + Sis) with two
120GBytes SATA disks. I created a logic volume and a RAID1 (/dev/md0)...
What happens is that when I have intensive transfer, the box gets frozen
dead (no inputs, no interrupts, no nothing). BTW, no logs.
Both partitions were created canonically and, particularly, for the RAID
it was ensured that both partitions have exactly the same geometry. Both
HDs are equal. RAID worked well under Micro$oft Window$ XP...
I guess that there must be some bug in the treatment of interrupts...
Have someone experienced similar problems with RAIDs ???
Best regards,
Casimiro
18 years, 3 months
Re: libtrash in fedora Core 5
by Horst H. von Brand
Paul A Houle <ph18(a)cornell.edu> wrote:
> Horst von Brand wrote:
[...]
> > If you want Windows with all its brokeness, you know where to find it...
> I don't think it's all that bad to offer people the option of a
> reversable delete.
Except it isn't exactly when you need it to be. "Reversable delete"
requires infinite-sized disks, and I haven't seen any of those lately. Next
you need reversable <anything> changes to random files (yes, files get
broken by editing too).
Moving to "Thrash" just postpones the moment of disposal, and then they
come whining that they emptied the thrashbin by mistake...
> I've never experienced it personally, but I do encounter people
> quite often who want to recover a deleted file on an ext3
> filesystem and find out that it can't be done.
And learn that what is deleted is /gone/. It is much better (if somewhat
harsh) to get used to that discipline. "It can be undeleted later" just
creates sloppiness. Plus automated responses like I remember from DOS days:
"del *.*\ny"...
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
18 years, 3 months
RFE: Retire Fedora Core 4 only _after_ FC6 has been released.
by Gilboa Davara
Hello all,
I've been following a very interesting discussion in fedora-list about
the recent transfer of FC3 to Fedora Legacy.
Following Rahul's suggestion, I'm starting this discussion in -devel.
I'm asking the FC foundation to consider the following:
1. Fedora's policy dictates that old releases (Current - 2) will be
retired once the new release hits Test2. This policy has one glaring
drawback: User that seek an upgrade can either (1) install a mid-life
release (FC4 in this case) or (2) install a beta release. (FC5 Test2 in
this case).
This being I suspect that most users will play the waiting game before
making a decision. They'll wait for the FC5 release and check how it
behaves before making a decision, which in turn, will leave them
vulnerable to security exploits.
Extending the life of FC4 by (a mere?) ~2 months, will give FC4 users
seeking an upgrade a chance to make an informed decision based upon how
FC6 behaves, without leaving them open to security risks.
2. It has been suggested (in the fedora-list discussion) that the last
official FC4 update will be a legacy yum configuration rpm that will
ease/automate the transition to legacy. This sounds like a great idea to
me. Is it possible?
Thanks,
Gilboa
18 years, 3 months
totem doesn't play dvd: no reason
by Gianluca Cecchi
After recompiling from source rpm packages from gstreamer site:
gstreamer-plugins-ugly-0.10.1-0.gst.1.4
gstreamer-ffmpeg-0.10.0-0.gst.2.4
gstreamer-plugins-ugly-devel-0.10.1-0.gst.1.4
and recompiling livna packages:
a52dec-0.7.4-0.lvn.7.4.src.rpm
djbfft-0.76-0.lvn.4.4.src.rpm
lame-3.96.1-0.lvn.4.4.src.rpm
libdvdcss-1.2.9-0.lvn.1.4.src.rpm
libdvdnav-0.1.10-0.lvn.1.4.src.rpm
libdvdplay-1.0.1-0.lvn.3.4.src.rpm
libdvdread-0.9.4-0.lvn.1.4.src.rpm
libmad-0.15.1-0.lvn.1.b.4.src.rpm
mpeg2dec-0.4.0-0.lvn.4.b.4.src.rpm
amrnb-0.0.1-0.lvn.1.src.rpm
I'm able to play with latest fc5 devel totem (totem-1.3.1-1) various
video files, and also divx.
Trying to play dvds I get
"totem was not able to play this disc. No reason"
If I want to stay with totem provided and be able to play dvds where
it is legal, what other requirements should I add?
Or have I to install necessarily totem-xine?
Gianluca
18 years, 3 months
re: Problems with gnome...
by Gianluca Cecchi
I have no problems here after upgrading to latest packages as of
rawhide 20060124 changes.
I didn't apply yesterday updates in the mean time so I don't know if
something was broken.
My card is nvidia geforce fx 5200 with default nv driver.
Performance of screen redraw operations, as detailed in other posts,
for example in workspace switching operations where both workspaces
have windows open, presents quite noticable latencies.
I never tried nvidia
Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nv"
VendorName "Videocard vendor"
BoardName "nVidia Corporation NV34 [GeForce FX 5200]"
EndSection
And I'm using a 19" monitor with resolution of 1280x1024@24bit
18 years, 3 months