Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31641 - [midori] private mode crashes

Attached to Project: Community Packages
Opened by Zhuoyun Wei (wzyboy) - Saturday, 22 September 2012, 02:23 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Thursday, 27 September 2012, 13:47 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Bartłomiej Piotrowski (Barthalion)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: After upgrading to Midori 0.4.7-1, <code>midori --private</code> will return:

<pre>**
ERROR:/build/src/midori-0.4.7/katze/midori-paths.vala:107:midori_paths_get_config_filename: assertion failed: (_tmp1_ != NULL)
Aborted</pre>

But running midori first and then turning on private mode works fine.


Additional info:
* package version(s) 0.7.1-1
* config and/or log files etc.


Steps to reproduce: Run <code>midori --private</code>, wherever in terminal emulator or from .desktop file.
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Thursday, 27 September 2012, 13:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  midori 0.4.7-2
Comment by Alexander F. Rødseth (xyproto) - Saturday, 22 September 2012, 18:40 GMT
Thanks for reporting. Please consider reporting this upstream to the midori developers and also include an url to the bug report here.
Comment by Zhuoyun Wei (wzyboy) - Sunday, 23 September 2012, 06:34 GMT
@Alexander I've reported this bug to Modori @ Launchpad.
Comment by Alexander F. Rødseth (xyproto) - Monday, 24 September 2012, 14:01 GMT Comment by speps (archspeps) - Tuesday, 25 September 2012, 00:20 GMT
The attached patch seems to solve. Further informations on the bug page.
Let's see what upstream says.

Loading...