[Bug 1205511] Re: The lpr and lp can not print Multilingual (Japanese) characters .
I tried to print Japanese Character on Ubuntu 15.04, but I can not print Japanese Characters yet. ** Attachment added: "(date; echo '星') | lpr 's output to CUPS-PDF" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+attachment/4394230/+files/_stdin_.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394163/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394165/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394155/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394164/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] Locale.txt
apport information ** Attachment added: "Locale.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394158/+files/Locale.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394162/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] Re: The lpr and lp can not print Multilingual (Japanese) characters .
apport information ** Tags added: apparmor apport-collected vivid ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center cups-bsd: 1.6.2-1ubuntu5 cups-client: 1.6.2-1ubuntu5 cups-filters: 1.0.34-0ubuntu1.1 3) What you expected to happen I expected to print Japanese characters . ex. $ echo '星' | lpr I expected to lpr and lp to be able to print multilingual characters . 4) What happened instead But the printer printed '?' . ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups-bsd 1.6.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CupsErrorLog: W [27/Jul/2013:07:14:32 +0900] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_MG6200LAN W [27/Jul/2013:07:14:32 +0900] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_MG6200LAN W [27/Jul/2013:07:14:32 +0900] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_MG6200LAN W [27/Jul/2013:07:14:32 +0900] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_MG6200LAN Date: Sat Jul 27 07:15:41 2013 InstallationDate: Installed on 2013-05-14 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring" - Build i386 LIVE Binary 20130430-17:57 Lpstat: device for MG6200LAN: cnijnet:/2C-9E-FC-03-2C-14 Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox MarkForUpload: True Papersize: a4 PpdFiles: MG6200LAN: Canon MG6200 series Ver.3.60 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-26-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH + --- + ApportVersion: 2.17.2-0ubuntu1 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.04 + InstallationDate: Installed on 2015-04-29 (10 days ago) + InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + Lpstat: + device for Canon-PIXMA-MG6220: dnssd://Canon%20MG6200%20series._printer._tcp.local/ + device for Generic-CUPS-PDF-Printer: cups-pdf:/ + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: innotek GmbH VirtualBox + Package: cups 2.0.2-1ubuntu3 + PackageArchitecture: amd64 + Papersize: a4 + PpdFiles: + Error: command ['fgrep', '-H', '*NickName', 'Generic-CUPS-PDF-Printer.ppd', '/etc/cups/ppd/Canon-PIXMA-MG6220.ppd'] failed with exit code 2: /etc/cups/ppd/Generic-CUPS-PDF-Printer: Generic CUPS-PDF Printer + grep: /etc/cups/ppd/Canon-PIXMA-MG6220.ppd: Permission denied + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=87bf2e08-71a5-4d97-98b5-a3150b93acfa ro quiet splash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=87bf2e08-71a5-4d97-98b5-a3150b93acfa ro quiet splash + ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 + Tags: vivid apparmor apparmor apparmor apparmor apparmor apparmor + UdevLog: Error: [Errno 2] そのようなファイルやディレクトリはありません: '/var/log/udev' + Uname: Linux 3.19.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/01/2006 + dmi.bios.vendor: innotek GmbH + dmi.bios.version: VirtualBox + dmi.board.name: VirtualBox + dmi.board.vendor: Oracle Corporation + dmi.board.version: 1.2 + dmi.chassis.type:
[Bug 1205511] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394159/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394156/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394154/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394161/+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/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] PrintingPackages.txt
apport information ** Attachment added: "PrintingPackages.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394160/+files/PrintingPackages.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1205511/+attachment/4394157/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
I reproduced this issue with ubuntu-13.10-desktop-amd64.iso + apt-get dist-upgrade + apt_0.9.9.1~ubuntu3. ** Attachment added: "dpkg -l" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+attachment/4144372/+files/dpkg-l.downgrade.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
** Attachment added: "/var/log/dist-upgrade/ files" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+attachment/4144373/+files/dist-upgrade.downgrade.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
I reproduced this issue in ubuntu-13.10-desktop-amd64.iso. Now, I found https://launchpad.net/ubuntu/+source/apt/0.9.9.1~ubuntu3.1/+build/5879608 . I will try downgrade test in ubuntu-13.10-desktop-amd64.iso + apt-get dist-upgrade + apt_0.9.9.1~ubuntu3.1 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
I am downloading ubuntu-13.10-desktop-amd64.iso(not Japanese Remix) now. But Templer wrote https://forums.ubuntulinux.jp/viewtopic.php?pid=104596#p104596 . He said that he reproduced this issue on "not Japanese Remix". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
1. I installed ubuntu-ja-13.10-desktop-amd64.iso. 2. I installed ssh. 3.I try "sudo apt-get install apt=0.9.9.1~ubuntu3.1", But apt-get says "E: Version '0.9.9.1~ubuntu3.1' for 'apt' was not found". I can not install apt-0.9.9.1~ubuntu3.1 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
I can reproduce this environment. 1. I installed ubuntu-ja-13.10-desktop-amd64.iso. 2. I installed ssh. 3. I upgraded to newest Saucy. sudo apt-get update sudo apt-get upgrade sudo apt-get update sudo apt-get upgrade And I configured sshd environment (~/.ssh/authorized_keys, /etc/ssh/sshd_config). Dropbox and virtualbox-guest-* have nothing to do with this issue. ** Attachment added: "this OS's /var/log/dist-upgrade/ files" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+attachment/4144226/+files/dist-upgrade.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
>is it clean-installed? I installed Saucy by these 1-3 steps. 1. I installed ubuntu-ja-13.10-desktop-amd64.iso. 2. I upgraded to newest Saucy. sudo apt-get update sudo apt-get upgrade sudo apt-get update sudo apt-get upgrade 3. I installed these by apt-get for getting files from guest OS. These are all of additional install. 3.a. I installed sshd. And I configured sshd environment (~/.ssh/authorized_keys, /etc/ssh/sshd_config). 3.b. I installed virtualbox-guest-dkms, virtualbox-guest-x11, and virtualox-guest-utils. 3.c. I tried to install nautilus-drobbox, but I could not install it. (install process could not finish.) So I stopped install process of Dropbox. >could you please test with downgrade to 0.9.9.1~ubuntu3.1 before upgrade?(If you can easily do). I have a guest OS that applied only step "1.". (I can clone the OS). Now, the OS is "0.9.9.1~ubuntu3". How do I update to "0.9.9.1~ubuntu3.1"? Please teach it, then I can test it. I am going to test the OS installed only sshd (3.a.). Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
I learned that the do-release-upgrade outputs log files on /var/log/dist-upgrade/. So I attached them. ** Attachment added: "tarball of /var/log/dist-upgrade/" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+attachment/4143871/+files/dist-upgrade.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
I ran "sudo dpkg --configure -a" on the broken OS, so But the command exits status 1. And the OS could not repair. I attached a message from the command. ** Attachment added: ""sudo dpkg --configure -a"'s message." https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+attachment/4143869/+files/typescript2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
** Attachment added: "output of "dpkg --list" when before upgrade" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+attachment/4143437/+files/dpkg--list.before.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
** Attachment added: "output of "dpkg --list" when after upgrade" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+attachment/4143438/+files/dpkg--list.after.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] [NEW] The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
Public bug reported: 1) before$ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 after$ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 2) ubuntu-release-upgrader-core 1:0.205.6 dpkg 1.16.12ubuntu1.3 3) Run "do-release-upgrade" or "do-release-upgrade -d" I expected that upgrading are complited. 4) But upgrading are stopped, OS are broken in the half-finished states. 5) Additional. I can reproduce many times this issue on VirtualBox. But OS are broken, then it is difficult to offer the after states. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.6 ProcVersionSignature: Ubuntu 3.11.0-24.41-generic 3.11.10.11 Uname: Linux 3.11.0-24-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CrashDB: ubuntu Date: Tue Jul 1 21:04:51 2014 InstallationDate: Installed on 2014-07-01 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Build amd64 LIVE Binary 20131024-17:53 MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade saucy trusty ** Attachment added: "typescript text" https://bugs.launchpad.net/bugs/1336267/+attachment/4143067/+files/typescript.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336267] Re: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states.
** Attachment added: "/var/log/dpkg.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+attachment/4143070/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336267 Title: The do-release-upgrade can not complete upgrade to Trusty from Saucy because dpkg says "too many errors, stopping", and OS are broken in the half-finished states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1336267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331283] Re: The perlbrew-0.35-1 can not link math library in ja_JP.UTF-8 Locale .
>5) details Sorry . >I can build perl-5.20.0, and I can use Perl 5.20.0 . s/^/I expected that / -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331283 Title: The perlbrew-0.35-1 can not link math library in ja_JP.UTF-8 Locale . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perlbrew/+bug/1331283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331283] [NEW] The perlbrew-0.35-1 can not link math library in ja_JP.UTF-8 Locale .
Public bug reported: 1) The release of Ubuntu $ lsb_release -rd Description:Ubuntu 12.04.4 LTS Release:12.04 2) The version of the package $ LANG=C apt-cache policy perlbrew perlbrew: Installed: 0.35-1 Candidate: 0.35-1 Version table: *** 0.35-1 0 500 http://jp.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected that I can build perl-5.20.0, and I can use Perl 5.20.0 . 4) What happened instead I could not find -lm library, could not link -lm, could not build Perl 5.20.0, and I could not use it . 5) details I am using Ubuntu 12.04 on Sony PCG-SRX7S/P Memory 512 M byte ( http://www.sony.jp/products/biz/vaio/PCG-SRX7S_P/spec.html ) . And I am using Ubuntu 12.04 32 bit on VirtualBox 4.3.12 r93733 in Windows 7 64 bit . Both Ubuntu 12.04 can not link math library in ja_JP.UTF-8 Locale . $echo $LANG ja_JP.UTF-8 $sudo apt-get install perlbrew $perlbrew init $source ~/perl5/perlbrew/etc/bashrc $perlbrew install perl-5.20.0 I can build perl-5.20.0, and I can use Perl 5.20.0 . But I could not find -lm library, could not link -lm, could not build Perl 5.20.0, and I could not use it. stdout and stderr messages Fetching perl-5.20.0 as /home/mitsutoshi/perl5/perlbrew/dists/perl-5.20.0.tar.gz Installing /home/mitsutoshi/perl5/perlbrew/build/perl-5.20.0 into ~/perl5/perlbrew/perls/perl-5.20.0 This could take a while. You can run the following command on another shell to track the status: tail -f ~/perl5/perlbrew/build.log Installing /home/mitsutoshi/perl5/perlbrew/build/perl-5.20.0 failed. See /home/mitsutoshi/perl5/perlbrew/build.log to see why. If you want to force install the distribution, try: perlbrew --force install perl-5.20.0 in ~/perl5/perlbrew/build.log cc -fstack-protector -L/usr/local/lib -o miniperl \ perlmini.o opmini.o miniperlmain.o gv.o toke.o perly.o pad.o regco mp.o dump.o util.o mg.o reentr.o mro.o keywords.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o univ ersal.o globals.o perlio.o perlapi.o numeric.o mathoms.o locale.o pp_pack.o pp_s ort.o caretx.o pp.o: In function `Perl_pp_pow': pp.c:(.text+0x2ff5): undefined reference to `pow' pp.o: In function `Perl_pp_modulo': pp.c:(.text+0x38af): undefined reference to `floor' pp.c:(.text+0x38d8): undefined reference to `floor' pp.c:(.text+0x3c67): undefined reference to `fmod' pp.o: In function `Perl_pp_atan2': pp.c:(.text+0x7073): undefined reference to `atan2' pp.o: In function `Perl_pp_sin': pp.c:(.text+0x7211): undefined reference to `sin' pp.o: In function `Perl_pp_int': pp.c:(.text+0x7692): undefined reference to `ceil' pp.c:(.text+0x76d1): undefined reference to `floor' pp.o:(.rodata+0x164): undefined reference to `cos' pp.o:(.rodata+0x168): undefined reference to `sin' pp.o:(.rodata+0x16c): undefined reference to `sin' pp.o:(.rodata+0x170): undefined reference to `exp' pp.o:(.rodata+0x174): undefined reference to `log' pp.o:(.rodata+0x178): undefined reference to `sqrt' pp_sys.o: In function `S_gmtime64_r.isra.3': pp_sys.c:(.text+0x24a): undefined reference to `ceil' pp_sys.c:(.text+0x2a3): undefined reference to `ceil' pp_sys.c:(.text+0x2fc): undefined reference to `ceil' pp_sys.c:(.text+0x3ce): undefined reference to `floor' pp_sys.c:(.text+0x5d0): undefined reference to `ceil' pp_sys.c:(.text+0x781): undefined reference to `floor' pp_sys.c:(.text+0x7d9): undefined reference to `floor' pp_sys.c:(.text+0x7f1): undefined reference to `floor' pp_sys.c:(.text+0x839): undefined reference to `fmod' pp_sys.c:(.text+0x872): undefined reference to `fmod' pp_sys.c:(.text+0x8a9): undefined reference to `fmod' pp_sys.c:(.text+0x8d6): undefined reference to `fmod' pp_sys.o: In function `Perl_pp_gmtime': pp_sys.c:(.text+0xbe8f): undefined reference to `floor' pp_sys.c:(.text+0xbfd1): undefined reference to `floor' pp_pack.o: In function `S_pack_rec': pp_pack.c:(.text+0x1a7e): undefined reference to `floor' pp_pack.c:(.text+0x1aa2): undefined reference to `floor' pp_pack.c:(.text+0x1ac0): undefined reference to `floor' (snip) 6) Additional: 1: I can build perl-5.20.0 with LANG=C locale . $LANG=C perlbrew install perl-5.20.0 But I can not use it because $PATH environment is broken . $perlbrew switch perl-5.20.0 $echo $PATH /home/mitsutoshi/perl5/perlbrew/bin: 2: I could build perl-5.20.0 using upstream's Perlbrew 0.68 $echo $LANG ja_JP.UTF-8 $curl -L http://install.perlbrew.pl | bash $perlbrew init $source ~/perl5/perlbrew/etc/bashrc $perlbrew install perl-5.20.0 $perlbrew switch perl-5.20.0 -> OK 3: I can build perl-5.20.0 with perlbrew-0.66-1 on Ubuntu 14.04 . $sudo apt-get install perlbrew $perlbrew --version /usr/bin/perlbrew - App::perlbrew/0.66 $perlbrew init $source ~/perl5/perlbrew/etc/bashrc $vi .bash_profile $perlbrew install perl-5.20.0 $perlbrew switch perl-5.20.0 $ perl -V | head S
[Bug 1204690] Re: update-manager says failed allways .
Sometimes this problem is reproduced . Please see also https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1206331 . This problem is reproduced on 13.10 daily (saucy) too . Please see also https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1206574 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1204690 Title: update-manager says failed allways . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1204690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206574] [NEW] Sometimes the update-manager says failed on saucy (daily 1310) .
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Saucy Salamander (development branch) Release:13.10 Codename: saucy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center update-manager: 1:0.190 update-notifier: 0.143 apt: 0.9.9.1~ubuntu1 dpkg: 1.16.10ubuntu3 3) What you expected to happen I expected that update would be completed normally . 4) What happened instead The update-notifier said failed . 5) I am testing Ubuntu 13.10 daily saucy i386 in VirtualBox 4.2.16 r86992 on Windows 7 SP1 64 bit . And I am using 13.04 raring i386 in VirtualBox 4.2.16 r86992 on Windows 7 SP1 64 bit . Host information: https://dl.dropboxusercontent.com/u/86335040/DxDiag17.txt . Sometimes the update-manager says failed on 13.10 and 13.04 . I think that the update-manager says failed when the kernel is updated . I attached dpkg and apt logs . Please see also: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1204690 https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1206331 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: update-manager 1:0.190 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic i686 ApportVersion: 2.11-0ubuntu1 Aptdaemon: Jul 31 00:25:41 mitsutoshi-VirtualBox AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/6a78b4ef5925430fb5a2962b9df8fa3b Architecture: i386 Date: Wed Jul 31 00:27:26 2013 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1375190423' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-width' b'496' InstallationDate: Installed on 2013-07-10 (19 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130710) MarkForUpload: True PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy ** Attachment added: "dpkg and apt logs ." https://bugs.launchpad.net/bugs/1206574/+attachment/3754678/+files/log.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206574 Title: Sometimes the update-manager says failed on saucy (daily 1310) . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1206574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206331] Re: Sometimes update-notifier says failed .
This problem is reproduced on 13.10 daily (saucy) too . Please see also https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1206574 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206331 Title: Sometimes update-notifier says failed . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1206331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206331] [NEW] Sometimes update-notifier says failed .
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 13.04 Release:13.04 Codename: raring 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center update-notifier: 0.134 update-manager: 1:0.186.1 apt: 0.9.7.7ubuntu4 dpkg: 1.16.10ubuntu1 3) What you expected to happen I expected that update would be completed normally . 4) What happened instead The update-notifier said failed . 5) Please see also https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1204690 . ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: update-notifier-common 0.134 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jul 30 11:05:00 2013 ExecutablePath: /usr/lib/update-notifier/backend_helper.py InstallationDate: Installed on 2013-05-14 (76 days ago) InstallationMedia: Ubuntu 13.04 "Raring" - Build i386 LIVE Binary 20130430-17:57 InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Attachment added: "dpkg and apt log" https://bugs.launchpad.net/bugs/1206331/+attachment/3753896/+files/log.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206331 Title: Sometimes update-notifier says failed . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1206331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205583] [NEW] nautilus crashed with SIGABRT in __GI___assert_fail (assertion=assertion@entry=0xb6fc1419 "ret != inval_id", file=file@entry=0xb6fc138a "../../src/xcb_io.c", line=line@entry=529, f
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 13.04 Release:13.04 Codename: raring 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center nautilus: 1:3.6.3-0ubuntu16 3) What you expected to happen I expected that the nautilus operated normally . 4) What happened instead The nautilus crashed with SIGABRT in __GI___assert_fail ( assertion=assertion@entry=0xb6fc1419 "ret != inval_id", file=file@entry=0xb6fc138a "../../src/xcb_io.c", line=line@entry=529, function=function@entry=0xb6fc149e <__PRETTY_FUNCTION__.14075> "_XAllocID") at assert.c:101 . ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Sat Jul 27 16:14:04 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+65+24'" InstallationDate: Installed on 2013-05-14 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring" - Build i386 LIVE Binary 20130430-17:57 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Attachment added: "crash dump and GDB backtrace" https://bugs.launchpad.net/bugs/1205583/+attachment/3750642/+files/_usr_bin_nautilus.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205583 Title: nautilus crashed with SIGABRT in __GI___assert_fail (assertion=assertion@entry=0xb6fc1419 "ret != inval_id", file=file@entry=0xb6fc138a "../../src/xcb_io.c", line=line@entry=529, function=function@entry=0xb6fc149e <__PRETTY_FUNCTION__.14075> "_XAllocID") at assert.c:101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1205583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205511] [NEW] The lpr and lp can not print Multilingual (Japanese) characters .
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 13.04 Release:13.04 Codename: raring 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center cups-bsd: 1.6.2-1ubuntu5 cups-client: 1.6.2-1ubuntu5 cups-filters: 1.0.34-0ubuntu1.1 3) What you expected to happen I expected to print Japanese characters . ex. $ echo '星' | lpr I expected to lpr and lp to be able to print multilingual characters . 4) What happened instead But the printer printed '?' . ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups-bsd 1.6.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CupsErrorLog: W [27/Jul/2013:07:14:32 +0900] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_MG6200LAN W [27/Jul/2013:07:14:32 +0900] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_MG6200LAN W [27/Jul/2013:07:14:32 +0900] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_MG6200LAN W [27/Jul/2013:07:14:32 +0900] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_MG6200LAN Date: Sat Jul 27 07:15:41 2013 InstallationDate: Installed on 2013-05-14 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring" - Build i386 LIVE Binary 20130430-17:57 Lpstat: device for MG6200LAN: cnijnet:/2C-9E-FC-03-2C-14 Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox MarkForUpload: True Papersize: a4 PpdFiles: MG6200LAN: Canon MG6200 series Ver.3.60 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-26-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205511 Title: The lpr and lp can not print Multilingual (Japanese) characters . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1205511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1204690] Re: update-manager says failed allways .
Today, the update-manager completed normally . I said "always", but it is an error . ** Attachment added: "/var/log/dpkg.log" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1204690/+attachment/3749335/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1204690 Title: update-manager says failed allways . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1204690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1204690] [NEW] update-manager says failed allways .
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 13.04 Release:13.04 Codename: raring 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center update-manager: 1:0.186.1 apt: 0.9.7.7ubuntu4 dpkg: 1.16.10ubuntu1 3) What you expected to happen I expected that update would be completed normally . 4) What happened instead The update-manager said failed . ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: update-manager 1:0.186.1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Thu Jul 25 07:31:08 2013 ExecutablePath: /usr/bin/update-manager GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1374704070' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-width' b'499' InstallationDate: Installed on 2013-05-14 (71 days ago) InstallationMedia: Ubuntu 13.04 "Raring" - Build i386 LIVE Binary 20130430-17:57 InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1204690 Title: update-manager says failed allways . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1204690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203747] [NEW] "sudo taskesl install kubuntu-full" says "tasksel: apptitude failed (100)", then fails .
Public bug reported: I am using Ubuntu 13.04 and 13.10 daily in VirtualBox 4.2.16 r86992 on Windows 7 SP1 64 bit . Host information: https://dl.dropboxusercontent.com/u/86335040/DxDiag17.txt . I input "sudo taskesl install kubuntu-full" . Then tasksel says "tasksel: apptitude failed (100)", and tasksel fails . 1) The release of Ubuntu you are using lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 13.04 Release:13.04 Codename: raring 2) The version of the package tasksel 2.88ubuntu14 aptitude 0.6.8.1-2ubuntu2 dpkg 1.16.10ubuntu1 3) What you expected to happen I expected that installation was completed. 4) What happened instead The tasksel said "tasksel: apptitude failed (100)", and tasksel failed . ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: tasksel 2.88ubuntu14 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Mon Jul 22 21:38:05 2013 InstallationDate: Installed on 2013-05-14 (68 days ago) InstallationMedia: Ubuntu 13.04 "Raring" - Build i386 LIVE Binary 20130430-17:57 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: tasksel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tasksel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203747 Title: "sudo taskesl install kubuntu-full" says "tasksel: apptitude failed (100)", then fails . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tasksel/+bug/1203747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181134] Re: xfce4-indicator-plugin crashed with SIGSEGV in g_type_check_instance_cast()
When I logouted, xfce4-indicator-plugin crashed with SIGSEGV in g_type_check_instance_cast() . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181134 Title: xfce4-indicator-plugin crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator-plugin/+bug/1181134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186936] Re: do-release-upgrade -d crash when trying to upgrade to saucy
I performed update-manager on 2013-July-06 . The update-manager said "Software Updater Not all updates can be installed Run a partial upgrade, to install as many updates as possible. This can be cased by: * A previous upgrade which didn't complete * Problems with some of the installed software * Unofficial software packages not provided by Ubuntu * Normal changes of a pre-releaes version of Ubuntu" So I selected "Partial Upgrade" . Then update-manager said " Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade: The package 'ubuntu-desktop' is marked for removal but it is in the removal blacklist. This can be caused by: * Upgrading to a pre-releae version of Ubuntu * Running the current pre-relase version of Ubuntu * Unofficial software packages not provided by Ubuntu This is most likely a transient problem, please try again later ." Then I selected "Close" . Then do-release-upgrade crashed and https://bugs.launchpad.net/bugs/1194870 opened but I coulud not see this report . Then searched launchpad with "saucy do-release-upgrade update-manager" . And I found this report . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186936 Title: do-release-upgrade -d crash when trying to upgrade to saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1186936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186936] Re: do-release-upgrade -d crash when trying to upgrade to saucy
I performed update-manager on 2013-July-06 . ** Attachment added: "/var/log/dist-upgrade/apt.log and crash dump" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1186936/+attachment/3726488/+files/do-release-upgrade.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186936 Title: do-release-upgrade -d crash when trying to upgrade to saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1186936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 840549] Re: hypertorus screensaver crashed in a VirtualBox VM
I am using Ubuntu 13.04 and Ubuntu 13.10 daily on VirtualBox . And I performed "sudo tasksel xubuntu-desktop" . The xscreensaver-gl pakage's screensavers crashed many time . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/840549 Title: hypertorus screensaver crashed in a VirtualBox VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/840549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105758] Re: On my PC, gcry_cipher_encrypt() doesn't release all x87 FPU data registers .
The patch was released to Gcrypt-devel ML ( http://lists.gnupg.org/mailman/listinfo/gcrypt-devel ) . For the people troubled by this problem, I wrote that how to apply the patch *** How to apply the patch . *** 1. Get source . $apt-get -b source libgcrypt11 $ cd libgcrypt11-1.5.0 NOTE: Additional packages may be required at this time and you may become an error. Follow directions then . ex) $ sudo apt-get install dpkg-dev $ sudo apt-get install debhelper texlive-latex-base texlive-generic-recommended texinfo cdbs libgpg-error-dev autotools-dev 2. Get the patch . 2.1. Access by your Web browser to http://marc.info/?l=gcrypt-devel&m=135944673925649&w=2 2.2. Start your editor. $vi mail.patch 2.3. Copy&paste the mail message whole sentence . 2.4. Save it NOTE: Don't use wget . 3. Apply the patch . $ patch -p1 -b https://bugs.launchpad.net/bugs/1105758 Title: On my PC, gcry_cipher_encrypt() doesn't release all x87 FPU data registers . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1105758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105758] Re: On my PC, gcry_cipher_encrypt() doesn't release all x87 FPU data registers .
Hi . I found the position of the problem, then I wrote a patch . When adapted in this patch, the test of gnome-keyring was OK . However, I cannot judge whether this correction is right . And I cannot judge whether there is the same problem as other parts . I want you to check these . And although "libgcrypt11:i386" is the i386 architecture, I cannot judge whether it is allowed to call MMX instructions by the i386 architecture. Then, I wish for the view from intellectuals . Thanks . ** Patch added: "rijndael.c.diff" https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1105758/+attachment/3502379/+files/rijndael.c.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105758 Title: On my PC, gcry_cipher_encrypt() doesn't release all x87 FPU data registers . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1105758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105758] [NEW] On my PC, gcry_cipher_encrypt() doesn't release all x87 FPU data registers .
Public bug reported: 1) Description:Xubuntu 12.10 desktop i386 Release:12.10 PC: Sony PCG-SRX7S/P Memory 512 M byte http://www.sony.jp/products/biz/vaio/PCG-SRX7S_P/spec.html Chipset: Intel 815EM $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 11 model name : Mobile Intel(R) Pentium(R) III CPU - M 900MHz stepping: 4 microcode : 0x2 cpu MHz : 500.000 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pse36 mmx fxsr sse up bogomips: 993.64 clflush size: 32 cache_alignment : 32 address sizes : 36 bits physical, 32 bits virtual power management: $ uname -a Linux loghost 3.5.0-22-generic #34-Ubuntu SMP Tue Jan 8 21:41:11 UTC 2013 i686 i686 i686 GNU/Linux 2) libgcrypt11 1.5.0-3ubuntu1 gnome-keyring 3.6.1-0ubuntu1 3) What you expected to happen $apt-get -b source gnome-keyring $cd gnome-keyring-3.6.1/ $make -k check | tee make-k-check2.txt →all check OK 4) What happened instead → but /gnome2-store/import/pkcs12: was FAIL on the PC . See also https://dl.dropbox.com/u/86335040/make-k-check2.txt . 5) I analyzed the gnome-keyring program. So I found that gcry_cipher_encrypt() doesn't release all x87 FPU data registers . Then -nan goes into a variable subsequent processing. This problem found on the test of /gnome2-store/import/pkcs12 on gnome-keyring-3.6.1, function is encrypt_buffer() in gnome-keyring-3.6.1/pkcs11/gnome2-store/gkm-gnome2-file.c . I wrote a reappearance program . https://dl.dropbox.com/u/86335040/bug.tar.gz . Please check it, and please fix this problem See also https://forums.ubuntulinux.jp/viewtopic.php?id=14643 and http://d.hatena.ne.jp/Itisango/searchdiary?word=%2A%5Bgnome-keyring%5D . Thanks . ** Affects: libgcrypt11 (Ubuntu) Importance: Undecided Status: New ** Tags: fpu gnome-keyring libgcrypt11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105758 Title: On my PC, gcry_cipher_encrypt() doesn't release all x87 FPU data registers . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1105758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
