[Touch-packages] [Bug 1427487] Re: Kubuntu Vivid 1 Beta 15.04 login screen
Please: - Report to https://bugs.kde.org/. - Copy the new report URL here. - Set this bug status back to confirmed. Thank you. ** Package changed: xorg (Ubuntu) = kde4libs (Ubuntu) ** Changed in: kde4libs (Ubuntu) Importance: Undecided = Critical ** Also affects: kdelibs Importance: Undecided Status: New ** Summary changed: - Kubuntu Vivid 1 Beta 15.04 login screen + Shutdown buttons aren't responsible ** Summary changed: - Shutdown buttons aren't responsible + Shutdown buttons aren't unresponding ** Summary changed: - Shutdown buttons aren't unresponding + Shutdown buttons are unresponding ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Confirmed ** Changed in: hundredpapercuts Importance: Undecided = Critical ** Summary changed: - Shutdown buttons are unresponding + Shutdown buttons are unresponsive ** Summary changed: - Shutdown buttons are unresponsive + Shutdown screen is unresponsive ** Changed in: hundredpapercuts Status: Confirmed = Incomplete ** Changed in: kde4libs (Ubuntu) Status: Confirmed = Incomplete ** Tags added: asked-to-upstream -- 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/1427487 Title: Shutdown screen is unresponsive Status in One Hundred Papercuts: Incomplete Status in kdelibs: New Status in kde4libs package in Ubuntu: Incomplete Bug description: Hardware Profile - https://gist.github.com/anonymous/2c98a06b53d1729e2907 When you start up and are at the login menu and you click shutdown, where the timer is counting down, you can not click the shutdown button. It is not responsive. -- The reboot command, at the login window does the same thing. See attachments ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Mar 2 22:24:03 2015 InstallationDate: Installed on 2015-03-03 (0 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224.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/hundredpapercuts/+bug/1427487/+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 1429529] Re: Unsolvable LTSEnablementStack Mesa package dependency
There seems to be quite a number of devel packages that can't be installed or installed via normal means. Maybe can be considered dupes of this bug - https://bugs.launchpad.net/ubuntu/+source/freeglut/+bug/1424466 https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1429464 https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1429623 https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/1429625 likely more could be found... ** Changed in: mesa-lts-utopic (Ubuntu) Status: New = Confirmed ** 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/1429529 Title: Unsolvable LTSEnablementStack Mesa package dependency Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages instead of *lts-utopic pendants as dependencies. This leads to unsolvable conflicts with the already installed *lts-utopic packages. [Test Case] [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install qtbase5-dev The following NEW packages will be installed: libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} qtbase5-dev qtbase5-dev-tools{a} 0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used. The following packages have unmet dependencies: xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libgles2-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libgles2-mesa : Conflicts: libgles2 which is a virtual package. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package. Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is to be installed. libglapi-mesa conflicts due to libgles2-mesa having a dependency on libglapi-mesa (= 10.1.3-0ubuntu0.3). [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install freeglut3-dev The following NEW packages will be installed: freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} 0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded. Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used. The following packages have unmet dependencies: libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 10.1.3-0ubuntu0.3 is to be installed. libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package. Conflicts: libgl1-mesa-glx but 10.1.3-0ubuntu0.3 is to be installed. xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libgl1-mesa-glx (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. [Workaround] [a] $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic [b] $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429529/+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 1429529] Re: Unsolvable LTSEnablementStack Mesa package dependency
To a lesser extent - https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1424491 -- 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/1429529 Title: Unsolvable LTSEnablementStack Mesa package dependency Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages instead of *lts-utopic pendants as dependencies. This leads to unsolvable conflicts with the already installed *lts-utopic packages. [Test Case] [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install qtbase5-dev The following NEW packages will be installed: libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} qtbase5-dev qtbase5-dev-tools{a} 0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used. The following packages have unmet dependencies: xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libgles2-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libgles2-mesa : Conflicts: libgles2 which is a virtual package. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package. Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is to be installed. libglapi-mesa conflicts due to libgles2-mesa having a dependency on libglapi-mesa (= 10.1.3-0ubuntu0.3). [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install freeglut3-dev The following NEW packages will be installed: freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} 0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded. Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used. The following packages have unmet dependencies: libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 10.1.3-0ubuntu0.3 is to be installed. libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package. Conflicts: libgl1-mesa-glx but 10.1.3-0ubuntu0.3 is to be installed. xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libgl1-mesa-glx (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. [Workaround] [a] $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic [b] $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429529/+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 1425891] Re: Xorg radeon freezes if firefix loads big images
I tested the vivid-desktop-amd64.iso of march 6th as a live cd and the firefox loads the big images without a problem. -- 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/1425891 Title: Xorg radeon freezes if firefix loads big images Status in xorg package in Ubuntu: Incomplete Bug description: If I open each of this URLs http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5dsr/downloads/02.jpg http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5ds/downloads/02.jpg in a firefox 36.0 on a Xorg Server of 1.15.1 with a R9 270 and a Ubuntu 14.04.1 AMD64 the desktop freezes. I can only move the mouse pointer, although the the login via SSH is still possible and works fine. By restarting the Xorg Server I can gain control over the local terminal again. This happens with the radeon driver, but not with the fglrx driver. The problem did not manifest itself with other applications. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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: Thu Feb 26 11:19:49 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3050] InstallationDate: Installed on 2014-04-22 (309 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic root=UUID=e0df56bb-b5a5-4b2c-9f89-ce5ff2e3b019 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 26 11:18:17 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1425891/+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 1112466] Re: ffmpeg(libav) cannot encode dvd
Ugh, there has been no response to this for more than two years. Is this still an issue with recent versions of libav? ** Changed in: libav (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1112466 Title: ffmpeg(libav) cannot encode dvd Status in libav package in Ubuntu: Incomplete Bug description: When using k9copy to resize the dvd, the resultant files are not playable. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ffmpeg 6:0.8.5-0ubuntu0.12.10.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Feb 1 13:51:07 2013 InstallationDate: Installed on 2012-12-23 (40 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libav UpgradeStatus: Upgraded to quantal on 2013-02-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1112466/+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 1429627] [NEW] When ibus-pinyin is activated, selecting text in firefox deletes text
Public bug reported: I have tested some other GTK programs, only a combination of Firefox and ibus-pinyin causes this problem. I am on Ubuntu 14.10, and this bug is always reproducible. I think both ibus and firefox has upgraded for several times, but the problem persists. Before I upgrade to 14.10, I did not encounter this problem in 14.04. I upgraded long before using the update manager. ibus-pinyin: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ibus: Installed: 1.5.8-2ubuntu2 Candidate: 1.5.8-2ubuntu2 Version table: *** 1.5.8-2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status firefox: Installed: 36.0+build2-0ubuntu0.14.10.4 Candidate: 36.0+build2-0ubuntu0.14.10.4 Version table: *** 36.0+build2-0ubuntu0.14.10.4 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu/ utopic-security/main amd64 Packages 100 /var/lib/dpkg/status 33.0+build2-0ubuntu0.14.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5 Uname: Linux 3.16.0-31-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 8 14:07:46 2015 InstallationDate: Installed on 2014-10-28 (130 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: ibus UpgradeStatus: Upgraded to utopic on 2015-01-30 (37 days ago) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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/1429627 Title: When ibus-pinyin is activated, selecting text in firefox deletes text Status in ibus package in Ubuntu: New Bug description: I have tested some other GTK programs, only a combination of Firefox and ibus-pinyin causes this problem. I am on Ubuntu 14.10, and this bug is always reproducible. I think both ibus and firefox has upgraded for several times, but the problem persists. Before I upgrade to 14.10, I did not encounter this problem in 14.04. I upgraded long before using the update manager. ibus-pinyin: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ibus: Installed: 1.5.8-2ubuntu2 Candidate: 1.5.8-2ubuntu2 Version table: *** 1.5.8-2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status firefox: Installed: 36.0+build2-0ubuntu0.14.10.4 Candidate: 36.0+build2-0ubuntu0.14.10.4 Version table: *** 36.0+build2-0ubuntu0.14.10.4 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu/ utopic-security/main amd64 Packages 100 /var/lib/dpkg/status 33.0+build2-0ubuntu0.14.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5 Uname: Linux 3.16.0-31-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 8 14:07:46 2015 InstallationDate: Installed on 2014-10-28 (130 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: ibus UpgradeStatus: Upgraded to utopic on 2015-01-30 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1429627/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
paolo, do you have the udisks package installed? If so, see above. If not, please file a new bug with the output of sudo udevadm test /block/mmcblk0rpmb. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1333140 Title: Fix udev rules to consider mmc rpmb partitions Status in systemd package in Ubuntu: Fix Released Status in udev package in Ubuntu: Invalid Status in udisks package in Ubuntu: Triaged Status in udev source package in Precise: Triaged Status in udisks source package in Precise: Confirmed Status in systemd source package in Trusty: Fix Committed Status in udisks source package in Trusty: Confirmed Bug description: As per JEDEC 4.5 spec for eMMC devices, There is a new partitions as part of eMMC storage devices it self. (Further details please refer eMMC spec) *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions with mmcblkXrpmb if device expresses it support of RPMB. Issues observed: issue 1: RPMB (Replay Protected Memory Block), A signed access to a Replay Protected Memory Block is provided. This function provides means for the system to store data to the specific memory area in an authenticated and replay protected manner. In that case, any read/write access to this partition device will report errors. issue 2: The by-path, line is wrongly mapping to platform-sdhci-tegra.1 - mmcblk2rpmb were as it should be platform-sdhci-tegra.1 - mmcblk2 ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 - ../../mmcblk2rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 - ../../mmcblk2p1 lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 - ../../mmcblk1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 - ../../mmcblk1p1 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 - ../../mmcblk0rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 - ../../mmcblk0p1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 - ../../mmcblk0p2 We have locally resolved in our platform in this file 60-persistent- storage.rules For issue 1: (with this rule) # skip block read for partitions of type rpmb KERNEL==mmcblk[0-9]rpmb, SUBSYSTEM==block, GOTO=persistent_storage_end For issue 2: ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL==mmcblk[0-9]rpmb, SYMLINK+=disk/by-path/$env{ID_PATH}-rpmb ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL!=mmcblk[0-9]rpmb, SYMLINK+=disk/by-path/$env{ID_PATH} Please consider this issues fix in next udev release . SRU INFO: This is mostly an issue with running backported kernels on 12.04 and 14.04. There is no test case which would reproduce this on arbitrary hardware, but there are several reporters which are in a position to verify a proposed update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 1429529] Re: Unsolvable LTSEnablementStack Mesa package dependency
And possibly - https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1428972 -- 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/1429529 Title: Unsolvable LTSEnablementStack Mesa package dependency Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages instead of *lts-utopic pendants as dependencies. This leads to unsolvable conflicts with the already installed *lts-utopic packages. [Test Case] [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install qtbase5-dev The following NEW packages will be installed: libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} qtbase5-dev qtbase5-dev-tools{a} 0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used. The following packages have unmet dependencies: xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libgles2-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libgles2-mesa : Conflicts: libgles2 which is a virtual package. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package. Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is to be installed. libglapi-mesa conflicts due to libgles2-mesa having a dependency on libglapi-mesa (= 10.1.3-0ubuntu0.3). [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install freeglut3-dev The following NEW packages will be installed: freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} 0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded. Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used. The following packages have unmet dependencies: libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 10.1.3-0ubuntu0.3 is to be installed. libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package. Conflicts: libgl1-mesa-glx but 10.1.3-0ubuntu0.3 is to be installed. xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libgl1-mesa-glx (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. [Workaround] [a] $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic [b] $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429529/+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 1427672] Re: System doesn't power off when shutting down
Ah, thanks. I misunderstood you then. Can you say with certain confidence that the kernel/graphics driver crash (that's what it seems to be) only happens with systemd, but not with upstart? Perhaps there's some difference in how we shut down X.org/lightdm under either. Can you reliably switch users or just start/stop your session under upstart and systemd? (The latter is the part that causes graphics driver/kernel crashes on my machine occasionally, but it doesn't seem init specific) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1427672 Title: System doesn't power off when shutting down Status in systemd package in Ubuntu: Confirmed Bug description: 1. Open the session indicator (cog in top-right) 2. Shut Down... 3. Shut Down 4. The monitors go blank 5. The system doesn't power off (waited 5 minutes) Things which do work - poweroff -f - Changing to a debug shell and shutting down using login1.Manager PowerOff I can't use the system-shutdown/ functionality since shutdown doesn't get that far. I can't SSH in since network is down. I can't switch VT when it's in this state so I'm not able to interact with the system. I can't see anything on the monitors since they are turned off. Any tips on how to get useful debugging information? I'll attach journalctl from the previous boot but the last message is the journal shutting down so it's not that useful I don't think. Also syslog. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 12:57:33 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX 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.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1427672/+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 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1274115 Title: snd_pcm_avail() returned a value that is exceptionally large Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sometimese sound begins stutter while listen to music or watching youtube. In syslog I see: Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 866944 bytes (4914 ms). Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. I'm using Kubuntu 13.10 $ uname -a Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ kde4-config --version Qt: 4.8.4 KDE Development Platform: 4.12.0 kde4-config: 1.0 $ pulseaudio --version pulseaudio 4.0 $ alsactl --version alsactl version 1.0.27.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+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 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large
I also have similar issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1274115 Title: snd_pcm_avail() returned a value that is exceptionally large Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sometimese sound begins stutter while listen to music or watching youtube. In syslog I see: Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 866944 bytes (4914 ms). Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. I'm using Kubuntu 13.10 $ uname -a Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ kde4-config --version Qt: 4.8.4 KDE Development Platform: 4.12.0 kde4-config: 1.0 $ pulseaudio --version pulseaudio 4.0 $ alsactl --version alsactl version 1.0.27.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+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 1429636] Re: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value()
*** This bug is a duplicate of bug 1428711 *** https://bugs.launchpad.net/bugs/1428711 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1428711, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429636/+attachment/4338206/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429636/+attachment/4338208/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429636/+attachment/4338210/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429636/+attachment/4338211/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429636/+attachment/4338212/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429636/+attachment/4338213/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429636/+attachment/4338214/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1428711 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1429636 Title: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value() Status in indicator-sound package in Ubuntu: New Bug description: Happened on login. Sound indicator is there, but is non working (every menu item is greyed out). ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 8 20:04:14 2015 EcryptfsInUse: Yes ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2014-05-05 (307 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service SegvAnalysis: Segfault happened at: 0x7f2905480b80:mov0x20(%rdi),%eax PC (0x7f2905480b80) ok source 0x20(%rdi) (0x0020) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-sound StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () accounts_service_user_set_player () _start () Title: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: Upgraded to vivid on 2015-03-06 (1 days ago) UserGroups: bumblebee cdrom debian-tor dip juner libvirtd lpadmin plugdev sambashare sudo vboxusers wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1429636/+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 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid
I'm not able to confirm this in krillin 14.10 r252. The strange thing is wasn't any work done on the brightness controls in the last two months, and there's nothing in the changelog indicating anything related to it landed since this bug was reported. Michael, Saviq, are either of you still seeing this bug? ** Changed in: indicator-power (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1411643 Title: Automatic brightness toggle switch missing on krillin/vivid Status in indicator-power package in Ubuntu: Incomplete Bug description: I noticed that on my krillin device with devel-propsed (r70), the automatic display brightness toggle switch is missing in the battery indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1424460] Re: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- 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/1424460 Title: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Confirmed Bug description: trying to install updates on ubuntu 14.10, reports package installation failed ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Sat Feb 21 21:10:43 2015 DuplicateSignature: package:lightdm:1.12.2-0ubuntu1: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-12 (102 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: lightdm Title: package lightdm 1.12.2-0ubuntu1 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/lightdm/+bug/1424460/+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 1424460] Re: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This happend after adding proposed updates to Ubuntu 14.10 on my Ugoos UT3 RK3288 device. -- 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/1424460 Title: package lightdm 1.12.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: Confirmed Bug description: trying to install updates on ubuntu 14.10, reports package installation failed ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Sat Feb 21 21:10:43 2015 DuplicateSignature: package:lightdm:1.12.2-0ubuntu1: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-12 (102 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: lightdm Title: package lightdm 1.12.2-0ubuntu1 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/lightdm/+bug/1424460/+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 1429472] Re: Kubuntu Vivid 1 Beta 15.04 installation: Progress bar is missing german translation
Thanks for taking your time to report this issue and help making Ubuntu better. I believe the string in question is not part of ubiquity (the Ubuntu installer) itself, but rather a program ubuquity uses when installing the packages for setting up the installed system. Digging a bit, I was able to find this string [1] which seems to be the one in question. However, this seems to have been translated a while back, so I'm not sure why the original would still be shown. [1] https://translations.launchpad.net/ubuntu/vivid/+source/aptdaemon/+pots/aptdaemon/de/196/+translate ** Package changed: xorg (Ubuntu) = aptdaemon (Ubuntu) ** Changed in: aptdaemon (Ubuntu) Status: New = Confirmed ** Tags added: vivid ** Also affects: ubuntu-translations Importance: Undecided Status: New -- 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/1429472 Title: Kubuntu Vivid 1 Beta 15.04 installation: Progress bar is missing german translation Status in Ubuntu Translations: New Status in aptdaemon package in Ubuntu: Confirmed Bug description: At some point of the installation the progress bar at the bottom of the screen is missing german translation. Screenshot attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1429472/+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 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
@ Norbert I'm unsuscribing the Ubuntu Bug Control team from this bug. If you think there's a good reason for the team to be subscribed, please email me. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The G Library - GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: [Impact] * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. 2a.2. Double click on 'test.odt' 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. 3. Get error message from LibreOffice: The file 'test.odt' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. The corruption could be the result of document manipulation or of structural document damage due to data transmission. We recommend that you do not trust the content of the repaired document. Execution of macros is disabled for this document. Should LibreOffice repair the file? Yes No 4a. If I click 'Yes', the file is opened, but the title of the document is Untitled 1 (repaired document), not original name. 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: The file 'test.odt' could not be repaired and therefore cannot be opened. OK I click 'OK' here, the next window LibreOffice 4.4.1.2 is opened with text: General Error. General input/output error. OK If I click OK here - no files are opened. While step 3 gvfsd-smb process eats CPU then terminates with error. This error is caused by bug in Glib (wrong type conversion in macros). [Regression Potential] * This functionality is essential. Please fix this bug. I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. * The patch has two lines (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) and well-tested at upstream. * This bug may cause potential loss of data. [Other Info] * Corresponding links to LibO bugs are: https://bugs.freedesktop.org/show_bug.cgi?id=67527 https://bugs.documentfoundation.org/show_bug.cgi?id=72337 [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+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 464442] Re: alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: -4496252 bytes (-25488 ms).
Looks like it pretty old but also affects me. Some details: Lenovo G50-45 laptop. 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Sound delayed and some echo played when I changes sound volume. Only reboot helps to fix it but only for some time. Usually sound breaks when I change volume level using Fn keys. Let me know if you need additional details to investigate. Thanks. -- 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/464442 Title: alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: -4496252 bytes (-25488 ms). Status in The Linux Kernel: New Status in alsa-driver package in Ubuntu: Incomplete Bug description: Audio hanged while using espeak TTS to read a large chuck of text. While playing other parallel audio notifications. The quality of audio is proper with lot of static and abberrations E: alsa-util.c: avail_min: 352 E: alsa-util.c: period_event : 1 E: alsa-util.c: start_threshold : -1 E: alsa-util.c: stop_threshold : 1845493760 E: alsa-util.c: silence_threshold: 0 E: alsa-util.c: silence_size : 0 E: alsa-util.c: boundary : 1845493760 E: alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel' device 0 subdevice 0 E: alsa-util.c: Its setup is: E: alsa-util.c: stream : PLAYBACK E: alsa-util.c: access : MMAP_INTERLEAVED E: alsa-util.c: format : S16_LE E: alsa-util.c: subformat: STD E: alsa-util.c: channels : 2 E: alsa-util.c: rate : 44100 E: alsa-util.c: exact rate : 44100 (44100/1) E: alsa-util.c: msbits : 16 E: alsa-util.c: buffer_size : 3520 E: alsa-util.c: period_size : 352 E: alsa-util.c: period_time : 7981 E: alsa-util.c: tstamp_mode : ENABLE E: alsa-util.c: period_step : 1 E: alsa-util.c: avail_min: 352 E: alsa-util.c: period_event : 1 E: alsa-util.c: start_threshold : -1 E: alsa-util.c: stop_threshold : 1845493760 E: alsa-util.c: silence_threshold: 0 E: alsa-util.c: silence_size : 0 E: alsa-util.c: boundary : 1845493760 E: alsa-util.c: appl_ptr : 18557793 E: alsa-util.c: hw_ptr : 19713488 E: alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: -4496252 bytes (-25488 ms). E: alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. E: alsa-util.c: snd_pcm_dump(): E: alsa-util.c: Soft volume PCM E: alsa-util.c: Control: PCM Playback Volume E: alsa-util.c: min_dB: -51 E: alsa-util.c: max_dB: 0 E: alsa-util.c: resolution: 256 E: alsa-util.c: Its setup is: E: alsa-util.c: stream : PLAYBACK E: alsa-util.c: access : MMAP_INTERLEAVED E: alsa-util.c: format : S16_LE E: alsa-util.c: subformat: STD E: alsa-util.c: channels : 2 E: alsa-util.c: rate : 44100 E: alsa-util.c: exact rate : 44100 (44100/1) E: alsa-util.c: msbits : 16 E: alsa-util.c: buffer_size : 3520 E: alsa-util.c: period_size : 352 E: alsa-util.c: period_time : 7981 E: alsa-util.c: tstamp_mode : ENABLE E: alsa-util.c: period_step : 1 E: alsa-util.c: avail_min: 352 E: alsa-util.c: period_event : 1 E: alsa-util.c: start_threshold : -1 E: alsa-util.c: stop_threshold : 1845493760 E: alsa-util.c: silence_threshold: 0 E: alsa-util.c: silence_size : 0 E: alsa-util.c: boundary : 1845493760 E: alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel' device 0 subdevice 0 E: alsa-util.c: Its setup is: E: alsa-util.c: stream : PLAYBACK E: alsa-util.c: access : MMAP_INTERLEAVED E: alsa-util.c: format : S16_LE E: alsa-util.c: subformat: STD E: alsa-util.c: channels : 2 E: alsa-util.c: rate : 44100 E: alsa-util.c: exact rate : 44100 (44100/1) E: alsa-util.c: msbits : 16 E: alsa-util.c: buffer_size : 3520 E: alsa-util.c: period_size : 352 E: alsa-util.c: period_time : 7981 E: alsa-util.c: tstamp_mode : ENABLE E: alsa-util.c: period_step : 1 E: alsa-util.c: avail_min: 352 E: alsa-util.c: period_event : 1 E: alsa-util.c: start_threshold : -1 E: alsa-util.c: stop_threshold : 1845493760 E: alsa-util.c: silence_threshold: 0 E: alsa-util.c: silence_size : 0 E: alsa-util.c: boundary : 1845493760 E: alsa-util.c: appl_ptr : 18589473 E: alsa-util.c: hw_ptr : 19713536 I: alsa-sink.c: Underrun! ProblemType: Bug Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS
[Touch-packages] [Bug 1194550] Re: [gallery] Gallery should not be fullscreen on thumbnail view
** Changed in: gallery-app (Ubuntu) Status: Triaged = Fix Released ** Changed in: platform-api (Ubuntu) Status: New = Fix Released ** Changed in: qtubuntu Status: In Progress = Fix Released ** Changed in: platform-api Status: In Progress = Fix Released ** Changed in: ubuntu-ux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1194550 Title: [gallery] Gallery should not be fullscreen on thumbnail view Status in Platform API: Fix Released Status in QT Ubuntu: Fix Released Status in Ubuntu UX bugs: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in platform-api package in Ubuntu: Fix Released Status in qtubuntu package in Ubuntu: Fix Released Bug description: As indicated in the design screenshots (http://design.ubuntu.com/apps /global-patterns/content-views#full-screen-view), the gallery app should only enter fullscreen mode (hiding the menu bar) when displaying an image, not when on the thumbnail overview. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1194550/+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 1428711] Re: indicator-sound-service crashed with SIGSEGV in g_variant_is_trusted()
Yep, it looks like we're getting a player with a NULL state somehow, which is crashing when we try to convert that into a variant for sending over the bus. (1) we should sanitize our inputs better, ie modify the state property setter to disallow NULLs. More importantly, (2) we need to figure out where this NULL state is coming from. ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1428711 Title: indicator-sound-service crashed with SIGSEGV in g_variant_is_trusted() Status in indicator-sound package in Ubuntu: Confirmed Bug description: Crash seemed to happen when I opened both rhythmbox and banshee at the same time. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 5 10:50:51 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2011-07-08 (1336 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR=set SegvAnalysis: Segfault happened at: 0x7f072b0e3b80:mov0x20(%rdi),%eax PC (0x7f072b0e3b80) ok source 0x20(%rdi) (0x0020) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-sound StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () accounts_service_user_set_player () _start () Title: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: Upgraded to vivid on 2015-01-19 (45 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1428711/+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 1425891] Re: Xorg radeon freezes if firefix loads big images
Christoph, have you tried upgrading your install to the Utopic enablement stack as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack to see if the issue is resolved? -- 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/1425891 Title: Xorg radeon freezes if firefix loads big images Status in xorg package in Ubuntu: Incomplete Bug description: If I open each of this URLs http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5dsr/downloads/02.jpg http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5ds/downloads/02.jpg in a firefox 36.0 on a Xorg Server of 1.15.1 with a R9 270 and a Ubuntu 14.04.1 AMD64 the desktop freezes. I can only move the mouse pointer, although the the login via SSH is still possible and works fine. By restarting the Xorg Server I can gain control over the local terminal again. This happens with the radeon driver, but not with the fglrx driver. The problem did not manifest itself with other applications. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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: Thu Feb 26 11:19:49 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3050] InstallationDate: Installed on 2014-04-22 (309 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic root=UUID=e0df56bb-b5a5-4b2c-9f89-ce5ff2e3b019 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 26 11:18:17 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1425891/+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 215341] Re: Add some visual feedback when hover mouse over menubar
** Changed in: gtk Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/215341 Title: Add some visual feedback when hover mouse over menubar Status in GTK+ GUI Toolkit: Fix Released Status in gtk+2.0 package in Ubuntu: Triaged Bug description: Binary package hint: human-theme Add some (subtle) visual feedback that appears when you hover the mouse over a menu in the menubar. I think this would improve usability, and make the system feel more responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/215341/+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 1429641] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1380982 *** https://bugs.launchpad.net/bugs/1380982 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1380982, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429641/+attachment/4338228/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429641/+attachment/4338230/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429641/+attachment/4338231/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429641/+attachment/4338232/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429641/+attachment/4338233/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429641/+attachment/4338234/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429641/+attachment/4338235/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1380982 ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- 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/1429641 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: New Bug description: Occurred in Xubuntu 15.04 ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: ibus 1.5.9-1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Sun Mar 8 16:36:56 2015 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2015-01-11 (56 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_BR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to vivid on 2015-02-18 (17 days ago) UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1429641/+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 1426942] Re: Kubuntu Vivid - unable to display Gujarati Text
There's Qt 5.4.1 brewing, but since it's currently blocked by a bug I'll include this in another 5.4.0 qtbase upload if it seems the blocker bug isn't seeing a fix soon. ** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: qtbase-opensource-src (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1426942 Title: Kubuntu Vivid - unable to display Gujarati Text Status in qtbase-opensource-src package in Ubuntu: Triaged Bug description: Applications built with qt5/KDE Framework 5 on Kubuntu Vivid Beta 1 can no longer render Gujarati script. This is probably due to https://bugreports.qt.io/browse/QTBUG-44568 My Platform: Kubuntu Vivid Beta 1 Packages affected: Any package built with Qt5 5.4 (e.g. konsole, Muon Package Manager etc) Expected: Render Gujarati script correctly (as was the case in Kubuntu versions prior to 15.04) Actual Results: Gujarati glyphs are displayed as squares The above Qt bug is scheduled to be fixed in Qt 5.5. If Kubuntu Vivid is going to ship with Qt 5.4, will it be possible to include a patched Qt5.4 to resolve this specific bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1426942/+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 1429644] [NEW] [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted
Public bug reported: sound quality poor. distoted sound ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaditya 15448 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 9 01:58:35 2015 InstallationDate: Installed on 2015-03-06 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI successful Symptom_Card: Creative Sound Blaster AudioPCI64V, AudioPCI128 - Ensoniq AudioPCI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or overdriven sound Title: [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2015-03-07T12:55:40.634974 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1429644 Title: [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted Status in pulseaudio package in Ubuntu: New Bug description: sound quality poor. distoted sound ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaditya 15448 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 9 01:58:35 2015 InstallationDate: Installed on 2015-03-06 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI successful Symptom_Card: Creative Sound Blaster AudioPCI64V, AudioPCI128 - Ensoniq AudioPCI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or overdriven sound Title: [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2015-03-07T12:55:40.634974 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1429644/+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 1414516] Re: Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a system/laptop battery
** Changed in: upower (Ubuntu) Importance: Undecided = Medium -- 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/1414516 Title: Ubuntu 14.10 sees logitech k810 bluetooth keyboard battery as a system/laptop battery Status in upower package in Ubuntu: Confirmed Bug description: This is a HP desktop computer using a IOGEAR USB Bluetooth dongle. When I enable the logitech k810 keyboard the OS behaves like it's on battery power. Inside the power management GUI under Power Settings the What to do when power is critically low selection is set to Power Off, and I can't select another option. Here's the output of upower -d rob@hp-ubuntu:~$ upower -d Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20o92o1bo18_battery native-path: hid-00:1f:20:92:1b:18-battery model:Logitech K810 power supply: no updated: Sun 25 Jan 2015 07:02:46 PM CST (5 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging energy: 0 Wh energy-empty:0 Wh energy-full: 0 Wh energy-full-design: 0 Wh energy-rate: 0 W percentage: 85% capacity:100% Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: no on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: no is-docked: no ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upower 0.9.23-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 25 18:57:04 2015 InstallationDate: Installed on 2015-01-14 (11 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1414516/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
On my HP stream 11 with xubuntu 14.04, the 204.5ubuntu20.11 did not solve the issue. (I do not know how to tag it as not working). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1333140 Title: Fix udev rules to consider mmc rpmb partitions Status in systemd package in Ubuntu: Fix Released Status in udev package in Ubuntu: Invalid Status in udisks package in Ubuntu: Triaged Status in udev source package in Precise: Triaged Status in udisks source package in Precise: Confirmed Status in systemd source package in Trusty: Fix Committed Status in udisks source package in Trusty: Confirmed Bug description: As per JEDEC 4.5 spec for eMMC devices, There is a new partitions as part of eMMC storage devices it self. (Further details please refer eMMC spec) *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions with mmcblkXrpmb if device expresses it support of RPMB. Issues observed: issue 1: RPMB (Replay Protected Memory Block), A signed access to a Replay Protected Memory Block is provided. This function provides means for the system to store data to the specific memory area in an authenticated and replay protected manner. In that case, any read/write access to this partition device will report errors. issue 2: The by-path, line is wrongly mapping to platform-sdhci-tegra.1 - mmcblk2rpmb were as it should be platform-sdhci-tegra.1 - mmcblk2 ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 - ../../mmcblk2rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 - ../../mmcblk2p1 lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 - ../../mmcblk1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 - ../../mmcblk1p1 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 - ../../mmcblk0rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 - ../../mmcblk0p1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 - ../../mmcblk0p2 We have locally resolved in our platform in this file 60-persistent- storage.rules For issue 1: (with this rule) # skip block read for partitions of type rpmb KERNEL==mmcblk[0-9]rpmb, SUBSYSTEM==block, GOTO=persistent_storage_end For issue 2: ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL==mmcblk[0-9]rpmb, SYMLINK+=disk/by-path/$env{ID_PATH}-rpmb ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL!=mmcblk[0-9]rpmb, SYMLINK+=disk/by-path/$env{ID_PATH} Please consider this issues fix in next udev release . SRU INFO: This is mostly an issue with running backported kernels on 12.04 and 14.04. There is no test case which would reproduce this on arbitrary hardware, but there are several reporters which are in a position to verify a proposed update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 215341] Re: Add some visual feedback when hover mouse over menubar
** Also affects: human-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/215341 Title: Add some visual feedback when hover mouse over menubar Status in GTK+ GUI Toolkit: Fix Released Status in gtk+2.0 package in Ubuntu: Triaged Status in human-theme package in Ubuntu: New Bug description: Binary package hint: human-theme Add some (subtle) visual feedback that appears when you hover the mouse over a menu in the menubar. I think this would improve usability, and make the system feel more responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/215341/+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 1427487] Re: Kubuntu Vivid 1 Beta 15.04 login screen
@ Mustang When reporting a bug try to guess what the package is, instead of reporting by default to xorg. -- 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/1427487 Title: Kubuntu Vivid 1 Beta 15.04 login screen Status in xorg package in Ubuntu: Confirmed Bug description: Hardware Profile - https://gist.github.com/anonymous/2c98a06b53d1729e2907 When you start up and are at the login menu and you click shutdown, where the timer is counting down, you can not click the shutdown button. It is not responsive. -- The reboot command, at the login window does the same thing. See attachments ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Mar 2 22:24:03 2015 InstallationDate: Installed on 2015-03-03 (0 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224.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/1427487/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Hello guys! The bug seems to be fixed on my PC. There were lots of changes since the last check, but the last I did was disabling ACPI HPET Table in BIOS. Also I got rid of indicators. Other BIOS settings: suspend to ram - auto check ready bit - auto away mode support - disabled restore on AC - power off Ring-in power on - disabled PCI devices power on - disabled PS/2 Keyboard power on - disabled RTC alarm - by OS ACPI HPET Table - disabled -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: Invalid Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1323837] Re: Sim toolkit is not available on UT
up on this bug. I have been in holidays abroad again and could not get any network connection. -- 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/1323837 Title: Sim toolkit is not available on UT Status in ofono package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ /SIM-Toolkit While a lot of those addons are completely crap and useless, the SIm toolkit is sometimes used by some phone provider to set your sim card to roaming mode when you are abroad which makes it a must have. For the moment i need to borrow a second phone put my sim card in it, go to the Sim-toolkit, enable my sim card for roaming and put the sim card back in my UT to get my phone working while i am abroad. I need to do the same when i go back home. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1323837/+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 1427640] Re: indicator-sound-service crashed with signal 5 in main()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1427640 Title: indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Bug description: N/A ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 2 18:45:39 2015 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2014-12-08 (84 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha i386 (20141208) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1427640/+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 1429548] [NEW] The Today scope has a wrong italian translation
Public bug reported: In the Today scope (Oggi in italian) there are wrong italian translations. What in english is holiday, in Italy is festività - you can't call it vacanza (singular) or vacanze (plural). Vacanze is similar to holiday, but in this particular context festività is the right translation. I'm using Aquaris e4.5 with Ubuntu 14.10 (r19). PS: I'm member of Ubuntu italian translators, but I can't find where Today scope translations' are. ** Affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: Vacanza5.png https://bugs.launchpad.net/bugs/1429548/+attachment/4337809/+files/Vacanza5.png -- 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/1429548 Title: The Today scope has a wrong italian translation Status in unity-scopes-shell package in Ubuntu: New Bug description: In the Today scope (Oggi in italian) there are wrong italian translations. What in english is holiday, in Italy is festività - you can't call it vacanza (singular) or vacanze (plural). Vacanze is similar to holiday, but in this particular context festività is the right translation. I'm using Aquaris e4.5 with Ubuntu 14.10 (r19). PS: I'm member of Ubuntu italian translators, but I can't find where Today scope translations' are. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1429548/+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 1429143] Re: Slow shutdown after booting with systemd
Can you please boot without quiet and splash (in the grub menu, edit the default boot entry), then shut down. There should be a line like waiting for job to shut down and some asterisks. Which is that? If you don't get such a thing, please have a look at Debugging boot/shutdown problems in /usr/share/doc/systemd/README.Debian . Thanks! ** Changed in: systemd (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429143 Title: Slow shutdown after booting with systemd Status in systemd package in Ubuntu: Incomplete Bug description: When running vivid booted with systemd kernel, shutdown consistently takes around 90 seconds. With the normal kernel it is about 15 seconds. In the log, shutdown started (from the cog) at 13:50:20, Mar 6th. The purple Ubuntu screen with dots appears after a few seconds and then sits there. It actually powered off at 13:51:55. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-7-generic 3.19.0-7.7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colinl 1948 F pulseaudio /dev/snd/controlC1: colinl 1948 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 6 13:54:29 2015 InstallationDate: Installed on 2014-10-21 (135 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 init=/lib/systemd/systemd RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429143/+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 1429544] Re: systemd-logind crashed with SIGABRT in session_start_scope()
Sorry, I have rebooted many times since then. (F**ed NVIDIA drivers) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429544 Title: systemd-logind crashed with SIGABRT in session_start_scope() Status in systemd package in Ubuntu: Incomplete Bug description: . ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Sun Mar 8 10:13:11 2015 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2014-11-28 (99 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 2447MU0 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=!Windows 2012 splash Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/graphical.target → /lib/systemd/system/graphical.target.d/xdiagnose.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT UpgradeStatus: Upgraded to vivid on 2015-03-08 (0 days ago) UserGroups: dmi.bios.date: 08/22/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA0WW (2.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 2447MU0 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA0WW(2.60):bd08/22/2014:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2447MU0 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429544/+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 1429545] Re: systemd-logind crashed with SIGABRT
*** This bug is a duplicate of bug 1429544 *** https://bugs.launchpad.net/bugs/1429544 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1429544, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429545/+attachment/4337761/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429545/+attachment/4337764/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429545/+attachment/4337769/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429545/+attachment/4337771/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429545/+attachment/4337772/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429545/+attachment/4337773/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429545/+attachment/4337774/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1429544 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429545 Title: systemd-logind crashed with SIGABRT Status in systemd package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Sun Mar 8 10:13:11 2015 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2014-11-28 (99 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 2447MU0 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=!Windows 2012 splash Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/graphical.target → /lib/systemd/system/graphical.target.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT UpgradeStatus: Upgraded to vivid on 2015-03-08 (0 days ago) UserGroups: dmi.bios.date: 08/22/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA0WW (2.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 2447MU0 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA0WW(2.60):bd08/22/2014:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2447MU0 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429545/+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 1429529] [NEW] Unsolvable LTSEnablementStack Mesa package dependency
Public bug reported: [Description] On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages instead of *lts-utopic pendants as dependencies. This leads to unsolvable conflicts with the already installed *lts-utopic packages. [Test Case] [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install qtbase5-dev The following NEW packages will be installed: libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} qtbase5-dev qtbase5-dev-tools{a} 0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used. The following packages have unmet dependencies: xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libgles2-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libgles2-mesa : Conflicts: libgles2 which is a virtual package. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package. Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is to be installed. libglapi-mesa conflicts due to libgles2-mesa having a dependency on libglapi-mesa (= 10.1.3-0ubuntu0.3). [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install freeglut3-dev The following NEW packages will be installed: freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} 0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded. Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used. The following packages have unmet dependencies: libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 10.1.3-0ubuntu0.3 is to be installed. libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package. Conflicts: libgl1-mesa-glx but 10.1.3-0ubuntu0.3 is to be installed. xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libgl1-mesa-glx (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. [Workaround] [a] $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic [b] $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mesa-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 trusty ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1429529 Title: Unsolvable LTSEnablementStack Mesa package dependency Status in mesa package in Ubuntu: New Status in mesa-lts-utopic package in Ubuntu: New Bug description: [Description] On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages instead of *lts-utopic pendants as dependencies. This leads to unsolvable conflicts with the already installed *lts-utopic packages. [Test Case] [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) $ sudo aptitude install qtbase5-dev The following NEW packages will be installed: libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} qtbase5-dev qtbase5-dev-tools{a} 0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used. The following packages have unmet
[Touch-packages] [Bug 1422125] Re: ntpdate[634]: no servers can be used, exiting
Warning: The system is configured to read the RTC time in the local time zone. This mode can not be fully supported. It will create various problems with time zone changes and daylight saving time adjustments. The RTC time is never updated, it relies on external facilities to maintain it. If at all possible, use RTC in UTC by calling 'timedatectl set-local-rtc 0'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1422125 Title: ntpdate[634]: no servers can be used, exiting Status in ntp package in Ubuntu: New Bug description: desktop booted with systemd-sysv from journalctl: networking[439]: ...done. systemd[1]: Started LSB: Raise network interfaces.. systemd[1]: Stopped LSB: Start NTP daemon. apparmor_parser[594]: audit-1400 apparmor=STATUS operation=profile_load profile=unconfined name=/usr/lib/lightdm/lightdm-guest-session pid=594 comm=apparmor_pa apparmor_parser[594]: audit-1400 apparmor=STATUS operation=profile_load profile=unconfined name=chromium pid=594 comm=apparmor_parser kernel: audit: type=1400 audit(1423979133.654:2): apparmor=STATUS operation=profile_load profile=unconfined name=/usr/lib/lightdm/lightdm-guest-session pid=594 co kernel: audit: type=1400 audit(1423979133.654:3): apparmor=STATUS operation=profile_load profile=unconfined name=chromium pid=594 comm=apparmor_parser ntpdate[634]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) ntpdate[634]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) ntpdate[634]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) ntpdate[634]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) ntpdate[634]: Can't find host ntp.ubuntu.com: Name or service not known (-2) ntpdate[634]: no servers can be used, exiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ntpdate 1:4.2.6.p5+dfsg-3ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Sun Feb 15 15:38:14 2015 NtpStatus: ntpq: read: Connection refused SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1422125/+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 1429354] Re: Systemd takes very long to boot with error in swap mounting and nvidia persistenced
Can you please file a bug against nvidia-graphics-drivers-346 for the persistenced issue? ** Summary changed: - Systemd takes very long to boot with error in swap mounting and nvidia persistenced + Systemd takes very long to boot with error in swap mounting -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429354 Title: Systemd takes very long to boot with error in swap mounting Status in systemd package in Ubuntu: Incomplete Bug description: My system boots almost instantly with upstart. Today i tried booting with systemd via the additional grub option. However, with systemd it takes really long to boot but – so long that i forced a reboot once because i thought i got stuck. Looking in to boot journal, i found the following error concerning the swap: Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, code=exited status=255 Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition. Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state. And this concerning nvidia-persistenced Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433) Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 116 has read and write permissions for thos Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced I checked that /dev/sda3 exists and is a swap partition and i check for the /dev/nvidia files: $ ls -Alst /dev/nvidia0 0 crw-rw-rw- 1 root root 195, 0 Mär 7 09:29 /dev/nvidia0 However, the interesting part is here, where nothing seems to happen for a minute: (see the timestamps): Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization. Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 messages. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start timed out. Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 messages. Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap. Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes. Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start failed with result 'timeout'. Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 09:31:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-05 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7 init=/lib/systemd/systemd systemd.debugshell SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-23 (11 days ago) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H97 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name:
[Touch-packages] [Bug 1429354] Re: Systemd takes very long to boot with error in swap mounting and nvidia persistenced
You'll get the 90 second timeout with waiting for dev-disk-by\x2duuid- 0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device (which presumably is the one containing swap), then your system should boot without swap. Mär 07 09:28:00 darw1n swapon[418]: swapon: /dev/sda3: Swap-Header konnte nicht gelesen werden This indicates that your /etc/fstab contains an invalid swap partition entry, as you now use an encrypted swap. Your udev database has no device with the above UUID, and /dev/sda3 has no file system on it at all, so it'll indeed wait for that in vain. It might be the UUID of the /dev/mapper/cryptswap1 device. Can you please attach your /etc/fstab and /etc/crypttab files? (They shouldn't contain keys, just the names of the key files; but please do have a look at them, and feel free to obfuscate anything which looks like a password/key with X or so). Thanks! ** Changed in: systemd (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429354 Title: Systemd takes very long to boot with error in swap mounting Status in systemd package in Ubuntu: Incomplete Bug description: My system boots almost instantly with upstart. Today i tried booting with systemd via the additional grub option. However, with systemd it takes really long to boot but – so long that i forced a reboot once because i thought i got stuck. Looking in to boot journal, i found the following error concerning the swap: Mär 07 09:28:00 darw1n systemd[1]: dev-sda3.swap swap process exited, code=exited status=255 Mär 07 09:28:00 darw1n systemd[1]: Failed to activate swap Swap Partition. Mär 07 09:28:00 darw1n systemd[1]: Unit dev-sda3.swap entered failed state. And this concerning nvidia-persistenced Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Started (433) Mär 07 09:28:00 darw1n nvidia-persistenced[433]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 116 has read and write permissions for thos Mär 07 09:28:00 darw1n nvidia-persistenced[433]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced I checked that /dev/sda3 exists and is a swap partition and i check for the /dev/nvidia files: $ ls -Alst /dev/nvidia0 0 crw-rw-rw- 1 root root 195, 0 Mär 7 09:29 /dev/nvidia0 However, the interesting part is here, where nothing seems to happen for a minute: (see the timestamps): Mär 07 09:28:01 darw1n systemd[1]: Started LSB: AppArmor initialization. Mär 07 09:28:31 darw1n systemd-journal[234]: Forwarding to syslog missed 99 messages. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start timed out. Mär 07 09:29:29 darw1n systemd-journal[234]: Forwarding to syslog missed 1 messages. Mär 07 09:29:29 darw1n systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for /dev/mapper/cryptswap1. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Swap. Mär 07 09:29:29 darw1n systemd[1]: Job swap.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Dependency failed for Encrypted Volumes. Mär 07 09:29:29 darw1n systemd[1]: Job cryptsetup.target/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. Mär 07 09:29:29 darw1n systemd[1]: Job dev-disk-by\x2duuid-0b93a0a2\x2d115c\x2d4a45\x2d9075\x2d5f31454c5a41.device/start failed with result 'timeout'. Mär 07 09:29:29 darw1n systemd[1]: Reached target System Initializatio ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 09:31:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-05 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=63ea7e2a-9b00-4298-b58c-7a68c2775a87 ro vt.handoff=7
[Touch-packages] [Bug 1429544] Re: systemd-logind crashed with SIGABRT in session_start_scope()
OK. I'm afraid I need to see the actual assertion message, which will be in the journal. If you can reproduce this assertion (i. e. it happens reasonably often), can you please save the output of sudo journalctl -u systemd-logind immediately? Also, can you please attach /var/log/syslog? Perhaps the error message is still there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429544 Title: systemd-logind crashed with SIGABRT in session_start_scope() Status in systemd package in Ubuntu: Incomplete Bug description: . ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Sun Mar 8 10:13:11 2015 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2014-11-28 (99 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 2447MU0 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=!Windows 2012 splash Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/graphical.target → /lib/systemd/system/graphical.target.d/xdiagnose.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT UpgradeStatus: Upgraded to vivid on 2015-03-08 (0 days ago) UserGroups: dmi.bios.date: 08/22/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA0WW (2.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 2447MU0 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA0WW(2.60):bd08/22/2014:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2447MU0 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429544/+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 1429171] Re: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused
dino99, can you please do journalctl -ab /tmp/journal.txt and attach it here? Didier, can you please have a look at this? ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Didier Roche (didrocks) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429171 Title: systemd-fsckd[232]: Couldn't connect to plymouth: Connection refused Status in systemd package in Ubuntu: New Bug description: get that error logged many times into journalctl on that vivid booting with systemd-sysv ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Mar 6 16:11:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429171/+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 1366291] Re: python2.7 crashed with SIGSEGV in g_closure_invoke()
That looks like a crash in python-wxgtk2.8 ** Package changed: pygobject (Ubuntu) = wxwidgets2.8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1366291 Title: python2.7 crashed with SIGSEGV in g_closure_invoke() Status in wxwidgets2.8 package in Ubuntu: New Bug description: Ran Tribler, error message occured during program run ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: python2.7-minimal 2.7.8-6ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 5 22:19:13 2014 Disassembly: = 0x720065: Cannot access memory at address 0x720065 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2014-02-22 (195 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) ProcCmdline: python -O Tribler/Main/tribler.py ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x720065: Cannot access memory at address 0x720065 PC (0x720065) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: python2.7 StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: python2.7 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/1366291/+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 1299824] Re: ubuntu-after-install.py assertion failure: (gtk_widget_get_parent (child) == GTK_WIDGET (container))
** Summary changed: - python2.7 crashed with SIGABRT in g_assertion_message() + ubuntu-after-install.py assertion failure: (gtk_widget_get_parent (child) == GTK_WIDGET (container)) ** Package changed: pygobject (Ubuntu) = gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1299824 Title: ubuntu-after-install.py assertion failure: (gtk_widget_get_parent (child) == GTK_WIDGET (container)) Status in gtk+3.0 package in Ubuntu: New Bug description: Appeared when starting session ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: python2.7-minimal 2.7.6-8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 Date: Thu Mar 27 23:10:38 2014 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2014-03-18 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140317) ProcCmdline: python ubuntu-after-install.py ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) LANG=pt_PT.UTF-8 SHELL=/bin/bash TERM=unknown Signal: 6 SourcePackage: python2.7 StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 gtk_container_propagate_draw () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 Title: python2.7 crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1299824/+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 1429661] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1380982 *** https://bugs.launchpad.net/bugs/1380982 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1380982, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429661/+attachment/4338284/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429661/+attachment/4338286/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429661/+attachment/4338288/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429661/+attachment/4338289/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429661/+attachment/4338290/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429661/+attachment/4338291/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429661/+attachment/4338292/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1380982 ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1429661 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: New Bug description: Happened on startup ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: ibus 1.5.9-1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Mar 8 22:06:35 2015 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2014-04-19 (323 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to vivid on 2015-03-02 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1429661/+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 1242918] Re: Writing metadata is not supported for CR2
** Changed in: exiv2 (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1242918 Title: Writing metadata is not supported for CR2 Status in exiv2 package in Ubuntu: Fix Released Bug description: I tried to write metadata to RAW CR2 files in digikam, but without success (it worked for JPG). When I started digikam from console I got the following: digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::Private::printExiv2ExceptionError: Cannot find Xmp key 'Xmp.mwg-rs.Regions/mwg-rs:RegionList[0]/mwg-rs:Name' into image using Exiv2 (Error # 35 : No namespace info available for XMP prefix `mwg-rs' digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::getXmpTagStringSeq: XMP String Seq ( Xmp.digiKam.TagsList ): (Betti, Próba) digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords: /home/kisben/Képek/új/IMG_2590.CR2 == Iptc Keywords: Betti,Emberek,Próba digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::save: KExiv2::metadataWritingMode 0 digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::save: Will write Metadata to file IMG_2590.CR2 digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::Private::saveOperations: Writing metadata is not supported for file IMG_2590.CR2 digikam(4116)/KEXIV2 KExiv2Iface::KExiv2::save: Metadata for file IMG_2590.CR2 written to file. NOTE: I already reported the problem to digikam (https://bugs.kde.org/show_bug.cgi?id=326408), but they closed as the problem is in libexiv2. If this is not the right place to report, pls write me where I can report the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1242918/+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 1429670] [NEW] Desktop reverts to defaults, can't be changed
Public bug reported: All of a sudden my launcher icons, wallpaper image etc, reverted to default, and when I unlock from launcher on the defaults, they disappear after about a second, and then reappear when I tried to re- arrange the icon order. I think there's perhaps something screwy with gconf (? - isn't that where the personal launcher app list is?) because another setting went away and can't be restored (I use caps lock as another control). However, I don't know how to test this or where to look for logs, and the *symptoms* turn up in Unity. If anyone can help with places to look for diagnostics etc., I'd appreciate it. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale] CurrentDesktop: Unity Date: Sun Mar 8 18:06:28 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-21 (290 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1429670 Title: Desktop reverts to defaults, can't be changed Status in unity package in Ubuntu: New Bug description: All of a sudden my launcher icons, wallpaper image etc, reverted to default, and when I unlock from launcher on the defaults, they disappear after about a second, and then reappear when I tried to re- arrange the icon order. I think there's perhaps something screwy with gconf (? - isn't that where the personal launcher app list is?) because another setting went away and can't be restored (I use caps lock as another control). However, I don't know how to test this or where to look for logs, and the *symptoms* turn up in Unity. If anyone can help with places to look for diagnostics etc., I'd appreciate it. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale] CurrentDesktop: Unity Date: Sun Mar 8 18:06:28 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-21 (290 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1429670/+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 1429678] Re: media player fail to connect
** Attachment added: syslog with apparmor messages around 16:35:32 https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1429678/+attachment/4338380/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1429678 Title: media player fail to connect Status in mediaplayer-app package in Ubuntu: New Bug description: Sometimes (three occasions in the last month) my Nexus 7 can't play media files. If I select a video in the Video scope, the player launches but displays a dialog saying Error playing video \n Fail to connect with playback backend. If I select an audio file in the Music scope, the music app opens, but th file doesn't play and the user interface does nothing. On the last two occasions I noticed apparmor messages in syslog. I will attach the most recent syslog. The players have played these audio and video files successfully at other times. On the most recent occasion, I powered the device off twice without fixing the problem but another power cycle three days later fixed it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1 Uname: Linux 3.4.0-3-flo armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Sun Mar 8 20:04:02 2015 InstallationDate: Installed on 2014-12-01 (97 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141201-020204) SourcePackage: mediaplayer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1429678/+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 1429678] [NEW] media player fail to connect
Public bug reported: Sometimes (three occasions in the last month) my Nexus 7 can't play media files. If I select a video in the Video scope, the player launches but displays a dialog saying Error playing video \n Fail to connect with playback backend. If I select an audio file in the Music scope, the music app opens, but th file doesn't play and the user interface does nothing. On the last two occasions I noticed apparmor messages in syslog. I will attach the most recent syslog. The players have played these audio and video files successfully at other times. On the most recent occasion, I powered the device off twice without fixing the problem but another power cycle three days later fixed it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1 Uname: Linux 3.4.0-3-flo armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Sun Mar 8 20:04:02 2015 InstallationDate: Installed on 2014-12-01 (97 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141201-020204) SourcePackage: mediaplayer-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mediaplayer-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1429678 Title: media player fail to connect Status in mediaplayer-app package in Ubuntu: New Bug description: Sometimes (three occasions in the last month) my Nexus 7 can't play media files. If I select a video in the Video scope, the player launches but displays a dialog saying Error playing video \n Fail to connect with playback backend. If I select an audio file in the Music scope, the music app opens, but th file doesn't play and the user interface does nothing. On the last two occasions I noticed apparmor messages in syslog. I will attach the most recent syslog. The players have played these audio and video files successfully at other times. On the most recent occasion, I powered the device off twice without fixing the problem but another power cycle three days later fixed it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1 Uname: Linux 3.4.0-3-flo armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Sun Mar 8 20:04:02 2015 InstallationDate: Installed on 2014-12-01 (97 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141201-020204) SourcePackage: mediaplayer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1429678/+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 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid
I can still see this with emulator devel-proposed #130. Krillin seems fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1411643 Title: Automatic brightness toggle switch missing on krillin/vivid Status in indicator-power package in Ubuntu: Incomplete Bug description: I noticed that on my krillin device with devel-propsed (r70), the automatic display brightness toggle switch is missing in the battery indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1427876] Re: bug
I mean, please add a description of the bug that prompted you to file this ticket. -- 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/1427876 Title: bug Status in xorg package in Ubuntu: Incomplete Bug description: ProblemType: Compiz Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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: Tue Mar 3 22:58:18 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-46-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c708] InstallationDate: Installed on 2015-02-25 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5EV/300E4EV/270E5EV/270E4EV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=95d32bd4-7502-4fa5-b6ab-75a2503aefdd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P05RBD dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP270E5V-K03DZ dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP05RBD:bd05/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP270E5V-K03DZ:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 3 21:11:24 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5539 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1427876/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
After an upgrade to 14.10 the workaround stopped working (restarting network manager each resume). Due to another problem I had to reinstall 14.10 and the problem is no longer present for me after the reinstall. I am not sure whether this has been fixed in 14.10 or whether it was the re-installation that fixed it, but either way the problem has been fixed for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: Invalid Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1316777] Re: Translation template has full path to source files
** Changed in: intltool Milestone: None = 0.51.0 ** Changed in: intltool Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1316777 Title: Translation template has full path to source files Status in Internationalization Tool Collection: Fix Released Status in intltool package in Ubuntu: New Status in unity-scope-click package in Ubuntu: Fix Released Bug description: The translation template currently has full paths to source files. This needs to be fixed so that only relative paths are encoded in the template. To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1316777/+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 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts
** Summary changed: - Unsolvable LTSEnablementStack Mesa package dependency + Package resolver can't find *-lts-utopic package dependencies, aborts ** Description changed: [Description] - On 14.04.2 aptitude/APT determinates non-LTSEnablementStack Mesa packages instead of *lts-utopic pendants as dependencies. This leads to unsolvable conflicts with the already installed *lts-utopic packages. + On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) package resolver fails to find *-lts-utopic package dependencies, aborts. - - [Test Case] - [a] libgles2-mesa (10.1.3-0ubuntu0.3) instead of libgles2-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) - $ sudo aptitude install qtbase5-dev - The following NEW packages will be installed: - libglapi-mesa{a} libgles2-mesa{ab} libgles2-mesa-dev{a} libglu1-mesa-dev{a} libqt5concurrent5{a} libqt5opengl5-dev{a} qt5-qmake{a} - qtbase5-dev qtbase5-dev-tools{a} - 0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded. - Need to get 4,439 kB of archives. After unpacking 27.9 MB will be used. - The following packages have unmet dependencies: - xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. -Conflicts: libgles2-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. - libgles2-mesa : Conflicts: libgles2 which is a virtual package. - libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. - libgles2-mesa-lts-utopic : Conflicts: libgles2 which is a virtual package. - Conflicts: libgles2-mesa but 10.1.3-0ubuntu0.3 is to be installed. - - libglapi-mesa conflicts due to libgles2-mesa having a dependency on - libglapi-mesa (= 10.1.3-0ubuntu0.3). - - [b] libgl1-mesa-dev (10.1.3-0ubuntu0.3) instead of libgl1-mesa-lts-utopic (10.3.2-0ubuntu1~trusty2) - $ sudo aptitude install freeglut3-dev - The following NEW packages will be installed: - freeglut3{a} freeglut3-dev libdrm-dev{a} libgl1-mesa-dev{a} libgl1-mesa-dri{a} libgl1-mesa-glx{ab} libglapi-mesa{a} libglu1-mesa-dev{a} - libice-dev{a} libllvm3.4{a} libpthread-stubs0-dev{a} libsm-dev{a} libx11-dev{a} libx11-doc{a} libx11-xcb-dev{a} libxau-dev{a} - libxcb-dri2-0-dev{a} libxcb-dri3-dev{a} libxcb-glx0-dev{a} libxcb-present-dev{a} libxcb-randr0-dev{a} libxcb-render0-dev{a} - libxcb-shape0-dev{a} libxcb-sync-dev{a} libxcb-xfixes0-dev{a} libxcb1-dev{a} libxdamage-dev{a} libxdmcp-dev{a} libxext-dev{a} - libxfixes-dev{a} libxshmfence-dev{a} libxt-dev{a} libxxf86vm-dev{a} mesa-common-dev{a} x11proto-core-dev{a} x11proto-damage-dev{a} - x11proto-dri2-dev{a} x11proto-fixes-dev{a} x11proto-gl-dev{a} x11proto-input-dev{a} x11proto-kb-dev{a} x11proto-xext-dev{a} - x11proto-xf86vidmode-dev{a} xorg-sgml-doctools{a} xtrans-dev{a} - 0 packages upgraded, 45 newly installed, 0 to remove and 68 not upgraded. - Need to get 16.6 MB of archives. After unpacking 88.2 MB will be used. - The following packages have unmet dependencies: - libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 10.1.3-0ubuntu0.3 is to be installed. - libgl1-mesa-glx-lts-utopic : Conflicts: libgl1 which is a virtual package. - Conflicts: libgl1-mesa-glx but 10.1.3-0ubuntu0.3 is to be installed. - xserver-xorg-lts-utopic : Conflicts: libgl1-mesa-dri (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. -Conflicts: libgl1-mesa-glx (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. -Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. - libgl1-mesa-glx : Conflicts: libgl1 which is a virtual package. - libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. + [Test case] + $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev + (Log attached as apt.log) [Workaround] - [a] - $ sudo aptitude install qtbase5-dev libgles2-mesa-lts-utopic + Manually resolve: + $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic - [b] - $ sudo aptitude install -s freeglut3-dev libgl1-mesa-dev-lts-utopic + Possible catch all solution: + $ sudo apt-get install .*-dev-lts-utopic + + [Speculation] + Control file of libgles2-mesa-dev-lts-utopic do look right: + http://debian-handbook.info/browse/stable/sect.package-meta-information.html + + Guess APT just get overwhelmend by the possibilies and aborts before + finding the right one. + + Is there some SAT-solver, which could conform? Aptitude's resolver fails, too. + Could control files be tweaked to make resolving easier? + + [Possible affected packages] + Possible all packages which have dependencies on *-mesa-dev for which there's an updated version in the LTS Enablement Stacks. + Roughly: + $ apt-cache rdepends .*-mesa-dev ** Attachment added: apt.log
[Touch-packages] [Bug 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts
-- 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/1429529 Title: Package resolver can't find *-lts-utopic package dependencies, aborts Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) package resolver fails to find *-lts-utopic package dependencies, aborts. [Test case] $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev (Log attached as apt.log) [Workaround] Manually resolve: $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic Possible catch all solution: $ sudo apt-get install .*-dev-lts-utopic [Speculation] Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does look right imho: http://debian-handbook.info/browse/stable/sect.package-meta-information.html Guess APT just get overwhelmed by the possibilies and aborts before finding the right one. Is there some SAT-solver, which could conform? Aptitude's resolver fails, too. Could control files be tweaked to make resolving easier? [Possible affected packages] Possible all packages which have dependencies on *-mesa-dev for which there's an updated version in the LTS Enablement Stacks. Roughly: $ apt-cache rdepends .*-mesa-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429529/+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 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts
** Attachment added: apport.libgles2-mesa-dev-lts-utopic.m_aroj3l.apport https://bugs.launchpad.net/ubuntu/+source/mesa-lts-utopic/+bug/1429529/+attachment/4338327/+files/apport.libgles2-mesa-dev-lts-utopic.m_aroj3l.apport ** Description changed: [Description] On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) package resolver fails to find *-lts-utopic package dependencies, aborts. [Test case] $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev (Log attached as apt.log) [Workaround] Manually resolve: $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic Possible catch all solution: $ sudo apt-get install .*-dev-lts-utopic [Speculation] - Control file of libgles2-mesa-dev-lts-utopic do look right: + Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does look right imho: http://debian-handbook.info/browse/stable/sect.package-meta-information.html Guess APT just get overwhelmend by the possibilies and aborts before finding the right one. Is there some SAT-solver, which could conform? Aptitude's resolver fails, too. Could control files be tweaked to make resolving easier? [Possible affected packages] Possible all packages which have dependencies on *-mesa-dev for which there's an updated version in the LTS Enablement Stacks. Roughly: $ apt-cache rdepends .*-mesa-dev ** Description changed: [Description] On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) package resolver fails to find *-lts-utopic package dependencies, aborts. [Test case] $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev (Log attached as apt.log) [Workaround] Manually resolve: $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic Possible catch all solution: $ sudo apt-get install .*-dev-lts-utopic [Speculation] Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does look right imho: http://debian-handbook.info/browse/stable/sect.package-meta-information.html - Guess APT just get overwhelmend by the possibilies and aborts before + Guess APT just get overwhelmed by the possibilies and aborts before finding the right one. Is there some SAT-solver, which could conform? Aptitude's resolver fails, too. Could control files be tweaked to make resolving easier? [Possible affected packages] Possible all packages which have dependencies on *-mesa-dev for which there's an updated version in the LTS Enablement Stacks. Roughly: $ apt-cache rdepends .*-mesa-dev -- 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/1429529 Title: Package resolver can't find *-lts-utopic package dependencies, aborts Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) package resolver fails to find *-lts-utopic package dependencies, aborts. [Test case] $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev (Log attached as apt.log) [Workaround] Manually resolve: $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic Possible catch all solution: $ sudo apt-get install .*-dev-lts-utopic [Speculation] Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does look right imho: http://debian-handbook.info/browse/stable/sect.package-meta-information.html Guess APT just get overwhelmed by the possibilies and aborts before finding the right one. Is there some SAT-solver, which could conform? Aptitude's resolver fails, too. Could control files be tweaked to make resolving easier? [Possible affected packages] Possible all packages which have dependencies on *-mesa-dev for which there's an updated version in the LTS Enablement Stacks. Roughly: $ apt-cache rdepends .*-mesa-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429529/+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 1424074] Re: Vivid Unity Wallpaper horizontally hashed
*** This bug is a duplicate of bug 1406802 *** https://bugs.launchpad.net/bugs/1406802 Do not create new bug reports for the exact same issue. This is also not unity’s fault, as I can reproduce the issue in GNOME Shell as well, so the bug must be somewhere else. ** This bug has been marked a duplicate of bug 1406802 Vivid Unity Wallpaper horizontally hashed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1424074 Title: Vivid Unity Wallpaper horizontally hashed Status in unity package in Ubuntu: New Bug description: Wallpaper still hashed on this Lenovo M58P DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION=Ubuntu Vivid Vervet (development branch) Linux Lenovo2 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) Files Pictures select picture set as wallpaper will correct the image - may have to do this several times. Settings - Appearance - wallpaper did not correct the image. See attachment. Note, this does not occur on my other test systems which have different graphic controllers. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.1-0ubuntu2 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: Fri Feb 20 16:45:20 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkCentre M6258 [17aa:3048] Subsystem: Lenovo Device [17aa:3048] InstallationDate: Installed on 2015-02-20 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150219) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic root=UUID=733dbf2f-324c-4185-820a-512e6f8a6a7b ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4 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.917-1~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Feb 20 16:44:26 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.2.901-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1424074/+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 1427804] Re: Mouse pointer disappears after upgrade to kernel 3.19
Same here on Ubuntu 3.19 Kernel and on 3.19pf1 custom kernel. So I think it has something to do with a specific device or class of devices. I'm using a Satelite C875-S7132NR -- 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/1427804 Title: Mouse pointer disappears after upgrade to kernel 3.19 Status in xorg package in Ubuntu: New Bug description: After upgrade to kernel 3.19, the mouse pointer disappears. The mouse is fully functional, just cannot see its pointer, which makes it pretty useless... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 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: Tue Mar 3 19:23:30 2015 DistUpgraded: 2014-11-04 19:50:17,092 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-31-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-031900-generic, x86_64: installed vboxhost, 4.3.18, 3.16.0-30-generic, x86_64: installed vboxhost, 4.3.18, 3.16.0-31-generic, x86_64: installed vboxhost, 4.3.18, 3.19.0-031900-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8534] InstallationDate: Installed on 2014-10-24 (129 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-031900-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-11-04 (118 days ago) dmi.bios.date: 09/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Mar 3 19:21:19 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4121 vendor WAC xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1427804/+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 1429697] Re: indicator-sound-service crashed with signal 5 in main()
*** This bug is a duplicate of bug 1429303 *** https://bugs.launchpad.net/bugs/1429303 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1429303, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429697/+attachment/4338421/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429697/+attachment/4338423/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429697/+attachment/4338425/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429697/+attachment/4338426/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429697/+attachment/4338427/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429697/+attachment/4338428/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429697/+attachment/4338429/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1429303 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1429697 Title: indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Bug description: Crash report appeared at login. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Mar 8 15:51:33 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2014-11-30 (98 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: Upgraded to vivid on 2015-02-09 (27 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1429697/+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 1190344] Re: lightdm is leaking FDs -fix
Hmm, turns out I only committed the session leak from the attached patch and not the greeter leak. I've committed that fix now. -- 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/1190344 Title: lightdm is leaking FDs -fix Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Confirmed Status in lightdm source package in Utopic: Fix Committed Status in lightdm source package in Vivid: Fix Released Status in Fedora: Unknown Bug description: [Impact] LightDM doesn't close the server side end of the pipes used to communicate with session processes. This means each session that is created leaks two file descriptors eventually leading to the system stopping it from creating new pipes. [Test Case] 1. Start LightDM 2. Check how many pipes are open # lsof -p {lightdm_pid} | grep FIFO | wc -l 3. Create sessions by either cycling between users in Unity Greeter or logging in and out 4. Check how many pipes exist using step 2. Expected result: No more pipes should be open Observed result: Many pipes remain open [Regression Potential] Low. Fix is to close pipes when finished with them. Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190344/+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 601555] Re: Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry.
** Changed in: exiv2 (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/601555 Title: Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry. Status in The GNU Image Manipulation Program (GIMP): Unknown Status in exiv2 package in Ubuntu: Fix Released Status in exiv2 package in Debian: Confirmed Bug description: Binary package hint: exiv2 When I start digikam from the command line, it bombs it with (thousands?) of messages like: [...] Warning: Directory NikonPreview, entry 0xb3b2 has unknown Exif (TIFF) type 46516; setting type size 1. Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry. [...] Error: Offset of directory NikonPreview, entry 0x00c4 is out of bounds: Offset = 0x01010101; truncating the entry Warning: Directory NikonPreview, entry 0x0504 has unknown Exif (TIFF) type 1798; setting type size 1. [...] According to http://mail.kde.org/pipermail/digikam- users/2009-July/007947.html It's a problem of libexiv2 *t ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libexiv2-6 0.19-1 ProcVersionSignature: Ubuntu 2.6.31-21.59-generic Uname: Linux 2.6.31-21-generic x86_64 Architecture: amd64 Date: Sun Jul 4 11:08:10 2010 ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, user) LANG=de_CH.utf8 SHELL=/bin/bash SourcePackage: exiv2 To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/601555/+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 1319789] Re: Trackpad not working on 14.04
I thank you for your support and am sorry for the delayed response. The sticker on the laptop sys HP Pavillion 15 Notebook PC. Not too sure of the model no. Thanks, Varun. Original Message From: Christopher M. Penalver Sent: Thursday, 19 February 2015 16:51 To: varun19...@gmail.com Reply To: Bug 1319789 Subject: [Bug 1319789] Re: Trackpad not working on 14.04 varun, could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)? ** Tags added: needs-full-computer-model ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1319789 Title: Trackpad not working on 14.04 Status in xorg package in Ubuntu: Incomplete Bug description: ever since the laptop was updated to 14.04 lts from 12.04 lts, the tracpad has not been working, and is not recognised. there is no trackpad option under mouse and trackpad settings. i have tried many attempts to fix it, but has not worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 15 17:02:52 2014 DistUpgraded: 2014-05-11 18:24:24,169 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-puli-precise-amd64-20130925-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2166] Subsystem: Hewlett-Packard Company Device [103c:2166] InstallationDate: Installed on 2013-11-28 (168 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130925-02:34 MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=856eced2-cdd1-459e-8b1e-55b1ed18f5ac ro i915.modeset=1 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-11 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.34 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd10/31/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr09921100410600080:rvnHewlett-Packard:rn2166:rvr29.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 09921100410600080 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 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.1.0-4ubuntu5 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu May 15 16:37:20 2014 xserver.configfile: default xserver.errors: module ABI major version (18) doesn't match the server's version (20) Failed to load module syntp (module requirement mismatch, 0) module ABI major version (18) doesn't match the server's version (20) Failed to load module syntp (module requirement mismatch, 0) No input driver matching `syntp' xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1319789/+subscriptions -- 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/1319789 Title: Trackpad not working on 14.04 Status in xorg package in Ubuntu:
[Touch-packages] [Bug 1248642] Re: dynamic library inconsistencies with OpenGL/C++
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-319 (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1248642 Title: dynamic library inconsistencies with OpenGL/C++ Status in binutils package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in binutils source package in Trusty: In Progress Status in nvidia-graphics-drivers-319 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-331 source package in Trusty: Confirmed Status in binutils package in Debian: Fix Released Bug description: While using the nvidia-319 driver, the following C++ program won't run: $ cat test.cpp EOF #include string #include GL/gl.h int main(int argc, char *argv[]) { std::string s; glEnable(GL_LIGHT0); } EOF Instead, it fails with the following error message: $ g++ test.cpp -lGL $ ./a.out Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed! Using the xserver-xorg-video-nouveau driver, the problem does not occur. Also, when std::string is not used, the program runs without problems. Using OpenGL from pure C programs is also not a problem. The problem can be reproduced with both g++-4.6 and g++-4.8. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-319 319.32-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 6 18:25:48 2013 InstallationDate: Installed on 2013-11-01 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) MarkForUpload: True SourcePackage: nvidia-graphics-drivers-319 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.319.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1248642/+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 1248642] Re: dynamic library inconsistencies with OpenGL/C++
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1248642 Title: dynamic library inconsistencies with OpenGL/C++ Status in binutils package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in binutils source package in Trusty: In Progress Status in nvidia-graphics-drivers-319 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-331 source package in Trusty: Confirmed Status in binutils package in Debian: Fix Released Bug description: While using the nvidia-319 driver, the following C++ program won't run: $ cat test.cpp EOF #include string #include GL/gl.h int main(int argc, char *argv[]) { std::string s; glEnable(GL_LIGHT0); } EOF Instead, it fails with the following error message: $ g++ test.cpp -lGL $ ./a.out Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed! Using the xserver-xorg-video-nouveau driver, the problem does not occur. Also, when std::string is not used, the program runs without problems. Using OpenGL from pure C programs is also not a problem. The problem can be reproduced with both g++-4.6 and g++-4.8. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-319 319.32-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 6 18:25:48 2013 InstallationDate: Installed on 2013-11-01 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) MarkForUpload: True SourcePackage: nvidia-graphics-drivers-319 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.319.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1248642/+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 1429644] Re: [ENS1371 - Emulated Ensoniq AudioPCI inside VMware, playback] Sound is distorted
** Summary changed: - [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted + [ENS1371 - Emulated Ensoniq AudioPCI inside VMware, playback] Sound is distorted ** Changed in: pulseaudio (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1429644 Title: [ENS1371 - Emulated Ensoniq AudioPCI inside VMware, playback] Sound is distorted Status in pulseaudio package in Ubuntu: Incomplete Bug description: sound quality poor. distoted sound ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaditya 15448 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 9 01:58:35 2015 InstallationDate: Installed on 2015-03-06 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI successful Symptom_Card: Creative Sound Blaster AudioPCI64V, AudioPCI128 - Ensoniq AudioPCI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or overdriven sound Title: [ENS1371 - Ensoniq AudioPCI, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2015-03-07T12:55:40.634974 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1429644/+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 1429709] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1429709/+attachment/4338477/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1429709 Title: indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Bug description: This immediatly crash comes after a normal start-up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 9 05:18:07 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-03-09 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150308) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=de_AT:de XDG_RUNTIME_DIR=set LANG=de_AT.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1429709/+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 1429709] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429709/+attachment/4338478/+files/ThreadStacktrace.txt ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429709/+attachment/4338457/+files/CoreDump.gz ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1429709 Title: indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Bug description: This immediatly crash comes after a normal start-up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 9 05:18:07 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-03-09 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150308) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=de_AT:de XDG_RUNTIME_DIR=set LANG=de_AT.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1429709/+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 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Changed in: init-system-helpers (Ubuntu Vivid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: In Progress Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: In Progress Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Branch linked: lp:ubuntu/vivid-proposed/init-system-helpers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: Fix Committed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
Finally finally finally I got that salad to work but not the same way, here the details : In fact they are to pins disconnected that I had to connect, the 0x1a and THE 0x18, the connections in hdajackretask are now : 0x1a = Line out (back) 0x18 = (Center/LFE) Which gives in alsamixer : Master = Master fonction. Headphone (Headphone) = Adjustable volume for the headphone jack (first one). Headphone (Headphone 1) = [00] Not adjustable (probably the headset jack ?). Speaker (Speaker) = [00] Not adjustable. Front (Front) = Adjustable and corresponding to front speakers (if on 00 you ear only the subwoofer). Surround (Surround) = seems to correspond to the subwoofer (if on 00 you ear high front frequency). Mic (Mic) = Mic adjustable. Mic Boost (Mic Boost) = Adjustable but no idee what for. Auto-Mute (Auto-mute Mode) (line out, speaker, disable) = If line out selected it mute all speakers, if speaker selected it mute only the tweeters but the subwoofer is still active. So I hope that it will be usefull to others that were fyghting to get that crap working. P.S. I didn't try if the headset nor mic are fonctionnal but the headphone are, no problem. -- 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/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in alsa-driver package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+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 1429709]
StacktraceTop: main (argc=optimized out, argv=optimized out) at /build/buildd/indicator-sound-12.10.2+15.04.20150227.1/src/main.c:53 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1429709 Title: indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Bug description: This immediatly crash comes after a normal start-up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 9 05:18:07 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-03-09 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150308) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=de_AT:de XDG_RUNTIME_DIR=set LANG=de_AT.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1429709/+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 1429709] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1429709/+attachment/4338476/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1429709 Title: indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Bug description: This immediatly crash comes after a normal start-up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 9 05:18:07 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-03-09 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150308) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=de_AT:de XDG_RUNTIME_DIR=set LANG=de_AT.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1429709/+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 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/platform.vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: In Progress Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: In Progress Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-meta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: Fix Committed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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 1193238] Re: Xorg freeze
Hello My laptop which encounters this bug has been lost (stolen). I cannot support debugging anymore. On Sun, Feb 15, 2015 at 6:14 AM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Hồng Quân, could you please capture the crash via https://help.ubuntu.com/community/DebuggingSystemCrash ? ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1193238 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1193238/+subscriptions -- Quân *** * Nguyễn Hồng Quân* * Y!M: ng_hquan_vn* * Facebook: ng.hong.quan * * Web: quan.hoabinh.vn* *** -- 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/1193238 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: This occurs a couple of times per day. When it occurs, the sound is noisy, keyboard and mouse do not work. I have to press Power button to turn it off. Attached is the photo of screen when the bug happens ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 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: Fri Jun 21 15:05:50 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1652] InstallationDate: Installed on 2013-04-25 (56 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK Computer Inc. K43E MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=e9b9ae42-e5a4-4231-a673-a0bc16b188ec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43E.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K43E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43E.216:bd09/26/2011:svnASUSTeKComputerInc.:pnK43E:pvr1.0:rvnASUSTeKComputerInc.:rnK43E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K43E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri Jun 21 10:17:00 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-11-03 (62 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: third-party-packages saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip
[Touch-packages] [Bug 1413865] Re: No default setting for When power is critically low in Power settings
from gsd-power-manager.c we get as follows /* this is only used on critically low battery where * hibernate is not available and is marginally better * than just powering down the computer mid-write */ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1413865 Title: No default setting for When power is critically low in Power settings Status in Ubuntu Kylin: Confirmed Status in ubuntu-settings package in Ubuntu: New Bug description: No default setting for When power is critically low in Power settings. 电源设置中”电量严重不足时“没有默认选项 Steps: 1. Install the latest Ubuntu kylin Vivid x64 OS 2. Enter into System settings--Power 3. Check the default value of When power is critically low --Failed. No default value for it Configuration: OS: Ubuntu Kylin vivid Daily build 20150122 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1413865/+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 1190344] Re: lightdm is leaking FDs -fix
** Changed in: lightdm/1.2 Status: Fix Released = Fix Committed ** Changed in: lightdm/1.2 Milestone: 1.2.9 = 1.2.10 ** Changed in: lightdm/1.12 Status: Fix Released = Fix Committed ** Changed in: lightdm/1.12 Milestone: 1.12.2 = 1.12.3 ** Changed in: lightdm/1.10 Status: Fix Released = Fix Committed ** Changed in: lightdm/1.10 Milestone: 1.10.4 = 1.10.5 ** Changed in: lightdm Status: Fix Released = Fix Committed ** Changed in: lightdm Milestone: 1.13.0 = 1.13.2 ** Changed in: lightdm (Ubuntu Trusty) Status: Confirmed = Triaged ** Changed in: lightdm (Ubuntu Utopic) Status: Fix Committed = Triaged ** Changed in: lightdm (Ubuntu Vivid) Status: Fix Released = Triaged -- 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/1190344 Title: lightdm is leaking FDs -fix Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Triaged Status in lightdm source package in Vivid: Triaged Status in Fedora: Unknown Bug description: [Impact] LightDM doesn't close the server side end of the pipes used to communicate with session processes. This means each session that is created leaks two file descriptors eventually leading to the system stopping it from creating new pipes. [Test Case] 1. Start LightDM 2. Check how many pipes are open # lsof -p {lightdm_pid} | grep FIFO | wc -l 3. Create sessions by either cycling between users in Unity Greeter or logging in and out 4. Check how many pipes exist using step 2. Expected result: No more pipes should be open Observed result: Many pipes remain open [Regression Potential] Low. Fix is to close pipes when finished with them. Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190344/+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 1408376] Re: [HDA-Intel - HDA ATI SB, playback] Playback problem
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = Expired -- 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/1408376 Title: [HDA-Intel - HDA ATI SB, playback] Playback problem Status in alsa-driver package in Ubuntu: Expired Bug description: Solo puedo escuchar el audio atraves de auriculares ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-43.72~precise1-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-43-generic. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2800 F pulseaudio /dev/snd/pcmC0D0p: victor 2800 F...m pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0x9230 irq 16' Mixer name : 'Conexant CX20585' Components : 'HDA:14f15069,1179fdf4,00100302' Controls : 11 Simple ctrls : 6 CheckboxSubmission: e45f082e2d24f59b336f1a596b97f898 CheckboxSystem: 5202e7ee197af4942baf4f50cf4120c6 Date: Wed Jan 7 14:33:54 2015 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=es_PY:es TERM=xterm PATH=(custom, no user) LANG=es_PY.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Audio Interno - HDA ATI SB Symptom_Type: None of the above Title: [HDA-Intel - HDA ATI SB, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.asset.tag: No Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/27/2011:svnTOSHIBA:pnSatelliteC645D:pvrPSC04U-011LM5:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite C645D dmi.product.version: PSC04U-011LM5 dmi.sys.vendor: TOSHIBA mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-07T13:33:52.953873 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1408376/+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 1399223] Re: python-testtools should be upgraded to version 1.5.0
[Expired for python-testtools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: python-testtools (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1399223 Title: python-testtools should be upgraded to version 1.5.0 Status in python-testtools package in Ubuntu: Expired Bug description: We are using an old version of testtools on ubuntu which prevents us from running all dashboard tests and keeping the dashboard from being green. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1399223/+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 1406006] Re: [HP Pavilion Sleekbook 15 PC, IDT 92HD99BXX, Black Headphone Out, Right] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = Expired -- 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/1406006 Title: [HP Pavilion Sleekbook 15 PC, IDT 92HD99BXX, Black Headphone Out, Right] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: I can hear souds from my speackers but not on my headphones. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parissa1697 F pulseaudio /dev/snd/pcmC0D0p: parissa1697 F...m pulseaudio CurrentDesktop: Unity Date: Sat Dec 27 22:25:40 2014 InstallationDate: Installed on 2014-12-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parissa1697 F pulseaudio /dev/snd/pcmC0D0p: parissa1697 F...m pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [HP Pavilion Sleekbook 15 PC, IDT 92HD99BXX, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 18FE dmi.board.vendor: Hewlett-Packard dmi.board.version: 82.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd10/04/2012:svnHewlett-Packard:pnHPPavilionSleekbook15PC:pvr087E103B590320100:rvnHewlett-Packard:rn18FE:rvr82.13:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Sleekbook 15 PC dmi.product.version: 087E103B590320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1406006/+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 1429709] [NEW] indicator-sound-service crashed with signal 5 in main()
Public bug reported: This immediatly crash comes after a normal start-up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 9 05:18:07 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-03-09 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150308) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=de_AT:de XDG_RUNTIME_DIR=set LANG=de_AT.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: indicator-sound (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1429709 Title: indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Bug description: This immediatly crash comes after a normal start-up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 9 05:18:07 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-03-09 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150308) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=de_AT:de XDG_RUNTIME_DIR=set LANG=de_AT.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1429709/+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 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Changed in: ubuntu-meta (Ubuntu Vivid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: Fix Committed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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 1413865] Re: No default setting for When power is critically low in Power settings
** Patch added: patch https://bugs.launchpad.net/ubuntukylin/+bug/1413865/+attachment/4338505/+files/battery-critical-low.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1413865 Title: No default setting for When power is critically low in Power settings Status in Ubuntu Kylin: Confirmed Status in ubuntu-settings package in Ubuntu: New Bug description: No default setting for When power is critically low in Power settings. 电源设置中”电量严重不足时“没有默认选项 Steps: 1. Install the latest Ubuntu kylin Vivid x64 OS 2. Enter into System settings--Power 3. Check the default value of When power is critically low --Failed. No default value for it Configuration: OS: Ubuntu Kylin vivid Daily build 20150122 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1413865/+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 1429143] Re: Slow shutdown after booting with systemd
Oops, following Martin's helpful pointers I see that it was down to one my home-brewed services that does not seem to like being run via systemd. Likely a problem of my own making. Thanks for the help and sorry for the noise. ** Changed in: systemd (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429143 Title: Slow shutdown after booting with systemd Status in systemd package in Ubuntu: Invalid Bug description: When running vivid booted with systemd kernel, shutdown consistently takes around 90 seconds. With the normal kernel it is about 15 seconds. In the log, shutdown started (from the cog) at 13:50:20, Mar 6th. The purple Ubuntu screen with dots appears after a few seconds and then sits there. It actually powered off at 13:51:55. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-7-generic 3.19.0-7.7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colinl 1948 F pulseaudio /dev/snd/controlC1: colinl 1948 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 6 13:54:29 2015 InstallationDate: Installed on 2014-10-21 (135 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 init=/lib/systemd/systemd RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429143/+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 1428811] Re: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges
I uploaded the trusty update with the modified patch (see above). Please note that this is blocked on https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.11 getting accepted into trusty-updates. ** Changed in: systemd (Ubuntu Trusty) Status: New = In Progress ** Changed in: systemd (Ubuntu Trusty) Assignee: (unassigned) = Craig Magina (craig.magina) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1428811 Title: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Trusty: In Progress Bug description: This is an additional change following after the m800 bug (LP: #1347776) and m400 bug (LP: #1354306), udev/systemd needs a rule to cover triggering a graceful shutdown on the HP Proliant m400 Cartridge when running the utopic hwe kernel in trusty. [Impact] Currently, graceful shutdown via the iLO works when running the base trusty kernel, but if the hwe kernel is installed, it does not. [Test Case] Initiate a graceful shutdown via the iLO. [Regression Potential] The new rule is pretty tightly bound to the m400 system - so the risk of this rule matching and impacting behavior on a different platform is minimal. This will presumably cause new code to run and read /proc/device-tree/model on other platforms - but this is already done for the m800 system in both utopic and trusty as well as the 3.13.0 kernel m400 rule. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428811/+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 1419248] Re: udev-204-5ubuntu20.10 breakes usb_modeswitch
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.10 adjusted the udev rules to prove some more drivers, perhaps one got in the way for you. Can you please install ubuntu20.9 (the old, working udev), activate the modem, do lsmod ~/modules.old dmesg ~/dmesg.old . Then upgrade to current udev (i. e. ubuntu20.10), try to activate the modem (i. e. you get a failure), then do lsmog ~/modules.new dmesg ~/dmesg.new and attach modules.old, dmesg.old, modules.new, dmesg.new here? Thanks! ** Changed in: systemd (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1419248 Title: udev-204-5ubuntu20.10 breakes usb_modeswitch Status in systemd package in Ubuntu: Incomplete Bug description: usb_modeswitch doesn't work after upgrade from udev-204-5ubuntu20.9 to udev-204-5ubuntu20.10. Downgrading to udev-204-5ubuntu20.9 solves the problem. Kernel: Linux localhost 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:37:48 UTC 2015 i686 i686 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1419248/+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 1429143] Re: Slow shutdown after booting with systemd
Well, we do want to know about/fix issues like that system does not seem to like being run via systemd, as we'll switch to systemd tomorrow :-) So unless it was a problem with a custom init.d script or so, and not with our Ubuntu packages, please do keep filing bugs. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1429143 Title: Slow shutdown after booting with systemd Status in systemd package in Ubuntu: Invalid Bug description: When running vivid booted with systemd kernel, shutdown consistently takes around 90 seconds. With the normal kernel it is about 15 seconds. In the log, shutdown started (from the cog) at 13:50:20, Mar 6th. The purple Ubuntu screen with dots appears after a few seconds and then sits there. It actually powered off at 13:51:55. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-7-generic 3.19.0-7.7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colinl 1948 F pulseaudio /dev/snd/controlC1: colinl 1948 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 6 13:54:29 2015 InstallationDate: Installed on 2014-10-21 (135 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro quiet splash vt.handoff=7 init=/lib/systemd/systemd RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-25 (8 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1429143/+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 1429563] [NEW] Printer parallel port kernel call trace
Public bug reported: Hi, I'm trying to install an old printer on my Ubuntu 14.04. Printer isn't found. I found this in dmesg: [ 240.800054] INFO: task parallel:1815 blocked for more than 120 seconds. [ 240.800063] Not tainted 3.13.0-46-generic #77-Ubuntu [ 240.800066] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.800070] parallel D d2867e80 0 1815 1 0x0004 [ 240.800078] d2867ec8 0086 c105baf7 d2867e80 c1664875 c1a95580 c1926a00 c1664633 [ 240.800089] c1a95580 c1926a00 ce406800 df3a4580 de68f600 0002 d2867ee4 c1664633 [ 240.800098] da8d3900 0002 037a de68f600 0002 d2867ee4 ff16 d286007b [ 240.800109] Call Trace: [ 240.800122] [c105baf7] ? irq_exit+0x47/0xa0 [ 240.800131] [c1664875] ? do_IRQ+0x45/0xb0 [ 240.800136] [c1664633] ? common_interrupt+0x33/0x38 [ 240.800145] [c1664633] ? common_interrupt+0x33/0x38 [ 240.800165] [e02e21e2] ? parport_pc_frob_control+0x32/0xd0 [parport_pc] [ 240.800173] [c1659d73] schedule_preempt_disabled+0x23/0x60 [ 240.800178] [c165b6bd] __mutex_lock_slowpath+0x10d/0x171 [ 240.800185] [c165abec] mutex_lock+0x1c/0x28 [ 240.800192] [e026dbfb] pp_ioctl+0x1b/0x40 [ppdev] [ 240.800198] [e026dbe0] ? pp_do_ioctl+0x860/0x860 [ppdev] [ 240.800204] [c118afc2] do_vfs_ioctl+0x2e2/0x4d0 [ 240.800211] [e026dfae] ? pp_read+0x17e/0x1ed [ppdev] [ 240.800216] [c117a544] ? vfs_read+0xd4/0x140 [ 240.800221] [c118b210] SyS_ioctl+0x60/0x80 [ 240.800226] [c166414d] sysenter_do_call+0x12/0x12 [ 240.800230] INFO: task hpfax:1819 blocked for more than 120 seconds. [ 240.800233] Not tainted 3.13.0-46-generic #77-Ubuntu [ 240.800235] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.800238] hpfax D ce401a00 0 1819 1 0x [ 240.800244] de71fec8 00200086 ce401a00 ce401a00 de71fef4 c1a95580 c1926a00 [ 240.800253] c1a95580 c1926a00 ce401a00 df3a4580 de71fec4 0008 de7790a4 [ 240.800262] de71fef4 ce440a00 de71fee0 c1187a60 de71ff80 de71fec0 de782000 [ 240.800270] Call Trace: [ 240.800277] [c1187a60] ? path_openat+0xb0/0x530 [ 240.800284] [c1659d73] schedule_preempt_disabled+0x23/0x60 [ 240.800289] [c165b6bd] __mutex_lock_slowpath+0x10d/0x171 [ 240.800295] [c165abec] mutex_lock+0x1c/0x28 [ 240.800302] [e026dbfb] pp_ioctl+0x1b/0x40 [ppdev] [ 240.800308] [e026dbe0] ? pp_do_ioctl+0x860/0x860 [ppdev] [ 240.800313] [c118afc2] do_vfs_ioctl+0x2e2/0x4d0 [ 240.800317] [c1187efd] ? final_putname+0x1d/0x40 [ 240.800321] [c1187efd] ? final_putname+0x1d/0x40 [ 240.800326] [c11880a4] ? putname+0x24/0x40 [ 240.800330] [c1179916] ? do_sys_open+0x196/0x260 [ 240.800334] [c118b210] SyS_ioctl+0x60/0x80 [ 240.800339] [c166414d] sysenter_do_call+0x12/0x12 [ 240.800343] INFO: task hpfax:1844 blocked for more than 120 seconds. [ 240.800346] Not tainted 3.13.0-46-generic #77-Ubuntu [ 240.800348] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.800351] hpfax D ce403400 0 1844 1 0x [ 240.800356] ce4fbec8 00200086 ce403400 ce403400 ce4fbef4 c1a95580 c1926a00 [ 240.800365] c1a95580 c1926a00 ce403400 df3a4580 ce4fbec4 0008 de7790a4 [ 240.800374] ce4fbef4 ce479800 ce4fbee0 c1187a60 ce4fbf80 ce4fbec0 de781000 [ 240.800383] Call Trace: [ 240.800388] [c1187a60] ? path_openat+0xb0/0x530 [ 240.800395] [c1659d73] schedule_preempt_disabled+0x23/0x60 [ 240.800400] [c165b6bd] __mutex_lock_slowpath+0x10d/0x171 [ 240.800407] [c165abec] mutex_lock+0x1c/0x28 [ 240.800413] [e026dbfb] pp_ioctl+0x1b/0x40 [ppdev] [ 240.800419] [e026dbe0] ? pp_do_ioctl+0x860/0x860 [ppdev] [ 240.800424] [c118afc2] do_vfs_ioctl+0x2e2/0x4d0 [ 240.800428] [c1187efd] ? final_putname+0x1d/0x40 [ 240.800433] [c1187efd] ? final_putname+0x1d/0x40 [ 240.800437] [c11880a4] ? putname+0x24/0x40 [ 240.800441] [c1179916] ? do_sys_open+0x196/0x260 [ 240.800445] [c118b210] SyS_ioctl+0x60/0x80 [ 240.800450] [c166414d] sysenter_do_call+0x12/0x12 [ 240.800454] INFO: task hp:1846 blocked for more than 120 seconds. [ 240.800457] Not tainted 3.13.0-46-generic #77-Ubuntu [ 240.800459] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.800461] hp D ce40 0 1846 1 0x [ 240.800466] ce4e9ec8 00200086 ce40 ce40 ce4e9ef4 c1a95580 e0fa46c9 0016 [ 240.800475] c1a95580 ce48db00 ce40 df3b2580 ce4e9ec4 0008 de7790a4 [ 240.800484] ce4e9ef4 ce582b00 ce4e9ee0 c1187a60 ce4e9f80 ce4e9ec0 dbdb5000 [ 240.800493] Call Trace: [ 240.800499] [c1187a60] ? path_openat+0xb0/0x530 [ 240.800506] [c1659d73] schedule_preempt_disabled+0x23/0x60 [ 240.800511] [c165b6bd] __mutex_lock_slowpath+0x10d/0x171 [ 240.800517] [c165abec] mutex_lock+0x1c/0x28 [ 240.800524] [e026dbfb] pp_ioctl+0x1b/0x40 [ppdev] [ 240.800529] [e026dbe0] ? pp_do_ioctl+0x860/0x860 [ppdev] [ 240.800534] [c118afc2] do_vfs_ioctl+0x2e2/0x4d0 [ 240.800539] [c1187efd] ? final_putname+0x1d/0x40 [ 240.800543] [c1187efd] ? final_putname+0x1d/0x40 [ 240.800547] [c11880a4] ? putname+0x24/0x40 [
[Touch-packages] [Bug 1429496] Re: Kubuntu Vivid 1 Beta 15.04: Ubuntu-bug hangs on cancel
Argh, sorry. Of course not. :-) I didn't see, launchpad used the package settings from my previous bug report. ** Package changed: wmaker (Ubuntu) = apport (Ubuntu) -- 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/1429496 Title: Kubuntu Vivid 1 Beta 15.04: Ubuntu-bug hangs on cancel Status in apport package in Ubuntu: New Bug description: What I did: 1. Started ubuntu-bug 2. Selected other problem and clicked on Ok 3. Clicked on Cancel on the second dialog. Expected behaviour: Second dialog is closed and first is shown OR ubuntu-bug closes completely. Observerd behaviour: ubuntu-bug hangs. No console output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1429496/+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 1429568] Re: powerd crashed with SIGABRT in ua_sensors_proximity_new()
*** This bug is a duplicate of bug 1420385 *** https://bugs.launchpad.net/bugs/1420385 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1420385, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1429568/+attachment/4337937/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1429568/+attachment/4337939/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1429568/+attachment/4337941/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1429568/+attachment/4337942/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1429568/+attachment/4337943/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1429568/+attachment/4337944/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1429568/+attachment/4337945/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1420385 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429568 Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() Status in powerd package in Ubuntu: New Bug description: possible related to #1338021 and/or #1351314 just switched to systemd by default ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: powerd 0.16+15.04.20150219-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Sun Mar 8 07:39:03 2015 ExecutablePath: /usr/bin/powerd InstallationDate: Installed on 2014-04-12 (329 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Daily i386 (20140411) ProcCmdline: /usr/bin/powerd Signal: 6 SourcePackage: powerd StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/i386-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/i386-linux-gnu/libubuntu_application_api.so.2 ua_sensors_proximity_new () from /usr/lib/i386-linux-gnu/libubuntu_application_api.so.2 powerd_sensors_init() () Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() UpgradeStatus: Upgraded to vivid on 2015-01-24 (42 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1429568/+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 1429569] Re: package linux-image-3.13.0-46-generic 3.13.0-46.77 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 255
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1429569 Title: package linux-image-3.13.0-46-generic 3.13.0-46.77 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 255 Status in initramfs-tools package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-46-generic 3.13.0-46.77 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adilson2019 F pulseaudio /dev/snd/controlC0: adilson2019 F pulseaudio Date: Sat Mar 7 08:53:28 2015 DuplicateSignature: package:linux-image-3.13.0-46-generic:3.13.0-46.77:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 255 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 255 HibernationDevice: RESUME=UUID=f63ee586-c464-414c-a272-1c4647f36edc InstallationDate: Installed on 2014-11-06 (121 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: ECS A880GM-M6 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=de9c63c5-6c2b-4ef0-a4c2-dbf1a5938ccf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: SourcePackage: initramfs-tools Title: package linux-image-3.13.0-46-generic 3.13.0-46.77 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 255 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: A880GM-M6 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd08/11/2010:svnECS:pnA880GM-M6:pvr1.0:rvnECS:rnA880GM-M6:rvr1.0:cvnECS:ct3:cvr: dmi.product.name: A880GM-M6 dmi.product.version: 1.0 dmi.sys.vendor: ECS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1429569/+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 1421938] Re: asked for permission to unmount partition while extracting file with file-roller
This looks related, were you trying to look at an iso? It sounds a bit like you were trying to look at an ISO which got loop-mounted, then tracker jumped at it, and tried to unmount it again? Feb 14 22:39:23 duhast gnome-session[6392]: (tracker-extract:6756): libmediaart-WARNING **: Unmount operation failed, adding back mount point... Feb 14 22:39:23 duhast gnome-session[6392]: (tracker-miner-fs:6797): Tracker-WARNING **: Unmount operation failed, adding back mount point... Feb 14 22:39:23 duhast gnome-session[6392]: (tracker-extract:6756): Tracker-WARNING **: Unmount operation failed, adding back mount point... Feb 14 22:39:49 duhast polkitd(authority=local)[1227]: Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-unmount-others for system-bus-name::1.70 [/usr/lib/gvfs/gvfs-udisks2-volume-monitor] (owned by unix-user:darkness) ** Package changed: systemd (Ubuntu) = tracker (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1421938 Title: asked for permission to unmount partition while extracting file with file-roller Status in tracker package in Ubuntu: New Bug description: I just tried to extract a file using file-roller and was then asked for permission to umount a partition, seems kind of fishy to me, will attach output of journalctl, but not currently booted with debug (I don't think) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1421938/+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 1253693] Re: top status bar missing shutdown button, clock, sound icon and more on upgrade to 13.10
experiencing the same problem with 14.10. not in the beginning, it was fine for a couple of months. an upgrade in the last 2 weeks cased to disappear the shutdown entry and user menu. it looks like was known before from gnome panel, where there are a lot of how to reset entries in google. but this seems not to work here? gconftool-2 --recursive-unset /apps/panel killall gnome-panel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1253693 Title: top status bar missing shutdown button, clock, sound icon and more on upgrade to 13.10 Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-session package in Ubuntu: Confirmed Bug description: This bug has been split from #1239710 as the branch for which changing launcher placement to all displays does not work. Every time I login, without fail, the top status bar is missing the gear icon for shutdown, the date, the sound icon and some others. The icons do show from the login window. So if I let the session time out so that the screen locks, I the gear icon appears in the top status bar and works. I have also added a new user to see if the issue has something to do with my account. The new user also has an empty top status bar. The issue happens for both dual monitor and single monitor configurations. When the second monitor is connected, setting launcher placement to all displays does not solve the problem. Neither does mirroring the displays. Everything worked just fine with 13.04. The problem appeared immediately following upgrade to 13.10. mark@mark-desktop:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1253693/+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 1424724] Re: package udev 204-5ubuntu20.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
As long as the bug is not automatically purged (which would mean duplicates would be missed), this should be fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1424724 Title: package udev 204-5ubuntu20.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in systemd package in Ubuntu: Invalid Bug description: System stopped responding. After a hard reboot, several devices were not detected. Hardware detection seems to work on issuing udevadm.upgrade hwdb --update manually. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.10 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.7 Architecture: amd64 CustomUdevRuleFiles: 60-ssd-scheduler.rules 99-usb.rules 99-ikalogic.rules~ Date: Mon Feb 23 21:52:15 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DuplicateSignature: package:udev:204-5ubuntu20.10:subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2014-05-24 (274 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Inspiron 3437 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=5ae9f976-4a9d-4da4-94dd-0d0c6b4088bf ro vesafb.nonsense=1 quiet splash vt.handoff=7 SourcePackage: systemd Title: package udev 204-5ubuntu20.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UdevLog: UpgradeStatus: Upgraded to trusty on 2014-07-06 (232 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0Y004V dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1424724/+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 1382789] Re: If I plug a second monitor into my laptop while its sleeping, and then wake it up, the lock screen freezes
Hello, I have since upgraded to 14.10, so I am not sure if any tests I could do would be of relevance anymore. Let me know though. //-- James Robb //-- +354.666.0887 (Iceland/Ísland) //-- I am migrating away from my ja...@gearedinteractive.ca address //-- Please send new communications to me at m...@jamesrobb.ca On 2015-02-23 04:34 PM, Christopher M. Penalver wrote: James Robb, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/04/product- support/product/inspiron-15-7537/drivers an update to your computer's buggy and outdated BIOS is available (A12). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status New. Thank you for your understanding. ** Tags added: bios-outdated-a12 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = 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/1382789 Title: If I plug a second monitor into my laptop while its sleeping, and then wake it up, the lock screen freezes Status in xorg package in Ubuntu: Incomplete Bug description: I find sometimes that if I plug in my monitor into my laptop (via an HDMI port, and and then HDMI to DVI connector) the monitor doesn't seem to be recognized by ubuntu and no image displays on it. I have gotten around this issue by having my laptop go to sleep and then plugging it in then, at which point I could wake it up and things would generally work. It seems lately though that the lock screen is just frozen upon waking up (though not always, I can't seem to notice any pattern or triggers), and therefore I usually have to restart X. What I expect to happen is to be able to plug in my secondary monitor at any point, at the lock screen, when at the desktop, or when the laptop is closed or asleep, and then just have it recgonized and work without needing to reboot or restart the display server. Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.14.1-031401-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 CurrentDesktop: Unity Date: Sat Oct 18 11:38:24 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05fa] InstallationDate: Installed on 2014-04-28 (172 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.14.1-031401-generic root=UUID=815b9800-4a18-417a-b15a-1bac42f91bfe ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 07PF9F 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.:bvrA10:bd07/18/2014:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 7537 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.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
[Touch-packages] [Bug 1429571] Re: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1429571 Title: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: i notice that when i use chrome to much , my laptop need to restart and if I don't do it , the Ubuntu force my laptop to . ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-32-generic 3.16.0-32.42 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ahmadalkaid 2998 F pulseaudio /dev/snd/controlC0: ahmadalkaid 2998 F pulseaudio Date: Sun Mar 8 02:35:16 2015 DuplicateSignature: package:linux-image-3.16.0-32-generic:3.16.0-32.42:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=696dd809-7429-49b0-97e0-88e45dc9318a InstallationDate: Installed on 2014-11-09 (119 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Sony Corporation VPCF111FX ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=9d4dfa20-1332-46fe-b809-81d7d4372b07 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-15 SourcePackage: initramfs-tools Title: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0280Y6 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:svnSonyCorporation:pnVPCF111FX:pvrC603MAKW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF111FX dmi.product.version: C603MAKW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1429571/+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 1429571] [NEW] package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: i notice that when i use chrome to much , my laptop need to restart and if I don't do it , the Ubuntu force my laptop to . ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-32-generic 3.16.0-32.42 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ahmadalkaid 2998 F pulseaudio /dev/snd/controlC0: ahmadalkaid 2998 F pulseaudio Date: Sun Mar 8 02:35:16 2015 DuplicateSignature: package:linux-image-3.16.0-32-generic:3.16.0-32.42:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=696dd809-7429-49b0-97e0-88e45dc9318a InstallationDate: Installed on 2014-11-09 (119 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Sony Corporation VPCF111FX ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=9d4dfa20-1332-46fe-b809-81d7d4372b07 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-15 SourcePackage: initramfs-tools Title: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0280Y6 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:svnSonyCorporation:pnVPCF111FX:pvrC603MAKW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF111FX dmi.product.version: C603MAKW dmi.sys.vendor: Sony Corporation ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1429571 Title: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: i notice that when i use chrome to much , my laptop need to restart and if I don't do it , the Ubuntu force my laptop to . ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-32-generic 3.16.0-32.42 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ahmadalkaid 2998 F pulseaudio /dev/snd/controlC0: ahmadalkaid 2998 F pulseaudio Date: Sun Mar 8 02:35:16 2015 DuplicateSignature: package:linux-image-3.16.0-32-generic:3.16.0-32.42:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=696dd809-7429-49b0-97e0-88e45dc9318a InstallationDate: Installed on 2014-11-09 (119 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Sony Corporation VPCF111FX ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=9d4dfa20-1332-46fe-b809-81d7d4372b07 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-15 SourcePackage: initramfs-tools Title: package linux-image-3.16.0-32-generic 3.16.0-32.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0280Y6 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias:
[Touch-packages] [Bug 1426362] Re: logind session files fill up /run space
** Package changed: systemd (Ubuntu) = systemd-shim (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1426362 Title: logind session files fill up /run space Status in systemd-shim package in Ubuntu: New Bug description: Under Ubuntu 14.10 (server), systemd fills up /run/systemd/sessions directory with files. The files are 240-260 bytes, but there are many As per default install, /run is on tmpfs with 50 MB size. After a couple of days, /run/ runs out of free space, which can cause not so funny errors, like failed kernel update (kernel postinst tries to create files here, then fails) As I see, thesefiles are releated to ssh sesssions, and yes there are plenty SSH connection to this host. Shouldn't systemd remove these old session files? # lsb_release -rd Description:Ubuntu 14.10 Release:14.10 # apt-cache policy systemd systemd: Installed: 208-8ubuntu8.2 Candidate: 208-8ubuntu8.2 Version table: *** 208-8ubuntu8.2 0 500 http://hu.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages 100 /var/lib/dpkg/status 208-8ubuntu8 0 500 http://hu.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1426362/+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 1421205] Re: Keyboard Volume up/down keys not work with pc105
Reassigning to X.org's evdev driver then. If evtest gets the correct events, then kernel, keymaps, and evdev are alright, but it seems the press events somehow get lost in X.org's input driver. ** Package changed: systemd (Ubuntu) = xserver-xorg-input-evdev (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1421205 Title: Keyboard Volume up/down keys not work with pc105 Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: Problem: Keyboard Volume up/down keys not work after installation If I set in keyboard control panel another shortcut for volume up/down (Ctrl+arrows) - this works right. If I set in keyboard control panel volume up/down keys from my keyboard, this assigned in control panel, but not works, even after restart. Pre-Diagnosis: No keydown event for volume_up/volume down Guide: https://wiki.ubuntu.com/Hotkeys/Troubleshooting System: Recently installed Ubuntu 14.10 x64 Keyboard: Genius GK-110001 (PS/2) xev application gets only release event (example for vol down): FocusOut event, serial 37, synthetic NO, window 0x641, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 37, synthetic NO, window 0x641, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 KeyRelease event, serial 37, synthetic NO, window 0x641, root 0x2eb, subw 0x0, time 77585669, (-285,866), root:(480,918), state 0x10, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False FocusOut event, serial 37, synthetic NO, window 0x641, mode NotifyNormal, detail NotifyNonlinear evtest application report gets all events (vol down press/release and vol up press/release): - Event: time 1423744203.723254, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae Event: time 1423744203.723254, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1 Event: time 1423744203.723254, -- SYN_REPORT Event: time 1423744203.781803, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae Event: time 1423744203.781803, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0 Event: time 1423744203.781803, -- SYN_REPORT Event: time 1423744204.330757, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0 Event: time 1423744204.330757, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1 Event: time 1423744204.330757, -- SYN_REPORT Event: time 1423744204.405869, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0 Event: time 1423744204.405869, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0 RESULT SCANCODE CURRENT_KEYCODE MEANING AE KEY_VOLUMEDOWN VOLUME DOWN B0 KEY_VOLUMEUPVOLUME UP MORE INFO: udev info /dev/input/event2 gets me: P: /devices/platform/i8042/serio0/input/input2/event2 N: input/event2 S: input/by-path/platform-i8042-serio-0-event-kbd E: DEVLINKS=/dev/input/by-path/platform-i8042-serio-0-event-kbd E: DEVNAME=/dev/input/event2 E: DEVPATH=/devices/platform/i8042/serio0/input/input2/event2 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_PATH=platform-i8042-serio-0 E: ID_PATH_TAG=platform-i8042-serio-0 E: ID_SERIAL=noserial E: MAJOR=13 E: MINOR=66 E: SUBSYSTEM=input E: USEC_INITIALIZED=8103 E: XKBLAYOUT=us,ru E: XKBMODEL=pc105 E: XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll E: XKBVARIANT=, ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: udev 208-8ubuntu8.2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity CustomUdevRuleFiles: 60-vboxdrv.rules Date: Thu Feb 12 23:12:51 2015 InstallationDate: Installed on 2015-02-11 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. P67A-D3-B3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic root=/dev/mapper/main-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FE dmi.board.name: P67A-D3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
[Touch-packages] [Bug 1424724] Re: package udev 204-5ubuntu20.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Hello Martin I ran sudo apt-get install -f, and it re-applied post-install configuration for udev. That seemed to solve the problem. Unfortunately, I have upgraded to 14.10, and there are no files in /var/crash which seem related to this, only more recent crashes. I suppose this bug can be left as it is unless it is reported again by others. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1424724 Title: package udev 204-5ubuntu20.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in systemd package in Ubuntu: Incomplete Bug description: System stopped responding. After a hard reboot, several devices were not detected. Hardware detection seems to work on issuing udevadm.upgrade hwdb --update manually. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.10 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.7 Architecture: amd64 CustomUdevRuleFiles: 60-ssd-scheduler.rules 99-usb.rules 99-ikalogic.rules~ Date: Mon Feb 23 21:52:15 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DuplicateSignature: package:udev:204-5ubuntu20.10:subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2014-05-24 (274 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Inspiron 3437 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=5ae9f976-4a9d-4da4-94dd-0d0c6b4088bf ro vesafb.nonsense=1 quiet splash vt.handoff=7 SourcePackage: systemd Title: package udev 204-5ubuntu20.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UdevLog: UpgradeStatus: Upgraded to trusty on 2014-07-06 (232 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0Y004V dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1424724/+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