Ubuntu

Is Midori really supported?

Asked by Mike O'Connor

Midori crashes almost immediately, seemingly in response to almost anything I do. I was able to load a page, but then do nothing else. This was repeated upon several reboots. I first installed the latest version from Midori, but then when I tried to report the problem using the menu item for that (gingerly, as if that would avert a crash) the dialog (accessing it DID cause a crash but the dialog stayed around) said that I the problem would not be reported because I was not using an official Ubuntu version.

So I hit sudo apt-get remove --purge midori, which seemed to be carried out OK, and then used the Ubuntu Software Center--- this is 12.04 LTS on a 32-bit i386 machine--- to install the official (out of date) version.

The final insult: after installing the official Ubuntu version because it said that I needed that to report the problem, it said the same thing after I launched the official version (which promptly also crashed, again leaving the problem-reporting dialog box behind) and tried again to report the problem.

Finally, upon attempting to post a negative review of the package on the Ubuntu Software Center after having installed from there without any indicated errors it refused to accept my review on the following declared error: "Server's response was :: package midori not in lp-ppa-midori precise for precise" (this is an error upon trying to post a review; no error was reported upon installation). I had previously run "sudo add-apt-repository ppa:midori", successfully, and I had run "sudo apt-get update" and "upgrade" first, before the official install.

Additional beef... Holy cow, the captcha to sign up for the Ubunto Software Center is very nearly illegible--- much too much so. I had to skip through about ten and I was wrong twice.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said : 		#1

By installing different versions of midori from various sources (official Ubuntu source, midori PPA, ...) you might have created a mixture of incompatible versions.

I recommend that you deinstall your current version and check whether there are any leftovers to delete (sudo updatedb; locate midori), and then re-start with a clean installation of midori.

You have to be aware that you can report bugs only for the (maybe outdated) version in the official Ubuntu source, not for a version from a PPA, and not for the version downloaded from midori-browser.org. Questions/bugs for the midori version from the midori PPA or the version from midori-browser.org should be entered in the https://launchpad.net/midori area, not on https://launchpad.net/ubuntu/+source/midori

Revision history for this message
Mike O'Connor (moc-i) said : 		#2

