Re: Dual monitor setup changes after logoff/on
by Armelius Cameron
On Tuesday, April 26, 2011 08:55:49 am you wrote:
> 2011/4/25 Gene Smith <gds(a)chartertn.net>:
> > Алексей Подтележников wrote, On 04/25/2011 11:27 AM:
> >> I found a workaround for this problem.
> >> You should edit .kde/share/config/krandrrc by hand.
> >> The bottom line is that the StartupCommands= line
> >> is currently brain dead. Try to use a single xrandr call
> >> with multiple --output options there.
> >>
> >> More details here: https://bugzilla.redhat.com/show_bug.cgi?id=699024
> >>
> >> Let me know if you have more questions, or send me the broken
> >> StartupCommands= line, so that I can fix it for you.
> >
> > Thanks for the additional info. However, I saw your bug post describing
> > this in the original bug report
> > https://bugs.kde.org/show_bug.cgi?id=183143#c50 but haven't tried it
> > yet. I also wonder about a related file called startupconfig in the same
> > dir that also contains the same string. This file seems to be saved only
> > when you do the "save as default" from the config screen (not sure when
> > krandrrc is saved). Anyhow, not sure why this bug is considered fixed
> > and resolved!
>
> Gene,
>
> It is important that you tweak StartupCommands= line to work for you,
> Your independent confirmation is valuable, so please post your factual
> findings with respect to this particular line in the config files.
> This will bring it to focus by upstream.
>
> Alexei
Thanks for the info. I will try this when I get back to my office.
AC
13 years
KWallet and KMail issue
by Martin Kho
Hi,
Using full updated standard fc14 (no kde-redhat) I experience a problem with
retrieving the saved password in KWallet for sending e-mails. Checking mail
works ok. I get the following message:
"There have been repeated failed attempts to gain access to a wallet. An
application may be misbehaving."
I've tried to remove all entries in KWallet, moved config and *.kwl files
without succes.
Anyone else have seen this? Any ideas how to solve this issue?
Thanks,
Martin Kho
13 years
Dual monitor setup changes after logoff/on
by Gene Smith
I have two monitors (1600*1200) with DVI0 on right and DVI1 on left.
DVI0 has the panel and begins at x,y = 1600,0 with DVI0 at 0,0 so the
mouse moves horizontally across both monitors as expected. After doing
this initial setup in KDE it worked fine for several days but I never
logged off.
Then upgrade to kde 4.6.2 required logoff/on and the dual monitor
configuration was not preserved and it returned to the original default
(when moving mouse pointer on right monitor to the left edge it stops
and if moved past right edge of right monitor it reappears on left edge
of left monitor). Effectively this mean that DVI0 is at 0,0 and DVI1 is
at 1600,0 which is probably the most used default. This time I reset the
coordinates as described in my first paragraph and it worked correctly
again. However, this time I decided to set this as the default hoping
this would cause KDE or whatever to keep my settings after an X restart
or logoff/on. (Note: The help screen for monitor setup in KDE is grayed
out so not really sure what "set as default" really means.)
However, now after logoff/on the monitors come up "cloned" with the same
stuff on both (and having the same coordinates I think). Again, using
the monitor config KDE screen I was able to get my desired setup back.
There is probably a workaround to this such as reversing my monitor
cables and setting the right monitor (now DVI1) to "primary" so it
contains the panel. However, it still appears to be a bug that my
settings are not preserved across reboots or logins.
-gene
13 years
New glitch in Akregator
by Anne Wilson
Because I subscribe to some very busy feeds I tend to use the Unread view.
After the latest update, clicking on one message makes that and the next
message disappear, without any possibility of reading it.
Anyone else seeing this?
Anne
--
New to KDE Software? - get help from http://userbase.kde.org
13 years
Interested in helping.
by Brock Hudson
Hello, I am interested in Joining the KDE sig. I have been a previous member
of the Xfce sig but since my prefered desktop is KDE I wanted to help further
it in Fedora. I helped with documentation in the Xfce sig and I have minor
programming skills, enough to patch and fix bugs but not enough to create an
application from scratch. I can package as well however I am sure there are
enough users doing this already. Hopefully I can help you guys.
13 years
kdepim-4.5.95-1 works for me
by Peter G.
sending, receiving mail; newsgroups in knode; calendar and alerts; addressbook:
no problems experienced so far.
13 years
printer config permission problems
by Neal Becker
Nice applet for system settings/printer configuration. But don't try to change
any settings, because it doesn't ask for root permission. All it does is say:
"There was an error during CUPS operation: 'client-error-forbidden'
This is kdebase-4.6.0-0.1.fc14.x86_64
13 years
Incorrect F15 package kdebase-runtime-flags in kde-testing for F14
by Laurent Rineau
On my Fedora 14, with kde-testing enabled:,
$ rpm -q fedora-release
fedora-release-14-1.noarch
$ yum -C list kdebase-runtime-flags
Loaded plugins: changelog, downloadonly, presto, ps, refresh-packagekit,
remove-with-leaves, security, verify
Installed Packages
kdebase-runtime-flags.noarch 4.6.2-1.fc14
@kde-testing
Available Packages
kdebase-runtime-flags.noarch 4.6.2-1.fc15
kde-testing
If I try to update, I get the following deps errors:
$ sudo yum update
Loaded plugins: changelog, downloadonly, presto, ps, refresh-packagekit,
remove-with-leaves, security, verify
Setting up Update Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: kdebase-runtime-flags = 4.6.2-1.fc14 for package:
kdebase-runtime-4.6.2-1.fc14.x86_64
---> Package kdebase-runtime-flags.noarch 0:4.6.2-1.fc15 set to be updated
--> Processing Dependency: kdebase-runtime = 4.6.2-1.fc15 for package:
kdebase-runtime-flags-4.6.2-1.fc15.noarch
--> Finished Dependency Resolution
Error: Package: kdebase-runtime-flags-4.6.2-1.fc15.noarch (kde-testing)
Requires: kdebase-runtime = 4.6.2-1.fc15
Installed: kdebase-runtime-4.6.2-1.fc14.x86_64 (@kde-testing)
kdebase-runtime = 4.6.2-1.fc14
Available: kdebase-runtime-4.5.2-1.fc14.x86_64 (fedora)
kdebase-runtime = 4.5.2-1.fc14
Error: Package: kdebase-runtime-4.6.2-1.fc14.x86_64 (@kde-testing)
Requires: kdebase-runtime-flags = 4.6.2-1.fc14
Removing: kdebase-runtime-flags-4.6.2-1.fc14.noarch (@kde-testing)
kdebase-runtime-flags = 4.6.2-1.fc14
Updated By: kdebase-runtime-flags-4.6.2-1.fc15.noarch (kde-testing)
kdebase-runtime-flags = 4.6.2-1.fc15
Available: kdebase-runtime-flags-4.5.2-1.fc14.noarch (fedora)
kdebase-runtime-flags = 4.5.2-1.fc14
You could try using --skip-broken to work around the problem
13 years
Device Notifier - Phantom Entry
by Ed Greshko
I've an entry in the Device Notifier for a 4GB SD card that isn't
plugged in. Yet Device Notifier shows it. Of course if I tell it to
mount it, it can't...but the entry is still there.
Maybe it will go away at some point if I reboot...but at the moment I
don't want to reboot.
So, the question is where is this information kept and not to clear the
bogus entry. I did log out and log in...no help.
13 years
Split up juk and dragon player in kdemultimedia
by Rahul Sundaram
Hi
For the purposes of a Fedora Remix that includes KDE by default, I
would like to split up juk and dragon player from kdemultimedia package
inorder to enable the remix to exclude these since alternatives are
preferred and included by default. Multiple apps for the same purpose
is redundant, clutters the menu and occupies space in the live image.
Would a spec file patch that resurrects dragon player as a individual
package be accepted? Should it be called kdemultimedia-dragonplayer and
kdemultimedia-juk instead? Let me know the current thoughts on this.
Rahul
13 years