@bitinerant,i was able to return mine for a full refund. i advise you
to do the same. my theory is that due to the architecture of the vostro
v13 and latitude 13, it will be a ***very*** long time, if ever that any
linux distro will support it. the synaptics touchpad is a child of a
broadcom
resolved
** Bug watch added: KDE Bug Tracking System #250263
http://bugs.kde.org/show_bug.cgi?id=250263
** Bug watch added: KDE Bug Tracking System #250263
http://bugs.kde.org/show_bug.cgi?id=250263
--
[maverick] Rekonq crashes without network connection.
resolved in kubuntu and upstream as well.
thanx :)
cheers
--
[maverick] Rekonq crashes without network connection.
https://bugs.launchpad.net/bugs/647332
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to rekonq in ubuntu.
--
kubuntu-bugs
Public bug reported:
Binary package hint: kdebase-workspace
the KDE SC4 plasma widgets pager and tasks (taskbar) have no
configuration capability to disable touchpad/mouse scroll events. see
upstream bug report for tasks at
https://bugs.kde.org/show_bug.cgi?id=198661
submitted here for
understood.
for those finding this bug report and wishing to add some input and/or
heat, please vote in either or both of the following bug reports
taskbar https://bugs.kde.org/show_bug.cgi?id=198661
pager https://bugs.kde.org/show_bug.cgi?id=252585
cheers
** Bug watch added: KDE Bug Tracking
i see it listed in ubuntu-desktop 1.206.
will this eventually get included in kubuntu-desktop (1.203 as of
today), or is additional action required?
not sure if needed in other *buntu meta packages
thanks,
cheers
--
source NEW ubuntu-extras-keyring and upload new ubuntu-meta
** Attachment added: rekonq-20100924.kcrash
https://bugs.launchpad.net/bugs/647332/+attachment/1633902/+files/rekonq-20100924.kcrash
--
[maverick] Rekonq crashes without network connection.
https://bugs.launchpad.net/bugs/647332
You received this bug notification because you are a member
Public bug reported:
Binary package hint: rekonq
rekonq (0.6.0) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
Operating System: Linux 2.6.35-22-generic x86_64
Distribution: Ubuntu maverick (development branch)
- What I was doing when the application crashed:
attempted to use rekonq to view
daniel,
updated today and the double-click behavior is corrected in
kpackagekit_0.6.1+svn1176533-0ubuntu2_amd64
thanx :)
cheers
** Changed in: kpackagekit (Ubuntu)
Status: New = Fix Released
--
[Maverick] kpackagekit ui not working with double-click
updated today, and the signal strength indicator is now working.
thanx :)
cheers
** Changed in: plasma-widget-networkmanagement (Ubuntu)
Status: New = Fix Released
--
[maverick] plasma-widget-networkmanagment signal strength indicator inop with
bcmwl
*** This bug is a duplicate of bug 629753 ***
https://bugs.launchpad.net/bugs/629753
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/645563/+attachment/1624430/+files/Dependencies.txt
** Attachment added: ProcMaps.txt
Public bug reported:
Binary package hint: kpackagekit
# dpkg -l | grep kpackagekit
ii kpackagekit 0.6.1+svn1176533-0ubuntu1
KDE package management tool using PackageKit
# lsb_release -rd
Description:Ubuntu maverick (development branch)
** Attachment added: kpackagekit ui
https://bugs.launchpad.net/bugs/645638/+attachment/1624903/+files/kpackagekit.png
--
[Maverick] kpackagekit ui not working with double-click
https://bugs.launchpad.net/bugs/645638
You received this bug notification because you are a member of Kubuntu
** Attachment added: kpackagekit help error
https://bugs.launchpad.net/ubuntu/+source/kpackagekit/+bug/645638/+attachment/1624914/+files/kpackagekit-help.png
--
[Maverick] kpackagekit ui not working with double-click
https://bugs.launchpad.net/bugs/645638
You received this bug notification
** Tags added: amd64
--
printer-applet.py crashed with KeyError in get_notifications()
https://bugs.launchpad.net/bugs/629753
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdeutils in ubuntu.
--
kubuntu-bugs mailing list
Public bug reported:
Binary package hint: plasma-widget-networkmanagement
signal strength indicator not working, yet iwlist shows proper signal
strength. using broadcom sta driver
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu maverick (development
** Attachment added: plasma-widget-networkmanager-signal-strength.png
https://bugs.launchpad.net/bugs/645664/+attachment/1625010/+files/plasma-widget-networkmanager-signal-strength.png
--
[maverick] plasma-widget-networkmanagment signal strength indicator inop with
bcmwl
lspci excerpt
Network controller: Broadcom Corporation BCM4313 802.11b/g LP-PHY (rev
01)
--
[maverick] plasma-widget-networkmanagment signal strength indicator inop with
bcmwl
https://bugs.launchpad.net/bugs/645664
You received this bug notification because you are a member of Ubuntu
Bugs,
same issue after installation. if we can't get the fix incorporated
into the release, could we at least get instructions for adding the repo
and key on the home page of http://extras.ubuntu.com ?
--
Maverick: Installing Extras from livecd fails to import gpg pubkey
andy,
i can confirm this issue on kubuntu 10.04 amd64, running on a compaq cq62.
AMD Athlon(tm) II P320 Dual-Core Processor
Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010
x86_64 GNU/Linux
i've tracked it down to the default settings in powerdevil, the kde
power managment
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: xserver-xorg-input-synaptics
a few related bugs: 1, 611992, 556019, 483121, 380126, 191024, many,
many more, unassigned, undecided, unassigned...
synopsis: bug #1 has much to do with hardware oem's
excellent :) thanks much
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Fri, 21 Sep 2007 02:04:41 +
Subject: [Bug 42553] Re: wacom input devices enabled by default, why?
I've gone ahead and committed a change to disable the loading of wacom
input devices by default for Gutsy.
same issue in feisty herd 4. must we punish the masses whilst we work
out the wacom stuff? not only is it cluttering up local log files, but
it's also cluttering up other bug reports, forums and google searches
with lines such as
X Error: BadDevice, invalid or uninitialized input device 167
23 matches
Mail list logo
