openSUSE KDE June 2010

kde@lists.opensuse.org

41 participants
48 discussions

[opensuse-kde] Networkmanager-DBus Error

by Uwe der Linuxsusefan

Hi Guys, Concerns: KDE4-Factory → openSUSE 11.2 + Networkmanager-kde4 Packages With the update from 19.June of the network manager denied the collaboration with dbus! Error message: " .... kde4-network manager can not be registered, please communicate to your system administrator .... ........ network manager can not be started on dbus .... etc ..." something like this is the message! Only one downgrade the packages from: → NetworkManager-kde4-0.9.svn1128615-138.2 (KDE4-Factory-Depot) to: → NetworkManager-kde4-0.9.svn1128615-2.2 (home:/dirkmueller:/KDE444) Eliminated the above mentioned errors. could someone please look at the correct times and accurate? PS:Would like to thank you and times for the super work, it does great work, keep it up ... thanks! :) Sorry for my very very bad english, I am a German and my English is learned already some decades ago ;) Grüße aus dem Schwabenland, Uwe der Linuxsusefan Die SuSE sei mit euch, wo immer ihr seid .....

11 years, 11 months

[opensuse-kde] Re: [opensuse-kernel] Remote logging Kernel on a laptop

by Johannes Obermayr

On Monday 14 June 2010 07:41:26 you wrote: > On 06/13/2010 05:30 PM, Johannes Obermayr wrote: > > Hi, > > > > Because Kernel 2.6.34 crashes on my laptop while booting I want to do remote logging the boot process until the system crashes. > > > > Available ports: > > > > Crashing system (laptop with openSUSE): > > - USB > > - LPT > > - Bootloader: GRUB > > > > Remote systems (desktops with openSUSE): > > - USB > > - LPT > > - Serial > > > > Available cable: > > - USB/Serial (also possible connecting an adaptor Serial to LPT) > > > > > > Can you please say to me how I have to connect the cable (which port/plug to use on which system) and which commands I have to use on each system. > > (I know that the USB plug doesn't fit to the LPT port ;-) ) > > How far along in the boot process is it crashing? It may be that kdump > is your best bet. > Because I haven't received an useful hint I can only provide an image: http://img256.imageshack.us/img256/3038/dscn7736.jpg Johannes -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

[opensuse-kde] Re: [Kde-pim] migrating from KMail1 to KMail2 (and back?)

by Sebastian Kügler

On Thursday 17 June 2010 15:41:00 Kevin Krammer wrote: > On Thursday, 2010-06-17, Sebastian Kügler wrote: [...] > > Sounds perfectly robust, as no user intervention is needed. Cool :-) > > Right. > Some index data cannot be recovered, however. Things like special flags > (e.g. important), tags and such. Wonderful, thanks for all the answers! -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

[opensuse-kde] Re: [Kde-pim] migrating from KMail1 to KMail2 (and back?)

by Sebastian Kügler

Hi, [readding opensuse-kde list in CC:] On Thursday 17 June 2010 13:52:29 Kevin Krammer wrote: > On Thursday, 2010-06-17, Sebastian Kügler wrote: > > On Thursday 17 June 2010 13:22:39 Kevin Krammer wrote: > > > On Thursday, 2010-06-17, Sebastian Kügler wrote: > > > > - Is the migration process destructive, so after migration, the > > > > KMail1 config + cached data is gone? > > > > > > The migration process itself is only destructive on the user's choice. > > > I.e. when migrating disconnected IMAP accouts, users are presented with > > > the option to either keep the old cache or deleting it after import. > > > > Alright, I understood that (roughly) from your other emails on this > > subject. What is the default here? > > This is a question message box with two options, delete old cache being > the active/default button, ESC triggering "keep". > I could add another config option to not ask but always keep though. Is this per folder? (I have 60 folders, and I'm sure some of the audience here has even more. That might result in an exercise in RSI if I have to check something for every migrated folder (and I can't make up valid enough use- cases where you'd want to keep parts of your cache only). The thing that most users want is probably "keep old data around for some time until I know kmail2 works for me". That's essentially "keep old data", but with an option to clean up later. Not sure how to implement that cleanly (maybe as something that runs when we ship 12.0, though.) That's something we can flip in our shipped packages, so you guys don't worry too much about this at this point. :) > > > However, after migration, i.e. when using the new setup, certain > > > portions of the old KMail setup (metadata) might become invalid due to > > > folders being modified and thus making the KMail index files "too > > > old". > > > > Is this reported by KMail then, or what will happen? > > AFAIK, KMail will check the timestamp before it attemps loading. If the > index is to old it is ignored and rebuilt. Sounds perfectly robust, as no user intervention is needed. Cool :-) Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

[opensuse-kde] Re: [Kde-pim] migrating from KMail1 to KMail2 (and back?)

by Sebastian Kügler

Hi Kevin, On Thursday 17 June 2010 13:22:39 Kevin Krammer wrote: > On Thursday, 2010-06-17, Sebastian Kügler wrote: > > As you can see, we're a bit fuzzy on what will actually work in the > > migration process: > > > > - Are the two configs + data completely independant? > > - Can KMail1's config be kept, so users who try 2, and want to go back to > > 1 can do that easily? > > The config is copied on first migration attempt. It can be repeated in full > by deleting the newly created config (and kmail-migratorrc which stores > the migration state). > > So, config wise, this is not a problem. Awesome, nice work! > > - Is the migration process destructive, so after migration, the KMail1 > > config + cached data is gone? > > The migration process itself is only destructive on the user's choice. > I.e. when migrating disconnected IMAP accouts, users are presented with the > option to either keep the old cache or deleting it after import. Alright, I understood that (roughly) from your other emails on this subject. What is the default here? > However, after migration, i.e. when using the new setup, certain portions > of the old KMail setup (metadata) might become invalid due to folders > being modified and thus making the KMail index files "too old". Is this reported by KMail then, or what will happen? > > - If so, which would be the files to backup, so we can communicate that > > to our users (this is documented somewhere, right? :))? > > Userbase might have pages related to backup of mail setups. I'll have a look, but looks like this is less relevant, since -- in theory -- there's no need to backup, as you don't destroy current setups. > I actually wrote a blog entry about testing migration which contains > information about involved files, etc. but kdedevelopers.org doesn't let me > login, so I could publish it yet. OK, I'm on the lookout. :) Thanks for the quick turnaround time. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

