gdm-binary DEBUG GdmManager removing display
by Andrew Farris
This message is getting practically spammed to /var/log/messages on a
fresh beta install for i386. Is anyone else seeing this and if it is
expected debugging info isn't this a bit excessive?
Mar 29 11:21:57 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.148
Mar 29 12:21:57 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.149
Mar 29 12:21:57 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.149
Mar 29 12:21:57 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.150
Mar 29 13:21:57 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.151
Mar 29 13:21:57 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.151
Mar 29 13:21:57 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.152
Mar 29 13:36:07 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.153
Mar 29 13:36:07 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.153
Mar 29 13:36:07 localhost gdm-binary[2395]: DEBUG: GdmManager:
Removing display for service name: :1.154
--
Andrew Farris <lordmorgul(a)gmail.com> www.lordmorgul.net
gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E A2E0 F0F6 E622 C99B 1DF3
No one now has, and no one will ever again get, the big picture. - Daniel Geer
---- ----
16 years, 1 month
Install of Fedora 9 Beta (i386) On USB Disk Fails
by Robert L Cochran
I attempted to install the Fedora 9 beta (i386 arch) to a 60 Gb Hitachi
laptop drive I had purchased off of Ebay and promptly put in a Nexstar
external USB hard drive enclosure. The Nexstar enclosure was connected
to a powered USB hub which in turn was connected to a Dell Latitude D420
laptop. So this is a long way of saying I was installing Fedora 9 Beta
to an external hard drive, which shows up as /dev/sdb. I attempted to
install Fedora 9 no less than 4 times.
*I ran the media checker, and the DVD passed the media check.
First install attempt:
I selected "install from local CD/DVD", "obtain networking parameters
from DHCP", "remove all partitions on hard drive", "install to
/dev/sdb", "boot from /dev/sdb", encrypt the hard drive=checked,
provided a passphrase for the hard drive encryption, and change the LVM
Volume Group and Logical volume names. At the point where anaconda wants
to write the disk partitions to the install drive, the install process
stops with an unhandled exception condition. I'm not sure how to save
the error report, so I shut down the laptop by holding down the power
button.
Second install attempt:
I set up the install as above, except I noticed after changing the
logical volume names of the install drive that there was a partition
labelled as vfat. This hard drive was purchased off of ebay and I know
it has Windows 98 installed on it. When I finally "saw" the vfat
partition (I should have noticed it earlier in the install process but
didn't) I deleted the partition via anaconda. Then I clicked to allow
anaconda to write the partition layout to the install drive. Result:
installation freezes up, nothing happens. I'm entirely locked up. I hit
the power button again.
Third install attempt:
This time, I deleted the still-living vfat partition from the install
hard drive before changing the LVM Volume Group and Logical Volume
names. Then I clicked to allow anaconda to write the partition layout to
the install drive. Result: installation freezes up, nothing happens. I'm
entirely locked up. I hit the power button again.
Fourth install attempt:
The vfat partition seems gone from the target hard drive. This seems to
make a difference, and the installer is able to write the partition
layout to the install drive. The install proceeds, and 1402 packages are
installed. I take the DVD out of the DVD drive, unplug the DVD drive (it
is an external Dell-branded drive), and boot to the USB drive with F9
installed on it. Grub comes up, the kernel starts to boot...but then it
freezes up at a "switchroot" event. I am puzzled that I wasn't asked for
my passphrase to unlock the hard drive encryption, too.
Is there any way for me to get F9 to boot?
Thanks
Bob Cochran
Greenbelt, Maryland, USA
16 years, 1 month
Re: install from rsync tree on local partition possible?
by Gianluca Cecchi
On Sat, 29 Mar 2008 11:24:40 +1100 David Timms wrote:
> If you want to build a F9Beta from your pre-downloaded tree, I suggest
using jigdo {in fact pyjigdo}.
> You tell it the jigdo template location, then your pre-downloaded source
locations, and it uses the
> content to build the iso {downloading the bits that aren't present
locally}.
This is exactly what I want. Not to create a 12Gb iso...
The problem is shifted to where to find a jigdo template or how to create it
accordingly.
Using the jigdo file for F9 alpha at fedoraunity, changing the server line
in it to point to local tree and using jigdo-lite, it founds only 135 of
2009 files needed.....
> But perhaps you meant you would like to simulate what an iso image built
by Fedora at any possible moment would look like ?
In what will they differ? the first one above (beta) will match with this
latest in a particular moment (release of beta)... or not?
Thanks
Gianluca
16 years, 1 month
Re: Rawhide 20080328 Snapshot Released
by John Summerfield
I replied to fedora-list but I'm expecting a bounce any moment, I
unsubscribe from it. This seems a better place anyway.
Jesse Keating wrote:
> As part of our development schedule, we are releasing a snapshot of
> Rawhide in iso and Live form. We are releasing these via bittorrent
> only as it is a much lighter weight method to get bits out the door than
> to go through our mirroring system. If you cannot use bittorrent we
> apologize for the inconvenience.
Is it difficult to release jigdos?
A problem with bittorrent (other than intolerant firewalls) its that
many broadband offerings, such as ADSL, that are designed around the
assumption that most users download more than they upload, and I gather
peer2peer networking, such as bittorrent, doesn't work so well as it's
designed to prefer sending over receiving[1].
In Oz - I can't speak for other locations - IAPs tend to either mirror
popular downloads (including rawhide in my case) or peer with some other
IAPs and share mirrors.
And then some of us download the whole box and dice ourselves, and could
easily and quickly assemble it off their own network.
[1] It's serious enough a problem that some are seeking to "manage"
traffic by breaking connexions, and others are reviewing their charging
regimes. IAPs here that previously did not charge for uploads are now
reversing that practice.
_I_ think they must, they're not getting the expected return from their
investment and shareholders care about that.
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
16 years, 1 month
F9 Beta install improperly handles error condition
by shmuel siegel
I have a scratched DVD. When I hit continue from the test dialog box I
quickly got an Error dialog box which only had an OK button. Pressing
this button retried the install which of course failed with the same
dialog box. Removing the DVD didn't change anything.The only way out of
this infinite loop was a hard reboot. There should be other recovery
options.
16 years, 1 month
Xorg 1.3.0 vs. 1.4.99
by Boyan
Hi,
First I wish to thank to everyone involved in making Fedora what
it is in the moment - one of the best linux distributions for years,
and my choice for more than 10 years also. Thank you to all of you
guys!
In short for those impatient to read all the mail - I'm a bit
sceptical for the newer version in rawhide of Xorg (1.4.99 currently)
for it's lack of speed and bad usability compared to older release 1.3.
First a little background:
Around January 2007 I've tested for the first time desktop
effects. I'm using KDE so at this time my only choice was Beryl.
I've tested it on two boxes - first was with Intel 865 chipset and
integrated video (for short box1), second box with ATI Radeon 9550
(for short box2). On those two boxes Beryl was working fine at this
time, but because of other personal reasons (read: my eyes was
going mad with those effects :)) I've uninstalled it.
As you know there is no more Beryl for KDE, only Compiz, but it
doesn't matter for this writing. At December 2007 if you remember
there was a big change to the Xorg and a warning that it may break.
So I didn't installed it until January or February - I don't
remember correctly. This was needed because the older Xorg 1.3.0
was crashing when I've tried to start Compiz on KDE 3.5.7 or 3.5.8.
That's why I've installed the new Xorg, can't remember the exact
version, but it also didn't worked - with box1 it started but there
was no window borders. With box2 the ATI card was blacklisted and
I've needed to export a variable to make it start. It didn't work -
the whole desktop was white. In beginning of March I've tried on
box2 too the new Xorg too, but the desktop was white again. That's
for Compiz testing.
Now for the Xorg 1.4.99.
My impression and the numbers show that it is slower compared to
1.3. In January XAA in 1.4.XX was noticeably worse than XAA in 1.3.
Fonts in konsole were broken and I've needed to switch to EXA,
which is extremely slow, close to unusable - scrolling was slow,
switching to another desktop screen was slow, even switching to
another konsole tab was slow with time around 1-2 sec for
switching, so I've been forced to go back to Xorg 1.3. This month
I've tested the new Xorg again. XAA is almost as in 1.3 release but
with two problems - one is the 10-15 seconds needed for this fog
effect at KDE4 shutdown, which is not so important, but the worse
problem is that with video players I have (mplayer, vlc) starting
to watch some video file makes them spit out the message BadAlloc
for xv output even on smallest resolutions I've tested - 320x240.
mplayer:
xv X11/Xv
x11 X11 ( XImage/Shm )
So I think it's on all resolutions, and vlc is even crashing, but
that is not Xorg problem. As you know xv is faster than x11, that's
why I have it set default. Only x11 output is working with XAA on
the box1, I'll test on box2 to be sure it is not problem with
i810/intel driver only. On box1 I've tried to watch video with EXA
where xv output is working, but it was very slower compared to Xorg
1.3 - on the older version it was possible to watch even HD
resolutions 1920x1080 with almost no problems, but with Xorg 1.4.99
with EXA it is problem watching smoothly even 800x600/1024x768.
To summarize the problems of the new Xorg:
- XAA is a bit slower than before, with not working xv (or maybe it is
changed in some way that compatibility with applications is broken)
- EXA is extremely slow and almost not usable
- Compiz is making the desktop white on my ATI and with no window
borders for Intel, even ATI card is blacklisted but worked fine a
year ago
- compared with glxgears the newer Xorg is slower for Intel with arount
20-30%, no change for ATI, I don't play 3D games to check this fully
- in KDE4 screensavers are missing and can't test opengl there but
arount January they were crashing in KDE 3 on box1 (intel), and
working very slow on box2(ati) with Xorg 1.4.XX EXA.
So as it looks like this Xorg release is planned for Fedora 9 I have
some questions arising from those observations, even if some of
them are upstream too:
- Isn't Xorg 1.4.99 much worse than the older 1.3? (with not fully
working even XAA, with EXA not ready at all to be acceptable replacement)
- Is it planned (Fedora or upstream) Xorg to be fixed before Fedora 9 is
out, and if not (because ot upstream not ready) isn't it better to
stick with the older version until the new is usable even for
rawhide?
For some of the problems maybe it's better to fill bugzilla because
searching in it didn't show anything.
Regards
16 years, 1 month
Re: install from rsync tree on local partition possible?
by Gianluca Cecchi
Ok, so a no go at the moment.
And what would be the simpler way to create an iso image starting from the
14Gb rsync tree?
I'm trying with revisor but perhaps its particular aim is for customizing,
while I would like to recreate a sort of daily dvd iso image if it can help
for testing purposes...
Thanks,
Gianluca
16 years, 1 month
Booting F9beta KDE live image from USB: hangs at "starting auditd"
by Mary Ellen Foster
I looked around and it didn't look like anyone else had this issue, so
I wanted to check before filing a bug. Today, I downloaded the KDE
i386 live image of F9 beta and used livecd-tools to put it on a USB
stick. The stick boots successfully on my desktop machine, but the
startup always seems to hang at "starting auditd". I've left it for
several minutes at a time and it doesn't get anywhere.
I'm about to try the non-KDE image to see if it makes a difference.
Anyone else seeing this, or am I alone?
Thanks,
MEF
--
Mary Ellen Foster -- http://homepages.inf.ed.ac.uk/mef/
Informatik 6: Robotics and Embedded Systems, Technische Universität München
and ICCS, School of Informatics, University of Edinburgh
16 years, 1 month
Hang after enabling /etc/fstab swaps
by Alan
I did a partial update from Rawhide yesterday on my laptop. Now it hangs
with either kernel after printing "Enabling /etc/fstab swaps: [OK]".
Any idea what is going wrong here?
It is encrypted partition. It is mounting the encrypted partition after I
enter the passphrase. It just doesn't want to get very far after that
point.
I may have to recover what I can and scratch and burn and reinstall.
16 years, 1 month
Recovery disc and encrypted partitions
by Alan
Does the latest beta Fedora disc actually detect and mount encrypted
partitions correctly?
Either the latest Rawhide update has hosed up my laptop or it is in the
process of dying. It hangs after it gets to "Enabling /etc/fstab swaps"
in the boot process. (Including single user boot.) There was a message
looking on the console claiming that it was out of disk space. Something
must have filled the 20+ gigs I had free. (Does not matter which kernel I
boot with either. Both hang at the same spot.)
I figure at this point I need to mount the disc, recover what I can and
reinstall.
16 years, 1 month