Ubuntu
midori package

midori crashes when modifying settings

Bug #1302247 reported by Lyn Perrine
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
midori (Ubuntu)
New
Medium
Unassigned

Bug Description

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
midori:
  Installed: 0.4.3+dfsg-0.1
  Candidate: 0.4.3+dfsg-0.1
  Version table:
 *** 0.4.3+dfsg-0.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status
I expected to be able to change the settings of midori and not have the browser crash.

Instead the browser crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: midori 0.4.3+dfsg-0.1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: LXDE
Date: Thu Apr 3 16:08:39 2014
ExecutablePath: /usr/bin/midori
InstallationDate: Installed on 2014-01-02 (91 days ago)
InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64 (20140101)
ProcCmdline: midori
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: midori
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Lyn Perrine (walterorlin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 accumulate (accumulator=<error reading variable: Cannot access memory at address 0xffffffffffffff00>, handler_return=0xffffffffffffff10, return_accu=0xffffffffffffff30, ihint=0xffffffffffffff60) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3056
   [Error: /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c was not found in source tree]
 #1 g_signal_emit_valist (instance=<error reading variable: Cannot access memory at address 0xfffffffffffffef0>, instance@entry=<error reading variable: Cannot access memory at address 0x8>, signal_id=<optimized out>, detail=<error reading variable: Cannot access memory at address 0xfffffffffffffeec>, var_args=<error reading variable: Cannot access memory at address 0xfffffffffffffee0>) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3221
   [Error: /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c was not found in source tree]
StacktraceTop:
 accumulate (accumulator=<error reading variable: Cannot access memory at address 0xffffffffffffff00>, handler_return=0xffffffffffffff10, return_accu=0xffffffffffffff30, ihint=0xffffffffffffff60) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3056
 g_signal_emit_valist (instance=<error reading variable: Cannot access memory at address 0xfffffffffffffef0>, instance@entry=<error reading variable: Cannot access memory at address 0x8>, signal_id=<optimized out>, detail=<error reading variable: Cannot access memory at address 0xfffffffffffffeec>, var_args=<error reading variable: Cannot access memory at address 0xfffffffffffffee0>) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3221

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in midori (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Lyn Perrine (walterorlin)
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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