Segmentation fault on opening specific email

Bug #779522 reported by laleshii
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Postler
New
Undecided
Unassigned

Bug Description

I am trying to access an email from Postler and I get Segmentation Fault on click.

I get the following output from gdb:

Reading symbols from /usr/bin/postler...Reading symbols from /usr/lib/debug/usr/bin/postler...done.
done.
(gdb) run
Starting program: /usr/bin/postler
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffe8e09700 (LWP 9755)]
[New Thread 0x7fffe8608700 (LWP 9756)]
[New Thread 0x7fffe7e07700 (LWP 9757)]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000443ba1 in postler_content_parse_body (self=0x964000, stream=0xf38230,
    content_type=0xf6d160 "multipart/alternative; boundary=\"=_alternative 00258606C2257869_=\"", error=0x7fffffffd0c8) at postler-content.vala:906
906 postler-content.vala: No such file or directory.
 in postler-content.vala

Revision history for this message
darius (dariuskellermann) wrote :

I'm having the same symptoms, but I'm unsure if it's the same bug. here's the output I've gathered from the terminal via "postler -v":
"
darius@darius-laptop:~$ postler -v
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x83ced00)" of type `GString'

** (postler-bureau:31096): CRITICAL **: postler-messages.vala:428: parse_address: assertion '!address.length < 1' failed
Speicherzugriffsfehler
"

Where "Speicherzugriffsfehler" means segmentation fault.

Revision history for this message
Jan Bader (jacob-michlaustderaffe) wrote :

I got the same Problem using the latest git Version. gdb output:

$ gdb /usr/bin/postler
GNU gdb (GDB) 7.4
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/postler...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/postler
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0x7fffe9ea7700 (LWP 25933)]
[New Thread 0x7fffa96a4700 (LWP 25934)]
[New Thread 0x7fffa8ea3700 (LWP 25935)]
[New Thread 0x7fffa2b9c700 (LWP 25940)]

Program received signal SIGSEGV, Segmentation fault.
0x000000000046adb9 in ?? ()
(gdb) continue
Continuing.
[Thread 0x7fffa2b9c700 (LWP 25940) exited]
[Thread 0x7fffa8ea3700 (LWP 25935) exited]
[Thread 0x7fffa96a4700 (LWP 25934) exited]
[Thread 0x7fffe9ea7700 (LWP 25933) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.