[Bug 1511728] Re: "Meta object revision without matching export" in Qt Creator
This bug is caused by setting `exportMetaObjectRevisions` to `[0,0]` on `Component` blocks that only have one `export` defined. Deleting the comma and the second `0` fixes this. This change needs to be applied on lines 1058, 1067, and 1085 of the following file: `/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes` Once I made those changes, I was able to enter the design page for a new QML app with qmake without encountering a blocking popup block. I am running a fresh install of Ubuntu 15.10 with an amd64 architecture; other architectures may need to replace the `x86_64-linux-gnu` part of the file path with something more system-appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511728 Title: "Meta object revision without matching export" in Qt Creator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1511728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461044] Re: Importing Ubuntu components brings warning
*** This bug is a duplicate of bug 1457528 *** https://bugs.launchpad.net/bugs/1457528 I've also run into this problem. In the Ubuntu SDK, I am unable to access the design page because of a popup box that lists the errors. This should be fixed, and I imagine the fix is generally trivial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461044 Title: Importing Ubuntu components brings warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1461044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1261654] Re: missing LADSPA support
Also, a quick search of the source from github actually shows it searching in "/usr/local/lib/ladspa", set into the path list in "src/effects/ladspa/LoadLadspa.cpp". It would be simple to just set this to the correct path and be done with it. On Mon, May 26, 2014 at 10:21 PM, Adam Nickle wrote: > Would it be terribly difficult to make the search directory configurable? > It seems like sub-par design to hard code the path. In my opinion, the > ideal would be to have a configurable list of search paths. That way, if > the plugins are stored in multiple locations, we can still see them all. Of > course, this fix is more on the Audacity side of things. > > > On Mon, May 26, 2014 at 8:22 PM, Bug Watch Updater < > 1261...@bugs.launchpad.net> wrote: > >> ** Changed in: audacity >>Status: Unknown => New >> >> -- >> You received this bug notification because you are a member of Ubuntu >> Studio, which is subscribed to the bug report. >> https://bugs.launchpad.net/bugs/1261654 >> >> Title: >> missing LADSPA support >> >> Status in Audacity: >> New >> Status in “audacity” package in Ubuntu: >> Confirmed >> >> Bug description: >> The version of audacity in trusty seems to be missing LADSPA support: >> under Effects, I see only 29 plugins listed. Downgrading to version >> 2.0.3-1 (from raring/saucy), I see the expected list of 277 plugins. >> Comparing the configure for raring/saucy and trusty the only >> difference I can see is the following, but >> >> raring/saucy: --with-ffmpeg=system >> >> trusty: --without-ffmpeg >> >> I'd be surprised if that is relevant and added to which, the build log >> shows that ladspa is enabled (?!?) >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/audacity/+bug/1261654/+subscriptions >> > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261654 Title: missing LADSPA support To manage notifications about this bug go to: https://bugs.launchpad.net/audacity/+bug/1261654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1261654] Re: missing LADSPA support
Would it be terribly difficult to make the search directory configurable? It seems like sub-par design to hard code the path. In my opinion, the ideal would be to have a configurable list of search paths. That way, if the plugins are stored in multiple locations, we can still see them all. Of course, this fix is more on the Audacity side of things. On Mon, May 26, 2014 at 8:22 PM, Bug Watch Updater < 1261...@bugs.launchpad.net> wrote: > ** Changed in: audacity >Status: Unknown => New > > -- > You received this bug notification because you are a member of Ubuntu > Studio, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1261654 > > Title: > missing LADSPA support > > Status in Audacity: > New > Status in “audacity” package in Ubuntu: > Confirmed > > Bug description: > The version of audacity in trusty seems to be missing LADSPA support: > under Effects, I see only 29 plugins listed. Downgrading to version > 2.0.3-1 (from raring/saucy), I see the expected list of 277 plugins. > Comparing the configure for raring/saucy and trusty the only > difference I can see is the following, but > > raring/saucy: --with-ffmpeg=system > > trusty: --without-ffmpeg > > I'd be surprised if that is relevant and added to which, the build log > shows that ladspa is enabled (?!?) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/audacity/+bug/1261654/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261654 Title: missing LADSPA support To manage notifications about this bug go to: https://bugs.launchpad.net/audacity/+bug/1261654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 514997] Re: Dell E153Fpf 15" monitor not supported for native resolution
This problem is still present in ubuntu 10.04 LTS updated as of Oct 9, 2010. It can be easily fixed for individual computers following the steps here: http://turbulentsky.com/ubuntu-904-nvidia-driver-screen-resolution- problem.html The monitor remains unsupported/unrecognized, and yes, it would be nice if the monitor could be supported in the future. -- Dell E153Fpf 15" monitor not supported for native resolution https://bugs.launchpad.net/bugs/514997 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
