apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940430/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
apport information
** Attachment added: xkbcomp.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940431/+files/xkbcomp.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
Chase: thanks for looking into this again. I also had to explicitely
configure the Wacom device in the Gimp. One would also do so in a real
use case, for the pressure sensitivity.
Your guess about where the bug could be sounds reasonable. Let me know
if there is anything I can help you with.
--
Chase: I'm running cellwriter. I will try to disable it and see what
happens.
My girlfriend has a different Wacom tablet, so I will see if I can
reproduce this with her hardware, too. I will also try a live-usb
(+utouch ppas). I'll post my results here when I've gotten round to it.
One more
Here's an xinput test recording. What strikes me as odd is that there
are motion events with only an a[0] coordinate, and no a[1] coordinate.
This seems related.
As far as I can interpret the wacom-pen2.record, it also seems odd that
an x-axis event is not always followed by a y-axis event, like
Hendrik, do you have any ideas as to where the problem may be? I can
imagine that the problem is over for you when it is not in evdev, but
for me it is not!:-)
As far as I can tell now, gdk_event_get_coords() returns garbage y
coordinates exactly when these events occur. Some layer between
Sorry Henrik for my miss-spelling your name. Thanks for your help, I'll
see what I can find out and report the bug elsewhere if needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736500
Title:
Thanks for having a look. I found out how to 'play' the recording. The
old recording indeed doesn't show the weird behaviour, but the attached
version does.
** Attachment added: wacom-pen2.record
https://bugs.launchpad.net/utouch/+bug/736500/+attachment/1930224/+files/wacom-pen2.record
--
Just one more comment: at first I thought that it could be due to
Xournal, because it has some weird event handling trying to work around
xinput shortcomings. But I can also reproduce in the Gimp.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
James: thanks for taking the time to report the stability issues you're
experiencing. Could you please report them at #730215, or click the
'affects me too' button, there. You can also subscribe to that bug to
watch its progress.
This bugreport is just about the firmware symlinks, and will
Here's the requested evemu properties and recording.
** Attachment added: wacom-pen.prop
https://bugs.launchpad.net/utouch/+bug/736500/+attachment/1921144/+files/wacom-pen.prop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: wacom-pen.record
https://bugs.launchpad.net/utouch/+bug/736500/+attachment/1921145/+files/wacom-pen.record
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736500
Title:
very
Thanks for confirming, Mohegan. I'm setting the status to 'confirmed'.
** Changed in: linux-firmware (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728746
Mohegan: you should probably file a new bug for your stability issues.
File it against the 'linux' package. You could include the output of
lspci and dmesg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: linux-firmware
The brcm80211 module needs the contents of the firmware files
/lib/firmware/brcm/bcm43xx-0-610-809-0.fw
/lib/firmware/brcm/bcm43xx_hdr-0-610-809-0.fw
which are currently packaged in linux-firmware. But the module needs
these symlinks to
** Bug watch added: GNOME Bug Tracker #638462
https://bugzilla.gnome.org/show_bug.cgi?id=638462
** Also affects: libgnomecanvas via
https://bugzilla.gnome.org/show_bug.cgi?id=638462
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Here's an even easier fix: as far as I can tell (by looking at a small
sample of the render() methods), the anti-aliased version of GnomeCanvas
does not need the items to be realized at all. Please test the new
attached patch instead of my earlier try. I haven't run into any trouble
with it when
** Patch added: no-realize-if-aa.patch
https://bugs.launchpad.net/ubuntu/+source/libgnomecanvas/+bug/657783/+attachment/1780592/+files/no-realize-if-aa.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: A patch that unrealizes any invisible elements, in order to
free the gdk gc's.
https://bugs.launchpad.net/ubuntu/+source/libgnomecanvas/+bug/657783/+attachment/1775524/+files/gnome-canvas-do-not-map-invisible-items.patch
--
You received this bug notification because you are
I am pretty sure the problem lies in Gnome Canvas. It allocates a gdk
graphics context for every stroke, even when they are not visible. The
attached patch to libgnomecanvas alleviates this problem: xournal will
still be (very) slow in continuous page mode, but not in single-page
mode.
I am not
This is working right now with the wacom-dkms package in ppa:utouch-
team/utouch. It does require removing the xserver-xorg-input-wacom
package. However, stylus input continuous to work as well.
It is not yet usable because gesturetest always shows two-finger events,
even when touching lightly
I tried to compile Anjuta 2.32 myself. It turns out that Anjuta depends
on libgda-4.0 = 4.1.6, which is an unstable version. Maverick ships
with the stable version 4.0.9. This is probably the explanation. Still,
I would like the new Anjuta version to be included in Maverick.
--
[needs-packaging]
I have the same bug on a HP TouchSmart tm2, with the added bonus that
the backlight problems also happen at startup every now and then.
The easiest way I have found to trigger this situation is to set
brightness to 0 on a terminal (as root)
echo 0 /sys/class/backlight/acpi_video0/brightness
Thanks Tob, your patch fixed the touchpad buttons for me.
--
Synaptics Clickpad touchpad buttons are not working
https://bugs.launchpad.net/bugs/582809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this problem, both in the current maverick
2.6.35-22-generic kernel and in the corresponding mainline
2.6.35-02063507-generic kernel. In both these kernels,
xinput test 16
(where 16 is the id of the HP WMI hotkeys device) is silent.
In the mainline kernel 2.6.36-020636rc6-generic,
Fixed in today's packages (2.31.92-0ubuntu1); marked as such.
** Changed in: eog (Ubuntu)
Status: New = Fix Committed
--
eye of gnome hangs when opening in gimp
https://bugs.launchpad.net/bugs/639836
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I run into the same problem. LyX (and a web browser) are pretty much all
I need on a computer, and this is stopping me right now from using unity
on a daily basis.
Given that LyX uses qt widgets, I thought I'd also check other programs
that depend on libqtgui4. However, the menus in VLC and in
One thing I can think of which may be causing this problem is that LyX
constantly updates the menu items based on the current document view.
The menu Navigate contains entries and submenus for all chapters in
the current document.
--
Lyx and Adobe Reader menus are unreadable under Unity
Just one more message: LyX gives this message in debug output:
QVariantMap DBusMenuExporterDBus::GetProperties(int, const
QStringList): Condition failed: action
which is clearly related. This message does not appear in a gnome
session. It appears right after the message
GuiView.cpp(519):
Public bug reported:
Binary package hint: eog
When I open a file with Eye of Gnome and then use the shortcut Image -
Open with with - (gimp or inkscape), the Eye of Gnome window becomes
unresponsive and must be terminated using system monitor. It stays
unresponsive even when the spawned
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/639836/+attachment/1589992/+files/Dependencies.txt
** Attachment added: ProcMaps.txt
https://bugs.launchpad.net/bugs/639836/+attachment/1589993/+files/ProcMaps.txt
** Attachment added: ProcStatus.txt
For me, the bug was fixed by installing the drivers from ralink,
available at:
http://www.ralinktech.com/support.php?s=2
(mine are RT2860PCI/mPCI/CB/PCIe(RT2760/RT2790/RT2860/RT2890, version
2.3.0.0 of 01/29/2010)
Install instructions for who needs them, for the rt2860:
* unpack the files,
*** This bug is a duplicate of bug 543035 ***
https://bugs.launchpad.net/bugs/543035
I am experiencing this bug both in Firefox and Google Chrome. So it
seems to be due to the flash player. As such, I marked it as a duplicate
of https://bugs.launchpad.net/ubuntu/+source/flashplugin-
The bug affects me too, on EEE PC 1000HE running ubuntu karmic, on
university of amsterdam's eduroam.
I tried following KILinux's instructions for compiling wpasupplicant
(version 0.6.9 is included with karmic) against the GnuTLS library.
Build install succeeded. However, after a restart, the
Here is a pdf file that renders correctly in Okular and not in Evince
(2.28.1): it gives a blank page except for some bullets and headers.
** Attachment added: OER_B_BSc_Nsk_0910.pdf
http://launchpadlibrarian.net/36350404/OER_B_BSc_Nsk_0910.pdf
--
pdf files appears blank - were OK in Adobe
101 - 135 of 135 matches
Mail list logo
