[Bug 1384503] Re: rsync fails on large files with compression
I attempted to SRU a patch almost a year ago. And that was after two other people confirmed the patch worked for them. In reply to my email Alberto Salvia Novella said on Mon, Jan 12, 2015 at 5:14 PM C Peters: > https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300367 > Can someone nominate this for a SRU? Done ;) Please see Comment #6 of bug report https://bugs.launchpad.net/rsync/+bug/1300367. The fixed package has been available in my Launchpad PPA since 2014-10-20. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384503 Title: rsync fails on large files with compression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384503] Re: rsync fails on large files with compression
I attempted to SRU a patch almost a year ago. And that was after two other people confirmed the patch worked for them. In reply to my email Alberto Salvia Novella said on Mon, Jan 12, 2015 at 5:14 PM C Peters: > https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300367 > Can someone nominate this for a SRU? Done ;) Please see Comment #6 of bug report https://bugs.launchpad.net/rsync/+bug/1300367. The fixed package has been available in my Launchpad PPA since 2014-10-20. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1384503 Title: rsync fails on large files with compression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+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 1506059] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499737/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Re: Unreadable display
apport information ** Tags added: apport-collected ubuntu ** Description changed: It appears the Xserver version in wily is older than the version in Debian Jessie and is buggy. Given how hard it is to read, iI'll post further comment after I reboot this old dual bot laptop into Debian. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 ApportVersion: 2.19.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Wed Oct 14 09:03:50 2015 InstallationDate: Installed on 2014-08-28 (412 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823) SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago) + --- + ApportVersion: 2.19.1-0ubuntu2 + Architecture: i386 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: LXDE + DistUpgraded: 2015-10-12 07:06:32,592 DEBUG enabling apt cron job + DistroCodename: wily + DistroRelease: Ubuntu 15.10 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Advanced Micro Devices, Inc. [AMD/ATI] Rage Mobility 128 AGP 2X/Mobility M3 [1002:4c46] (rev 02) (prog-if 00 [VGA controller]) +Subsystem: CLEVO/KAPOK Computer Device [1558:8586] + InstallationDate: Installed on 2014-08-28 (417 days ago) + InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823) + Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: sag168168 Apollo Pro133AX + Package: xorg 1:7.7+7ubuntu4 + PackageArchitecture: i386 + PccardctlIdent: + Socket 0: +no product info available + Socket 1: +no product info available + PccardctlStatus: + Socket 0: +no card + Socket 1: +no card + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=8f11e8d0-b844-4697-8755-16c38e7b4c76 ro quiet splash + ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 + Renderer: Software + Tags: wily ubuntu + Uname: Linux 4.2.0-16-generic i686 + UpgradeStatus: Upgraded to wily on 2015-10-12 (6 days ago) + UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/18/2001 + dmi.bios.vendor: Phoenix + dmi.bios.version: 4.06CJ15 + dmi.board.name: 694x686a + dmi.board.vendor: VIA + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd10/18/2001:svnsag168168:pnApolloPro133AX:pvr8500V:rvnVIA:rn694x686a:rvrNone:cvnNoEnclosure:ct1:cvrN/A: + dmi.product.name: Apollo Pro133AX + dmi.product.version: 8500V + dmi.sys.vendor: sag168168 + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.64-1 + version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 + version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 + xserver.bootTime: Mon Oct 19 01:08:29 2015 + xserver.configfile: /etc/X11/xorg.conf + xserver.devices: + inputPower Button KEYBOARD, id 6 + inputSleep Button KEYBOARD, id 7 + inputAllegro KEYBOARD, id 8 + inputAT Translated Set 2 keyboard KEYBOARD, id 9 + inputAlpsPS/2 ALPS GlidePoint TOUCHPAD, id 10 + xserver.errors: AIGLX: reverting to software rendering + xserver.logfile: /var/log/Xorg.0.log + xserver.outputs: Output VGA-0 + xserver.version: 2:1.17.2-1ubuntu9 + xserver.video_driver: r128 ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499733/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499736/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499735/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499738/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] LightdmGreeterLog.txt
apport information ** Attachment added: "LightdmGreeterLog.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499739/+files/LightdmGreeterLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] LightdmGreeterLogOld.txt
apport information ** Attachment added: "LightdmGreeterLogOld.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499740/+files/LightdmGreeterLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499741/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] XorgConf.txt
apport information ** Attachment added: "XorgConf.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499749/+files/XorgConf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499753/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499742/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499734/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499743/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499748/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499750/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499752/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499745/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499751/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499744/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499747/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1506059/+attachment/4499746/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Re: Unreadable display
** Attachment added: "Xorg.0.log-with-xorg.conf" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494479/+files/Xorg.0.log-with-xorg.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Re: Unreadable display
The version of Lubuntu is wily. This old laptop was upgrade from 14.04 which had a working display until I updated it recently. The screenshot does not show how the display actually looks, if required I can try to take a picture of the laptop... Debian Jessie display is fine! Attached are the following files: xorg.conf used on Debian and earlier version of Ubuntu (14.04) and tried on wily. Xorg.0.log without an xorg.conf file on wily. Xorg.0.log-with-xorg.conf debian-Xorg.0.log working display on Debian Jessie. lspci-vv is output of lspci -vv lshw is output of lshw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Re: Unreadable display
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494478/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Re: Unreadable display
** Attachment added: "lshw" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494477/+files/lshw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Re: Unreadable display
** Attachment added: "debian-Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494446/+files/debian-Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Re: Unreadable display
** Attachment added: "lspci-vv" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494447/+files/lspci-vv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] Re: Unreadable display
** Attachment added: "xorg.conf" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494480/+files/xorg.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506059] [NEW] Unreadable display
Public bug reported: It appears the Xserver version in wily is older than the version in Debian Jessie and is buggy. Given how hard it is to read, iI'll post further comment after I reboot this old dual bot laptop into Debian. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 ApportVersion: 2.19.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Wed Oct 14 09:03:50 2015 InstallationDate: Installed on 2014-08-28 (412 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823) SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 wily ** Attachment added: "Screenshot of Desktop" https://bugs.launchpad.net/bugs/1506059/+attachment/4494407/+files/2015-10-14-083616_1400x1050_scrot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506059 Title: Unreadable display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406729] Re: dig does not have a default trusted key
I vote no, if someone is setting up or testing DNSSEC, let's not encourage them to use a broken dig option! I tried using the following command and dig core dumped. Note: www is setup as a CNAME. dig +trusted-key=trusted-key.key +topdown +sigchase +multiline -ta www.tuxedo.net I was wondering if I had done something wrong with DNSSEC... But other tools show (I think) it looks ok. drill -TD -k ../trusted-key.key www.tuxedo.net # See footnote 1 http://dnsviz.net/d/www.tuxedo.net/dnssec/ And some more digging and I found: The option is not compiled in by default upstream because it is broken. See: https://lists.isc.org/pipermail/bind-users/2012-May/087779.html https://lists.isc.org/pipermail/bind-users/2012-May/087781.html dig +trusted-key=trusted-key.key +topdown +sigchase +multiline -ta com ... ;; OK a DS valids a DNSKEY in the RRset ;; Now verify that this DNSKEY validates the DNSKEY RRset ;; VERIFYING DNSKEY RRset for com. with DNSKEY:30909: success ;; We are in a Grand Father Problem: See 2.2.1 in RFC 3568 ;; ERROR : com. is not a subdomain of: com. FAILED name.c:2151: REQUIRE(source-length 0) failed, back trace #0 0x7f1a1cda5954 in ?? #1 0x7f1a1cda58ba in ?? #2 0x7f1a1d4a7bdc in ?? #3 0x7f1a1dc45f72 in ?? #4 0x7f1a1dc48397 in ?? #5 0x7f1a1dc4a3d2 in ?? #6 0x7f1a1cdc7af6 in ?? #7 0x7f1a1cb80182 in ?? #8 0x7f1a1c8acefd in ?? Aborted (core dumped) I also compiled bind-9.9.6-P1 to test if it was fixed in a newer release, and it is still broken. Footnote 1: Note drill is currently part of ldnsutils package and not unbound. https://www.nlnetlabs.nl/projects/drill/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1406729 Title: dig does not have a default trusted key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1406729/+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 1406729] Re: dig does not have a default trusted key
I vote no, if someone is setting up or testing DNSSEC, let's not encourage them to use a broken dig option! I tried using the following command and dig core dumped. Note: www is setup as a CNAME. dig +trusted-key=trusted-key.key +topdown +sigchase +multiline -ta www.tuxedo.net I was wondering if I had done something wrong with DNSSEC... But other tools show (I think) it looks ok. drill -TD -k ../trusted-key.key www.tuxedo.net # See footnote 1 http://dnsviz.net/d/www.tuxedo.net/dnssec/ And some more digging and I found: The option is not compiled in by default upstream because it is broken. See: https://lists.isc.org/pipermail/bind-users/2012-May/087779.html https://lists.isc.org/pipermail/bind-users/2012-May/087781.html dig +trusted-key=trusted-key.key +topdown +sigchase +multiline -ta com ... ;; OK a DS valids a DNSKEY in the RRset ;; Now verify that this DNSKEY validates the DNSKEY RRset ;; VERIFYING DNSKEY RRset for com. with DNSKEY:30909: success ;; We are in a Grand Father Problem: See 2.2.1 in RFC 3568 ;; ERROR : com. is not a subdomain of: com. FAILED name.c:2151: REQUIRE(source-length 0) failed, back trace #0 0x7f1a1cda5954 in ?? #1 0x7f1a1cda58ba in ?? #2 0x7f1a1d4a7bdc in ?? #3 0x7f1a1dc45f72 in ?? #4 0x7f1a1dc48397 in ?? #5 0x7f1a1dc4a3d2 in ?? #6 0x7f1a1cdc7af6 in ?? #7 0x7f1a1cb80182 in ?? #8 0x7f1a1c8acefd in ?? Aborted (core dumped) I also compiled bind-9.9.6-P1 to test if it was fixed in a newer release, and it is still broken. Footnote 1: Note drill is currently part of ldnsutils package and not unbound. https://www.nlnetlabs.nl/projects/drill/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406729 Title: dig does not have a default trusted key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1406729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391409] [NEW] ghost domain names attack CVE-2012-1193
Public bug reported: http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1193.html shows needed for 12.04, 14.04 and 14.10. It appears the bug is fixed in 14.04 and 14.10 as it was fixed in PowerDNS Recursor version 3.5: I'm not using 12.04 or PowerDNS Recursor, but I hope the following patches will help someone else fix the issue. https://bugzilla.redhat.com/show_bug.cgi?id=794963 comment 4 says: From http://doc.powerdns.com/changelog.html#changelog-recursor-3.5: While Recursor 3.3 was not vulnerable to the specific attack noted in 'Ghost Domain Names: Revoked Yet Still Resolvable', further investigation showed that a variant of the attack could work. This was fixed in r3085. http://wiki.powerdns.com/trac/changeset/3085 related: http://wiki.powerdns.com/trac/changeset/3084 http://wiki.powerdns.com/trac/changeset/3083 http://wiki.powerdns.com/trac/changeset/3082 There's also the following upstream bug: http://wiki.powerdns.com/trac/ticket/668 ** Affects: pdns-recursor (Ubuntu) Importance: Undecided Status: New ** Tags: cve-2012-1193 ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391409 Title: ghost domain names attack CVE-2012-1193 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns-recursor/+bug/1391409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918588] Re: PowerDNS Authoritative Server can be caused to generate a traffic loop CVE-2012-0206
The tracker at http://people.canonical.com/~ubuntu- security/cve/2012/CVE-2012-0206.html lists 12.04, 14.04 and 14.10 as needed. However it looks like it is actually fixed in all of them. The CVE description states before 3.0.1 and 14.04 and 14.10 are newer than 3.01. This is from the changelog in the current 12.04 package. pdns (3.0-1.1) unstable; urgency=high * Non-maintainer upload. * Don't respond to responses fixes CVE-2012-0206 * Make build dependency on mongodb-dev arch specific (Closes: #654568). -- Luk Claes luk@debian Sun, 15 Jan 2012 19:13:17 +0100 And to confirm it I checked and the package and it does contain the patch CVE-2012-0206 in the debian/patches directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918588 Title: PowerDNS Authoritative Server can be caused to generate a traffic loop CVE-2012-0206 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns/+bug/918588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384355] Re: ownCloud should be removed
First I should note that we could use Debian's packages as a start for updating these packages. http://snapshot.debian.org/package/owncloud/ Debian versions available: 5.0.13+dfsg-2 or 5.0.14.a+dfsg-1 6.0.4+dfsg-1 or 6.0.3+dfsg-2 Ubuntu versions: 6.0.1+dfsg-1ubuntu1 trusty 5.0.4debian-0ubuntu1~ubuntu12.04 precise Owncloud versions with release dates: Version 7.0.2 August 28th 2014 Version 6.0.5 August 28th 2014 Version 5.0.17 June 23rd 2014 The proposed package suggests updating with OBS or juju and that would upgrade to either 7.0.1 (juju) or 7.0.2 (OBS) depending on the choice. The 5.x and 6.x versions of owncloud still have supported upstream packages which are less likely to break things: http://download.opensuse.org/repositories/isv:/ownCloud:/community:/5.0/xUbuntu_12.04/ http://download.opensuse.org/repositories/isv:/ownCloud:/community:/6.0/xUbuntu_14.04/ The trusty package also points to https://jujucharms.com/precise/owncloud/. One might wonder if the juju charm won't work for trusty. I have tried to identify the CVE patch sets without much success thus far. Support for the 5.x series will likely be ending within 6 months and it will require more work to update security patches included in 5.0.17. Would the SRU team accept an updated package based on the Debian's 6.0.4+dfsg-1 package for trusty? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384355 Title: ownCloud should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/owncloud/+bug/1384355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384355] Re: ownCloud should be removed
I should correct one error: Owncloud 6.0.6 was released Oct 22. 2014 https://owncloud.org/releases/Changelog shows something different than https://owncloud.org/releases/Changelog. Sorry for the error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384355 Title: ownCloud should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/owncloud/+bug/1384355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384355] Re: ownCloud should be removed
Sorry for the errors... https://owncloud.org/releases/Changelog shows the Release 6.0.6 Oct 22. 2014 https://owncloud.org/changelog/ shows Version 6.0.5 August 28th 2014 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384355 Title: ownCloud should be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/owncloud/+bug/1384355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372847] Re: [SRU] New stable release 2.40.1
I rebooted shortly after this update and it seems to have broken our IPv4 firewalls. The IPv6 tunnel through sixxs.net still seems to work. Connectivity for the fiewall itself was fine, but most everything on the LAN ground to a halt. One machine is Ubuntu 14.04 64 bit with ufw and the other is Ubuntu 14.04 32 bit using shorewall. I downgraded the libglib2.0-0_2.40.0-2_i386.deb and libglib2.0-data_2.40.0-2_all.deb on the 32 bit machine and reconfigured dhcpd to change the gateway and we are back on the net. I'll try some other tests on the 64 bit machine later or tonight, or more likely tomorrow. I should note that it is possible some other odd networking issue from our local cable company is causing this, but if it is the library, it is going to be ugly for a lot of people using Ubuntu firewalls if this isn't fixed soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372847 Title: [SRU] New stable release 2.40.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1372847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300367] Re: rsync 3.1.0 and 3.0.9 incompatibility
Attached is a patch which seems to fix the bug for Ubuntu Trusty or 14.04. Please test the package from my PPA and confirm it works OK. https://launchpad.net/~cp/+archive/ubuntu/bug-fixes/+packages The easy way to install it: sudo add-apt-repository ppa:cp/bug-fixes sudo apt-get update sudo apt-get upgrade Changelog rsync (3.1.0-2ubuntu0.2) trusty; urgency=medium * Use included zlib as transfers failed when using -z with the separate zlib. (LP: #11300367) - debian/rules: Add -Izlib to CPPFLAGS and change .configure to use -with-included-zlib=yes - debian/control: Remove Build-Depends zlib1g-dev My testing shows transfers with the -z option are working, but the real test will be when my backups run late tonight. ;) ** Patch added: Use rsync's internal zlib https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300367/+attachment/4240742/+files/rsync-trusty-zlib-internal.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1300367 Title: rsync 3.1.0 and 3.0.9 incompatibility To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1300367/+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 1300367] Re: rsync 3.1.0 and 3.0.9 incompatibility
Attached is a patch which seems to fix the bug for Ubuntu Trusty or 14.04. Please test the package from my PPA and confirm it works OK. https://launchpad.net/~cp/+archive/ubuntu/bug-fixes/+packages The easy way to install it: sudo add-apt-repository ppa:cp/bug-fixes sudo apt-get update sudo apt-get upgrade Changelog rsync (3.1.0-2ubuntu0.2) trusty; urgency=medium * Use included zlib as transfers failed when using -z with the separate zlib. (LP: #11300367) - debian/rules: Add -Izlib to CPPFLAGS and change .configure to use -with-included-zlib=yes - debian/control: Remove Build-Depends zlib1g-dev My testing shows transfers with the -z option are working, but the real test will be when my backups run late tonight. ;) ** Patch added: Use rsync's internal zlib https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300367/+attachment/4240742/+files/rsync-trusty-zlib-internal.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300367 Title: rsync 3.1.0 and 3.0.9 incompatibility To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1300367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300133] Re: Generate ED25519 host keys on upgrade
# ssh-keygen -A ssh-keygen: generating new host keys: RSA1 ED25519 I don't think we want to add the old RSA1 keys, just the new ED25519. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1300133 Title: Generate ED25519 host keys on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1300133/+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 1300133] Re: Generate ED25519 host keys on upgrade
# ssh-keygen -A ssh-keygen: generating new host keys: RSA1 ED25519 I don't think we want to add the old RSA1 keys, just the new ED25519. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300133 Title: Generate ED25519 host keys on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1300133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300133] [NEW] Generate ED25519 host keys on upgrade
Public bug reported: openssh (1:6.5p1-1) unstable; urgency=medium ... * Generate ED25519 host keys on fresh installations. Upgraders who wish to add such host keys should manually add 'HostKey /etc/ssh/ssh_host_ed25519_key' to /etc/ssh/sshd_config and run 'ssh-keygen -q -f /etc/ssh/ssh_host_ed25519_key -N -t ed25519'. ... -- Colin Watson cjwat...@debian.org Mon, 10 Feb 2014 14:58:26 + Most users and many administrators are not going to notice the new host key capabilities when it is buried in a changelog. We should at least give them a obvious hint about it. Even better would be to prompt the user to generate the keys with a debconf question like was recently done with the Change to PermitRootLogin without-password. I would like to label this as a security vulnerability, but that may be a bit over the top, it would be a security improvement! ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1300133 Title: Generate ED25519 host keys on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1300133/+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 1300133] [NEW] Generate ED25519 host keys on upgrade
Public bug reported: openssh (1:6.5p1-1) unstable; urgency=medium ... * Generate ED25519 host keys on fresh installations. Upgraders who wish to add such host keys should manually add 'HostKey /etc/ssh/ssh_host_ed25519_key' to /etc/ssh/sshd_config and run 'ssh-keygen -q -f /etc/ssh/ssh_host_ed25519_key -N -t ed25519'. ... -- Colin Watson cjwat...@debian.org Mon, 10 Feb 2014 14:58:26 + Most users and many administrators are not going to notice the new host key capabilities when it is buried in a changelog. We should at least give them a obvious hint about it. Even better would be to prompt the user to generate the keys with a debconf question like was recently done with the Change to PermitRootLogin without-password. I would like to label this as a security vulnerability, but that may be a bit over the top, it would be a security improvement! ** Affects: openssh (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/1300133 Title: Generate ED25519 host keys on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1300133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
root@kepler:~# uname -a Linux kepler 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:13:28 UTC 2014 i686 i686 i686 GNU/Linux The saucy-proposed kernel fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
This kernel boots and I didn't notice any other issues! $ uname -a Linux kepler 3.13.0-5-generic #20~lp1251816UpstreamRevert SMP Tue Jan 21 21:39:58 UTC 2014 i686 i686 i686 GNU/Linux Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
linux- image-3.13.0-031300rc8-generic_3.13.0-031300rc8.201401120535_i386.deb has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
This kernel boots. Thank you! $ uname -a Linux kepler 3.13.0-3-generic #18~lp1251816v1 SMP Tue Jan 14 22:20:13 UTC 2014 i686 i686 i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201401091651_i386 has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201401071104_i386 has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
This kernel boots. $ uname -a Linux kepler 3.9.0-030900rc2-generic #201401081132 SMP Wed Jan 8 16:47:32 UTC 2014 i686 i686 i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
I hope you had a good holiday! This kernel boots. $ uname -a Linux kepler 3.9.0-030900rc2-generic #201312201136 SMP Fri Dec 20 16:58:03 UTC 2013 i686 i686 i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201312181333_i386 has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201312161520_i386 has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
3.9.0-030900rc2.201312131341_i386 has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
This kernel has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
cp@kepler:~$ uname -a Linux kepler 3.9.0-030900-generic #201312121455 SMP Thu Dec 12 20:03:59 UTC 2013 i686 i686 i686 GNU/Linux This one boots OK! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
This one has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
This kernel boots! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
The kernel has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
The kernel has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
The test kernel fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
The 3.9 kernels work and the 3.10 kernels fail to boot. In addition to the above kernels you listed, I tried the last 3.9 and the first 3.10 based on the directory date listings at http://kernel.ubuntu.com/~kernel-ppa/mainline/. Boots OK: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9.11-saucy/ Fails to boot: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc1-saucy/ via686a :00:07.4: base address not set - upgrade BIOS or use force_addr=0xaddr Reading through https://www.kernel.org/doc/Documentation/hwmon/via686a it is a fan control issue and Addresses scanned: ISA in PCI-space encoded address. The kernel doc suggests to only try Example: 'modprobe via686a force_addr=0x6000' if one can't find an updated BIOS: but doesn't tell me how I find the correct address. The two variable speeds seem to be working OK. I checked the vendors website and emailed Sagar to ask about an updated BIOS. lshw shows: description: BIOS vendor: Phoenix physical id: 0 version: 4.06CJ15 date: 10/18/2001 This is the complete list of what kernels are currently installed. linux-generic 3.11.0.14.15 linux-headers-3.10.0-031000 3.10.0-031000.201306301935 linux-headers-3.10.0-031000-generic 3.10.0-031000.201306301935 linux-headers-3.10.0-031000rc1 3.10.0-031000rc1.201305130510 linux-headers-3.10.0-031000rc1-generic 3.10.0-031000rc1.201305130510 linux-headers-3.11.0-031100rc1 3.11.0-031100rc1.201307141935 linux-headers-3.11.0-031100rc1-generic 3.11.0-031100rc1.201307141935 linux-headers-3.11.0-13 3.11.0-13.20 linux-headers-3.11.0-13-generic 3.11.0-13.20 linux-headers-3.11.0-14 3.11.0-14.21 linux-headers-3.11.0-14-generic 3.11.0-14.21 linux-headers-3.12.0-9993.12.0-999.201311070405 linux-headers-3.12.0-999-generic3.12.0-999.201311070405 linux-headers-3.8.0-030800 3.8.0-030800.201302181935 linux-headers-3.8.0-030800-generic 3.8.0-030800.201302181935 linux-headers-3.9.0-030900 3.9.0-030900.201305071030 linux-headers-3.9.0-030900-generic 3.9.0-030900.201305071030 linux-headers-3.9.11-030911 3.9.11-030911.201307202035 linux-headers-3.9.11-030911-generic 3.9.11-030911.201307202035 linux-headers-generic 3.11.0.14.15 linux-image-2.6.32-52-generic 2.6.32-52.114 linux-image-3.10.0-031000-generic 3.10.0-031000.201306301935 linux-image-3.10.0-031000rc1-generic3.10.0-031000rc1.201305130510 linux-image-3.11.0-031100rc1-generic3.11.0-031100rc1.201307141935 linux-image-3.11.0-13-generic 3.11.0-13.20 linux-image-3.11.0-14-generic 3.11.0-14.21 linux-image-3.12.0-999-generic 3.12.0-999.201311070405 linux-image-3.8.0-030800-generic3.8.0-030800.201302181935 linux-image-3.8.0-32-generic3.8.0-32.47 linux-image-3.9.0-030900-generic3.9.0-030900.201305071030 linux-image-3.9.11-030911-generic 3.9.11-030911.201307202035 linux-image-extra-3.11.0-13-generic 3.11.0-13.20 linux-image-extra-3.11.0-14-generic 3.11.0-14.21 linux-image-extra-3.8.0-030800-generic 3.8.0-030800.201302181935 linux-image-extra-3.8.0-32-generic 3.8.0-32.47 linux-image-generic 3.11.0.14.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251816] [NEW] Boot failure with saucy kernel 3.11 probing eisa
Public bug reported: I have an old laptop that I upgraded to saucy and it will only boot the earlier 3.8 kernel. The 3.11, 3 versions tried including the proposed, hangs on Platform eisa.0: Probing EISA bus 0 I also tried the 3.12.0-999 kernel at http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-07-saucy/ and it hangs as well. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-generic 3.11.0.14.15 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cp 1926 F pulseaudio CRDA: country CO: (2402 - 2472 @ 40), (3, 27) (5170 - 5250 @ 40), (3, 17) (5250 - 5330 @ 40), (3, 23), DFS (5735 - 5835 @ 40), (3, 30) CurrentDmesg: [ 114.938323] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 115.026165] XFS (sdb6): Mounting Filesystem [ 119.437397] XFS (sdb6): Ending clean mount [ 119.878267] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Date: Fri Nov 15 23:18:27 2013 HibernationDevice: RESUME=UUID=33c5f08a-8efc-4eb2-b6ec-497bb57df899 Lsusb: Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA PATA Combo Bridge Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: sag168168 Apollo Pro133AX MarkForUpload: True PccardctlIdent: Socket 0: no product info available Socket 1: no product info available ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=5658ed45-be8e-4c39-b0e3-1944d7a303b0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-32-generic N/A linux-backports-modules-3.8.0-32-generic N/A linux-firmware1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to saucy on 2013-11-01 (14 days ago) WpaSupplicantLog: dmi.bios.date: 10/18/2001 dmi.bios.vendor: Phoenix dmi.bios.version: 4.06CJ15 dmi.board.name: 694x686a dmi.board.vendor: VIA dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd10/18/2001:svnsag168168:pnApolloPro133AX:pvr8500V:rvnVIA:rn694x686a:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Apollo Pro133AX dmi.product.version: 8500V dmi.sys.vendor: sag168168 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 package-from-proposed saucy staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247148] Re: rndc addzone isn't working. fix available
snippet of /etc/apparmor.d/usr.sbin.named # /etc/bind should be read-only for bind # /var/lib/bind is for dynamically updated zone (and journal) files. # /var/cache/bind is for slave/stub data, since we're not the origin of it. # See /usr/share/doc/bind9/README.Debian.gz /etc/bind/** r, /var/lib/bind/** rw, /var/lib/bind/ rw, /var/cache/bind/** lrw, /var/cache/bind/ rw, Pavel's proposed solution could cause other issues with apparmor. Furthermore Pavel should place the zone files in /var/lib/bind/. $ ls -ld /var/lib/bind/master/ drwxrws--- 3 root bind 4096 Jun 30 23:08 /var/lib/bind/master/ A directory from a hidden master containing one of my DNSSEC enabled zones, a zone which is configured to automatically rotate the ZSK or zone signing key: $ sudo ls -la /var/lib/bind/master/tuxedo.net total 104 drwxrws--- 2 bind bind 4096 Nov 8 18:03 . drwxrws--- 3 root bind 4096 Jun 30 23:08 .. -rw-r--r-- 1 root bind 1858 Sep 24 18:51 tuxedo.net.hosts -rw-r--r-- 1 bind bind 512 Sep 24 18:51 tuxedo.net.hosts.jbk -rw-r--r-- 1 bind bind 7509 Nov 8 18:03 tuxedo.net.hosts.signed -rw-r--r-- 1 bind bind 76419 Nov 8 17:48 tuxedo.net.hosts.signed.jnl -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1247148 Title: rndc addzone isn't working. fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1247148/+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 1247148] Re: rndc addzone isn't working. fix available
Perhaps a better approach would be to modify /etc/default/bind9. $ cat /etc/default/bind9 # run resolvconf? RESOLVCONF=no # startup options for the server OPTIONS=-u bind -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1247148 Title: rndc addzone isn't working. fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1247148/+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 1247148] Re: rndc addzone isn't working. fix available
snippet of /etc/apparmor.d/usr.sbin.named # /etc/bind should be read-only for bind # /var/lib/bind is for dynamically updated zone (and journal) files. # /var/cache/bind is for slave/stub data, since we're not the origin of it. # See /usr/share/doc/bind9/README.Debian.gz /etc/bind/** r, /var/lib/bind/** rw, /var/lib/bind/ rw, /var/cache/bind/** lrw, /var/cache/bind/ rw, Pavel's proposed solution could cause other issues with apparmor. Furthermore Pavel should place the zone files in /var/lib/bind/. $ ls -ld /var/lib/bind/master/ drwxrws--- 3 root bind 4096 Jun 30 23:08 /var/lib/bind/master/ A directory from a hidden master containing one of my DNSSEC enabled zones, a zone which is configured to automatically rotate the ZSK or zone signing key: $ sudo ls -la /var/lib/bind/master/tuxedo.net total 104 drwxrws--- 2 bind bind 4096 Nov 8 18:03 . drwxrws--- 3 root bind 4096 Jun 30 23:08 .. -rw-r--r-- 1 root bind 1858 Sep 24 18:51 tuxedo.net.hosts -rw-r--r-- 1 bind bind 512 Sep 24 18:51 tuxedo.net.hosts.jbk -rw-r--r-- 1 bind bind 7509 Nov 8 18:03 tuxedo.net.hosts.signed -rw-r--r-- 1 bind bind 76419 Nov 8 17:48 tuxedo.net.hosts.signed.jnl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247148 Title: rndc addzone isn't working. fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1247148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247148] Re: rndc addzone isn't working. fix available
Perhaps a better approach would be to modify /etc/default/bind9. $ cat /etc/default/bind9 # run resolvconf? RESOLVCONF=no # startup options for the server OPTIONS=-u bind -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247148 Title: rndc addzone isn't working. fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1247148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214749] [NEW] Sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main)
Public bug reported: Please sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/tests: Add autopkgtest. * Fix FTBFS: correct expected Python.h location in configure script (LP: #1098162). - d/control: add build dependency on dh-autoreconf - d/rules: use dh_autoreconf and dh_autoreconf_clean - d/patches/80_python_h_location.patch: patch configure.in * Fix FTBFS: correct expected Python.h location in configure script (LP: #1098162). - d/control: add build dependency on dh-autoreconf - d/rules: use dh_autoreconf and dh_autoreconf_clean - d/patches/80_python_h_location.patch: patch configure.in To check for possible merges I compared the Debian 2.1.15-1 and Ubuntu 2.1.15-1ubuntu2 source packages with diff -ru and then compared the changes to Debian's 2.1.16~rc2-1. I also checked with Yolanda Robla yolanda.ro...@canonical.com and Robie Basak robie.ba...@canonical.com about possible merges. It appears all of Ubuntu's changes have made it into the new Debian package or Mailman upstream. I tested the packages on raring using my production raring VPS and it appears to be running without any issues. The results of my saucy builds are posted at: https://launchpad.net/~cp/+archive/net/+sourcepub/3435869/+listing-archive-extra Changelog entries since current saucy version 1:2.1.15-1ubuntu2: mailman (1:2.1.16~rc2-1) unstable; urgency=low [ Thijs Kinkhorst ] * New upstream release candidate. - Exposes message-id to templates (closes: #614340). * Remove obsolete patches, applied upstream: 21_newlist_help.patch * Updates to Russian debconf templates, thanks Ivan Krylov! (closes: #710268). * Needs at least version 3.8.0 of logrotate (closes: #687215). * Add autopkgtests, thanks Yolanda Robla! (closes: #710095) * Packaging cleanup: checked for policy 3.9.4, update Vcs URL, recommend default-mta instead of exim4. [ Thorsten Glaser ] * Prevent losing stderr in the init script when there are many lists. (closes: #702002) * debian/watch: mangle the epoch away so DDPO is green again. -- Thijs Kinkhorst th...@debian.org Sun, 04 Aug 2013 12:00:05 +0200 ** Affects: mailman (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1214749 Title: Sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1214749/+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 1214749] [NEW] Sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main)
Public bug reported: Please sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/tests: Add autopkgtest. * Fix FTBFS: correct expected Python.h location in configure script (LP: #1098162). - d/control: add build dependency on dh-autoreconf - d/rules: use dh_autoreconf and dh_autoreconf_clean - d/patches/80_python_h_location.patch: patch configure.in * Fix FTBFS: correct expected Python.h location in configure script (LP: #1098162). - d/control: add build dependency on dh-autoreconf - d/rules: use dh_autoreconf and dh_autoreconf_clean - d/patches/80_python_h_location.patch: patch configure.in To check for possible merges I compared the Debian 2.1.15-1 and Ubuntu 2.1.15-1ubuntu2 source packages with diff -ru and then compared the changes to Debian's 2.1.16~rc2-1. I also checked with Yolanda Robla yolanda.ro...@canonical.com and Robie Basak robie.ba...@canonical.com about possible merges. It appears all of Ubuntu's changes have made it into the new Debian package or Mailman upstream. I tested the packages on raring using my production raring VPS and it appears to be running without any issues. The results of my saucy builds are posted at: https://launchpad.net/~cp/+archive/net/+sourcepub/3435869/+listing-archive-extra Changelog entries since current saucy version 1:2.1.15-1ubuntu2: mailman (1:2.1.16~rc2-1) unstable; urgency=low [ Thijs Kinkhorst ] * New upstream release candidate. - Exposes message-id to templates (closes: #614340). * Remove obsolete patches, applied upstream: 21_newlist_help.patch * Updates to Russian debconf templates, thanks Ivan Krylov! (closes: #710268). * Needs at least version 3.8.0 of logrotate (closes: #687215). * Add autopkgtests, thanks Yolanda Robla! (closes: #710095) * Packaging cleanup: checked for policy 3.9.4, update Vcs URL, recommend default-mta instead of exim4. [ Thorsten Glaser ] * Prevent losing stderr in the init script when there are many lists. (closes: #702002) * debian/watch: mangle the epoch away so DDPO is green again. -- Thijs Kinkhorst th...@debian.org Sun, 04 Aug 2013 12:00:05 +0200 ** Affects: mailman (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/1214749 Title: Sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1214749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1193205] [NEW] dhcp IPv6 sets accept_ra to 0 and doesn't get IPv6 route
Public bug reported: Configure IPv6 network so that the IP address is obtained through DHCPv6 and setup NetworkManager IPv6 to use the Automatic (DHCP only) method. accept_ra is then set to 0 and NetworkManager fails to obtain the IPv6 route. Attached is a script /etc/NetworkManager/dispatcher.d/02allowIPv6route which works around the issue to set accept_ra to 1. I am running Kubuntu 13.04, but I believe the bug is not limited to this release. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: 02allowIPv6route https://bugs.launchpad.net/bugs/1193205/+attachment/3708545/+files/02allowIPv6route -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1193205 Title: dhcp IPv6 sets accept_ra to 0 and doesn't get IPv6 route To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1193205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189312] [NEW] ufw-framework man page example breaks IP Masquerading
Public bug reported: Note this is ufw 0.33-0ubuntu3 on a Ubuntu 13.04 server. The ufw-framework man page says: All examples assume IPv4 only and that DEFAULT_FORWARD_POLICY in /etc/default/ufw is set to DROP. IP Masquerading To allow IP masquerading for computers from the 10.0.0.0/8 network to share the single IP address on eth0: Edit /etc/ufw/sysctl.conf to have: net.ipv4.ip_forward=1 Add to the end of /etc/ufw/before.rules, after the *filter section: *nat :POSTROUTING ACCEPT [0:0] -A POSTROUTING -s 10.0.0.0/8 -o eth0 -j MASQUERADE COMMIT However when the default policy is DROP, the machines on the LAN can't get anywhere and we have [UFW BLOCK] messages in the logs. The wiki page about setting up MASQ, https://help.ubuntu.com/13.04/serverguide/firewall.html#ip-masquerading, says to set DEFAULT_FORWARD_POLICY to ACCEPT. The page on setting up IPv6, https://wiki.ubuntu.com/IPv6#ufw_and_Routing, suggests setting DEFAULT_FORWARD_POLICY to DROP. Note I just changed the https://wiki.ubuntu.com/IPv6#ufw_and_Routing page to hopefully allow others to resolve the conflict. My solution to the problem is set the DEFAULT_FORWARD_POLICY to the default DROP and to add the following to end of /etc/ufw/after.rules # Added to forward MASQ traffic and resolve the DEFAULT_FORWARD_POLICY as # DROP that would have otherwise opened up all IPv6 addresses on the LAN. -A ufw-skip-to-policy-forward -j ACCEPT COMMIT ** Affects: ufw (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/1189312 Title: ufw-framework man page example breaks IP Masquerading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1189312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189312] Re: ufw-framework man page example breaks IP Masquerading
My solution isn't working. I have more work to do... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189312 Title: ufw-framework man page example breaks IP Masquerading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1189312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
