| Summary: | nvidiafb and Falkon => content of window is all black | ||
|---|---|---|---|
| Product: | [Applications] Falkon | Reporter: | LI AR <sexxxenator> |
| Component: | general | Assignee: | David Rosca <nowrep> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | estellnb |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Content is all black but site is correclty loaded with nvidiafb | ||
Can you please try with either "falkon --disable-gpu" or "LIBGL_ALWAYS_SOFTWARE=true falkon" Hi, Thanks for your quick answer. Both did the trick! Thanks a lot, Falkon is so light&fast, I'm so happy to be able to use it again !!! Yes, if I use --disable-gpu the SharedMemoryAlloc errors go away in deed. However the web page is still not viewed: I get a light gray background and the button images are void. I have tried it with different web pages:
> falkon --disable-gpu
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-elm'
Falkon: 1 extensions loaded
QObject::connect: invalid null parameter
[1145:1159:1216/183849.796781:ERROR:cert_verify_proc_nss.cc(944)] CERT_PKIXVerifyCert for www.elstel.org failed err=-8179
QSqlDatabasePrivate::addDatabase: duplicate connection name 'Falkon/94151366637344', old connection removed.
QObject::connect: invalid null parameter
|
Created attachment 115125 [details] Content is all black but site is correclty loaded with nvidiafb Hi, Since the "nouveau" drivers crashed my machine on a regular basis, I switched to nvidiafb (FYI it's an old - ~15 years -, but perfectly functional desktop, with a "GeForce 7600 GS" video card)). With this change, it's working perfectly, apart for Falkon: whatever site I go to, the content of Falkon's window - the webpage content part - is always all black - the menus and bars are OK. If I use the mouse in the page, I can copy-paste text, so I know Falkon is actually loading the pages correctly, it's just a display bug...