Bug#499344: Wrong cursor when oxygencursors are installed

2010-08-08 Thread Magnus Holmgren
have to provide all their cursors under the new names as well. That would also work around the swapped resize cursors bug 548804. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.

Bug#499344: reassign 499344 to crystalcursors

2010-08-08 Thread Magnus Holmgren
On söndagen den 8 augusti 2010, you stated the following: > KDE only tells X the paths where to look for cursors Also reported at https://bugs.kde.org/show_bug.cgi?id=213615, with a perhaps better analysis. I still don't think it's a bug in any cursor package; maybe in Qt? -- Ma

Bug#548804: crystalcursors: the corner resize cursors are swapped

2010-08-21 Thread Magnus Holmgren
reassign 548804 kdebase-workspace forwarded 548804 https://bugs.kde.org/248599 tags 548804 + upstream patch thanks On söndagen den 8 augusti 2010, Magnus Holmgren wrote: > Basically all the cursor packages except oxygencursors display the same > bug. It appears that it has to do with th

Bug#499344: reassign 499344 to crystalcursors

2010-08-21 Thread Magnus Holmgren
pt that Qt could have used standard X11 cursor names when running under X11). Perhaps lower the alternatives priority for oxygencursors so that if the administrator installs additional themes besides Oxygen, one of them will be the default by default, so to speak? -- Magnus Holmgren

Bug#499344: Wrong cursor when oxygencursors are installed

2010-08-21 Thread Magnus Holmgren
On söndagen den 8 augusti 2010, Magnus Holmgren wrote: > Alternatively, or as a workaround, all cursor packages might have to > provide all their cursors under the new names as well. That would also > work around the swapped resize cursors bug 548804. It appears that, at least for the t

Bug#328362: pmk: postinst fails, missing depends?

2007-03-09 Thread Magnus Holmgren
found 328362 0.9.3s2-2.1 thanks I can reproduce this bug too. Apparently pmksetup segfaults after reading pmkcpu.dat. Version 0.10.1 seems to fix the bug. I can take maintainership of the package and upload the new version. -- Magnus Holmgren[EMAIL PROTECTED