Still affected in upstream :(
Too bad it didn't make it into maverick. Any chance of going for upstream soon?
--
alt + backspace; alt+d etc. don't work anymore
https://bugs.launchpad.net/bugs/619754
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This affects me on a Dell Inspiron 13z. I will try to test/debug if this
exists in current Alpha3, but I am not sure how to test this thoroughly.
Any hints?
--
Bluetooth not discovered on Dell Inspiron 9400
https://bugs.launchpad.net/bugs/37288
You received this bug notification because you are a
Sorry, I forgot where my Firefox version is coming from.
I am using the "ppa:mozillateam/firefox-stable" ppa-repository.
--
tabs are not clickable sometimes, and firefox-bin needs to be killed when
exiting after this happens
https://bugs.launchpad.net/bugs/522727
You received this bug notificati
Okay, it is the following (background: I activated that I'm being asked
before accepting any cookies)
No chrome package registered for
chrome://cookie/content/cookieAcceptDialog.xul
--
tabs are not clickable sometimes, and firefox-bin needs to be killed when
exiting after this happens
https://b
The bug appears to be profile-bound. Using a new profile, will not
trigger the bug, although safe-mode will.
--
tabs are not clickable sometimes, and firefox-bin needs to be killed when
exiting after this happens
https://bugs.launchpad.net/bugs/522727
You received this bug notification because y
uh, sorry. I use 3.6 from the firefox-3.5 package - should I run apport
again? :>
--
tabs are not clickable sometimes, and firefox-bin needs to be killed when
exiting after this happens
https://bugs.launchpad.net/bugs/522727
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/39852311/XsessionErrors.txt
** Changed in: firefox (Ubuntu)
Status: Incomplete => New
** Tags added: apport-collected
--
tabs are not clickable sometimes, and firefox-bin needs to be killed when
exiting after th
Architecture: amd64
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: firefox-3.6 (not installed)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
Uname: Linux 2.6.31-19-generic x86_64
UserGroups: adm admin cdrom di
Ignoring task https://api.edge.launchpad.net/beta/ubuntu/+source/firefox
because it is closed ;)
--
tabs are not clickable sometimes, and firefox-bin needs to be killed when
exiting after this happens
https://bugs.launchpad.net/bugs/522727
You received this bug notification because you are a mem
For a few days now, I'm having the exact same bug - even with addons disabled.
I am running Firefox in safe-mode right now, with my tabs still not-clickable.
(Firefox 3.6 (not 3.6.2), on amd64, karmic and linux-kernel 2.6.31-19)
Kris' steps to reproduce the bug work - although it occurred to me i
The point is: My network is using 172.16.3.1 - a debian box - for routing,
internet access etc.
But there was also a normal "home router" (at 172.16.3.10) provided by my ISP
connected to that debian box to provide wireless access at my home. This "home
router" was advertising kinda rogueish, so
"The mouse is a bit strange - it has two logical "interfaces" for the USB
receiver/transmitter. They are on the same plug, but they are treated as
separate devices by the Linux USB subsystem. The first USB interface is the
normal mouse device - it has the X/Y motion, the normal buttons and the
Okay, I did what you suggested Teej, but I am using the left-handed
version of MX610 (which should not and does not make a difference):
Here's what xev says:
left-button: ButtonPress event, serial 33, synthetic NO, window 0x621,
state 0x10, button 1, same_screen YES
right-button: ButtonP
Thanks Charles :)
--
transmission is using the wrong upnp device for portforwarding
https://bugs.launchpad.net/bugs/500153
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://
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37158553/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/37158554/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/37158555/ProcStatus.txt
** Attachm
Public bug reported:
Binary package hint: transmission
Transmission gladly reports that it enabled port forwarding via UPnP on
172.16.3.10, but (as it should know!) 172.16.3.10 is *not* my gateway and not
responsible for any port-forwarding regarding my internet connection.
A simple "route -n"
So here's the dilemma:
Either we enable it by default (like Windows 7 does, btw!) and take a few risks
(networks are harder to debug, difficulties with applications, etc.) or we
disable it and lessen privacy for end-users.
I'd prefer the second option, but only if we had a way of disabling it
*
this is in progress for far too long..
what's wrong?
--
conntrack error prevents cutter from working
https://bugs.launchpad.net/bugs/240147
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.ub
I agree with the previous posts.
@ Jérémy Subtil: Who is to decide between SRU and backport?
Is there a way to speed things up? :)
Thanks.
--
Current version is obsolete
https://bugs.launchpad.net/bugs/258803
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
re it is a
compatibility problem worth fixing.
Console output of cutter:
$ cutter
usage: cutter ip [ port [ ip [ port ] ] ]
$ sudo cutter 172.16.3.104
openning /proc/net/ip_conntrack: No such file or directory
Best regards,
Frederik "ChosenOne" Braun
P.S.: It is stated in the man page,
Hello,
I'll directly start:
~# ls -l /usr/lib/libcups*
ls: cannot access /usr/lib/libcups.so.2: No such file or directory
Note the "cannot access". Also. see this result:
:~# ls -al /usr/lib/
ls: cannot access /usr/lib/libcups.so.2: No such file or directory
?? ? ?? ?
** Attachment added: "tarball of log files in /var/log/dist-upgrade/"
http://launchpadlibrarian.net/14452613/update.tar
--
upgrade from dapper to hardy fails
https://bugs.launchpad.net/bugs/229304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: update-manager
Upgrade during the upgrade-process and after having successfully upgraded a few
packages.
Details as follow:
Could not install the upgrades
The upgrade aborts now. Your system could be in an unusable state. A
recovery will run now (dpkg
23 matches
Mail list logo
