no desktop effects with kdelibs-4.6.4-4/5
by Peter G.
The 2 updates of kdelibs today don't work with compositing.
This morning I updated and when I rebooted later on in the day, my desktop
froze up and not even keyboard responses worked. I had no option but to alt-
sysrq.
Then I booted again and updated and got a second kdelibs today, namely
kdelibs-4.6.4-5.fc15.x86_64. Again, the same problem (after reboot). Desktop
frozen, no recourse but alt-sysrq.
I booted into multi-user.target and manually edited kwinrc to disable
compositing. Again I rebooted, and now I have a working desktop, but without
desktop effects.
12 years, 10 months
Question regarding the cashew and allow widgets on screensaver
by Richard Sewill
I am on the latest Fedora 15.
I wanted to enable "Allow widgets on screen saver".
This choice is found in System Settings -> Display and Monitor -> Screen Saver
Everything looked fine when I enabled "Allow widgets on screen saver",
but ... when I have the screen saver locked, the cashew will let me select the
"Settings" button without asking for a password.
The Settings screen is hesitant to come up, but if I am persistent
and keep trying, the Settings screen will come up.
On the Settings screen, I am able to select the "Open" button.
This lets me browse directories as if I was going to change my wallpaper.
I can see the names of directories and files.
This can be done without entering a password.
Question please: if we must have the cashew on the screen saver screen,
when we "Allow widgets on screen saver", is there a way to require the cashew
to ask for a password before letting someone use the Settings button?
Alternatively, can I make the cashew disappear from the screen saver screen?
I installed kde-plasma-ihatethecashew-0.4-3.fc15.x86_64.
Unfortunately, "I Hate the Cashew" is not a widget choice when I am in the
screen saver screen trying to add widgets.
I'd like to use "allow widgets on screensaver", but am hesitant.
The screen saver, to me, "saves" wear and tear on the monitor -and-
keeps others from seeing my files and directories without permission.
It may be true, they can only see the file names, not the file contents.
Even so, I consider this to be a security risk.
12 years, 10 months
power applet - stays at 100%
by Genes MailLists
After all the latest updates - the power applet now shows 100%
(discharging)
even tho the time remaining is declining correctly ..
the info in /proc/acpi/battery/BAT0/* looks correct.
Anyone else seeing this?
12 years, 10 months
Re: Proposal: Too similar application names
by Vitezslav Humpa
Forwarded from test list.
----- Forwarded Message -----
From: "John Dulaney" <j_dulaney(a)live.com>
To: "Fedora QA" <test(a)lists.fedoraproject.org>
Sent: Sunday, June 5, 2011 8:28:45 PM
Subject: RE: Proposal: Too similar application names
> That all said, question remains on what to actually do on this. In a
> long term I'd suggest trying advocate that there is a appropriate
> solution based in the upstream, might it be pop-ups (sounds reasonable
> to do for all the desktop environments) or something based on how KDE
> does it. Although having upstream to do something is, like I said -
> long term. Thus let's decide on what to do about this now.
>
> I'd say that a number of cases this relates to is limited to a fairly
> small number. I am counting:
> - Software Update/Software Updates
> - System Monitor
> - Terminal
> - system-config-(e.g. date) vs. gnome control panel applets
> (and likely a few more).
>
> As a compromise between getting rid of the problem (user annoyance...)
> completely and the amount of work that would have to be done, I suggest
> that we simply target these applications and modify the desktop files
> so that they become distinguishable. That means in the menus and on the
> first sight, whatever *.desktop field is responsible for that in particular
> environments. Should we manage to push having a popup in Upstream, that
> would be great later on.
I agree, this is a good starting point. I don't really see the point of the popups,
but if other folks think they're necessary, I won't argue.
> Now, should we agree on this quickfix now, how to do that? Am I right
> that this would mean asking the maintainers of these cca 10 packages to
> change the *.desktop files in the packaging process? Do the *.desktop
> files come from upstream or are they made or at least modified already
> by Fedora? I suppose it would be better if they already get modified,
> as then the single extra edit would be less painful for maintainers.
> Still - sounds relatively painless.
In theory, the technical side should be a thirty second fix. The issue would
be deciding new names. Some things shouldn't be too difficult, such as
renaming Software Updates to Software Sources.
> We can also consider making a simple (e.g. targeting just default live
> installs) release criterion that would "force" such, though I'd think
> having it done on "voluntary" basis is more appropriate.
I wonder if this should be a QA test? It would help with improving the
end product for us to check things like this, but it is also fairly subjective
as to what constitutes as 'too similar.' I'm for it, but the aforementioned
subjective nature makes coming up with a clear release criteria difficult.
John.
--
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
12 years, 10 months
KDE 4.7 beta
by Martin Airs
Good day all,
Sorry if this is an FAQ somewhere else, but I couldn't find an answer on this
list.
I was just wonder if/when we can expect the 4.7 beta in the kde redhat repo's,
anytime soon?
Apparently the plasma clock will show calendar events in 4.7, fingers crossed
:)
Martin
12 years, 10 months
virtuoso-opensource
by Ed Greshko
I see a bunch of files of the type virtuoso_hX2085.ini in my /tmp
directory growing in numbers. Looks as they are created by
virtuoso-opensource. So, not knowing what it is I decided to try
erasing it and found that it is part of KDE.
So, what actually uses virtuoso-opensource? And, shouldn't it be nice
enough to clean up its trash?
12 years, 10 months
Cannot lock screen.
by Emmett Culley
It is no possible for me to lock my screen except using the following command: /usr/libexec/kde4/kscreenlocker --forcelock.
Selecting the Lock item from the "Leave" menu, or setting the display screen to time out and lock does not lock the screen.
Anybody else seeing this?
This all work in Fedora 14, and I believe it also worked when I first installed Fedora 15. I have a laptop that works perfectly and it was an upgrade via DVD, whereas the unlockable machine was a fresh install, then copied the .kde directory to the new partition.
Emmett
12 years, 10 months
2.6.35.13-92.fc14.i686.PAE is unusable for me
by Anne Wilson
Yesterday I booted into 2.6.35.13-92.fc14.i686.PAE, only to find that KWrite
won't launch and Dolphin opens with an empty grey window - yes, I saw this
once before. As before, System Monitor shows Disk Sleep and nothing I can do,
including killing everything connected with kwrite and dolphin, clears the
problem, so the system is unusable.
Happily I can still work in 2.6.35.13-91.fc14.i686.PAE
Anne
--
New to KDE Software? - get help from http://userbase.kde.org
12 years, 10 months
graphical representation of LAN
by Timothy Murphy
Can someone recommend a KDE application to draw up
a graphical representation of a small computer network,
preferably for viewing on the web?
Any suggestions gratefully received.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
12 years, 10 months
