[Bug 1490692] Re: package apt-config-auto-update (not installed) failed to install/upgrade: trying to overwrite '/etc/apt/apt.conf.d/10periodic', which is also in package update-notifier-common 3.162
Not so sure about it being "fixed" - I just encountered it when attempting to (perhaps mistakenly) install apt-config-auto-update on 16.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490692 Title: package apt-config-auto-update (not installed) failed to install/upgrade: trying to overwrite '/etc/apt/apt.conf.d/10periodic', which is also in package update-notifier-common 3.162 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pk-update-icon/+bug/1490692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558753] Re: AppArmor denying CUPS authentication against PAM on AD joined system (SSSD-based)
Still a problem in 16.04 LTS. Workaround is simply "aa-complain cupsd" but that's kind of crummy... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558753 Title: AppArmor denying CUPS authentication against PAM on AD joined system (SSSD-based) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1558753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588862] Re: legacy-only plugin does not load in Xenial
Appears to be the same bug as #1578193 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588862 Title: legacy-only plugin does not load in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-ssh/+bug/1588862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588862] [NEW] legacy-only plugin does not load in Xenial
Public bug reported: After installing network-manager-ssh package in 16.04 LTS, nothing new appears in the Add Connection dialog box, but I do get this message in the system logs: Jun 03 09:58:40 sa1 gnome-session[27861]: ** Message: vpn: (ssh,/etc/NetworkManager/VPN/nm-ssh-service.name) cannot load legacy- only plugin (FWIW, the same bug affects -ssh, -openconnect, -iodine, and -strongswan plugins; only OpenVPN, PPTP and VPNC are available.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-ssh 0.9.4-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Jun 3 10:07:38 2016 InstallationDate: Installed on 2016-05-28 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-ssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-ssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588862 Title: legacy-only plugin does not load in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-ssh/+bug/1588862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249777] Re: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation
Confirming that this problem still affects 16.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249777 Title: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806761] Re: Feature Request: Upstart scripts for nslcd
Ah... I had failed to notice the component from was universe. I believed, incorrectly, that it was a Canonical-supported component. I'll switch to SSSD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806761 Title: Feature Request: Upstart scripts for nslcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449168] [NEW] nslcd is not reliable
Public bug reported: nslcd(8) simply isn't reliable in a variety of situations. https://bugs.launchpad.net/ubuntu/+source/nss-ldapd/+bug/227675 https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1029656 https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1374434 https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1449163 all could be solved or mitigated, as far as I can tell, by converting nslcd from sysvinit to upstart, as documented in this issue that has been open since 12.x: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761 I'm filing this new bug with the correct package name in the hopes this gets some attention... currently this makes Ubuntu pretty useless in a heterogenous environment where RFC2307 use is required. ** Affects: nss-pam-ldapd (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/1449168 Title: nslcd is not reliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1449168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449163] [NEW] nslcd exits prematurely at boot
Public bug reported: When using uri DNS in /etc/nslcd.conf, nslcd exits prematurely at boot because network-manager hasn't finished configuring networking yet. The relevant message is ONLY present in boot.log (nowhere else!), which made troubleshooting this a pain in the butt. /var/log/boot.log contains: root@dev2:~# cat /var/log/boot.log * Stopping adjust system clock and timezone [ OK ] * Stopping Read required files in advance [ OK ] * Starting Mount filesystems on boot [ OK ] * Starting Populate /dev filesystem [ OK ] * Starting Populate and link to /run filesystem [ OK ] * Stopping Populate /dev filesystem [ OK ] * Stopping Populate and link to /run filesystem [ OK ] * Stopping Track if upstart is running in a container [ OK ] * Starting Fix-up /sys/kernel/debug filesystem [ OK ] * Stopping Fix-up /sys/kernel/debug filesystem [ OK ] * Starting Initialize or finalize resolvconf [ OK ] * Starting set console keymap [ OK ] * Starting Signal sysvinit that virtual filesystems are mounted [ OK ] * Starting Signal sysvinit that virtual filesystems are mounted [ OK ] * Starting Bridge udev events into upstart [ OK ] * Starting Signal sysvinit that remote filesystems are mounted [ OK ] * Starting device node and kernel event manager [ OK ] * Starting Signal sysvinit that the rootfs is mounted [ OK ] * Stopping set console keymap [ OK ] * Starting load modules from /etc/modules [ OK ] * Starting cold plug devices [ OK ] * Starting log initial device creation [ OK ] * Starting Clean /tmp directory [ OK ] * Starting Uncomplicated firewall [ OK ] * Stopping Read required files in advance (for other mountpoints) [ OK ] * Stopping load modules from /etc/modules [ OK ] * Stopping Clean /tmp directory [ OK ] * Starting Signal sysvinit that local filesystems are mounted [ OK ] * Starting Flush boot log to disk [ OK ] * Starting flush early job output to logs [ OK ] * Stopping Mount filesystems on boot [ OK ] * Starting configure network device security [ OK ] * Starting configure network device security [ OK ] * Starting Enabling additional
[Bug 806761] Re: Feature Request: Upstart scripts for nslcd
CADT, anyone? As we're waiting for a fix to come out, the bug expires because we're all waiting. I guess that's one way to solve the problem... ** Changed in: nss-pam-ldapd (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806761 Title: Feature Request: Upstart scripts for nslcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806761] Re: Feature Request: Upstart scripts for nslcd
Per #54... yes, but for one thing: 14.04 LTS is still in the support cycle for several more years, and we're just now starting to deploy 14.04 across the board for developer desktops at work. Because I have more than one AD server, I'm using uri DNS (see https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1449168) and that fails because of the lack of dependency tracking between nslcd and network-manager. All the workstations I've integrated are unusable after reboot) because nslcd starts up before network-manager finishes setting up the DHCP interface, and the DNS lookup fails. Since the problem is known AND a solution is known, I would expect a fix to come out in the 14.04 LTS support cycle. Or is Canonical also subject to CADT (http://www.jwz.org/doc/cadt.html) ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806761 Title: Feature Request: Upstart scripts for nslcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254374] Re: unable to install 13.10 on Intel RAID0 volume
Fixed in Ubutun 14.10 (utopic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254374 Title: unable to install 13.10 on Intel RAID0 volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254374] Re: unable to install 13.10 on Intel RAID0 volume
Really? No-one comments on a bug for 60 days and it magically stops being a bug? WTF, Canonical? ** Changed in: ubiquity (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254374 Title: unable to install 13.10 on Intel RAID0 volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254374] Re: unable to install 13.10 on Intel RAID0 volume
By bogus, I mean the graphical display is referencing partitions and devices that don't/can't actually exist, and/or duplicate references to the same partition or device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254374 Title: unable to install 13.10 on Intel RAID0 volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1254374] Re: unable to install 13.10 on Intel RAID0 volume
On 14-02-15 02:59 PM, Phillip Susi wrote: Could you be more specific? Why can't they exist? And the duplicate line is normal. It's weird, but not harmful. Not at this time, as reproducing the problem would involve destroying my existing, functional, 12.04 install. (Or backing up and restoring, which sounds equally appealing to me right now.) -- -Adam Thompson athom...@athompso.net -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254374 Title: unable to install 13.10 on Intel RAID0 volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215098] Re: iPhone with iOS 7 does not work on Ubuntu
i have also tried numerous distro's and it so far does not work for me in Ubuntu, Linux Mint, Zorin OS, Opensuse, Arch Linux, and Fedora (i also have not tried any other distribution, JTLY) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215098 Title: iPhone with iOS 7 does not work on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1215098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254374] [NEW] unable to install 13.10 on Intel RAID0 volume
Public bug reported: Dell Precision T5400, all firmware up-to-date. 2 x 250GB HDDs, combined into a single RAID0 (striped) volume using Intel onboard RAID. (Note: the same system works fine if I attempt to install *without* the Intel RAID volume configured.) Ubiquity gets very confused with the /dev/mapper entries when doing manual partitioning, usually - but not always! - displaying bogus p0/p1/p2/p5 entries. Doesn't matter if the disks are zeroed beforehand or not, same results. Regardless of which partitioning option is chosen (automatic, encrypt, lvm, manual) the installer advances to the tzsetup screen but displays a modal dialog box titled (literally) ??? ??? with the text ??? ??? in it, and the dialog cannot be dismissed. Log files attached, syslog is longer and represents a full boot into the livecd environment and multiple ubiquity runs, the ubiquity logfiles and partman logfiles are from a single, minimal run that exhibits the problem. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: ubi-partman ** Attachment added: ubiquity-logs.tgz https://bugs.launchpad.net/bugs/1254374/+attachment/3915711/+files/ubiquity-logs.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254374 Title: unable to install 13.10 on Intel RAID0 volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254374] Re: unable to install 13.10 on Intel RAID0 volume
** Attachment added: I wasn't joking about the modal dialog box title... https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+attachment/3915712/+files/Screenshot%20from%202013-11-24%2002%3A56%3A03.png ** Tags added: ubi-partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254374 Title: unable to install 13.10 on Intel RAID0 volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254374] Re: unable to install 13.10 on Intel RAID0 volume
I'd rank this problem as critical, since it utterly prevents me from reinstalling Ubuntu on my primary workstation. There is no known workaround (yet). I have tried pre-partitioning the disk and pre-formatting the partitions, that didn't make any difference. (In fact, ubiquity insists it's going to reformat them all anyway.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254374 Title: unable to install 13.10 on Intel RAID0 volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254374] Re: unable to install 13.10 on Intel RAID0 volume
That doesn't help me, as I need striping for speed, not reliability. I see mdadm isn't present on the 13.10 live CD either, this completely crippling my efforts to do it using md inside Linux. Back to 12.04 I go for now, at least it mostly works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254374 Title: unable to install 13.10 on Intel RAID0 volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1254374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034747] Re: files on desktop continue onto non-existent monitor
https://bugzilla.gnome.org/show_bug.cgi?id=693820 ** Package changed: xserver-xorg-video-intel (Ubuntu) = nautilus ** Changed in: nautilus Status: Invalid = New ** Project changed: nautilus = nautilus (Ubuntu) ** Bug watch added: GNOME Bug Tracker #693820 https://bugzilla.gnome.org/show_bug.cgi?id=693820 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=693820 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034747 Title: files on desktop continue onto non-existent monitor To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1034747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952544] Re: package libsane 1.0.22-7ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: './lib/udev/rules.d/40-libsane.rules' is different from the same file on the s
Same error. udev rules file previous modified to accomodate Brother scanner drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952544 Title: package libsane 1.0.22-7ubuntu1 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: './lib/udev/rules.d/40-libsane.rules' is different from the same file on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/952544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034747] [NEW] files on desktop continue onto non-existent monitor
Public bug reported: With a dual-monitor setup where monitor A is larger (higher-res) than B, and A is positioned *above* B, centered; And when the display of files on the Desktop (corresponding to ~/Desktop) is enabled; And the files are organized in a top-to-bottom, left-to-right direction (this is the default); Then the leftmost column (or two, or three) of files extends right off the bottom of monitor A into mid-air to the left of where monitor B starts and they are completely inaccessible via the desktop. A file browser window must be opened and navigated to Desktop in order to access the files. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Aug 8 23:57:15 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:215a] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 2985EYU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=EAC4E521C4E4F0AD loop=/ubuntu/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET68WW (1.38 ) dmi.board.name: 2985EYU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET68WW(1.38):bd12/01/2011:svnLENOVO:pn2985EYU:pvrThinkPadX201Tablet:rvnLENOVO:rn2985EYU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2985EYU dmi.product.version: ThinkPad X201 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1.3 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 precise running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034747 Title: files on desktop continue onto non-existent monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1034747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034747] Re: files on desktop continue onto non-existent monitor
** Attachment added: Screenshot from 2012-08-09 00:04:10.png https://bugs.launchpad.net/bugs/1034747/+attachment/3253975/+files/Screenshot%20from%202012-08-09%2000%3A04%3A10.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034747 Title: files on desktop continue onto non-existent monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1034747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Sad to say, folks, that I've been seeing this bug VERY intermittently on multiple generations of hardware, although I think I can safely make these assertions: -only since GTK became widespread (this definitely did not occur back in the Athena, Motif, OpenWindows, etc. days) **specifically, I don't think I've ever seen this bug appear when I wasn't running GTK+-linked or GTK2-linked software** -only since GL extensions became widespread (including software, e.g. MESA) -mostly but not exclusively on Linux systems (at least once under Solaris shortly after GNOME became the default desktop) -some (hardware) systems tended to produce this error more than others -certain applications tend to cause it more often than others (notably Synaptic, per the Ubuntu reports) -I *think* higher compiler optimization causes it to happen more often, not sure -not exclusively on multiprocessor systems: I've definitely seen this error on a Pentium III 1.0GHz (ULV mobile) and a Sparc IIi (~400MHz?). It's almost certainly a race condition, since nothing else would produce this sort of intermittent behaviour across 10+ years and multiple hardware platforms. It may not be a regression - it's likely we're dealing with a design flaw that has existed since some piece of code was written, but is being triggered more and more often because of the proliferation of multiprocessor platforms with multithreaded libs and multithread-generating-compilers. Unfortunately, this all means that finding it will be nearly impossible. So much for the all bugs are shallow theory :-). Or it could just be something low-level in GTK, which would explain why it's been cropping up more and more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/507062 Title: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/507062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844369] Re: Deja-Dup backup to Ubuntu One failed
** Also affects: deja-dup 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/844369 Title: Deja-Dup backup to Ubuntu One failed To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/844369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811485] Re: EFI SYSTEM PARTITION should be atleast 100 MiB size and formatted as FAT32, not FAT16
Ah, I see what you mean. HP appears to be breaking that paradigm, however, in that they have UEFI firmware that supports legacy mode booting, and that they seem to be shipping systems with normal MBR-style partition tables that nonetheless have EFI boot partitions. My understanding of how Windows boots is, I think, the same as yours - although its legacy boot mode is very similar to EFI boot now, it's still different. So WTF is/are HP and Lenovo and Acer [I think], and... etc. doing? The existence of this hybrid non-GPT-but-still-EFI firmware and accompanying boot process, unless I'm missing some important detail, will require that Ubuntu and others abandon their very limited notions of UEFI-compliance and allow much greater flexibility. Meanwhile, I'm thankful that the Ubuntu systems I manage still have the ability to boot in 'normal' legacy mode. (As does the HP 8200 - if you're willing to wipe the existing disk, everything works just fine.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811485 Title: EFI SYSTEM PARTITION should be atleast 100 MiB size and formatted as FAT32, not FAT16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-efi/+bug/811485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811485] Re: EFI SYSTEM PARTITION should be atleast 100 MiB size and formatted as FAT32, not FAT16
The EFI/BIOS distinction does apply to the Windows boot process, but it applies ever earlier to the computer's IPL (initial program load - what the CPU automatically starts executing after poweron). The presence or absence of an MBR structure has no effect on whether a computer loads a legacy BIOS or EFI-style firmware at IPL - it is purely and entirely controlled by what code is present in ROM at (real-mode) address F000:FFF0 at the instant the CPU is powered on. During a typical Ubuntu installation, what Windows thinks is happening during the boot process becomes completely irrelevant, although if Ubuntu and Windows arrive at different conclusions then yes, major brain-damage can occur. As to the Allen's hardware, multiple independent sources confirm that HP is, indeed, shipping UEFI-capable systems with a valid MBR *with* an EFI boot partition. Yes, that's stupid, but given that I haven't seen a single vendor (neither software nor hardware) ship a UEFI-based system that's actually 100% UEFI-compliant, I'm not surprised. I've heard anectodal reports of other OEMs shipping similar stupidity, HP's sadly not alone. This seems to go hand-in-hand with legacy-enabled UEFI firmware, which - I think, I don't have any examples on hand to check right now - boots off an EFI-ish boot partition if one is present, even on a non-GPT disk. I would refactor Allen's request to be simpler: Ubuntu needs to be *MUCH* more flexible when dealing with UEFI (and partial-UEFI, and hybrid) systems, because the real world doesn't seem to actually conform the UEFI spec. Not to mention that Ubuntu doesn't currently conform the UEFI spec, either, which is a problem unto itself. The GPT specification *requires* a Protective MBR, and in all implementations found in the wild today, any GPT disk will/must/should have a valid MBR structure at LBA sector #0. The assertion that the presence of an MBR causes Windows to boot in BIOS mode is both untrue in my experience and impossible according to the GPT specification. That decision point comes much later, and as of at least Win7 x64 (possibly earlier, not sure), the MBR boot process is very, very similar to the EFI boot process: even MBR systems get a small boot partition. Thanks to HP, it's entirely possible that Allen's system does not have a GPT disk yet still uses UEFI firmware to boot; that situation is no longer impossible. Regardless, we all agree that Ubuntu's handling of UEFI+GPT systems leaves a lot to be desired. I can't imagine that it's handling of some of the newer hybrid-UEFI or UEFI+MBR systems out there will be any better! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811485 Title: EFI SYSTEM PARTITION should be atleast 100 MiB size and formatted as FAT32, not FAT16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-efi/+bug/811485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 809807] Re: WACf004 not in pnp.ids (Wacom Tablet digitizer)
pnp.ids hasn't been changed since 2009; I think it's safe to say that part of the project is pretty much defunct. (It's sort-of maintained by Red Hat, see http://fedorahosted.org/hwdata/.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/809807 Title: WACf004 not in pnp.ids (Wacom Tablet digitizer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pnputils/+bug/809807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745112] Re: [arrandale] desktop is messed up (goes black) when laptop is docked with two external 1920x1200 monitors (x86_64)
@Bryce: According to that page, Required knowledge and tools The rest of this page assumes that you know how to fetch a kernel from the Ubuntu git repository, and build it, and that you have basic git skills. If you can't do that yet, try starting with this wiki page. So there's the fundamental stumbling block for most users. I can probably figure it out, given a bit of time, although I haven't had to go bug-hunting in the kernel since 0.9-something. Also, I do not know of a working kernel version that I can use to narrow it down. This laptop has only ever run 11.04, so far... I have no idea what effect downgrading to 2.6.35-22 will have on this system. And, of course, I really have no great galloping desire to burn a day or two doing kernel rebuilds. But someone has to, eventually, to get this fixed - might as well be me :-( It would probably be easier to ship a cheap Arrandale laptop with DP-out to one of the X devs... *sigh* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745112 Title: [arrandale] desktop is messed up (goes black) when laptop is docked with two external 1920x1200 monitors (x86_64) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779279] [NEW] Thinkpad X201 external DP monitor goes black if internal display is disabled with Monitors applet
Public bug reported: I think this is related to #749817, but perhaps a bit more specific. Running up-to-date 11.04 as of Sat May 7 23:59:32 UTC 2011. Using the Monitor applet, if I disable the internal display, the external DisplayPort (DP) display also blanks and goes to sleep. The only error I see is in dmesg: [datetime] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting Using Fn+F7 sometimes works to restore the display, but more often gives me two black screens with a mouse pointer but no X clients painted. I can use ctrl+alt+f1 to switch back to the text console, alt+f8 to switch back to X and the same situation continues: two black screens, mouse pointer, nothing else. Note that the mouse pointer appears to correctly switch between pointers (arrow vs. insertion caret vs. resize handles) as it passes over various black areas of the screen, and the clients are still running perfectly OK, they just don't display. When Fn+F7 fails to restore the display, I get the above error logged again. Yet, using xrandr --output LVDS1 --off to accomplish my goal works perfectly with no side effects. Could the problem somehow be in the Monitors applet??? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: athompso 1684 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 44' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:14f15069,17aa2157,00100302 HDA:80862804,17aa21b5,0010' Controls : 12 Simple ctrls : 6 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6SHT32WW-1.13' Mixer name : 'ThinkPad EC 6SHT32WW-1.13' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sat May 7 18:53:20 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: LENOVO 2985EYU ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-2.6.38-8-generic root=UUID=a3148d82-bfc6-4b7a-8eb7-862ee9ef6654 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET64WW (1.34 ) dmi.board.name: 2985EYU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET64WW(1.34):bd02/24/2011:svnLENOVO:pn2985EYU:pvrThinkPadX201Tablet:rvnLENOVO:rn2985EYU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2985EYU dmi.product.version: ThinkPad X201 Tablet dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779279 Title: Thinkpad X201 external DP monitor goes black if internal display is disabled with Monitors applet -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779279] Re: Thinkpad X201 external DP monitor goes black if internal display is disabled with Monitors applet
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779279 Title: Thinkpad X201 external DP monitor goes black if internal display is disabled with Monitors applet -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779279] Re: Thinkpad X201 external DP monitor goes black if internal display is disabled with Monitors applet
*** This bug is a duplicate of bug 737891 *** https://bugs.launchpad.net/bugs/737891 ** This bug has been marked a duplicate of bug 737891 [Arrandale] gnome-display-properties unable to correctly enable monitors connected to VGA * You can subscribe to bug 737891 by following this link: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/737891/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779279 Title: Thinkpad X201 external DP monitor goes black if internal display is disabled with Monitors applet -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737891] Re: [Arrandale] gnome-display-properties unable to correctly enable monitors connected to VGA
Not much to add besides me too, but I can specifically confirm that using xrandr(1) does NOT trigger the problem, whereas using the GNOME Monitors applet does trigger the problem. Also, the GNOME Monitors applet produces some very bizarre geometry at times (half-height LVDS screen, typically), for which I will probably open another bug soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737891 Title: [Arrandale] gnome-display-properties unable to correctly enable monitors connected to VGA -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737891] Re: [Arrandale] gnome-display-properties unable to correctly enable monitors connected to VGA
Sorry, forgot to add: this is in 2D classic mode, NOT with compiz enabled, so I'm not hitting the 4096px problem. Nor do my two screens together add up to 4096px anyway, so this is not merely the Arrandale hardware limit that I'm hitting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737891 Title: [Arrandale] gnome-display-properties unable to correctly enable monitors connected to VGA -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566710] Re: package firebird2.1-classic 2.1.3.18185-0.ds1-6build1 failed to install/upgrade: on ubuntu 9.10-10.04 B2 upgrade
(You haven't included your email address in either of those complaints, nor have you published your email address at your Launchpad page, which makes it rather hard to reply directly to you. The bug tracker is not a forum for people to simply post instructions for straightforward [and easily google-able] instructions. However...) As @mariuz indicated in #16, there is a patched version of this package available for the *next* version of Ubuntu (Maverick, AKA version 10.10 [I think]). However, looking at the Launchpad page (http://launchpad.net/ubuntu/+source/firebird2.1) we can see that the patch has been made available for other versions as well. In either of the following cases, note that if you've reported this bug, chances are Firebird is already installed on your system - although likely not configured correctly. You may first want to *uninstall* these packages before attempting to reinstall them. The automatic way: go to Software Sources under the Administration menu in the GUI and enable the Universe repository. It's just a checkbox, you do not need to add any URLs to anything. (In fact, I recommend you undo whatever changes you were talking about, above.) If you can't figure this out, try googling ubuntu how to enable the universe repository - the top 10 hits are all reasonably clear; the instructions for v9.x should also work on v10.x. Then launch Synaptic, remove the offending firebird package(s) from your system (I would suggest right-clicking and choosing the Completely Remove... option if you're not sure how.), APPLY those changes, then re-install the firebird package(s). The manual way: Start at this page: https://launchpad.net/firebird/2.1, and click on the version of Ubuntu that corresponds to whatever you're running. (10.04 is Lucid Lynx) From the resultant page, under Builds: (right-hand column) click on the architecture you are running (most likely amd64 or i386, depending on whether you installed a 64-bit or 32-bit OS). Then click on the name of the package you want to download. From *that* page, under Downloadable files, click on the .deb file and download it. You'll probably have to download them all or you'll run into dependency problems. -- package firebird2.1-classic 2.1.3.18185-0.ds1-6build1 failed to install/upgrade: on ubuntu 9.10-10.04 B2 upgrade https://bugs.launchpad.net/bugs/566710 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 566710] Re: package firebird2.1-classic 2.1.3.18185-0.ds1-6build1 failed to install/upgrade: on ubuntu 9.10-10.04 B2 upgrade
I had the same issue, doing a fresh install of firebird2.1-classic on UNR10.04 (not an upgrade). There was a defunct process with proctitle starting with firebird2.1-something, I had to kill that *and* its companion frontend process before synaptic would continue. Manually running dpkg-reconfigure firebird2.1-classic reveals that it is attempting to ask me a question (whether I need the server running or not). Synaptic did not display any prompt of any sort; perhaps that was the problem (UI took a left turn into hyperspace, meanwhile dpkg still waiting for input)? -- package firebird2.1-classic 2.1.3.18185-0.ds1-6build1 failed to install/upgrade: on ubuntu 9.10-10.04 B2 upgrade https://bugs.launchpad.net/bugs/566710 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 279186] Re: x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
Also confirming that with Intel BIOS LF94510J.86A, Ubuntu 9.04 (64-bit) installs and operates correctly. Note that even with updated BIOS, I am unable to correctly boot or operate the 8.10 OS release. On the other hand, going WAY back to an old v6 disc I found, works fine (presumably due to the *lack* of ACPI support in that vintage). I appears that a workaround is still desirable and possible for the 8.x LTS stream, and likely for the 9.x stream also - we have multiple hardware vendors represented in this tree of bug reports, not all of whom are providing updated BIOSes. The problem appears to be isolated to ACPI initialization: booting non-ACPI-aware kernels seems to work just fine, as do other OSes that do not rely on the ACPI DTs for hardware initialization, e.g. older OpenBSD and NetBSD, DOS, etc. I think this should be re-escalated to kernel development; there's already precedent for in-kernel ACPI fixups (e.g. ASUS P4B-DS motherboard, off the top of my head) and it looks like this will likely affect a wide variety of Atom-based systems. Odd that it's Atom- specific, but chipset-independent, though. -- x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 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 326731] Re: Intrepid 64bit 2.6.27 kernels panic on boot on Intel D945GCF2
Confirming that this problem affects me on an Intel D945GCLF2, a mini-ITX i945/ICH7 with a dual-core Atom 330. Kernel panics *immediately* after boot from 8.10 AMD64 install CD. (By immediately, I mean that by the time my CRT finishes switching modes, I already have a stack trace on screeen - I never get to see the kernel initialize.) This is the most similar bug I've found so far, in that my stack traces always end in the middle of some ordinary function, although never exactly the same spot twice! I can't even tell what version of kernel is trying to load from CD... -- Intrepid 64bit 2.6.27 kernels panic on boot on Intel D945GCF2 https://bugs.launchpad.net/bugs/326731 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 130519] Re: selects Teletype frontend on non-ttys
Oddly enough, this works on my Mythbuntu (gutsy) system at home, but breaks on my Ubuntu (gutsy) system at work. Obviously those two environments are completely different, lending credence to the belief that it's dependant on something local to the system. I see this all the time from inside Update Manager, where it's rather impossible to run commands in the terminal window to find out $TERM, etc... Running debconf-preconfigure from a terminal does seem to work properly, regardless, so I presume it's something to do with having its I/O redirected...? -- selects Teletype frontend on non-ttys https://bugs.launchpad.net/bugs/130519 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
