The hardware I'm running Jaunty on is described a bit on the folowing wiki
pages.
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoVelocityMicroEdgeGx335
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoNvidia9800GTX+
The second link also describes the TwinView setup and t
Hi Scott,
I'm running the Jaunty release at the moment:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION="Ubuntu 9.04"
I'm not sure if it's feasible to run this testcase for this bug
from a live CD, as installing the nVidia restricted dri
Contents of /var/log/Xorg.0.log are attached.
There doesn't seem to be anything of interest in $HOME/.xsession-errors
** Attachment added: "Contents of /var/log/Xorg.0.log"
http://launchpadlibrarian.net/26470592/Xorg.0.log
--
Enhanced zoom not working with twinview enabled
https://bugs.launc
I can confirm that with TwinView enabled, Enhanced Zoom no longer works.
Attached a sample /etc/X11/xorg.conf showing TwinView configuration.
** Attachment added: "/etc/X11/xorg.conf showing simple TwinView configuration."
http://launchpadlibrarian.net/25989249/xorg.conf_sample
--
Enhanced zo
Public bug reported:
Binary package hint: nvidia-glx
I came across this when trying to ./configure mplayer with the
--enable-xvmc
flag to enable XvMC for nVidia, as described here:
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoNvidia5200
The mplayer configure script
./configu
I'm not sure why the launchpad system associated this
bug report with the 2.6.17 version of inux-restricted-modules.
I'm using 6.06 (Dapper Drake) with updates from the web, so
the actual package I'm using is:
linux-restricted-modules-2.6.15-26-686
Also included an attachment containing output of
Tested that this issue is fixed in Ubuntu 8.04 (Hardy Heron) (libpurple0
revision 1:2.4.1-1ubuntu2), so there's no longer any need to save the
password, for the pidgin logins over XMPP (Jabber) to work.
--
Pidgin does'nt connect to jabber servers (jabber plugin error)
https://bugs.launchpad.net/b
I can confirm that the patch posted by nicfagn works for digital optical output
(AC3 passthrough) too, see the "Audio" section of this page for details:
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoAppleiMac24
--
Sound doesn't work in Feisty on iMac 24
https://bugs.launchpad.net/bu
Public bug reported:
Binary package hint: linux-image-686
The v86d userspace utility executable is missing.
The v86d executable is needed by the uvesafb framebuffer VESA driver module.
The uvesafb module is included in the Hardy Heron kernel.
It would be great if it were possible to include this
When running from the Hardy "Live CD", an error still occurs as follows when
doing "dmsetup ls", even if "sudo" is used:
[EMAIL PROTECTED]:~$ sudo dmsetup ls
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper
Sorry to spam everyone subscribed to this bug: I wrote up a quick summary over
here:
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoAppleiMac24#Update_for_Ubuntu_8_04_Hardy_Her
Hope it helps anyone trying to the the iSight working on the iMac24 with alpha3
of Hardy Heron.
--
uvcv
Tested that this bug also reproduces in Gutsy x86 when running compiz-fusion
with the open-source "ati" driver
Section "Device"
Identifier "ATI Technologies Inc R423 UK [Radeon X800SE (PCIE)]"
Driver "ati"
BusID "PCI:1:0:0"
EndSection
This is on a
Tested on the XPS machine with the free "ati" driver
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoDellDimensionXPS
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoATIRadeonX800
running the Live CD of hardy-desktop-i386.iso (the January 2008 one with
18b9db3935b2910e4af
Tested that the symbolic link issue is indeed fixed in Hardy Heron.
The needed symbolic link is now there:
[EMAIL PROTECTED]:/usr/lib$ ls -al libXvMCNVIDIA.*
-rw-r--r-- 1 root root 194438 2008-01-11 11:08 libXvMCNVIDIA.a
lrwxrwxrwx 1 root root 25 2008-01-13 22:39 libXvMCNVIDIA.so.1 ->
libXvMC
If you enter your password in the "Password:" field of the "Basic" tab
on the "Modify Account" dialog, and check the "Remember password" box,
and save, then pidgin works OK with XMPP (Jabber).
--
Pidgin does'nt connect to jabber servers (jabber plugin error)
https://bugs.launchpad.net/bugs/153210
The bug is still there: If you _don't_ enter your password in the
"Password:" field of the "Basic" tab on the "Modify Account" dialog, or
_don't_ check the "Remember password" box, then this bug still happens
exactly as described above. Saving the password is only a workaround: I
guess some users w
Tested that this bug also reproduces in Gutsy on x86 (not only on x86_64) when
running compiz-fusion with the nVidia drivers (running Gutsy on a Dell box
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoDellDimensionXPS
with an nVidia 5200 card:
http://www.penlug.org/twiki/bin/view/M
Tested that this bug also reproduces in Gutsy x86 when running compiz-fusion
with the
open-source i810 driver, on a HP/Compaq dc7600 desktop.
As on x86_64, rebuilding xterm on x86 from source with debug symbols is a
workaround (problem doesn't occur):
sudo apt-get install libxaw-headers libxa
Confirmed on Ubuntu Gutsy 7.10 with Intel i810 driver on a HP/Compaq dc7600
desktop (using "xrandr -o left").
On the other hand, rotating works OK with compiz in Gutsy 7.10 using the nVidia
restricted drivers with
an nVidia 5200 card
(http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoN
The problem doesn't occur (using the same configuration file) using
Ubuntu Gutsy 7.10 on x86 machines, it seems to occur only on x86_64.
--
xterm on x86_64 intermittently segfaults when ~/XTerm contains "*scrollBar:
true" and "*saveLines: 10"
https://bugs.launchpad.net/bugs/176393
You recei
Public bug reported:
Binary package hint: xterm
On an Apple iMac running gutsy x86_64 (see the following page for how
I installed Ubuntu Gutsy 7.10)
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoAppleiMac24
I get intermittent segfaults (seen in dmesg as follows) when I have these l
Adding an attachment.
Place this file in your $HOME to reproduce the problem:
$ xterm &
[2] 7210
$ xterm &
[3] 7227
$ xterm &
[4] 7244
$ xterm &
[5] 7245
[4] Segmentation fault xterm
$ xterm &
[6] 7262
$ xterm &
[7] 7279
[1] Donexterm
[2] Donexte
The problem didn't occur on Ubuntu Feisty Fawn on x86_64 (I had been previously
using
the same configuration file on the iMac machine when it was running Feisty
Fawn, although
I no longer have that environment available any more as the machine is running
Gutsy now).
--
xterm on x86_64 intermit
sudo apt-get install libxaw-headers libxaw7-dev libncurses5-dev
$ apt-get source xterm
Reading package lists... Done
Building dependency tree
Reading state information... Done
Need to get 904kB of source archives.
Get:1 http://us.archive.ubuntu.com gutsy/main xterm 229-1 (dsc) [805B]
Get:2
Ah, sorry. I added "-lncurses" to the end of the link line, and now
xterm links OK using:
gcc -g -O2 -o xterm button.o cachedGCs.o charproc.o charsets.o \
cursor.o data.o doublechr.o fontutils.o input.o main.o menu.o misc.o \
print.o ptydata.o screen.o scrollbar.o tabs.o util.o xstrings.o xtermc
The bug doesn't appear to be in xterm, because disabling compiz-fusion
by adding the following line:
export WINDOW_MANAGER=metacity
to $HOME/.gnomerc
causes the bug to no longer occur.
The stack trace from "gdb /usr/bin/xterm" (i.e. without debug symbols)
and doing "run" over and over again unt
Strangely, when running "valgrind /usr/bin/xterm" it gives:
valgrind: /usr/bin/xterm: Permission denied
Whereas when running "valdrind ~/xterm-229/xterm" (i.e. on the one I built from
the sources) gives:
==8270== Memcheck, a memory error detector.
==8270== Copyright (C) 2002-2007, and GNU GPL'd
After installing libxt6-dbg (apt-get install libxt6-dbg) and running
under gdb, it gives:
$ gdb /usr/bin/xterm
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute co
** Description changed:
Binary package hint: nvidia-glx
I came across this when trying to ./configure mplayer with the
--enable-xvmc
flag to enable XvMC for nVidia, as described here:
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoNvidia5200
The mplayer configure
** Description changed:
Binary package hint: nvidia-glx
I came across this when trying to ./configure mplayer with the
--enable-xvmc
flag to enable XvMC for nVidia, as described here:
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoNvidia5200
The mplayer configure
Public bug reported:
On this machine, I have three separate batteries whose power status gets
displayed in various misleading ways.
- A CyberPower 1350AVR UPS (this is the battery whose status I'd prefer to
see in the menubar)
- A Bluetooth-connect Apple MagicTrackpad (synaptic driver)
-
Sorry, I meant to explain about the power status getting displayed in various
misleading ways:
What happens is, if the Bluetooth-connected Apple trackpad happens to become
disconnected
for whatever reason (happens occasionally, I still haven't figured out how to
prevent it), the
power meter show
** Attachment added: "What "unity-control-center power" window looks like on my
machine, note the mysterious red crossed circle near the UPS, what does that
tell the customer?"
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1475089/+attachment/4429670/+files/unity-control
** Attachment added: "Curious choice of panel icon and inconsistent display of
charge state in power dropdown menu."
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1475089/+attachment/4429671/+files/panel_icon_and_menu_showing_charge_state.jpg
--
You received this bug no
Public bug reported:
The Ubuntu 14.10 desktop amd64 live CD gives no graphical desktop on a Apple
MacBookPro 8,3 (A1397) 2011
(hardware described here:
http://www.penlug.org/foswiki/bin/view/Main/HardwareInfoAppleMacBookProA1297 ).
I also tested an upgrade from Ubuntu 14.04.02LTS to Ubuntu 14.1
This bug also occurs for me on Ubuntu 14.04, on a MacBook Pro
( http://www.penlug.org/foswiki/bin/view/Main/HardwareInfoAppleMacBookProA1297 )
and since the touchpad is managed using Synaptics (synclient) there appears to
be no need
for the "mouseemu" program to be running or even installed on th
I found that compiling Inkscape from source (rather time-consuming,
even on an i3 processor) gets the pen pressure working again for
a Wacom Intuos4 "small" tablet.
The steps to build from source are described on the Inkscape wiki
http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape#De
Hmmm... it seems that "sudo make install" causes the pen pressure
to stop working again, errp! So don't do that step!
It seems there's something that "sudo make install" puts into the
/usr/local/share/inkscape/palettes directory
that makes the pen pressure stop working, because if I just
com
Ahh, perhaps we're on to something here: I noticed that if
I choose e.g. the "Echo Icon Theme Palette" instead of using
the "Inkscape default" palette (by clicking on the tiny palette
selection arrow just to the right of the palette rectangle, which
is the thing just below the drawing area), the
I haven't installed Oneiric anywhere yet, but booting it from the live CD and
installing Inkscape, it doesn't look like the "palette trick" I mentioned
earlier
is any help in Oneiric: the pen pressure is still missing (even though the
"test
area" shows it is being sensed just fine). So perhaps t
Investigating the missing "pressure" when palette changes.
~~
Looking into the source code, the relevant files seem to be as follows:
./ui/dialog/swatches.cpp - swatch changes
./widgets/toolbox.cpp - usepressure (see "Use the pressure of the
Debugged a bit further: seems that what's happening is that the
call to gdk_event_get_axis around line 308 of dyna-draw-context.cpp
static void
sp_dyna_draw_extinput(SPDynaDrawContext *dc, GdkEvent *event)
{
if (gdk_event_get_axis (event, GDK_AXIS_PRESSURE, &dc->pressure))
dc->pressure
42 matches
Mail list logo
