[Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
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 resume - Did not test hibernate/resume This kernel image solved the reported issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
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 0101 0101 0101 030 0101 0101 0101 d04d a000 70f0 803e 2030 040 0035 a526 0010 1800 a6a4 a000 70f0 803e 050 2030 0035 a526 0010 1800 fe00 3000 060 3952 4b39 4c80 3151 3144 070 0200 0341 0128 0012 0b00 0a01 2020 4100 080 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
@tjaalton I recently switched to Debian, it's difficult for me now to test Ubuntu kernels. I tried on i915.enable_psr=0 on broken Debian kernel linux-image-5.4.0-4-amd64 (5.4.19+1): Screen corruption persisted. Let me know if you need to have it tested with an Ubuntu kernel, I'd try Ubuntu 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 ad 14 00 00 00 00 |M...| 0010 2a 1c 01 04 a5 1d 11 78 0e de 50 a3 54 4c 99 26 |*..x..P.TL.&| 0020 0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 |.PT.| 0030 01 01 01 01 01 01 4d d0 00 a0 f0 70 3e 80 30 20 |..Mp>.0 | 0040 35 00 26 a5 10 00 00 18 a4 a6 00 a0 f0 70 3e 80 |5.&..p>.| 0050 30 20 35 00 26 a5 10 00 00 18 00 00 00 fe 00 30 |0 5.&..0| 0060 52 39 39 4b 80 4c 51 31 33 33 44 31 00 00 00 00 |R99K.LQ133D1| 0070 00 02 41 03 28 01 12 00 00 0b 01 0a 20 20 00 41 |..A.(... .A| 0080 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
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 01 4d d0 00 a0 f0 70 3e 80 30 20 35 00 26 a5 10 00 00 18 a4 a6 00 a0 f0 70 3e 80 30 20 35 00 26 a5 10 00 00 18 00 00 00 fe 00 30 52 39 39 4b 80 4c 51 31 33 33 44 31 00 00 00 00 00 02 41 03 28 01 12 00 00 0b 01 0a 20 20 00 41 EDID version: 1.4 Manufacturer: SHP Model 5293 Serial Number 0 Made in week 42 of 2018 Digital display 8 bits per primary color channel DisplayPort interface Maximum image size: 29 cm x 17 cm Gamma: 2.20 Supported color formats: RGB 4:4:4, YCrCb 4:4:4 Default (sRGB) color space is primary color space First detailed timing includes the native pixel format and preferred refresh rate Color Characteristics Red: 0.6396, 0.3291 Green: 0.2998, 0.5996 Blue: 0.1494, 0.0595 White: 0.3125, 0.3281 Established Timings I & II: none Standard Timings: none Detailed mode: Clock 533.250 MHz, 294 mm x 165 mm 3840 3888 3920 4000 ( 48 32 80) 2160 2163 2168 ( 3 5 54) -hsync -vsync VertFreq: 59.997 Hz, HorFreq: 133.312 kHz Detailed mode: Clock 426.600 MHz, 294 mm x 165 mm 3840 3888 3920 4000 ( 48 32 80) 2160 2163 2168 ( 3 5 54) -hsync -vsync VertFreq: 47.997 Hz, HorFreq: 106.650 kHz Alphanumeric Data String: 0R99K Manufacturer-Specified Display Descriptor (0x00): 00 00 00 02 41 03 28 01 12 00 00 0b 01 0a 20 20 A.(... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
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. ** Bug watch added: freedesktop.org Bugzilla #110511 https://bugs.freedesktop.org/show_bug.cgi?id=110511 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855608] [NEW] Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10
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. Booting in recovery mode worked, though and I was able to install all updates for preinstalled 18.04 LTS with the OEM kernel. Problems in non- recovery mode persisted after installing all updates. I then updated to Ubuntu 19.04 and changed to "generic" linux kernel image without success: Problem persisted, only recovery mode was usable. I updated once more to 19.10 again without any success. >From the perhaps related bug #1849947 I tried latest drm-tip kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ drm-tip kernel solves the issue for first boot, but after resuming from suspend, the same issues display issues occur. Kernel images I tried: - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics output without "nomodeset" - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output without "nomodeset" - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output without "nomodeset" - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted graphics output after resuming from suspend ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.4.0-994-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 18:51:15 2019 DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-11-25 (13 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption eoan third-party-packages ubuntu ** Attachment added: "Picture taken after booting linux-image-5.3.0-24-generic kernel on Ubuntu 19.10" https://bugs.launchpad.net/bugs/1855608/+attachment/5310765/+files/IMG_20191208_181821455.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106737]
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 Title: Renaming folder to same name but different case not allowed To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/106737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013433] Re: e-uae crashes on startup
*** 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.launchpad.net/bugs/1013433 Title: e-uae crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e-uae/+bug/1013433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 288022] Re: The guest additions build, start but do nothing
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) doesn't match the server's version (4) (taken from my Xorg.0.log). This happens with virtualbox-ose-guest-utils version 2.0.4-dfsg- 0ubuntu1. -- The guest additions build, start but do nothing https://bugs.launchpad.net/bugs/288022 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292856] [NEW] [intrepid] guest utils do not work with xserver
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), then unloads the module and exits with No drivers available. [...] no screens found ** Affects: virtualbox-ose (Ubuntu) Importance: Undecided Status: New -- [intrepid] guest utils do not work with xserver https://bugs.launchpad.net/bugs/292856 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292856] Re: [intrepid] guest utils do not work with xserver
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/bugs/292856 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 230134] Re: [hardy] Unable to print in KDE 3.5
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 to print, if you're right it seems like the application I use most (for printing documents) won't be able to print for me ever again... -- [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-kde in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 230134] Re: [hardy] Unable to print in KDE 3.5
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 logs) and once using the lpr commandline tool (job number 118). Before testing, I set CUPS' LogLevel to debugging and restarted CUPS via the initscript. Printing via kpdf (job 117) did not work (the printer - an HP LaserJet 5M that I use via CUPS' LPD back- end - did not print anything, I'm not sure if it received any job at all as the printer is in another room) although CUPS said (I used the webinterface on localhost:631 to verify this) the job was completed. Printing via lpr (job 118) did work; job 118 completed nicely. Attached you can find CUPS' access_log, error_log and page_log entries. ** Attachment added: access_log of my test http://launchpadlibrarian.net/19149443/access_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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 230134] Re: [hardy] Unable to print in KDE 3.5
** 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-kde in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 230134] Re: [hardy] Unable to print in KDE 3.5
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 230134] Re: [hardy] Unable to print in KDE 3.5
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 filtered by pdftops and pstops. I guess this is the reason why it doesn't print. The printer actually needs real postscript. -- [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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 230134] [NEW] [hardy] Unable to print in KDE 3.5
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 konqueror, system-config-printer-applet-kde is started, the job is then fed to cups (according to the logfile) and then apparently succeeds but nothing gets actually printed. I am using an HP JetDirect Printserver with cups' remote lpd backend. I am suspecting system-config-printer-kde but have no evidence for my suspicion. I have not tested KDE4 as I do not use it, yet. ** Affects: system-config-printer-kde (Ubuntu) Importance: Undecided Status: New -- [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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191166] [NEW] [hardy] mediawiki does not work with postgresql 8.3
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 (2.2.8-1) libapache2-mod-php5 (5.2.4-2ubuntu4) libpq5 (8.3.0-1) mediawiki (1:1.11.1-1) mediawiki-math (1:1.11.1-1) php5 (5.2.4-2ubuntu4) php5-cli (5.2.4-2ubuntu4) php5-common (5.2.4-2ubuntu4) php5-gd (5.2.4-2ubuntu4) php5-pgsql (5.2.4-2ubuntu4) postgresql-8.2 (8.2.6-2) postgresql-client-8.2 (8.2.6-2) postgresql-client-common (85) postgresql-common (85) postgresql-contrib-8.2 (8.2.6-2) ** Affects: mediawiki (Ubuntu) Importance: Undecided Status: New -- [hardy] mediawiki does not work with postgresql 8.3 https://bugs.launchpad.net/bugs/191166 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191164] [NEW] [hardy] mediawiki update.php does not work on postgresql
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 (Ubuntu) Importance: Undecided Status: New -- [hardy] mediawiki update.php does not work on postgresql https://bugs.launchpad.net/bugs/191164 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181767] [hardy] postgresql support broken in 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 currently no mediawiki version with working postgresql support in hardy and I would lose my wiki. mediawiki1.10 from gutsy works with postgresql. ** Affects: mediawiki (Ubuntu) Importance: Undecided Status: New -- [hardy] postgresql support broken in mediawiki https://bugs.launchpad.net/bugs/181767 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99800] Re: [feisty] CD-ROM drive is not detected correctly since transition to ata_piix for PATA devices
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 notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99800] Re: [feisty] CD-ROM drive is not detected correctly since transition to ata_piix for PATA devices
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 is always detected as a non-removable harddisk. The solution would probably be to hardcode the SR243T as CD-ROM device so that it won't be claimed by sd_mod. -- [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 notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98928] [feisty] NetworkManager forgets statically configured domain
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. What happens is the following: 1. Configure domain: knetworkmanager-Static Connection...-Domain Name System-Domain name 2. Examine resolv.conf: The entry domain is there and correct 3. Restart networking: sudo /etc/init.d/networking restart 4. Examine resolv.conf: domain is missing My current workaround is to deinstall knetworkmanager and network- manager. ** Affects: knetworkmanager (Ubuntu) Importance: Undecided Assignee: Brian Murray Status: Needs Info -- [feisty] NetworkManager forgets statically configured domain https://bugs.launchpad.net/bugs/98928 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 99800] [feisty] CD-ROM drive is not detected correctly since transition to ata_piix for PATA devices
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 afterwards), but it still does not work. Somehow, the kernel seems to think my old /dev/hdc (the CD-ROM drive) is a disk and the sd_mod driver claims it as /dev/sdb. sd_mod of course does not work for a CD-ROM drive. Manually loading sr_mod after booting does not solve the issue, as the device seems to be already claimed by sd_mod. The CD-ROM drive is a slim Mitsumi SR243T. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- [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.com/mailman/listinfo/ubuntu-bugs
[Bug 99800] Re: [feisty] CD-ROM drive is not detected correctly since transition to ata_piix for PATA devices
** 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99800] Re: [feisty] CD-ROM drive is not detected correctly since transition to ata_piix for PATA devices
** 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.com/mailman/listinfo/ubuntu-bugs
[Bug 98928] [feisty] NetworkManager forgets statically configured domain
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 following: 1. Configure domain: knetworkmanager-Static Connection...-Domain Name System-Domain name 2. Examine resolv.conf: The entry domain is there and correct 3. Restart networking: sudo /etc/init.d/networking restart 4. Examine resolv.conf: domain is missing My current workaround is to deinstall knetworkmanager and network- manager. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- [feisty] NetworkManager forgets statically configured domain https://launchpad.net/bugs/98928 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98928] Re: [feisty] NetworkManager forgets statically configured domain
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68293] Re: [edgy] /var/run is mounted before /var
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
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
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. I cannot confirm this now, but it seems like time runs much too fast in dom0 (this is on the computer where the CPU clock speed is reported correctly), and this leads to ntpd stepping the time back for as much as 4 seconds at once. -- [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
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
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/listinfo/ubuntu-bugs
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
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 one second), negative adjustments. Positive adjustments don't trigger this bug. Attached is the source code for the test program. ** Attachment added: test program http://librarian.launchpad.net/4935549/test.c -- [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
[Bug 68293] [edgy] /var/run is mounted before /var
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) Importance: Undecided Status: Unconfirmed -- [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
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
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. both Xen and Linux report 1.0 GHz). -- [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
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
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 but after killing and restarting X the keyboard didn't work anymore. -- [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
[Bug 67519] [edgy] keyboard broken in X11 on xen dom0
Public bug reported: Hello! Booting Kubuntu edgy as Xen dom0 makes my keyboard unusable under X11. It gets very sluggish, meaning that there is a varying delay between key press and printing of a character on the screen and that some characters are doubled. After logging in to X11, the keyboard first behaves as it should, but at the time kdewallet asks for the wallet passphrase (which is usually the last thing that happens when the session is restored), the keyboard starts to behave like this. I have installed the following packages: libc6-xen (2.4-1ubuntu12) libxen3.0 (3.0.3-0ubuntu1) python-xen3.0 (3.0.3-0ubuntu1) xen-docs-3.0 (3.0.3-0ubuntu1) xen-hypervisor-3.0-i386 (3.0.3-0ubuntu1) xen-image-xen0-2.6.17-6-generic-xen0 (2.6.17-6) xen-restricted-modules-2.6.17-6-generic-xen0 (2.6.17-3) xen-utils-3.0 (3.0.3-0ubuntu1) The problem seems to be (K)Ubuntu specific, as it does not happen with the Xen 3.0.3 live CD. I have suspected it might be a kernel/hypervisor problem and tried the latest unstable XEN kernel/hypervisor (from xen-unstable.hg) without replacing the user space tools, but the problem still occurs. I have also suspected, that my CPU is detected wrong, because I 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 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
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
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
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
** 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
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
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/listinfo/ubuntu-bugs
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
** 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
[Bug 67519] Re: [edgy] keyboard broken in X11 on xen dom0
** 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
[Bug 62748] Re: 2.0.55-4ubuntu4 update causes svn failure
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61120] Re: [edgy] glibc-doc-reference is uninstallable
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 really a bug in glibc-doc-reference, but a bug in glibc-doc _and_ glibc-doc-reference. -- [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
[Bug 60607] Re: info documentation missing
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://launchpad.net/bugs/60607 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61120] [edgy] glibc-doc-reference is uninstallable
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/share/doc-base/glibc-manual', which is also in package glibc-doc dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/glibc-doc-reference_2.3.6-1_all.deb Should be simple to fix. But I am asking myself why the heck it happens so often. It should be rather trivial to have a program check the whole archive if all packages whose files conflict with the files of other packages do declare a conflict with these other packages in the control file. If that is not the case, either the control file is wrong or the package contents are wrong. The data needed for this tool is already gathered by packages.ubuntu.com Search the contents of packages. This check should be made _before_ inclusion of a new package upload. ** Affects: glibc-doc-reference (Ubuntu) Importance: Untriaged Status: Unconfirmed -- [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
[Bug 61120] Re: [edgy] glibc-doc-reference is uninstallable
** 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
[Bug 58320] Re: edgy's kdenetwork-dev is not installable
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/include/kde/kopete/kabcpersistence.h', which is also in package kopete-dev dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/kdenetwork-dev_4%3a3.5.4-0ubuntu2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- edgy's kdenetwork-dev is not installable https://launchpad.net/bugs/58320 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
