Re: [KDE 4.2 snapshots] Unpacking kde-icons-oxygen conflicts with koffice-data
Le samedi 20 décembre 2008 11:47:48 Ana Guerrero, vous avez écrit : > On Fri, Dec 19, 2008 at 11:13:41PM +0100, Xavier Brochard wrote: > > Le vendredi 19 décembre 2008 19:41:04 Ana Guerrero, vous avez écrit : > > > > Preparing to replace kde-icons-oxygen 4:4.1.3-1 (using > > > > .../kde-icons-oxygen_4%3a4.1.85+svn898692-0r1_all.deb) ... > > > > `/usr/share/icons/oxygen/16x16/actions/object-order-front.png', which > > > > is also in package koffice-data > > > > koffice-data is at version 1:1.9.98.3-2, and I'm on an amd64 system. > > > > > > Thansk for reporting, I am aware of this issue, but package is made for > > > experimental for KDE 4.1 in experimental where those icons are not > > > provided. > > > > yes, I'm sure they are > > I'm also on sid/experimental, AMD64 system, and I've got the same error > > (and others ;-) > > If I remember right, the problem comes with the last koffice beta. > > I am not sure I do follow you. If there is any remaining problem with > koffice beta4 (check you have the version -2) and kde from experimental > (4.1.3), you should file a bug please. If you are talking about -1 those > are resolved. I know I should have fill a bug Ana. But I have 2 very young babies and it's sometimes hard to do what I wanted to. I lost my notes about this bug, sorry. It was a conflict between koffice and kde-icons-oxygen, starting with /usr/share/icons/oxygen/16x16/actions/format-text-italic.png there was about 5 or 10 more files icons (may be the ones you have removed in -2). I resolved it by hand (dpkg --force-overwrite), and dpkg log doesn't contain such errors. -- Xavier xav...@alternatif.org 09 54 06 16 26 -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
kde 4.2 beta showstoppers?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm willing to give the 4.2 beta packages a try - as long as my fundamental application is still working (kmail). What are the experiences? Does kmail run without problems and what is the state of akonadi? Is it save to use? Thanks, Andy - -- BOFH excuse #390: Increased sunspot activity. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAklPb+oACgkQRrny/uOBVy6INACeM7k6KP3EFIa7NJhemQyxF35o IycAoIy3D8FfgHtl5eIcRwL4JYjVFlzD =Xega -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [KDE 4.2 snapshots] Unpacking kde-icons-oxygen conflicts with koffice-data
Hello, pirmadienis 22 Gruodis 2008, Xavier Brochard rašė: > I know I should have fill a bug Ana. ??? You should know that it only affects KDE 4.2. Filling bugs, huh? -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Re: kde 4.2 beta showstoppers?
Hello > I'm willing to give the 4.2 beta packages a try - as long as my fundamental > application is still working (kmail). > What are the experiences? Does kmail run without problems and what is the > state of akonadi? Is it save to use? KMail is rock solid here (with pop accounts), and with a lovely new folder view. It still doesn't use akonadi for email storage. Only apps using akonadi are kabc and korganiser, data is migrated automaticaly on first start (keeping the old format as a backup). As for me kdepim4.2 is ok. Regards -- Xavier Vello signature.asc Description: This is a digitally signed message part.
Re: [KDE 4.2 snapshots] Unpacking kde-icons-oxygen conflicts with koffice-data
Le lundi 22 décembre 2008 12:03:36 Modestas Vainius, vous avez écrit : > Hello, > > pirmadienis 22 Gruodis 2008, Xavier Brochard rašė: > > I know I should have fill a bug Ana. > > ??? You should know that it only affects KDE 4.2. Filling bugs, huh? I though we were talking about 4.1.3 and Koffice 1:1.9.98.3-1 this discussion is very confusing! ;-) -- Xavier xav...@alternatif.org 09 54 06 16 26 -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [KDE 4.2 snapshots] Unpacking kde-icons-oxygen conflicts with koffice-data
Hello, pirmadienis 22 Gruodis 2008, Xavier Brochard rašė: > I though we were talking about 4.1.3 and Koffice 1:1.9.98.3-1 > this discussion is very confusing! ;-) It would not have been confusing if you actually read the subject. What's the point to talk about non up-to-date koffice version anyway. -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Re: kde 4.2 beta showstoppers?
On Monday 22 December 2008, Xavier Vello wrote: > Hello > > > I'm willing to give the 4.2 beta packages a try - as long as my > > fundamental application is still working (kmail). > > What are the experiences? Does kmail run without problems and what is the > > state of akonadi? Is it save to use? > > KMail is rock solid here (with pop accounts), and with a lovely new folder > view. It still doesn't use akonadi for email storage. > Only apps using akonadi are kabc and korganiser, data is migrated > automaticaly on first start (keeping the old format as a backup). There have been some issues with the Akonadi compatibility plugins, e.g. a freeze like situation when adding an email address as a new contact into the addressbook (hopefully fixed that one yesterday). Obviously we appreciate any form of testing in that area since so much depends on the actual setup used and users usage patterns. However, if one rather wants to beta test other areas of KDE, resource automigration can be disabled [1] And just to avoid misunderstandings: the change is how the data is accessed by applications, not how it is stored on disk. A vcard file will still remain a vcard file even if used by a native Akonadi storage agent (called Akoandi VCard Resource) Cheers, Kevin [1] http://techbase.kde.org/Projects/PIM/Akonadi#How_do_I_disable_automatic_migration_from_KDE.27s_traditional_framework.3F signature.asc Description: This is a digitally signed message part.
Re: Small issues with powerdevil
Hello, pirmadienis 22 Gruodis 2008, Christian Surlykke rašė: > - Even though I have configured it to do so, powerdevil doesn't suspend my > laptop (dell inspiron 1525) to ram when closing the lid. It shows a > notification that it is going to suspend, so the 'lid closed' event is > recognized, but the suspend never happens. # Does s2ram work when you run it from console? If not, that might be a reason for powerdevil (hal?) failing to suspend to ram. > - I have configured that pressing the power button, should bring up the > logout dialog, but what happens is an imediate shutdown. Debian specific, edit /etc/acpi/events/powerbtn and disable event. -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
FW: Re: kde 4.2 beta showstoppers?
Hi,
...ok - I've been brave this afternoon, but seems like I got bad luck :(
During dist-upgrade I got the already mentioned conflicting icon files for
koffice (I'm using sid with some experimental packages like kde-4.1...). Anyway
- that was not the problem.
After installation finished, I restarted my laptop and logged into kde 4.2.
First thing I noticed - my complete settings were gone (might be due to 4.2
using ~/.kde whereas 4.1 is using ~/.kde4 ??). So I decided to copy the
configuration files from my ~/.kde4 to the ~/.kde directory. Panel settings
didn't reappear and most of my mail setup is gone. The bad thing about it - I
cannot reconfigure kmail for my account settings (I'm usually using ~ 5
different accounts). But whenever I create a new account and press "save",
nothing happens. The only joice I have is to press "cancel" which reproducable
crashes kmail ("*** KMail got signal 6").
So currently I'm using a web-mailer to write to the list ;-) I know, that this
is not the place for reporting bugs for 4.2, but any hint on re-activating
kmail would be great (as I mentioned before - this is the most important
application for me ;-)).
Besides that - I still have a lot of problems customizing 4.2 (widgets are not
added to panels, ...) but that's currently not too important for me.
Thanks for any help,
regards,
andy
>On Monday 22 December 2008, Xavier Vello wrote:
>> Hello
>>
>> > I'm willing to give the 4.2 beta packages a try - as long as my
>> > fundamental application is still working (kmail).
>> > What are the experiences? Does kmail run without problems and what is the
>> > state of akonadi? Is it save to use?
>>
>> KMail is rock solid here (with pop accounts), and with a lovely new folder
>> view. It still doesn't use akonadi for email storage.
>> Only apps using akonadi are kabc and korganiser, data is migrated
>> automaticaly on first start (keeping the old format as a backup).
>
>There have been some issues with the Akonadi compatibility plugins, e.g. a
>freeze like situation when adding an email address as a new contact into the
>addressbook (hopefully fixed that one yesterday).
>
>Obviously we appreciate any form of testing in that area since so much depends
>
>on the actual setup used and users usage patterns.
>However, if one rather wants to beta test other areas of KDE, resource
>automigration can be disabled [1]
>
>And just to avoid misunderstandings: the change is how the data is accessed by
>
>applications, not how it is stored on disk.
>A vcard file will still remain a vcard file even if used by a native Akonadi
>storage agent (called Akoandi VCard Resource)
>
>Cheers,
>Kevin
>
>[1]
>http://techbase.kde.org/Projects/PIM/Akonadi#How_do_I_disable_automatic_migrati
>on_from_KDE.27s_traditional_framework.3F
signature.asc
Description: PGP signature
Re: FW: Re: kde 4.2 beta showstoppers?
Hello,
pirmadienis 22 Gruodis 2008, a...@bourges.de rašė:
> After installation finished, I restarted my laptop and logged into kde 4.2.
> First thing I noticed - my complete settings were gone (might be due to 4.2
> using ~/.kde whereas 4.1 is using ~/.kde4 ??).
No, KDE 4.2 is using ~/.kde4
> So I decided to copy the
> configuration files from my ~/.kde4 to the ~/.kde directory. Panel settings
> didn't reappear and most of my mail setup is gone. The bad thing about it -
> I cannot reconfigure kmail for my account settings (I'm usually using ~ 5
> different accounts). But whenever I create a new account and press "save",
> nothing happens. The only joice I have is to press "cancel" which
> reproducable crashes kmail ("*** KMail got signal 6").
Start with a clean ~/.kde4 and copy config files which you need from the old
.kde4.
> So currently I'm using a web-mailer to write to the list ;-) I know, that
> this is not the place for reporting bugs for 4.2, but any hint on
> re-activating kmail would be great (as I mentioned before - this is the
> most important application for me ;-)).
If you start with a clean ~/.kde4, you should be able to reconfigure kmail
redoing your settings. Importing mails might more demanding and complicated
task (check ~/Mail or ~/.kde4/share/apps/kmail/).
> Besides that - I still have a lot of problems customizing 4.2 (widgets are
> not added to panels, ...) but that's currently not too important for me.
Again, something is badly screwed in your config. The easiest way is to start
fresh. However, if you still face similar problems with fresh ~/.kde4, check
your installation.
--
Modestas Vainius
signature.asc
Description: This is a digitally signed message part.
Re: Small issues with powerdevil
Monday 22 December 2008 skrev Modestas Vainius: > Hello, > > pirmadienis 22 Gruodis 2008, Christian Surlykke rašė: > > - Even though I have configured it to do so, powerdevil doesn't suspend > > my laptop (dell inspiron 1525) to ram when closing the lid. It shows a > > notification that it is going to suspend, so the 'lid closed' event is > > recognized, but the suspend never happens. > > # Does s2ram work when you run it from console? If not, that might be a > reason for powerdevil (hal?) failing to suspend to ram. Hmm. It needs the '-f' switch. However, If I clik the sleep button on the battery monitor widget, it suspends allright. And it worked in kpowersave. > > > - I have configured that pressing the power button, should bring up the > > logout dialog, but what happens is an imediate shutdown. > > Debian specific, edit /etc/acpi/events/powerbtn and disable event. Thanks. That fixed the powerbutton issue. br. Chr.
