** Package changed: ubuntu => xinput (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682193
Title:
Mouse acceleration significantly reduced after upgrade to 17.04
To manage notifications ab
Public bug reported:
My external Logitech USB mouse was behaving nicely under 16.10 but after
upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are
set at the maximum acceleration, but it only affects the touch pad, the
mouse is extremely slow.
** Affects: ubuntu
Importance:
Hello Anthony,
I have the same problem as everyone else, and the new driver is not
working for me either...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1119842
Title:
[ASUSTeK COMPUTER INC. G75VX
Not relevant to me anymore. I would suggest closing it
Le vendredi 12 avril 2013 à 08:06 +, Ma Xiaojun a écrit :
> Is this still a problem? Since GTK+ already entered 3.0 era.
>
> ** Changed in: gtk+2.0 (Ubuntu)
>Status: New => Incomplete
>
--
You received this bug notification bec
great news for anyone following that post. I have upgraded the BIOS to
A08 and now wireless works as before.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
ubuntu 10.10 dell_laptop module disables wifi
https://bugs.launchpad.net/bugs/667441
You received this bug notification bec
--
ubuntu 10.10 dell_laptop module disables wifi
https://bugs.launchpad.net/bugs/667441
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
Public bug reported:
This is new to 10.10. In 10.04, wireless was working just fine.
I am reporting against dell_laptop because everything else works fine.
Wireless DOES work using wicd, even though nm-applet is reporting it disabled.
I can only assume it's not a problem with the broadcom drive
Well, I don't think the rfkill status is related to the driver. It is an
interaction with the
bios as far as I know...
But thanks for your input :)
De: "Cypher2"
À: "Daniel Cardin"
Envoyé: Mardi 12 Octobre 2010 09:31:30
Objet: Re: [Bug 644452] Re: Atheros
Why would I do that ? The driver works just fine. I have been using it
all day with wicd.
It's only the killswitch status that prevents network-manager from doing its
job. If there were
an option to diregard the status, it would work :)
De: "Cypher2"
À: "Daniel Cardin
I have a fresh install of 10.10 and I am experimenting the disabled wireless
problem as well.
But, on my Dell Vostro 1720, I cannot change the state of the rfkill using
unblock all. It remains blocked.
On the other hand, the wireless IS working as using wicd works just
fine, where NM fails.
su
I agree with Cos Costa. It hurts the perception. I have a bunch of
developers here that I'm trying to convince to switch to Ubuntu. The
ones who have made the switch are running Jaunty at the moment and I'll
have to "coach" them about this problem. It should work out of the box.
--
Buttons in Ecl
With kernel 2.6.31.14 #47 the patches to the dell-laptop module have been
committed and will probably fix the problem for many of you. I suggest you
remove module dell-laptop-dkms for those of you who have installed it, and try
upgrading to the new kernel.
Discussions about this are in bug 43080
Mario:
Thanks for the time you spent fixing this. It is very important IMHO
that dell is well supported at release time. It was a crippling bug
without a workaround. Good job!
--
[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill
switch
https://bugs.launchpad.net/bug
Mario:
Ok let's assume there is a BIOS bug. I would still have one last request
for you. I suggest we pick the lesser of two evils and always have the
driver respond the wireless is available. it _will_ cause problems if
Karmic is released with a default mode of operation which prevents users
from
Is it because nm-applet uses rfkill's underlying mechanism ? rfkill
reports
with switch on :
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Mario: What is different if I boot with the switch off then ? How does
nm-applet and the rest make it work ? What's different?
another way to put it, how was it working in hal in jaunty prior to v4 IIRC ?
There has to be something... Otherwise I wouldn't be online at the
moment through nm-applet
Yup... same thing.
Wireless Info:
Hardware switch supported
Hardware switch is Off
WiFi Locator not supported
Wireless Keyboard not supported
NVRAM Size: 256 bytes
NVRAM format version: 1
This is booting with the switch off, and then turning it on.
I wonder though why would the switch work perfectly if I boot in the off
position first.
The situation is as follows :
boot with switch in the off position:
-- wireless and bluetooth follow the switch state
boot with switch in the on position :
-- bluetooth follows the switch state
-- wifi'
Libsmbios version : 2.2.13
smbios-wireless-ctl version : 2.2.13
Wireless Info:
Hardware switch supported
Hardware switch is Off
WiFi Locator not supported
Wireless Keyboard not supported
NVRAM Size: 256 bytes
NVRAM format version: 1
Radio Status for
The dmesg outputs are done on kernel 2.6.31-13 #45 with dell-laptop-dkms
0.3
--
[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill
switch
https://bugs.launchpad.net/bugs/430809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "dmesg.on.atboot.v3"
http://launchpadlibrarian.net/33604831/dmesg.on.atboot.v3
--
[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill
switch
https://bugs.launchpad.net/bugs/430809
You received this bug notification because you are a member of U
** Attachment added: "dmesg.off.atboot.v3"
http://launchpadlibrarian.net/33604857/dmesg.off.atboot.v3
--
[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill
switch
https://bugs.launchpad.net/bugs/430809
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 430809 ***
https://bugs.launchpad.net/bugs/430809
follow bug 430809
** This bug has been marked a duplicate of bug 430809
[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling
kill switch
--
Dell Vostro 1720 wireless switch's state
I sent them to your gmail address... I am reluctant to pollute the bug
here. But if that's what you want, I will.
--
[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill
switch
https://bugs.launchpad.net/bugs/430809
You received this bug notification because you are a m
I closed my report because I am now following the development for the Karmic
branch.
You might want to have a look at bug 430809
--
"hal-system-smbios --st_wlan" reports rfkill switch always on, nm-applet always
disabled (wireless, dell laptops)
https://bugs.launchpad.net/bugs/394663
You receiv
Mario: I know this build was targetting Janne, but I tested it. Still
exhibits the same problem.
On another note, is the new build 2.6.31-13.45 really including the
lp430809v3 patch? I would assume so from the description, but I want to
make absolutely sure for the next tests.
--
[Dell Latitude
This it not yet working with Vostro 1720 either using #44+lp430809v3 +
dell-laptop-dkms 0.2
Mario, I can give you both dmesg outputs booting on or off if you want. But
what strikes me as the first difference
is that rfkill lists a device hci0 if booting with the switch in the on
position.
1: d
I have installed #lp430809v3 + DKMS v4 and I can feel it's getting
close... Now wireless works properly IF and only IF I boot with the
killswitch off. So this is progress for me, but it falls into the bug
441161 now.
When I boot with the killswitch on, the logic seems reversed meaning
that the swi
Dell Vostro 1720 with #lp430809v3 + DKMS v4. I can feel it's getting
close... Now wireless works properly IF and only IF I boot with the
killswitch off. So this is progress for me, but it falls into the bug
441161 now.
When I boot with the killswitch on, the logic seems reversed meaning
that the
latest kernel?
>
> uname -a should have "#44+lp430809v3" in it.
>
> On Sun, Oct 11, 2009 at 18:54, Daniel Cardin
> wrote:
>
> > I have a Dell Vostro 1720 with a BCM4322 running wl on kernel 2.6.31-13
> > and it still exhibits the problem.
> >
I have a Dell Vostro 1720 with a BCM4322 running wl on kernel 2.6.31-13
and it still exhibits the problem.
0: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: yes
2: hci0: Bluetooth
Soft
** Changed in: hal (Ubuntu)
Status: New => Incomplete
** Changed in: hal (Ubuntu)
Status: Incomplete => Invalid
--
New version (0.5.12~rc1+git20090403-0ubuntu3) breaks wireless (Broadcom wl
driver)
https://bugs.launchpad.net/bugs/390449
You received this bug notification because y
Public bug reported:
Binary package hint: hal
There have been many problems with the switch detection. But un Jaunty I
have been able to make wireless properly by not upgrading the hal
package, but since Karmic, network-manager cannot be used anymore.
This is a major problem, because I cannot se
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33409877/Dependencies.txt
--
Dell Vostro 1720 wireless switch's state incorrect
https://bugs.launchpad.net/bugs/448074
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Thanks Davide,
I have indeed done the same thing, going to 1.0.20.
I believe a backport would have been the good thing to do so current users who
do not know how to upgrade ALSA can still benefit from the fixes.
--
Headphone jack-sense not working with Intel Corporation 82801I (ICH9 Family) HD
Is there a workaround for Jaunty ? backport ?
--
Headphone jack-sense not working with Intel Corporation 82801I (ICH9 Family) HD
Audio Controller (rev 03)
https://bugs.launchpad.net/bugs/382836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I have tracked the source of the problem to bug #368553. So this bug can
be closed if 368553 is reverted to "in progress".
--
New version (0.5.12~rc1+git20090403-0ubuntu3) breaks wireless (Broadcom wl
driver)
https://bugs.launchpad.net/bugs/390449
You received this bug notification because you a
Gerhard,
I have submitted a bug report for the same problem you have encountered
and can also confirm the problem lies with the last update to hal.
You can force a specific version in synaptic using the ctrl-e key on the
specific package. It will provide you with a dropdown list of the two
availa
Public bug reported:
On Jaunty, fully updated:
After an upgrade to package hal was performed -- from
(0.5.12~rc1+git20090403-0ubuntu1) to (0.5.12~rc1+git20090403-0ubuntu3)
-- on my Dell Vostro 1720, wireless stopped working.
Symptoms: network manager reports wireless is disabled, shows no
networ
bump. this is still the case with Jaunty
--
Installation of the package breaks automatic version detection
https://bugs.launchpad.net/bugs/155852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
The new compiz update fixes the issue. Thanks!
** Changed in: compiz (Ubuntu)
Status: New => Fix Committed
** Changed in: compiz (Ubuntu)
Status: Fix Committed => Fix Released
--
maximized windows unresponsive [hardy]
https://bugs.launchpad.net/bugs/220278
You received this bug no
Definitely related to compiz. When I select no effects, things work
correctly.
--
maximized windows unresponsive [hardy]
https://bugs.launchpad.net/bugs/220278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
I am setup with an nvidia 8400m gs card, using the latest drivers
169.12, dual screen in separate X configurations.
In my primary desktop, if I maximize a window, it becomes unresponsive, mouse
and keyboard events are held back.
resuming the window size, the events are proce
It documents the option's format, not the actual process of locating the jvm
though.
that's what I'm looking for
--
Installation of the package breaks automatic version detection
https://bugs.launchpad.net/bugs/155852
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I am trying to find information about this but it's very scarce. I think
I will have to look at the actual source code for the launcher.
I can only tell you the actual "behavior" for now. If the directory has
the right name, java picks it up.
--
Installation of the package breaks automatic versi
why is it on incomplete ? I have uploaded the video.
If there are more questions, feel free to ask.
Thanks
--
Works in xine, but not in totem
https://bugs.launchpad.net/bugs/157864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I will try attaching the file. The video sync is not correct. It sort of
displays but not properly.
Sound is correct.
** Attachment added: "the problematic video file"
http://launchpadlibrarian.net/10205034/wake-up.wmv
--
Works in xine, but not in totem
https://bugs.launchpad.net/bugs/157864
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/10188001/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/10188002/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/10188003/ProcStatus.txt
--
Works
Public bug reported:
Binary package hint: totem
this is my first submission through totem, I hope there is some info attached.
but there is a wmv that plays in xine and not in totem, the video is distorted.
Should this be submitted?
ProblemType: Bug
Architecture: i386
Date: Sat Oct 27 15:31:08 2
Public bug reported:
the ubuntu packages for java install to /usr/lib/jvm using a pattern
like this :
java-6-sun (symlink)
java-6-sun-1.6.0.03
However, proper jvm detection is done using the pattern
jdkVERSION
jreVERSION
Second problem, the directory is named [...].0.03 where the convention
s
50 matches
Mail list logo
