Re: Root login in rawhide and display managers
by Otto Rey
Since Fedora 3 (in some configurations) post-installation wizard (Anaconda?) have a keyboard bug (garbage characters), when ask names to add users. So, cannot add users in wizard. Need to log in as root and add users "manually". If we disable root login in graphical enviroment, we can add using command line, like a workaround, but not all users have strong skills in console.
----- Mensaje original ----
De: David Boles <dgboles(a)gmail.com>
Para: Development discussions related to Fedora <fedora-devel-list(a)redhat.com>
Enviado: viernes 21 de septiembre de 2007, 17:38:20
Asunto: Re: Root login in rawhide and display managers
on 9/21/2007 4:11 PM, Richi Plana wrote:
> On Fri, 2007-09-21 at 15:08 -0400, David Boles wrote:
>> The stripped down session that you propose would be ok. But then you will
>> start a 'flame' about just what this session should contain. ;-)
>
> Well, we can always start with X and twm then slowly change or add
> things, ;). There's already a proposal to give them at least metacity
> and lxpanel. I dunno ... that seems a lot, ;).
>
> In effect, it would be like kids asking for a little bit more at a time
> proving along the way that it's needed. :)
Which is pretty much what I said. ;-)
I don't know why it is but most Linux users, not *ALL* of us, have this
mindset that Linux, and the developers, owe us this great debt of
gratitude because we use the software that they so generously work on for
next to nothing and give to us for free. 8-)
--
David
Los referentes más importantes en compra/ venta de autos se juntaron:
Demotores y Yahoo!
Ahora comprar o vender tu auto es más fácil. Vistá ar.autos.yahoo.com/
16 years, 7 months
Package EVR problems in Fedora 2007-09-21
by Fedora Koji Build System
Broken upgrade path report for repositories FC5, FC5-updates, FE5, FC6,
FC6-updates, FE6, F7, F7-updates, F7-updates-testing, F8
apr-util:
F7-updates-testing > F8 (0:1.2.10-1.fc7 > 0:1.2.10-1)
aspell-fo:
FC5 > F8 (50:0.51-4.2.1 > 50:0.2.16-6.fc8)
FC6 > F8 (50:0.51-4.2.2 > 50:0.2.16-6.fc8)
F7 > F8 (50:0.51-6.fc7 > 50:0.2.16-6.fc8)
balsa:
FE6 > F7-updates (0:2.3.20-1.fc6 > 0:2.3.17-2.fc7)
clamav:
F7-updates > F8 (0:0.91.2-2.fc7 > 0:0.91.2-1.fc8)
cyrus-imapd:
FE6 > F7 (0:2.3.9-6.fc6 > 0:2.3.8-3.fc7)
eclipse-subclipse:
FE6 > F8 (0:1.2.4-1.fc6 > 0:1.2.2-6.fc8)
F7-updates > F8 (0:1.2.4-1.fc7 > 0:1.2.2-6.fc8)
fedora-usermgmt:
FE6 > F7 (0:0.10-1.fc6 > 0:0.9-2.fc7)
fortune-firefly:
FE5 > F7 (0:2.1.2-2.fc5 > 0:2.1.1-2.fc6)
FE6 > F7 (0:2.1.2-4.fc6 > 0:2.1.1-2.fc6)
fslint:
FE6 > F7-updates (0:2.24-1 > 0:2.22-1.fc7)
gammu:
FE6 > F8 (0:1.12.92-1.fc6 > 0:1.11.0-1.fc8)
F7-updates-testing > F8 (0:1.12.92-1.fc7 > 0:1.11.0-1.fc8)
gcstar:
FE6 > F7 (0:1.2.2-1.fc6 > 0:1.1.1-2.fc7)
gtranslator:
F7-updates > F8 (0:1.1.7-4.fc7 > 0:1.1.7-3.fc8)
irqbalance:
FC5-updates > FC6-updates (2:0.55-4.fc5 > 2:0.55-2.fc6)
FC5-updates > F7 (2:0.55-4.fc5 > 2:0.55-2.fc7)
jrtplib:
FE6 > F7 (0:3.7.1-1.fc6 > 0:3.7.0-1.fc7)
kanatest:
FE6 > F7-updates (0:0.4.4-3 > 0:0.4.2-2.fc7)
libextractor:
FE6 > F7 (0:0.5.18a-1.fc6 > 0:0.5.17a-1.fc7)
libgtop2:
FC6-updates > F7 (0:2.14.9-1.fc6 > 0:2.14.8-1.fc7)
libtasn1:
FE5 > F7 (0:0.3.10-1.fc5 > 0:0.3.9-1.fc7)
FE6 > F7 (0:1.1-1.fc6 > 0:0.3.9-1.fc7)
lostirc:
FE6 > F7-updates (0:0.4.6-3.fc6 > 0:0.4.6-2.fc7)
FE6 > F8 (0:0.4.6-3.fc6 > 0:0.4.6-2.fc8)
mimetic:
FE5 > F7 (0:0.9.3-1.fc5 > 0:0.9.2-1.fc7)
FE6 > F7 (0:0.9.3-1.fc6 > 0:0.9.2-1.fc7)
monotone:
FE6 > F7 (0:0.36-2.fc6 > 0:0.35-3.fc7)
nethack-vultures:
FE6 > F7 (0:2.1.0-10.fc6 > 0:2.1.0-9.fc7)
nsd:
F7-updates > F8 (0:3.0.6-3.fc7 > 0:3.0.6-2.fc8)
nss_ldap:
FC6-updates > F7 (0:257-3.fc6 > 0:254-2)
perl-Net-Libdnet:
F7-updates > F8 (0:0.01-3.fc7.1 > 0:0.01-2.fc8)
perl-Nmap-Parser:
F7-updates > F8 (0:1.05-4.fc7 > 0:1.05-3.fc8)
postgresql-pgpool-II:
FE6 > F7-updates (0:1.2-4.fc6 > 0:1.2-1.fc7)
python-cheetah:
FE6 > F7 (0:2.0-0.6.rc8.fc6 > 0:2.0-0.5.rc8.fc7)
python-gammu:
FE6 > F7-updates (0:0.21-1.fc6 > 0:0.20-1.fc7)
FE6 > F8 (0:0.21-1.fc6 > 0:0.20-1.fc7)
python-setuptools:
FE6 > F8 (0:0.6c7-1.fc6 > 0:0.6c6-2.fc8)
F7-updates-testing > F8 (0:0.6c7-1.fc7 > 0:0.6c6-2.fc8)
remind:
FE6 > F7-updates-testing (0:03.01.02-2 > 0:03.01.02-1.fc7)
specto:
FE6 > F8 (0:0.2.2-1.fc6 > 0:0.2.0-4.fc8)
F7-updates > F8 (0:0.2.2-1.fc7 > 0:0.2.0-4.fc8)
tcptraceroute:
FE6 > F7-updates (0:1.5-0.2.beta7.fc6 > 0:1.5-0.1.beta7.fc7)
util-vserver:
FE5 > F7 (0:0.30.213-1.fc5 > 0:0.30.212-3.fc7)
FE6 > F7 (0:0.30.214-2 > 0:0.30.212-3.fc7)
xmlrpc-c:
FE5 > F7 (0:1.06.14-1.fc5 > 0:1.06.11-2.fc7)
FE6 > F7 (0:1.06.18-1.fc6 > 0:1.06.11-2.fc7)
16 years, 7 months
[FHS] Directory for icc color profiles
by Nicolas Chauvet
Hello!
I've found that bug on http://www.pathname.com/fhs/
(given from man 7 hier )
http://bugs.freestandards.org/show_bug.cgi?id=77
The problem is: most profiles are installed with oyranos (currently in
review ), but oyranos has an optionnal requires (xcalib), which also
bundle icc profiles...
The easy way would be to have xcalib to own icc profile directory
(meant /usr/share/color/icc ) but if not installed, then the dir
wouldn't be own...
Another way would be to have it own by lcms.
But the same problem appears, if ever lcms is getting uninstalled (icc
profiles will be unusefull on the system then), packages that only
bundle icc profiles won't have the directory owns by any package...
So, i'm wondering if that directory could be own by filesystem...?
oyranos have others directories in /usr/share/color
/usr/share/color/cmms contains .xml file for backend with other apps
/usr/share/color/settings/ contains xml profiles setting
Anyway, oyranos is still in an alpha state, so when it will be stable,
that might be desirable to have it with a FC-8-updates (if possible)..
Références:
xcalib review: https://bugzilla.redhat.com/show_bug.cgi?id=285351
oyranos review: https://bugzilla.redhat.com/show_bug.cgi?id=239936
16 years, 7 months
new behavior of Logitech diNovo Edge keyboard
by DI Mario Bruckschwaiger
When not moving the cursor (touching the touch disk) during startup, the
keyboard won't work (red bluetooth light on the keyboard). Either the
cursor is moved during the startup process or the bluetooth usb receiver
for the keyboard is unplugged and plugged in again when in gdm will make
the keyboard work. This is not so in Fedora 7. I noticed this behavior
with the last three or four kernels from rawhide, don't know if this
behavior also showed up before. It's also the same with the current
xen-kernel. So I don't think it's a kernel problem. But it is strange
and it is not very comfortable.
For information: I did not do a clean install, instead I upgraded a
former Fedora 7 installation.
Mario.
16 years, 7 months
mono Provides
by Michael Schwendt
Is it intentional and safe for these packages to provide these Mono
capabilities? Are the pairs of packages, which provide exactly the
same things, interchangable at run-time? You know what can happen when
Yum resolves a dependency by pulling in the pkg with the shortest
name...
banshee provides mono(Boo.Lang) = 0:1.0.0.0
boo provides mono(Boo.Lang) = 0:1.0.0.0
required by: boo - 0.7.6.2237-12.fc7.i386
required by: banshee - 0.13.1-1.fc8.i386
banshee provides mono(Boo.Lang.Compiler) = 0:1.0.0.0
boo provides mono(Boo.Lang.Compiler) = 0:1.0.0.0
required by: boo - 0.7.6.2237-12.fc7.i386
required by: banshee - 0.13.1-1.fc8.i386
banshee provides mono(Boo.Lang.Parser) = 0:1.0.0.0
boo provides mono(Boo.Lang.Parser) = 0:1.0.0.0
required by: boo - 0.7.6.2237-12.fc7.i386
banshee provides mono(ipod-sharp) = 0:0.0.1.0
ipod-sharp provides mono(ipod-sharp) = 0:0.0.1.0
required by: banshee - 0.13.1-1.fc8.i386
banshee provides mono(ipod-sharp-ui) = 0:0.0.1.0
ipod-sharp provides mono(ipod-sharp-ui) = 0:0.0.1.0
required by: banshee - 0.13.1-1.fc8.i386
banshee provides mono(NDesk.DBus) = 0:1.0.0.0
f-spot provides mono(NDesk.DBus) = 0:1.0.0.0
required by: f-spot - 0.4.0-2.fc8.i386
required by: banshee - 0.13.1-1.fc8.i386
banshee provides mono(Boo.Lang.Interpreter) = 0:1.0.0.0
boo provides mono(Boo.Lang.Interpreter) = 0:1.0.0.0
required by: boo - 0.7.6.2237-12.fc7.i386
required by: banshee - 0.13.1-1.fc8.i386
db4o provides mono(Mono.Cecil) = 0:0.4.3.1
monodevelop provides mono(Mono.Cecil) = 0:0.4.3.1
required by: db4o - 6.1-2.fc7.i386
db4o provides mono(Mono.GetOptions) = 0:2.0.0.0
mono-core provides mono(Mono.GetOptions) = 0:2.0.0.0
mono-core provides mono(Mono.GetOptions) = 0:1.0.5000.0
required by: f-spot - 0.4.0-2.fc8.i386
required by: mono-debugger - 0.31-2.fc7.i386
required by: mono-devel - 1.2.4-2.fc8.i386
required by: db4o - 6.1-2.fc7.i386
f-spot provides mono(Mono.Addins.Gui) = 0:0.2.0.0
tomboy provides mono(Mono.Addins.Gui) = 0:0.2.0.0
required by: tomboy - 0.8.0-1.fc8.i386
required by: f-spot - 0.4.0-2.fc8.i386
f-spot provides mono(Mono.Addins) = 0:0.2.0.0
tomboy provides mono(Mono.Addins) = 0:0.2.0.0
required by: tomboy - 0.8.0-1.fc8.i386
required by: f-spot - 0.4.0-2.fc8.i386
mono-core provides mono(ICSharpCode.SharpZipLib) = 0:0.84.0.0
nant provides mono(ICSharpCode.SharpZipLib) = 0:0.84.0.0
16 years, 7 months
gnomebaker 0.6.1-4 oddity
by Alexandru Ciobanu
Hello,
Since last update gnomebaker doest not start. I don't know how to make a
proper BZ entry since I don't have any errors other than:
** (gnomebaker:8039): WARNING **: Add decoder bethsoftvid (107) please
** (gnomebaker:8039): WARNING **: Add decoder c93 (106) please
** (gnomebaker:8039): WARNING **: Add decoder dnxhd (103) please
** (gnomebaker:8039): WARNING **: Add decoder dsicinvideo (97) please
** (gnomebaker:8039): WARNING **: Add decoder dxa (102) please
** (gnomebaker:8039): WARNING **: Add decoder gif (100) please
** (gnomebaker:8039): WARNING **: Add decoder kmvc (88) please
** (gnomebaker:8039): WARNING **: Add decoder nuv (87) please
** (gnomebaker:8039): WARNING **: Add decoder ptx (108) please
** (gnomebaker:8039): WARNING **: Add decoder sgi (105) please
** (gnomebaker:8039): WARNING **: Add decoder smackvid (86) please
** (gnomebaker:8039): WARNING **: Add decoder targa (96) please
** (gnomebaker:8039): WARNING **: Add decoder thp (104) please
** (gnomebaker:8039): WARNING **: Add decoder tiertexseqvideo (98) please
** (gnomebaker:8039): WARNING **: Add decoder tiff (99) please
** (gnomebaker:8039): WARNING **: Add decoder VMware video (92) please
** (gnomebaker:8039): WARNING **: Add decoder atrac 3 (86050) please
** (gnomebaker:8039): WARNING **: Add decoder dsicinaudio (86045) please
** (gnomebaker:8039): WARNING **: Add decoder imc (86046) please
** (gnomebaker:8039): WARNING **: Add decoder gsm (86037) please
** (gnomebaker:8039): WARNING **: Add decoder gsm_ms (86049) please
** (gnomebaker:8039): WARNING **: Add decoder mpc sv7 (86047) please
** (gnomebaker:8039): WARNING **: Add decoder smackaud (86042) please
** (gnomebaker:8039): WARNING **: Add decoder wavpack (86044) please
** (gnomebaker:8039): WARNING **: Add decoder adpcm_thp (69650) please
I'm running latest rawhide (20070914) and I could really use some pointers.
TIA,
Alex
16 years, 7 months
Does anyone have gnome-keyring problems?
by Alexander Larsson
The new gnome-keyring has a small change in behaviour. When you look for
a key that doesn't exist it used to return a DENIED error. This is
somewhat wrong (as it seems to indicate that there is a permissions
error). This was changed to return OK, with a list of zero hits.
Bug for this:
https://bugzilla.redhat.com/show_bug.cgi?id=298871
This caused problems for at least network manager, where nm-applet would
crash. We have a patch for this, so that will be fixed. However, this
could affect other applications too. Has anyone seen any strange
behaviour with the keyring?
16 years, 7 months