Public bug reported:
Binary package hint: dolphin
Description:
When hovering the mouse over a FIFO, dolphin stops responding until I kill it
manually.
Steps to reproduce:
1) mkfifo THEFIFO
2) open Dolphin
3) hover mouse over THEFIFO
What I expected to happen:
Dolphin shows some basic informati
** Attachment added: "last 10 lines of strace dolphin --nofork"
http://launchpadlibrarian.net/17059396/dolphin_fifo.strace.txt
--
kde 4.1 dolphin hangs when hovering mouse over a fifo/pipe
https://bugs.launchpad.net/bugs/261106
You received this bug notification because you are a member of Ub
Done. See: https://bugs.kde.org/show_bug.cgi?id=169786
--
kde 4.1 dolphin hangs when hovering mouse over a fifo/pipe
https://bugs.launchpad.net/bugs/261106
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I can confirm this report. Neither FN+F1 nor the "kill-switch" works. In
Windows, pressing either of them starts a 3rd party tool that allows me to
disable/enable WiFi and Bluetooth.
However, I don't think this is a bug. This notebook simply isn't supported (and
may even never get to that point,
Yet another "me too", this time the error seems related to the graphics-
controller:
Nov 2 13:36:21 box kernel: [ 8055.273097] ACPI: EC: missing confirmations,
switch off interrupt mode.
Nov 2 13:36:21 box kernel: [ 8055.793155] ACPI Exception (evregion-0419):
AE_TIME, Returned by Handler for
I can confirm this behaviour. If gnome-power-manager is started while
the battery is not plugged in, then the "On Battery Power" tab never
appears. However, G-P-M does seem to recognize the battery as the status
icon is updated and the battery-related options now appear in the
context menu. See g-p
** Attachment added: "Starting g-p-m with attached battery"
http://launchpadlibrarian.net/19512254/g-p-m_bat.txt
--
No "On Battery Power" tab after inserting battery
https://bugs.launchpad.net/bugs/250172
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Error: "org.freedesktop.DBus.Error.UnknownMethod: Method "CreateDevice" with
signature "s" on interface "org.bluez.input.Manager" doesn't exist"
probably means that you haven't installed the bluez-input package.
This has fixed it for me:
quit kbluetooth4
sudo apt-get install bluez-input
sudo inv
Setting package to kdebluetooth although gnome-bluetooth seems to be
affected too (confirmation needed)
** Changed in: kdebluetooth (Ubuntu)
Sourcepackagename: None => kdebluetooth
--
kbluetooth4 fails to add mouse
https://bugs.launchpad.net/bugs/268383
You received this bug notification becaus
I'm sorry that the information provided so far ist too thin.
It seems that, if the print-job's media size differs from the printer's default
media-size, rastertoqpdl segfaults.
My printer is set to A4 media, while all KDE programs use "Letter" by default.
This probably has caused the crashes I o
I've installed the LSB package; unfortunately, nothing has changed. Printing in
Letter format causes a segfault while A4 produces a black page.
I've repeated the steps described in my last post and attached the results.
** Attachment added: "bug267903-splix_lsb.tar.gz"
http://launchpadlibra
The supplied version of pdftoraster solves both problems: no black pages and
rastertoqpdl doesn't crash. Thank you.
And sorry for getting you on the wrong track with rastertoqpdl.
--
rastertoqpdl segfaults or produces black printouts
https://bugs.launchpad.net/bugs/267903
You received this bug n
The bluez-input packge is now recommended by bluez-utils (as of version
3.36-1ubuntu2).
If no PIN is entered in the authentication dialog, the following warning still
appears:
BTWizard::createBonding: Error: "org.bluez.Error.AuthenticationRejected:
Authentication Rejected"
Despite the warning,
I've created a small patch that hopefully fixes this.
It uses readlink to overcome the problem of custom names in hdparm.conf.
** Attachment added: "acpi-support_dont_overwrite_hdparm.diff"
http://launchpadlibrarian.net/21960794/acpi-support_dont_overwrite_hdparm.diff
--
acpi-support's 90-h
This patch tries to make sure that /etc/acpi/*.d/90-hdparm.sh does not
overwrite settings made by laptop-mode-tools or hdparm. Each harddisk is
checked individually; APM settings are only applied if the drive is
neither controlled by /etc/laptop-mode/laptop-mode.conf nor by a
matching section in /e
Thanks for your quick response. You are right, there might be spaces at the
start of the line and before the curly brace, so I changed the regex to:
'^[[:space:]]*/dev[-_/[:alnum:]]*[-_[:alnum:]]+[[:space:]]+{'
I also fixed the return-values and that _very_ stupid "echo $HDPARM" error...
Sorry :
I wrote the patch because my laptop hard drive was heating up to about
50°C because acpi-support disables the disk's APM while the laptop is on
AC power.
I think if the user explicitly sets a value in /etc/hdparm.conf, acpi-support
should not overwrite this setting, even if the power state change
The SKB allocation failures can be triggered fairly reliably in 2.6.27-2.3 by
causing some network traffic (using e.g. iperf) and writing data to my USB
harddrive (using dd). Running just iperf or dd is fine. However, as soon as I
run both at the same time, I get a lot of "iwlagn: Can not alloca
Public bug reported:
Binary package hint: splix
Whenever I try to print anything on my Samsung ML-2510 the printout is either
completely black or the printer doesn't print at all and the following messages
appear in /var/log/cups/error_log:
E [08/Sep/2008:21:39:46 +0200] PID 14178 (/usr/lib/cup
** Attachment added: "apport crash file"
http://launchpadlibrarian.net/17436454/_usr_lib_cups_filter_rastertoqpdl.7.crash
--
rastertoqpdl segfaults
https://bugs.launchpad.net/bugs/267903
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Controling the birghtness with FN + F8 and FN + F9 is working again in
Intrepid using the 2.6.27-2.3 kernel. However, FN + F8 still produces
unknown keycodes; a minor annoyance.
Output of showkey -s:
FN + F8: no output
FN + F9: 0xe0 0x6f 0xe0 0xef
Xev output:
FN + F8: no output
FN + F9: 120 NoSym
Public bug reported:
Binary package hint: udev
Various non-standard extra keys of my Samsung N220 (model:
NP-N220-JA03DE) don't work in Lucid (and most likely older releases as
well). I followed the steps in /usr/share/doc/udev/README.keymap.txt.gz:
1. Find the keyboard device.
r...@n220:~# /lib
** Attachment added: "orig-map.txt"
http://launchpadlibrarian.net/42895168/orig-map.txt
--
Samsung N220 hotkeys don't work
https://bugs.launchpad.net/bugs/554066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "udev-db.txt"
http://launchpadlibrarian.net/42895294/udev-db.txt
--
Samsung N220 hotkeys don't work
https://bugs.launchpad.net/bugs/554066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Attachment added: "udev_rules_patch.tgz"
http://launchpadlibrarian.net/42895393/udev_rules_patch.tgz
--
Samsung N220 hotkeys don't work
https://bugs.launchpad.net/bugs/554066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
25 matches
Mail list logo
