gsettings-qt problem
Hi,
I have a problem using the gsettings-qt binding:
https://launchpad.net/gsettings-qt
Now I try to use it in my .qml
import QtQuick 2.1
import QtQuick.Controls 1.1
import GSettings 1.0
import QtQuick.Window 2.1
Window {
id:window
GSettings {
id: test
schema.id: org.test.test //I created this schema but it
doesn't work with any
onChanged: changes.push([key, value]);
}
color: test.testcolor
}
Whatever I do it says unable to assign [undefined] to QColor, but if
I try to set the value like from a button test.testcolor = mycolor The
color gets properly set, but reading always returns undefined.
Anyone an idea?
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: chromium no longer maintained
Hi, Jordan, aacually what you describe is not a fork. In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct piece of software. The term often implies not merely a development branch, but a split in the developer community, a form of schism.[1] The base of Chrome is Chromium Chrome = Chromium + other proprietary extensions. Linux Mint is no fork of Ubuntu. It is based on it. Regards, Damian 2012/9/4 Jordon Bedwell jor...@envygeeks.com: On Tue, Sep 4, 2012 at 2:35 AM, Nicolas Michel be.nicolas.mic...@gmail.com wrote: You have wrong. Chromium is and ever was the core of the web browser from Google. And it is open source (there was no before, no after, no fork - it is the core). Google Chrome is that core, plus a certain amout of code which is not open-source and so, you don't have access to the source code of Google Chrome itself (which is a packages chromium + other codes). While I don't completely understand what you are saying I will attempt to refute it. Please do research before stating somebody is wrong: In September 2008, Google released a large portion of Chrome's source code as an open source project called Chromium [2], which Chrome releases are still based on. [1] [1] http://en.wikipedia.org/wiki/Google_Chrome [2] http://arstechnica.com/information-technology/2008/09/google-unveils-chrome-source-code-and-linux-port/ While today Chrome may be be based off of Chromium, originally Chromium was based off of Chrome. Chrome is the original, Chromium is the fork. I am correct as I stated exactly that. So I repeat again, stop spreading lies and use fact and truth please. Thanks and have a great day sir. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: chromium no longer maintained
Hi David, Bad said, Ubuntu is a fork of Debian, it gets forked once in a while after a release to update packages, see wikipedia. Anyway I think chromium is still the most recent, from when 12.04 was released, so may somebody will just need to pick it up for 12.10 I guess 2012/9/4 David Klasinc bigwh...@lubica.net: On 09/04/2012 02:10 PM, Nicolas Michel wrote: In conclusion : Google Chrome is mostly Chromium but not entirely. And one is not the fork of the other because in a fork, the codebase tends to differienciate along the time which is not the case here. One is based on the other, plus some more features. Apart from the licenses, Chrome is to Chromium what Ubuntu is to Debian. But is this discussion really necessary here on this list? Unmaintained package is chromium-browser. That's all that matters. :) Regards, David -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: chromium no longer maintained
-- Forwarded message -- From: Damian Ivanov damianator...@gmail.com Date: 2012/9/4 Subject: Re: chromium no longer maintained To: Gareth McCumskey gare...@nexustech.co.za From wikipedeia: scroll down to history and development, Ubuntu is a forkhttp://en.wikipedia.org/wiki/Fork_(software_development) of the Debian http://en.wikipedia.org/wiki/Debian project's codebasehttp://en.wikipedia.org/wiki/Codebase . 2012/9/4 Gareth McCumskey gare...@nexustech.co.za From Wikipedia: Ubuntu ([image: play] /http://en.wikipedia.org/wiki/Wikipedia:IPA_for_English ʊ http://en.wikipedia.org/wiki/Wikipedia:IPA_for_English#Keyˈhttp://en.wikipedia.org/wiki/Wikipedia:IPA_for_English#Key b http://en.wikipedia.org/wiki/Wikipedia:IPA_for_English#Keyʊhttp://en.wikipedia.org/wiki/Wikipedia:IPA_for_English#Key n http://en.wikipedia.org/wiki/Wikipedia:IPA_for_English#Keythttp://en.wikipedia.org/wiki/Wikipedia:IPA_for_English#Key uː http://en.wikipedia.org/wiki/Wikipedia:IPA_for_English#Key/http://en.wikipedia.org/wiki/Wikipedia:IPA_for_English *u-bun-too*http://en.wikipedia.org/wiki/Wikipedia:Pronunciation_respelling_key )[8] http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#cite_note-7 [9]http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#cite_note-about_ubuntu-8 is a computer operating systemhttp://en.wikipedia.org/wiki/Operating_system * based* on the Debian http://en.wikipedia.org/wiki/Debian Linux distribution http://en.wikipedia.org/wiki/Linux_distribution and distributed. Emphasis my own On Tue, Sep 4, 2012 at 2:26 PM, Damian Ivanov damianator...@gmail.comwrote: Hi David, Bad said, Ubuntu is a fork of Debian, it gets forked once in a while after a release to update packages, see wikipedia. Anyway I think chromium is still the most recent, from when 12.04 was released, so may somebody will just need to pick it up for 12.10 I guess 2012/9/4 David Klasinc bigwh...@lubica.net: On 09/04/2012 02:10 PM, Nicolas Michel wrote: In conclusion : Google Chrome is mostly Chromium but not entirely. And one is not the fork of the other because in a fork, the codebase tends to differienciate along the time which is not the case here. One is based on the other, plus some more features. Apart from the licenses, Chrome is to Chromium what Ubuntu is to Debian. But is this discussion really necessary here on this list? Unmaintained package is chromium-browser. That's all that matters. :) Regards, David -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc Mobile: 071 397 8758 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: chromium no longer maintained
http://www.webupd8.org/2012/09/new-chromium-stable-and-development.html 2012/9/4 Colin Law clan...@googlemail.com: On 4 September 2012 13:26, Damian Ivanov damianator...@gmail.com wrote: Hi David, Bad said, Ubuntu is a fork of Debian, it gets forked once in a while after a release to update packages, see wikipedia. Anyway I think chromium is still the most recent, from when 12.04 was released, so may somebody will just need to pick it up for 12.10 I guess 12.10 currently has chromium-browser 20.0.1132.47 Ubuntu 12.10 (144678) Colin 2012/9/4 David Klasinc bigwh...@lubica.net: On 09/04/2012 02:10 PM, Nicolas Michel wrote: In conclusion : Google Chrome is mostly Chromium but not entirely. And one is not the fork of the other because in a fork, the codebase tends to differienciate along the time which is not the case here. One is based on the other, plus some more features. Apart from the licenses, Chrome is to Chromium what Ubuntu is to Debian. But is this discussion really necessary here on this list? Unmaintained package is chromium-browser. That's all that matters. :) Regards, David -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
ecryptfs default config
Hi folks, I just did an ubuntu 12.04 fresh install and I wanted to test something in ecryptfs. So basically I selected during install to require password to login and to encrypt home folder. I logged in and created secret.txt on my desktop and shut down. I booted up again but in bootloader I appended init=/bin/bash booted into the root shell, did a mount -o remount,rw / and passwd $my_user set a new password and rebooted. After reboot I logged into $my_user account with the new password. secret.txt is readable and all other files too. Is this the expected behaviour?! If yes isn't it better to change the behaviour to something more secure... Regards, Damian -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: ecryptfs default config
Hi John, I appreciate your fast answer! So what can I do to prevent this default behaviour? e.g if password gets changed data is unreadable unless to have the secret key? Wouldn't this be a more reasonable default? Best regards, Damian 2012/9/2 John Moser john.r.mo...@gmail.com: Yes that would indicate that there's a key stored somewhere that doesn't need a known secret, unless pam is storing a key and re-crypting it when you change passwords (unlikely). On 09/02/2012 09:16 AM, Damian Ivanov wrote: Hi folks, I just did an ubuntu 12.04 fresh install and I wanted to test something in ecryptfs. So basically I selected during install to require password to login and to encrypt home folder. I logged in and created secret.txt on my desktop and shut down. I booted up again but in bootloader I appended init=/bin/bash booted into the root shell, did a mount -o remount,rw / and passwd $my_user set a new password and rebooted. After reboot I logged into $my_user account with the new password. secret.txt is readable and all other files too. Is this the expected behaviour?! If yes isn't it better to change the behaviour to something more secure... Regards, Damian -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: ecryptfs default config
I changed it using root account, since like you correctly told init=/bin/bash dropped me directly to root account. 2012/9/2 John Moser john.r.mo...@gmail.com: did you change your password from your account or using the root account? It looks like pam actually stores encryption keys in /var/lib/ somewhere and can re-cypher them. That only works if you enter the previous password when changing passwords, though (which I hadn't considered, since normally when you init=/bin/bash you drop straight to root...) On 09/02/2012 09:37 AM, Damian Ivanov wrote: Hi John, I appreciate your fast answer! So what can I do to prevent this default behaviour? e.g if password gets changed data is unreadable unless to have the secret key? Wouldn't this be a more reasonable default? Best regards, Damian 2012/9/2 John Moser john.r.mo...@gmail.com: Yes that would indicate that there's a key stored somewhere that doesn't need a known secret, unless pam is storing a key and re-crypting it when you change passwords (unlikely). On 09/02/2012 09:16 AM, Damian Ivanov wrote: Hi folks, I just did an ubuntu 12.04 fresh install and I wanted to test something in ecryptfs. So basically I selected during install to require password to login and to encrypt home folder. I logged in and created secret.txt on my desktop and shut down. I booted up again but in bootloader I appended init=/bin/bash booted into the root shell, did a mount -o remount,rw / and passwd $my_user set a new password and rebooted. After reboot I logged into $my_user account with the new password. secret.txt is readable and all other files too. Is this the expected behaviour?! If yes isn't it better to change the behaviour to something more secure... Regards, Damian -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