[opensuse-kde] migrating from KMail1 to KMail2 (and back?)

by Sebastian Kügler

Hi PIMsters, In the openSUSE team, we're currently planning the migration of our users from KMail1 to KMail2. The idea is to offer both options for some time and give the user the opportunity to switch when it fits her. You can read more details in this email: http://lists.opensuse.org/opensuse-kde/2010-06/msg00066.html With this strategy, we hope to make users' lives easier by giving some transition time, and to make testing of the new Akonadi-based PIM easier by providing packages people can grind their teeth on. We intend to fully go with an Akonadi-based PIM for openSUSE 12.0, in early spring next year. I've seen that a lot of work is going into the migration of the users config + data, and I think that's great. The best marketing for the new PIM is users that had a smooth transition and talk about it. As you can see, we're a bit fuzzy on what will actually work in the migration process: - Are the two configs + data completely independant? - Can KMail1's config be kept, so users who try 2, and want to go back to 1 can do that easily? - Is the migration process destructive, so after migration, the KMail1 config + cached data is gone? - If so, which would be the files to backup, so we can communicate that to our users (this is documented somewhere, right? :))? Really looking forward to my Akonadi-based PIM, btw. Keep up the good work. :) Thanks for your insights, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

[opensuse-kde] K3b 2.0 RC3 released

by Markus

Hi there. I'd like to inform you that K3b received a new bugfix release: http://sourceforge.net/projects/k3b/files/ Changelog: * In some cases medium doesn't get accepted for multisession burning (230742) * Data files in VCD ripping view are not listed * Show "Modify Permissions" button in System Problem Dialog only when it makes sense (230706) * Crash after "Cancel" was clicked while adding audio files to AudioCD project (231348) * Error window at the start when a place on the left pane is not accessible (230194) * Incorrect minimum size of welcome widget (231939) * Hangs while ripping AudioCD with data tracks (231174) * Crash when auto-removing non-existing files from a project before the burning (236005) * Empty Blu-ray medium not detected properly (236069) * eMovix project cannot be burned (236823) * M3U playlist not read properly (237654) * K3b overwrites iso ignoring user choice on dvd copy with option "only create image" checked (185251) * Compilation fails with FFmpeg version SVN-r23001 (236036) * Crash when waiting for reload the medium -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

[opensuse-kde] RFC: KMail Akonadi migration in openSUSE

by Sebastian Kügler

Hi all, A couple of people (wstephenson, tittiatcoke, llunak, dirk, alin, krop and me were present) talked about how we could make the Akonadi migration of the PIM components smooth and pleasant for our valued users. We came up with the following plan: - In 11.3, we (obviously) ship KMail from 4.4, address book is akonadi-based, the rest isn't (that's what 4.4 upstream ships). - Users upgrading to KDE SC 4.5.1 (which contains supposedly the first Akonadi-based KMail) automatically keep 4.5.0's KDEPIM, so no Akonadi-based email. - Users that want to try KMail2 (*0) can install that, it'll replace KMail1 as package and migrate the data in so far that's possible (a migration tool is part of upstream PIM, so it should work at least for the upgrade). - In 12.0, which will be based on KDE SC 4.6.x, we'll ship Akonadi-based PIM from 4.6 by default (so we re-align with upstream). This proposal gives users a window of roughly 8 months in which they can decide to migrate to Akonadi, and those that just follow the stable releases and don't follow KDE's upstream releases will get migrated with 12.0. By 12.0, we'll also be able to ship some components that make use of the new Akonadi features, so we can make clear that the pain of the migration is worthwhile -- you're migrating to an already matured KMail2, and get some nice PIM integration, for example in Plasma (*1), on top of that. *0: needs checking if KMail1's config can be kept while upgrading, so it's possible to switch back and forth between the two, I'll check with the upstream PIMsters if that will work *1: I have some stuff up in my sleeve :-) Please comment on this if you think it's a good idea to go forward with this plan, or if you have better ideas. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

[opensuse-kde] openSUSE KDE meeting 20100610

by Sebastian Kügler

Ladies and Gents, Today's KDE Meeting minutes are to be found at: http://en.opensuse.org/KDE/Meetings/20100610 Those are my first minutes for this kind of meeting, so please be kind if I made any mistakes (but do tell me). Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

[opensuse-kde] KDE SC 4.5 Beta 2 on openSUSE 11.2

by Andi Sugandi

Hello list-mates, Can anyone confirm that KDE SC 4.5 Beta 2 is more responsive (of course more bug-fixes) than earlier versions, at least from Beta1? I'm using it on openSUSE 11.2 (ASUS EEEPC 1201T, with fglrx for its display driver), and can see it is more stable and more responsive than earlier. CMIIW. How to measure this so it can be good thing in marketing area for KDE and openSUSE? Best regards, -- Andi Sugandi. Bandung, Indonesia. openSUSE-id Team, openSUSE Community Member. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

11 years, 11 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE KDE June 2010