New answers tagged application-development
To have a sure response at my question i have tryed with my app: 1) I have uploaded to the Ubuntu store the new version of the app 2) I have updated the old version already installed on my Tablet with the new one (using the ubuntu update features of the tablet) Conclusion: the old Database created by the old app version was NOT reused by the new App: a ...
The static libraries are likely there because you have installed one or more of the C development packages - to see exactly which, you can query the package database e.g. $ dpkg -S libm.a libc6-dev-i386: /usr/lib32/libm.a libc6-dev:amd64: /usr/lib/x86_64-linux-gnu/libm.a libc6-dev-armel-cross: /usr/arm-linux-gnueabi/lib/libm.a
The differences might seem subtle in actual usage, but: libappindicator1 is bound via GTK2 libappindicator3-1 is bound via GTK3. There may be deeper stuff that you can look into but that should get you pointed in the right direction. Nothing to do with the version of Python. All the heavy lifting is done through GObject introspection. Oh there does seem ...
Add the following line to your APP-NAME.desktop file: X-Ubuntu-Supported-Orientations=portrait
for Ubuntu 16.04 and newer The Quickly application recommended in the accepted answer is not available in the default Ubuntu 16.04 repositories. An alternative software to Quickly is Illumination Software Creator. Version 6 of this software (the latest version) is released as a Debian package under a GPLv2 license. Illumination Software Creator allows you ...
After long searching in the sources and other topics here on this board: No, Ubuntu is not designed for having simple drag and drop operations between File manager and applications, despite they copied a lot from OSX and others but just not the more important functionality nor implementing such things right.
You need to learn how to package your program (no matter whether it's a script or binary executable) in the .deb format. Then you can sign up to Launchpad and create a PPA (personal package archive) where you can upload the package. Users may then add your PPA to their software sources (sudo add-apt-repository ppa:USERNAME/PPANAME && sudo apt-get ...
Perhaps the most 'Ubuntu' way of seeing the source code for rsync, as well as seeing the Debian packaging and patching material, is to activate the sources by following (under Xenial): Dash > Software & Updates > Ubuntu Software > Source Code Ticking the 'Source Code' box and allowing the repositories to reload. Then run the following single ...
I think it caused by this bug: Cannot assign to non-existent property "tools" The fix has landed in ubuntu-ui-toolkit - 1.3.1984+16.10.20160527.2, it's available for 16.10 Apart from this, I found it works on my 16.04 system by changing the import form: import Ubuntu.Components 1.3 To import Ubuntu.Components 1.2
Top 50 recent answers are included