I've built a KDesktop package (latest Kubuntu KDE sources with the patch
above applied). This is meant to be a temporary fix until KDE 3.5.4
arrives.
The package and instructions are located here:
http://www.kde-apps.org/content/show.php?content=42637
--
Screensaver does not work
The fix won't affect GNOME/XFce since it only modifies the KDE Hooks
which are contained only by the kscreensaver-xsavers package.
The fix doesn't modify the files in the /usr/share/gnome-
screensaver/themes/ directory. It only modifies the KDE Hooks located in
Isn't /usr/share/applnk/System/ScreenSavers/ a KDE-only directory?
--
kscreensaver-xsavers installed but screensavers from xscreensaver-gl missing
https://launchpad.net/bugs/49228
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: kdeartwork (Ubuntu)
Status: Unconfirmed = Confirmed
--
kscreensaver-xsavers installed but screensavers from xscreensaver-gl missing
https://launchpad.net/bugs/49228
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: kdeartwork (Ubuntu)
Status: Unconfirmed = Confirmed
--
kscreensaver-xsavers doesn't contain hooks for xscreensaver-data-extra
https://launchpad.net/bugs/48056
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
*** This bug is a duplicate of bug 51261 ***
** This bug has been marked a duplicate of bug 51261
Vim 7
--
Vim 7.0.037
https://launchpad.net/bugs/53379
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug 53379 has been marked a duplicate of this bug
--
Vim 7
https://launchpad.net/bugs/51261
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** This bug is no longer a duplicate of bug 51261
Vim 7
--
vim-gtk backport
https://launchpad.net/bugs/52539
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug watch added: KDE Bug Tracking System #51965
http://bugs.kde.org/show_bug.cgi?id=51965
** Also affects: kdenetwork (upstream) via
http://bugs.kde.org/show_bug.cgi?id=51965
Importance: Unknown
Status: Unknown
** Changed in: kdenetwork (Ubuntu)
Status: Unconfirmed =
Using the Input Actions instead of Global Shortcuts worked for me. This solved
the multimedia keys (stop, prev, next) problem in Amarok 2 (needs to be focused
for keys to work) and the PrintScreen problem with KSnapshot too.
For Amarok, I used the D-BUS calls: org.kde.amarok /Player
Any chance of pushing an official fix now? This issue looks pretty minor
at first, but considering the fact that it causes actual data loss due
to the system shutting down without any confirmation, I believe that
this should be considered of high importance. I've actually been hit by
this bug at
Attached is a patch for /etc/acpi/powerbtn.sh.
I've already tested this (single-user only) on my machine. Of course, I wasn't
able to do it without valuable help:
http://samwiseandthestereotypical.blogspot.com/2008/09/using-dbus-and-ksmserver-to-logout-and.html
*** This bug is a duplicate of bug 268734 ***
https://bugs.launchpad.net/bugs/268734
** This bug is no longer a duplicate of bug 321100
acpid steals powerbutton events from powerdevil
** This bug has been marked a duplicate of bug 268734
immediate shutdown after pressing shutdown button
*** This bug is a duplicate of bug 268734 ***
https://bugs.launchpad.net/bugs/268734
** This bug is no longer a duplicate of bug 321100
acpid steals powerbutton events from powerdevil
** This bug has been marked a duplicate of bug 268734
immediate shutdown after pressing shutdown button
*** This bug is a duplicate of bug 268734 ***
https://bugs.launchpad.net/bugs/268734
** This bug is no longer a duplicate of bug 321100
acpid steals powerbutton events from powerdevil
** This bug has been marked a duplicate of bug 268734
immediate shutdown after pressing shutdown button
*** This bug is a duplicate of bug 268734 ***
https://bugs.launchpad.net/bugs/268734
** This bug has been marked a duplicate of bug 268734
immediate shutdown after pressing shutdown button
--
acpid steals powerbutton events from powerdevil
https://bugs.launchpad.net/bugs/321100
You
*** This bug is a duplicate of bug 268734 ***
https://bugs.launchpad.net/bugs/268734
** This bug is no longer a duplicate of bug 321100
acpid steals powerbutton events from powerdevil
** This bug has been marked a duplicate of bug 268734
immediate shutdown after pressing shutdown button
*** This bug is a duplicate of bug 268734 ***
https://bugs.launchpad.net/bugs/268734
** This bug is no longer a duplicate of bug 321100
acpid steals powerbutton events from powerdevil
** This bug has been marked a duplicate of bug 268734
immediate shutdown after pressing shutdown button
Checking for a running kded is not enough because a running kded does
not guarantee that the PowerDevil service is actually running. Checking
if kded is running AND if the PowerDevil module is loaded should be the
way to go (this is actually the way klaptopdaemon was being checked for
by
Debian's CheckPolicy() essentially does the same thing as my patch (that
is, check for PowerDevil and not just for kded). Actually, it does even
more because it switches to the current non-root user first before using
qdbus to check for PowerDevil.
Anyway, you're right. The most sensible solution
Updated patch. /etc/acpi/powerbtn.sh now checks for powerdevil. Checking
for klaptopdaemon has been removed since it no longer exists in the
official repositories of Intrepid and later.
** Attachment added: acpi-powerbtn-kde4.patch
A workaround that worked for me is to totally disable screen powersaving
in PowerDevil and just use the display power management in System
Settings - Display - Power Control.
--
DPMS doesn't turn off the screen
https://bugs.launchpad.net/bugs/288318
You received this bug notification because you
A patched GPM is available from my PPA:
https://launchpad.net/~baudm/+archive/backports
The packages incorporate the original patch that I've posted here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this bug has something to do with the Battery widget. With the
Battery widget loaded in the System Tray, quitting plasma-desktop like
so:
$ kquitapp plasma-desktop
would make plasma-desktop crash. Attached is the backtrace (I currently don't
have the debug packages installed).
Even
I solved this problem by adding a gconf key, named
brightness_in_hardware (reminiscent of HAL), for setting whether or not
to use xrandr for stepping the brightness up/down. Please test my patch
(agaist gpm 2.30.1) and see if it works for you.
** Patch added: 14-brightness-in-hardware.patch
Here's the updated patch.
** Patch removed: 14-brightness-in-hardware.patch
http://launchpadlibrarian.net/52070036/14-brightness-in-hardware.patch
** Patch added: 14-brightness-in-hardware.patch
http://launchpadlibrarian.net/52071575/14-brightness-in-hardware.patch
--
Brightness controls
Patch updated:
- Honor brightness_in_hardware setting regardless of the backend used (xrandr,
HAL, or whatever future backend; for consistent behavior)
- Set default value of brightness_in_hardware to 'true' (most people would
probably set this to 'true' anyway)
** Patch added:
*** This bug is a duplicate of bug 383263 ***
https://bugs.launchpad.net/bugs/383263
** This bug has been marked a duplicate of bug 383263
Subwoofer don't mute/unmute on plugging external acoustics
--
Lenovo Y430 - headphone does not mute speaker
https://bugs.launchpad.net/bugs/583292
*** This bug is a duplicate of bug 383263 ***
https://bugs.launchpad.net/bugs/383263
** This bug has been marked a duplicate of bug 383263
Subwoofer don't mute/unmute on plugging external acoustics
--
Lenovo Y430 Laptop Subwoofer Bug
https://bugs.launchpad.net/bugs/578538
You received
Already fixed in ALSA upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2010-June/028682.html
The patch, which has been already merged upstream, can be readily applied to
the Ubuntu kernels. I've been using a similar patch since Karmic.
** Changed in: alsa-driver (Ubuntu)
I can confirm that the upstream fix actually solves the problem. I've been
using the patch since Lucid until now (Maverick).
Attached is my alsa-info.
** Attachment added: alsa-info.txt.hkbDl9TvVg
For Lucid users, attached is the patch rebased to Linux 2.6.32.
For Maverick users, the patch specified in my post #17 can be readily applied
to the 2.6.35 kernel.
@Jimz, the easiest way would be to obtain the source code for your
kernel, recompile just the snd-hda-codec-conexant.ko module with
For those who can't wait for an official kernel update containing the
fix, download this file, extract, run install.sh as root, then reboot.
This should work for both Lucid and Maverick users. Make sure that
linux-headers-* (for your kernel version) and build-essential are
installed.
**
Why not just backport the fix since this is already a confirmed upstream
issue and an upstream patch is already available?
--
Subwoofer don't mute/unmute on plugging external acoustics
https://bugs.launchpad.net/bugs/383263
You received this bug notification because you are a member of Ubuntu
This bug has been fixed upstream since 2.6.34-rc6 by this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3143751ff51a163b77f7efd389043e038f3e008e
I've rebuilt the i915 module in 2.6.32 with the patch above and the
brightness keys are working again as
35 matches
Mail list logo
