GNOME Bugzilla – Bug 737898
Crashes right at startup
Last modified: 2017-12-27 04:56:56 UTC
When starting Notes 3.14 on Mageia Cauldron, it segfaults immediately.
+ Trace 234176
Thread 7 (Thread 0x7fffd9b75700 (LWP 14919))
Thread 6 (Thread 0x7fffda376700 (LWP 14918))
Thread 5 (Thread 0x7fffdab77700 (LWP 14917))
Thread 4 (Thread 0x7fffe0b14700 (LWP 14916))
Thread 2 (Thread 0x7fffe3101700 (LWP 14914))
Inferior 1 [process 14909] will be killed. Quit anyway? (y or n)
Further info: this is when running from gdb. When attaching gdb later, bijiben actually starts up but crashes as soon as a note is opened. Backtrace again: Continuing. [Thread 0x7f20c5b75700 (LWP 15147) exited] [New Thread 0x7f20c5b75700 (LWP 15165)] [New Thread 0x7f20ccf50700 (LWP 15166)] Detaching after fork from child process 15167. [New Thread 0x7f20a7b2b700 (LWP 15169)] [New Thread 0x7f20a732a700 (LWP 15170)] [New Thread 0x7f20a6b29700 (LWP 15171)] openjdk version "1.8.0_40" OpenJDK Runtime Environment (build 1.8.0_40-b02) OpenJDK 64-Bit Server VM (build 25.40-b05, mixed mode) [New Thread 0x7f205f9c3700 (LWP 15192)] (bijiben:15136): GLib-CRITICAL **: g_variant_ref: assertion 'value->ref_count > 0' failed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Program received signal SIGTERM, Terminated. [Switching to Thread 0x7f20cf53d700 (LWP 15142)] 0x00007f20dea3c039 in raise (sig=15) at ../sysdeps/unix/sysv/linux/pt-raise.c:36 36 return INLINE_SYSCALL (tgkill, 3, pid, THREAD_GETMEM (THREAD_SELF, tid), Missing separate debuginfos, use: debuginfo-install flash-player-plugin-11.2.202.406-4.mga5.nonfree.x86_64 (gdb) thread apply all bt
+ Trace 234177
Thread 9 (Thread 0x7f20cf53d700 (LWP 15142))
Thread 1 (Thread 0x7f20e43e7940 (LWP 15136))
Bijiben crashes on startup for me as well. Output from Debian's gdb: Starting program: /usr/bin/bijiben bijiben [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe1a38700 (LWP 23543)] [New Thread 0x7fffe10ae700 (LWP 23544)] [New Thread 0x7fffdad44700 (LWP 23545)] [New Thread 0x7fffd9d0c700 (LWP 23546)] [New Thread 0x7fffd950b700 (LWP 23547)] [New Thread 0x7fffd8d0a700 (LWP 23548)] [New Thread 0x7fffcffff700 (LWP 23549)] [New Thread 0x7fffcf7fe700 (LWP 23550)] [New Thread 0x7fffceffd700 (LWP 23551)] [New Thread 0x7fffcd5f8700 (LWP 23552)] Unable to load location /home/myusername/.local/share/bijiben/.Trash: No such file or directory Program received signal SIGSEGV, Segmentation fault. 0x000000000043b176 in time_val_from_icaltime (itt=0x0, result=0x7fffffffe060) at provider/biji-memo-provider.c:81 81 iso = isodate_from_time_t (icaltime_as_timet (*itt));
Created attachment 288610 [details] gdb bt
(In reply to comment #3) > Created an attachment (id=288610) [details] > gdb bt thanks erusan, however I'm not sure this is the same. Which Debian are you on? Can you also provide me evolution version?
>I'm not sure this is the same I wasn't sure. Apologies. I'm running an up-to-date Debian testing. evolution is at 3.12.6 These problems did not occur with 3.12, but have occurred since Debian upgraded. I filed a bug with Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765381) and was asked to file it upstream.
(In reply to comment #5) > >I'm not sure this is the same > > I wasn't sure. Apologies. no problem > > I'm running an up-to-date Debian testing. evolution is at 3.12.6 > > These problems did not occur with 3.12, but have occurred since Debian > upgraded. I filed a bug with Debian > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765381) and was asked to > file it upstream. right, I will look & tell you if another report would be better
Some additional information: Bijiben seems to launch fine on a fresh install. Once the user's home folder is encrypted using ecryptfs, however, bijiben no longer launches. I encountered this after performing a fresh Debian testing install today, testing to see if bijiben launched (it did), and then encrypting the user's home folder with ecryptfs-utils ('ecryptfs-migrate-home' command).
FWIW, I observed the problem on an unencrypted btrfs home partition.
Bijiben code has changed in these 3 years and I don't have this kind of problem neither I was able to reproduce it. I'm doing some house cleaning, so if this problem still happens, please re-open it. Thx.