[Touch-packages] [Bug 1074879] Re: Xorg freeze
.tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2014-10-27 10:34:38,268 DEBUG The following packages are marked for removal: libavformat54 libcdr-0.0-0 libplist1 gcc-4.8-base:i386 libgdata13 libexiv2-12 libepoxy0 liboil0.3 libass4 libmspub-0.0-0 libwpg-0.2-2 libcolorhug1 libgnome-desktop-3-7 liborcus-0.6-0 libopenjpeg2 linux-image-extra-3.13.0-30-generic libvisio-0.0-0 linux-image-3.13.0-30-generic libpoppler44 libreoffice-presentation-minimizer python-ibus librtmp0 libswscale2 linux-headers-3.13.0-24 linux-headers-3.13.0-30-generic linux-headers-3.13.0-30 linux-headers-3.13.0-37 libparted0debian1 libcamel-1.2-45 libwps-0.2-2 libwpd-0.9-9 libgtop2-7 linux-image-extra-3.13.0-24-generic libt1-5 libcolord1 linux-headers-3.13.0-37-generic linux-image-3.13.0-24-generic libqmi-glib0 libplymouth2 libgnutls26:i386 qtdeclarative5-ubuntu-ui-extras-browser-plugin-assets libavcodec54 linux-headers-3.13.0-24-generic libraw9 libavutil52 DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M G] [10de:0428] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:1422] InstallationDate: Installed on 2014-04-18 (211 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: FUJITSU SIEMENS LIFEBOOK E8410 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=219eb9d8-d2a9-4f91-9545-31ad28db91a9 ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Tags: utopic third-party-packages ubuntu compiz-0.9 Uname: Linux 3.16.0-24-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (19 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.15 dmi.board.name: FJNB1D0 dmi.board.vendor: FUJITSU dmi.board.version: CP335601-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: E8410 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd02/25/2008:svnFUJITSUSIEMENS:pnLIFEBOOKE8410:pvr:rvnFUJITSU:rnFJNB1D0:rvrCP335601-02:cvnFUJITSUSIEMENS:ct10:cvrE8410: dmi.product.name: LIFEBOOK E8410 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58+git1411031830.00847f~gd~u version.libgl1-mesa-dri: libgl1-mesa-dri 10.4~git1411140730.bd20fa~gd~u version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4~git1411140730.bd20fa~gd~u version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.99+git140730.2f11dc~gd~u version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git1411141930.6c2707~gd~u version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git1411032101.3fb97d~gd~u xserver.bootTime: Sun Nov 16 09:04:22 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-D-1 LVDS-1 VGA-1 xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: nouveau ** Tags added: apport-collected compiz-0.9 third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1074879] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261659/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] BootLog.txt
apport information ** Attachment added: BootLog.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261660/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261662/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261661/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261663/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261664/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] LightdmDisplayLog.txt
apport information ** Attachment added: LightdmDisplayLog.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261665/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] LightdmGreeterLog.txt
apport information ** Attachment added: LightdmGreeterLog.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261666/+files/LightdmGreeterLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] PccardctlIdent.txt
apport information ** Attachment added: PccardctlIdent.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261671/+files/PccardctlIdent.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261670/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] PccardctlStatus.txt
apport information ** Attachment added: PccardctlStatus.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261672/+files/PccardctlStatus.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261674/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261673/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261675/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261678/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261679/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] LightdmGreeterLogOld.txt
apport information ** Attachment added: LightdmGreeterLogOld.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261667/+files/LightdmGreeterLogOld.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261680/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261681/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] LightdmLog.txt
apport information ** Attachment added: LightdmLog.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261668/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261682/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] xserver.devices.txt
apport information ** Attachment added: xserver.devices.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261684/+files/xserver.devices.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261683/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261676/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1074879/+attachment/4261677/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381010] Re: Cannot get Chinese string in the scope setting
** Tags added: univ-train -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1381010 Title: Cannot get Chinese string in the scope setting Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: In Progress Bug description: I am trying to set some Chinese Strings in the scope. however, I cannot get it but the default one. If I input an English string there in the setting, I can always get it correctly. My test code is at: bzr branch lp:~liu-xiao- guo/debiantrial/settingscope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1381010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393151] [NEW] Writing to ext4 LVM FS causes GPF in mpage_process_page_bufs
Public bug reported: Writing data to a 3 TB ext4-formatted logical volume on a 2x6 TB mdadm raid 1 mirror always results in a GPF within 1 minute of writing the data. Disks seem to be OK smart-wise. When the GPF occurs, the md1 raid volume gets degrated, the entire system gets irresponsive and after the next boot (hard reset), the raid syncing starts from scratch (which takes 10 hours with the two 6 TB drives). The GPF always happens in mpage_process_page_bufs: Nov 16 09:26:03 nas kernel: [ 230.610495] [ cut here ] Nov 16 09:26:03 nas kernel: [ 230.610510] WARNING: CPU: 1 PID: 1927 at /build/buildd/linux-3.13.0/kernel/exit.c:711 do_exit+0x55/0xa50() Nov 16 09:26:03 nas kernel: [ 230.610531] Modules linked in: ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_codec_hdmi arc4 bridge stp llc x86_pkg_temp_thermal intel_powerc$ Nov 16 09:26:03 nas kernel: [ 230.610810] CPU: 1 PID: 1927 Comm: vsftpd Tainted: G D 3.13.0-39-generic #66-Ubuntu Nov 16 09:26:03 nas kernel: [ 230.610830] Hardware name: Gigabyte Technology Co., Ltd. H97N-WIFI/H97N-WIFI, BIOS F4 06/28/2014 Nov 16 09:26:03 nas kernel: [ 230.610849] 0009 8800cb61d9e0 8171ece7 Nov 16 09:26:03 nas kernel: [ 230.610877] 8800cb61da18 8106773d 000b 8800cb61db38 Nov 16 09:26:03 nas kernel: [ 230.610898] 0246 8800cb633000 8800cb61da28 Nov 16 09:26:03 nas kernel: [ 230.610920] Call Trace: Nov 16 09:26:03 nas kernel: [ 230.610928] [8171ece7] dump_stack+0x45/0x56 Nov 16 09:26:03 nas kernel: [ 230.610941] [8106773d] warn_slowpath_common+0x7d/0xa0 Nov 16 09:26:03 nas kernel: [ 230.610956] [8106781a] warn_slowpath_null+0x1a/0x20 Nov 16 09:26:03 nas kernel: [ 230.610970] [81069a45] do_exit+0x55/0xa50 Nov 16 09:26:03 nas kernel: [ 230.610984] [817282b9] oops_end+0xa9/0x150 Nov 16 09:26:03 nas kernel: [ 230.610997] [810171cb] die+0x4b/0x70 Nov 16 09:26:03 nas kernel: [ 230.611008] [81727c4e] do_general_protection+0x11e/0x1b0 Nov 16 09:26:03 nas kernel: [ 230.611024] [81727568] general_protection+0x28/0x30 Nov 16 09:26:03 nas kernel: [ 230.611039] [8123e0b8] ? mpage_process_page_bufs+0x38/0x130 Nov 16 09:26:03 nas kernel: [ 230.611055] [8123f0e9] mpage_prepare_extent_to_map+0x219/0x2c0 Nov 16 09:26:03 nas kernel: [ 230.611071] [81242ef2] ext4_writepages+0x3f2/0xd20 Nov 16 09:26:03 nas kernel: [ 230.611086] [8115a9be] do_writepages+0x1e/0x40 Nov 16 09:26:03 nas kernel: [ 230.611101] [8114fac9] __filemap_fdatawrite_range+0x59/0x60 Nov 16 09:26:03 nas kernel: [ 230.67] [8114fb7c] filemap_flush+0x1c/0x20 Nov 16 09:26:03 nas kernel: [ 230.611130] [81240928] ext4_alloc_da_blocks+0x38/0x70 Nov 16 09:26:03 nas kernel: [ 230.611156] [81239e89] ext4_release_file+0x79/0xc0 Nov 16 09:26:03 nas kernel: [ 230.611171] [811bed84] __fput+0xe4/0x260 Nov 16 09:26:03 nas kernel: [ 230.611184] [811bef4e] fput+0xe/0x10 Nov 16 09:26:03 nas kernel: [ 230.611197] [81088227] task_work_run+0xa7/0xe0 Nov 16 09:26:03 nas kernel: [ 230.611210] [81013df7] do_notify_resume+0x97/0xb0 Nov 16 09:26:03 nas kernel: [ 230.611225] [8172faaa] int_signal+0x12/0x17 Nov 16 09:26:03 nas kernel: [ 230.612259] ---[ end trace c2c7ff1f119c2b75 ]--- apt-cache policy e2fslibs:amd64 e2fslibs: Installed: 1.42.9-3ubuntu1 Candidate: 1.42.9-3ubuntu1 Version table: *** 1.42.9-3ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED smartctl -H /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED /dev/md1: Version : 1.2 Creation Time : Sat Nov 15 20:27:36 2014 Raid Level : raid1 Array Size : 5860389696 (5588.90 GiB 6001.04 GB) Used Dev Size : 5860389696 (5588.90 GiB 6001.04 GB) Raid
[Touch-packages] [Bug 1393152] [NEW] establish connection even if wireless hardware is removed
Public bug reported: Hallo TESTCASE: Start from a fully working wireless connection. *Shutdown *Phisically remove the wireless card and connect with ethernet *Reboot *Sometime you will see the NM trying to connect to wireless net and sometime stating that is connected Is expected that it don't try to connect to a not existing net (no way to receive) Best regards ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.8.8-0ubuntu34 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 16 10:07:46 2014 EcryptfsInUse: Yes IpRoute: default via 192.168.0.1 dev eth0 proto static 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.12 metric 1 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-08-21T11:25:28.586075 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH retenjin 2fce5e43-bae6-4b88-8f7d-96bdfe5a2e4d 802-11-wireless 1416128840 dom 16 nov 2014 10:07:20 CET yes no /org/freedesktop/NetworkManager/Settings/2 Auto Ethernet f8e95dc1-09fc-4b20-95c1-c3deb1ec1502 802-3-ethernet1416128759 dom 16 nov 2014 10:05:59 CET yes no /org/freedesktop/NetworkManager/Settings/1 retenjin_EXT 0aa3e412-316b-489a-b9cf-1749f3ff668b 802-11-wireless 1410629422 sab 13 set 2014 19:30:22 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug vivid ** Changed in: network-manager (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1393152 Title: establish connection even if wireless hardware is removed Status in “network-manager” package in Ubuntu: Invalid Bug description: Hallo TESTCASE: Start from a fully working wireless connection. *Shutdown *Phisically remove the wireless card and connect with ethernet *Reboot *Sometime you will see the NM trying to connect to wireless net and sometime stating that is connected Is expected that it don't try to connect to a not existing net (no way to receive) Best regards ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.8.8-0ubuntu34 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 16 10:07:46 2014 EcryptfsInUse: Yes IpRoute: default via 192.168.0.1 dev eth0 proto static 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.12 metric 1 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-08-21T11:25:28.586075 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH retenjin 2fce5e43-bae6-4b88-8f7d-96bdfe5a2e4d 802-11-wireless 1416128840 dom 16 nov 2014 10:07:20 CET yes no /org/freedesktop/NetworkManager/Settings/2 Auto Ethernet f8e95dc1-09fc-4b20-95c1-c3deb1ec1502 802-3-ethernet1416128759 dom 16 nov 2014 10:05:59 CET yes no /org/freedesktop/NetworkManager/Settings/1 retenjin_EXT 0aa3e412-316b-489a-b9cf-1749f3ff668b 802-11-wireless 1410629422 sab 13 set 2014 19:30:22 CEST yes no
[Touch-packages] [Bug 1393151] Re: Writing to ext4 LVM FS causes GPF in mpage_process_page_bufs
** Description changed: - Writing data to a 3 TB ext4-formatted logical volume on a 2x6 TB mdadm - raid 1 mirror always results in a GPF within 1 minute of writing the - data. Disks seem to be OK smart-wise. - - When the GPF occurs, the md1 raid volume gets degrated, the entire + Writing lots of data to a 3 TB ext4-formatted logical volume on a 2x6 TB + mdadm raid 1 mirror always results in a GPF within 1 minute of writing + the data. Disks seem to be OK smart-wise. + + When the GPF occurs, the md1 raid volume gets degraded, the entire system gets irresponsive and after the next boot (hard reset), the raid syncing starts from scratch (which takes 10 hours with the two 6 TB - drives). + drives to complete). The GPF occurs when the raid is still syncing and + also after it is in sync. The GPF always happens in mpage_process_page_bufs: Nov 16 09:26:03 nas kernel: [ 230.610495] [ cut here ] Nov 16 09:26:03 nas kernel: [ 230.610510] WARNING: CPU: 1 PID: 1927 at /build/buildd/linux-3.13.0/kernel/exit.c:711 do_exit+0x55/0xa50() Nov 16 09:26:03 nas kernel: [ 230.610531] Modules linked in: ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_codec_hdmi arc4 bridge stp llc x86_pkg_temp_thermal intel_powerc$ Nov 16 09:26:03 nas kernel: [ 230.610810] CPU: 1 PID: 1927 Comm: vsftpd Tainted: G D 3.13.0-39-generic #66-Ubuntu Nov 16 09:26:03 nas kernel: [ 230.610830] Hardware name: Gigabyte Technology Co., Ltd. H97N-WIFI/H97N-WIFI, BIOS F4 06/28/2014 Nov 16 09:26:03 nas kernel: [ 230.610849] 0009 8800cb61d9e0 8171ece7 Nov 16 09:26:03 nas kernel: [ 230.610877] 8800cb61da18 8106773d 000b 8800cb61db38 Nov 16 09:26:03 nas kernel: [ 230.610898] 0246 8800cb633000 8800cb61da28 Nov 16 09:26:03 nas kernel: [ 230.610920] Call Trace: Nov 16 09:26:03 nas kernel: [ 230.610928] [8171ece7] dump_stack+0x45/0x56 Nov 16 09:26:03 nas kernel: [ 230.610941] [8106773d] warn_slowpath_common+0x7d/0xa0 Nov 16 09:26:03 nas kernel: [ 230.610956] [8106781a] warn_slowpath_null+0x1a/0x20 Nov 16 09:26:03 nas kernel: [ 230.610970] [81069a45] do_exit+0x55/0xa50 Nov 16 09:26:03 nas kernel: [ 230.610984] [817282b9] oops_end+0xa9/0x150 Nov 16 09:26:03 nas kernel: [ 230.610997] [810171cb] die+0x4b/0x70 Nov 16 09:26:03 nas kernel: [ 230.611008] [81727c4e] do_general_protection+0x11e/0x1b0 Nov 16 09:26:03 nas kernel: [ 230.611024] [81727568] general_protection+0x28/0x30 Nov 16 09:26:03 nas kernel: [ 230.611039] [8123e0b8] ? mpage_process_page_bufs+0x38/0x130 Nov 16 09:26:03 nas kernel: [ 230.611055] [8123f0e9] mpage_prepare_extent_to_map+0x219/0x2c0 Nov 16 09:26:03 nas kernel: [ 230.611071] [81242ef2] ext4_writepages+0x3f2/0xd20 Nov 16 09:26:03 nas kernel: [ 230.611086] [8115a9be] do_writepages+0x1e/0x40 Nov 16 09:26:03 nas kernel: [ 230.611101] [8114fac9] __filemap_fdatawrite_range+0x59/0x60 Nov 16 09:26:03 nas kernel: [ 230.67] [8114fb7c] filemap_flush+0x1c/0x20 Nov 16 09:26:03 nas kernel: [ 230.611130] [81240928] ext4_alloc_da_blocks+0x38/0x70 Nov 16 09:26:03 nas kernel: [ 230.611156] [81239e89] ext4_release_file+0x79/0xc0 Nov 16 09:26:03 nas kernel: [ 230.611171] [811bed84] __fput+0xe4/0x260 Nov 16 09:26:03 nas kernel: [ 230.611184] [811bef4e] fput+0xe/0x10 Nov 16 09:26:03 nas kernel: [ 230.611197] [81088227] task_work_run+0xa7/0xe0 Nov 16 09:26:03 nas kernel: [ 230.611210] [81013df7] do_notify_resume+0x97/0xb0 Nov 16 09:26:03 nas kernel: [ 230.611225] [8172faaa] int_signal+0x12/0x17 Nov 16 09:26:03 nas kernel: [ 230.612259] ---[ end trace c2c7ff1f119c2b75 ]--- apt-cache policy e2fslibs:amd64 e2fslibs: - Installed: 1.42.9-3ubuntu1 - Candidate: 1.42.9-3ubuntu1 - Version table: - *** 1.42.9-3ubuntu1 0 - 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.42.9-3ubuntu1 + Candidate: 1.42.9-3ubuntu1 + Version table: + *** 1.42.9-3ubuntu1 0 + 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen,
[Touch-packages] [Bug 1393153] [NEW] I was preparing to scan a document with Simple Scan.
Public bug reported: I am new and my summary is all I really know? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Sun Nov 16 19:50:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7800] InstallationDate: Installed on 2014-11-11 (5 days ago) InstallationMedia: Kubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: MEDION MS-7800 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0f81aa7a-1b64-4cea-85d6-6d5d53d7459f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M7800W08.209 dmi.board.name: MS-7800 dmi.board.vendor: MEDION dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM7800W08.209:bd11/02/2012:svnMEDION:pnMS-7800:pvr1.0:rvnMEDION:rnMS-7800:rvr1.0:cvnMEDION:ct3:cvr: dmi.product.name: MS-7800 dmi.product.version: 1.0 dmi.sys.vendor: MEDION version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 16 19:47:25 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 inputUVC Camera (046d:0824) KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1393153 Title: I was preparing to scan a document with Simple Scan. Status in “xorg” package in Ubuntu: New Bug description: I am new and my summary is all I really know? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Sun Nov 16 19:50:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7800] InstallationDate: Installed on 2014-11-11 (5 days ago) InstallationMedia: Kubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: MEDION MS-7800 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0f81aa7a-1b64-4cea-85d6-6d5d53d7459f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M7800W08.209 dmi.board.name: MS-7800 dmi.board.vendor: MEDION dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM7800W08.209:bd11/02/2012:svnMEDION:pnMS-7800:pvr1.0:rvnMEDION:rnMS-7800:rvr1.0:cvnMEDION:ct3:cvr: dmi.product.name: MS-7800 dmi.product.version: 1.0 dmi.sys.vendor: MEDION version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1351424] Re: [icons] browser, settings and calculator icons too similar to another well known mobile O/S
** Changed in: ubuntu-calculator-app Status: Confirmed = Opinion ** Changed in: ubuntu-calculator-app Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1351424 Title: [icons] browser, settings and calculator icons too similar to another well known mobile O/S Status in Camera App: Opinion Status in Calculator application for Ubuntu devices: Opinion Status in Ubuntu UX bugs: Triaged Status in Web Browser App: Opinion Status in “ubuntu-themes” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: The browser and system settings icons in image #165 looks extremely similar in both content and colour to another well-known mobile operating system. IMHO they are also too busy Please can we change these to make them simpler and more uniquely Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1351424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359117] Re: lightdm and xorg fails to start after kernel update, voltage errors
same issue with Asus ux21a, 3.16.0-24-generic: dmesg | grep voltage [2.659756] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 936.220837] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 3230.334988] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 4568.440454] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1359117 Title: lightdm and xorg fails to start after kernel update, voltage errors Status in “xorg” package in Ubuntu: Confirmed Bug description: Hardware: ASUS UX32VD (zenbook prime) Software: Ubuntu 14.04 I see following errors on dmesg after kernel updated to 3.13.0-34: [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up Lightdm won't start, startx did not help also. Tried linux-image-3.16.1 from Utopic - same issue. Last working kernel where there is no such problem: 3.13.0-32-generic Upstream bug reports: https://bugs.freedesktop.org/show_bug.cgi?id=70117 https://bugzilla.kernel.org/show_bug.cgi?id=74931 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 20 12:57:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1507] Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507] MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=69b256f1-59c3-4193-a1e0-b7c0e333cfbd ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 20 11:19:17 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4931 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1359117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359117] Re: lightdm and xorg fails to start after kernel update, voltage errors
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1359117 Title: lightdm and xorg fails to start after kernel update, voltage errors Status in “xorg” package in Ubuntu: Confirmed Bug description: Hardware: ASUS UX32VD (zenbook prime) Software: Ubuntu 14.04 I see following errors on dmesg after kernel updated to 3.13.0-34: [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up Lightdm won't start, startx did not help also. Tried linux-image-3.16.1 from Utopic - same issue. Last working kernel where there is no such problem: 3.13.0-32-generic Upstream bug reports: https://bugs.freedesktop.org/show_bug.cgi?id=70117 https://bugzilla.kernel.org/show_bug.cgi?id=74931 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 20 12:57:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1507] Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507] MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=69b256f1-59c3-4193-a1e0-b7c0e333cfbd ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 20 11:19:17 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4931 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1359117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388582] Re: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks
** Also affects: alsa-driver via http://bugzilla.kernel.org/show_bug.cgi?id=88251 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1388582 Title: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have a fresh install of KUbuntu 14.10 with this problem and i come of a KUbuntu 13.10 without problems. I don't have any sound from speakers or headphone, i think the driver isn't loaded, but the microphone works, it records. The sound playback works too, but the sound doesn't go through speakers or headphones. I was testing with a lot of LiveCD KUbuntu when the problem comes. With LiveCDs KUbuntu 12.04.5 LTS, 12.10, 13.04 the sound works, they configs the sound system as HDA Intel AD198x. Since LiveCDs 13.10, 14.04.1 LTS and, of course, 14.10 Live CD and my install, i have this problem, because the sound system is now AD1986A. I will attach the alsa-info output for all this systems in my computer. But with HDA_Analyzer http://www.alsa- project.org/main/index.php/HDA_Analyzer i found the details of the problem: i can create a python script to brought back the sound working in a basic mode, like as previously. The details are activating EAPD in Card 0, Codec 0, Node 0x1b PIN (In my computer, it could be different in another) what brought back the sound to the speakers, and unmuting Output Amplifier in Card 0, Codec 0, Node 0x1a VAL[0] and VAL[1] to brought back sound to the headphones when they are plugged. I will attach too the output of this diff and the python script created by HDA_Analyzer for my system. At least, the basic working state should be back, because with a untoching fresh install there isn't any sound. There are related bugs here and other post in internet, but i collected all information i found and can give more if it's necessary. For additional information: Searching the solution, i tested too all the models availables for HDA Intel AD1986A (editing /etc/modprobe.d /alsa-base.conf with AD1986A models /usr/share/doc/alsa-base/driver /HD-Audio-Models.txt.gz) and i found the default one doesn't fit my system and anothers are better, but have problems of no sound too and i don't found how to fix these problem. When this bug is corrected, i want to help to found a better model for my computer, i don't know how now, but first it brought back the sound. Also, i test with snd-hda- tools https://launchpad.net/~diwic/+archive/ubuntu/hda and with hda- jack-sense-test the Green Line Out sense doesn't work (always NO present) but the Pink Mic sense works without problems. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thywalls 2380 F pulseaudio CurrentDesktop: KDE Date: Sun Nov 2 16:24:36 2014 InstallationDate: Installed on 2014-10-30 (3 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12JNC.206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX65 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12JNC.206:bd09/28/2006:svnPackardBellBV:pnEasyNote_MX65:pvrPB63E03104:rvnPackardBellBV:rnEasyNote_MX65:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX65 dmi.product.version: PB63E03104 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1388582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393085] Re: Performance degraded and video glitches with i915 after upgrade to utopic
** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1393085 Title: Performance degraded and video glitches with i915 after upgrade to utopic Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: After upgrading from trusty to utopic, I noticed a performance degradation in the video performance. In particular the flash plugin video (like youtube) starts OK but it degrades after a couple of seconds when in full screen, looking as if it was doing something like 10~15 fps with videos that worked fine before. When switching to windowed more again, the video goes more smoothly but the seek bar blinks and other parts of the video present some glitches. Also when switching from X to a console, via Ctrl-Alt-F1 for example, it takes like 2 seconds to get the console, and I see this message in the console: [ 184.436477] [drm:intel_enable_lvds] *ERROR* timed out waiting for panel to power on When switching back to X is fast as usual, but when switching back to the console, again 2 seconds delay and the message. Other weird looking messages are found in dmesg: [4.673834] [drm] GMBUS [i915 gmbus panel] timed out, falling back to bit banging on pin 3 [...] [4.732400] [drm] Wrong MCH_SSKPD value: 0x16040307 [4.732404] [drm] This can cause pipe underruns and display issues. [4.732406] [drm] Please upgrade your BIOS to fix this. Unfortunately there is no BIOS update for my notebook (Toshiba Z830). I've search for all those errors without any significant results. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None CurrentDesktop: Unity Date: Sat Nov 15 22:52:27 2014 DistUpgraded: 2014-11-08 12:14:07,528 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2012-04-26 (933 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: TOSHIBA SATELLITE Z830 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=36929bf3-a158-44d9-a80d-3adac2840fa8 ro quiet splash acpi_backlight=vendor pcie_aspm=force i915.enable_rc6=7 i915.enable_fbc=1 i915.lvds_downclock=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-11-08 (7 days ago) dmi.bios.date: 04/18/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.80 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.80:bd04/18/2013:svnTOSHIBA:pnSATELLITEZ830:pvrPT22LE-00300GGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: SATELLITE Z830 dmi.product.version: PT22LE-00300GGR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Nov 15 22:40:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1393085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1393151] Re: Writing to ext4 LVM FS causes GPF in mpage_process_page_bufs
Additional info: A GPF also occurs when creating the filesystem on the LV using mkfs.ext3, while creating the inode tables. Since mkfs.ext4 doesn't do this, it happens later when more data is being written to the lv. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1393151 Title: Writing to ext4 LVM FS causes GPF in mpage_process_page_bufs Status in “e2fsprogs” package in Ubuntu: New Bug description: Writing data to a 3 TB ext4-formatted logical volume on a 2x6 TB mdadm raid 1 mirror always results in a GPF within 1 minute of writing the data. Disks seem to be OK smart-wise. When the GPF occurs, the md1 raid volume gets degraded, the entire system gets irresponsive and after the next boot (hard reset), the raid syncing starts from scratch (which takes 10 hours with the two 6 TB drives). The GPF always happens in mpage_process_page_bufs: Nov 16 09:26:03 nas kernel: [ 230.610495] [ cut here ] Nov 16 09:26:03 nas kernel: [ 230.610510] WARNING: CPU: 1 PID: 1927 at /build/buildd/linux-3.13.0/kernel/exit.c:711 do_exit+0x55/0xa50() Nov 16 09:26:03 nas kernel: [ 230.610531] Modules linked in: ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_codec_hdmi arc4 bridge stp llc x86_pkg_temp_thermal intel_powerc$ Nov 16 09:26:03 nas kernel: [ 230.610810] CPU: 1 PID: 1927 Comm: vsftpd Tainted: G D 3.13.0-39-generic #66-Ubuntu Nov 16 09:26:03 nas kernel: [ 230.610830] Hardware name: Gigabyte Technology Co., Ltd. H97N-WIFI/H97N-WIFI, BIOS F4 06/28/2014 Nov 16 09:26:03 nas kernel: [ 230.610849] 0009 8800cb61d9e0 8171ece7 Nov 16 09:26:03 nas kernel: [ 230.610877] 8800cb61da18 8106773d 000b 8800cb61db38 Nov 16 09:26:03 nas kernel: [ 230.610898] 0246 8800cb633000 8800cb61da28 Nov 16 09:26:03 nas kernel: [ 230.610920] Call Trace: Nov 16 09:26:03 nas kernel: [ 230.610928] [8171ece7] dump_stack+0x45/0x56 Nov 16 09:26:03 nas kernel: [ 230.610941] [8106773d] warn_slowpath_common+0x7d/0xa0 Nov 16 09:26:03 nas kernel: [ 230.610956] [8106781a] warn_slowpath_null+0x1a/0x20 Nov 16 09:26:03 nas kernel: [ 230.610970] [81069a45] do_exit+0x55/0xa50 Nov 16 09:26:03 nas kernel: [ 230.610984] [817282b9] oops_end+0xa9/0x150 Nov 16 09:26:03 nas kernel: [ 230.610997] [810171cb] die+0x4b/0x70 Nov 16 09:26:03 nas kernel: [ 230.611008] [81727c4e] do_general_protection+0x11e/0x1b0 Nov 16 09:26:03 nas kernel: [ 230.611024] [81727568] general_protection+0x28/0x30 Nov 16 09:26:03 nas kernel: [ 230.611039] [8123e0b8] ? mpage_process_page_bufs+0x38/0x130 Nov 16 09:26:03 nas kernel: [ 230.611055] [8123f0e9] mpage_prepare_extent_to_map+0x219/0x2c0 Nov 16 09:26:03 nas kernel: [ 230.611071] [81242ef2] ext4_writepages+0x3f2/0xd20 Nov 16 09:26:03 nas kernel: [ 230.611086] [8115a9be] do_writepages+0x1e/0x40 Nov 16 09:26:03 nas kernel: [ 230.611101] [8114fac9] __filemap_fdatawrite_range+0x59/0x60 Nov 16 09:26:03 nas kernel: [ 230.67] [8114fb7c] filemap_flush+0x1c/0x20 Nov 16 09:26:03 nas kernel: [ 230.611130] [81240928] ext4_alloc_da_blocks+0x38/0x70 Nov 16 09:26:03 nas kernel: [ 230.611156] [81239e89] ext4_release_file+0x79/0xc0 Nov 16 09:26:03 nas kernel: [ 230.611171] [811bed84] __fput+0xe4/0x260 Nov 16 09:26:03 nas kernel: [ 230.611184] [811bef4e] fput+0xe/0x10 Nov 16 09:26:03 nas kernel: [ 230.611197] [81088227] task_work_run+0xa7/0xe0 Nov 16 09:26:03 nas kernel: [ 230.611210] [81013df7] do_notify_resume+0x97/0xb0 Nov 16 09:26:03 nas kernel: [ 230.611225] [8172faaa] int_signal+0x12/0x17 Nov 16 09:26:03 nas kernel: [ 230.612259] ---[ end trace c2c7ff1f119c2b75 ]--- apt-cache policy e2fslibs:amd64 e2fslibs: Installed: 1.42.9-3ubuntu1 Candidate: 1.42.9-3ubuntu1 Version table: *** 1.42.9-3ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART
[Touch-packages] [Bug 1390994] Re: Lost ability to print duplex
The file is /etc/cups/cupsd.conf (d at the end) can you attach it's content together with a complete cups error log after trying to print duplex with debugging enabled as described here: https://wiki.ubuntu.com/DebuggingPrintingProblems. Can your follow the instructions of the sections CUPS error_log, Capturing print job data, and Getting the data which would go to the printer. Can you also attach the file(s) which you tried to print? Please do this for all situations with problems (LibreOffice, evince, ...). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1390994 Title: Lost ability to print duplex Status in “cups” package in Ubuntu: Incomplete Bug description: A recent update (about a week or two ago) has resulted in my HP 8600 printer no longer printing double-sided. All the configuration information appears to be unchanged, but pages are not printed double- sided, when requested. The duplexer works properly in local mode. My configuration is: Ubuntu 14.04 (up-to-date), HP Pavilion dv6 with AMD quad-core processor. I have been running Ubuntu on this machine for about 27 months. I successfully upgraded from 12.04 to 14.04 last summer. The 8600 printer has been in use for about two years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1390994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393151] Re: Writing to ext4 LVM FS causes GPF in mpage_process_page_bufs
More detailed SMART info: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051Pre-fail Always - 0 3 Spin_Up_Time0x0027 241 201 021Pre-fail Always - 6941 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 39 5 Reallocated_Sector_Ct 0x0033 200 200 140Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000Old_age Always - 58 10 Spin_Retry_Count0x0032 100 253 000Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 39 192 Power-Off_Retract_Count 0x0032 200 200 000Old_age Always - 31 193 Load_Cycle_Count0x0032 200 200 000Old_age Always - 24 194 Temperature_Celsius 0x0022 119 103 000Old_age Always - 33 196 Reallocated_Event_Count 0x0032 200 200 000Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x0032 200 200 000Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged --- ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 253 051Pre-fail Always - 0 3 Spin_Up_Time0x0027 243 200 021Pre-fail Always - 6816 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 39 5 Reallocated_Sector_Ct 0x0033 200 200 140Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000Old_age Always - 58 10 Spin_Retry_Count0x0032 100 253 000Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 39 192 Power-Off_Retract_Count 0x0032 200 200 000Old_age Always - 31 193 Load_Cycle_Count0x0032 200 200 000Old_age Always - 25 194 Temperature_Celsius 0x0022 120 105 000Old_age Always - 32 196 Reallocated_Event_Count 0x0032 200 200 000Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x0032 200 200 000Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged ** Description changed: - Writing lots of data to a 3 TB ext4-formatted logical volume on a 2x6 TB - mdadm raid 1 mirror always results in a GPF within 1 minute of writing - the data. Disks seem to be OK smart-wise. + Writing data to a 3 TB ext4-formatted logical volume on a 2x6 TB mdadm + raid 1 mirror always results in a GPF within 1 minute of writing the + data. Disks seem to be OK smart-wise. When the GPF occurs, the md1 raid volume gets degraded, the entire system gets irresponsive and after the next boot (hard reset), the raid syncing starts from scratch (which takes 10 hours with the two 6 TB - drives to complete). The GPF occurs when the raid is still syncing and - also after it is in sync. + drives). The GPF always happens in mpage_process_page_bufs: Nov 16 09:26:03 nas kernel: [ 230.610495] [ cut here ] Nov 16 09:26:03 nas kernel: [ 230.610510] WARNING: CPU: 1 PID: 1927 at /build/buildd/linux-3.13.0/kernel/exit.c:711 do_exit+0x55/0xa50() Nov 16 09:26:03 nas kernel: [ 230.610531] Modules linked in: ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_codec_hdmi arc4 bridge stp llc x86_pkg_temp_thermal intel_powerc$ Nov 16 09:26:03 nas kernel: [ 230.610810] CPU: 1 PID: 1927 Comm: vsftpd Tainted: G D 3.13.0-39-generic #66-Ubuntu Nov 16 09:26:03 nas kernel: [ 230.610830] Hardware name: Gigabyte Technology Co., Ltd. H97N-WIFI/H97N-WIFI, BIOS F4 06/28/2014 Nov 16 09:26:03 nas kernel: [ 230.610849] 0009 8800cb61d9e0
[Touch-packages] [Bug 1393152] Re: establish connection even if wireless hardware is removed
** Description changed: - Hallo - - TESTCASE: - - Start from a fully working wireless connection. - *Shutdown - *Phisically remove the wireless card and connect with ethernet - *Reboot - *Sometime you will see the NM trying to connect to wireless net and sometime stating that is connected - - Is expected that it don't try to connect to a not existing net (no way - to receive) - - Best regards - - ProblemType: Bug - DistroRelease: Ubuntu 15.04 - Package: network-manager 0.9.8.8-0ubuntu34 - ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 - Uname: Linux 3.16.0-24-generic x86_64 - ApportVersion: 2.14.7-0ubuntu10 - Architecture: amd64 - CurrentDesktop: Unity - Date: Sun Nov 16 10:07:46 2014 - EcryptfsInUse: Yes - IpRoute: - default via 192.168.0.1 dev eth0 proto static - 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.12 metric 1 - 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 9 - RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no - SourcePackage: network-manager - UpgradeStatus: No upgrade log present (probably fresh install) - mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-08-21T11:25:28.586075 - nmcli-con: - NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH - retenjin 2fce5e43-bae6-4b88-8f7d-96bdfe5a2e4d 802-11-wireless 1416128840 dom 16 nov 2014 10:07:20 CET yes no /org/freedesktop/NetworkManager/Settings/2 - Auto Ethernet f8e95dc1-09fc-4b20-95c1-c3deb1ec1502 802-3-ethernet1416128759 dom 16 nov 2014 10:05:59 CET yes no /org/freedesktop/NetworkManager/Settings/1 - retenjin_EXT 0aa3e412-316b-489a-b9cf-1749f3ff668b 802-11-wireless 1410629422 sab 13 set 2014 19:30:22 CEST yes no /org/freedesktop/NetworkManager/Settings/0 - nmcli-dev: - DEVICE TYPE STATE DBUS-PATH - wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 - eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 - nmcli-nm: - RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN - running 0.9.8.8connected enabled enabled enabledenabled disabled + . ** Attachment removed: modified.conffile..etc.NetworkManager.NetworkManager.conf.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261700/+files/modified.conffile..etc.NetworkManager.NetworkManager.conf.txt ** Attachment removed: WifiSyslog.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261699/+files/WifiSyslog.txt ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261698/+files/ProcEnviron.txt ** Attachment removed: PciNetwork.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261697/+files/PciNetwork.txt ** Attachment removed: NetworkManager.conf.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261695/+files/NetworkManager.conf.txt ** Attachment removed: CRDA.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261687/+files/CRDA.txt ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261688/+files/Dependencies.txt ** Attachment removed: IfupdownConfig.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261689/+files/IfupdownConfig.txt ** Attachment removed: IpAddr.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261690/+files/IpAddr.txt ** Attachment removed: IwConfig.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261691/+files/IwConfig.txt ** Attachment removed: NetDevice.eth0.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261692/+files/NetDevice.eth0.txt ** Attachment removed: NetDevice.lo.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261693/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1393152 Title: invalid Status in “network-manager” package in Ubuntu: Invalid Bug description: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+subscriptions --
[Touch-packages] [Bug 1393164] [NEW] package libopenal1:amd64 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: Non known ... unsure what openal-soft is? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libopenal1:amd64 1:1.14-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Sun Nov 16 11:30:49 2014 DuplicateSignature: package:libopenal1:amd64:1:1.14-4ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-03-11 (250 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) SourcePackage: openal-soft Title: package libopenal1:amd64 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-12 (95 days ago) ** Affects: openal-soft (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openal-soft in Ubuntu. https://bugs.launchpad.net/bugs/1393164 Title: package libopenal1:amd64 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in “openal-soft” package in Ubuntu: New Bug description: Non known ... unsure what openal-soft is? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libopenal1:amd64 1:1.14-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Sun Nov 16 11:30:49 2014 DuplicateSignature: package:libopenal1:amd64:1:1.14-4ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-03-11 (250 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) SourcePackage: openal-soft Title: package libopenal1:amd64 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-12 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1393164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393152] Re: establish connection even if wireless hardware is removed
** Attachment removed: NetworkManager.state.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261696/+files/NetworkManager.state.txt ** Attachment removed: NetDevice.wlan0.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+attachment/4261694/+files/NetDevice.wlan0.txt ** Tags removed: amd64 apport-bug vivid ** Summary changed: - establish connection even if wireless hardware is removed + . ** Summary changed: - . + invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1393152 Title: invalid Status in “network-manager” package in Ubuntu: Invalid Bug description: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393164] Re: package libopenal1:amd64 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openal-soft in Ubuntu. https://bugs.launchpad.net/bugs/1393164 Title: package libopenal1:amd64 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in “openal-soft” package in Ubuntu: New Bug description: Non known ... unsure what openal-soft is? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libopenal1:amd64 1:1.14-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Sun Nov 16 11:30:49 2014 DuplicateSignature: package:libopenal1:amd64:1:1.14-4ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-03-11 (250 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) SourcePackage: openal-soft Title: package libopenal1:amd64 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-12 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1393164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375742] Re: ibus-daemon uses 100% CPU after a modifier key is pressed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1375742 Title: ibus-daemon uses 100% CPU after a modifier key is pressed Status in “ibus” package in Ubuntu: Confirmed Bug description: 1. Open a gtk app like gnome-calculator or gedit 2. Press a modifier key (shift, ctrl...) 3. Watch ibus-daemon and ibus-x11 use 100% cpu 4. Can be stopped by right clicking, or switching windows ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 21:26:06 2014 InstallationDate: Installed on 2014-09-03 (27 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1375742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393169] [NEW] Double mouse cursor
Public bug reported: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: screen copy of the mouse cursor https://bugs.launchpad.net/bugs/1393169/+attachment/4261774/+files/Cursor.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1393169 Title: Double mouse cursor Status in “xorg” package in Ubuntu: New Bug description: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393172] [NEW] [VGN-G2ABPS, Realtek ALC262, Black Headphone Out, Front] No sound at all
*** This bug is a security vulnerability *** Public security bug reported: my front side speaker some time does not work when i connect with headphone then work properly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monir 1767 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 16 17:41:42 2014 InstallationDate: Installed on 2014-08-28 (79 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monir 1767 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [VGN-G2ABPS, Realtek ALC262, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0031N9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0031N9:bd02/07/2008:svnSonyCorporation:pnVGN-G2ABPS:pvrJ003MUHA:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-G2ABPS dmi.product.version: J003MUHA dmi.sys.vendor: Sony Corporation ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1393172 Title: [VGN-G2ABPS, Realtek ALC262, Black Headphone Out, Front] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: my front side speaker some time does not work when i connect with headphone then work properly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monir 1767 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 16 17:41:42 2014 InstallationDate: Installed on 2014-08-28 (79 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: monir 1767 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [VGN-G2ABPS, Realtek ALC262, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0031N9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0031N9:bd02/07/2008:svnSonyCorporation:pnVGN-G2ABPS:pvrJ003MUHA:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-G2ABPS dmi.product.version: J003MUHA dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1393172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU
fast'n'dirty patch sudo sed -i's/Exec=chromium-browser/Exec=env LIBGL_DRI3_DISABLE=1 chromium-browser/g' /usr/share/applications/chromium-browser.desktop It is possible you have to apply the patch to ~/.local/share/applications/chromium-browser.desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377220 Title: Google Chrome crash with mesa 10.3 on Intel GPU Status in “mesa” package in Ubuntu: Confirmed Bug description: When I start google-chrome on my Ubuntu 14.10 system the process it uses to test for a working GPU crashes and then Chrome falls back to software rendering. In chrome://gpu/ I get: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Threaded Rasterization: Unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_ext_occlusion_query disable_post_sub_buffers_for_onscreen_surfaces scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all [...] In Ubuntu 14.04 (and also previous versions), on the same laptop, the exact same Google Chrome used to work perfectly with GPU acceleration. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgl1-mesa-dri 10.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting sensors limits [240G [234G[ OK ] * Setting up X socket directories... [240G [234G[ OK ] CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri Oct 3 17:48:09 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 2 13:54:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1377220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 417778] Re: xfce4-volumed takes 100% cpu when system is idle for some time
Launchpad has imported 8 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=5183. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-04-03T02:03:31+00:00 Hesperaux wrote: If I add a mixer plugin to my panel, it works fine. The volume is controlled properly and the CPU does not max out. Some time later, I repeatedly notice it has begun using 100% of both my cores. I have an onboard sound chipset that dmixes properly with alsa. I do not use a sound daemon of any kind. I also have a (mostly-unsupported by Linux) Creative X-Fi sound card which is plugged in but unused. The plugin detects the following sound cards: NVidia CK804 (Alsa mixer) - this is the onboard chipset that I use all the time. Monitor Integrated Webcam (Alsa mixer) - one of my DFP microphones pcsp (Alsa mixer) - I have no idea what this is. Monitor Integrated Webcam (Alsa mixer) - one of my DFP microphones (dual monitors) Realtek ALC850 rev 0 (OSS Mixer) - I'm assuming this could be my X-Fi, but it really looks like something else. In any case, I've not seen it before. That's the list exactly as I'm given it. I haven't been able to find out what causes the mixer to go crazy. My sound card is not disconnecting as in bug 4962, but I think it may be a related problem, so I would suggest taking both bugs into account. Thanks for all of your hard work. All of us appreciate XFCE. Other information: Linux atlas 2.6.28-ARCH #1 SMP PREEMPT Tue Mar 17 06:42:43 UTC 2009 i686 Dual Core AMD Opteron(tm) Processor 165 AuthenticAMD GNU/Linux Motherboard containing audio chipset: Asus A8n-SLI-Premium Exact version of plugin and panel: xfce4-mixer 4.6.0-2 xfce4-panel-4.6.0-1 Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/417778/comments/0 On 2009-04-05T20:09:06+00:00 Hesperaux wrote: Hello again. I wanted to update this bug, because I now know that it is directly related to bug 4962. The plugin works properly without issue until I turn off my monitors (something I do when I go away from my PC). When I come back, and turn them on, I notice the CPU is at maximum usage. This is because the USB microphone/hub/webcam imbedded in the monitors is one of the available devices to control using the mixer plugin. As soon as they are detached, it is the same issue as in bug 4962 - the CPU load goes up immensely, as though the plugin is trying to check or configure the microphones that were powered off. And obviously when they are powered back on, it still freaks out. Hope this helps. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/417778/comments/1 On 2009-08-21T06:26:48+00:00 Xfce-e wrote: I have the same problem on xubuntu jaunty. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/417778/comments/2 On 2010-01-09T13:03:47+00:00 Charlie Kravetz wrote: This bug has been reported on Ubuntu Launchpad as: https://bugs.launchpad.net/bugs/417778 It is possible the root causes of both this bug and bug 4962 are the same. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/417778/comments/30 On 2010-01-09T16:04:58+00:00 cmeerw wrote: I think this is caused by https://bugzilla.gnome.org/show_bug.cgi?id=507527 Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/417778/comments/33 On 2010-10-03T10:40:27+00:00 Fork0 wrote: (In reply to comment #4) I think this is caused by https://bugzilla.gnome.org/show_bug.cgi?id=507527 You're right (well, not caused by, but is related to). There are changes on the bug, and a workaround (attached to the discussion). Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/417778/comments/42 On 2014-11-16T07:34:09+00:00 Robby Workman wrote: Looks like this was a gstreamer bug that was fixed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=614545 Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/417778/comments/44 On 2014-11-16T08:25:19+00:00 Robby Workman wrote: *** Bug 5460 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/417778/comments/45 ** Changed in: xfce4-mixer Status: Unknown = Fix Released ** Changed in:
[Touch-packages] [Bug 1393079] [NEW] Touchpad not working after suspend/resume
You have been subscribed to a public bug: Ubuntu 14.10 on an Acer Laptop, model: Aspire E5-571G-941Y $ uname -a Linux Acer-Aspire-E5-571G 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Every time I suspend, the trackpad no longer works when resuming. I see several other people have the same issue with the same laptop here: http://ubuntuforums.org/showthread.php?t=2250002 (some people say it's a 14.10 specific problem) I realize this report is very poor but please don't hesitate to request data / clarifications from me, I'll be happy to help. ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Touchpad not working after suspend/resume https://bugs.launchpad.net/bugs/1393079 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393079] Re: Touchpad not working after suspend/resume
Following https://wiki.ubuntu.com/Bugs/FindRightPackage I think this problems probably lies in pm-utils or the Kernel, but to be honest, I have no idea. ** Package changed: ubuntu = pm-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1393079 Title: Touchpad not working after suspend/resume Status in “pm-utils” package in Ubuntu: New Bug description: Ubuntu 14.10 on an Acer Laptop, model: Aspire E5-571G-941Y $ uname -a Linux Acer-Aspire-E5-571G 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Every time I suspend, the trackpad no longer works when resuming. I see several other people have the same issue with the same laptop here: http://ubuntuforums.org/showthread.php?t=2250002 (some people say it's a 14.10 specific problem) I realize this report is very poor but please don't hesitate to request data / clarifications from me, I'll be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1393079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] Re: Xorg freeze
Josef Schlehofer, please do not apport-collect to a report you are not the original reporter of. If you want your problem addressed, and so your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal: ubuntu-bug xorg Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. For more on this, please see the official Ubuntu documentation: Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. As well, please do not announce in this report you created a new bug report. Thank you for your understanding. ** Tags removed: apport-collected compiz-0.9 third-party-packages utopic ** Attachment removed: Xrandr.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261682/+files/Xrandr.txt ** Attachment removed: XorgLogOld.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261681/+files/XorgLogOld.txt ** Attachment removed: XorgLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261680/+files/XorgLog.txt ** Attachment removed: UnitySupportTest.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261679/+files/UnitySupportTest.txt ** Attachment removed: UdevLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261678/+files/UdevLog.txt ** Attachment removed: UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261677/+files/UdevDb.txt ** Attachment removed: ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261676/+files/ProcModules.txt ** Attachment removed: ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261675/+files/ProcInterrupts.txt ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261674/+files/ProcEnviron.txt ** Attachment removed: ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261673/+files/ProcCpuinfo.txt ** Attachment removed: PccardctlStatus.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261672/+files/PccardctlStatus.txt ** Attachment removed: PccardctlIdent.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261671/+files/PccardctlIdent.txt ** Attachment removed: Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261670/+files/Lsusb.txt ** Attachment removed: Lspci.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261669/+files/Lspci.txt ** Attachment removed: LightdmLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261668/+files/LightdmLog.txt ** Attachment removed: LightdmGreeterLogOld.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261667/+files/LightdmGreeterLogOld.txt ** Attachment removed: LightdmGreeterLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261666/+files/LightdmGreeterLog.txt ** Attachment removed: LightdmDisplayLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261665/+files/LightdmDisplayLog.txt ** Attachment removed: GconfCompiz.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261664/+files/GconfCompiz.txt ** Attachment removed: DpkgLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261663/+files/DpkgLog.txt ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261662/+files/Dependencies.txt ** Attachment removed: CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261661/+files/CurrentDmesg.txt ** Attachment removed: BootLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261660/+files/BootLog.txt ** Attachment removed: xserver.devices.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261684/+files/xserver.devices.txt ** Attachment removed: xdpyinfo.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261683/+files/xdpyinfo.txt ** Attachment removed: BootDmesg.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+attachment/4261659/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg”
[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
I have been googling and experimenting a bit. Basically I'd like to
change:
. $CONFIG_FILE 2$ERR
to something along these lines:
. $CONFIG_FILE 2 (tee $ERR 2)
There is just one tiny problem: It's bash syntax and doesn't work in sh.
If I change the shebang line of /usr/sbin/lightdm-session to
#!/bin/bash it works like a charm. Actually, it works much better,
since it recursively prevents syntax errors in sourced files from
causing fatal errors. OTOH, I suppose that switching to bash wouldn't be
approved just like that. ;)
I got the tip from the first answer at this page:
http://stackoverflow.com/questions/692000/how-do-i-write-stderr-to-a
-file-while-using-tee-with-a-pipe
The answer also includes the equivalent code for sh. I have successfully
applied that approach in stand-alone test scripts, but when moved to
/usr/sbin/lightdm-session, all my attempts so far have caused buggy
behavior.
You might think that something like this should work:
. $CONFIG_FILE 21 /dev/null | tee $ERR 2
It doesn't. As soon as you add a pipe like that, setting environment
variables via the sourced files fails.
So I'm stuck. Any help from a shell scripting wizard would be much
appreciated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393151] Re: Writing to ext4 LVM FS causes GPF in mpage_process_page_bufs
** Description changed: - Writing data to a 3 TB ext4-formatted logical volume on a 2x6 TB mdadm - raid 1 mirror always results in a GPF within 1 minute of writing the - data. Disks seem to be OK smart-wise. + mkfs.ext3 always causes a kernel panic on both of my WD 6 TB drives + while writing the inode tables. Both drives were initialised using + parted with a GPT and a single partition (mkpart primary 2048s 100%) - When the GPF occurs, the md1 raid volume gets degraded, the entire - system gets irresponsive and after the next boot (hard reset), the raid - syncing starts from scratch (which takes 10 hours with the two 6 TB - drives). + sdc 8:32 0 5.5T 0 disk + └─sdc1 8:33 0 5.5T 0 part + sdd 8:48 0 5.5T 0 disk + └─sdd1 8:49 0 5.5T 0 part - The GPF always happens in mpage_process_page_bufs: + mkfs.ext3 /dev/sdc1 + mke2fs 1.42.10 (18-May-2014) + Creating filesystem with 1465130240 4k blocks and 18318 inodes + Filesystem UUID: 1a6458a3-908d-48a0-a532-e9cbc1eb5ca4 + Superblock backups stored on blocks: + 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, + 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, + 10240, 214990848, 51200, 550731776, 644972544 - Nov 16 09:26:03 nas kernel: [ 230.610495] [ cut here ] - Nov 16 09:26:03 nas kernel: [ 230.610510] WARNING: CPU: 1 PID: 1927 at /build/buildd/linux-3.13.0/kernel/exit.c:711 do_exit+0x55/0xa50() - Nov 16 09:26:03 nas kernel: [ 230.610531] Modules linked in: ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables snd_hda_codec_hdmi arc4 bridge stp llc x86_pkg_temp_thermal intel_powerc$ - Nov 16 09:26:03 nas kernel: [ 230.610810] CPU: 1 PID: 1927 Comm: vsftpd Tainted: G D 3.13.0-39-generic #66-Ubuntu - Nov 16 09:26:03 nas kernel: [ 230.610830] Hardware name: Gigabyte Technology Co., Ltd. H97N-WIFI/H97N-WIFI, BIOS F4 06/28/2014 - Nov 16 09:26:03 nas kernel: [ 230.610849] 0009 8800cb61d9e0 8171ece7 - Nov 16 09:26:03 nas kernel: [ 230.610877] 8800cb61da18 8106773d 000b 8800cb61db38 - Nov 16 09:26:03 nas kernel: [ 230.610898] 0246 8800cb633000 8800cb61da28 - Nov 16 09:26:03 nas kernel: [ 230.610920] Call Trace: - Nov 16 09:26:03 nas kernel: [ 230.610928] [8171ece7] dump_stack+0x45/0x56 - Nov 16 09:26:03 nas kernel: [ 230.610941] [8106773d] warn_slowpath_common+0x7d/0xa0 - Nov 16 09:26:03 nas kernel: [ 230.610956] [8106781a] warn_slowpath_null+0x1a/0x20 - Nov 16 09:26:03 nas kernel: [ 230.610970] [81069a45] do_exit+0x55/0xa50 - Nov 16 09:26:03 nas kernel: [ 230.610984] [817282b9] oops_end+0xa9/0x150 - Nov 16 09:26:03 nas kernel: [ 230.610997] [810171cb] die+0x4b/0x70 - Nov 16 09:26:03 nas kernel: [ 230.611008] [81727c4e] do_general_protection+0x11e/0x1b0 - Nov 16 09:26:03 nas kernel: [ 230.611024] [81727568] general_protection+0x28/0x30 - Nov 16 09:26:03 nas kernel: [ 230.611039] [8123e0b8] ? mpage_process_page_bufs+0x38/0x130 - Nov 16 09:26:03 nas kernel: [ 230.611055] [8123f0e9] mpage_prepare_extent_to_map+0x219/0x2c0 - Nov 16 09:26:03 nas kernel: [ 230.611071] [81242ef2] ext4_writepages+0x3f2/0xd20 - Nov 16 09:26:03 nas kernel: [ 230.611086] [8115a9be] do_writepages+0x1e/0x40 - Nov 16 09:26:03 nas kernel: [ 230.611101] [8114fac9] __filemap_fdatawrite_range+0x59/0x60 - Nov 16 09:26:03 nas kernel: [ 230.67] [8114fb7c] filemap_flush+0x1c/0x20 - Nov 16 09:26:03 nas kernel: [ 230.611130] [81240928] ext4_alloc_da_blocks+0x38/0x70 - Nov 16 09:26:03 nas kernel: [ 230.611156] [81239e89] ext4_release_file+0x79/0xc0 - Nov 16 09:26:03 nas kernel: [ 230.611171] [811bed84] __fput+0xe4/0x260 - Nov 16 09:26:03 nas kernel: [ 230.611184] [811bef4e] fput+0xe/0x10 - Nov 16 09:26:03 nas kernel: [ 230.611197] [81088227] task_work_run+0xa7/0xe0 - Nov 16 09:26:03 nas kernel: [ 230.611210] [81013df7] do_notify_resume+0x97/0xb0 - Nov 16 09:26:03 nas kernel: [ 230.611225] [8172faaa] int_signal+0x12/0x17 - Nov 16 09:26:03 nas kernel: [ 230.612259] ---[ end trace c2c7ff1f119c2b75 ]--- + Allocating group tables: done + Writing inode tables: 4937/44713 - + + mkfs.ext3 /dev/sdd1 + mke2fs 1.42.10 (18-May-2014) + Creating filesystem with 1465130240 4k blocks and 18318 inodes + Filesystem UUID: 3d6537ee-78f6-4a68-a833-e5dda4b69028 + Superblock backups stored on blocks: + 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, + 4096000, 7962624, 11239424,
[Touch-packages] [Bug 1371401] Re: randomly freezing
I can confirm this bug. I have the same problem with Jospeh. I have Victor g541 (clevo w651sj) - Nvidia GTX 850M. I have Kubuntu 14.10 installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1371401 Title: randomly freezing Status in “xorg” package in Ubuntu: Confirmed Bug description: Seems to be related to https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1220426 ASUS N550JK Touchscreen nVidia 343 graphics on Geforce GTX 850M Latest Linux kernel 3.16, Ubuntu 14.04 with xfce Screen can be unfrozen by doing ctrl+alt+f6 and then back with ctrl+alt+f6. Sometimes the touch screen and keyboard will continue to work but the touchpad will not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.16.0-031600-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 343.13 Thu Jul 31 19:06:44 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 18 23:12:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed bbswitch, 0.7, 3.16.0-031600-generic, x86_64: installed nvidia-343, 343.13, 3.16.0-031600-generic, x86_64: installed psmouse, elantech-x551c, 3.13.0-35-generic, x86_64: installed psmouse, elantech-x551c, 3.16.0-031600-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2014-09-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-031600-generic root=UUID=31b12bbb-0095-44fd-b6e6-6964171a74b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 18 22:30:52 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1371401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371401] Re: randomly freezing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1371401 Title: randomly freezing Status in “xorg” package in Ubuntu: Confirmed Bug description: Seems to be related to https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1220426 ASUS N550JK Touchscreen nVidia 343 graphics on Geforce GTX 850M Latest Linux kernel 3.16, Ubuntu 14.04 with xfce Screen can be unfrozen by doing ctrl+alt+f6 and then back with ctrl+alt+f6. Sometimes the touch screen and keyboard will continue to work but the touchpad will not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.16.0-031600-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 343.13 Thu Jul 31 19:06:44 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 18 23:12:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed bbswitch, 0.7, 3.16.0-031600-generic, x86_64: installed nvidia-343, 343.13, 3.16.0-031600-generic, x86_64: installed psmouse, elantech-x551c, 3.13.0-35-generic, x86_64: installed psmouse, elantech-x551c, 3.16.0-031600-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2014-09-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-031600-generic root=UUID=31b12bbb-0095-44fd-b6e6-6964171a74b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 18 22:30:52 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1371401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393151] Re: mkfs.ext3 causes kernel panic on new WD 6 TB drive
Screenshot of GPF / KP ** Attachment added: Screenshot of GPF / KP https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1393151/+attachment/4261854/+files/kp.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1393151 Title: mkfs.ext3 causes kernel panic on new WD 6 TB drive Status in “e2fsprogs” package in Ubuntu: New Bug description: mkfs.ext3 always causes a kernel panic on both of my WD 6 TB drives while writing the inode tables. Both drives were initialised using parted with a GPT and a single partition (mkpart primary 2048s 100%) sdc 8:32 0 5.5T 0 disk └─sdc1 8:33 0 5.5T 0 part sdd 8:48 0 5.5T 0 disk └─sdd1 8:49 0 5.5T 0 part mkfs.ext3 /dev/sdc1 mke2fs 1.42.10 (18-May-2014) Creating filesystem with 1465130240 4k blocks and 18318 inodes Filesystem UUID: 1a6458a3-908d-48a0-a532-e9cbc1eb5ca4 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848, 51200, 550731776, 644972544 Allocating group tables: done Writing inode tables: 4937/44713 -- KP occurs here -- mkfs.ext3 /dev/sdd1 mke2fs 1.42.10 (18-May-2014) Creating filesystem with 1465130240 4k blocks and 18318 inodes Filesystem UUID: 3d6537ee-78f6-4a68-a833-e5dda4b69028 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848, 51200, 550731776, 644972544 Allocating group tables: done Writing inode tables: 4997/44713 -- KP occurs here -- I'll have to try to take a photo of the KP since it's not being logged, I'm just seeing it on the screen. Creating an ext4 partition works fine but the crash just happens later after writing files to the partition. Disks seems to be fine smart- wise. It's unlikely that both disks are damaged in almost the same area without S.M.A.R.T. noticing it. -- apt-cache policy e2fslibs:amd64 e2fslibs: Installed: 1.42.9-3ubuntu1 Candidate: 1.42.9-3ubuntu1 Version table: *** 1.42.9-3ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status -- smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED smartctl -H /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED -- lshw -short H/W path Device Class Description system H97N-WIFI (To be filled by O.E.M.) /0busH97N-WIFI /0/0 memory 64KiB BIOS /0/3d processor Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz /0/3d/3e memory 128KiB L1 cache /0/3d/3f memory 512KiB L2 cache /0/3d/40 memory 3MiB L3 cache /0/42 memory 8GiB System Memory /0/42/0 memory 4GiB DIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/42/1 memory DIMM [empty] /0/42/2 memory 4GiB DIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/42/3 memory DIMM [empty] /0/100bridge 4th Gen Core Processor DRAM Controller /0/100/2 display4th Generation Core Processor Family Integrated Graphics Controller /0/100/3 multimedia Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller /0/100/14 bus9 Series Chipset Family USB xHCI Controller /0/100/16 communication 9 Series Chipset Family ME Interface #1 /0/100/19 eth1 networkEthernet
[Touch-packages] [Bug 1393079] Re: Touchpad not working after suspend/resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pm-utils (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1393079 Title: Touchpad not working after suspend/resume Status in “pm-utils” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 on an Acer Laptop, model: Aspire E5-571G-941Y $ uname -a Linux Acer-Aspire-E5-571G 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Every time I suspend, the trackpad no longer works when resuming. I see several other people have the same issue with the same laptop here: http://ubuntuforums.org/showthread.php?t=2250002 (some people say it's a 14.10 specific problem) I realize this report is very poor but please don't hesitate to request data / clarifications from me, I'll be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1393079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] Re: Xorg freeze
I know, but when I saw many duplicates bugs and noone was solved, so I though it will be better if I will continue at primary bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393213] [NEW] package bluez 4.101-0ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Launcher and tool bar at top of window do not appear. Three icons for closing iconifying and maximizing windows do not appear ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bluez 4.101-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sun Nov 16 00:03:18 2014 DuplicateSignature: package:bluez:4.101-0ubuntu20:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-24 (52 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 2764CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=d7a2b8cd-4023-418c-bdca-d1f6bcb680a7 ro recovery nomodeset SourcePackage: bluez Title: package bluez 4.101-0ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET91WW (3.21 ) dmi.board.name: 2764CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET91WW(3.21):bd12/06/2010:svnLENOVO:pn2764CTO:pvrThinkPadT400:rvnLENOVO:rn2764CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2764CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:23:4D:F5:84:7F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:1050 acl:0 sco:0 events:52 errors:0 TX bytes:1423 acl:0 sco:0 commands:52 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1393213 Title: package bluez 4.101-0ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “bluez” package in Ubuntu: New Bug description: Launcher and tool bar at top of window do not appear. Three icons for closing iconifying and maximizing windows do not appear ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bluez 4.101-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sun Nov 16 00:03:18 2014 DuplicateSignature: package:bluez:4.101-0ubuntu20:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-24 (52 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 2764CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=d7a2b8cd-4023-418c-bdca-d1f6bcb680a7 ro recovery nomodeset SourcePackage: bluez Title: package bluez 4.101-0ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET91WW (3.21 ) dmi.board.name: 2764CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET91WW(3.21):bd12/06/2010:svnLENOVO:pn2764CTO:pvrThinkPadT400:rvnLENOVO:rn2764CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2764CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:23:4D:F5:84:7F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:1050 acl:0 sco:0 events:52 errors:0 TX bytes:1423 acl:0 sco:0 commands:52 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1393213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1393213] Re: package bluez 4.101-0ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1393213 Title: package bluez 4.101-0ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “bluez” package in Ubuntu: New Bug description: Launcher and tool bar at top of window do not appear. Three icons for closing iconifying and maximizing windows do not appear ProblemType: Package DistroRelease: Ubuntu 14.10 Package: bluez 4.101-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sun Nov 16 00:03:18 2014 DuplicateSignature: package:bluez:4.101-0ubuntu20:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-24 (52 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 2764CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=d7a2b8cd-4023-418c-bdca-d1f6bcb680a7 ro recovery nomodeset SourcePackage: bluez Title: package bluez 4.101-0ubuntu20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET91WW (3.21 ) dmi.board.name: 2764CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET91WW(3.21):bd12/06/2010:svnLENOVO:pn2764CTO:pvrThinkPadT400:rvnLENOVO:rn2764CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2764CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:23:4D:F5:84:7F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:1050 acl:0 sco:0 events:52 errors:0 TX bytes:1423 acl:0 sco:0 commands:52 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1393213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1063570] Re: colord-sane crashed with SIGSEGV in opendir()
*** This bug is a duplicate of bug 1026520 *** https://bugs.launchpad.net/bugs/1026520 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: colord (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1063570 Title: colord-sane crashed with SIGSEGV in opendir() Status in “colord” package in Ubuntu: Confirmed Bug description: no idea, it just crashed after login to lightdm ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Fri Oct 5 10:36:18 2012 ExecutablePath: /usr/lib/i386-linux-gnu/colord/colord-sane InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcCmdline: /usr/lib/i386-linux-gnu/colord/colord-sane ProcEnviron: SegvAnalysis: Segfault happened at: 0xb72ff3bf:cmpb $0x0,(%edx) PC (0xb72ff3bf) ok source $0x0 ok destination (%edx) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 opendir () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0 libusb_get_device_list () from /lib/i386-linux-gnu/libusb-1.0.so.0 ?? () from /usr/lib/libhpmud.so.0 Title: colord-sane crashed with SIGSEGV in opendir() UpgradeStatus: Upgraded to quantal on 2012-10-03 (4 days ago) UserGroups: scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1063570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385095] Re: apport-kde crashed reporting a bug
apport-bug network-manager (produces the same crash) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1385095 Title: apport-kde crashed reporting a bug Status in “apport” package in Ubuntu: Confirmed Bug description: As requested I ran the ubntu-bug command; here below the result mencaraglia@menka-HP-Pavilion-15-Notebook-PC:~$ ubuntu-bug ubuntu-release-upgrader-core Traceback (most recent call last): File /usr/share/apport/apport-kde, line 533, in module sys.exit(UserInterface.run_argv()) File /usr/lib/python3/dist-packages/apport/ui.py, line 650, in run_argv return self.run_report_bug() File /usr/lib/python3/dist-packages/apport/ui.py, line 488, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File /usr/share/apport/apport-kde, line 355, in ui_present_report_details desktop_info) File /usr/share/apport/apport-kde, line 168, in __init__ self.ui.ui_update_view(self) File /usr/share/apport/apport-kde, line 345, in ui_update_view QTreeWidgetItem(keyitem, [line]) TypeError: arguments did not match any overloaded call: QTreeWidgetItem(int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(list-of-str, int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(QTreeWidget, int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(QTreeWidget, list-of-str, int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(QTreeWidget, QTreeWidgetItem, int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(QTreeWidgetItem, int type=QTreeWidgetItem.Type): argument 2 has unexpected type 'list' QTreeWidgetItem(QTreeWidgetItem, list-of-str, int type=QTreeWidgetItem.Type): argument 2 has unexpected type 'list' QTreeWidgetItem(QTreeWidgetItem, QTreeWidgetItem, int type=QTreeWidgetItem.Type): argument 2 has unexpected type 'list' QTreeWidgetItem(QTreeWidgetItem): too many arguments mencaraglia@menka-HP-Pavilion-15-Notebook-PC:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1385095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390921] Re: Problem with Lexmark 120n print driver
Please report this problem to CUPS upstream at http://www.cups.org/str.php with link to this bug report and post a link to your upstream bug report here. Thanks. ** Tags added: needs-upstream-report ** Changed in: cups (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1390921 Title: Problem with Lexmark 120n print driver Status in “cups” package in Ubuntu: Confirmed Bug description: I believe this is the same as Bug #1335558 (and the other bugs it references), just a different printer model (same make as that bug though, so might be worth investigating the other printers in the same range from Lexmark, if that's possible). The workaround in the comments on that bug seems to have worked for me. First print after a restart of the printer works okay, subsequent prints output page after page of garbage characters, with the string PJL ENTER LANGUAGE at the start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1390921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385095] Re: apport-kde crashed reporting a bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1385095 Title: apport-kde crashed reporting a bug Status in “apport” package in Ubuntu: Confirmed Bug description: As requested I ran the ubntu-bug command; here below the result mencaraglia@menka-HP-Pavilion-15-Notebook-PC:~$ ubuntu-bug ubuntu-release-upgrader-core Traceback (most recent call last): File /usr/share/apport/apport-kde, line 533, in module sys.exit(UserInterface.run_argv()) File /usr/lib/python3/dist-packages/apport/ui.py, line 650, in run_argv return self.run_report_bug() File /usr/lib/python3/dist-packages/apport/ui.py, line 488, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File /usr/share/apport/apport-kde, line 355, in ui_present_report_details desktop_info) File /usr/share/apport/apport-kde, line 168, in __init__ self.ui.ui_update_view(self) File /usr/share/apport/apport-kde, line 345, in ui_update_view QTreeWidgetItem(keyitem, [line]) TypeError: arguments did not match any overloaded call: QTreeWidgetItem(int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(list-of-str, int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(QTreeWidget, int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(QTreeWidget, list-of-str, int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(QTreeWidget, QTreeWidgetItem, int type=QTreeWidgetItem.Type): argument 1 has unexpected type 'QTreeWidgetItem' QTreeWidgetItem(QTreeWidgetItem, int type=QTreeWidgetItem.Type): argument 2 has unexpected type 'list' QTreeWidgetItem(QTreeWidgetItem, list-of-str, int type=QTreeWidgetItem.Type): argument 2 has unexpected type 'list' QTreeWidgetItem(QTreeWidgetItem, QTreeWidgetItem, int type=QTreeWidgetItem.Type): argument 2 has unexpected type 'list' QTreeWidgetItem(QTreeWidgetItem): too many arguments mencaraglia@menka-HP-Pavilion-15-Notebook-PC:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1385095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074879] Re: Xorg freeze
Josef Schlehofer, just to clarify, this isn't a primary bug report for anything or anybody except for the original reporter and his hardware. As well, as one would notice, the duplicates are all from the original reporter and his hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1074879 Title: Xorg freeze Status in “xorg” package in Ubuntu: Expired Bug description: keep happen when using HUD ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 4 22:32:17 2012 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day InstallationDate: Installed on 2012-10-20 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1074879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1181530] Re: 13.04 64bit error in cupsd.conf
Since /etc/cups/cupsd.conf is a file that can be changed by anyone with root permission, any idea what caused the double Listen line? Anyway Ubuntu 13.04 is no longer supported, did you still experience this problem in a supported 64 bit release? ** Changed in: cups (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1181530 Title: 13.04 64bit error in cupsd.conf Status in “cups” package in Ubuntu: Incomplete Bug description: I found the system impossible for selecting a package for this bug. I was not able to access localhost:631. I think this may be a bug. I found cupsd.conf had tne Listen /var/run/cups/cups.sock included twice I needed to add Listen localhost:631 (There was no problem in the 32bit version on my laptop} To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1181530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1181530] Re: 13.04 64bit error in cupsd.conf
If I put in Listen /var/run/cups/cups.sock included twice I have no problem accessing localhost:631 on Ubuntu 14.04. Please provide the cupsd.conf file/directive which causes the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1181530 Title: 13.04 64bit error in cupsd.conf Status in “cups” package in Ubuntu: Incomplete Bug description: I found the system impossible for selecting a package for this bug. I was not able to access localhost:631. I think this may be a bug. I found cupsd.conf had tne Listen /var/run/cups/cups.sock included twice I needed to add Listen localhost:631 (There was no problem in the 32bit version on my laptop} To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1181530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389438] [NEW] libedit is missing utf8 support (neeedd for non-Engliish)
You have been subscribed to a public bug: The libedit and libedit-dev packages are missing support for utf8 (and thus, support for most on-English languages). Aparantly, this was a package build bug; the support was always there in the sources, and was just not being built for the package. The issue appears to be fixed upstream, in Debian, and only needs to be pulled into mint: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756736 Symptoms: nm /usr/lib/x86_64-linux-gnu/libedit.a |grep el_wgets reveals nothing, similarly, no symbol for history_w history_winit el_wset history_wend and so on, all of which are in the header file /usr/include/editline/readline.h This is in mint 17 qianna There's a parallel,unassigned bug report for ubuntu: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1375921 ** Affects: libedit (Ubuntu) Importance: Undecided Status: New ** Tags: libedit -- libedit is missing utf8 support (neeedd for non-Engliish) https://bugs.launchpad.net/bugs/1389438 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389438] Re: libedit is missing utf8 support (neeedd for non-Engliish)
*** This bug is a duplicate of bug 1375921 *** https://bugs.launchpad.net/bugs/1375921 ** Project changed: linuxmint = libedit (Ubuntu) ** This bug has been marked a duplicate of bug 1375921 libedit should be updated to wchar_t capable version from debian 3.1-20140620-2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1389438 Title: libedit is missing utf8 support (neeedd for non-Engliish) Status in “libedit” package in Ubuntu: New Bug description: The libedit and libedit-dev packages are missing support for utf8 (and thus, support for most on-English languages). Aparantly, this was a package build bug; the support was always there in the sources, and was just not being built for the package. The issue appears to be fixed upstream, in Debian, and only needs to be pulled into mint: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756736 Symptoms: nm /usr/lib/x86_64-linux-gnu/libedit.a |grep el_wgets reveals nothing, similarly, no symbol for history_w history_winit el_wset history_wend and so on, all of which are in the header file /usr/include/editline/readline.h This is in mint 17 qianna There's a parallel,unassigned bug report for ubuntu: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1375921 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1389438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
As suggested here: http://ubuntuforums.org/showthread.php?t=2249774, a workaround is to upgrade to gnome staging. The forum post suggests testing, but staging solved all problems for me: sudo apt-add-repository ppa:gnome3-team/gnome3 sudo apt-add-repository ppa:gnome3-team/gnome3-staging sudo apt-get update sudo apt-get dist-upgrade This can of course introduce other problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in “xorg” package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible chops (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway. Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372596] Re: /etc/cups/printers.conf rewritten with wrong information at every reboot
Anything in your cups error_log with debugging enabled as described
here: https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS_error_log
** Changed in: cups (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1372596
Title:
/etc/cups/printers.conf rewritten with wrong information at every
reboot
Status in “cups” package in Ubuntu:
Incomplete
Bug description:
When I boot up my system, /etc/cups/printers.conf has the wrong device
URI for my printer. I've tried:
A) correcting it through the cups web GUI at localhost:631
B) substituting a corrected printers.conf by hand by performing:
service cups stop
cp -a /etc/cups/printers.conf.correct /etc/cups/printers.conf
service cups start
Both means correct the problem, and I can print again... UNTIL I
reboot. After the next boot, the incorrect URI is back in
printers.conf and I can't print again.
I can't find where the bad URI is respawning from.
find /etc /var /home -type d -exec grep -H bad_IP_address_from_URI '{}' \;
-print
comes up with nothing. It's got to be cached somewhere, though it appears
not in textual form. Where does this bad URI keep growing back from and how do
I stop it?!?!?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CupsErrorLog:
CurrentDesktop: XFCE
Date: Mon Sep 22 11:00:49 2014
InstallationDate: Installed on 2014-07-22 (61 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64
(20140416.2)
KernLog:
Lpstat: device for Brother8680DN:
ipp://192.168.150.203:631/printers/Brother8680DN
MachineType: Micro-Star International Co., Ltd. GT70 2PC
Papersize: letter
PpdFiles: Brother8680DN: Brother MFC-8680DN BR-Script3
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic
root=UUID=9dda5f94-8c6c-45a4-8a4c-38b3f69a8b15 ro rootflags=subvol=@
rootflags=discard,ssd,compress=no,subvol=@ quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1763IMS.70T
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1763
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.C
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE1763IMS.70T:bd02/12/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT702PC:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1763:rvrREV0.C:cvnMicro-StarInternational:ct10:cvrN/A:
dmi.product.name: GT70 2PC
dmi.product.version: REV:0.C
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1372596/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1393151] Re: Writing to ext4 LVM FS causes GPF in mpage_process_page_bufs
If you can see the GPF happen when mkfs.ext3 is writing to a bare block device (/dev/sdc1 or /dev/sdd1), then it's not involving the file system code at all, but just the block device or device driver code. It's clearly not a file system bug at all, nor is it a e2fsprogs bug, because nothing from user space should be able to trigger this kind of failure --- nor have we seen anyone report anything even vaguely like this on upstream kernels. So it's likely that this is either triggered by some hardware bug, a device-driver specific bug if you are using something esoteric, or a some other miscellaneous bug introduced in the Ubuntu kernel. It's likely that the bug is corrupting the data structures which track the page cache buffers, judging from the stack trace and the fact that the process which died was something entirely unrelated to the the mkfs.ext3: - Nov 16 09:26:03 nas kernel: [ 230.610810] CPU: 1 PID: 1927 Comm: vsftpd Tainted: G D 3.13.0-39-generic #66-Ubuntu It might be useful to try running mkfs.ext3 to a USB-attached storage device, and see if that triggers the problem. If doesn't and you can safely write to the USB drive, then the figure of suspicion would pretty squarely fall on the hardware device or its device driver (or the Ubuntu kernel, of course). It might also be useful to try this on another server altogether, or to try swapping out to another kernel (say, an upstream kernel). Cheers, - Ted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1393151 Title: mkfs.ext3 causes kernel panic on new WD 6 TB drive Status in “e2fsprogs” package in Ubuntu: New Bug description: mkfs.ext3 always causes a kernel panic on both of my WD 6 TB drives while writing the inode tables. Both drives were initialised using parted with a GPT and a single partition (mkpart primary 2048s 100%) sdc 8:32 0 5.5T 0 disk └─sdc1 8:33 0 5.5T 0 part sdd 8:48 0 5.5T 0 disk └─sdd1 8:49 0 5.5T 0 part mkfs.ext3 /dev/sdc1 mke2fs 1.42.10 (18-May-2014) Creating filesystem with 1465130240 4k blocks and 18318 inodes Filesystem UUID: 1a6458a3-908d-48a0-a532-e9cbc1eb5ca4 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848, 51200, 550731776, 644972544 Allocating group tables: done Writing inode tables: 4937/44713 -- KP occurs here -- mkfs.ext3 /dev/sdd1 mke2fs 1.42.10 (18-May-2014) Creating filesystem with 1465130240 4k blocks and 18318 inodes Filesystem UUID: 3d6537ee-78f6-4a68-a833-e5dda4b69028 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848, 51200, 550731776, 644972544 Allocating group tables: done Writing inode tables: 4997/44713 -- KP occurs here -- I'll have to try to take a photo of the KP since it's not being logged, I'm just seeing it on the screen. Creating an ext4 partition works fine but the crash just happens later after writing files to the partition. Disks seems to be fine smart- wise. It's unlikely that both disks are damaged in almost the same area without S.M.A.R.T. noticing it. -- apt-cache policy e2fslibs:amd64 e2fslibs: Installed: 1.42.9-3ubuntu1 Candidate: 1.42.9-3ubuntu1 Version table: *** 1.42.9-3ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status -- smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED smartctl -H /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED -- lshw -short H/W path Device Class Description
[Touch-packages] [Bug 1393221] [NEW] package python3-crypto 2.6.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I was upgrading the current Lubuntu (14.04) to Ubuntu when this occurred. I was using the terminal and sudo apt-get install ubuntu. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: python3-crypto 2.6.1-5 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Sun Nov 16 11:07:53 2014 DuplicateSignature: package:python3-crypto:2.6.1-5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-11-09 (7 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) SourcePackage: python-crypto Title: package python3-crypto 2.6.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-crypto (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1393221 Title: package python3-crypto 2.6.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “python-crypto” package in Ubuntu: New Bug description: I was upgrading the current Lubuntu (14.04) to Ubuntu when this occurred. I was using the terminal and sudo apt-get install ubuntu. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: python3-crypto 2.6.1-5 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Sun Nov 16 11:07:53 2014 DuplicateSignature: package:python3-crypto:2.6.1-5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-11-09 (7 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) SourcePackage: python-crypto Title: package python3-crypto 2.6.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1393221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393221] Re: package python3-crypto 2.6.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1393221 Title: package python3-crypto 2.6.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “python-crypto” package in Ubuntu: New Bug description: I was upgrading the current Lubuntu (14.04) to Ubuntu when this occurred. I was using the terminal and sudo apt-get install ubuntu. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: python3-crypto 2.6.1-5 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Sun Nov 16 11:07:53 2014 DuplicateSignature: package:python3-crypto:2.6.1-5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-11-09 (7 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) SourcePackage: python-crypto Title: package python3-crypto 2.6.1-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1393221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 814732] Re: Screen freezes after lid closed / opening lid: Screen restored, mouse moves but no reaction!
Ringelkrat, thank you for reporting this bug to Ubuntu. Natty reached EOL on October 28, 2012. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 814732 ** This bug is no longer a duplicate of bug 772925 Screen freezes after laptop lid closed for more than 1 minute ** Package changed: xorg (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/814732 Title: Screen freezes after lid closed / opening lid: Screen restored, mouse moves but no reaction! Status in “linux” package in Ubuntu: Incomplete Bug description: I can not reproduce it certainly: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description: Ubuntu 11.04 Release: 11.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center xorg: Installiert: 1:7.6+4ubuntu3.1 Kandidat:1:7.6+4ubuntu3.1 Versionstabelle: *** 1:7.6+4ubuntu3.1 0 500 http://de.archive.ubuntu.com/ubuntu/ natty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.6+4ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 3) What you expected to happen That when I open the lid the screen is restored and that I can continue to work with Ubuntu. 4) What happened instead The screen has been restored, but I could only move the mouse. Nothing responded in the session (neither to the mouse nor keyboard). But I could restart xorg by CTR+ALT+BACKSPACE. Of course then my session was lost. I assume it may be the same bug as #772925 ! ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3.1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Jul 22 18:49:57 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.38+bdcom, 2.6.38-10-generic, x86_64: installed bcmwl, 5.100.82.38+bdcom, 2.6.38-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:161d] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: Hewlett-Packard HP ProBook 6460b ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=591551af-239b-442e-a423-f8ee2f1975c5 ro vga=799 quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.03 dmi.board.name: 161D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.40 dmi.chassis.asset.tag: CNU1234JXQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.03:bd04/27/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.40:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6460b dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1393238] [NEW] package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a
Public bug reported: i don't know (automatic generated report) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 15 15:39:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.2:no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado ErrorMessage: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3629] InstallationDate: Installed on 2014-09-29 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. M85M-US2H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=950b265a-1846-43c2-89b8-a3d488cefc08 ro quiet splash SourcePackage: mesa Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: M85M-US2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM85M-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM85M-US2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M85M-US2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 16 20:32:48 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1393238 Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux- gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so .dpkg-new': fin de fichero o de flujo inesperado Status in “mesa” package in Ubuntu: New Bug description: i don't know (automatic generated report) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins:
[Touch-packages] [Bug 1393238] Re: package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1393238 Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux- gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so .dpkg-new': fin de fichero o de flujo inesperado Status in “mesa” package in Ubuntu: New Bug description: i don't know (automatic generated report) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 15 15:39:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.2:no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado ErrorMessage: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3629] InstallationDate: Installed on 2014-09-29 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. M85M-US2H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=950b265a-1846-43c2-89b8-a3d488cefc08 ro quiet splash SourcePackage: mesa Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: M85M-US2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM85M-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM85M-US2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M85M-US2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 16 20:32:48 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1393238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393241] [NEW] Xorg memory leak
Public bug reported: Xorg keeps going up with its physical memory usage and it keeps on doing so until it takes over all of my RAM and eventually my system becomes highly unstable. It goes up faster if I do stuff on my pc, like browsing or using applications. After a few days of non-stop usage I need to restart it because my pc cannot handle it anymore, it skyrockets, slowly but surely. I'm using ubuntu trusty, fglrx gpu drivers and everything is encrypted using built-in encryption. This is a serious issue and needs to be fixed asap, it renders the pc useless after just a few days. I'll gladly provide further information if you contact me on my mail. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 16 20:40:55 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-32-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-39-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2308] InstallationDate: Installed on 2014-11-01 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0407 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0407:bd07/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Nov 14 16:05:13 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1393241 Title: Xorg memory leak Status in “xorg” package in Ubuntu: New Bug description: Xorg keeps going up with its physical memory usage and it keeps on doing so until it takes over all of my RAM and eventually my system becomes highly unstable. It goes up faster if I do stuff on my pc, like browsing or using applications. After a few days of non-stop usage I need to restart it because my pc cannot
[Touch-packages] [Bug 1393242] [NEW] I need Help with how to fix Ubuntu Bugs
Public bug reported: Dear Sir The Ubuntu One Bug Report about my computer is all useless info because I do not understand this report is all very confusioning do you have eny type of repair software or programs to fix Ubuntu Bugs Forms and blogs are very uesless and you just hear about lots of peoples Ubuntu problems and computer nightmares and I do not unerstand thos sites at all . Can you please help me with this becasue I am very lost with this hole thing thank you Phillip Coss ps don't how use termal very lost don't understand it at all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Nov 16 11:09:19 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0292] InstallationDate: Installed on 2014-11-14 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Gateway NV53 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0a956056-f4b9-4936-b377-dec9899a8781 ro splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.02 dmi.board.name: SJV50TR dmi.board.vendor: Gateway dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.02:bd08/11/2009:svnGateway:pnNV53:pvr0100:rvnGateway:rnSJV50TR:rvrRev:cvnGateway:ct10:cvrNone: dmi.product.name: NV53 dmi.product.version: 0100 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 16 10:18:07 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1393242 Title: I need Help with how to fix Ubuntu Bugs Status in “xorg” package in Ubuntu: New Bug description: Dear Sir The Ubuntu One Bug Report about my computer is all useless info because I do not understand this report is all very confusioning do you have eny type of repair software or programs to fix Ubuntu Bugs Forms and blogs are very uesless and you just hear about lots of peoples Ubuntu problems and computer nightmares and I do not unerstand thos sites at all . Can you please help me with this becasue I am very lost with this hole thing thank you Phillip Coss ps don't how use termal very lost don't understand it at all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Nov 16 11:09:19 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0292] InstallationDate: Installed on 2014-11-14 (1 days ago) InstallationMedia: Ubuntu
[Touch-packages] [Bug 1393242] Re: I need Help with how to fix Ubuntu Bugs
Need help how to fix of find software to fix bug probelms i am very lost with hole bug thin Phillip Coss needs HELP PLEASE thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1393242 Title: I need Help with how to fix Ubuntu Bugs Status in “xorg” package in Ubuntu: New Bug description: Dear Sir The Ubuntu One Bug Report about my computer is all useless info because I do not understand this report is all very confusioning do you have eny type of repair software or programs to fix Ubuntu Bugs Forms and blogs are very uesless and you just hear about lots of peoples Ubuntu problems and computer nightmares and I do not unerstand thos sites at all . Can you please help me with this becasue I am very lost with this hole thing thank you Phillip Coss ps don't how use termal very lost don't understand it at all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Nov 16 11:09:19 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0292] InstallationDate: Installed on 2014-11-14 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Gateway NV53 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0a956056-f4b9-4936-b377-dec9899a8781 ro splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.02 dmi.board.name: SJV50TR dmi.board.vendor: Gateway dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.02:bd08/11/2009:svnGateway:pnNV53:pvr0100:rvnGateway:rnSJV50TR:rvrRev:cvnGateway:ct10:cvrNone: dmi.product.name: NV53 dmi.product.version: 0100 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 16 10:18:07 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302491] Re: when autlogin with a timeout is used, it should be reapplied when the user logs out.
** Tags removed: verification-needed ** Tags added: verification-dibe ** Tags removed: verification-dibe ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1302491 Title: when autlogin with a timeout is used, it should be reapplied when the user logs out. Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: Fix Committed Status in “lightdm” source package in Utopic: Fix Released Bug description: [Impact] If LightDM is set up for timed login this only occurs on first login, i..e after a session logout timed login is not reattempted. This doesn't match the traditional behaviour of GDM. A common use case for timed login is kiosk setups where the greeter should never be displayed for any significant amount of time; this is currently impossible to set up with LightDM. [Test Case] 1. Setup LightDM to do a timed login 2. Wait for timeout (session starts) 3. Log out of session Expected result: The session is started again after the timeout. Observed result: The greeter is show forever. [Regression potential] There is some risk that someone might have been relying on the existing behaviour. The assumption is that most timed login users would prefer the new behaviour. There is a small risk that these changes may have broken something else, this has been reduced by using the regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1302491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393215] [NEW] loss of temporary IPv6 addresses
You have been subscribed to a public bug: (filing bug via web form because of 1385095) Description:Ubuntu 14.10 Release:14.10 network-manager: Installato: 0.9.8.8-0ubuntu28 Candidato: 0.9.8.8-0ubuntu28 Tabella versione: *** 0.9.8.8-0ubuntu28 0 500 http://it.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Expected behaviour: permanent and temporary IPv6 are renewed when necessary Observed behaviour: Every so often, the system loses its temporary IPv6 addresses and is left with the main address alone. In this situation, sites such as Google (which already prefers IPv6 if available) will stall. Workaround is to disconnect/reconnect wifi to obtain new temporary addresses. There seems to be no interesting message in the router log (using OpenWRT 14.07) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- loss of temporary IPv6 addresses https://bugs.launchpad.net/bugs/1393215 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370327] Re: Add API to get UID for users
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1370327 Title: Add API to get UID for users Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: Fix Committed Status in “lightdm” source package in Utopic: Fix Released Bug description: [Impact] The LightDM user list provided to greeters via liblightdm doesn't have a method to access the user ID. This requires a greeter that might need this information to do a second lookup to get it. [Test Case] 1. Write a greeter that needs the user ID Expected result: Can do it. Observed result: Can't do it. [Regression Potential] Low, the information was already in liblightdm, we just now expose it. Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1370327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393215] Re: loss of temporary IPv6 addresses
** Package changed: ubuntu = network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1393215 Title: loss of temporary IPv6 addresses Status in “network-manager” package in Ubuntu: New Bug description: (filing bug via web form because of 1385095) Description:Ubuntu 14.10 Release:14.10 network-manager: Installato: 0.9.8.8-0ubuntu28 Candidato: 0.9.8.8-0ubuntu28 Tabella versione: *** 0.9.8.8-0ubuntu28 0 500 http://it.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Expected behaviour: permanent and temporary IPv6 are renewed when necessary Observed behaviour: Every so often, the system loses its temporary IPv6 addresses and is left with the main address alone. In this situation, sites such as Google (which already prefers IPv6 if available) will stall. Workaround is to disconnect/reconnect wifi to obtain new temporary addresses. There seems to be no interesting message in the router log (using OpenWRT 14.07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393215] Re: loss of temporary IPv6 addresses
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1393215 Title: loss of temporary IPv6 addresses Status in “network-manager” package in Ubuntu: New Bug description: (filing bug via web form because of 1385095) Description:Ubuntu 14.10 Release:14.10 network-manager: Installato: 0.9.8.8-0ubuntu28 Candidato: 0.9.8.8-0ubuntu28 Tabella versione: *** 0.9.8.8-0ubuntu28 0 500 http://it.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Expected behaviour: permanent and temporary IPv6 are renewed when necessary Observed behaviour: Every so often, the system loses its temporary IPv6 addresses and is left with the main address alone. In this situation, sites such as Google (which already prefers IPv6 if available) will stall. Workaround is to disconnect/reconnect wifi to obtain new temporary addresses. There seems to be no interesting message in the router log (using OpenWRT 14.07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393151] Re: mkfs.ext3 causes kernel panic on new WD 6 TB drive
Ted, thanks for taking the time to reply to my problem in such a prompt manner. - Using an old 2 TB drive instead of the 6 TB drive: GPF (so it's not related to the drives or the large capacity) - mainline/v3.17.3 kernel: GPF - Debian wheezy live cd: GPF - mkfs.ext3 to a USB-stick: worked flawlessly Interestingly, two 120 GB SSDs work just fine with everything I throw at them. I can't believe I'm the only one affected by this problem, the Gigabyte H97N-WIFI board is available since April... but for the moment it looks im SOL. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1393151 Title: mkfs.ext3 causes kernel panic on new WD 6 TB drive Status in “e2fsprogs” package in Ubuntu: New Bug description: mkfs.ext3 always causes a kernel panic on both of my WD 6 TB drives while writing the inode tables. Both drives were initialised using parted with a GPT and a single partition (mkpart primary 2048s 100%) sdc 8:32 0 5.5T 0 disk └─sdc1 8:33 0 5.5T 0 part sdd 8:48 0 5.5T 0 disk └─sdd1 8:49 0 5.5T 0 part mkfs.ext3 /dev/sdc1 mke2fs 1.42.10 (18-May-2014) Creating filesystem with 1465130240 4k blocks and 18318 inodes Filesystem UUID: 1a6458a3-908d-48a0-a532-e9cbc1eb5ca4 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848, 51200, 550731776, 644972544 Allocating group tables: done Writing inode tables: 4937/44713 -- KP occurs here -- mkfs.ext3 /dev/sdd1 mke2fs 1.42.10 (18-May-2014) Creating filesystem with 1465130240 4k blocks and 18318 inodes Filesystem UUID: 3d6537ee-78f6-4a68-a833-e5dda4b69028 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848, 51200, 550731776, 644972544 Allocating group tables: done Writing inode tables: 4997/44713 -- KP occurs here -- I'll have to try to take a photo of the KP since it's not being logged, I'm just seeing it on the screen. Creating an ext4 partition works fine but the crash just happens later after writing files to the partition. Disks seems to be fine smart- wise. It's unlikely that both disks are damaged in almost the same area without S.M.A.R.T. noticing it. -- apt-cache policy e2fslibs:amd64 e2fslibs: Installed: 1.42.9-3ubuntu1 Candidate: 1.42.9-3ubuntu1 Version table: *** 1.42.9-3ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status -- smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org smartctl -H /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED smartctl -H /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED -- lshw -short H/W path Device Class Description system H97N-WIFI (To be filled by O.E.M.) /0busH97N-WIFI /0/0 memory 64KiB BIOS /0/3d processor Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz /0/3d/3e memory 128KiB L1 cache /0/3d/3f memory 512KiB L2 cache /0/3d/40 memory 3MiB L3 cache /0/42 memory 8GiB System Memory /0/42/0 memory 4GiB DIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/42/1 memory DIMM [empty] /0/42/2 memory 4GiB DIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/42/3 memory DIMM [empty] /0/100bridge 4th Gen Core Processor DRAM Controller /0/100/2 display4th Generation Core Processor
[Touch-packages] [Bug 1359582] Re: Aggregating scope results sometimes miss one of their children at startup
** Changed in: unity-scopes-api (Ubuntu) Status: New = Fix Released ** Changed in: unity-scopes-api (Ubuntu Utopic) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1359582 Title: Aggregating scope results sometimes miss one of their children at startup Status in API for Unity scopes integration: Fix Released Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Fix Released Status in “unity-scopes-api” source package in Utopic: Fix Released Bug description: build: #202 last known good build: #201 Test Case: 1. Upload music to ~/Music via MTP 2. Go to the music scope Expected Behaviour Music uploaded is displayed in the scope Actual Behaviour Music uploaded is not displayed in the scope To confirm that the music is valid, open the filemanager, navigate to ~/Music and launch the title you just uploaded On #202 downgrading the following packages fixes the problem: - libunity-scopes3 0.6.1+14.10.20140809-0ubuntu1 - unity-plugin-scopes 0.5.3+14.10.20140806-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-scope-mediascanner2 0.2+14.10.20140813-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Thu Aug 21 09:23:25 2014 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140821-020204) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scopes-api/+bug/1359582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392529] Re: Error executing scope with long name on PC
In real l ife, the path is something like /run/user/uid/zmqscope_id or /run/user/uid/zmq/priv/scope_id. That leaves around 80 characters for the scope ID. The 107 character limit is hard-baked into the kernel, so we can't change that. We could do something along the lines of computing an MD4 hash and using that as the name instead, but that would leave the endpoint names incomprehensible, which is not good. Pragmatically, I think a better solution would be for the scope tool to shorten the prefix it creates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1392529 Title: Error executing scope with long name on PC Status in “unity-scopes-api” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Bug description: I'm developing a scope, but I have this error after the launch, and I'm not able have any response by any query: com.ubuntu.developer.rpadovani.discerningduck_discerningduck-c query(): unity::scopes::MiddlewareException: Socket path name too long (max = 107): /tmp/rpadovani/scope-dev-endpoints.USoi22/priv/com.ubuntu.developer.rpadovani.discerningduck_discerningduck-c The interesting part it's I have two computers, a desktop and a netbook, and I have the error only on the netbook. Both have same code, both have utopic updated with same apt sources, I have the same username (rpadovani) on both and both are 64bit. I have no idea on why on one fails and on other doesn't, please let me know if I could provide some logs to debug this. Alejandro J. Cura suggests this is a bug in the scope registry, because sockets paths do have the limit that the error shows: http://bugs.mysql.com/bug.php?id=42512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1392529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375921] Re: libedit should be updated to wchar_t capable version from debian 3.1-20140620-2
Basically, this means that there's no utf8 support, which means that almost any non-Eglish language fails. Appearently, this was/is a package build bug; the support was always there in the sources, and was just not being built for the package. typical symptoms: nm /usr/lib/x86_64-linux-gnu/libedit.a |grep el_wgets reveals nothing, likewise a grep for history_w history_winit el_wset history_wend and so on, all of which are in the header file /usr/include/editline/readline.h -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1375921 Title: libedit should be updated to wchar_t capable version from debian 3.1-20140620-2 Status in “libedit” package in Ubuntu: Confirmed Bug description: Current libedit claims to have wchar_t support in its changelog but doesn't, as per this bug on the debian bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756736 The debian package has been fixed and the package minor version updated, it'd be really nice to get this into ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1375921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378184] Re: RTM r3 why is Nepali Unicode texts not displaying in browser app
Rakesh, this bug potentially affects every single application on ubuntu touch, not just the browser, so it’s not useful to mark webbrowser-app as affected. The bug is already tracked where it belongs, in ubuntu- touch-meta. ** Changed in: webbrowser-app Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1378184 Title: RTM r3 why is Nepali Unicode texts not displaying in browser app Status in Web Browser App: Invalid Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Status in “webbrowser-app” package in Ubuntu: Invalid Status in “ubuntu-touch-meta” package in Ubuntu RTM: Confirmed Bug description: In browser app including facebook and google+ web app nepali unicode texts are displayed as rectangle boxes instead of actual texts. Doesn't it support unicode? To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1378184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393255] [NEW] need find a debugging software
Public bug reported: Hi its Phillip Coss [Bug 1393122] Re: package libegl1-mesa:amd64 10.1.3-0ubuntu 0.2 failed to install/upgrade: package libegl1-mesa: amd64 is already installed and configured What do i do to fix this Bug Help thank you Phillip Coss is there a good how to book on to use this OS Ubuntu 14.04v amd64 pc ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Nov 16 13:46:26 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0292] InstallationDate: Installed on 2014-11-14 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Gateway NV53 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0a956056-f4b9-4936-b377-dec9899a8781 ro splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.02 dmi.board.name: SJV50TR dmi.board.vendor: Gateway dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.02:bd08/11/2009:svnGateway:pnNV53:pvr0100:rvnGateway:rnSJV50TR:rvrRev:cvnGateway:ct10:cvrNone: dmi.product.name: NV53 dmi.product.version: 0100 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 16 13:42:52 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1393255 Title: need find a debugging software Status in “xorg” package in Ubuntu: New Bug description: Hi its Phillip Coss [Bug 1393122] Re: package libegl1-mesa:amd64 10.1.3-0ubuntu 0.2 failed to install/upgrade: package libegl1-mesa: amd64 is already installed and configured What do i do to fix this Bug Help thank you Phillip Coss is there a good how to book on to use this OS Ubuntu 14.04v amd64 pc ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Nov 16 13:46:26 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0292] InstallationDate: Installed on 2014-11-14 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Gateway NV53 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0a956056-f4b9-4936-b377-dec9899a8781 ro splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Phoenix Technologies LTD
[Touch-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
I have the same problem with an apple keyboard # uname -a Linux saturn 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # lsb_release Distributor ID: Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 Codename: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Precise: Invalid Status in “upower” source package in Precise: Fix Released Status in “gnome-power-manager” source package in Quantal: Invalid Status in “upower” source package in Quantal: Confirmed Status in “gnome-power-manager” source package in Raring: Invalid Status in “upower” source package in Raring: Fix Released Status in “gnome-power-manager” source package in Saucy: Invalid Status in “upower” source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to Critically Low and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions:
[Touch-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
I have the same problem with an apple keyboard # uname -a Linux saturn 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # lsb_release Distributor ID: Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 Codename: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Precise: Invalid Status in “upower” source package in Precise: Fix Released Status in “gnome-power-manager” source package in Quantal: Invalid Status in “upower” source package in Quantal: Confirmed Status in “gnome-power-manager” source package in Raring: Invalid Status in “upower” source package in Raring: Fix Released Status in “gnome-power-manager” source package in Saucy: Invalid Status in “upower” source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to Critically Low and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions:
[Touch-packages] [Bug 1358151] Re: package libgl1-mesa-dri 10.1.0-4ubuntu5 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1358151 Title: package libgl1-mesa-dri 10.1.0-4ubuntu5 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in “mesa” package in Ubuntu: Confirmed Bug description: This update crashes since I moved to Ubuntu 14.04. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.0-4ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 337.19 Tue Apr 29 19:58:58 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Sun Aug 17 15:20:50 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:10.1.0-4ubuntu5:trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0977] InstallationDate: Installed on 2013-01-31 (563 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Vostro 470 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=ee5fd3d1-507f-4967-b739-8995eebbe0e6 ro drm.debug=0xe plymouth:debug SourcePackage: mesa Title: package libgl1-mesa-dri 10.1.0-4ubuntu5 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0NW73C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/05/2012:svnDellInc.:pnVostro470:pvr:rvnDellInc.:rn0NW73C:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54+git20140523.8fc62ca8-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0~git20140523.172ef0c5-0ubuntu0ricotz~trusty version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Aug 18 09:17:03 2014 xserver.configfile: default xserver.errors: Failed to load module nouveau (module does not exist, 0) Failed to load module nouveau (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1358151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393264] [NEW] Sync lzo2 2.08-1 (main) from Debian unstable (main)
Public bug reported: Please sync lzo2 2.08-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * SECURITY UPDATE: denial of service or possible code execution via integer overflow - debian/patches/CVE-2014-4607.patch: check for overflow in minilzo/minilzo.c, src/lzo1_d.ch, src/lzo1b_d.ch, src/lzo1f_d.ch, src/lzo1x_d.ch, src/lzo2a_d.ch. - CVE-2014-4607 * SECURITY UPDATE: denial of service or possible code execution via integer overflow - debian/patches/CVE-2014-4607.patch: check for overflow in minilzo/minilzo.c, src/lzo1_d.ch, src/lzo1b_d.ch, src/lzo1f_d.ch, src/lzo1x_d.ch, src/lzo2a_d.ch. - CVE-2014-4607 * Build using dh-autoreconf. * Build using dh-autoreconf. Debian supports autotools instead autoreconf. Changelog entries since current vivid version 2.06-1.2ubuntu2: lzo2 (2.08-1) unstable; urgency=low * New upstream release (closes: #752861) (CVE-2014-4607) * Update standards version * Add autotools-dev to build dependencies (closes: #750622) -- Peter Eisentraut pet...@debian.org Mon, 14 Jul 2014 21:03:12 -0400 ** Affects: lzo2 (Ubuntu) Importance: Wishlist Status: New ** Changed in: lzo2 (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lzo2 in Ubuntu. https://bugs.launchpad.net/bugs/1393264 Title: Sync lzo2 2.08-1 (main) from Debian unstable (main) Status in “lzo2” package in Ubuntu: New Bug description: Please sync lzo2 2.08-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * SECURITY UPDATE: denial of service or possible code execution via integer overflow - debian/patches/CVE-2014-4607.patch: check for overflow in minilzo/minilzo.c, src/lzo1_d.ch, src/lzo1b_d.ch, src/lzo1f_d.ch, src/lzo1x_d.ch, src/lzo2a_d.ch. - CVE-2014-4607 * SECURITY UPDATE: denial of service or possible code execution via integer overflow - debian/patches/CVE-2014-4607.patch: check for overflow in minilzo/minilzo.c, src/lzo1_d.ch, src/lzo1b_d.ch, src/lzo1f_d.ch, src/lzo1x_d.ch, src/lzo2a_d.ch. - CVE-2014-4607 * Build using dh-autoreconf. * Build using dh-autoreconf. Debian supports autotools instead autoreconf. Changelog entries since current vivid version 2.06-1.2ubuntu2: lzo2 (2.08-1) unstable; urgency=low * New upstream release (closes: #752861) (CVE-2014-4607) * Update standards version * Add autotools-dev to build dependencies (closes: #750622) -- Peter Eisentraut pet...@debian.org Mon, 14 Jul 2014 21:03:12 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lzo2/+bug/1393264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341125] Re: Cannot enter floating point (double) numbers
After further investigation it seems that gdb assumes that floating- point numbers use . as decimal mark, as these lines from c-exp.y show else if (!got_dot *p == '.') got_dot = 1; but, later, the function parse_float() (in parse.c) feeds the string into sscanf num = sscanf (copy, % DOUBLEST_SCAN_FORMAT %n, d, n); and, apparently, sscanf is locale-sensitive, so, if the current locale has , as decimal mark, sscanf will leave everything past the . sign unscanned. gdb, then, notices that something is unscanned and says invalid number -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1341125 Title: Cannot enter floating point (double) numbers Status in “gdb” package in Ubuntu: New Bug description: (gdb) show version GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word. (gdb) p 1.0 Invalid number 1.0. Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b from today) recognises 1.0 just fine, as a double To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1341125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341125] Re: Cannot enter floating point (double) numbers
Filed upstream bug https://sourceware.org/bugzilla/show_bug.cgi?id=17607 ** Bug watch added: Sourceware.org Bugzilla #17607 http://sourceware.org/bugzilla/show_bug.cgi?id=17607 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1341125 Title: Cannot enter floating point (double) numbers Status in “gdb” package in Ubuntu: New Bug description: (gdb) show version GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word. (gdb) p 1.0 Invalid number 1.0. Yet, the latest git (tested 76bd66cfb5207137dac01534cf7d8af8f708743b from today) recognises 1.0 just fine, as a double To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1341125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393206] [NEW] SD/mmc card with exFAT fs not automatically mounted since upgrade to utopic
You have been subscribed to a public bug:
Inserting a memory card formatted with exFAT in my built-in memory
reader doesn't automatically mount the partition since I upgraded to
utopic (from trusty). Before this it mounted the partition without any
problems. I have installed exfat-fuse and exfat-utils as before.
udisks2 detects the partition correctly but gvfs ignores it:
17:00:48.133: Added /org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95
org.freedesktop.UDisks2.Drive:
CanPowerOff:false
Configuration: {}
ConnectionBus: sdio
Ejectable: false
Id: SU64G-0xa21a0d95
Media: flash_sd
MediaAvailable: true
MediaChangeDetected:true
MediaCompatibility: flash_sd
MediaRemovable: true
Model: SU64G
Optical:false
OpticalBlank: false
OpticalNumAudioTracks: 0
OpticalNumDataTracks: 0
OpticalNumSessions: 0
OpticalNumTracks: 0
Removable: true
Revision:
RotationRate: 0
Seat: seat0
Serial: 0xa21a0d95
SiblingId:
Size: 63864569856
SortKey:01hotplug/1416153648130773
TimeDetected: 1416153648130773
TimeMediaDetected: 1416153648130773
Vendor:
WWN:
17:00:48.134: Added /org/freedesktop/UDisks2/block_devices/mmcblk0
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/mmcblk0
DeviceNumber: 45824
Drive:
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/mmcblk0
ReadOnly: false
Size: 63864569856
Symlinks: /dev/disk/by-id/mmc-SU64G_0xa21a0d95
org.freedesktop.UDisks2.PartitionTable:
Type: dos
17:00:48.183: Added /org/freedesktop/UDisks2/block_devices/mmcblk0p1
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/mmcblk0p1
DeviceNumber: 45825
Drive:
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/mmcblk0p1
ReadOnly: false
Size: 63863521280
Symlinks: /dev/disk/by-id/mmc-SU64G_0xa21a0d95-part1
org.freedesktop.UDisks2.Partition:
Flags: 0
IsContained:false
IsContainer:false
Name:
Number: 1
Offset: 1048576
Size: 63863521280
Table: '/org/freedesktop/UDisks2/block_devices/mmcblk0'
Type:
UUID:
Drive connected:'SU64G'
Drive(0): SU64G
Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
ids:
unix-device: '/dev/mmcblk0'
themed icons: [drive-removable-media-flash-sd]
[drive-removable-media-flash] [drive-removable-media] [drive-removable]
[drive]
symbolic themed icons: [drive-removable-media-symbolic]
[drive-removable-symbolic] [drive-symbolic] [drive-removable-media]
[drive-removable] [drive]
is_media_removable=1
has_media=1
is_media_check_automatic=1
can_poll_for_media=0
can_eject=0
can_start=0
can_stop=0
start_stop_type=shutdown
sort_key=01hotplug/1416153648130773
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-25-lowlatency 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-lowlatency 3.16.7
Uname:
[Touch-packages] [Bug 1393206] Re: SD/mmc card with exFAT fs not automatically mounted since upgrade to utopic
It looks like apparmor isn't allowing the mount.
[ 7963.575900] audit: type=1400 audit(1416145652.685:70):
apparmor=DENIED operation=mount info=failed mntpnt match error=-13
profile=/usr/lib/lightdm/lightdm-guest-session
name=/run/user/127/gvfs/ pid=7101 comm=gvfsd-fuse fstype=fuse
.gvfsd-fuse srcname=gvfsd-fuse flags=rw, nosuid, nodev
I'm not sure which package is really to blame here, but I'm pretty sure
it isn't the kernel. I'm changing this to affect apparmor, as I'm
guessing someone there ought to know which package has actually caused
this to regress.
** Package changed: linux (Ubuntu) = apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1393206
Title:
SD/mmc card with exFAT fs not automatically mounted since upgrade to
utopic
Status in “apparmor” package in Ubuntu:
Confirmed
Bug description:
Inserting a memory card formatted with exFAT in my built-in memory
reader doesn't automatically mount the partition since I upgraded to
utopic (from trusty). Before this it mounted the partition without any
problems. I have installed exfat-fuse and exfat-utils as before.
udisks2 detects the partition correctly but gvfs ignores it:
17:00:48.133: Added /org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95
org.freedesktop.UDisks2.Drive:
CanPowerOff:false
Configuration: {}
ConnectionBus: sdio
Ejectable: false
Id: SU64G-0xa21a0d95
Media: flash_sd
MediaAvailable: true
MediaChangeDetected:true
MediaCompatibility: flash_sd
MediaRemovable: true
Model: SU64G
Optical:false
OpticalBlank: false
OpticalNumAudioTracks: 0
OpticalNumDataTracks: 0
OpticalNumSessions: 0
OpticalNumTracks: 0
Removable: true
Revision:
RotationRate: 0
Seat: seat0
Serial: 0xa21a0d95
SiblingId:
Size: 63864569856
SortKey:01hotplug/1416153648130773
TimeDetected: 1416153648130773
TimeMediaDetected: 1416153648130773
Vendor:
WWN:
17:00:48.134: Added /org/freedesktop/UDisks2/block_devices/mmcblk0
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/mmcblk0
DeviceNumber: 45824
Drive:
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/mmcblk0
ReadOnly: false
Size: 63864569856
Symlinks: /dev/disk/by-id/mmc-SU64G_0xa21a0d95
org.freedesktop.UDisks2.PartitionTable:
Type: dos
17:00:48.183: Added /org/freedesktop/UDisks2/block_devices/mmcblk0p1
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/mmcblk0p1
DeviceNumber: 45825
Drive:
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/mmcblk0p1
ReadOnly: false
Size: 63863521280
Symlinks: /dev/disk/by-id/mmc-SU64G_0xa21a0d95-part1
org.freedesktop.UDisks2.Partition:
Flags: 0
IsContained:false
[Touch-packages] [Bug 1393271] [NEW] ibus can't select past the first five choices
Public bug reported: The ibus can't select past the first five choices. after turning to second page or more, pressing 1~5 will not get that corresponding character/word, but something entirely unrelated instead. 13.10下的ibus-googlepinyin就已经不能输入前五个选项以外的字词了--即，凡是要翻页的，翻页以后就不能正常选字、词了。13 .10下的ibus-table-wubi也有同样的问题。 All ibus related packages installed in my Ubuntu 13.10, problem shows up as early as: gir1.2-ibus-1.0_1.5.3-6ubuntu2.1 ibus_1.5.3-6ubuntu2.1 ibus-googlepinyin_0.1.2-2 ibus-pinyin_1.4.0-2ubuntu2 ibus-pinyin-db-open-phrase_1.4.0-2ubuntu2 ibus-table_1.5.0.is.1.5.0-0ubuntu1 ibus-table-wubi_1.4.0.20121008-1 libibus-1.0-5:amd64_1.5.3-6ubuntu2 libusb-0.1-4:amd64_2:0.1.12-23.2ubuntu1 libusb-1.0-0:amd64_2:1.0.16-3 libusbmuxd2_1.0.8-1ubuntu1 libustr-1.0-1:amd64_1.0.4-3ubuntu1 python-ibus_1.5.3-6ubuntu2.1 $ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 $ uname -rm 3.11.0-26-generic x86_64 ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Affects: ibus-googlepinyin (Ubuntu) Importance: Undecided Status: New ** Affects: ibus-table-wubi (Ubuntu) Importance: Undecided Status: New ** Also affects: ibus-googlepinyin (Ubuntu) Importance: Undecided Status: New ** Also affects: ibus-table-wubi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1393271 Title: ibus can't select past the first five choices Status in “ibus” package in Ubuntu: New Status in “ibus-googlepinyin” package in Ubuntu: New Status in “ibus-table-wubi” package in Ubuntu: New Bug description: The ibus can't select past the first five choices. after turning to second page or more, pressing 1~5 will not get that corresponding character/word, but something entirely unrelated instead. 13.10下的ibus-googlepinyin就已经不能输入前五个选项以外的字词了--即，凡是要翻页的，翻页以后就不能正常选字、词了。13 .10下的ibus-table-wubi也有同样的问题。 All ibus related packages installed in my Ubuntu 13.10, problem shows up as early as: gir1.2-ibus-1.0_1.5.3-6ubuntu2.1 ibus_1.5.3-6ubuntu2.1 ibus-googlepinyin_0.1.2-2 ibus-pinyin_1.4.0-2ubuntu2 ibus-pinyin-db-open-phrase_1.4.0-2ubuntu2 ibus-table_1.5.0.is.1.5.0-0ubuntu1 ibus-table-wubi_1.4.0.20121008-1 libibus-1.0-5:amd64_1.5.3-6ubuntu2 libusb-0.1-4:amd64_2:0.1.12-23.2ubuntu1 libusb-1.0-0:amd64_2:1.0.16-3 libusbmuxd2_1.0.8-1ubuntu1 libustr-1.0-1:amd64_1.0.4-3ubuntu1 python-ibus_1.5.3-6ubuntu2.1 $ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 $ uname -rm 3.11.0-26-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1393271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
