1 |
Hello everyone, I am brand new to this list and hopefully this is the |
2 |
right place to get a little help. I recently jumped back on the horse |
3 |
with Catalyst after quite some time away from using it. I picked it back |
4 |
up at the suggestion of Chris Gianelloni, who has been great at getting |
5 |
me on track. |
6 |
|
7 |
|
8 |
|
9 |
Here is what I have happening. I am running a fairly straight forward |
10 |
livecd-stage1 build nothing to crazy, my use options and packages are |
11 |
listed below: |
12 |
|
13 |
|
14 |
|
15 |
livecd/use: -* livecd ncurses ssl gtk2 gnome X |
16 |
|
17 |
livecd/packages: baselayout livecd-tools gnome mozilla-firefox hotplug |
18 |
coldplug syslog-ng vim ethtool |
19 |
|
20 |
|
21 |
|
22 |
At the end of the gdm build I get the following error: |
23 |
|
24 |
|
25 |
|
26 |
>>> Completed installing gdm-2.6.0.9-r3 into |
27 |
/var/tmp/portage/gdm-2.6.0.9-r3/image/ |
28 |
|
29 |
|
30 |
|
31 |
--------------------------- ACCESS VIOLATION SUMMARY |
32 |
--------------------------- |
33 |
|
34 |
LOG FILE = |
35 |
"/var/log/sandbox/sandbox-gnome-base_-_gdm-2.6.0.9-r3-2358.log" |
36 |
|
37 |
|
38 |
|
39 |
open_wr: /etc/pam.d/gdm |
40 |
|
41 |
open_wr: /etc/pam.d/gdm-autologin |
42 |
|
43 |
------------------------------------------------------------------------ |
44 |
-------- |
45 |
|
46 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage1-x86-2005.8.19/dev: |
47 |
device is busy |
48 |
|
49 |
umount: /var/tmp/catalyst/tmp/default/livecd-stage1-x86-2005.8.19/dev: |
50 |
device is busy |
51 |
|
52 |
!!! catalyst: First attempt to unmount: |
53 |
/var/tmp/catalyst/tmp/default/livecd-stage1-x86-2005.8.19/dev failed. |
54 |
|
55 |
!!! catalyst: Killing any pids still running in the chroot |
56 |
|
57 |
Checking for processes running in chroot and killing them. |
58 |
|
59 |
Running command "/bin/bash |
60 |
/usr/lib/catalyst/targets/support/kill-chroot-pids.sh" |
61 |
|
62 |
|
63 |
|
64 |
Killing process(es) |
65 |
|
66 |
pid: process name |
67 |
|
68 |
12288: |
69 |
/var/tmp/catalyst/tmp/default/livecd-stage1-x86-2005.8.19/usr/libexec/gc |
70 |
onfd-2 |
71 |
|
72 |
12365: |
73 |
/var/tmp/catalyst/tmp/default/livecd-stage1-x86-2005.8.19/usr/libexec/gc |
74 |
onfd-2 |
75 |
|
76 |
15587: |
77 |
/var/tmp/catalyst/tmp/default/livecd-stage1-x86-2005.8.19/usr/libexec/gc |
78 |
onfd-2 |
79 |
|
80 |
|
81 |
|
82 |
Press Ctrl-C within 10 seconds to abort |
83 |
|
84 |
|
85 |
|
86 |
Traceback (most recent call last): |
87 |
|
88 |
File "modules/livecd_stage1_target.py", line 21, in run_local |
89 |
|
90 |
cmd("/bin/bash "+self.settings["sharedir"]+\ |
91 |
|
92 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 102, |
93 |
in cmd |
94 |
|
95 |
raise CatalystError,myexc |
96 |
|
97 |
CatalystError: <unprintable instance object> |
98 |
|
99 |
None |
100 |
|
101 |
|
102 |
|
103 |
!!! catalyst: Couldn't umount one or more bind-mounts; |
104 |
aborting for safety. |
105 |
|
106 |
|
107 |
|
108 |
|
109 |
|
110 |
It looks like pam and gdm are not getting along as they should. I have |
111 |
tried several things including removing pam from my package list, and |
112 |
building a new stage3 from scratch. I can't seem to get around this |
113 |
problem. Has anyone seen anything like this before or have any |
114 |
suggestions? |
115 |
|
116 |
|
117 |
|
118 |
|
119 |
|
120 |
Paul |