Bug 235652 - gedit crash as user: file gutf8.c: line 1537 (g_utf8_validate): assertion `str != NULL` failed
gedit crash as user: file gutf8.c: line 1537 (g_utf8_validate): assertion `st...
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gedit (Show other bugs)
4.0
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-09 05:14 EDT by Marek Mahut
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-30 21:09:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
strace of gedit crash under normal user (13.37 KB, application/x-gzip)
2007-04-09 05:17 EDT, Marek Mahut
no flags Details
normal gedit situation under root (54.22 KB, application/x-gzip)
2007-04-09 05:18 EDT, Marek Mahut
no flags Details

  None (edit)
Description Marek Mahut 2007-04-09 05:14:42 EDT
Description of problem:

On one of customer's system, gedit crash (segfault) with message "gedit crash:
file gutf8.c: line 1537 (g_utf8_validate): assertion `str != NULL` failed" on
console.

Version-Release number of selected component (if applicable):

gedit-2.8.1-4
glibc-2.3.4-2.25

How reproducible:

Everytme.

Steps to Reproduce:
1. Open gedit (as user, it works under root)
2. Gedit segfaults.

  
Actual results:

Gedit crash.

Expected results:

Gedit opens a file and customer is happy.

Additional info:

Will attach it in next post.
Comment 1 Marek Mahut 2007-04-09 05:17:30 EDT
Created attachment 151949 [details]
strace of gedit crash under normal user
Comment 2 Marek Mahut 2007-04-09 05:18:15 EDT
Created attachment 151950 [details]
normal gedit situation under root
Comment 5 Ray Strode [halfline] 2007-05-30 21:09:20 EDT
If it happens again, please reopen.

Note You need to log in before you can comment on or make changes to this bug.