This one has been driving me mad for a while now too. It seems as though
Mick K's patch fixes the issue, so I am submitting this patch to see if
we can get it included for jaunty.
** Attachment added: "tsclient_0.150-1ubuntu6.debdiff"
http://launchpadlibrarian.net/23884366/tsclient_0.150-1ubunt
** Attachment added: "desktop-data-model_1.2.5-1ubuntu3.debdiff"
http://launchpadlibrarian.net/23893563/desktop-data-model_1.2.5-1ubuntu3.debdiff
** Changed in: desktop-data-model (Ubuntu)
Status: New => Confirmed
--
Rebuild for libempathy19 -> libempathy22 transition
https://bugs.la
Public bug reported:
Rebuild required for dependant NBS package libempathy19.
** Affects: desktop-data-model (Ubuntu)
Importance: Undecided
Status: Confirmed
--
Rebuild for libempathy19 -> libempathy22 transition
https://bugs.launchpad.net/bugs/343408
You received this bug notific
I have similar problem that i think may be related.
I can move the mouse pointer, but the local and remote pointers are
offset from each other. As i move my local mouse pointer off the bottom
of the vnc window, the remote pointer is still about 1/6th up the
screen.
I am on an Asus 901 with Jaunty
Ok i just force downgraded my xserver-xorg-input-synaptics package from
0.99.3-2ubuntu3 down to 0.15.2-0ubuntu7 and the problem appeared to be
fixed for me.
Can anyone else confirm the version of xserver-xorg-input-synaptics they
are running?
I am not sure if this is a different bug i have come a
Public bug reported:
Binary package hint: freemat
Rebuild required for dependant NBS package libsuitesparse-3.1.0.
** Affects: freemat (Ubuntu)
Importance: Undecided
Status: New
--
Rebuild for libsuitesparse-3.1.0 -> libsuitesparse-3.2.0
https://bugs.launchpad.net/bugs/343728
You
** Attachment added: "freemat_3.6+dfsg-5build1.debdiff"
http://launchpadlibrarian.net/23927420/freemat_3.6%2Bdfsg-5build1.debdiff
** Changed in: freemat (Ubuntu)
Status: New => Confirmed
--
Rebuild for libsuitesparse-3.1.0 -> libsuitesparse-3.2.0
https://bugs.launchpad.net/bugs/343728
The patch above is rubbish. Got the version numbers mixed up in the
changelog.
** Attachment added: "freemat_3.6+dfsg-5build1.debdiff"
http://launchpadlibrarian.net/23928266/freemat_3.6%2Bdfsg-5build1.debdiff
--
Rebuild for libsuitesparse-3.1.0 -> libsuitesparse-3.2.0
https://bugs.launchpad.n
Yeah that sounds like a good idea.
How do we do that?
--
Rebuild for libsuitesparse-3.1.0 -> libsuitesparse-3.2.0
https://bugs.launchpad.net/bugs/343728
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
This is fixed upstream in 1.0.19.
** Changed in: alsa-driver (Ubuntu)
Status: New => Fix Committed
--
Typo in /etc/modprobe.d/alsa-base.conf
https://bugs.launchpad.net/bugs/344213
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Public bug reported:
When trying to rebuild petsc i was getting link errors with
libhypre2.0.0.
After rebuilding hypre, petsc compiled ok. Checking upstream shows that
openmpi 1.3 causes the missing symbol problems and anything that depends
on it will need a rebuild.
** Affects: hypre (Ubuntu)
** Changed in: debian
Sourcepackagename: hypre => None
** Attachment added: "hypre_2.0.0.dfsg-7ubuntu1.debdiff"
http://launchpadlibrarian.net/24053068/hypre_2.0.0.dfsg-7ubuntu1.debdiff
** Changed in: hypre (Ubuntu)
Status: New => Confirmed
--
Rebuild required due to new openmpi 1.3 c
** Also affects: xfree86-driver-synaptics (Ubuntu)
Importance: Undecided
Status: New
--
vino: mouse cursor stays in upper left corner
https://bugs.launchpad.net/bugs/337926
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Thanks Daniel.
Stupid thing is I know that, but in this case forgot.
So I know you only change the maintainer field when doing a change to
the package for ubuntu. Do you mean I can drop the "changed maintainer
field" changelog entry in this case as well?
Also wasn't exactly sure how to link this
Public bug reported:
No change rebuild required for libsuitesparse-3.1.0 ->
libsuitesparse-3.2.0.
** Affects: petsc (Ubuntu)
Importance: Undecided
Status: New
--
Rebuild for libsuitesparse-3.1.0 -> libsuitesparse-3.2.0
https://bugs.launchpad.net/bugs/353086
You received this bug n
** Attachment added: "petsc_2.3.3-15ubuntu2.debdiff"
http://launchpadlibrarian.net/24628641/petsc_2.3.3-15ubuntu2.debdiff
** Changed in: petsc (Ubuntu)
Status: New => Confirmed
--
Rebuild for libsuitesparse-3.1.0 -> libsuitesparse-3.2.0
https://bugs.launchpad.net/bugs/353086
You recei
I have just been trying to rebuild octave3.0 for Jaunty in light of
libsuitesparse-3.1.0 -> libsuitesparse-3.2.0 and it FTBFS due to changes
in libsuitesparse.
Seen as libsuitesparse-3.1.0 is NBS something has to be done to
octave3.0 to get it to compile.
It looks like this issue has been address
I am wondering if we should do this sync for Jaunty.
I am looking at libdvdread3 as an NBS package and can see that ogmrip
needs to be rebuilt, but a simple rebuild isn't enough as it fails
trying to find libdvdread. There is a patch to build against libdvdread4
in 0.12.3-0.1 from debian-multimedi
Public bug reported:
Illuminator needs to be rebuilt for the libsuitesparse-3.1.0 ->
libsuitesparse-3.2.0 transition.
** Affects: illuminator (Ubuntu)
Importance: Undecided
Status: Confirmed
--
Rebuild required for libsuitesparse-3.1.0 -> libsuitesparse-3.2.0 transition.
https://b
** Attachment added: "illuminator_0.11.0-1build1.debdiff"
http://launchpadlibrarian.net/24749685/illuminator_0.11.0-1build1.debdiff
** Changed in: illuminator (Ubuntu)
Status: New => Confirmed
--
Rebuild required for libsuitesparse-3.1.0 -> libsuitesparse-3.2.0 transition.
https://bug
I can confirm that this is no longer an problem.
I use suspend and resume all the time in Karmic without issue.
I would recommend closing.
--
[ASUSTeK Computer INC. 901] suspend/resume failure [non-free: wl]
https://bugs.launchpad.net/bugs/439370
You received this bug notification because you ar
Public bug reported:
Suspended the machine by closing the lid.
The LED's indicated that it hadn't successfully suspended and when i
opened the lid there was no change. Screen was blank and the system was
unresponsive.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32747790/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32747791/BootDmesg.txt
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/32747792/Card0.Amixer.valu
23 matches
Mail list logo
