Ticket #174 (closed defect: worksforme)
Re: [Kdesvn-bugs] Fwd: problems with kdesvn and UTF-8
| Reported by: | "Alexander Hoffmann" <almiho@…> | Owned by: | alwin |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | All | Version: | |
| Severity: | tweak | Keywords: | gentoo |
| Cc: |
Description (last modified by Alexander Hoffmann) (diff)
Hello, Sorry for the long silence, I was too busy to continue with this. Meanwhile the problem changed from a crash to an error message, maybe due to a later version of kdesvn being installed now. Whenever I try to use kdesvn I get the message that a valid sequence of UTF-8 chars is followed by an invalid sequence of UTF-8 chars. After google'ing I found some people discussing this issue, there even was a bug report for kdesvn being closed as "invalid". I do not see how this can be invalid since it happens every time I start kdesvn. Maybe some guys in some forums are right and this is an issue with subversion not with kdesvn, but what I do not understand then is why is the command line tool svn working fine all the time while kdesvn reports this error ? My impression from looking at the search results for this problem was that no one is accepting this problem as a bug in kdesvn and consequently no fix can be expected in near future. Thus, I followed the recommendation of some guy in a forum and downgraded to kdesvn 0.9.2. Now it works for me (one more reason for me to think that this is a bug in kdesvn later than 0.9.2). Regards, Alex 2007/6/3, Jens Seidel <jensseidel@users.sf.net>: > On Sun, Jun 03, 2007 at 08:19:52PM +0200, Alexander Hoffmann wrote: > > I recompiled libtool, glibc, qt, subversion and kdesvn. The problem > > remained the same. > > You should definitivly compile with debugging information, at least > kdesvn, especially if you want to analyse a problem. > > > You can see the stacktrace from the crashing kdesvn below. > > Sorry, I see no stacktrace ... > > > And now the stacktrace: > > GNU gdb 6.6 > > (no debugging symbols found) > > This is probably the problem. > > > Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. > > Loaded symbols for /usr/lib/gconv/ISO8859-1.so > > There is something missing here! Where happens the crash, in what > function? Even without debugging information I would expect more > information. Strange ... > > > Core was generated by `kdesvn --nocrashhandler exec co > > https://myserver/myrepository'. > > Ah, do you have a core file? In this case please start > $ gdb -c /path/to/core /usr/bin/kdesvn > > bt > > quit > > and send this output. > > Jens > _______________________________________________ > Kdesvn-bugs mailing list > Kdesvn-bugs@alwins-world.de > http://lists.alwins-world.de/mailman/listinfo/kdesvn-bugs >
Attachments
Change History
comment:2 Changed 6 years ago by alwin
- Priority changed from normal to low
- Severity set to tweak
As long as I'm not able to check this I can do nothing.
I have no problems. Others have no problems. The one and only utf8 problems I saw where all on missconfigured Gentoo-systems.
Inside KnownIssues or ticket #171 are some tips for this problem. In all cases this works. In all cases it were a problem with libexpat0 and libexpat1. I tried it with my vmwared gentoo twice. After painfull updating all stuff to libexpat1, fixing all of this horrible gcc-update-issues and so on kdesvn works wonderfull. It works with cyrillic signs, western european signs.
That it may work with commandline and not with kdesvn: the commandline does not this what kdesvn does on open a working copy.
Other words: this problem you're describing is only within gentoo. Nowhere else. And not on all gentoos. Only on a few. And I can not see what the problem should be. IMHO this is not a problem of kdesvn nor subversion. Its a problem of gentoo and missing consistency.
I'd checked the difference between 0.9.2 and 0.10.0 again and again, there is nothing done on utf8. The last fix on utf8 inside svnqt was long before release 0.9.2.
comment:3 Changed 6 years ago by alwin
- Keywords gentoo added
- Status changed from new to closed
- Resolution set to worksforme
No feedback anymore so I'll close this now.
I know it may frustrating - but I can not reproduce it. If someone having this problem find a solution please report to me if a problem of kdesvn otherwise put it into KnownIssues, too.
comment:6 Changed 5 years ago by anonymous
I don't know whether this issue still exists.
I got the same problem and could "solve" it with the following steps:
1)
# epm -qa | grep apr
apr-util-1.2.8
apr-1.2.8
apr-0.9.12
apr-util-0.9.12
2)
# emerge --unmerge apr-0.9.12
3) (don't know whether necessary...)
# emerge apr kdesvn (this (re-)emerges apr-1.2.8 and kdesv-0.14.0)
4)
I started kdesvn but got a message that libapr-0.so.0 is missing, so I made a (dirty :) ) work-around:
# ln -sf /usr/lib/libapr-1.so.0 /usr/lib/libapr-0.so.0
# ln -sf /usr/lib/libaprutil-1.so.0 /usr/lib/libaprutil-0.so.0
http://christian--gross.de/?p=69
http://forums.gentoo.org/viewtopic-t-553946-highlight-convert+string+native+encoding+utf8.html

added mailto line
This message has 0 attachment(s)