Sorry, @tjaalton, took a while (needed to install Ubuntu again). I was
able to test your custom kernel on a freshly installed Ubuntu 19.10.
Results with custom kernel from https://aaltoset.kapsi.fi/lp1826125:
- Screen corruption was gone
- Suspend/resume worked and graphics output was usable after
Hex dump of EDID (without ASCII representation due to line wrapping):
packet@xps:~$ cat
/sys/devices/pci\:00/\:00\:02.0/drm/card0/card0-eDP-1/edid | hexdump
000 ff00 00ff 104d 14ad
010 1c2a 0401 1da5 7811 de0e a350 4c54 2699
020 500f 0054 0101 0101
untu 19.10 live usb thumbdrive then.
@kent-jclin I guess your question for EDID data was already answered. In
case it wasn't, this is what I got from /sys:
packet@xps:~$ cat
/sys/devices/pci\:00/\:00\:02.0/drm/card0/card0-eDP-1/edid | hexdump -C
00 ff ff ff ff ff ff 00 4d 10
Decodes to:
packet@xps:~$ cat
/sys/devices/pci\:00/\:00\:02.0/drm/card0/card0-eDP-1/edid |
edid-decode
edid-decode (hex):
00 ff ff ff ff ff ff 00 4d 10 ad 14 00 00 00 00
2a 1c 01 04 a5 1d 11 78 0e de 50 a3 54 4c 99 26
0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01
With a custom kernel built from Ubuntu linux package 5.3.0-24.26 with
this patch:
https://bugs.freedesktop.org/attachment.cgi?id=144765
(freedesktop.org bug
https://bugs.freedesktop.org/show_bug.cgi?id=110511)
display works as expected: Flickering after first boot and after resume
is gone.
** B
Public bug reported:
I just received a new Dell XPS 13 7390 laptop. With factory preinstalled
Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics was severely
distorted. The display would constantly flicker with areas of the
display staying black or showing patterns of square color blocks.
B
I can confirm the same issue on Thunderbird 15.0.1, Mozilla 5.0 on
Debian 6.0.5. Thunderbird is installed from Mozilla and not the Debian
repos.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106737
Ti
*** This bug is a duplicate of bug 991091 ***
https://bugs.launchpad.net/bugs/991091
** This bug has been marked a duplicate of bug 991091
e-uae segfaults at startup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
The attached patch for the virtualbox-ose source package fixes the
problem for me.
** Attachment added: "patch for virtualbox-ose 2.0.4-dfsg-0ubuntu1"
http://launchpadlibrarian.net/19259791/virtualbox-intrepid.diff
--
[intrepid] guest utils do not work with xserver
https://bugs.launchpad.net/
Public bug reported:
Binary package hint: virtualbox-ose
The vboxvideo driver from virtualbox-ose-guest-utils version 2.0.4-dfsg-
0ubuntu1 in intrepid does not work with xserver-xorg version
1:7.4~5ubuntu3 (the Xserver says "module ABI major version (2) doesn't
match the server's version (4)", t
I can also confirm the problem. The reason for this is that "vboxvideo"
must be used as a video driver but x11config.pl does not add vboxvideo.
And there's another problem, too: If you use the vboxvideo driver under
intrepid, the xserver won't even start, because of "module ABI major
version (2) d
I tested it and successfully printed an OpenOffice.org document using
OpenOffice.org and a PDF using KGhostview. Then the bug has changed
throughout hardy's lifetime: when I first reported it, I could not print
from any GUI application. Although I'm glad that now at least some
applications are able
Looking at the error_log, I see that printing via kpdf sets the content
type to application/postscript, which is obviously wrong for a PDF.
Printing via lpr sets the content type to application/pdf. As a
consequence, the job 117 (kpdf) is only filtered by pstops whereas the
job 118 (lpr) is filtere
** Attachment added: "page_log of the test"
http://launchpadlibrarian.net/19149460/page_log
--
[hardy] Unable to print in KDE 3.5
https://bugs.launchpad.net/bugs/230134
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: "error_log of the test"
http://launchpadlibrarian.net/19149450/error_log
--
[hardy] Unable to print in KDE 3.5
https://bugs.launchpad.net/bugs/230134
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to system-config-printer-
Yes, this problem still occurs. I am currently using KDE version 3.5.10
(this translates to versions 4:3.5.10-0ubuntu1~hardy2 and
4:3.5.10-0ubuntu1~hardy1 versions of the various KDE packages). To test
if the problem is still there I tried to print a PDF file once using
kpdf (job number 117 in the
Public bug reported:
Binary package hint: system-config-printer-kde
I can't print using any KDE application anymore since the upgrade to
Hardy. Printing from the commandline via cupsys-bsd's /usr/bin/lpr
command works, but printing through KDE does not. When I try to print
anything from kpdf or k
Public bug reported:
Binary package hint: mediawiki
The current mediawiki package (1:1.11.1-1) does not work with postgresql
version 8.3, but works with postgresql version 8.2. This is the setup
that works for me right now:
apache2-mpm-prefork (2.2.8-1)
apache2-utils (2.2.8-1)
apache2.2-common (
Public bug reported:
Binary package hint: mediawiki
The updaters.inc script in mediawiki 1:1.11.1-1 uses the method
Database::Postgres.hasConstraint() in line 1463. This method needs to be
picked from mediawiki SVN, otherwise the update procedure fails when
using postgres.
** Affects: mediawiki
Public bug reported:
Binary package hint: mediawiki
Hi!
After upgrading to hardy's mediawiki 1:1.11.0-2, I noticed php errors on my
wiki when editing a page.
Turns out, it is this bug: http://bugzilla.wikimedia.org/show_bug.cgi?id=11292
This means I can't upgrade to hardy because there is curr
I'm using the Plextor drive right now, but I still have the Mitsumi
drive. I can test it with Gutsy, but it will take a little while.
--
[feisty] CD-ROM drive is not detected correctly since transition to ata_piix
for PATA devices
https://bugs.launchpad.net/bugs/99800
You received this bug notif
More testing revealed that
1) the problem still persists with Gutsy's linux-image-2.6.22-5-generic and
2) the problem is probably caused by the CD-ROM firmware, replacing the Mitsumi
drive with a Plextor drive fixed the problem: the Plextor was correctly
detected as CD-ROM, whereas the Mitsumi i
You have been subscribed to a public bug:
I am using Kubuntu Feisty Fawn and I cannot set the domain (as in
resolv.conf's "domain" keyword) persistently via knetworkmanager. It
seems like knetworkmanager appends the domain to resolv.conf, but
NetworkManager regenerates resolv.conf when started. Wh
** Attachment added: "dmesg output"
http://librarian.launchpad.net/7099691/dmesg
--
[feisty] CD-ROM drive is not detected correctly since transition to ata_piix
for PATA devices
https://launchpad.net/bugs/99800
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
** Attachment added: "lspci -vvv output"
http://librarian.launchpad.net/7099692/lspci
--
[feisty] CD-ROM drive is not detected correctly since transition to ata_piix
for PATA devices
https://launchpad.net/bugs/99800
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
Public bug reported:
Binary package hint: linux-image-2.6.20-13-generic
After the transition to libata/ata_piix for my PATA computer, the kernel
does not detect my CD-ROM drive anymore. I tried "options libata
atapi_enabled=1" in /etc/modprobe.d/libata (regenerating the initrd and
rebooting after
I know it does. I just mentioned it as a way to reproduce the bug
without rebooting. Of course, rebooting also triggers the bug.
--
[feisty] NetworkManager forgets statically configured domain
https://launchpad.net/bugs/98928
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
Public bug reported:
I am using Kubuntu Feisty Fawn and I cannot set the domain (as in
resolv.conf's "domain" keyword) persistently via knetworkmanager. It
seems like knetworkmanager appends the domain to resolv.conf, but
NetworkManager regenerates resolv.conf when started. What happens is the
fol
Thanks for the info, mkdir /var/run, /var/lock on my root filesystem
fixed the problem.
--
[edgy] /var/run is mounted before /var
https://launchpad.net/bugs/68293
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: initscripts
Hi!
The current edgy initscripts try to mount /var/run before /var could be
mounted. This obviously fails and in the end, networking does not work
(because /var/run/network also seems to be missing)
** Affects: sysvinit (Ubuntu)
Importa
I was a bit too fast, turns out, that openntpd's "adjusting local clock
by" message means adjtime(). I've written a small test program to
reproduce this bug.
sudo ./test -4
triggers the bug and
sudo ./test 0
fixes it after doing the first.
The bug can only be triggered with big (i.e. more than
I didn't mention it before, but to reproduce this bug it might be
necessary to use a PS/2 keyboard, this is what I'm using.
--
[edgy] keyboard broken in X11 on xen dom0
https://launchpad.net/bugs/67519
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
I think I have found the cause: openntpd. The keyboard begins stuttering
in the exact moment that ntpd is stepping time because of a great
offset. Keyboard works if I disable ntpd and stops working if I start it
then. I have tested this on the second computer and will test it now on
the first one.
Seems like I was a bit too fast. It is not working on the other
computer, it just takes a bit longer but then not only the keyboard
behaves odd, but shortly after the keyboard begins to make trouble, X
(or the keyboard, I currently have no mouse) locks up completely.
Logging in via ssh still worked
The same setup as above is working in another computer. On this one (the
working one), Xen and the Dom0 kernel agree about the CPU clock speed
(it's an old 1.3 GHz Athlon, clocked down to 1.0 GHz to reduce heat) and
the reported CPU clock speed equals the actual clock setting from the
BIOS (i.e. bo
** Attachment added: "dmesg gathered under xen"
http://librarian.launchpad.net/4922322/dmesg.txt
--
[edgy] keyboard broken in X11 on xen dom0
https://launchpad.net/bugs/67519
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "xm dmesg"
http://librarian.launchpad.net/4922321/xm-dmesg.txt
--
[edgy] keyboard broken in X11 on xen dom0
https://launchpad.net/bugs/67519
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sound is also stuttering under Xen, so maybe it really is a timing
problem caused by the disagreement over CPU clock speed.
--
[edgy] keyboard broken in X11 on xen dom0
https://launchpad.net/bugs/67519
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
** Attachment added: "lspci gathered under xen"
http://librarian.launchpad.net/4922320/lspci-xen.txt
--
[edgy] keyboard broken in X11 on xen dom0
https://launchpad.net/bugs/67519
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On the console the keyboard works fine. So it's probably a problem in
the Xserver that is exposed by Xen.
--
[edgy] keyboard broken in X11 on xen dom0
https://launchpad.net/bugs/67519
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
have a
Pentium 4 1.8 GHz which the hypervisor rightly detects as such but the
dom0 kernel (from the package and also the xen upstream kernel) reports
a 2 GHz Pentium.
Read U!
packet
** Affects: xen-3.0 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
[edgy] keyboard broken in
I can confirm this bug. It makes libsvn-javahl (1.3.2-3ubuntu2)
unusable. I can reproduce this bug with a self-compiled subversion 1.4.0
javahl linked against the same libraries (libapr0 2.0.55-4ubuntu4 and
libneon 0.25.5.dfsg-5). The problem vanishes if I compile subversion
1.4.0 against the curre
I seem to have forgotten to enable the attachment...
** Attachment added: "JVM error trace"
http://librarian.launchpad.net/4824478/hs_err_pid8671.log
--
2.0.55-4ubuntu4 update causes svn failure
https://launchpad.net/bugs/62748
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
The info documentation is included in glibc-doc-reference. The real bug
here is, the glibc-doc's doc-base entry (/usr/share/doc-base/glibc-
manual) references the info files, but the package does not depend on
glibc-doc-reference. A related bug is #61120.
--
info documentation missing
https://lau
You need to install both glibc-doc and glibc-doc-reference, as glibc-
doc-reference tries to overwrite the file /usr/share/doc-base/glibc-
manual which is installed by glibc-doc. So whichever comes first will
install without error, breaking installation of the other package. It's
probably not reall
** Tags added: edgy
--
[edgy] glibc-doc-reference is uninstallable
https://launchpad.net/bugs/61120
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: glibc-doc-reference
1. Install package glibc-doc.
2. Install package glibc-doc-reference
3. There is no step three, it fails with:
dpkg: error processing
/var/cache/apt/archives/glibc-doc-reference_2.3.6-1_all.deb (--unpack):
trying to overwrite `/usr/
There seems to be at least one file from kopete-dev left in the new
kdenetwork-dev:
Unpacking kdenetwork-dev (from .../kdenetwork-dev_4%3a3.5.4-0ubuntu2_i386.deb)
...
dpkg: error processing
/var/cache/apt/archives/kdenetwork-dev_4%3a3.5.4-0ubuntu2_i386.deb (--unpack):
trying to overwrite `/usr/
Public bug reported:
Binary package hint: kdenetwork-dev
Hi!
kdenetwork-dev (4:3.5.4-0ubuntu1) depends on kopete (=
4:3.5.4-0ubuntu1), which is not available since kopete is not built from
kdenetwork source package anymore.
The same holds true for Jonathan Riddell's KDE 3.5.4 packages for
dappe
49 matches
Mail list logo
