Any chances of getting this fixed before the LTS “support” ends?
I notice that quantal is already without this patch. So I wonder, was it
dropped because some other change made it unneccessary, or was it
dropped simply because it broke more than it fixed. If the latter, then
please drop the patch
Almost a year later, and two release cycles. I observe this problem on
ubuntu 13.10. I consider it a real papercut kind of problem, beacuse if
some new user accidentially hides the launcher, he might not know how to
get it back if he already closed the settings window.
--
You received this bug no
Public bug reported:
I'm trying to create an up-to-date chroot based on precise-updates.
Since I don't know how to include updates while using debootstrap (see
https://answers.launchpad.net/ubuntu/+source/debootstrap/+question/199330
on this), I have to install updates later on from within the chr
On 05.07.2012 23:35, Chase Douglas wrote:
> If you aren't receiving a TouchEnd event, then there is something wrong.
I am receiving the TouchEnd, but it doesn't update the core state the
way it should.
> The patch you are reverting is needed to fix a different bug. If you can
> reproduce the iss
Hi Cédric,
Although this took a little while longer, the amd packages have been
built successfully by now, and are available from my ppa.
I have the impression that your problems manifest in cases when some
application is listening to the higher level touch interfaces,
presumably using XInput. My
Cédric, I attached the patch, after copy & paste from gmane. But it
applies all right, at least to the xorg-server-1.12.1.902-1ubuntu1
currently in quantal. For precise, some adjustments are required.
I updated https://launchpad.net/~gagern/+archive/ppa to provide fixed
versions of the latest pack
** Patch added: "Suppress touch state for emulated ButtonPress (from c#19)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+attachment/3213240/+files/lp1015183e.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
With that patch by Chase, I also wonder what would happen if two touch
devices were used simultaneously.
When I both touch my screen and click my conventional mouse button, I
get two button events, but the state is the bitwise or of both, so the
second click will be "pressed button 1 while button
Hi Chase,
thank you for looking into this, and working towards a solution.
Is the patch you referenced intended as a replacement for both my
patches? Working with the touch screen alone, things work out fairly
well. But if I also use a mouse, then the lack of a TOUCH_END event
still causes the mo
As the core pointer button state appears to be exclusively maintained
inside the x server core, the evdev driver is blameless.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
OK, here are the two patches which I currently use to get a working core
pointer from my touch screen. I've included them in packages available
from https://launchpad.net/~gagern/+archive/ppa for precise and quantal,
so feel free to use those to give things a try.
--
You received this bug notific
** Patch added: "Fix state when replaying event history"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+attachment/3205762/+files/lp1015183d.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Patch added: "Reverse commit which removed TOUCH_END"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+attachment/3205761/+files/lp1015183c.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
One aspect of those patches, the removal of TOUCH_END events, breaks
emulated pointer core mouse event state for me. See bug #1015183 for
discussion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/97488
I have a patch for the second issue of the mouse state during replay.
Will attach it here shortly. I'm currently trying to get this to my PPA,
for quantal first and for precise afterwards.
Editing the change log, I found that the removal of the TOUCH_END is not
part of the orig tarball, but comes
OK, I believe I now have a good idea as to why the first ButtonPress in
xev has state 0x100. This appears to be due to an TouchOwnership event.
If ownership changes, such an event is inserted into the queue, so it
will always be processed after the BeginTouch event. I wonder how much
later it might
OK, I bvelieve I've identified the main problem here:
http://cgit.freedesktop.org/xorg/xserver/commit/?id=a986f2f30cbe2a00e72ded7315c4951d7703e549
http://anonscm.debian.org/gitweb/?p=pkg-xorg/xserver/xorg-server.git;a=commitdiff;h=96d8df5bc9d400d55830b23afe5525b222f8dfc7
Due to that commit, the E
Similar behaviour, but not entirely the same: I do receive press events.
The incorrect status is the same, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015183
Title:
Inconsistent mouse eve
** Tags added: touch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015183
Title:
Inconsistent mouse events for Acer T231H multitouch monitor
To manage notifications about this bug go to:
https://b
I had hoped that backing
http://cgit.freedesktop.org/xorg/xserver/commit/?id=634b0da9a83076d0e9e0fc44dc5dc77b0c368bc1
out of the xorg server core code base might be enough to solve this, but
if I do so, core events never have any buttons set in their state, so
that is not a solution. Nevertheless,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015183
Title:
Inconsistent mouse events for Acer T231H multitouch monitor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
Public bug reported:
I already submitted this at http://askubuntu.com/questions/153043/ but
decided to update to the latest development snapshot in order to give
that a try and write a proper bug report if the issue persists. It does
persist.
My setup is a quantal alpha 1, just upgraded from prec
** Also affects: dkms
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1014789
Title:
No valid dkms.conf in dkms_source_tree or dkms_binaries_only
To manage
Public bug reported:
It seems that the upstream-2.2.0.1 tag introduced a bug in the script
logic: it replaced these lines:
-if ! [ -d "$temp_dir_name/dkms_main_tree" ]; then
+if [[ ! $temp_dir_name/dkms_main_tree ]]; then
This changes a check for the existence of a certain directory with
Coming from the duplicate bug #950745: I lost both the glowing launcher
indicator and the entry in the alt+tab window list, contrary to most
comments above. Does that mean there are two more or less independent
bugs? Will you track that switcher aspect here as well?
--
You received this bug notif
One reboot later, I cannot reproduce this problem. So what did I do in my last
session?
* Install ccsm
* Reduce icon size in dock
* Drag terminal icon from dash to dock
* Install some recent updates, kernel I believe, maybe others as well
Not sure how any of these might influence the issue, but I'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950745
Title:
Terminal windows not listed in switcher
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug
Public bug reported:
It appears to me as if unity doesn't really see Terminal windows. The
Alt+Tab application switcher doesn't list them at all. And after I've
dragged the Terminal icon from the dash thingy to the dock, it still
isn't illuminated like other running applications are, althigh I hav
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950728
Title:
Wireshark install hangs, no details available
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/soft
Public bug reported:
Usually I'm a command line user, but today I decided to give the
software center in my newly installed ubuntu a chance. Selected
wireshark from the list and started installation. The progress tab
showed a nice progress bar next to it, which completed to about 85% or
so, and th
The new dsync functionality of dovecot 2 to sync servers makes it
particularly interesting for me. Really looking forward to a ubuntu
package, hopefully followed by a backport to LTS. Having ubuntu servers
with that feature would be great.
--
upgrade to latest stable version 2.0.6
https://bugs.la
If I had access to the pyqt repository (likely hg), I might try
bisecting this... Has anyone contacted pyqt people already?
--
qlog fails with a special combination of PyQt4 and Qt
https://bugs.launchpad.net/bugs/544928
You received this bug notification because you are a member of Ubuntu
Bugs, w
Sennaista, you might want to have a look at ~/.xsession-errors, see if
there is an error message in there that might be related to your
keyboard layout configuration.
--
"Error activating XKB configuration." - Requires manual xorg.conf editing
https://bugs.launchpad.net/bugs/67188
You received th
Fix committed but not released yet. Pre-release available at
http://alpha.gnu.org/gnu/wdiff/ and final release expected this month.
--
wdiff does not work correctly with <() redirection
https://bugs.launchpad.net/bugs/160912
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: trac-bzr
Status: Fix Committed => Fix Released
--
Does not work with bzr 1.6
https://bugs.launchpad.net/bugs/263300
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.ubun
Public bug reported:
Binary package hint: libdbi-perl
Seems that libdbi-perl suggests a package, dbishell, which exists only
for dapper and hardy. I suggest you adjust that dependency.
** Affects: libdbi-perl (Ubuntu)
Importance: Undecided
Status: New
--
libdbi-perl suggests obso
** Bug watch added: GNU Savannah Bug Tracker #25883
http://savannah.gnu.org/bugs/?25883
** Also affects: wdiff via
http://savannah.gnu.org/bugs/?25883
Importance: Unknown
Status: Unknown
--
wdiff does not work correctly with <() redirection
https://bugs.launchpad.net/bugs/160912
The _get_weave issue has been resolved for some time now, although not
as early as comment #8 suggests, but since http://bazaar.launchpad.net
/~trac-bzr-team/trac-bzr/trunk/revision/68
** Changed in: trac-bzr
Importance: Undecided => Medium
** Changed in: trac-bzr
Status: New => Fix Com
NicoInattendu wrote:
> I have the same issue on imac 24on karmic , with setting up a french
> keyboard.
> The problem apperas on karmic, noi problem on jaunty
Seems to be a bug in my fix: The french layout only has layout variants
"extended" and "nodeadkeys", not "basic", and as I defined "mac"
RedVivi schrieb:
> I encountered the same problem with my integrated MacBookPro keyboard.
What version of Ubuntu? Have you tried with Karmic?
Have you had a look at your ~/.xsession-errors file, to check whether
there are any messages there related to keyboard layout configuration?
--
"Error ac
I repeatedly asked for a new upstream release, without reply so far. References:
http://thread.gmane.org/gmane.editors.joe/503
https://sourceforge.net/projects/joe-editor/forums/forum/131147/topic/3445084
--
jmacs crashes with SIGSEGV when opening multiple files
https://bugs.launchpad.net/bugs/44
Jim Rorie wrote:
> Ok, If I understand this correctly, you are saying that the hal
> configuration file is only used for X. Gnome is controlled through
> gnome-settings-demon and most of the settings are changed through gconf
> or menu. You are not sure about KDE.
Correct.
> Synclient controls e
I'll try. The current docs describe how you should place a file in
/etc/hal/fdi/policy/ in order to enable tapping and two-finger scrolling
and such stuff. While this is still true for the initial settings of the
X server, once a user logs in, gnome-settings-daemon overwrites these
initial settings
Stupid me: it's the Gnome settings which disabled taps and stuff like
that. I just found out that with my fdi file in place, taps worked all
right in the gdm login screen, but failed once the session was started.
I found the corresponding settings in System / Settings / Mouse /
Touchpad.
So I take
Unfortunately the bcm5974-dkms PPA module is delivered as full text
source, not as a patch against some underlying kernel source. So when
comparing that file to the one in the current kernel, and as I don't
know the common ancestor, I don't know which modifications were
introduced in the kernel sin
Still an issue on current Karmic beta. There "Unredirect Fullscreen
Window" is disabled by default, and enabling it changes nothing.
--
gnome panel displayed running wine apps full screen with desktop effects enabled
https://bugs.launchpad.net/bugs/138508
You received this bug notification becaus
** Bug watch added: Gentoo Bugzilla #283508
http://bugs.gentoo.org/show_bug.cgi?id=283508
** Also affects: gentoo via
http://bugs.gentoo.org/show_bug.cgi?id=283508
Importance: Unknown
Status: Unknown
--
jmacs crashes with SIGSEGV when opening multiple files
https://bugs.launchpad
Doesn't work out of the box for me on current Karmic Beta, as Jim Rorie
claims. It used to work on Intrepid with some additional packages from
the Mactel Support PPA, but I deliberately dropped all PPA packages
after updating to Karmic, and even moved the fdi file I had created on
Intrepid. So my s
Same with Karmic on Apple MacBook Pro 5,1. And a LOT of dups out there.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/435877
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Bug #431807 in its current form doesn't help with the situation I'm
concerned with here. The errors I have in mind come from the xkbcomp
executable, and don't match the format of glib errors. I just updated to
Karmic Beta and made sure that the relevant lines are still missing from
the report. Matc
I came to this report here from bug #430705. I had the initial
impression that this thing here was intended to provide a solution for
that one. However, at least in its current form, it does not:
The errors I am concerned with are generated by the xkbcomp binary, and don't
match the glib pattern
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33120896/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/33120897/XsessionErrors.txt
--
jmacs crashes with SIGSEGV when opening multiple files
https://bugs.launchpad.net/bugs/444
Public bug reported:
Binary package hint: joe
$ jmacs foo bar
Processing '/etc/joe/jmacsrc'...Processing '/etc/joe/ftyperc'...done
done
Segmentation fault (core dumped)
According to gdb, the error occurs in main.c:434 which reads
p_goto_bol(bw->cursor);
One can easily see that bw in this case
So you say that an error message containing some technical information
is worse than one with almost no information at all? I'm sure I disagree
for myself, as I find an error message like 'No Symbols named
"mac_nodeadkeys" in the include file "macintosh_vndr/de"' (from bug
#327963) to be both under
The new one I opened requests that users be told to include their
.xsession-errors in bug reports, which is a first step. So if a user
encounters some xkbcomp error, and wants to report a bug about it, then
he will include a portion of that error log file, and the resulting bug
report will be more
I personally would wish for the error message to be displayed to the
user in a dialog window, not only logged in some obscure file. So my
original request hasn't been dealt with in full.
However, I believe that taking the lack of manpower into account, a
solution at the distro level is at the mome
apport would make sense, yes. Should I file another report for this, or
shall we mark this one here as affecting apport?
--
Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
https://bugs.launchpad.net/bugs/430705
You received this bug notification because you are a member o
I'll take the two months without reply from the ubuntu maintainers of
gnome-settings-daemon as a "No" to my question wherther they'd take it
from here. So I just filed a separate request, bug #430705, about
mentioning ~/.xsession-errors in the error message after a failed xkb
activation. Let's hope
OK, this patch does implement the request as outlined above.
I even adjusted the message files, except for the Azerbaijani (az) one,
as that uses different wording for the two existing lines, and I have no
clue why that's the case. Some other languages were changed from fixed
command strings to %s
Public bug reported:
Binary package hint: gnome-settings-daemon
As mentioned in bug #328980 comment #5, it would be a good idea to have
users include their ~/.xsession-errors when reporting errors with their
keybord konfiguration. This is because errors from xkbcomp end up in
that file. These wou
OK, now gladly disregarding VB and your external keyboard. My advice is to
1. change keyboard layout from "USA Mac" to "USA" and
2. change keyboard model from "Generic" to "Apple/MacBook/MacBook Pro".
Order is relevant if you want to avoid error messages in between.
If that works for you, then bug
Bryce, did you approach upsream, as your comment 5 indicates? What's
current status there? Do you have a URL for a bug report, mailing list
thread or similar? Recent comments on bug #67188 indicate that there is
still a lot of confustion caused by this bug here, so a fix would be
great, maybe even
So let me get this right: you're now working with a USB keyboard plugged into
your MacBook Pro?
Is it a Mac keyboard, or some other, more PCish keybord? If the latter, then
"Generic" is most definitely the way to go, I'd say.
When you claim that a Generic 102 keyboard was the "only way", have you
I hit bug #369158 with gqview as well, which has been duped here. I'm
using Jaunty on nvidia here. Could reproduce it with the latest gqview
CVS trunk as well. By the way, I guess the gqview fullscreen mode should
be much simpler to reproduce this issue and investigate the problem than
a full wine
spbrereton, if what you experience is in fact bug #327963, then I
believe that you should set the MODEL to something mac (e.g.
"macintosh_vndr/ch") and the LAYOUT to a variant not mentioning mac
(e.g. "de", not "de_mac").
The reason is that the layout files for mac models simply don't mention
any
> Can you try with the latest development release of Ubuntu? ISO CD
> images are available from http://cdimage.ubuntu.com/releases/karmic .
Tried to reproduce this with current up-to-date Intrepid, and failed. So
the issue seems to be fixed in the current stable release.
I couldn't try with the l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
raketenman wrote:
> Error:No Symbols named "de_mac" in the include file
> "macintosh_vndr/ch"
Same as my bug #327963, I guess.
You can either have a Macintosh Swiss keyboard model with a German
layout, or you can have a generic keyboard
Starting with Jaunty, people seeing this "Error activating XKB
configuration" dialog might have a look at the .xsession-errors file in
their home directory. Error messages from xkbcomp will end up there, and
others might as well. Maybe the information from these files can be used
to differentiate t
Starting with Jaunty, error messages from xkbcomp end up in ~/.xsession-
errors where they can be inspected by the technically inclined user.
This is probably due to the following change in gnome-settings-daemon:
http://git.gnome.org/cgit/gnome-settings-daemon/commit/?id=015e92a82c6bd19b4d3fcbcbe6
** Bug watch added: GNOME Bug Tracker #588607
http://bugzilla.gnome.org/show_bug.cgi?id=588607
** Also affects: gnome-settings-daemon via
http://bugzilla.gnome.org/show_bug.cgi?id=588607
Importance: Unknown
Status: Unknown
--
xkbcomp errors should be displayed
https://bugs.launch
Public bug reported:
Binary package hint: php-openid
php-openid-2.0.0 does not correctly deal with associations of type HMAC-
SHA256. The code only supports the generation of HMAC-SHA1 signatures,
but it fails to reject attempts at a HMAC-SHA256 connection with an
"unsupported-type" error code as
This is the hunk I already pasted above, plus its credit, this time as a
proper patch attachment so we won't have to worry about whitespace or
similar issues.
** Attachment added: "Changes for Content-Length"
http://launchpadlibrarian.net/27248332/lp381384.patch
--
mod_deflate with mod_fastcg
For those interested in mod_fastcgi development in general, or in the
greater context of the upstream fix, I'm attaching a diff between the
2.4.6 release and the SNAP-0811090952 snapshot source tree. I've written
to the fastcgi-developers mailing list, pointing at this issue here and
asking as to w
http://thread.gmane.org/gmane.comp.web.fastcgi.devel/2613 indicates
another approach towards a solution, and it seems that a variation of it
has been committed to some mod_fastcgi repository (though not the git at
http://repo.or.cz/w/mod_fastcgi.git). It's also available in a snapshot
dated 0811090
Public bug reported:
Binary package hint: libapache-mod-fastcgi
When compressing the content generated by mod_fastcgi, mod_deflate will
keep any Content-Length header created by the script, instead of
adjusting the header to match the compressed length.
References:
http://bugs.debian.org/cgi-bin
As I need trac on a Hardy LTS server, I just uploaded a fixed version of
the package to my PPA. I tried to use the Debian patch from comment 32,
but had to adjust it to include the -I flag to the compiler, no just the
include path without a flag. I attach the corresponding diff. It would
be really
valgrind helps:
Invalid read of size 4
at 0x5FC6A97: xf86WcmDevProc (xf86Wacom.c:1012)
by 0x808662E: ActivateDevice (devices.c:447)
by 0x8086731: InitAndStartDevices (devices.c:637)
by 0x807229E: main (main.c:370)
Address 0x4d261d8 is 56 bytes inside a block of size 108 free'd
at 0x
Making progress. Added a DebugLevel option with a value of 10 to the
wacom sections in xorg.conf. Also found out that the package xserver-
xorg-core-dbg containing the required Xorg debug symbols does exist, it
just isn't printed by dpkg -l. With those tools in place, the situation
looks like this:
Bug 357544 is probably the same, and came to the same (intermediate) conclusion.
Bug 361972 is probably the same as well.
--
Xorg crashed with SIGSEGV in ActivateDevice() - wacom tablet
https://bugs.launchpad.net/bugs/336401
You received this bug notification because you are a member of Ubuntu
Bu
Same here, after freshly upgrading from Intrepid to Jaunty RC, running
natively on hardware (no VM), wacom tablet configured in xorg.conf, but
not plugged in. Access via ssh possible. Reproducable.
Xorg.0.log contains those same lines as in the attached XorgLogOld.txt, except
for minor address of
OK, yet another debdiff. Revertet to -dbg packages (including a few
extra ones), dropped the lintian overrides, and also completed the
mapping from non-debug to debug packages, as the implicit cdbs build
logic didn't work as I originally expected. Currently queued in my ppa,
let's see...
** Attach
It took me a while to find the relevant documentation about pkg-create-dbgsym:
https://launchpad.net/pkg-create-dbgsym
https://wiki.ubuntu.com/AptElfDebugSymbols
https://launchpad.net/ubuntu/+spec/apt-get-debug-symbols
If this is really the way to go, some reference in
https://wiki.ubuntu.com/Pack
I created an updated patch for Jaunty. It failed to build on my PPA,
though, due to some PostgreSQL-related issue that seems unrelated to my
patch, but makes testing a bit difficult. I'll try a local build
tomorrow, I think. The attached patch introduces three new debug
packages, for qt4-dev-tools
> The resulting list of debug symbol files looks somewhat longer, needs
to be invedtigated still.
I've investigated this now. The original debug packages only contained
debug symbols for libraries. With my patch in place, it contains debug
symbols for binaries as well. Debug files for the followin
Do I understand you correctly that the diff in my PPA is enough for now,
rendering Marco's request for a patch obsolete?
So now I wait for some sponsor to have a look at this, and work out the next
steps based on his opinion?
The version against which my patch was created is no longer current. Sh
Can some Ubuntu qt packager please have a look at this?
I've put quite a lot of personal time, and even more computer runtime,
into trying to get this fixed. I've posted the relevant modifications as
well as instructions how to integrate them. I'm clobbering my PPA with
almost 1 GiB of packages fo
> could you describe a way to trigger the error?
I hit this in bug #327963. So a way to reproduce is this:
1. set keyboard layout to "Germany Macintosh, no dead keys"
2. set keyboard model to "MacBook / MacBook Pro (Intl)"
This might only work until someone fixes #327963, though. After that,
you
I just confirmed that the stderr of the xkbcomp invocation is redirected
to /dev/null, so error messages are indeed completely lost.
A fist step towards sensible error messages would probably be to
redirect stderr in libxklavier in such a way that it can be directed
into the syslog. This would inv
I have the feeling that this bug here might be a collection of several
distinct issues, which all look the same due to lack of precise error
messages. I filed bug #328980 asking for error messages to be displayed
to the user.
Until then, you might use the attached script to learn more about this
k
> Getting a better error message for the Gnome UI is a GNOME issue
obviously, not xkeyboard-config's duty, and really ought to be filed
separately against the appropriate GNOME component.
I agree, just filed bug #328980 for this. It's a bit tricky, as it
involves multiple packages.
> As to the se
Public bug reported:
Binary package hint: gnome-settings-daemon
When the user runs gnome-keyboard-properties and some of his settings
cause xkbcomp to fail, the user gets a general error message about
"Error activating XKB configuration" and some obscure hints as to where
the cause might lie. The
> both combinations don't fully match the key labels.
I guess I'll take that back. Having the left Alt key perform as AltGr as
it does in Mac OS X doesn't seem to make too much sense, as many
applications expect the existence of an Alt/Meta key to invoke commands.
The right Alt key works as AltGr
** Attachment added: "Screenshot of config and error"
http://launchpadlibrarian.net/22493771/xkberr.png
** Also affects: mactel-support
Importance: Undecided
Status: New
--
Error activating XKB configuration with MacBook keyboard model
https://bugs.launchpad.net/bugs/327963
You rec
Public bug reported:
Binary package hint: xkb-data
I've got Intrepid installed on a MacBookPro5,1 with German keyboard
layout. I started configuring the keyboads using gnome-keyboard-
properties as available from the settings menu. I first selected the
layout "Germany Macintosh, eliminate dead ke
*** This bug is a duplicate of bug 86685 ***
https://bugs.launchpad.net/bugs/86685
** This bug has been marked a duplicate of bug 86685
trac BROKEN on AMD64: "neo_cgi.so: undefined symbol: Py_InitModule4"
--
undefined symbol: Py_InitModule4
https://bugs.launchpad.net/bugs/320590
You recei
Public bug reported:
Binary package hint: python-clearsilver
python-clearsilver 0.10.4-1ubuntu1 from ubuntu hardy fails to load with
python 2.5.2:
$ python --version
Python 2.5.2
$ python -c "import neo_cgi"
Traceback (most recent call last):
File "", line 1, in
ImportError: /usr/lib/python2.
Complete list of my modifications:
* Modified debian/rules according to attached script.
* Added nostrip patch to debian patch series
* rm debian/*-dbg.install
* sed -i 's: \./\(.*\)\.debug: ./usr/lib/debug/\1:' debian/*-dbg.lintian
* Updated changelog :-)
I could have wrapped all this in a single
This patch can be added to the debian patch series in order to prevent
the qt build system from stripping objects.
** Attachment added: "nostrip.diff"
http://launchpadlibrarian.net/20842185/bug261380-nostrip.diff
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
Y
** Attachment added: "rules.diff"
http://launchpadlibrarian.net/20842168/bug261380-rules.diff
--
Packages have invalid .gnu_debuglink
https://bugs.launchpad.net/bugs/261380
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
I've got a proposed version in my PPA, with debug packages managed by dh_strip,
not the qt build process.
See https://launchpad.net/~gagern/+archive
Adding CONFIG+=nostrip to QMAKE_VARS in the configure script didn't
work, so I added it to some other spec file. I also found that cdbs
provides ela
1 - 100 of 169 matches
Mail list logo
