Skip to content

Ubuntu Rendering Issue When There is a Long View or Trigger #1001

Closed

Description

@christopherthompson81

Ubuntu Rendering Issue When There is a Long View or Trigger

There is a rendering issue on the 'Database Structure' tab when using DB Browser for SQLite under Ubuntu when there is a long view or trigger. I suspect there is some problem with limitless horizontal scrolling.

See attached screen-shot:

dbfs_rendering_bug

Useful extra information

I'm opening this issue because:

  • DB4S is crashing
  • DB4S has a bug
  • DB4S needs a feature
  • DB4S has another problem

I'm using DB4S on:

  • Windows: ( version: ___ )
  • Linux: ( _distro:Ubuntu 16.04 )
  • Mac OS: ( version: ___ )
  • Other: ___

I'm using DB4S version:

  • 3.9.1
  • 3.9.0
  • Other: 3.9.99

I have also:

Activity

  1. justinclift commented on May 1, 2017

    @justinclift
    Member

    Oh, that's interesting. Is the data set which you're using to trigger that, a public one?

    Just thinking that might be helpful for debugging. 😄

  2. christopherthompson81 commented on May 1, 2017

    @christopherthompson81
    Author
  3. justinclift commented on May 1, 2017

    @justinclift
    Member

    Yep, definitely interested, that would really help. 😄

  4. MKleusberg commented on May 8, 2017

    @MKleusberg
    Member

    I've just prepared a test database containing two long lorem ipsum views. xx is one long line, yy are many lines. Not sure if they are long enough though. For both views it's struggling (xx prints one long empty line as a tooltip, yy fills the entire screen with its tooltip) but I never get the weird output from your screenshot.

    @justinclift Do you still have an Ubuntu VM somewhere to test this? I've only tryed this on KDE. My test db is here.

  5. justinclift commented on May 9, 2017

    @justinclift
    Member

    @yep, I can test this. My Ubuntu VM is really Kubuntu, but it's pretty easy to download standard Ubuntu 16.04.2 and whip up a new one. I'll add this to my task list for this week.

  6. justinclift commented on May 9, 2017

    @justinclift
    Member

    Aha, I knew this sounded familiar. Pretty sure this bug is another occurance of #920, and the solution is to compile it against a newer Qt library.

    That being said, I'm trying to compile DB4S on Ubuntu 16.04.2 right now, and it's failing due to a different (known) problem. Looking into solutions for that next... 😄

  7. justinclift commented on May 9, 2017

    @justinclift
    Member

    @MKleusberg As a data point, just tried your test database on an Ubuntu 16.04.2 VM here, compiling using Qt 5.6 (from a 3rd party PPA).

    No rendering issue like the above showed up, but the "Database Structure" tab took ages (~9.5 seconds) to show up. Switching from "Database Structure" to any of the other tabs was instant. From them back to "Database Structure"... wait 9.5 seconds again. Every time.

    So, something not quite right there. Possibly just something weird with the VM, VMware Fusion, or whatever else too. I'll muck around with a few settings next and see if that fixes the problem.

  8. justinclift commented on May 9, 2017

    @justinclift
    Member

    Well, it's not caused by VMware Fusion's implementation of "Graphics Acceleration" for Linux. Same problem both ways.

  9. justinclift commented on May 9, 2017

    @justinclift
    Member

    Tried it with a fresh build with Qt 5.5 (using the initial compatiblity patch) instead. Same behaviour with that database.

    Using a different database (eg this), DB4S has no delay. The "Database Structure" tab shows immediately when switching at all times.

  10. justinclift commented on May 9, 2017

    @justinclift
    Member

    Ahh, this is interesting. I just installed Qt 5.8 from the official Qt download site (qt.io). When DB4S is compiled using that, the slowness issue isn't present.

    Looks like whatever the problem is, it's been fixed in Qt sometime after Qt 5.6.1.

  11. justinclift commented on May 9, 2017

    @justinclift
    Member

    Qt 5.7 doesn't have the problem either.

    It really looks like both Qt 5.5 and 5.6 on Ubuntu aren't fantastic for DB4S. For anyone having weird slowness or screen corruption issues, it'll need to be compiling using Qt 5.7 or above instead.

  12. MKleusberg commented on May 12, 2017

    @MKleusberg
    Member

    Should we add a warning to the build instructions then that we discourage using Qt < 5.7 even though it compiles just fine? Doesn't seem like we can do much else about it.

  13. justinclift commented on May 12, 2017

    @justinclift
    Member

    Yep. If you want to do it, then go for it. Otherwise I'll get it done later on today. 😄

  14. MKleusberg commented on May 12, 2017

    @MKleusberg
    Member

    @justinclift Done 😃

  15. justinclift commented on Feb 16, 2018

    @justinclift
    Member

    @christopherthompson81 Did you ever get around to trying a build created with a newer version of Qt? eg something that shouldn't have this rendering problem

  16. karim commented on Aug 2, 2018

    @karim
    Member

    Closing this due to lack of response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions