On Wednesday 12 August 2009 18:09:25 Hans Ecke wrote:
Yes, entirely seamless. Great job Rex & Co!
+1
Anne
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Neal Becker wrote:
Oh, except 1 problem so far. kmail crashes (repeatably) when
connection is
lost.
What account types/servers? Also, do you have auto-checking enabled? Comcast drops reliably, but unpredictably and all I get are error dialogs.
- --Ben
On Wednesday 12 August 2009, Ben Boeckel wrote:
Neal Becker wrote:
Oh, except 1 problem so far. kmail crashes (repeatably) when
connection is
lost.
What account types/servers? Also, do you have auto-checking enabled? Comcast drops reliably, but unpredictably and all I get are error dialogs.
Mail is d/l automatically with dimap. 2 times since updating to 4.3 kmail was crashed, and both times I saw the router had crapped out - so I'm guessing this is not coincidence.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Neal Becker wrote:
On Wednesday 12 August 2009, Ben Boeckel wrote:
Neal Becker wrote:
Oh, except 1 problem so far. kmail crashes (repeatably)
when
connection is
lost.
What account types/servers? Also, do you have auto-checking enabled? Comcast drops reliably, but unpredictably and all I
get
are error dialogs.
Mail is d/l automatically with dimap. 2 times since updating
to 4.3 kmail was
crashed, and both times I saw the router had crapped out - so
I'm guessing
this is not coincidence.
I have 5 dimap accounts here, though I think only one is auto- updating (gmail account is too high traffic to check every so often and the others are too low traffic to bother).
- --Ben
On Wednesday 12 August 2009 21:44:58 Neal Becker wrote:
On Wednesday 12 August 2009, Ben Boeckel wrote:
Neal Becker wrote:
Oh, except 1 problem so far. kmail crashes (repeatably) when
connection is
lost.
What account types/servers? Also, do you have auto-checking enabled? Comcast drops reliably, but unpredictably and all I get are error dialogs.
Mail is d/l automatically with dimap. 2 times since updating to 4.3 kmail was crashed, and both times I saw the router had crapped out - so I'm guessing this is not coincidence.
I use plain imap, and have seen the same. If I use a cabled network connection all is fine, but on wireless the signal gets lost occasionally and I have to restart KMail. It's not a freeze - I can close it and restart - but it stops working. I can't fetch and read any message.
Anne
On Thursday 13 August 2009, Anne Wilson wrote:
On Wednesday 12 August 2009 21:44:58 Neal Becker wrote:
On Wednesday 12 August 2009, Ben Boeckel wrote:
Neal Becker wrote:
Oh, except 1 problem so far. kmail crashes (repeatably) when
connection is
lost.
What account types/servers? Also, do you have auto-checking enabled? Comcast drops reliably, but unpredictably and all I get are error dialogs.
Mail is d/l automatically with dimap. 2 times since updating to 4.3 kmail was crashed, and both times I saw the router had crapped out - so I'm guessing this is not coincidence.
I use plain imap, and have seen the same. If I use a cabled network connection all is fine, but on wireless the signal gets lost occasionally and I have to restart KMail. It's not a freeze - I can close it and restart - but it stops working. I can't fetch and read any message.
Anne
kmail did not stop working - it segfaulted. x86_64 if that matters.
2009/8/13 Neal Becker ndbecker2@gmail.com:
kmail did not stop working - it segfaulted. x86_64 if that matters.
You could install the debug packages and file a bugreport upstream. I guess it's reproducable.
I use plain imap, pop3 and filters. kmail crashes 10-20 time per day :( After last upgrade to kdepim-4.3.0-2.fc11.x86_64 I can't find proper debuginfo packages for making good bug reports...
On Thursday 13 August 2009 00:05:52 Ben Boeckel wrote:
Neal Becker wrote:
Oh, except 1 problem so far. kmail crashes (repeatably) when
connection is
lost.
What account types/servers? Also, do you have auto-checking enabled? Comcast drops reliably, but unpredictably and all I get are error dialogs.
--Ben
On Thursday 13 August 2009 10:31:12 Nikita Bige wrote:
I use plain imap, pop3 and filters. kmail crashes 10-20 time per day :( After last upgrade to kdepim-4.3.0-2.fc11.x86_64 I can't find proper debuginfo packages for making good bug reports...
My guess would be kdepim-debuginfo ;-) Isn't that there for x86_64?
Anne
Anne Wilson wrote:
On Thursday 13 August 2009 10:31:12 Nikita Bige wrote:
I use plain imap, pop3 and filters. kmail crashes 10-20 time per day :( After last upgrade to kdepim-4.3.0-2.fc11.x86_64 I can't find proper debuginfo packages for making good bug reports...
My guess would be kdepim-debuginfo ;-) Isn't that there for x86_64?
I'm starting to sync latest packages in upates-testing to kde-testing, but without debuginfo. Ie, if you want debuginfo, you need to get them from updates-testing.
-- Rex
On Thu, 2009-08-13 at 06:36 -0500, Rex Dieter wrote:
Anne Wilson wrote:
On Thursday 13 August 2009 10:31:12 Nikita Bige wrote:
I use plain imap, pop3 and filters. kmail crashes 10-20 time per day :( After last upgrade to kdepim-4.3.0-2.fc11.x86_64 I can't find proper debuginfo packages for making good bug reports...
My guess would be kdepim-debuginfo ;-) Isn't that there for x86_64?
I'm starting to sync latest packages in upates-testing to kde-testing, but without debuginfo. Ie, if you want debuginfo, you need to get them from updates-testing.
Er, that confuses me. I was under the impression that it went like this:
kde-testing -> updates-testing -> updates
Is that wrong?
poc
Patrick O'Callaghan wrote:
Er, that confuses me. I was under the impression that it went like this:
kde-testing -> updates-testing -> updates
Is that wrong?
Rex syncs the KDE stuff from updates-testing to kde-testing for those who don't want to update to all of updates-testing.
Kevin Kofler
On Thu, 2009-08-13 at 16:33 +0200, Kevin Kofler wrote:
Patrick O'Callaghan wrote:
Er, that confuses me. I was under the impression that it went like this:
kde-testing -> updates-testing -> updates
Is that wrong?
Rex syncs the KDE stuff from updates-testing to kde-testing for those who don't want to update to all of updates-testing.
So it's really the other way round, i.e. updates-testing is at least as up to date as kde-testing. If so, it would appear to make more sense for testers to do:
yum --enablerepo=updates-testing groupupdate "KDE (K Desktop Environment)"
or am I missing something?
poc
Patrick O'Callaghan wrote:
So it's really the other way round, i.e. updates-testing is at least as up to date as kde-testing.
That's not what I said. Update pushes take some time, so often the updates will hit kde-testing before they make their way into the official updates- testing.
Kevin Kofler
On Thu, 2009-08-13 at 10:36 -0430, Patrick O'Callaghan wrote:
So it's really the other way round, i.e. updates-testing is at least as up to date as kde-testing. If so, it would appear to make more sense for testers to do:
yum --enablerepo=updates-testing groupupdate "KDE (K Desktop
Environment)"
Running this from a fully updated F11/KDE install:
# yum --enablerepo=updates-testing groupupdate "KDE (K Desktop Environment)" Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities, refresh-packagekit updates-testing/metalink | 13 kB 00:00 updates-testing | 4.4 kB 00:00 updates-testing/primary_db | 893 kB 00:01 1113 packages excluded due to repository priority protections Setting up Group Process updates-testing/group_gz | 372 kB 00:00 Package kdebase-workspace-4.2.4-5.fc11.i586 already installed and latest version Package 6:kdelibs-4.2.4-6.fc11.i586 already installed and latest version Package kpackagekit-0.4.1.1-2.fc11.i586 already installed and latest version Package digikam-0.10.0-1.fc11.i586 already installed and latest version Package 6:kdemultimedia-4.2.4-1.fc11.i586 already installed and latest version Package 1:NetworkManager-gnome-0.7.1-8.git20090708.fc11.i586 already installed and latest version Package 6:kdeutils-printer-applet-4.2.4-2.fc11.i586 already installed and latest version Package 6:kdepim-4.2.4-1.fc11.i586 already installed and latest version Package 6:kdebase-4.2.4-2.fc11.i586 already installed and latest version Package 6:kdegames-4.2.4-1.fc11.i586 already installed and latest version Package 6:kdeutils-4.2.4-2.fc11.i586 already installed and latest version Package xine-lib-extras-freeworld-1.1.16.3-1.fc11.i586 already installed and latest version Package 7:kdenetwork-4.2.4-4.fc11.i586 already installed and latest version Package kdeplasma-addons-4.2.4-1.fc11.i586 already installed and latest version Package pinentry-qt-0.7.4-6.fc11.i586 already installed and latest version Package amarok-2.1.1-1.fc11.i586 already installed and latest version Package 7:kdegraphics-4.2.4-1.fc11.i586 already installed and latest version Package kdeartwork-screensavers-4.2.4-1.fc11.i586 already installed and latest version Package 1:kdebluetooth-0.3-3.fc11.i586 already installed and latest version Package gstreamer-ffmpeg-0.10.7-2.fc11.1.i586 already installed and latest version Package gstreamer-plugins-ugly-0.10.12-1.fc11.i586 already installed and latest version Resolving Dependencies --> Running transaction check ---> Package PolicyKit-kde.i586 0:4.2.90-1.fc11 set to be updated --> Processing Dependency: libpolkit-qt-gui.so.0 for package: PolicyKit-kde-4.2.90-1.fc11.i586 --> Processing Dependency: libpolkit-qt-core.so.0 for package: PolicyKit-kde-4.2.90-1.fc11.i586 ---> Package cups-pk-helper.i586 0:0.0.4-1.fc11 set to be updated ---> Package k3b-extras-freeworld.i586 0:1.0.5-6.fc11 set to be updated ---> Package kaffeine.i586 0:0.8.7-7.fc11 set to be updated ---> Package kde-settings-pulseaudio.noarch 0:4.2-10.20090430svn.fc11 set to be updated --> Processing Dependency: pulseaudio-module-x11 for package: kde-settings-pulseaudio-4.2-10.20090430svn.fc11.noarch ---> Package kdeaccessibility.i586 1:4.2.4-1.fc11 set to be updated ---> Package kdepim-runtime.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: kdepim-runtime-libs = 4.3.0-1.fc11 for package: kdepim-runtime-4.3.0-1.fc11.i586 --> Processing Dependency: libknotificationitem-1.so.1 for package: kdepim-runtime-4.3.0-1.fc11.i586 --> Processing Dependency: libakonadi-xml.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 --> Processing Dependency: libmicroblog.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 --> Processing Dependency: libkdepim-copy.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 ---> Package kftpgrabber.i586 0:0.8.1-9.fc11 set to be updated ---> Package kipi-plugins.i586 0:0.5.0-1.fc11 set to be updated ---> Package konq-plugins.i586 0:4.2.4-1.fc11 set to be updated ---> Package konversation.i586 0:1.1-6.fc11 set to be updated ---> Package ksshaskpass.i586 0:0.5.1-3.fc11 set to be updated ---> Package ktorrent.i586 0:3.2.2-2.fc11 set to be updated --> Processing Dependency: libGeoIP.so.1 for package: ktorrent-3.2.2-2.fc11.i586 ---> Package libtunepimp-extras-freeworld.i586 0:0.5.3-7.fc11 set to be updated ---> Package scribus.i586 0:1.3.5-0.14.rc3.fc11 set to be updated --> Processing Dependency: tkinter for package: scribus-1.3.5-0.14.rc3.fc11.i586 ---> Package system-config-printer-kde.i586 7:4.2.4-1.fc11 set to be updated ---> Package xsettings-kde.i586 0:0.9-2.fc11 set to be updated --> Running transaction check ---> Package GeoIP.i586 0:1.4.6-1.fc11 set to be updated ---> Package kdelibs-experimental.i586 0:4.3.0-1.fc11 set to be updated ---> Package kdepim-runtime.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: libmicroblog.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 ---> Package kdepim-runtime-libs.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: akonadi(x86-32) >= 1.1.95 for package: kdepim-runtime-libs-4.3.0-1.fc11.i586 ---> Package polkit-qt.i586 0:0.9.2-1.fc11 set to be updated ---> Package pulseaudio-module-x11.i586 0:0.9.15-14.fc11 set to be updated ---> Package tkinter.i586 0:2.6-9.fc11 set to be updated --> Processing Dependency: libTix.so for package: tkinter-2.6-9.fc11.i586 --> Running transaction check ---> Package kdepim-runtime.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: libmicroblog.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 ---> Package kdepim-runtime-libs.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: akonadi(x86-32) >= 1.1.95 for package: kdepim-runtime-libs-4.3.0-1.fc11.i586 ---> Package tix.i586 1:8.4.3-3.fc11 set to be updated --> Finished Dependency Resolution kdepim-runtime-4.3.0-1.fc11.i586 from updates-testing has depsolving problems --> Missing Dependency: libmicroblog.so.4 is needed by package kdepim-runtime-4.3.0-1.fc11.i586 (updates-testing) kdepim-runtime-4.3.0-1.fc11.i586 from updates-testing has depsolving problems --> Missing Dependency: libmicroblog.so.4 is needed by package kdepim-runtime-4.3.0-1.fc11.i586 (updates-testing) kdepim-runtime-libs-4.3.0-1.fc11.i586 from updates-testing has depsolving problems --> Missing Dependency: akonadi(x86-32) >= 1.1.95 is needed by package kdepim-runtime-libs-4.3.0-1.fc11.i586 (updates-testing) DEBUG: [] Error: Missing Dependency: libmicroblog.so.4 is needed by package kdepim-runtime-4.3.0-1.fc11.i586 (updates-testing) Error: Missing Dependency: akonadi(x86-32) >= 1.1.95 is needed by package kdepim-runtime-libs-4.3.0-1.fc11.i586 (updates-testing) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest
What is the best way to cure these dependency problems ? Use kde-testing instead ?
Thanks
Linuxguy123 wrote:
On Thu, 2009-08-13 at 10:36 -0430, Patrick O'Callaghan wrote:
So it's really the other way round, i.e. updates-testing is at least as up to date as kde-testing. If so, it would appear to make more sense for testers to do:
yum --enablerepo=updates-testing groupupdate "KDE (K Desktop
Environment)"
Running this from a fully updated F11/KDE install:
# yum --enablerepo=updates-testing groupupdate "KDE (K Desktop Environment)" Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities, refresh-packagekit updates-testing/metalink | 13 kB 00:00 updates-testing | 4.4 kB 00:00 updates-testing/primary_db | 893 kB 00:01 1113 packages excluded due to repository priority protections Setting up Group Process updates-testing/group_gz | 372 kB 00:00 Package kdebase-workspace-4.2.4-5.fc11.i586 already installed and latest version Package 6:kdelibs-4.2.4-6.fc11.i586 already installed and latest version Package kpackagekit-0.4.1.1-2.fc11.i586 already installed and latest version Package digikam-0.10.0-1.fc11.i586 already installed and latest version Package 6:kdemultimedia-4.2.4-1.fc11.i586 already installed and latest version Package 1:NetworkManager-gnome-0.7.1-8.git20090708.fc11.i586 already installed and latest version Package 6:kdeutils-printer-applet-4.2.4-2.fc11.i586 already installed and latest version Package 6:kdepim-4.2.4-1.fc11.i586 already installed and latest version Package 6:kdebase-4.2.4-2.fc11.i586 already installed and latest version Package 6:kdegames-4.2.4-1.fc11.i586 already installed and latest version Package 6:kdeutils-4.2.4-2.fc11.i586 already installed and latest version Package xine-lib-extras-freeworld-1.1.16.3-1.fc11.i586 already installed and latest version Package 7:kdenetwork-4.2.4-4.fc11.i586 already installed and latest version Package kdeplasma-addons-4.2.4-1.fc11.i586 already installed and latest version Package pinentry-qt-0.7.4-6.fc11.i586 already installed and latest version Package amarok-2.1.1-1.fc11.i586 already installed and latest version Package 7:kdegraphics-4.2.4-1.fc11.i586 already installed and latest version Package kdeartwork-screensavers-4.2.4-1.fc11.i586 already installed and latest version Package 1:kdebluetooth-0.3-3.fc11.i586 already installed and latest version Package gstreamer-ffmpeg-0.10.7-2.fc11.1.i586 already installed and latest version Package gstreamer-plugins-ugly-0.10.12-1.fc11.i586 already installed and latest version Resolving Dependencies --> Running transaction check ---> Package PolicyKit-kde.i586 0:4.2.90-1.fc11 set to be updated --> Processing Dependency: libpolkit-qt-gui.so.0 for package: PolicyKit-kde-4.2.90-1.fc11.i586 --> Processing Dependency: libpolkit-qt-core.so.0 for package: PolicyKit-kde-4.2.90-1.fc11.i586 ---> Package cups-pk-helper.i586 0:0.0.4-1.fc11 set to be updated ---> Package k3b-extras-freeworld.i586 0:1.0.5-6.fc11 set to be updated ---> Package kaffeine.i586 0:0.8.7-7.fc11 set to be updated ---> Package kde-settings-pulseaudio.noarch 0:4.2-10.20090430svn.fc11 set to be updated --> Processing Dependency: pulseaudio-module-x11 for package: kde-settings-pulseaudio-4.2-10.20090430svn.fc11.noarch ---> Package kdeaccessibility.i586 1:4.2.4-1.fc11 set to be updated ---> Package kdepim-runtime.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: kdepim-runtime-libs = 4.3.0-1.fc11 for package: kdepim-runtime-4.3.0-1.fc11.i586 --> Processing Dependency: libknotificationitem-1.so.1 for package: kdepim-runtime-4.3.0-1.fc11.i586 --> Processing Dependency: libakonadi-xml.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 --> Processing Dependency: libmicroblog.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 --> Processing Dependency: libkdepim-copy.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 ---> Package kftpgrabber.i586 0:0.8.1-9.fc11 set to be updated ---> Package kipi-plugins.i586 0:0.5.0-1.fc11 set to be updated ---> Package konq-plugins.i586 0:4.2.4-1.fc11 set to be updated ---> Package konversation.i586 0:1.1-6.fc11 set to be updated ---> Package ksshaskpass.i586 0:0.5.1-3.fc11 set to be updated ---> Package ktorrent.i586 0:3.2.2-2.fc11 set to be updated --> Processing Dependency: libGeoIP.so.1 for package: ktorrent-3.2.2-2.fc11.i586 ---> Package libtunepimp-extras-freeworld.i586 0:0.5.3-7.fc11 set to be updated ---> Package scribus.i586 0:1.3.5-0.14.rc3.fc11 set to be updated --> Processing Dependency: tkinter for package: scribus-1.3.5-0.14.rc3.fc11.i586 ---> Package system-config-printer-kde.i586 7:4.2.4-1.fc11 set to be updated ---> Package xsettings-kde.i586 0:0.9-2.fc11 set to be updated --> Running transaction check ---> Package GeoIP.i586 0:1.4.6-1.fc11 set to be updated ---> Package kdelibs-experimental.i586 0:4.3.0-1.fc11 set to be updated ---> Package kdepim-runtime.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: libmicroblog.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 ---> Package kdepim-runtime-libs.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: akonadi(x86-32) >= 1.1.95 for package: kdepim-runtime-libs-4.3.0-1.fc11.i586 ---> Package polkit-qt.i586 0:0.9.2-1.fc11 set to be updated ---> Package pulseaudio-module-x11.i586 0:0.9.15-14.fc11 set to be updated ---> Package tkinter.i586 0:2.6-9.fc11 set to be updated --> Processing Dependency: libTix.so for package: tkinter-2.6-9.fc11.i586 --> Running transaction check ---> Package kdepim-runtime.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: libmicroblog.so.4 for package: kdepim-runtime-4.3.0-1.fc11.i586 ---> Package kdepim-runtime-libs.i586 0:4.3.0-1.fc11 set to be updated --> Processing Dependency: akonadi(x86-32) >= 1.1.95 for package: kdepim-runtime-libs-4.3.0-1.fc11.i586 ---> Package tix.i586 1:8.4.3-3.fc11 set to be updated --> Finished Dependency Resolution kdepim-runtime-4.3.0-1.fc11.i586 from updates-testing has depsolving problems --> Missing Dependency: libmicroblog.so.4 is needed by package kdepim-runtime-4.3.0-1.fc11.i586 (updates-testing) kdepim-runtime-4.3.0-1.fc11.i586 from updates-testing has depsolving problems --> Missing Dependency: libmicroblog.so.4 is needed by package kdepim-runtime-4.3.0-1.fc11.i586 (updates-testing) kdepim-runtime-libs-4.3.0-1.fc11.i586 from updates-testing has depsolving problems --> Missing Dependency: akonadi(x86-32) >= 1.1.95 is needed by package kdepim-runtime-libs-4.3.0-1.fc11.i586 (updates-testing) DEBUG: [] Error: Missing Dependency: libmicroblog.so.4 is needed by package kdepim-runtime-4.3.0-1.fc11.i586 (updates-testing) Error: Missing Dependency: akonadi(x86-32) >= 1.1.95 is needed by package kdepim-runtime-libs-4.3.0-1.fc11.i586 (updates-testing) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest
What is the best way to cure these dependency problems ? Use kde-testing instead ?
Wuoldn't hurt. I think the last F11 updates push got botched (I inadvertantly was editing the update while it was being pushed).
-- Rex
On Thu, 2009-08-13 at 12:07 -0500, Rex Dieter wrote:
What is the best way to cure these dependency problems ? Use kde-testing instead ?
Wuoldn't hurt. I think the last F11 updates push got botched (I inadvertantly was editing the update while it was being pushed).
What is the full repository name for "kde-testing" ?
Thanks
2009/8/13 Linuxguy123 linuxguy123@gmail.com:
On Thu, 2009-08-13 at 12:07 -0500, Rex Dieter wrote:
What is the best way to cure these dependency problems ? Use kde-testing instead ?
Wuoldn't hurt. I think the last F11 updates push got botched (I inadvertantly was editing the update while it was being pushed).
What is the full repository name for "kde-testing" ?
If you are using the provided repo files at kde-redhat.sourceforge.net then the full repo name is "kde-testing". If you have hand edited the repo file then obviously it could be whatever you changed it to.
Patrick O'Callaghan wrote:
On Thu, 2009-08-13 at 06:36 -0500, Rex Dieter wrote:
Anne Wilson wrote:
On Thursday 13 August 2009 10:31:12 Nikita Bige wrote:
I use plain imap, pop3 and filters. kmail crashes 10-20 time per day :( After last upgrade to kdepim-4.3.0-2.fc11.x86_64 I can't find proper debuginfo packages for making good bug reports...
My guess would be kdepim-debuginfo ;-) Isn't that there for x86_64?
I'm starting to sync latest packages in upates-testing to kde-testing, but without debuginfo. Ie, if you want debuginfo, you need to get them from updates-testing.
Er, that confuses me. I was under the impression that it went like this:
kde-testing -> updates-testing -> updates
Is that wrong?
No. kde* repos we have direct control over, so we can put anything we want in them. In this case, I've been syncing the latest updates-testing builds into kde-testing too. The caveat of doing that is it (kde*) misses -debuginfo pkgs.
-- Rex
On Thu, 2009-08-13 at 09:36 -0500, Rex Dieter wrote:
Patrick O'Callaghan wrote:
On Thu, 2009-08-13 at 06:36 -0500, Rex Dieter wrote:
Anne Wilson wrote:
On Thursday 13 August 2009 10:31:12 Nikita Bige wrote:
I use plain imap, pop3 and filters. kmail crashes 10-20 time per day :( After last upgrade to kdepim-4.3.0-2.fc11.x86_64 I can't find proper debuginfo packages for making good bug reports...
My guess would be kdepim-debuginfo ;-) Isn't that there for x86_64?
I'm starting to sync latest packages in upates-testing to kde-testing, but without debuginfo. Ie, if you want debuginfo, you need to get them from updates-testing.
Er, that confuses me. I was under the impression that it went like this:
kde-testing -> updates-testing -> updates
Is that wrong?
No. kde* repos we have direct control over, so we can put anything we want in them. In this case, I've been syncing the latest updates-testing builds into kde-testing too. The caveat of doing that is it (kde*) misses -debuginfo pkgs.
I just answered Kevin before seeing this, which changes things a little.
From what you say there is no guaranteed precedence relation between the
two repos, i.e. one may have more recent packages than the other, or vice versa. So what's the conscientious tester to do? Use both? (I'm not being provocative, it's a real question).
poc
Patrick O'Callaghan wrote:
On Thu, 2009-08-13 at 09:36 -0500, Rex Dieter wrote:
Patrick O'Callaghan wrote:
On Thu, 2009-08-13 at 06:36 -0500, Rex Dieter wrote:
Anne Wilson wrote:
On Thursday 13 August 2009 10:31:12 Nikita Bige wrote:
I use plain imap, pop3 and filters. kmail crashes 10-20 time per day :( After last upgrade to kdepim-4.3.0-2.fc11.x86_64 I can't find proper debuginfo packages for making good bug reports...
My guess would be kdepim-debuginfo ;-) Isn't that there for x86_64?
I'm starting to sync latest packages in upates-testing to kde-testing, but without debuginfo. Ie, if you want debuginfo, you need to get them from updates-testing.
Er, that confuses me. I was under the impression that it went like this:
kde-testing -> updates-testing -> updates
Is that wrong?
No. kde* repos we have direct control over, so we can put anything we want in them. In this case, I've been syncing the latest updates-testing builds into kde-testing too. The caveat of doing that is it (kde*) misses -debuginfo pkgs.
I just answered Kevin before seeing this, which changes things a little.
From what you say there is no guaranteed precedence relation between the
two repos, i.e. one may have more recent packages than the other, or vice versa. So what's the conscientious tester to do? Use both? (I'm not being provocative, it's a real question).
My own personal recommendation is usually to use the union of both kde-testing and updates-testing.
For those less willing to touch updates-testing, then just do kde-testing.
Some folks prefer to cherry-pick stuff from updates-testing, but that has it's own downsides and pitfalls (ie, there are sometimes implicit dependencies with other stuff in updates-testing ).
-- Rex
On Thursday 13 August 2009 09:41:29 Jeremy Sanders wrote:
Linuxguy123 wrote:
Subject says it all. Just wondering...
No problems except for the PackageKit crash above.
Oh, and, the fact that using PulseAudio causes Amarok to hang at the end of tracks (as it did previously). I blame PulseAudio personally!
On this laptop PA fails totally - but it does fall back gracefully. I have no complaints. On the netbook PA does work. Naturally I don't use Amarok much on the netbook, but I have done, and haven't seen this problem.
PA problems largely come down to the audio chipset, so it's always useful to mention that. Mine is Intel ICH6 - and Intel audio chipsets seem to be among the worst for PA working. However, as I said, fall-back is smooth, and sound works perfectly, so no complaints from me.
Anne
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Anne Wilson wrote:
On Thursday 13 August 2009 09:41:29 Jeremy Sanders wrote:
Linuxguy123 wrote:
Subject says it all. Just wondering...
No problems except for the PackageKit crash above.
Oh, and, the fact that using PulseAudio causes Amarok to hang
at the end of
tracks (as it did previously). I blame PulseAudio personally!
Not seeing with last.fm here :/ .
On this laptop PA fails totally - but it does fall back
gracefully. I have no
complaints. On the netbook PA does work. Naturally I don't
use Amarok much
on the netbook, but I have done, and haven't seen this
problem.
PA problems largely come down to the audio chipset, so it's
always useful to
mention that. Mine is Intel ICH6 - and Intel audio chipsets
seem to be among
the worst for PA working. However, as I said, fall-back is
smooth, and sound
works perfectly, so no complaints from me.
Huh. that's what I have on both my machines where it works without complaint. They're ICH8, maybe that's the difference?
- --Ben
Anne
Anne Wilson wrote:
PA problems largely come down to the audio chipset, so it's always useful to mention that. Mine is Intel ICH6 - and Intel audio chipsets seem to be among the worst for PA working. However, as I said, fall-back is smooth, and sound works perfectly, so no complaints from me.
Mine is an Audigy 4 for reference: $ cat /proc/asound/cards 0 [Audigy2 ]: Audigy2 - Audigy 4 [SB0610] Audigy 4 [SB0610] (rev.0, serial:0x10211102) at 0x1000, irq 18
Jeremy
Linuxguy123 wrote:
Subject says it all. Just wondering...
Now I'm seeing really strange things happening on the Task Manager bar which I never saw on KDE 4.2.
Even though I have it set to only show applications on the current desktop, it shows them on other desktops. It is also currently showing two buttons that correspond to a single window! I've also seen some buttons which correspond to closed windows.
Jeremy
On Tuesday 18 August 2009 10:45:35 Jeremy Sanders wrote:
Linuxguy123 wrote:
Subject says it all. Just wondering...
Now I'm seeing really strange things happening on the Task Manager bar which I never saw on KDE 4.2.
Even though I have it set to only show applications on the current desktop, it shows them on other desktops. It is also currently showing two buttons that correspond to a single window! I've also seen some buttons which correspond to closed windows.
I'm not seeing such problems here. Have you tried re-starting plasma? In a konsole
kquitapp plasma & plasma
Anne
Anne Wilson wrote:
I'm not seeing such problems here. Have you tried re-starting plasma? In a konsole
kquitapp plasma & plasma
That fixes it but the problems return after a while.
This appears to be part of the problem: http://bugs.kde.org/show_bug.cgi?id=202199
Jeremy
On Tuesday 18 August 2009 14:42:20 Jeremy Sanders wrote:
Anne Wilson wrote:
I'm not seeing such problems here. Have you tried re-starting plasma? In a konsole
kquitapp plasma & plasma
That fixes it but the problems return after a while.
This appears to be part of the problem: http://bugs.kde.org/show_bug.cgi?id=202199
There doesn't seem any clear indication of where problems like this really do come from. I haven't seen any of the things mentioned in that thread (as far as I can see from a quick skim through). I do have the problem of firefox apparently shutting down, in that it disappears from both screen and taskbar, but stays active behind the scenes, quickly building up to 99% cpu. I have to manually kill it every time I use it. However, that's no concern of plasma, and if restarting clears it for you it obviously is a plasma bug. I don't know what to suggest, other than filing another bug report.
Anne
On Tue, 2009-08-18 at 15:22 +0100, Anne Wilson wrote:
On Tuesday 18 August 2009 14:42:20 Jeremy Sanders wrote:
Anne Wilson wrote:
I'm not seeing such problems here. Have you tried re-starting plasma? In a konsole
kquitapp plasma & plasma
That fixes it but the problems return after a while.
This appears to be part of the problem: http://bugs.kde.org/show_bug.cgi?id=202199
There doesn't seem any clear indication of where problems like this really do come from. I haven't seen any of the things mentioned in that thread (as far as I can see from a quick skim through). I do have the problem of firefox apparently shutting down, in that it disappears from both screen and taskbar, but stays active behind the scenes, quickly building up to 99% cpu. I have to manually kill it every time I use it. However, that's no concern of plasma, and if restarting clears it for you it obviously is a plasma bug. I don't know what to suggest, other than filing another bug report.
I haven't seen either of these problems, but with KDE it's often a good idea to try things in a fresh user account to see if they are reproducible.
poc