I'm having a weird problem (is there any other kind?)
I have a logitech mouse that bluedevil can see and successfully pair. I have
no trouble on any account.
But for some reason, I do not get my mouse to move until after I log into an
account. After I log into an account my mouse works just fine and bluedevil
reports that my mouse is paired and trusted.
When I'm on the kdm the mouse does not move.
When I try to run blutooth-wizard, the program does not see my mouse at all
I've tried googling the problem with no success. I can't help but feel that
I'm missing something very simple, but I'm stumped.
Any advice would be very welcome.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Well, partly, anyway. After the latest upgrade of Mozilla Firefox, PDF
files, loaded into a tab, will not print. Nothing comes out of the print
device except blank pages.
But if I download a PDF file, save it, open it with the Adobe Reader
application, and print from there, I get a readable printout, just as I
Where do I file the bug, and against what?
pam-kwallet brings to kde what gnome-keyring-pam is for gnome. It offers
the ability to automatically open your kwallet using your login password.
Builds are available in kde-testing repo, package review is at:
1. install pam-kwallet
2. set kwallet password to be the same as your login password
3. make sure kwallet is configured to *not* autoclose wallets under any
circumstances (pam-kwallet only functions once on initial login, it will not
reopen closed wallets)
4. configure pam accordingly. in short, add
-auth optional pam_kwallet.so
-session optional pam_kwallet.so
(near similar pam-gnome-keyring entries) in your loginmanager pam
configuration. I added these to /etc/pam.d/kdm for example, since I'm
Strange, can't see any changes between 4.11.9-2 and 4.11.9-4 touching
kwin code at all.
On 05/02/2014 01:49 PM, Peter Gueckel wrote:
> I updated to kde-workspace-4.11.9-4.fc20.1.kde413.x86_64 this morning,
> turned the computer off/on and logged in. Kwin crashed immediately. I logged
> out and got only a black screen and therewith, vt1 was hung. I logged in to
> vt2 and killed gdm, then back to vt1 and logged in again. I noticed that the
> active edges no longer worked and then saw that all of the desktop effects
> are disabled. I tried to enae and was told that there are 20 effects that
> have errors and the desktop effects cannot be enabled.
> Prior to this morning's updates, everything was fine.
On 05/01/2014 06:10 PM, Felix Miata wrote:
> I asked a bad question, but you might have done a better job correlating
> it to
> $SUBJECT. The subject is about required components unlikely ever to be
> used by
> other than laptop installations.
As far as I can tell,
* QtLocation is needed for GeoLocation support, probably want to keep that.
* QtSensors seems to be used to support something about screen
orientation and rotation. not sure of the use-case for including this
support, so could consider omitting this part I suppose.
Anyone want to argue for or against either of these qtwebkit features?
> As a single 3M package previously, I never
> noticed the existence of qt-mobility. Obviously the old qt-mobility version
> has been broken up into 15 separate rpms of which all are not mandatory,
> apparently means some wireless stuff previously mandatory is now optional,
> thus an improvement:
Indeed, that was the plan.
On 05/01/2014 05:52 AM, Felix Miata wrote:
> On 2014-05-01 05:17 (GMT-0500) Rex Dieter composed:
>> Felix Miata wrote:
>>> Is this wasteful new F21 dependency on Nokia intentional? Did I miss an
>>> announcement? Seems like an AYBABTU.
>> qtwebkit has used bits from qt-mobility (libQtLocation mostly) for a
>> very long time.
> What uses qtwebkit?
*Lots* of things
try for yourself,
repoquery --whatrequires qtwebkit
notable items in that list:
On 05/01/2014 01:54 AM, Felix Miata wrote:
> Is this wasteful new F21 dependency on Nokia intentional? Did I miss an
> announcement? Seems like an AYBABTU.
qtwebkit has used bits from qt-mobility (libQtLocation mostly) for a
very long time.
Is this wasteful new F21 dependency on Nokia intentional? Did I miss an announcement?
Seems like an AYBABTU.
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/