** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/39697592/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/39697594/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39697596/Dependencies.txt
** A
Public bug reported:
Binary package hint: xterm
xterm misinterpretes some characters and writes junk text to the
terminal under the followign conditions:
1. The prompt contains special charachters, in this test case german umlauts
2. The text printed from a command (shell built-in, program, scri
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/39697590/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/39697591/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39697593/Dependencies.txt
** A
Public bug reported:
Binary package hint: xterm
xterm misinterpretes some characters and writes junk text to the
terminal under the followign conditions:
1. The prompt contains special charachters, in this test case german umlauts
2. The text printed from a command (shell built-in, program, scri
FYI, I still have this problem when using KDM. When I configure GDM it
works fine. Even the updates to Karmic that should affect exactly such a
case when both KDM and GDM are installed did not solve the problem for
me.
--
X-Server fails to start at boot time, debconf complains about unavailable T
*** This bug is a duplicate of bug 312491 ***
https://bugs.launchpad.net/bugs/312491
I think this can be closed duplicate for now based on the last two
comments, Bug 312491 discusses handling out-of-disk-space situations in
a more user-friendly way.
** Changed in: user-mode-linux (Ubuntu)
Could this be related to Bug #491483?
--
X-Server fails to start at boot time, debconf complains about unavailable TERM
https://bugs.launchpad.net/bugs/483645
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
_
there is a new binary pakage at
http://salt.com.tw/Download/Driver/PenMount/PenMount%20Ubuntu%209.10%20Driver%20V2.4.4.tar.gz
which works fine for me, but the installer isn't very polite have a look
at install.sh bevore using it!
--
xorg-input-penmount seems not to work on karmic
https://bugs.l
The basic problem of updating some packages is because of this (found in
the attached logfile):
dpkg: error processing
/var/cache/apt/archives/user-mode-linux_2.6.22-2um-0ubuntu2_i386.deb (--unpack):
failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during
`./usr/lib/uml/modules/2.6.22-
set to incomplete based on previous comment.
** Changed in: fglrx-installer (Ubuntu)
Status: New => Incomplete
--
package xorg-driver-fglrx 2:8.660-0ubuntu4 failed to install/upgrade: failed in
buffer_write(fd) (10, ret=-1): backend dpkg-deb during
`./usr/lib/libatiadlxx.so'
https://bug
so my laymans analysis would be that X tries to reconfigure itself and
fails miserably. The first question then is why does it need to
reconfigure in the first place? Can I turn that off?
--
X-Server fails to start at boot time, debconf complains about unavailable TERM
https://bugs.launchpad.net/
KDM-Logfile that shows the strange errors from debconf.
** Attachment added: "kdm.log.1"
http://launchpadlibrarian.net/35750790/kdm.log.1
--
X-Server fails to start at boot time, debconf complains about unavailable TERM
https://bugs.launchpad.net/bugs/483645
You received this bug notification
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/35750754/BootDmesg.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/35750755/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35750756/Dependencies.txt
** Att
Public bug reported:
Binary package hint: xorg
Since upgrading from 9.04 to 9.10 I have trouble getting the xserver and
kdm to start up. I did some investigation and found the following log in
the kdm.log file:
Dropping master
ddxSigGiveUp: Closing log
X.Org X Server 1.6.4
Release Date: 2009-9
I did some more investigation, this is what I came up with:
It seems to be depending on the kernel and the type of hibernate/resume
that is used.
- For stock kernels from Karmic with swsusp it does NOT happen
- For TuxOnIce-enalbed kernels from the TuxOnIce PPA it HAPPENS
- If I download pre-kern
@bjaglin
Your solution is... complex, especially regarding the obtaining of the
mesa packages and locking them. The libgl1-mesa-dri/libgl1-mesa-glx
packages can be easily obtained from packages.ubuntu.com. I wrote a
short explanation of how to "fix" the problem in bug 385539 and a more
detailed ex
I have it reproducible here, anything that I can provide to aid in
debugging this? Where would I start?
--
After update to karmic ALT-F[1-8] switches to text console
https://bugs.launchpad.net/bugs/463762
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I think it only happens after I hibernate/resume using the default
swsusp functionality.
I have a kernel that has both, TuxOnIce and the standard swsusp
functionality from the TuxOnIce PPA. If I hibernate/resume using
TuxOnIce via the "hibernate" script, it works fine, if I use the
standard hibern
I saw that restarting fixes this for some time, but it reappears and it
"survives" a hibernate/resume.
Logging in/out does not help.
Restarting kdm does help for a while until it reappears.
Cannot yet say for sure if hibernate/resume is related, but might be.
--
After update to karmic ALT-F[1-
Public bug reported:
Binary package hint: xserver-xorg-input-penmount
Having a Display from IEI using Penmount 9000 Serial chip [1]
as I installed Karmic the touch functionality wont work even if i tried to
calibrate the display
by tool or giving known parameters from the installation before w
Like I commented on bug 385539, I fixed this temporarily by installing
libgl1-mesa-dri and libgl1-mesa-glx from the Jaunty repositories.
I'm now getting
direct rendering: No (LIBGL_ALWAYS_INDIRECT set)
and
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R200 20060
I can confirm this, on Radeon 9200.
Downloading libgl1-mesa-dri and libgl1-mesa-glx 7.4 from jaunty
repositories and installing them with dpkg fixed the problem.
But, now I have indirect rendering, glxinfo says:
direct rendering: No (LIBGL_ALWAYS_INDIRECT set)
and glxgears flickers. Haven't had
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/34626125/BootDmesg.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/34626126/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34626127/Dependencies.txt
** Att
Public bug reported:
Reporting to X-Server as I don't know where else this could be caused.
After upgrading to Karmic I now have the strange behavior that not only
ALT-CTRL-F[1-8] switches to the text console from X-Server, but also
ALT-F[1-8] does this switching. I don't know where this comes fr
Nevermind, it was just because grub was not updated and it started with
the old kernel...
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
Xorg assert failure: *** glibc detected *** /usr/bin/X: realloc(): invalid
pointer: 0x028c0020 ***
https://bugs.launchpad.net/bu
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34251468/BootDmesg.txt
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/34251469/CoreDump.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/34251470/CurrentDmesg.txt
** Attachment
Just to be clear: this is with stock ati drivers from the repos.
--
[ATI][KMS][R300] Compiz boots to white screen with Mesa 7.6+git
https://bugs.launchpad.net/bugs/411451
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
_
I am also experiencing this issue on R200 hardware.
In Jaunty, when enabling compositing, the system looks for 3 instances
of texture_from_pixmap in the output from glxinfo. It's there.
On Karmic, there are only 2 instances of this in glxinfo output.
Compositing in KDE is horribly slow, in Gnome
In that case, the output of "grep commit /var/log/Xorg.0.log" in both
cases (with the driver on the LiveCD and the driver from the PPA)
produces blank output. I guess the driver doesn't get loaded?
--
Acer Ferrari 3000 fails to resume from standby in Jaunty
https://bugs.launchpad.net/bugs/339336
Is a fix really released? After all, it sort-of works in Karmic, but
it's still broken in Jaunty.
Switching to console and back does not fix the corruption.
If I understand correctly, if I installed ati and radeon packages
version 6.12.99+git20090825.fc74e119 I'm supposed to look for fc74e119
in
In Karmic Alpha 5 the computer resumes from standby correctly.
This happens both with the driver from the CD and with the driver from
the PPA (although I'm not really able to determine that the driver from
PPA gets loaded correctly, as it reports the same version?).
With both drivers, however, th
Lowering the AGP mode to 4 does not do anything.
However, the computer resumes correctly with the VESA driver.
--
Acer Ferrari 3000 fails to resume from standby in Jaunty
https://bugs.launchpad.net/bugs/339336
You received this bug notification because you are a member of Ubuntu-X,
which is subs
This doesn't work in Jaunty for me. The key commands works in the system
console.
System informations placed in bug 412097. I use a Dell Inspiron 6400 notebook.
"xev" output of pressing alt + prnt (sys-rq):
KeyPress event, serial 35, synthetic NO, window 0x401,
root 0xab, subw 0x0, time
*** This bug is a duplicate of bug 305762 ***
https://bugs.launchpad.net/bugs/305762
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30188415/Dependencies.txt
** Attachment added: "LsHal.txt"
http://launchpadlibrarian.net/30188416/LsHal.txt
** Attachment added: "
*** This bug is a duplicate of bug 305762 ***
https://bugs.launchpad.net/bugs/305762
Public bug reported:
Binary package hint: xorg
This is a duplicate of bug 305762 (change: issue exists also in Jaunty)
with system information from command "ubuntu-bug -p xorg".
Don't know how to extract th
,
Dominik
--
fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
___
Mailing list: https
Catalyst 9.5 might solve the problem. See my post at
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/314600
--
fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is
not supported on this hardware (return code = 1) [EPR#257840]
https://bugs.launchpad.net/bugs
Under openSUSE 11.1 (64bit) it seems that with catalyst 9.5 the problem
is gone (I am using an ATI Mobility Radeon HD 3650). The X server starts
up just fine without using "aticonfig --acpi-services=off". (This also
solves a problem with the HDMI output (hot-plug) recognition.)
I am sorry, that I
101 - 138 of 138 matches
Mail list logo
