Hallo,
spätestens seit dem Update auf KDE 4.2.2 kommt im kadressbook beim Anklicken
eines Kontaktes der mehrere Mailadressen hat immer zu diesen nervigen
Dialogen überschrieben mit "Select Email Adress". Im Dialog kann man die
Mailadressen des Dialogs auswählen und bestätigen, der Dialog kommt aber
sofort wieder, typischerweise 2x.
Sobald dann aber wieder der Kontakt ausgewählt wird kommt der Dialog wieder
- er scheint also zumindest nicht irgendwelche Standardmailadressen
sicherheitshalber zu setzen.
Was der Dialog sonst bewirkt ist mir nicht bekannt.
Weiß da jemand näheres bzw. wie man das kadressbook wieder abgewöhnen kann?
Danke,
Christian
--
Christian Lorch :: der nett.Zwerg-Berater
I'm breaking my own rules again, but I just reenabled publish on
KDE:KDE4:STABLE:Desktop after about a 12 hour unpublish to prepare online
updates there for
kdelibs4
kdepimlibs4
kdebase4
kdebase4-runtime
kdebase4-workspace
kdepim4
4.1.3 users, this update fixes a lot of bugs - please test, but be aware that
Plasma did not see much work in 4.1 branch and our packages already have many
backports from trunk, so don't expect the world to change there.
Will
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Geoff wrote:
> Hi
> yawp
> <http://www.kde-look.org/content/show.php/yaWP+%28Yet+Another+Weather+Plasmo…>
> has african weather
>
> regards
> Geoff
>
Thanks Geoff, yawp seems to be even better than kweather, maybe thats
why nobody requested a feature change in kde4-kweather.
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hello SuSE people,
In my 11.1 testbed with KDE4.2, I finally am able to open my CD & DVD drives,
flash cards, and my USB hard drive. When the little device notifier pops up
it correctly identifies the app. However, it only gives the choice of opening
with Dolphin. In the case of a CD with music on it, it should offer a music
player or with a DVD movie offer a video player which it does not.
Am I the only one or do others verify this quirk? If I am the only one, is
there a config file someplace for hal? I guess it is. If others have the same
problem and there is no work-around I will file a bug.
Bob S
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
That's good news. Thank you for your attention.
On Tue, Apr 7, 2009 at 12:56 PM, Jan Kara <jack(a)suse.cz> wrote:
> Hi,
>
> On Tue 07-04-09 12:52:05, Danilo Luvizotto wrote:
>> If I listen to music for some time (I guess around 1 hour after
>> starting listening to music) my filesystem becomes readonly and I
>> can't continue using the system, so I have to reboot. When I do it,
>> fsck has to check the filesystem for 20 minutes and find some errors
>> but I have never lost data (yet). I have already run the hard drive
>> auto-diagnostic in the notebook BIOS (HP Pavillion dv2872br) but no
>> problems were found.
>> At first I thought the problem was with the nvidia driver, but at
>> the nvidia forum they said there was nothing related to nvidia in my
>> log files and I had no video problems. Anyway, as the filesystem gets
>> readonly, no information is recorded to the log files. I could get a
>> lot of information running nvidia-bug-report.sh in a folder in my
>> windows partition (witch was not readonly), it's output is attached to
>> this message.
>> A relevant part of the log is:
>>
>> EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted
>> EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Journal has aborted
>> EXT3-fs error (device dm-0) in ext3_dirty_inode: Journal has aborted
>> ext3_abort called.
>> EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
>> Remounting filesystem read-only
>> JBD: Detected IO errors while flushing file data on dm-0
>> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
>> ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
>> res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> This is a known bug. Should be fixed by the nearest kernel update (which
> is already in QA AFAIK). Thanks for the report.
>
> Honza
> --
> Jan Kara <jack(a)suse.cz>
> SUSE Labs, CR
>
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
What is the status of the KDE4 Unstable repositories. I can see that the
new snapshot has been build successfully, but still it is not published.
Also the KDE4:Community repositories connected to the Unstable build are
blocked for publishing.
My personal experience is that the quality/stability of the KDE4.3 is
getting better with each snapshot. With the new snapshot 4.2.69 I
noticed that Plasma is crashing if NetworkManager-kde4 is being used. It
is crashing on kglobalaccel.
Thanks
Regards
Raymond
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hi,
Knetworkmanager (kde3) is/was still default in kde4.2.
But if one knows that somehow wpa settings do not get saved, so one has
to configure these everytime one boots, one wants to try another
version, like NetworkManager-kde4.
Invoking it from the cmd as $, gives the location, and the hint to
invoke it as #.
Invoking it as root gives nothing.
wpa_gui also is bugged as it states you have to use a minimum of eight
symbols when you use 8, and will also not save anything...
I upgraded to 2.6.29.60 today to find that wifi is onboard again, so i
end up with dead end streets again.
Is it usefull to file a bug against knetworkmanager, as it is gonna be
dropped anyway?
I would like to be able to use my wireless without having to config it
every startup..
--
Have a nice day ;)
Oddball aka M9.
OS: Linux 2.6.29-60-default i686
Huidige gebruiker: oddball@EEEPC-901-ROB
Systeem: openSUSE 11.1 (i586)
KDE: 4.2.2 (KDE 4.2.2) "release 110"
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
On Thu, Apr 2, 2009 at 3:54 PM, Sven Burmeister <sven.burmeister(a)gmx.net> wrote:
> - Create a KDE 4.2 repo by copying the files from the Factory repo. The KDE
> 4.2 repo is opensuse stable, i.e. frozen. The repo will not see any 4.2.3
> version and only really, really important patches are added after the
> creation.
I have been watching and discussing the proposed repository layout for a
while. And I believe with the new release schedule for openSUSE the KDE repo
should be simple and look something like:
KDE:/{Stable,Release,Factory}
Where Stable is the current openSUSE version.
Where Release (or something that defines a release from KDE) is the latest
version from KDE such as 4.2.2 now.
Where Factory is the next openSUSE version.
Users should have no problem using Release and it switching from 4.2.4 to
4.3.0 as long as it is the latest release from KDE, right? With Release users
will never miss a release from KDE (and that's what they want).
Let's really try to keep this simple and avoid version number labeled
repositories. That really was the original intention of Stable, Factory, and
Unstable, wasn't it?
Therefore, the spins could just point to Release. This way Release is always
the latest from KDE.
At times there will be overlapping between the repositories but this is
acceptable. On the other hand right now Stable would be openSUSE 11.1 patched
packages, Release would be KDE 4.2.2 packages, and Factory would be whatever
openSUSE 11.2 will be using.
This way openSUSE KDE testing could always be done in Factory and bleeding
edge KDE users can always use Release.
--
Marc Benstein
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
On 03/04/09 19:30, Lubos Lunak wrote:
> On the other hand, maintaining such packages should be quite simple. Updates
> needed about once in a month, no patches, it should generally build fine.
> IMHO this just depends on whether there would be somebody who would want to
> do this - I would find it a waste of resources if somebody did it just
> because it "should" be done.
But for which KDE versions would this be necessary ? The KDE version in
Factory or also for versions lower ? I agree that it would sense to have
such a Vanilla repository.
But is the current KDE4:Unstable not already a Vanilla KDE ?
Regards
Raymond
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
In the previous thread KDE 4.2 stable repo and KDE live CD respin the
discussion evolved at one point to a community maintained vanilla version of KDE.
By vanilla I mean an unmodified (openSUSE branding could be optional) packages
directly from the KDE release?
Is there an interest from the community for a vanilla set of KDE packages
based on official KDE releases?
Who would be willing to maintain such a set of packages? Would our resources
be better used to help Factory? Certainly right now it is much better to use
the latest from KDE, but will it be in the future? The reason I came to the
openSUSE project was because of the heavily modified KDE. If the community is
using resources to package and use a vanilla KDE then what makes KDE on
openSUSE so special?
--
Marc Benstein
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org