[Bug 1797282] Re: fsck not running at all on reboot
I'm seeing this on an Ubuntu 16.04.5 LTS system running on top of LVM. In my case, I get: *** /dev/mapper/wolf-root will be checked for errors at next reboot *** Having to dig out a 16.04 LTS Server USB stick every time I need to run FSCK is extremely inconvenient. It turns an unattended maintenance job into one that requires a lot of hand-holding. Please let me know if there's any information I can provide to get this fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797282 Title: fsck not running at all on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786090] Re: Installation fails on HP T610 Plus Thin Client internal flash (EFI)
Hi Steve, thanks for the response. I managed to get this working by coldbooting the machine, then ran: sudo update-grub # this fixes the missing GRUB config Next I installed Vim -- APT figured out that shim-signed hadn't been configured, and retried. This time it succeeded! The machine came with Windows 7 Embedded, and I warm-booted into the installer (reboot from Windows, select "boot from USB stick" in the BIOS boot menu). I suspect the warm-booting may be a factor. Regardless, I will probably be doing a reinstall on this machine anyway and will update the ticket if I find out anything further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786090 Title: Installation fails on HP T610 Plus Thin Client internal flash (EFI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1786090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786090] Re: Installation fails on HP T610 Plus Thin Client internal flash (EFI)
Shim-signed failed to install. Here's the terminal output: root@cedric:~$ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up shim-signed (1.34.9.2+13-0ubuntu2) ... Installing for x86_64-efi platform. Could not delete variable: Invalid argument grub-install: error: efibootmgr failed to register the boot entry: Block device required. dpkg: error processing package shim-signed (--configure): installed shim-signed package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: shim-signed E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786090 Title: Installation fails on HP T610 Plus Thin Client internal flash (EFI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1786090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786090] Re: Installation fails on HP T610 Plus Thin Client internal flash (EFI)
I've just rebooted the system and it dropped into a GRUB prompt.
I managed to boot it manually using the instructions here:
https://askubuntu.com/questions/38082/how-do-i-manually-boot-from-the-
grub-prompt-after-do-release-upgrade
After booting into Xubuntu, I ran:
sudo grub-install
Which ran to completion and appears to have succeeded ("Installation
finished. No error reported.")
I've just found out that the "shim-signed" package hasn't installed, so
I'm waiting for apt-get install -f to finish.
** Also affects: shim-signed (Ubuntu)
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/1786090
Title:
Installation fails on HP T610 Plus Thin Client internal flash (EFI)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1786090/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786090] [NEW] Installation fails on HP T610 Plus Thin Client internal flash (EFI)
Public bug reported: I tried to install Xubunti 18.04.1 LTS on a HP T610 Plus thin client with the 1.20 Rev A BIOS (recently upgraded from 1.16 Rev A). The installation proceeded normally until the bootloader was installed -- grub-install failed. I ran grub-install a second time from a console and got the same error as seen in the installer: $ sudo chroot /target grub-install /dev/sda Installing for x86_64-efi platform. Could not delete variable: Invalid argument grub-install: error: efibootmgr failed to register the boot entry: Block device required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Wed Aug 8 19:23:41 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786090 Title: Installation fails on HP T610 Plus Thin Client internal flash (EFI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1786090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735991] Re: QL-570 printer : the led flashes red and nothing happens
Another thought - can you also post the Brother part number of the labels you're using please? (then I can look that up and make sure your page size is right) It'll be on a label on the side of the plastic label roll cartridge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735991 Title: QL-570 printer : the led flashes red and nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735991] Re: QL-570 printer : the led flashes red and nothing happens
Clean Print Head doesn't apply to the QL driver. "cleaning" the heads requires either a cleaning card or a bit of manual work (can't remember if the 570 is like a Zebra printer; the instructions should be in the manual). The CUPS test page is geared up for page printers, not label printers. I haven't tried it with the Ptouch driver but I wouldn't be surprised if it had problems. As I said - you need to configure the label dimensions correctly in both the driver and the application. I've never tried Libreoffice, but gLabels works well. If you get the page size wrong (especially width), the printer may refuse to print on the labels. Can you post the settings you have set in the driver? Screenshots from CUPS (http://localhost:631 -> printers -> QL) would be useful, and I can see if you have anything set obviously wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735991 Title: QL-570 printer : the led flashes red and nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735991] Re: QL-570 printer : the led flashes red and nothing happens
The most common issue which can cause this is setting the Page Size incorrectly in the driver. You'll get the red flashing light if the intended page size doesn't match the label. The other issue is swapping the X and Y dimensions - the X (as far as the printer is concerned) is across the printer; the Y axis is the direction the label feeds. Note that most of the Ptouch labels are longer (Y axis) than they are wide (X axis), but the dimensions on the label box are the other way around. This means you need to specify the paper size as it is on the physical label (i.e. longer than wide) then rotate the label (e.g. gLabels's "Rotated" option). What are you trying to print, and with which application? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735991 Title: QL-570 printer : the led flashes red and nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709511] Re: Kernel 4.4.0-89 panics on boot on xenial
I just upgraded to 4.4.0-91 from the main repository, and it boots again! All my virtual machines are running too. Looks like this is fixed in something which was changed between -89 and -91. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709511 Title: Kernel 4.4.0-89 panics on boot on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709511] Re: Kernel 4.4.0-89 panics on boot on xenial
I can't provide the Apport logs; it asks me to log in to Launchpad using Lynx, then fails with "Bad bot!" Is there an alternative way to do this? The machine is a headless server. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709511 Title: Kernel 4.4.0-89 panics on boot on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709564] Re: Kernel bug after upgrade to 4.4.0-89
This looks a lot like what I'm seeing on #1709511 I'm running qemu+kvm virtual machines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709564 Title: Kernel bug after upgrade to 4.4.0-89 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709511] Re: Kernel 4.4.0-89 panics on boot on xenial
I'd like to provide a better backtrace if it's needed, but I'm not sure how to do this. Attaching lspci -vnvn ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+attachment/4929105/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709511 Title: Kernel 4.4.0-89 panics on boot on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709511] Re: Kernel 4.4.0-89 panics on boot on xenial
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+attachment/4929106/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709511 Title: Kernel 4.4.0-89 panics on boot on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709511] [NEW] Kernel 4.4.0-89 panics on boot on xenial
Public bug reported: After applying the 4.4.0-89 kernel update, I get a panic on boot. 4.4.0-87 boots normally. I expected that 4.4.0-89 would boot normally (as 4.4.0-87) instead of crashing. Systemd displays an announcement: "Starting udev Wait for Complete Device Initialization...", then I get: * "kobject: can not set name properly!" * "BUG: unable to handle kernel null pointer dereference at * A kernel error backtrace Part of the backtrace is (I'm having to enter this from a video): Call Trace: [81258ff3] ep_alloc+0x43/0xe0 [81259162] SyS_epoll_create1+0x42/0xe0 [81841f32] entry_SYSCALL_64_fastpath+0x16/0x71 RIP [811ed65b] kmem_cache_alloc_trace+0x7b/0x1f0 Kernel panic - not syncing: CRED: put_cred_rcu() sees 880231fc3cc0 with usage -1 lsb_release -rd: Description:Ubuntu 16.04.3 LTS Release:16.04 ** Affects: linux (Ubuntu) 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/1709511 Title: Kernel 4.4.0-89 panics on boot on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570
I've just released version 1.4.2 which fixes the two QL-570 bugs raised by Ladislav Laska. Bug #1607917 open to (hopefully) get the upstream packages updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604036 Title: Upgrade printer-driver-ptouch to support Brother QL-570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1604036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607917] [NEW] Update to upstream V1.4.2
Public bug reported: I've just released upstream version 1.4.2 of the P-touch printer driver to resolve two issues raised by Ladislav Laska and @Pander. https://bitbucket.org/philpem/printer-driver-ptouch Issues resolved: * NegativePrint=True causes "Unknown RLE flag" errors from CUPS (This is considered a critical bug and prevents the driver from functioning) * CutMedia=JobEnd doesn't cut. The label is printed, but not cut. =LabelEnd works as expected. I would appreciate it if the Ubuntu (and upstream Debian) maintainers could release these bugfixes in their packages. ** Affects: ptouch-driver (Ubuntu) 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/1607917 Title: Update to upstream V1.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1607917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570
I've managed to source a slightly-used QL-570 for a more reasonable price, along with (apparently) five rolls of labels. That should be arriving "soon-ish". I'll have a look at the driver when I get a spare moment. As I've said on the upstream ticket, the negative-print bug looks like the thing losing track of a buffer and may be tricky to debug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604036 Title: Upgrade printer-driver-ptouch to support Brother QL-570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1604036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570
Upstream version bumped to 1.4.1. Be advised that there's an open ticket on QL-570 support: https://bitbucket.org/philpem/printer-driver-ptouch/issues/2 /negativeprint-and-cutmedia-jobend-doesnt Main issue is that media cutting apparently doesn't work 100% as described on QL printers. Unless/until I can get a QL570 (or someone lets me borrow one for a while), debugging this might be tricky. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604036 Title: Upgrade printer-driver-ptouch to support Brother QL-570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1604036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439895] Re: QL-500 prints past end of label
This is now fixed as a result of my changes which were merged into ptouch-driver version 1.3-8ubuntu1. ** Changed in: ptouch-driver (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439895 Title: QL-500 prints past end of label To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1439895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439895] Re: QL-500 prints past end of label
The patch which fixes it for the QL-550 is debian/patches/foomatic-data- fixes.patch, already in repo, extract below: --- --- a/printer/Brother-QL-550.xml +++ b/printer/Brother-QL-550.xml @@ -28,7 +28,7 @@ resolution dpi x300/x -y300/y +y275/y /dpi /resolution consumables --- The issue is mentioned in passing in this Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555892 (search for the text 275 dpi, message 5 by Lars Wirzenius). I found another patch at https://github.com/mgrela/dropzone/blob/master /net-print/ptouch-driver/files/ptouch-driver-1.3-fix-dpi-for-QL5x0.patch which seems to do a much more comprehensive job of fixing the issue - * Makes a lot of changes to opt/Brother-Ptouch-Resolution.xml, the effects of which I'm not 100% sure about * The same 300dpi - 275dpi patch we have on the QL-550, but applied to the QL-500 too. I intend to test this on my QL-500 later today. Brother only quote the 300dpi figure, which is the resolution of the thermal print head. If all else fails, I can put together a PDF label with identical content, print it on Windows and with ptouch-driver and compare the bitmap data and see what we're getting wrong. ** Bug watch added: Debian Bug tracker #555892 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555892 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439895 Title: QL-500 prints past end of label To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1439895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439895] Re: QL-500 prints past end of label
Okay, I've merged the aforementioned patch in with a local copy of the driver. Setting the DPI to 275 is *not* the correct fix, as this throws off the aspect ratio. Squares become rectangles. A 10mm square becomes a 10x9mm square - an error of 10%. 275/0.9 = 305. So 300DPI is probably about right, accounting for measurement error. To reiterate: the printer's hardware resolution is 300x300dpi *square*. The bug lies elsewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439895 Title: QL-500 prints past end of label To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1439895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439895] Re: QL-500 prints past end of label
The driver uses MediaType to identify whether the printer is being fed with continuous paper tape (MediaType=roll) or die-cut labels (MediaType=labels). If the MediaType field in the CUPS page header (cups_page_header_t) is set to Labels (case insensitive match), then the driver is configured to tell the printer to accept die-cut labels. The MediaType fed from CUPS is always an empty string, so the driver assumes continuous paper rolls. Also, the Label Preamble (only sent to QL series printers, explained in the QL series reference manual on undocprint.) is incorrectly coded: * ESC i z (1B-69-7A) Specify print information byte n1 defines which fields in the command are valid. This is always set to zero (normal) or 0x40 (high quality printing). The printer is never told that the paper type (continuous/diecut), width or length are valid. * ESC i z (1B-69-7A) Specify print information byte n2 defines whether the printer is loaded with continuous paper tape (0x0A) or die-cut labels (0x0B). The driver uses the values 0x00 (continuous) and 0x01 (diecut). * A comment in the driver asks /* WHY DON'T WE SET MARGIN (ESC i d ...)? */ -- good question. The QL manual specifies that for die-cut labels, the margin must be set to zero. For continuous tape, apparently we should set 35 dots. Perhaps fixing the MediaType reading (so the driver correctly gets the MediaType from CUPS) and the label preamble might get this working properly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439895 Title: QL-500 prints past end of label To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1439895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342979] Re: QL-570 don't cut anymore
Patch ready for review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342979 Title: QL-570 don't cut anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1342979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439895] [NEW] QL-500 prints past end of label
Public bug reported: The QL-500 label printer prints past the end of the label in the vertical (direction of feed) direction. This means that when you print e.g. an address label and use the label cutter, several things happen: 1) Because the printer has printed past the end of the label, the head is positioned part-way into the next label 2) Because the head is positioned part-way into the next label, the optical alignment sensor cannot see the black alignment marks on the back of the labels. This causes the printer to flag an alignment error when you next try to print a label. The effect is you can only print one label at a time. There is a patch included which reduces the Y resolution of the QL-550 printer to 275 dpi. It seems like it may be necessary to extend this to the QL-500 too. ** Affects: ptouch-driver (Ubuntu) Importance: Undecided Assignee: Phil Pemberton (philpem) Status: New ** Changed in: ptouch-driver (Ubuntu) Assignee: (unassigned) = Phil Pemberton (philpem) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439895 Title: QL-500 prints past end of label To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1439895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342979] Re: QL-570 don't cut anymore
Sounds like my ESC i A patch still isn't quite right then... This is the difficulty; I only have a QL-500 (paper label printer) and a PT- 2450DX (plastic label printer) to hand. The QL series are the ones which support the ESC i A (auto cutter) command; if you send that to a PT- series printer, it'll throw an Interface Error. This is actually a mistake on my part, on line 43 of my patch (debian/patches/send-esc-i-A-for-QL-only.patch): + job_options-pixel_xfer == ULP); Should be: + job_options-pixel_xfer); This would have the effect of breaking emit_page_cmds() so that if the printer is in ULP mode, the emit_feed_cut_mirror() function is passed a 'true' (probably a 1), which is equal to pixel_xfer being RLE. That means emit_feed_cut_mirror() won't send ESC i A because it thinks it's talking to a P-Touch PT label printer. I've noticed some other issues with ptouch-driver - notably the MediaType isn't being passed through. I've done some work this week to clean up some of the cruft in the code (get rid of the deprecation warnings during 'make'). There are some problems in that some print options aren't being passed through to the driver correctly (MediaType is one). Current bug list I'm working on: * Print resolution for the QL-500 is wrong, it should be 300x275dpi for both (the QL-550 was fixed but not the QL-500) * MediaType doesn't seem to make it through from the PPD to the driver, so the driver never sets the continuous tape / cut labels option isn't loaded correctly. (I've changed this from a page option to a job option) I'll see if I can submit a patch for this bug -- I just need to try and remember how to do that, it's been a while! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342979 Title: QL-570 don't cut anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1342979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427360] Re: firefox doesn't open an url as argument
*** This bug is a duplicate of bug 1425972 *** https://bugs.launchpad.net/bugs/1425972 Bug #1425972 would seem to be related, and comment 4 on that bug includes a fix. ** This bug has been marked a duplicate of bug 1425972 Firefox no longer supports -remote parameter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427360 Title: firefox doesn't open an url as argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1427360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328798] Re: Setting default printer does not work
** Changed in: cups (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328798 Title: Setting default printer does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1328798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328798] Re: Setting default printer does not work
It appears that the printer dialogs are ignoring the system default printer, or they're picking up a default from elsewhere. If you right-click a printer in the dialog box, then select Set As Default, you get two options. One is to set it as a personal default, which updates ~/.cups/lpoptions. If you do that, then applications will detect it as the default. If you pick the set as the system-wide default and also check clear my personal default setting, applications seem to pick the first printer known to CUPS (the first one ever added) -- certainly not the one I picked to be my default printer. Doing this twice -- setting the printer as a personal default, then setting it as the system default and deselecting clear my personal default seems to get everything working as expected. However, I do have a /etc/lpoptions which points to the wrong default printer (the one I'm seeing in applications). After deleting this file, the default printer is picked up correctly! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328798 Title: Setting default printer does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1328798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332385] Re: Applications Menu plugin not showing Wine Programs submenu
I can confirm this. If I use the Whisker menu, the WINE Programs menu appears fine. But on the Applications menu, it doesn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332385 Title: Applications Menu plugin not showing Wine Programs submenu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1332385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287971] [NEW] rastertoptch sends unsupported command to PT-series printers
Public bug reported: The rastertoptch filter includes a patch which sends the ESC i A (enable cutter) command to any printer which uses this filter. Sadly, this command is only supported on the QL series, so this patch has the effect of breaking printing on most of Brother's P-Touch line (the entire PT series). The ESC i A command should only be sent to QL-series printers, and never to PT-series printers. ** Affects: ptouch-driver (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~philpem/ubuntu/trusty/ptouch-driver/fix-esc-i-a -for-pt-series -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287971 Title: rastertoptch sends unsupported command to PT-series printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1287971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264910] Re: Tmux backend can't handle spaces in window name
The problem with the F-keys is that Byobu's binding of them makes it
somewhat difficult to use Midnight Commander... hence why I prefer the
screen-style Ctrl-A-{letter} commands.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1264910
Title:
Tmux backend can't handle spaces in window name
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1264910/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1264910] Re: Tmux backend can't handle spaces in window name
The problem with the F-keys is that Byobu's binding of them makes it
somewhat difficult to use Midnight Commander... hence why I prefer the
screen-style Ctrl-A-{letter} commands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264910
Title:
Tmux backend can't handle spaces in window name
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1264910/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264910] [NEW] Tmux backend can't handle spaces in window name
Public bug reported: When hitting Ctrl-a A (ctrl-a shift-a) to rename the window, if I enter a name with spaces, Tmux briefly displays an error Usage: rename-window [-t target-window] new-name and the window retains its current name. Entering a window name without spaces works fine. Similarly, the window name cannot be set to an empty string - this results in the same error message. This seems to be a regression of #1224352. byobu 5.35-0ubuntu1 and 5.68-0ubuntu1~raring (latter from ppa:byobu/ppa) Ubuntu 13.04 Raring Ringtail ** Affects: byobu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1264910 Title: Tmux backend can't handle spaces in window name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1264910/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1264910] Re: Tmux backend can't handle spaces in window name
Also confirmed on byobu 5.68-0ubuntu1~raring from the Byobu PPA (ppa:byobu/ppa). ** Description changed: When hitting Ctrl-a A (ctrl-a shift-a) to rename the window, if I enter a name with spaces, Tmux briefly displays an error Usage: rename-window [-t target-window] new-name and the window retains its current name. Entering a window name without spaces works fine. Similarly, the window name cannot be set to an empty string - this results in the same error message. This seems to be a regression of #1224352. - byobu 5.35-0ubuntu1 + byobu 5.35-0ubuntu1 and 5.68-0ubuntu1~raring Ubuntu 13.04 Raring Ringtail ** Description changed: When hitting Ctrl-a A (ctrl-a shift-a) to rename the window, if I enter a name with spaces, Tmux briefly displays an error Usage: rename-window [-t target-window] new-name and the window retains its current name. Entering a window name without spaces works fine. Similarly, the window name cannot be set to an empty string - this results in the same error message. This seems to be a regression of #1224352. - byobu 5.35-0ubuntu1 and 5.68-0ubuntu1~raring + byobu 5.35-0ubuntu1 and 5.68-0ubuntu1~raring (latter from ppa:byobu/ppa) Ubuntu 13.04 Raring Ringtail -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1264910 Title: Tmux backend can't handle spaces in window name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1264910/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1264910] Re: Tmux backend can't handle spaces in window name
Also confirmed on byobu 5.68-0ubuntu1~raring from the Byobu PPA (ppa:byobu/ppa). ** Description changed: When hitting Ctrl-a A (ctrl-a shift-a) to rename the window, if I enter a name with spaces, Tmux briefly displays an error Usage: rename-window [-t target-window] new-name and the window retains its current name. Entering a window name without spaces works fine. Similarly, the window name cannot be set to an empty string - this results in the same error message. This seems to be a regression of #1224352. - byobu 5.35-0ubuntu1 + byobu 5.35-0ubuntu1 and 5.68-0ubuntu1~raring Ubuntu 13.04 Raring Ringtail ** Description changed: When hitting Ctrl-a A (ctrl-a shift-a) to rename the window, if I enter a name with spaces, Tmux briefly displays an error Usage: rename-window [-t target-window] new-name and the window retains its current name. Entering a window name without spaces works fine. Similarly, the window name cannot be set to an empty string - this results in the same error message. This seems to be a regression of #1224352. - byobu 5.35-0ubuntu1 and 5.68-0ubuntu1~raring + byobu 5.35-0ubuntu1 and 5.68-0ubuntu1~raring (latter from ppa:byobu/ppa) Ubuntu 13.04 Raring Ringtail -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264910 Title: Tmux backend can't handle spaces in window name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1264910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264910] [NEW] Tmux backend can't handle spaces in window name
Public bug reported: When hitting Ctrl-a A (ctrl-a shift-a) to rename the window, if I enter a name with spaces, Tmux briefly displays an error Usage: rename-window [-t target-window] new-name and the window retains its current name. Entering a window name without spaces works fine. Similarly, the window name cannot be set to an empty string - this results in the same error message. This seems to be a regression of #1224352. byobu 5.35-0ubuntu1 and 5.68-0ubuntu1~raring (latter from ppa:byobu/ppa) Ubuntu 13.04 Raring Ringtail ** Affects: byobu (Ubuntu) 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/1264910 Title: Tmux backend can't handle spaces in window name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1264910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950413] Re: Bluetooth connections stalling
@VittGam - Can you provide a link to the bug on the kernel Bugzilla? I'm also seeing this issue on Quantal - philpem@cheetah:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.10 Release:12.10 Codename: quantal philpem@cheetah:~$ sudo l2ping -s300 00:04:48:11:03:5C Ping: 00:04:48:11:03:5C from 00:0B:0D:62:F5:50 (data size 300) ... 0 bytes from 00:04:48:11:03:5C id 0 time 39.78ms 0 bytes from 00:04:48:11:03:5C id 1 time 21.88ms 0 bytes from 00:04:48:11:03:5C id 2 time 20.50ms 0 bytes from 00:04:48:11:03:5C id 3 time 19.72ms 0 bytes from 00:04:48:11:03:5C id 4 time 20.03ms 0 bytes from 00:04:48:11:03:5C id 5 time 19.80ms 0 bytes from 00:04:48:11:03:5C id 6 time 19.92ms 0 bytes from 00:04:48:11:03:5C id 7 time 19.89ms 0 bytes from 00:04:48:11:03:5C id 8 time 20.39ms 0 bytes from 00:04:48:11:03:5C id 9 time 19.29ms no response from 00:04:48:11:03:5C: id 10 no response from 00:04:48:11:03:5C: id 11 no response from 00:04:48:11:03:5C: id 12 no response from 00:04:48:11:03:5C: id 13 no response from 00:04:48:11:03:5C: id 14 Recv failed: Software caused connection abort philpem@cheetah:~$ dmesg |tail [23687.938626] usb 2-1.1.2: USB disconnect, device number 11 [23687.959165] usb 2-1.1.3: USB disconnect, device number 12 [23690.679189] usb 2-1.1: new full-speed USB device number 13 using ehci_hcd [23690.794663] usb 2-1.1: New USB device found, idVendor=0a5c, idProduct=200a [23690.794669] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [23690.794672] usb 2-1.1: Product: BCM92035DGROM [23690.794674] usb 2-1.1: Manufacturer: Broadcom [23690.794677] usb 2-1.1: SerialNumber: 000B0D62F550 [24048.803235] Bluetooth: hci0 link tx timeout [24048.803243] Bluetooth: hci0 killing stalled connection 00:04:48:11:03:5C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950413 Title: Bluetooth connections stalling To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/950413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 970358] Re: Flash Video has wrong colors
I'm seeing this too. It's like setting the hue slider to +100 in smplayer. So basically, Flash is messing up the hue setting when X video acceleration is enabled. A nasty workaround is to right-click a flash video and select Settings. On the first tab, disable hardware acceleration. That'll get the videos to play with the right colours, but they might skip, stutter or Flash might hog the CPU a bit more :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/970358 Title: Flash Video has wrong colors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/970358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911873] [NEW] No way to manually restrict DHCP to one interface
Public bug reported: This is more a feature request than an actual bug. When Orchestra installs and Cobbler is first configured with a server, it defaults to listening on the first available network interface (usually eth0) for DHCP requests. This causes problems when Orchestra is used to bring up a cluster of virtual machines running on one physical server -- the virtual machines send DHCP requests over a host-only interface, but dnsmasq (the DNS/DHCP server Orchestra uses) never sees them. This leaves the VMs stuck waiting for DHCP data which will never arrive... The solution is twofold: - Initially, use Virt-Manager or similar to create a virtual network for all the virtual machines which are to be managed by Orchestra. Call it, for example PxeReload. Virt-Manager will tell you what the physical network device name is -- in my case, it was virbr1. Set this as active, autostarting on boot, with DHCP disabled and the IP range you desire (I used 192.168.100.0/24). Forwarding should be set to Isolated Network (otherwise it will stomp all over your LAN's DHCP server) - Install orchestra-server. Provide details about your network. In my case, I used: Password for cobbler user -- (like I'd tell you that!) Boot and PXE server IP -- was autodetected OK, but in my case, 192.168.100.1 Enable Orchestra Managed DHCP/DNS? Yes DHCP Range: 192.168.100.5,192.168.100.200 Default Gateway for DHCP clients: leave blank (it's the Provisioning server) Domain name: virtual.lan (I just used virtual) Once you've done this, you can follow the instructions in http://cloud.ubuntu.com/2011/09/oneiric-server-deploy-server-fleets-p2/ and/or http://cloud.ubuntu.com/2011/10/getting-started-with-ubuntu- orchestra-servers-in-concert/ to add the virtual machine (created with virt-manager, VirtualBox, VMware or whatever) to Cobbler. Now you need to edit Cobbler's DNSMasq config template -- - sudo vim /etc/cobbler/dnsmasq.template After domain=virtual, insert these lines: # Restrict DNSMasq DHCP and DNS to host-only virtual Ethernet bridge used for PXE reloads interface = virbr1 Save and exit. Run sudo cobbler sync and everything should work. If DNSMasq fails to restart, sudo killall dnsmasq then sudo service dnsmasq restart (sometimes the rcscript thinks DNSMasq is stopped when in fact it is still running). After all this, you should have a server, hosting virtual machines which you can create, configure, set up, tear down and reinstall to your heart's content. ** Affects: orchestra (Ubuntu) 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/911873 Title: No way to manually restrict DHCP to one interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orchestra/+bug/911873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911873] Re: No way to manually restrict DHCP to one interface
I forgot something -- after interface = (virbr1, br0, or whatever) you need to add: bind-interfaces Otherwise dnsmasq will still bind to all interfaces instead of just the assigned interface. Another thing worth mentioning is that virt-manager / libvirt uses dnsmasq internally. It gets VERY upset if you try and run Cobbler on a bridged interface. What you need to do is create a bridge with no assigned interfaces in /etc/network/interfaces (I called mine 'vmpxe' -- Virtual Machine PXE), give it an IP address and so forth, and attach Orchestra's dnsmasq instance to that interface. Then when you create the VM, attach the network adapter to that interface (i.e. specify shared device name, then the name of the bridge) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911873 Title: No way to manually restrict DHCP to one interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orchestra/+bug/911873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912065] [NEW] Orchestra should allow for multi-NIC servers
Public bug reported: Scenario: You have a cluster of servers (virtual or otherwise). Each server has two NICs -- one connects to the LAN, another connects to a private network which is used to bring up the servers over PXE, reinstall them and so forth. The PXE network is segregated to allow Orchestra to be installed on the virtual-machine host, or to segregate PXE reinstall traffic from normal network traffic. Both interfaces are configured over DHCP, and config settings for both interfaces (MAC address) are present in the Cobbler web config. Problem: When the virtual server reboots for the first time, only one interface will come up -- the interface which was used by PXE and the Ubuntu Installer to bring up the system. Both interfaces need to be brought up, otherwise the machine will not be accessible from the LAN. ** Affects: orchestra (Ubuntu) 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/912065 Title: Orchestra should allow for multi-NIC servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orchestra/+bug/912065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912067] [NEW] Orchestra should allow installation username/password to be configured
Public bug reported: When installing a new server with Orchestra, the username and password on the new install are forced to a default of 'ubuntu' for both. There does not appear to be an easy way to change this. Orchestra should make it possible to change the default username and password. Alternatively, if this is already possible, the procedure for doing so should be documented in an obvious place (perhaps a Help section on the Cobbler web-admin panel, or a chapter in the Ubuntu Server Guide) ** Affects: orchestra (Ubuntu) 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/912067 Title: Orchestra should allow installation username/password to be configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orchestra/+bug/912067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 910611] [NEW] Kernel build system installs modules in the wrong place
Public bug reported: Oneiric kernels seem to have an issue with the version numbering on the kernel build system not being set correctly: $ uname -a Linux cheetah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ head /lib/modules/3.0.0-14-generic/build/Makefile VERSION = 3 PATCHLEVEL = 0 SUBLEVEL = 9 EXTRAVERSION = NAME = Sneaky Weasel What this means is that if you use Module-Assistant to build a driver (e.g. vloopback) or install WebcamStudio (http://www.ws4gl.org/) then the module will be installed in the wrong place -- specifically, the kernel's build system will install the modules in /lib/modules/3.0.9, when they should be installed in /lib/modules/3.0.0-14-generic. This happens with the r8168 (Realtek Ethernet) driver, WebcamStudio, and several other modules. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-14-generic 3.0.0-14.23 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn] Subdevices: 0/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philpem2273 F pulseaudio philpem2280 F xfce4-volumed /dev/snd/pcmC0D0c: philpem2273 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'XFi'/'Creative X-Fi 20K2 SB0880' Mixer name : '20K2' Components : '' Controls : 29 Simple ctrls : 10 Date: Sun Jan 1 18:34:00 2012 HibernationDevice: RESUME=UUID=dbc4d840-7fcc-47f8-9b23-3039abb4055e InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=9eb32ed4-f0a3-4e50-9b8a-95b8f5be1b64 ro nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-14-generic N/A linux-backports-modules-3.0.0-14-generic N/A linux-firmware1.60 RfKill: 14: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: Z68AP-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68AP-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/910611 Title: Kernel build system installs modules in the wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/910611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 910611] Re: Kernel build system installs modules in the wrong place
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/910611 Title: Kernel build system installs modules in the wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/910611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744619] Re: Screen doesn't unlock; stuck on Checking
I usually see this happen if my ecryptfs home directory has somehow become unmounted... There's an outstanding bug in Sudo 1.8.2 which causes this (and is due to be fixed in 1.8.3), see Debian bug #639391. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744619 Title: Screen doesn't unlock; stuck on Checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/744619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659143] Re: 64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with ralink [1814:0781]
Doesn't seem to fix the RT3090 here. If I force modprobe to load the rt2800pci or rt2x00pci driver, the card will scan for networks quite happily, but won't establish a connection (WPA encrypted, pre-shared password mode). If I go back to blacklisting rt2800pci et al, then the (insanely buggy) rt2860sta driver loads, and the card works (more or less) fine, aside from occasionally falling over after a hibernate or suspend cycle. lspci -v: 02:00.0 Network controller: RaLink RT3090 Wireless 802.11n 1T/1R PCIe Subsystem: Micro-Star International Co., Ltd. Device 6891 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at feaf (32-bit, non-prefetchable) [size=64K] Capabilities: access denied Kernel driver in use: rt2860 Kernel modules: rt2800pci, rt2860sta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659143 Title: 64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with ralink [1814:0781] -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659143] Re: 64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with ralink [1814:0781]
OK, I renamed the driver, then rebooted and modprobed rt2800pci. This had the nice side-effect of kicking the other laptop off the WiFi, and I couldn't get it to associate. rmmod -rv rt2800pci followed by modprobe -v rt2860sta got me a Kernel Panic. When the laptop rebooted, the BIOS threw up this warning: INFO [CHIPSET]: A HyperTransport Sync Flood event was detected on the last boot. Press F1 to continue booting. Rebooted, renamed rt2860sta back and re-blacklisted rt2800pci, and now my WiFi is working again. iwlist wlan0 scan: phil...@ryoko:~$ iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:14:BF:9E:46:17 Protocol:802.11g ESSID:Stargate Mode:Managed Channel:11 Quality:100/100 Signal level:-41 dBm Noise level:-83 dBm Encryption key:on Bit Rates:11 Mb/s IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659143 Title: 64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with ralink [1814:0781] -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659143] Re: 64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with ralink [1814:0781]
Did it panic on unloading rt2800pci or on loading rt2860sta? That sounds a bit like bug 662288. On loading rt2860sta after unloading rt2800pci. Anyway, we need a trace of that panic. Maybe comment 15 of bug 662288 can help you get one. Might be a bit hard when the machine locks solid after the module loads... Serial console would be one option, if this machine had any serial ports... kicking the other laptop off Not sure what you mean here. For as long as the laptop running rt2800pci was powered up (and running rt2800pci), the other laptop sitting across the room couldn't connect to the access point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659143 Title: 64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with ralink [1814:0781] -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659143] Re: 64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with ralink [1814:0781]
You might want to take a look at bug 594866; that's the thread where I originally reported my issues, and exactly describes what was happening with the RT3090 in my MSI U230 netbook. No errors relating to firmware loading, but I can't connect to the WLAN... Load rt2860sta instead (by blacklisting per the bug I listed above), and the card works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659143 Title: 64bit-only: regression: kernels =2.6.34: rt2800pci: load firmware Error with ralink [1814:0781] -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594866] Re: [Maverick][2.6.35] RT2860 (ralink) support seems to be broken (it fails to connect to secured wireless networks)
@Bruno #14 -- thanks for that, works like a charm on my MSI U230 (Ralink RT3090) running Maverick and kernels 2.6.35-22-generic and 2.6.35-19-generic. -19 throws a load of PBF system register not ready errors in dmesg, -22 doesn't seem to do that but won't associate with the access point. After rebooting from -22 (with the default modules loaded), the BIOS reports a HyperTransport Sync Flood error. Blacklist the modules and it works great. -- [Maverick][2.6.35] RT2860 (ralink) support seems to be broken (it fails to connect to secured wireless networks) https://bugs.launchpad.net/bugs/594866 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 60315] Re: Launching HTTP Cache Cleaner
Same thing in 9.04 x64, Amarok 2.0.2. -- Launching HTTP Cache Cleaner https://bugs.launchpad.net/bugs/60315 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde4libs in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 257894] Re: VGA-out dies after a while on Eee 1000H
@Sean Bridges: I'd try this -- Exit X -- either: sudo /etc/init.d/gdm stop Or: sudo /etc/init.d/kdm stop When you land at the shell: sudo apt-get clean all sudo apt-get purge libdrm2 libdrm-intel1 xserver-xorg-video-intel -- if apt-get removes anything other than these three packages, add the packages it deletes to the list below ... remove the PPA from /etc/apt/sources.list or /etc/apt/sources.list.d ... sudo apt-get update sudo apt-get install libdrm2 libdrm-intel1 xserver-xorg-video-intel sudo reboot That should get rid of any traces of the 2.5.1 drivers. -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
OK, the Eee's been running for about two days now, and no VGA-out blanking. This is with stock Intrepid, upgraded from Hardy. I think upgrading to 8.10 fixed it. That doesn't really help the folks who are running Hardy, but my 1000H is working fine, ergo problem solved :) Thanks for the help, guys. -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
It's probably worth saying that the only option I have set against the intel graphics driver in xorg.conf is: Option ModeDebug yes I'm about to turn this off... -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
Strangely enough I'm not seeing this happening on Ubuntu 8.10 at all. For reference: phil...@cougar:~$ lsb_release -rd Description:Ubuntu 8.10 Release:8.10 phil...@cougar:~$ uname -a Linux cougar.homenet.philpem.me.uk 2.6.27-8-eeepc #1 SMP Sun Nov 16 12:02:12 MST 2008 i686 GNU/Linux The kernel is the array.org EeePC Enhanced kernel, everything else is stock, right down to the graphics driver (2:2.4.1-1ubuntu10). Additionally, a few other visual glitches seem to have vanished without trace -- if I Alt-tabbed away from then back to Amarok on 8.04.1 with the visualiser off, the whole vis panel filled with random noise. Similarly, the checkboxes and radio buttons that weren't being drawn correctly (when selected, they were clear, and the checks/bullets never displayed) are now drawing fine... Uptime five hours, three of those using the VGA output. I'm tempted to call this fixed, but will leave the Eee powered up overnight with one of the Reallyslick OpenGL screensavers running to see if it really /is/ fixed. -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
Right, based on the changelogs for those packages, the intel-gfx- testing packages should be identical to the ones I backported to Hardy on the 16th. 2.5.1 didn't seem to lose VGA-out, and I was using it for the best part of a day. I'll look into doing a full backup and an upgrade to Intrepid on my Eee tomorrow; for now, I've got a basic Intrepid install on an 8GB USB flashdrive. 2.5.1 seems stable, but I've only had it running for a few minutes. I've got some development work on my to-do list, and the code is on the Eee, so I think I'll use that as an excuse to hook up the KVM and do an 8-hour long-term test :) Certainty that the bug is fixed: currently hovering at around 10% Cheers for the help thus far guys, it's much appreciated. -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
I've just backported 2.5.1 from Jaunty to Hardy -- this involved backporting and installing: libdrm 2.4.1-0ubuntu7 libpciaccess 0.10.3-1 xserver-xorg-video-intel 2.5.1-1ubuntu6 Switching from internal to external monitor worked, until I started running OpenGL screensavers (Euphoria fullscreen, Space, Solarwinds, Particle Fountain, Krotation, Kpendulum, Gravity and Flux for a few seconds each in the preview box, then finally Fireworks 3D fullscreen). The VGA display went blank (monitor showed sync, but no video) shortly after Fireworks 3D did the Welcome to KDE 3.5.9 part of its animation. Fn-F8 got the LCD running again, but switching from LCD to VGA again produces the blank screen. lspci, lsb-release, etc. output is the same as the above. Xorg log attached. ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/20466165/Xorg.0.log -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
xorg.conf ** Attachment added: xorg.conf.1strun http://launchpadlibrarian.net/20466282/xorg.conf.1strun -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
OK, backporting libdrm and xorg-video-intel completely broke DRI... I got a driOpen failed error in xorg.log, and completely lost 3D. Ugh. Looks like I need to do some more research to find out what else needs rebuilding (hopefully not all of Xorg...) -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
OK, I've modified my Xorg config a little: Section Device Identifier Configured Video Device Driver intel # VideoRam16384 # Option ForceEnablePipeA Option ModeDebug yes Option FramebufferCompressionoff EndSection [...] Section Screen Identifier Default Screen Monitor Configured Monitor Device Configured Video Device SubSection Display Depth 16 Virtual 20482048 EndSubSection SubSection Display Depth 24 Virtual 20482048 EndSubSection EndSection This seems to have resolved the pipe underruns, but I'm not 100% convinced yet. It's been about 10 minutes since I last restarted X, I played with the screensavers a little at the start, and VGA is still up and running. -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 290624] Re: Stack smashing in libcdk5 calendar applet
This was also reported in Debian #452401 last year by Ron Murray: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452401 Nearly a year later, the bug is still listed as open, unfixed... -- Stack smashing in libcdk5 calendar applet https://bugs.launchpad.net/bugs/290624 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 290624] [NEW] Stack smashing in libcdk5 calendar applet
Public bug reported: Binary package hint: libcdk5 Ubuntu release: 8.04.1 Source Package: libcdk5 5.0.20060507-1 What I expected to happen: I expected the Calendar widget, and calendar_ex example program to work correctly. What actually happened: glibc Stack Smashing alert and SIGABORT. I compiled the demo applications that were included in CDK 5.0.20060507-1 (after some modifications to the Makefile), and the calendar example failed to run. In fact, instead of running, it produced the following backtrace output: *** stack smashing detected ***: ./calendar_ex terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7ecc138] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb7ecc0f0] /usr/lib/libcdk.so.5[0xb7f96314] /usr/lib/libcdk.so.5[0xb7f75ccd] ./calendar_ex[0x8048dc6] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7df5450] ./calendar_ex[0x8048a01] === Memory map: 08048000-0804a000 r-xp 08:02 452935 /home/philpem/Projects/cdk_tests/calendar_ex 0804a000-0804b000 rw-p 1000 08:02 452935 /home/philpem/Projects/cdk_tests/calendar_ex 0804b000-0806c000 rw-p 0804b000 00:00 0 [heap] b7c62000-b7c6c000 r-xp 08:02 827445 /lib/libgcc_s.so.1 b7c6c000-b7c6d000 rw-p a000 08:02 827445 /lib/libgcc_s.so.1 b7c81000-b7cba000 rw-p b7c81000 00:00 0 b7cba000-b7cf9000 r--p 08:02 1740016 /usr/lib/locale/en_GB.utf8/LC_CTYPE b7cf9000-b7dda000 r--p 08:02 1740015 /usr/lib/locale/en_GB.utf8/LC_COLLATE b7dda000-b7ddb000 rw-p b7dda000 00:00 0 b7ddb000-b7ddd000 r-xp 08:02 844839 /lib/tls/i686/cmov/libdl-2.7.so b7ddd000-b7ddf000 rw-p 1000 08:02 844839 /lib/tls/i686/cmov/libdl-2.7.so b7ddf000-b7f28000 r-xp 08:02 844835 /lib/tls/i686/cmov/libc-2.7.so b7f28000-b7f29000 r--p 00149000 08:02 844835 /lib/tls/i686/cmov/libc-2.7.so b7f29000-b7f2b000 rw-p 0014a000 08:02 844835 /lib/tls/i686/cmov/libc-2.7.so b7f2b000-b7f2f000 rw-p b7f2b000 00:00 0 b7f2f000-b7f5c000 r-xp 08:02 827473 /lib/libncurses.so.5.6 b7f5c000-b7f5f000 rw-p 0002c000 08:02 827473 /lib/libncurses.so.5.6 b7f5f000-b7f98000 r-xp 08:02 1714974/usr/lib/libcdk.so.5.0 b7f98000-b7f9a000 rw-p 00038000 08:02 1714974/usr/lib/libcdk.so.5.0 b7f9d000-b7f9e000 r--p 08:02 1740021 /usr/lib/locale/en_GB.utf8/LC_NUMERIC b7f9e000-b7f9f000 r--p 08:02 1738503 /usr/lib/locale/en_GB.utf8/LC_TIME b7f9f000-b7fa r--p 08:02 1739018 /usr/lib/locale/en_GB.utf8/LC_MONETARY b7fa-b7fa1000 r--p 08:02 1753138 /usr/lib/locale/en_GB.utf8/LC_MESSAGES/SYS_LC_MESSAGES b7fa1000-b7fa2000 r--p 08:02 1740022 /usr/lib/locale/en_GB.utf8/LC_PAPER b7fa2000-b7fa3000 r--p 08:02 1739965 /usr/lib/locale/en_GB.utf8/LC_NAME b7fa3000-b7fa4000 r--p 08:02 1739013 /usr/lib/locale/en_GB.utf8/LC_ADDRESS b7fa4000-b7fa5000 r--p 08:02 1738989 /usr/lib/locale/en_GB.utf8/LC_TELEPHONE b7fa5000-b7fa6000 r--p 08:02 1740018 /usr/lib/locale/en_GB.utf8/LC_MEASUREMENT b7fa6000-b7fad000 r--s 08:02 1723071 /usr/lib/gconv/gconv-modules.cache b7fad000-b7fae000 r--p 08:02 1738496 /usr/lib/locale/en_GB.utf8/LC_IDENTIFICATION b7fae000-b7fb rw-p b7fae000 00:00 0 b7fb-b7fb1000 r-xp b7fb 00:00 0 [vdso] b7fb1000-b7fcb000 r-xp 08:02 927069 /lib/ld-2.7.so b7fcb000-b7fcd000 rw-p 00019000 08:02 927069 /lib/ld-2.7.so bfb5e000-bfb73000 rw-p bffeb000 00:00 0 [stack] Aborted Due to the lack of debug symbols in the release libraries, I recompiled libcdk with CFLAGS=-g -ggdb, then relinked calendar_ex against the new static library: CFLAGS=-g -ggdb bash ./configure make make cdkshlib mkdir -p /tmp/cdkdebug cp libcdk.* /tmp/cdkdebug Then to rebuild calendar_ex (the -DExitProgram is a modification that removes the need for cdk_test.h -- I search/replaced all instances of cdk_test.h with cdk/cdk.h in the example .c source files): gcc -Wall -g -ggdb -DHAVE_CONFIG_H -I../include -I./../include -I. -D_GNU_SOURCE -DExitProgram=exit calendar_ex.c -o calendar_ex -L.. -lcdk -lncurses -L/tmp/cdkdebug After running the app again through gdb, it still crashed. The backtrace pointed to an error in the function drawCDKCalendarField in calendar.c. It seems the underlying issue is that a statically-allocated string is being declared, and being overrun by the sprintf at line 498. Temp is declared on line 462, as a char[10]. The sprintf creates a string containing the month name and day number, separated by a space, and with a trailing comma. That means that if the day number is between 1 and 9, the length of the final string will be strlen(monthname)+3, or strlen(monthname)+4 for a 2-digit day (excluding the trailing null). As the variable is allocated as 10 bytes, then the month name can be no longer than 5 characters (noting the trailing null). Therefore, this code
[Bug 290624] Re: Stack smashing in libcdk5 calendar applet
** Attachment added: Fix for stack smashing bug http://launchpadlibrarian.net/18978623/cdk-stacksmashing-fix.patch -- Stack smashing in libcdk5 calendar applet https://bugs.launchpad.net/bugs/290624 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 118181] Re: Possible bug in libcdk5-dev
Not seeing this on Hardy with latest libcdk5-dev. -- Possible bug in libcdk5-dev https://bugs.launchpad.net/bugs/118181 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 257894] Re: VGA-out dies after a while on Eee 1000H
I've just done some more testing: xserver-xorg-video-intel_2.3.2-2_i386.deb (from Debian lenny): - Exhibits the same bug. xserver-xorg-video-intel_2.4.0~melchiorre-5_i386.deb (from http://melchiorre.wordpress.com/2008/07/31/driver-intel-240-deb-package/) - After adding Driver 'intel' to xorg.conf, works fine. Does not appear to exhibit the same issue as 2.3.2-2 and 2.2.1-ubuntu12/2.2.1-ubuntu13.6. Still testing to see if 2.4.0 has fixed the bug. -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] Re: VGA-out dies after a while on Eee 1000H
Update: same problem on 2.4.0 :( -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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 257894] [NEW] VGA-out dies after a while on Eee 1000H
Public bug reported: Binary package hint: xserver-xorg-video-intel I am using Kubuntu 8.04.1 (with all current updates installed) on an ASUS Eee 1000H mini-notebook PC. I'm also using xrandr to switch off the LCD and use an external monitor with the machine while it's on my desk. Xorg video driver is xserver-xorg-video-intel 2:2.2.1-1ubuntu13.6. Video chipset is an Intel 945GME. The problem is, if I switch from LCD to the VGA-out with xrandr, after a few minutes to a few hours, the screen will change to a single solid colour. Switching back to the LCD allows me to interact with the machine again, but VGA-out remains black when I switch back to VGA again. Sync is being output on the VGA port as the monitor is showing the resolution I set it to in the Info screen. Only rebooting the machine will allow VGA-out to work again -- simply restarting X has no effect on the VGA- out issue. I've tried enabling ForceEnablePipeA, but this had no effect on the problem. Typically, the video starts glitching when I switch from LCD to VGA-out. It's about once every few minutes, and looks like the screen has missed a sync pulse or something -- the video is shifted right (or maybe left?) a bit for around 1 video frame. This starts happening a few minutes before the video locks, but may not be related. I have a suspicion that the recent driver update pushed to hardy-updates may be the cause of this. I am going to revert to 2:2.2.1-1ubuntu12 later and see if this resolves the issue. Other people have included the following in there bug reports -- I can't see any firm requirement for the lspci dumps, but I have included them anyway as they might be helpful, if only for accurately IDing the chipset. $ lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 $ uname -a Linux cougar.homenet.philpem.me.uk 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux $ lspci -nn 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) $ sudo lspci -vvvnn 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8340] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at f7f0 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at dc00 [size=8] Region 2: Memory at d000 (32-bit, prefetchable) [size=256M] Region 3: Memory at f7ec (32-bit, non-prefetchable) [size=256K] Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Address: Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8340] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Region 0: Memory at f7f8 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: xserver-xorg-video-intel I am using Kubuntu 8.04.1 (with all current updates installed) on an ASUS Eee 1000H mini-notebook PC. I'm also using xrandr to switch off the LCD and use an external monitor with the machine while it's on my desk. Xorg video driver is xserver-xorg-video-intel 2:2.2.1-1ubuntu13.6. Video chipset is an Intel 945GME. The problem is, if I switch from LCD to the VGA-out with xrandr, after a few minutes to a few hours, the screen will change to a single solid colour. Switching back to the LCD allows me to interact with the machine - again, but VGA-out remains black. Sync is being output on the VGA port - as the monitor is showing the resolution I set it to in the Info screen. + again, but VGA-out remains black when I switch back to VGA again. Sync + is being
[Bug 257894] Re: VGA-out dies after a while on Eee 1000H
I've done some more testing: - Reverting to 2:2.2.1-ubuntu12 didn't fix anything. The problem still exists on the older driver. - Setting KDE to use the Solar Winds (GL) OpenGL screensaver seems to reduce the time required to reproduce this bug. Activate the screensaver, and wait for it to start. Leave it for a few minutes, then move the mouse. The machine will (sometimes) crash. When it does, you'll need to power off and back on again (hold the power switch down until the 1000H powers off, then wait a few seconds and press it again). When the machine reboots, switch to VGA-out. After a few minutes, the screen will black out, but the machine will still respond to keypresses. -- VGA-out dies after a while on Eee 1000H https://bugs.launchpad.net/bugs/257894 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
