1 |
Try to reemerge vim without python support. |
2 |
|
3 |
Do you use any python scripts in vim? If no just dont use python flag |
4 |
for vim, if it solve the problem. But it is strange, really seems |
5 |
something with pygtk, but dont know. |
6 |
|
7 |
Maybe try to run python-updater. |
8 |
|
9 |
Robert. |
10 |
|
11 |
|
12 |
V Mon, 23 Apr 2012 00:31:27 +0900 |
13 |
Seong-ho Cho <darkcircle.0426@×××××.com> napsáno: |
14 |
|
15 |
> emm .... this happen also does for normal users. |
16 |
> I've tried "mv ~/.vimrc ~/.vimrc.bak" before run vim for normar user |
17 |
> named "meow", |
18 |
> but similar message is shown. :-$ |
19 |
> |
20 |
> ... so ... |
21 |
> I did try to install and run mc, as you told me. |
22 |
> This program doesn't show that similar message. (-0-! Amazing~~) |
23 |
> |
24 |
> when I execute valgrind /usr/bin/vi I found messages as below |
25 |
> |
26 |
> ------------ |
27 |
> ... |
28 |
> ==18494== by 0x6D0190F: read_compiled_module (in |
29 |
> /usr/lib64/libpython2.7.so.1.0) |
30 |
> ==18494== by 0x6D03F46: load_source_module (in |
31 |
> /usr/lib64/libpython2.7.so.1.0) |
32 |
> ==18494== by 0x6D049DC: load_package |
33 |
> (in /usr/lib64/libpython2.7.so.1.0) ==18494== |
34 |
> |
35 |
> ** (process:18494): WARNING **: Trying to register gtype |
36 |
> 'GMountMountFlags' as enum when in fact it is of type 'GFlags' |
37 |
> |
38 |
> ** (process:18494): WARNING **: Trying to register gtype |
39 |
> 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' |
40 |
> |
41 |
> ** (process:18494): WARNING **: Trying to register gtype |
42 |
> 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags' |
43 |
> ==18494== Invalid read of size 4 |
44 |
> ==18494== at 0x6C97833: PyObject_Free |
45 |
> (in /usr/lib64/libpython2.7.so.1.0) ==18494== by 0x6C69C5A: |
46 |
> code_dealloc (in /usr/lib64/libpython2.7.so.1.0) ==18494== by |
47 |
> 0x6D03D69: load_source_module (in /usr/lib64/libpython2.7.so.1.0) |
48 |
> |
49 |
> ... |
50 |
> ----------- |
51 |
> |
52 |
> I exactly don't know where this message comes from. |
53 |
> ... by the way ... python? |
54 |
> |
55 |
> result log named strace-vi.log for "strace /usr/bin/vi" is attached. |
56 |
> I think that this problem caused by pygtk-related component. |
57 |
> I did re-emerge pygtk related packages |
58 |
> (pywebkitgtk python-gtkmvc pygtksourceview pygtkhelpers pygtkglext |
59 |
> gtkspell-python pygtk) |
60 |
> but I didn't fix this problem : ( |
61 |
> |
62 |
> 2012/4/22 Robert David <robert.david.public@×××××.com>: |
63 |
> > This is strange. |
64 |
> > |
65 |
> > Does this happen only for some files? Or globaly. Does this happen |
66 |
> > also for root? Did you try clean .vimrc? |
67 |
> > |
68 |
> > Do you have mc installed? If not, please try to install a and run |
69 |
> > mc, if it will show similar stuff (maybe some ncurses problem) |
70 |
> > |
71 |
> > Best would be run vi in valgrind, strace, etc, to see what is |
72 |
> > happening. But this is not trivial. |
73 |
> > |
74 |
> > Robert. |
75 |
> > |
76 |
> > V Sun, 22 Apr 2012 21:50:39 +0900 |
77 |
> > Seong-ho Cho <darkcircle.0426@×××××.com> napsáno: |
78 |
> > |
79 |
> >> OK. I attached screenshot (NOT PHOTOSHOPED) for your question. |
80 |
> >> |
81 |
> >> |
82 |
> >> 2012/4/22 Robert David <robert.david.public@×××××.com>: |
83 |
> >> > Hmm, I dont know glib so much, so I cant say. |
84 |
> >> > |
85 |
> >> > What is the process 635 here? Is it the vim or not? |
86 |
> >> > Paste the output "ldd vim". |
87 |
> >> > |
88 |
> >> > Robert. |
89 |
> >> > |
90 |
> >> > |
91 |
> >> > V Sun, 22 Apr 2012 20:38:31 +0900 |
92 |
> >> > Seong-ho Cho <darkcircle.0426@×××××.com> napsáno: |
93 |
> >> > |
94 |
> >> >> ah ... by the way, where are 'GFlags' as a type and gtype |
95 |
> >> >> 'G*Flags' as an enum from? |
96 |
> >> >> |
97 |
> >> >> 2012/4/22 Seong-ho Cho <darkcircle.0426@×××××.com>: |
98 |
> >> >> > Hi, |
99 |
> >> >> > |
100 |
> >> >> > I've tried revdep-rebuild in many time. |
101 |
> >> >> > I tried to run the same __in the xterm__ and __in the |
102 |
> >> >> > lxterminal__ as you said. |
103 |
> >> >> > |
104 |
> >> >> > but I also saw a similar message as below : ( |
105 |
> >> >> > |
106 |
> >> >> >>>> |
107 |
> >> >> > |
108 |
> >> >> > meow@darkcircle ~/xfce-ko $ vi xfdesktop.master.ko.po |
109 |
> >> >> > |
110 |
> >> >> > ** (process:635): WARNING **: Trying to register gtype |
111 |
> >> >> > 'GMountMountFlags' as enum when in fact it is of type 'GFlags' |
112 |
> >> >> > |
113 |
> >> >> > ** (process:635): WARNING **: Trying to register gtype |
114 |
> >> >> > 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' |
115 |
> >> >> > |
116 |
> >> >> > ** (process:635): WARNING **: Trying to register gtype |
117 |
> >> >> > 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags' |
118 |
> >> >> > meow@darkcircle ~/xfce-ko $ |
119 |
> >> >> > |
120 |
> >> >> >>>> |
121 |
> >> >> > |
122 |
> >> >> > 2012/4/22 Robert David <robert.david.public@×××××.com>: |
123 |
> >> >> >> Hi, |
124 |
> >> >> >> |
125 |
> >> >> >> do you have clean environmet, eg: revdep-rebuild ?? |
126 |
> >> >> >> |
127 |
> >> >> >> What kind of terminal you using? Because vim does not use |
128 |
> >> >> >> glib, as I know. Try to run the same in xterm or other |
129 |
> >> >> >> terminal. |
130 |
> >> >> >> |
131 |
> >> >> >> Robert. |
132 |
> >> >> >> |
133 |
> >> >> >> |
134 |
> >> >> >> V Sun, 22 Apr 2012 02:58:44 +0900 |
135 |
> >> >> >> Seong-ho Cho <darkcircle.0426@×××××.com> napsáno: |
136 |
> >> >> >> |
137 |
> >> >> >>> Yes. I can edit text file after these messages. |
138 |
> >> >> >>> Your thinking is so exact !! :D |
139 |
> >> >> >>> |
140 |
> >> >> >>> 2012/4/22 Stroller <stroller@××××××××××××××××××.uk>: |
141 |
> >> >> >>> > |
142 |
> >> >> >>> > On 21 April 2012, at 15:32, Seong-ho Cho wrote: |
143 |
> >> >> >>> > |
144 |
> >> >> >>> >>>>> |
145 |
> >> >> >>> >> |
146 |
> >> >> >>> >> meow@darkcircle ~/xfce-ko $ vi xfdesktop.master.ko.po |
147 |
> >> >> >>> >> |
148 |
> >> >> >>> >> ** (process:15449): WARNING **: Trying to register gtype |
149 |
> >> >> >>> >> 'GMountMountFlags' as enum when in fact it is of type |
150 |
> >> >> >>> >> 'GFlags' |
151 |
> >> >> >>> >> |
152 |
> >> >> >>> >> ** (process:15449): WARNING **: Trying to register gtype |
153 |
> >> >> >>> >> 'GDriveStartFlags' as enum when in fact it is of type |
154 |
> >> >> >>> >> 'GFlags' |
155 |
> >> >> >>> >> |
156 |
> >> >> >>> >> ** (process:15449): WARNING **: Trying to register gtype |
157 |
> >> >> >>> >> 'GSocketMsgFlags' as enum when in fact it is of type |
158 |
> >> >> >>> >> 'GFlags' |
159 |
> >> >> >>> >> |
160 |
> >> >> >>> >>>>> |
161 |
> >> >> >>> >> |
162 |
> >> >> >>> >> when I execute vim as above, I've met some messages like |
163 |
> >> >> >>> >> that. |
164 |
> >> >> >>> >> |
165 |
> >> >> >>> >> what does above mean? how can I solve that problem? |
166 |
> >> >> >>> >> |
167 |
> >> >> >>> >> I did damn googling but I didn't find why that message |
168 |
> >> >> >>> >> shown. |
169 |
> >> >> >>> > |
170 |
> >> >> >>> > I find at least 3 bugs when I google that message. |
171 |
> >> >> >>> > |
172 |
> >> >> >>> > They're Ubuntu bugs, they don't refer to vim, but they |
173 |
> >> >> >>> > make some sense to me. |
174 |
> >> >> >>> > |
175 |
> >> >> >>> > Am I right in thinking that vim does work and allow you to |
176 |
> >> >> >>> > edit this file after showing these messages? |
177 |
> >> >> >>> > |
178 |
> >> >> >>> > Stroller. |
179 |
> >> >> >>> > |
180 |
> >> >> >>> > |
181 |
> >> >> >>> |
182 |
> >> >> >> |
183 |
> >> > |
184 |
> > |