Ubuntu
falkon package

lubuntu 18.10 falkon nouveau_pushbuf_kick

Bug #1794917 reported by Chris Guiver
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
falkon (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Falkon crashes... (no messages on screen)

Daily image - tested ("check disk for defects") fine on my usual d610 (laptop), so tried on another system, hp dx6120. (pentium 4, dual core, 1.5gb ram)

There were messages on boot "acpi bios error (bug) \_sb.pcio._..." that I ignored assuming it's an outdated bios or something..., a slower boot (compared d610 laptop), but system was fine once booted.

Testing had issues only with falkon. On opening via menu, it would close.
I ran it from terminal, then got messages.
I shutdown system, walked thumb-drive back to d610 & no issues with falkon.

Returned to this hp dx6120, booted
I opened terminal `sudo apt update` (no need, just to confirm it has network etc)
Then opened `falkon` from terminal.

// note: copy of terminal output from this point on follows

Falkon started - entered `youtube.com` into search; no issues (youtube showed menu)
Searched for 'bloomberg live' on youtube ; got list of matching search videos

On selecting the "Bloomberg Live" stream, the window draws normally, then crash back to terminal.

NOTE: it's not just bloomberg; but appears to be any stream (news live I tried first time)

I `ubuntu-bug` reported on dx6120, but on opening browser to submit; crash again (paste following this) I suspect because falkon would try & continue... The Qterminal messages were saved (featherpad), & `scp` to this box where I'm completing this.

I got the error multiple times, multiple boots; different youtube videos - but I only tried youtube.

This is the first test day of lubuntu 18.10 on dx6120

// --------
// Terminal output from 'falkon' & 'ubuntu-bug'

lubuntu@lubuntu:~$ falkon
Falkon: Creating new profile directory
Error creating database schema "No query Unable to fetch row"
Falkon: 1 extensions loaded
Xlib: sequence lost (0x105a1 > 0x5a5) in reply type 0x0!
Received signal 11 SEGV_MAPERR 00000000510d
#0 0x0000b1cf38bb <unknown>
#1 0x0000b1cf3ec2 <unknown>
#2 0x0000b1cf44ad <unknown>
#3 0x0000b7fbed58 ([vdso]+0xd57)
#4 0x0000a6c3efd4 <unknown>
#5 0x0000a669893f <unknown>
#6 0x0000a6698c63 <unknown>
#7 0x0000a66998fa nouveau_pushbuf_kick
#8 0x0000a6c3f0b2 <unknown>
#9 0x0000a68dfa61 <unknown>
#10 0x0000a671a4f9 <unknown>
#11 0x0000b26721a3 <unknown>
#12 0x0000b28a2fbd <unknown>
#13 0x0000b281c123 <unknown>
#14 0x0000b2847100 <unknown>
#15 0x0000b457ce87 <unknown>
#16 0x0000b458e85e <unknown>
#17 0x0000b45925fa <unknown>
#18 0x0000b45976a3 <unknown>
#19 0x0000b4597775 <unknown>
#20 0x0000b4593acc <unknown>
#21 0x0000b4581370 <unknown>
#22 0x0000b1cf4670 <unknown>
#23 0x0000b1d161a5 <unknown>
#24 0x0000b1d16bb2 <unknown>
#25 0x0000b1d16d86 <unknown>
#26 0x0000b1d19579 <unknown>
#27 0x0000b1d3a338 <unknown>
#28 0x0000b1d5c71f <unknown>
#29 0x0000b1d581ba <unknown>
#30 0x0000af6dafed start_thread
#31 0x0000b6c91a76 clone
  gs: 00000033 fs: 00000000 es: 0000007b ds: 0000007b
 edi: 02030f50 esi: 054393e4 ebp: 7fe21b30 esp: 95feb320
 ebx: a7348000 edx: 01c16090 ecx: 00000000 eax: 00005101
 trp: 0000000e err: 00000006 ip: a6c3efd4 cs: 00000073
 efl: 00210202 usp: 95feb320 ss: 0000007b
[end of stack trace]
Calling _exit(1). Core file will not be generated.

lubuntu@lubuntu:~$ ubuntu-bug falkon

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...................................................................

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (13.6 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): s

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.

97%

*** To continue, you must visit the following URL:

  https://bugs.launchpad.net/ubuntu/+source/falkon/+filebug/aa556374-c2d0-11e8-b34a-002481e7f48a?

You can launch a browser now, or copy this URL into a browser on another computer.

Choices:
  1: Launch a browser now
  C: Cancel
Please choose (1/C):
Choices:
  1: Launch a browser now
  C: Cancel
Please choose (1/C): 1
Falkon: 1 extensions loaded
[3532:3604:0928/034343.178607:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3604:0928/034343.179056:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3604:0928/034343.179369:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[3532:3604:0928/034343.182933:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3604:0928/034343.185472:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3604:0928/034343.185813:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[3532:3549:0928/034346.053388:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3549:0928/034346.053888:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3549:0928/034346.054182:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[3532:3549:0928/034346.057193:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3549:0928/034346.057668:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3549:0928/034346.058034:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
Xlib: sequence lost (0x105d5 > 0x5d7) in reply type 0x0!
[3532:3548:0928/034442.334637:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3548:0928/034442.334719:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3548:0928/034442.334818:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[3532:3548:0928/034442.337023:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3548:0928/034442.337099:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3548:0928/034442.337188:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[3532:3548:0928/034446.172661:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3548:0928/034446.172761:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3548:0928/034446.172858:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[3532:3548:0928/034446.183019:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3548:0928/034446.183120:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3532:3548:0928/034446.183221:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
free(): invalid pointer
Received signal 6
#0 0x0000b1c588bb <unknown>
#1 0x0000b1c58ec2 <unknown>
#2 0x0000b1c594ad <unknown>
#3 0x0000b7f23d58 ([vdso]+0xd57)
#4 0x0000b7f23d41 ([vdso]+0xd40)
#5 0x0000b6b2a512 gsignal
#6 0x0000b6b142b6 abort
#7 0x0000b6b6c74c <unknown>
#8 0x0000b6b735dd <unknown>
#9 0x0000b6b74c4b <unknown>
#10 0x0000b6d50768 operator delete()
#11 0x0000b2819f2e <unknown>
#12 0x0000b281da04 <unknown>
#13 0x0000b279375e <unknown>
#14 0x0000b27937c2 <unknown>
#15 0x0000b27ac100 <unknown>
#16 0x0000b44e1e87 <unknown>
#17 0x0000b44f385e <unknown>
#18 0x0000b44f75fa <unknown>
#19 0x0000b44fc6a3 <unknown>
#20 0x0000b44fc775 <unknown>
#21 0x0000b44f8b4c <unknown>
#22 0x0000b44e6370 <unknown>
#23 0x0000b1c59670 <unknown>
#24 0x0000b1c7b1a5 <unknown>
#25 0x0000b1c7bbb2 <unknown>
#26 0x0000b1c7bd86 <unknown>
#27 0x0000b1c7e579 <unknown>
#28 0x0000b1c9f338 <unknown>
#29 0x0000b1cc171f <unknown>
#30 0x0000b1cbd1ba <unknown>
#31 0x0000af63ffed start_thread
#32 0x0000b6bf6a76 clone
  gs: 00000033 fs: 00000000 es: 0000007b ds: 0000007b
 edi: 00000000 esi: 00000008 ebp: 966ec0dc esp: 966ec0c0
 ebx: 00000002 edx: 00000000 ecx: 966ec0dc eax: 00000000
 trp: 00000000 err: 00000000 ip: b7f23d41 cs: 00000073
 efl: 00200246 usp: 966ec0c0 ss: 0000007b
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Falkon: 1 extensions loaded
[3623:3639:0928/034535.578254:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3623:3639:0928/034535.578553:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3623:3639:0928/034535.578733:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[3623:3639:0928/034535.581082:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3623:3639:0928/034535.581352:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[3623:3639:0928/034535.581524:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
falkon: ../../nouveau/pushbuf.c:233: pushbuf_krel: Assertion `pkref' failed.
Received signal 6
#0 0x0000b1c2e8bb <unknown>
#1 0x0000b1c2eec2 <unknown>
#2 0x0000b1c2f4ad <unknown>
#3 0x0000b7ef9d58 ([vdso]+0xd57)
#4 0x0000b7ef9d41 ([vdso]+0xd40)
#5 0x0000b6b00512 gsignal
#6 0x0000b6aea2b6 abort
#7 0x0000b6aea1c1 <unknown>
#8 0x0000b6af8369 __assert_fail
#9 0x0000a65d31d9 <unknown>
#10 0x0000a65d4827 nouveau_pushbuf_reloc
#11 0x0000a6b869e9 <unknown>
#12 0x0000a6b705a4 <unknown>
#13 0x0000a6b707ee <unknown>
#14 0x0000a6ae98eb <unknown>
#15 0x0000a6b7beb9 <unknown>
#16 0x0000a6b83a1b <unknown>
#17 0x0000a6b87126 <unknown>
#18 0x0000a6af0f78 <unknown>
#19 0x0000a6a4b298 <unknown>
#20 0x0000a6827a56 <unknown>
#21 0x0000a67e9453 <unknown>
#22 0x0000a67e9eef <unknown>
#23 0x0000afa4ecee <unknown>
#24 0x0000af9dd472 QPlatformBackingStore::composeAndFlush()
#25 0x0000a809314d <unknown>
#26 0x0000b74c17e4 <unknown>
#27 0x0000b74c341c <unknown>
#28 0x0000b74c472a <unknown>
#29 0x0000b74c48d9 <unknown>
#30 0x0000b74de267 QWidgetPrivate::syncBackingStore()
#31 0x0000b74f85e9 QWidget::event()
#32 0x0000b761879f QMainWindow::event()
#33 0x0000b7ba2c07 BrowserWindow::event()
#34 0x0000b74b4096 QApplicationPrivate::notify_helper()
#35 0x0000b74bbfc9 QApplication::notify()
#36 0x0000b70959da QCoreApplication::notifyInternal2()
#37 0x0000b74c584d <unknown>
#38 0x0000b74c645d <unknown>
#39 0x0000b74e0268 QWidget::repaint()
#40 0x0000b7684da3 QTabBar::mouseReleaseEvent()
#41 0x0000b7cb6915 TabBarHelper::mouseReleaseEvent()
#42 0x0000b74f84ba QWidget::event()
#43 0x0000b7682e9d QTabBar::event()
#44 0x0000b7cb60bd TabBarHelper::event()
#45 0x0000b74b4096 QApplicationPrivate::notify_helper()
#46 0x0000b74bc66e QApplication::notify()
#47 0x0000b70959da QCoreApplication::notifyInternal2()
#48 0x0000b74bb3ac QApplicationPrivate::sendMouseEvent()
#49 0x0000b7516736 <unknown>
#50 0x0000b7519aa1 <unknown>
#51 0x0000b74b4096 QApplicationPrivate::notify_helper()
#52 0x0000b74bbfc9 QApplication::notify()
#53 0x0000b70959da QCoreApplication::notifyInternal2()
#54 0x0000af72ebe8 QGuiApplicationPrivate::processMouseEvent()
#55 0x0000af730d49 QGuiApplicationPrivate::processWindowSystemEvent()
#56 0x0000af706674 QWindowSystemInterface::sendWindowSystemEvents()
#57 0x0000a810935e <unknown>
#58 0x0000b70943d7 QEventLoop::exec()
#59 0x0000b709cd3e QCoreApplication::exec()
#60 0x0000af7249f1 QGuiApplication::exec()
#61 0x0000b74b4004 QApplication::exec()
  gs: 00000033 fs: 00000000 es: 0000007b ds: 0000007b
 edi: 00000000 esi: 00000008 ebp: bfa8a33c esp: bfa8a320
 ebx: 00000002 edx: 00000000 ecx: bfa8a33c eax: 00000000
 trp: 00000000 err: 00000000 ip: b7ef9d41 cs: 00000073
 efl: 00200246 usp: bfa8a320 ss: 0000007b
[end of stack trace]
Calling _exit(1). Core file will not be generated.
xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/falkon/+filebug/aa556374-c2d0-11e8-b34a-002481e7f48a?'
lubuntu@lubuntu:~$

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: falkon 3.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic i686
ApportVersion: 2.20.10-0ubuntu11
Architecture: i386
CasperVersion: 1.396
CurrentDesktop: LXQt
Date: Fri Sep 28 03:42:49 2018
LiveMediaBuild: Lubuntu 18.10 "Cosmic Cuttlefish" - Beta i386 (20180927)
SourcePackage: falkon
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Chris Guiver (guiverc) wrote :
Chris Guiver (guiverc)
description: updated
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1794917

tags: added: iso-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in falkon (Ubuntu):
status: New → Confirmed
Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

Did you have any problems with:
 * different sites
 * different drivers (i.e. the proprietary ones)
 * different browsers and the same sites (especially qtwebengine ones like qutebrowser)
???

Changed in falkon (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Chris Guiver (guiverc) wrote :

different web sites - yes & no.

I've gone to launchpad.net many times without issue, looked up wiki & google searches too without issue, and actually forgotten about this bug to be honest.

Booted hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, nvidia 7600gt) using 2018-10-03 daily-x86-iso and it was fine going to launchpad.net, google, and many sites.

However I went to youtube, it showed the first screen then locked up. (no reports) then crashed. I tried plus.google.com, freeze then crash back to qterminal.

I installed qutebrowser; -- it started showing the message on attached screenshot; I selected software-rendering it performed equal to Falkon. (fine on sites falkon was good with, but painful where falkon was painful). It spat out TONS of messages to qterminal during its operation ; eventually Seg fault (core dump).

I haven't yet tried the other options - i re-opened qutebrowser hoping to get question again, no it tried to continue & coredump. (doing ubuntu-bug of one of those crashes now; I'll deal with that, try and link it too here & aim to return to see if I can provide more..

I'll [also] explore other proprietary video drivers

notes: installed (& updated) system is no different to when used live. Box now has 3gb of ram.

Revision history for this message
Chris Guiver (guiverc) wrote :

qutebrowser crash is https://bugs.launchpad.net/ubuntu/+source/qutebrowser/+bug/1796034

Revision history for this message
Chris Guiver (guiverc) wrote :

summary : "Force QtWebEngine backend" was just endless loop (see jpeg)

The 1796034 bug states "The information on this page is private"

From that report is --

SegvAnalysis:
 Segfault happened at: 0xb7db24bb <__GI_____strtoul_l_internal+27>: movl $0x0,0x4(%esp)
 PC (0xb7db24bb) ok
 source "$0x0" ok
 destination "0x4(%esp)" (0x8028eff4) in non-writable VMA region: 0x8028e000-0x8028f000 ---p None
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA None
Signal: 11
SourcePackage: qutebrowser

I re-started qutebrowser - it went to plus.google.com okay, until I selected to start a video, then the endless messages start flooding... (the endless flood causes stack exhaustion??) ending in segfault (coredump).

I've been unsuccessful it switching to my other option in qute; will reboot..
-- paste from `journalctl -a`

Oct 04 07:09:28 lubuntu whoopsie[1382]: [07:09:28] Parsing /var/crash/_usr_bin_qutebrowser.999.crash.
Oct 04 07:09:28 lubuntu whoopsie[1382]: [07:09:28] Uploading /var/crash/_usr_bin_qutebrowser.999.crash.
Oct 04 07:09:33 lubuntu whoopsie[1382]: [07:09:33] Sent; server replied with: No error
Oct 04 07:09:33 lubuntu whoopsie[1382]: [07:09:33] Response code: 200
Oct 04 07:09:33 lubuntu whoopsie[1382]: [07:09:33] Reported OOPS ID 71205824-c7a4-11e8-9d5d-fa163e6cac46

lubuntu@lubuntu:/var/lib/whoopsie$ sudo cat whoopsie-id
3852de6a0b397884b88721664e2ad137f8038783f7d5b0ae62cf851f7a4226fd9fcf056168785c3796cb9021c4e79faf9e9e23ad84e48b1f2d077ebad0d41c96

I rebooted, installed qutebrowser, choosing "Force QtWebEngine backend" this time, but it gave me a "Failed to start QtWebKit backend!" error, letting me quit or "Force QtWebEngine backend" before returning me to the screen attached to prior comment. No luck with qutebrowser (but I didn't see a nouveau_pushbuf_kick anywhere)

Revision history for this message
Chris Guiver (guiverc) wrote :

the proprietary drivers I think are a no go, nvidia-driver-304 are unsupported in 18.04 up.

Revision history for this message
Chris Guiver (guiverc) wrote :

just a FYI
booted daily image in dx6120 & all good today (using now default firefox)
(http://iso.qa.ubuntu.com/qatracker/milestones/390/builds/182148/testcases/1303/results)

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for falkon (Ubuntu) because there has been no activity for 60 days.]

Changed in falkon (Ubuntu):
status: Incomplete → Expired
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.