Thanks for the prompt reply m-hampl. But the cheeky remark "You have to be aware that you can report bugs only for the (maybe outdated) version in the official Ubuntu source, not for a version from a PPA, and not for the version downloaded from midori-browser.org" was inappropriate since it was by my reporting on the prior installation of the up-to-date version from ppa that you came by your concept that I perhaps had a mixture of incompatible versions (that's exactly why I mentioned it). And of course I WAS after all reporting here on a problem with the official Ubuntu version.

I also stated that I had run sudo apt-get remove --purge midori prior to installing from the Ubuntu Software Center. Shouldn't that have gotten rid of all prior installations? I did that to eliminate potential conflicts.

Anyway, I'm grateful to have been told about sudo updatedb. Right after filing my bug complaint I had used the Ubuntu Software Center to uninstall, but just now I did what you suggested and ran "sudo updatedb" and "locate midori" and, lo and behold, there were many midori files... which I removed using sudo apt-get --purge remove midori. Even sudo apt-get autoclean removed something additional. So evidently the Ubuntu Software Center uninstall doesn't work thoroughly.

And I then just now re-installed Midori from the Ubuntu Software Center and got exactly the same crashes. And I still can't write a review in Ubuntu Software Center for the same reason. And so I again uninstalled it using the Ubuntu Software Center and again ran sudo updatedb and locate midori and again there were many files to remove which I did using sudo apt-get --purge remove.

Next I'm going to move to my 64-bit laptop and try it there. I've never installed Midori on it.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#3

If you rate parts of my answer as being inappropriate, I have to apologize. It was not my intention to sound rude or insulting. I just wanted to explain the general rules for bug reporting (see also https://help.ubuntu.com/community/ReportingBugs ).

Re-reading your original post, I still have to conclude that currently you are using a PPA version (the sequence '"sudo add-apt-repository ppa:midori", "sudo apt-get update" and "upgrade"' will configure your system in a way that the software-center installs the PPA version).

What is the output of the terminal commands

uname -a
lsb_release -a
midori --version
apt-cache policy midori

Revision history for this message
Daniel Letzeisen (dtl131) said : 		#4

After purging midori package, there may be leftover (user configuration) files in your home folder. Check ~/.config/midori
(Note that this is also true for other packages).

I've used midori before and it was well-behaved for me. If you're really interested in debugging the crash, there are ways to manually get a backtrace. https://wiki.ubuntu.com/Backtrace

Revision history for this message
Mike O'Connor (moc-i) said : 		#5

So sorry to m-hampl for being snippy myself. I went overboard.

And thanks to dtl131 for also trying to help. I have done everything that both of you suggested. Manfred is correct that the ppa version was stuck in there in apt preferences. Here is the printout that he requested:

    mike@Presario:~$ uname -a
    Linux Presario 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:55:18 UTC 2014 i686 athlon i386 GNU/Linux
    mike@Presario:~$ lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.4 LTS
    Release: 12.04
    Codename: precise
    mike@Presario:~$ midori --version
    The program 'midori' is currently not installed. You can install it by typing:
    sudo apt-get install midori
    mike@Presario:~$ apt-cache policy midori
    midori:
      Installed: (none)
      Candidate: 0.5.8-1~precise~ppa1
      Version table:
         0.5.8-1~precise~ppa1 0
            500 http://ppa.launchpad.net/midori/ppa/ubuntu/ precise/main i386 Packages
         0.4.3-1ubuntu1 0
            500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages

So I did some homework and discovered that the ppp.launchpad.net reference is not in any /etc/apt/sources.list* file but is instead in /etc/sources.list.d/midori-ppa-precise.list and in /etc/sources.list.d/midori-ppa-precise.list.save. In both files I commented out http://ppa.launchpad.net/midori/ppa/ubuntu/ precise/main i386 Packages.

Upon reinstalling midori using the Ubuntu Software Center I got:

    mike@Presario:~$ apt-cache policy midori
    midori:
      Installed: 0.4.3-1ubuntu1
      Candidate: 0.4.3-1ubuntu1
      Version table:
     *** 0.4.3-1ubuntu1 0
            500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages
            100 /var/lib/dpkg/status

This is indeed not the newer version that I had previously installed but is the same as the version in the Unbuntu Software Center.

Now, Daniel is right about there having been old .config/midori files (and I suppose that the reasonable idea was that they could cause the old yet official version of the program to crash, since the configs would be for the new version). Prior to reinstalling midori I ran the first part of the following:

    dpkg -l | grep '^rc' | awk '{print $2}' | xargs dpkg --purge

I got that from https://help.ubuntu.com/community/AptGet/Howto. It didn't list midori even though the /home/mike/.config/midori files were there and I had not yet reinstalled midori and apt-cache policy midori was showing it not installed. I therefore did not run the --purge part.

So I manually deleted the .config/midori directory.

Finally, I ran the gdb program as directed on the link that you provided. This time when the program launched it crashed again, but not as fast. I was able to start http://finance.yahoo.com but when I clicked on a story link the story launched but when, with difficulty, I scrolled to the bottom the program froze (mouse working only, clicking it did nothing). That was with gdb. When I started it without gdb the behavior was much the same but instead of freezing it quit. Here's the gdb backtrace printout:

GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
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 "i686-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/midori...(no debugging symbols found)...done.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run midori
Starting program: /usr/bin/midori midori
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb7d73b40 (LWP 9370)]
[New Thread 0xb73ffb40 (LWP 9371)]
[New Thread 0xb69ffb40 (LWP 9372)]
[New Thread 0xb60feb40 (LWP 9373)]
[New Thread 0xb3be0b40 (LWP 9375)]
[New Thread 0xb2da7b40 (LWP 9376)]
[New Thread 0xb2571b40 (LWP 9377)]
[New Thread 0xb0d16b40 (LWP 9378)]
[New Thread 0xb0515b40 (LWP 9379)]
[New Thread 0xafd14b40 (LWP 9380)]
[New Thread 0xaf513b40 (LWP 9381)]
[Thread 0xaf513b40 (LWP 9381) exited]
[Thread 0xb2da7b40 (LWP 9376) exited]
[New Thread 0xb2da7b40 (LWP 9382)]
[New Thread 0xaf513b40 (LWP 9383)]
[New Thread 0xae347b40 (LWP 9384)]
[Thread 0xae347b40 (LWP 9384) exited]
[Thread 0xaf513b40 (LWP 9383) exited]
[Thread 0xb0515b40 (LWP 9379) exited]
[Thread 0xb0d16b40 (LWP 9378) exited]
[Thread 0xb2da7b40 (LWP 9382) exited]
[New Thread 0xb2da7b40 (LWP 9385)]
[New Thread 0xb0d16b40 (LWP 9386)]
[New Thread 0xb0515b40 (LWP 9387)]
[New Thread 0xaf513b40 (LWP 9388)]
[New Thread 0xacfe7b40 (LWP 9389)]
[New Thread 0xac7e6b40 (LWP 9390)]
[New Thread 0xabfe5b40 (LWP 9391)]
[New Thread 0xab472b40 (LWP 9392)]
[New Thread 0xaab71b40 (LWP 9393)]
[Thread 0xaab71b40 (LWP 9393) exited]
[Thread 0xab472b40 (LWP 9392) exited]
[Thread 0xabfe5b40 (LWP 9391) exited]
[Thread 0xafd14b40 (LWP 9380) exited]
[Thread 0xaf513b40 (LWP 9388) exited]
[Thread 0xb0d16b40 (LWP 9386) exited]
[Thread 0xb2da7b40 (LWP 9385) exited]
[Thread 0xb0515b40 (LWP 9387) exited]
[Thread 0xac7e6b40 (LWP 9390) exited]
[New Thread 0xac7e6b40 (LWP 9394)]
[Thread 0xac7e6b40 (LWP 9394) exited]
[Thread 0xb2571b40 (LWP 9377) exited]
[New Thread 0xb2571b40 (LWP 9395)]
[New Thread 0xac7e6b40 (LWP 9396)]
[Thread 0xacfe7b40 (LWP 9389) exited]
[Thread 0xb2571b40 (LWP 9395) exited]
[New Thread 0xb2571b40 (LWP 9397)]
[New Thread 0xacfe7b40 (LWP 9398)]
[New Thread 0xb0515b40 (LWP 9399)]
[Thread 0xb2571b40 (LWP 9397) exited]
[Thread 0xb0515b40 (LWP 9399) exited]
[Thread 0xac7e6b40 (LWP 9396) exited]

(midori:9367): GLib-GObject-WARNING **: value "-nan" of type `gdouble' is invalid or out of range for property `upper' of type `gdouble'

(midori:9367): GLib-GObject-WARNING **: value "-nan" of type `gdouble' is invalid or out of range for property `upper' of type `gdouble'
[New Thread 0xac7e6b40 (LWP 9400)]
[New Thread 0xb0515b40 (LWP 9401)]
[New Thread 0xb2571b40 (LWP 9402)]
[New Thread 0xb2da7b40 (LWP 9403)]
[New Thread 0xa9bedb40 (LWP 9404)]
[New Thread 0xa93ecb40 (LWP 9405)]
[Thread 0xb2571b40 (LWP 9402) exited]
[Thread 0xb2da7b40 (LWP 9403) exited]
[Thread 0xacfe7b40 (LWP 9398) exited]
[Thread 0xa9bedb40 (LWP 9404) exited]
[New Thread 0xa9bedb40 (LWP 9406)]
[Thread 0xac7e6b40 (LWP 9400) exited]
[Thread 0xa93ecb40 (LWP 9405) exited]
[Thread 0xb0515b40 (LWP 9401) exited]
[New Thread 0xb0515b40 (LWP 9407)]

(midori:9367): GLib-GObject-WARNING **: value "-nan" of type `gdouble' is invalid or out of range for property `upper' of type `gdouble'

(midori:9367): GLib-GObject-WARNING **: value "-nan" of type `gdouble' is invalid or out of range for property `upper' of type `gdouble'

(midori:9367): GLib-GObject-WARNING **: value "-nan" of type `gdouble' is invalid or out of range for property `upper' of type `gdouble'

(midori:9367): GLib-GObject-WARNING **: value "-nan" of type `gdouble' is invalid or out of range for property `upper' of type `gdouble'

(midori:9367): GLib-GObject-WARNING **: value "-nan" of type `gdouble' is invalid or out of range for property `upper' of type `gdouble'
[Thread 0xa9bedb40 (LWP 9406) exited]
[New Thread 0xa9bedb40 (LWP 9408)]
[New Thread 0xa93ecb40 (LWP 9409)]
[New Thread 0xac7e6b40 (LWP 9410)]
[Thread 0xac7e6b40 (LWP 9410) exited]
[Thread 0xa93ecb40 (LWP 9409) exited]
[New Thread 0xa93ecb40 (LWP 9411)]
[Thread 0xa9bedb40 (LWP 9408) exited]
[Thread 0xb0515b40 (LWP 9407) exited]
[New Thread 0xb0515b40 (LWP 9412)]
[New Thread 0xa9bedb40 (LWP 9413)]
[Thread 0xa9bedb40 (LWP 9413) exited]
[New Thread 0xa9bedb40 (LWP 9414)]
[New Thread 0xacfe7b40 (LWP 9415)]
[Thread 0xacfe7b40 (LWP 9415) exited]
[Thread 0xa9bedb40 (LWP 9414) exited]
[Thread 0xb0515b40 (LWP 9412) exited]
[New Thread 0xb0515b40 (LWP 9416)]
[Thread 0xb0515b40 (LWP 9416) exited]
[New Thread 0xb0515b40 (LWP 9420)]
midori: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed.
[New Thread 0xa9bedb40 (LWP 9421)]

Program received signal SIGABRT, Aborted.
0x00132416 in __kernel_vsyscall ()
(gdb) backtrace full
#0 0x00132416 in __kernel_vsyscall ()
No symbol table info available.
#1 0x027761df in raise () from /lib/i386-linux-gnu/libc.so.6
No symbol table info available.
#2 0x02779825 in abort () from /lib/i386-linux-gnu/libc.so.6
No symbol table info available.
#3 0x0276f085 in ?? () from /lib/i386-linux-gnu/libc.so.6
No symbol table info available.
#4 0x0276f137 in __assert_fail () from /lib/i386-linux-gnu/libc.so.6
No symbol table info available.
#5 0x0098ef6a in cairo_surface_set_device_offset () from /usr/lib/i386-linux-gnu/libcairo.so.2
No symbol table info available.
#6 0x00754194 in gdk_window_begin_paint_region () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
No symbol table info available.
#7 0x003eb0f3 in gtk_main_do_event () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#8 0x007592bf in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
No symbol table info available.
#9 0x00759262 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
No symbol table info available.
#10 0x0078bcd3 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
No symbol table info available.
#11 0x00753dc4 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
No symbol table info available.
#12 0x0075604f in gdk_window_process_all_updates () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
No symbol table info available.
#13 0x007560c8 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
No symbol table info available.
#14 0x00730f88 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
No symbol table info available.
#15 0x001c6810 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#16 0x001c8d46 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#17 0x001c90e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#18 0x001c952b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#19 0x003e9b8f in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#20 0x8001c574 in main ()
No symbol table info available.
(gdb) info registers
eax 0x0 0
ecx 0x2497 9367
edx 0x6 6
ebx 0x2497 9367
esp 0xbfffe980 0xbfffe980
ebp 0x80c81f10 0x80c81f10
esi 0x0 0
edi 0x28edff4 42917876
eip 0x132416 0x132416 <__kernel_vsyscall+2>
eflags 0x202 [ IF ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51
(gdb) x/16i $pc
=> 0x132416 <__kernel_vsyscall+2>: ret
   0x132417: add %ch,(%esi)
   0x132419: jae 0x132483
   0x13241b: jae 0x132491
   0x13241d: jb 0x132493
   0x13241f: popa
   0x132420: bound %eax,(%eax)
   0x132422: cs
   0x132423: push $0x687361
   0x132428: cs
   0x132429: fs
   0x13242a: jns 0x13249a
   0x13242c: jae 0x1324a7
   0x13242e: insl (%dx),%es:(%edi)
   0x13242f: add %ch,(%esi)
   0x132431: fs
(gdb) thread apply all backtrace

Thread 49 (Thread 0xa9bedb40 (LWP 9421)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x02737d13 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2 0x00208900 in g_cond_wait_until () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0x0019c0b9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 0x001ed03b in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5 0x001ec673 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6 0x02733d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#7 0x02837bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 48 (Thread 0xb0515b40 (LWP 9420)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x02737d13 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2 0x057829d6 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so
#3 0x057a6193 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so
#4 0x05782cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so
#5 0x057831d6 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so
#6 0x02733d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#7 0x02837bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 42 (Thread 0xa93ecb40 (LWP 9411)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x02737d13 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2 0x00208900 in g_cond_wait_until () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0x0019c0b9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 0x001ed03b in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5 0x001ec673 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6 0x02733d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#7 0x02837bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 6 (Thread 0xb3be0b40 (LWP 9375)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x02737d13 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2 0x023f74ed in WTF::ThreadCondition::timedWait(WTF::Mutex&, double) () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#3 0x0223f1d2 in JSC::Heap::waitForRelativeTimeWhileHoldingLock(double) () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#4 0x0223f234 in JSC::Heap::waitForRelativeTime(double) () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#5 0x0223f287 in JSC::Heap::blockFreeingThreadMain() () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#6 0x0223f33b in JSC::Heap::blockFreeingThreadStartFunc(void*) () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#7 0x023f6b92 in ?? () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#8 0x023f6cfe in ?? () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#9 0x02733d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#10 0x02837bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 5 (Thread 0xb60feb40 (LWP 9373)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x0273796b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2 0x023f7443 in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#3 0x012a878c in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
#4 0x012a8a75 in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
#5 0x012a8acb in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
#6 0x023f6b92 in ?? () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#7 0x023f6cfe in ?? () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#8 0x02733d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#9 0x02837bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 4 (Thread 0xb69ffb40 (LWP 9372)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x02800d06 in nanosleep () from /lib/i386-linux-gnu/libc.so.6
#2 0x02800aff in sleep () from /lib/i386-linux-gnu/libc.so.6
#3 0x023d5aae in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#4 0x023d5b5b in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#5 0x02733d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6 0x02837bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xb73ffb40 (LWP 9371)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x02829460 in poll () from /lib/i386-linux-gnu/libc.so.6
#2 0x001d6a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0x001c906e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 0x001c952b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5 0x0089a4aa in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6 0x001ec673 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7 0x02733d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8 0x02837bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb7d73b40 (LWP 9370)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x02829460 in poll () from /lib/i386-linux-gnu/libc.so.6
#2 0x001d6a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3 0x001c906e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4 0x001c952b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5 0x045dd134 in ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
#6 0x001ec673 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7 0x02733d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8 0x02837bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb7fd5880 (LWP 9367)):
#0 0x00132416 in __kernel_vsyscall ()
#1 0x027761df in raise () from /lib/i386-linux-gnu/libc.so.6
#2 0x02779825 in abort () from /lib/i386-linux-gnu/libc.so.6
#3 0x0276f085 in ?? () from /lib/i386-linux-gnu/libc.so.6
#4 0x0276f137 in __assert_fail () from /lib/i386-linux-gnu/libc.so.6
#5 0x0098ef6a in cairo_surface_set_device_offset () from /usr/lib/i386-linux-gnu/libcairo.so.2
#6 0x00754194 in gdk_window_begin_paint_region () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#7 0x003eb0f3 in gtk_main_do_event () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#8 0x007592bf in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#9 0x00759262 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#10 0x0078bcd3 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#11 0x00753dc4 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#12 0x0075604f in gdk_window_process_all_updates () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#13 0x007560c8 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#14 0x00730f88 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#15 0x001c6810 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#16 0x001c8d46 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#17 0x001c90e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#18 0x001c952b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#19 0x003e9b8f in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#20 0x8001c574 in main ()
(gdb) quit
A debugging session is active.

 Inferior 1 [process 9367] will be killed.

Quit anyway? (y or n)

Regrettably it's almost entirely beyond my understanding (I code, but only in Python, Javascript, etc... no registers please).

Thanks again to you both and if you see a way to help I would be appreciative. I do have Midori running on a 64-bit laptop; the problem is on the old 32-bit desktop.

-Mike

Revision history for this message
Daniel Letzeisen (dtl131) said : 		#6

I wonder if it's related to: https://bugs.launchpad.net/midori/+bug/1290632
Both complain about libcairo

Anyway, your backtrace isn't the best because you don't have the appropriate debugging packages installed (a developer would want your backtrace to have those).

Now that you have the package situation straightened out, can you report the bug with apport? apport does the heavy lifting for you with tracing.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#7

Have you tried renaming the Midori config foldee then launch it to get vanilla settings for the browser?

Have you tried (if you aren't already) the Unity2D session which is selectable on the login page?

Thanks

Revision history for this message
Mike O'Connor (moc-i) said : 		#8

Hi actionparsnip,

    Thanks much for responding. After Daniel Letzeisen suggested that
    there might be a problem with the .config/midori files from the
    previous install being there--- made sense to me--- I simply deleted
    the folder. That was after having done a "sudo apt-get --purge
    remove midori".

    I have since re-installed and the folder has reappeared and it does
    function to restore the home page that I designated (which I can see
    but not navigate on without causing a crash).

    I vaguely recall having heard of Unity 2D versus 3D, but I forgot
    what they were about so I Googled. That led me to run "locate
    unity-2d" in a terminal, which confirmed directory contents for it.

    So I went to login and hit the icon for Unity version selection and
    tried to select Unity 2D. It was there, but didn't seem to give any
    positive indication of having been selected.

    I nonetheless logged on and ran Midori again and it crashed exactly
    as before. And the desktop environment looked the same as usual.

    I then did some more Googling (to find out if I was actually in
    Unity 2D) and then ran and got the following in the terminal:

        mike@Presario:~$ echo $DESKTOP_SESSION
        ubuntu-2d

    So maybe I've always been in Unity 2D. I saw some references to the
    fact that Ubuntu automatically loads 2D on older machines with
    certain characteristics. I've also installed Midori on my new 64-bit
    laptop and there are no problems.

-Mike

On 04/05/2014 10:56 PM, actionparsnip wrote:
> Your question #246499 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/246499
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> Have you tried renaming the Midori config foldee then launch it to get
> vanilla settings for the browser?
>
> Have you tried (if you aren't already) the Unity2D session which is
> selectable on the login page?
>
> Thanks
>

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#9

Are there any bugs reported?

If you want a light browser I can suggest Arora.
https://apps.ubuntu.com/cat/applications/precise/arora/

Revision history for this message
Mike O'Connor (moc-i) said : 		#10

Yes, see https://bugs.launchpad.net/ubuntu/+source/midori/+bug/1302980.
Sorry that I didn't mention that before but I'm new to the system and
didn't realize that you weren't looking at it.

Daniel Letzeisen remarked that it might be related to
https://bugs.launchpad.net/midori/+bug/1290632.

I'll look into arora. Yes I'm looking for a lightweight browser.

-Mike

On 04/05/2014 11:36 PM, actionparsnip wrote:
> Your question #246499 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/246499
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> Are there any bugs reported?
>
> If you want a light browser I can suggest Arora.
> https://apps.ubuntu.com/cat/applications/precise/arora/
>

Revision history for this message
Launchpad Janitor (janitor) said : 		#11

This question was expired because it remained in the 'Open' state without activity for the last 15 days.