[Touch-packages] [Bug 1342923] Re: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()
Is there a way to restart tracker? I'm not sure what this bug means, or why the program is even calling vprintf. https://wiki.ubuntu.com/Tracker -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1342923 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() Status in Meta-tracker: New Status in Ubuntu GNOME: New Status in “tracker” package in Ubuntu: Confirmed Bug description: i ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: tracker 1.0.2-1ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 16 21:39:09 2014 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-07-16 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x7f02dd2c9cb3 _IO_vfprintf_internal+7443: repnz scas %es:(%rdi),%al PC (0x7f02dd2c9cb3) ok source %es:(%rdi) (0xc0023630) not located in a known VMA region (needed readable region)! destination %al ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: tracker StacktraceTop: _IO_vfprintf_internal (s=s@entry=0x7f02d37fd600, format=optimized out, format@entry=0x7f02de5f5da0 Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s'), ap=ap@entry=0x7f02d37fd7a8) at vfprintf.c:1661 __GI___vasprintf_chk (result_ptr=0x7f02d37fd758, flags=1, format=0x7f02de5f5da0 Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s'), args=0x7f02d37fd7a8) at vasprintf_chk.c:66 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_new_valist () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() 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/tracker/+bug/1342923/+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 1345463] Re: Banshee.exe crashed with SIGSEGV in conservatively_pin_objects_from()
** Package changed: gstreamer0.10 (Ubuntu) = gstreamer1.0 (Ubuntu) ** 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 gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1345463 Title: Banshee.exe crashed with SIGSEGV in conservatively_pin_objects_from() Status in “gstreamer1.0” package in Ubuntu: New Bug description: (( ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: libgstreamer0.10-0 0.10.36-1.2ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 14:15:54 2014 ExecutablePath: /usr/lib/banshee/Banshee.exe InstallationDate: Installed on 2014-05-01 (80 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) InterpreterPath: /usr/bin/mono-sgen ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued Signal: 11 SourcePackage: gstreamer0.10 StacktraceTop: conservatively_pin_objects_from (start=0x7f8faf7feffc, end=0x7f8faf7ff000, start_nursery=start_nursery@entry=0x7f901e00, end_nursery=end_nursery@entry=0x7f901e40, pin_type=pin_type@entry=0) at sgen-gc.c:1478 scan_thread_data (start_nursery=0x7f901e00, end_nursery=end_nursery@entry=0x7f901e40, precise=precise@entry=0, queue=queue@entry=0x983120 gray_queue) at sgen-gc.c:4057 pin_from_roots (start_nursery=optimized out, end_nursery=end_nursery@entry=0x7f901e40, queue=0x983120 gray_queue) at sgen-gc.c:1537 collect_nursery (unpin_queue=unpin_queue@entry=0x0, finish_up_concurrent_mark=finish_up_concurrent_mark@entry=0) at sgen-gc.c:2586 collect_nursery (finish_up_concurrent_mark=0, unpin_queue=0x0) at sgen-gc.c:3547 Title: Banshee.exe crashed with SIGSEGV in conservatively_pin_objects_from() UpgradeStatus: Upgraded to utopic on 2014-07-12 (7 days ago) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1345463/+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 1345488] [NEW] package gir1.2-gtk-3.0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/girepository-1.0/Gdk-3.0.typelib' to '/usr/lib/gireposi
Public bug reported: getting error message while updating packages ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gir1.2-gtk-3.0 3.10.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sun Jul 20 12:54:25 2014 DuplicateSignature: package:gir1.2-gtk-3.0:3.10.8-0ubuntu1:cannot copy extracted data for './usr/lib/girepository-1.0/Gdk-3.0.typelib' to '/usr/lib/girepository-1.0/Gdk-3.0.typelib.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/girepository-1.0/Gdk-3.0.typelib' to '/usr/lib/girepository-1.0/Gdk-3.0.typelib.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-07-14 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gtk+3.0 Title: package gir1.2-gtk-3.0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/girepository-1.0/Gdk-3.0.typelib' to '/usr/lib/girepository-1.0/Gdk-3.0.typelib.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1345488 Title: package gir1.2-gtk-3.0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/girepository-1.0/Gdk-3.0.typelib' to '/usr/lib/girepository-1.0/Gdk-3.0.typelib.dpkg-new': unexpected end of file or stream Status in “gtk+3.0” package in Ubuntu: New Bug description: getting error message while updating packages ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gir1.2-gtk-3.0 3.10.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sun Jul 20 12:54:25 2014 DuplicateSignature: package:gir1.2-gtk-3.0:3.10.8-0ubuntu1:cannot copy extracted data for './usr/lib/girepository-1.0/Gdk-3.0.typelib' to '/usr/lib/girepository-1.0/Gdk-3.0.typelib.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/girepository-1.0/Gdk-3.0.typelib' to '/usr/lib/girepository-1.0/Gdk-3.0.typelib.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-07-14 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gtk+3.0 Title: package gir1.2-gtk-3.0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/girepository-1.0/Gdk-3.0.typelib' to '/usr/lib/girepository-1.0/Gdk-3.0.typelib.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1345488/+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 1345505] [NEW] lightdm leaks keystrokes to window behind greeter
*** This bug is a security vulnerability *** Public security bug reported: When my machine comes out of suspend, I am shown the lightdm greeter. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) ** Affects: lightdm (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug third-party-packages utopic ** Information type changed from Public to Public Security -- 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/1345505 Title: lightdm leaks keystrokes to window behind greeter Status in “lightdm” package in Ubuntu: New Bug description: When my machine comes out of suspend, I am shown the lightdm greeter. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1345505/+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 1345533] Re: [hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on
From http://launchpadlibrarian.net/180157436/mir_0.4.1%2B14.10.20140714-0ubuntu1_0.5.0%2B14.10.20140717-0ubuntu1.diff.gz it seems that the reason is that now this error is fatal, while before it wasn't even checking the return value. Do we need this error to be fatal? ** Also affects: mir Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1345533 Title: [hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on Status in Mir: New Status in “mir” package in Ubuntu: New Bug description: Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5 (hammerhead), as it fails to turn the vsync signal on. This is what I get from logcat: D/libEGL ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so D/libEGL ( 3038): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so D/libEGL ( 3038): loaded /vendor/lib/egl/libGLESv2_adreno.so I/qdutils ( 3038): Right Split=0 D/qdhwcomposer( 3038): int qhwc::adRead(): /sys/class/graphics/fb2/ad could not be opened : No such file or directory I/qdhwcomposer( 3038): Initializing Qualcomm Hardware Composer I/qdhwcomposer( 3038): MDP version: 500 I/Adreno-EGL( 3038): qeglDrvAPI_eglInitialize:320: EGL 1.4 QUALCOMM Build: I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13 D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, width = 1080 D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, height = 1920 I/Adreno-EGL( 3038): qeglDrvAPI_eglInitialize:320: EGL 1.4 QUALCOMM Build: I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13 I/qdhwcomposer( 3038): hwc_registerProcs I/qdhwcomposer( 3038): Initializing UEVENT Thread I/qdhwcomposer( 3038): Initializing VSYNC Thread I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=0 from /sys/class/graphics/fb0/vsync_event I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=1 from /sys/class/graphics/fb1/vsync_event D/qdhwcomposer( 3038): hwc_blank: Unblanking display: 0 D/qdhwcomposer( 3038): hwc_blank: Done unblanking display: 0 E/qdhwcomposer( 3038): hwc_vsync_control: vsync control failed. Dpy=0, enable=1 : Operation not supported W/libEGL ( 3038): eglTerminate() called w/ 1 objects remaining E/libEGL ( 3038): validate_display:263 error 3001 (EGL_NOT_INITIALIZED) I/ServiceManager( 913): service 'display.qservice' died The vsync control failed message was always there, and Mir 0.4 worked fine with it still. System compositor log: root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log ERROR: /build/buildd/mir-0.5.0+14.10.20140717/src/platform/graphics/android/real_hwc_wrapper.cpp(75): Throw in function virtual void mir::graphics::android::RealHwcWrapper::vsync_signal_on() const Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: error turning vsync signal on. rc = ffa1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1345533/+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 1283826] Re: lightdm hangs after updates
An update. I had written here that I seemed to be affected by this bug too, but I remembered later that just before running the Software Updater gui tool I had enabled the pre-released updates update source. After the update the system wouldn't boot, and seemed totally hosed. But I had a backup of the root partition made with fsarchiver and so I was able to restore it. I did that, then just now tried disabling, then enebling one at a time, all of the sources and PPAs that I had been using---excpt for that pre-released updates source. The updates went without a hitch, and it seems all good. So in my case the bug report was seemingly a false alarm, and I just wanted to let y'all know. -- 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/1283826 Title: lightdm hangs after updates Status in GDM: The Gnome Display Manager: New Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: I've updated today my Trusy Thar installation. I can't login to Unity, with my account, or a guest account. Lightdm hangs after password input, or after I click on the Guest account. Also, I used to auto-login. Now it greets me with the screen where I must input my password. After inputing it, lightdm hangs and I can't login. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Sun Feb 23 23:16:24 2014 InstallationDate: Installed on 2014-01-25 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140115) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=cristi autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1283826/+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 1283826] Re: lightdm hangs after updates
ps: I hid my first comments because they now seems not to be really helping. -- 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/1283826 Title: lightdm hangs after updates Status in GDM: The Gnome Display Manager: New Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: I've updated today my Trusy Thar installation. I can't login to Unity, with my account, or a guest account. Lightdm hangs after password input, or after I click on the Guest account. Also, I used to auto-login. Now it greets me with the screen where I must input my password. After inputing it, lightdm hangs and I can't login. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Sun Feb 23 23:16:24 2014 InstallationDate: Installed on 2014-01-25 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140115) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=cristi autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1283826/+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 1323822] Re: Firefox can not play some WebM videos generated by avconv on Trusty
@Mossroy: I posted in May already that upstream avconv fixes the issue. Thanks for your work, it finally works now. :) -- 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/1323822 Title: Firefox can not play some WebM videos generated by avconv on Trusty Status in The Mozilla Firefox Browser: Confirmed Status in the libav multimedia framework: Fix Released Status in “firefox” package in Ubuntu: Invalid Status in “libav” package in Ubuntu: Fix Released Bug description: Steps to reproduce : - Download the source H.264 video attached to this bug - On a Trusty machine, convert this video to WebM with avconv -i P5270914.MOV P5270914-trusty.webm. It should give the same result as attached - Open this webm file in Totem or in VLC : it plays correctly - Open this webm file in Firefox 29. When you click on play, it goes directly to the end and does not show anything - Open this same webm file in Chromium (tested with version 34) : it plays correctly If you generate the WebM file on Precise, with the same command-line, it plays correctly in Firefox (see attached P5270914-precise.webm). So I suppose it comes from a difference in the way avconv does the conversion, that is not correctly supported by Firefox All tests are made with Precise and Trusty amd64, with all current updates. Firefox version 29.0 on both avconv 9.13-0ubuntu0.14.04.1 on Trusty, and 0.8.10-0ubuntu0.12.04.1 on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1323822/+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 1301549] Re: Black screen after logging in after resume in Xubuntu 14.04
*** This bug is a duplicate of bug 1303736 *** https://bugs.launchpad.net/bugs/1303736 This solution also does not work with Ubuntu 14.04 on my Lendovo T61. I'm using the Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller. Doing this actually prevented my laptop from suspending. The screen would shut off when I closed the lid, but the laptop was still on. Opening the lid didn't turn on the display. I had to move the mouse or hit a key. After entering the password the screen still went blank. -- 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/1301549 Title: Black screen after logging in after resume in Xubuntu 14.04 Status in “lightdm” package in Ubuntu: Confirmed Bug description: Occasionally, when resuming Xubuntu 14.04 after hibernating it before, the screen is very dark. I must turn it bright with Fn+F5 then. After entering my password, I only see a black screen and I have to restart lightdm in order to be able to continue work. $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.13-0ubuntu1 Uname: Linux 3.14.0-031400-generic i686 ApportVersion: 2.14-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Wed Apr 2 20:20:16 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-21 (12 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225) LightdmGreeterLog: ** (lightdm-gtk-greeter:1278): WARNING **: Failed to load user background: Datei »/home/michael/Downloads/Not_My_Tux_by_Twarrior.jpg« konnte nicht geöffnet werden: Keine Berechtigung ** (lightdm-gtk-greeter:1278): WARNING **: Failed to load user image: Datei »/home/michael/.face« konnte nicht geöffnet werden: Keine Berechtigung init: indicator-power-main-Prozess (1323) wurde von TERM-Signal beendet init: indicator-sound-main-Prozess (1325) wurde von TERM-Signal beendet SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1301549/+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 1322055] Re: Create SMS and choose a contact from popup list
** Branch linked: lp:~iahmad/ubuntu-autopilot-tests/add-recipient-to- sms-bug1322055 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1322055 Title: Create SMS and choose a contact from popup list Status in Ubuntu Autopilot Tests: In Progress Status in “messaging-app” package in Ubuntu: Fix Released Bug description: Prerequisites:There must be a contact in the contacts database. 1.Open messaging app 2.Select 'Compose' from bottom bar 3.Click the Add Contact icon 4.Choose the contact from the list 5.Ensure that the chosen contact is in the list of added contacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-autopilot-tests/+bug/1322055/+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 1342903] Re: unity retains focus on virtualbox session when locked
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- 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/1342903 Title: unity retains focus on virtualbox session when locked Status in “unity” package in Ubuntu: Confirmed Bug description: While using virtualbox in fullscreen mode, CTRL + ALT + L, leaves focus with the virtual machine. However this still locks the host's unity session. This leaves all key events trapped in the virtual machine, so typing in your password becomes impossible. After a reboot all functionality returned. This could be a potential security hazard, depending on the virtual machine being used, as it allows arbitrary commands to be executed through a locked unity session without any authentication. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1342903/+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 713985] Re: [armel] Function tgammal has precision issues in version 2.12.1-0ubuntu10.2 on ARM
It would be great to know in more details how to get the fix mentioned
on an armhfl Ubuntu 12.10 (no, we cannot upgrade the system,
unfortunately).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/713985
Title:
[armel] Function tgammal has precision issues in version
2.12.1-0ubuntu10.2 on ARM
Status in Linaro Toolchain Miscellanies:
Fix Released
Status in “eglibc” package in Ubuntu:
Confirmed
Bug description:
Consider the following test program :
#include stdio.h
#include math.h
int
main (int argc,
char* argv[])
{
long double x = 6.0;
printf(tgammal (%.20Lf)=%.20Lfn, x, tgammal(x));
return 0;
}
When run on 2.12.1-0ubuntu10.2, the result is :
tgammal (6.)=119.97157829
while when run on 2.11.2-11 (glibc's unstable), the result is :
tgammal (6.)=119.8612
The second result is acceptable, while the second isn't. This makes
sage (http://www.sagemath.org) unhappy...
To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-toolchain-misc/+bug/713985/+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 1343802] Re: Installation of cgmanager prevents booting with systemd
FTR, I have tested systemd 208 packages in http://people.canonical.com/~pitti/tmp/systemd-208/ for amd64 and armhf. Note that the newer systemd-shim code itself should not cause any regression at all, as logind 204 does not call it. But starting cgmanager might of course interfere with logind. My system has run fine for several days though (current utopic, logind 204, with upstart), so I can't reproduce this problem. -- 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/1343802 Title: Installation of cgmanager prevents booting with systemd Status in “cgmanager” package in Ubuntu: Confirmed Status in “systemd-shim” package in Ubuntu: Confirmed Bug description: I have a completely upgraded Ubuntu Utopic development branch setup, with proprietary nvidia drivers installed. I have set my booting system to boot with systemd instead of the upstart one. The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager. However, installation of cgmanager (versions 0.26-0ubuntu5 or 0.27-0ubuntu7) does not complete booting with systemd. Not even tty1 is created and thus gdm (which I use instead of lightdm) is not started. I have the newest systemd installed (version 204-14ubuntu2). Booting with upstart on the other hand goes just fine. If I downgrade systemd to version 6-3 (and remove package cgmanager) all is well again and systemd booting is fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1343802/+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 1233578] [NEW] [osk] Hebrew symbols revised
You have been subscribed to a public bug: I've just noticed the hebrew-symbols.xml file and I have some corrections. The New Sheqel sign should be in higher priority: key binding label=₪ / /key key binding label=$ / /key key binding label=€ / /key key binding label=£ / /key key binding label=¥ / /key key binding label=% / /key Next there are these changes: Adding Geresh (U+05F3) - Often used. Adding Gershayim (U+05F4) - Often used (for acronyms mostly). I would push apostrophe and quotes down the hierarchy in favor of these symbols. Please don't push any changes yet, I need a review from the Israeli community. ** Affects: ubuntu-keyboard Importance: Medium Assignee: Michael Sheldon (michael-sheldon) Status: Confirmed ** Affects: ubuntu-ux Importance: Undecided Assignee: Benjamin Keyser (bjkeyser) Status: New ** Affects: ubuntu-keyboard (Ubuntu) Importance: High Status: Fix Released -- [osk] Hebrew symbols revised https://bugs.launchpad.net/bugs/1233578 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1233578] Re: [osk] Hebrew symbols revised
ubuntu-keyboard (0.99.trunk.phablet2+14.10.20140718-0ubuntu1) utopic; urgency=low [ Michael Sheldon ] * Enable the language menu when single pressing the language switcher button and add a settings item to the bottom of the language switcher. * Add numbers to the extended keys in the top row and extra punctuation on existing punctuation keys. Also adds the new sheqel symbol to the Hebrew keyboard and ensures that the Hebrew keyboard still displays keys when in capital mode. (LP: #1233578) * Fix incorrect Russian characters and layout (LP: #1321908) * Implement swiping behaviour for the selection of extended keys and fix popover position when selecting the same extended key after changing orientation. -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 18 Jul 2014 16:27:52 + ** Package changed: ubuntu = ubuntu-keyboard (Ubuntu) ** Changed in: ubuntu-keyboard (Ubuntu) Importance: Undecided = High ** Changed in: ubuntu-keyboard (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1233578 Title: [osk] Hebrew symbols revised Status in Ubuntu Keyboard: Confirmed Status in Ubuntu UX bugs: New Status in “ubuntu-keyboard” package in Ubuntu: Fix Released Bug description: I've just noticed the hebrew-symbols.xml file and I have some corrections. The New Sheqel sign should be in higher priority: key binding label=₪ / /key key binding label=$ / /key key binding label=€ / /key key binding label=£ / /key key binding label=¥ / /key key binding label=% / /key Next there are these changes: Adding Geresh (U+05F3) - Often used. Adding Gershayim (U+05F4) - Often used (for acronyms mostly). I would push apostrophe and quotes down the hierarchy in favor of these symbols. Please don't push any changes yet, I need a review from the Israeli community. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1233578/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
** No longer affects: oracle-jdk7-installer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Unknown Status in GTK+ GUI Toolkit: Fix Released Status in Unity GTK+ module: In Progress Status in “gtk+3.0” package in Ubuntu: New Status in “unity-gtk-module” package in Ubuntu: Fix Released Bug description: [Impact] Switching tabs between open source files with different file types in Eclipse causes the Source and Refactor menus to be empty in the global menu bar under Unity. This is a severe usability problem for many Eclipse users. The fix proposed has been available in a PPA and is well-tested. [Test Case] 1. Open a new project in Eclipse. 2. Open two files: one with a .java extension, another with a .txt extension. 3. Switch between the .java file and the .txt file and back again. 4. Open the Source or Refactor menu in the Unity global menu bar. Expected result: menus with menu items Actual result: empty menus for both [Regression Potential] The fix involves changes to both gtk and unity-gtk-module. The changes to gtk are minimal and only involve the reversal of a pair of signal emissions, in a part of the code (GtkMenuTracker) which is normally used by desktop environments, not typical user applications. Therefore regression potential for the gtk update is unlikely. The changes to unity-gtk-module involve emitting show and hide signals where they were none before has some regression potential for applications that are explicitly watching for when their menus are opening and closing. But this is rare for applications to do, and we likely would have already received bug reports for those that do. Being completely sure would require extensive testing across all gtk apps though. Both changes together have been available as a PPA, thoroughly tested for quite some time now. [Other Info] The changes to unity-gtk-module depend on the changes to gtk, so both must be tested in simultaneity. Suggested to upload both to trusty- proposed at the same time. Original bug report follows: === % === HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1345571] Re: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1300713 *** https://bugs.launchpad.net/bugs/1300713 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 #1300713, 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/1345571/+attachment/4157879/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1345571/+attachment/4157882/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1345571/+attachment/4157894/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1345571/+attachment/4157896/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1345571/+attachment/4157897/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1345571/+attachment/4157898/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1345571/+attachment/4157899/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1300713 ** 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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1345571 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() Status in “unity” package in Ubuntu: New Bug description: Random letters because I don't know why. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140711-0ubuntu1 Uname: Linux 3.16.0-031600rc4-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.4-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 CurrentDesktop: Unity Date: Sun Jul 20 13:54:54 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3969] InstallationDate: Installed on 2014-07-05 (15 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) MachineType: LENOVO 20071 ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=pl XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-031600rc4-generic root=UUID=3da1b177-6eec-425d-abe3-6f5add956745 ro acpi_osi=Linux pcie_aspm=force acpi_enforce_resources=lax acpi_backlight=vendor quiet splash SegvAnalysis: Segfault happened at: 0x7f0eecfa10fc:mov(%rdi),%rbx PC (0x7f0eecfa10fc) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 06/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 36CN15WW(V2.01) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Guam dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr36CN15WW(V2.01):bd06/08/2010:svnLENOVO:pn20071:pvrLenovoG565:rvnLENOVO:rnGuam:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: 20071 dmi.product.version: Lenovo G565 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri:
[Touch-packages] [Bug 1299975] Re: wireless script checks wrong sys file
* condition ubuntu 14.04-64bit $ lspci -nnv 02:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01) --- --- --- --- --- (snip) --- --- --- --- --- Kernel driver in use: ath9k * before proposed package AC plug Connect Disconnect. $ LANG=C apt list pm-utils Listing... Done pm-utils/trusty,now 1.4.1-13 all [installed] AC plug Connnect tail /var/log/pm-powersave.log --- --- --- --- --- (snip) --- --- --- --- --- Running hook /usr/lib/pm-utils/power.d/wireless false: cat: /sys/class/net/wlan0/device/enable: No such file or directory /usr/lib/pm-utils/power.d/wireless false: success. --- --- --- --- --- (snip) --- --- --- --- --- AC plug Disconnnect tail /var/log/pm-powersave.log --- --- --- --- --- (snip) --- --- --- --- --- Running hook /usr/lib/pm-utils/power.d/wireless true: cat: /sys/class/net/wlan0/device/enable: No such file or directory /usr/lib/pm-utils/power.d/wireless true: success. --- --- --- --- --- (snip) --- --- --- --- --- * after proposed package AC plug Connect Disconnect. $ LANG=C apt list pm-utils Listing... Done pm-utils/trusty-proposed,now 1.4.1-13ubuntu0.1 all [installed] AC plug Connnect tail /var/log/pm-powersave.log --- --- --- --- --- (snip) --- --- --- --- --- Running hook /usr/lib/pm-utils/power.d/wireless false: Turning powersave for wlan0 off...Error for wireless request Set Power Management (8B2C) : SET failed on device wlan0 ; Operation not supported. Failed. /usr/lib/pm-utils/power.d/wireless false: success. --- --- --- --- --- (snip) --- --- --- --- --- AC plug Disconnnect tail /var/log/pm-powersave.log --- --- --- --- --- (snip) --- --- --- --- --- Running hook /usr/lib/pm-utils/power.d/wireless true: Turning powersave for wlan0 on...Error for wireless request Set Power Management (8B2C) : SET failed on device wlan0 ; Operation not supported. Failed. /usr/lib/pm-utils/power.d/wireless true: success. --- --- --- --- --- (snip) --- --- --- --- --- * result The /usr/lib/pm-utils/power.d/wireless script operated normally. However, ath9k module or wireless device seems not to be supported. -- Turning powersave for wlan0 on...Error for wireless request Set Power Management (8B2C) : SET failed on device wlan0 ; Operation not supported. Failed. -- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1299975 Title: wireless script checks wrong sys file Status in “pm-utils” package in Ubuntu: Fix Released Status in “pm-utils” source package in Trusty: Fix Committed Bug description: TEST CASE: - on a machine with a wireless interface, run: PM_FUNCTIONS=/usr/lib/pm-utils/functions sh -ex /usr/lib/pm-utils/power.d/wireless true and verify that it fails with /sys/class/net/wlan0/device/enable: No such file or directory - install the update and run the command again and verify that the script continue beyond the point it stopped earlier, i.e. that it stops at a later point when running e.g. iwconfig - now powersaving for wireless via pm-utils should work as intended from the script REGRESSION POTENTIAL: - the functionality in the script was completely broken before, by fixing this bug any bug in the power management that were previously hidden may now be uncovered. On Trusty (beta), while trying to diagnose an issue with the wireless not connecting upon resume from standby, I discovered an invalid check in '/usr/lib/pm-utils/power.d/wireless'. The script checks '/sys/class/net/$1/device/enable' to see if the wireless device is enabled, failing to perform any configuration if this sys file does not exist. That happens to be the case for me (intel wireless), which the actual location is '/sys/class/net/$1/device/enabled' (enable - enabled). Changing the script to use the correct location has not fixed my wireless resume issue, but perhaps it is contributing to wireless issues for others. My wireless power-saving is correctly turned off upon resume now, though (it would get stuck in power-saving mode sometimes). $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy pm-utils pm-utils: Installed: 1.4.1-13 Candidate: 1.4.1-13 Version table: *** 1.4.1-13 0 500
[Touch-packages] [Bug 1192651] Re: subunit should depend on python3-junitxml
Is this an ubuntu specific issue? subunit2junitxml on Debian just use #!/usr/bin/python - in other words, Python 2. ** Changed in: subunit (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to subunit in Ubuntu. https://bugs.launchpad.net/bugs/1192651 Title: subunit should depend on python3-junitxml Status in “subunit” package in Ubuntu: Incomplete Bug description: $ trial --reporter=subunit landscape/lib/tests/test_bpickle.py | /usr/bin/subunit2junitxml python-junitxml (https://launchpad.net/pyjunitxml or http://pypi.python.org/pypi/junitxml) is required for this filter.Traceback (most recent call last): File /usr/bin/subunit2junitxml, line 27, in module from junitxml import JUnitXmlResult ImportError: No module named 'junitxml' There is no python3-junitxml in the repositories. python-junitxml is installed on the system but only contains 2.7 libraries. UPDATE: as of now, there is a python3-junitxml. It just needs to be included as a dep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subunit/+bug/1192651/+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 1268421] Re: Test failures if subunit module is installed
** Also affects: subunit (Ubuntu) Importance: Undecided Status: New ** Changed in: subunit (Ubuntu) Status: New = Triaged ** Changed in: subunit (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to subunit in Ubuntu. https://bugs.launchpad.net/bugs/1268421 Title: Test failures if subunit module is installed Status in SubUnit: Triaged Status in “subunit” package in Ubuntu: Triaged Bug description: Several tests in the test_subunit_filter.py file run the subunit- filter command as part of the test suite. They find the path to the file by doing: root = os.path.dirname(os.path.dirname(os.path.dirname(os.path.dirname(__file__ Which will fail if the subunit module has been installed to a virtualenv. This logic ought to work in both cases. To reproduce: autoreconf -vi mkdir -p build/py33 virtualenv -p python3.3 build/py33/ve . build/py33/ve/bin/activate easy_install testtools easy_install testscenarios python setup.py install cd build/py33 ../../configure make distcheck Leaving out the 'python setup.py install' makes all the tests work. To manage notifications about this bug go to: https://bugs.launchpad.net/subunit/+bug/1268421/+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 1345597] [NEW] On a Thinkpad X230 tablet, the rotate bezel button does not rotate touch device
Public bug reported: In Trusty, pressing the rotate button on the bezel of a Thinkpad X230 tablet - rotates the orientation of the display in steps of 90° - rotates the orientation of the input device for the stylus accordingly (which is good, it did not work in saucy) - BUT it does NOT rotate the orientation of the touch screen device (which makes using the touch screen impossible) Please do rotate the orientation of the touch screen input device synchronously with screen orientation. This will be such a useful feature, once it works! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 Date: Sun Jul 20 16:14:17 2014 DistUpgraded: 2014-04-18 10:31:00,413 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2013-04-12 (463 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: LENOVO 34382AG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=/dev/mapper/vg-lv--root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-18 (93 days ago) dmi.bios.date: 02/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GCET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 34382AG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET92WW(2.52):bd02/25/2013:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34382AG dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Jul 20 15:56:47 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1345597 Title: On a Thinkpad X230 tablet, the rotate bezel button does not rotate touch device Status in “xorg” package in Ubuntu: New Bug description: In Trusty, pressing the rotate button on the bezel of a Thinkpad X230 tablet - rotates the orientation of the display in steps of 90° - rotates the orientation of the input device for the stylus accordingly (which is good, it did not work in saucy) - BUT it does NOT rotate the orientation of the touch screen device (which makes using the touch screen impossible) Please do rotate the orientation of the touch screen input device synchronously with screen orientation. This will be such a useful feature, once it works! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 Date: Sun Jul 20 16:14:17 2014
Re: [Touch-packages] [Bug 1343802] Re: Installation of cgmanager prevents booting with systemd
Harry [2014-07-20 13:59 -]: Can you reproduce the bug with systemd booting? No, that works fine as well, I tested both before I uploaded the new systemd-shim. -- 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/1343802 Title: Installation of cgmanager prevents booting with systemd Status in “cgmanager” package in Ubuntu: Confirmed Status in “systemd-shim” package in Ubuntu: Confirmed Bug description: I have a completely upgraded Ubuntu Utopic development branch setup, with proprietary nvidia drivers installed. I have set my booting system to boot with systemd instead of the upstart one. The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager. However, installation of cgmanager (versions 0.26-0ubuntu5 or 0.27-0ubuntu7) does not complete booting with systemd. Not even tty1 is created and thus gdm (which I use instead of lightdm) is not started. I have the newest systemd installed (version 204-14ubuntu2). Booting with upstart on the other hand goes just fine. If I downgrade systemd to version 6-3 (and remove package cgmanager) all is well again and systemd booting is fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1343802/+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 1345606] [NEW] Can't create amd64 chroot - Unable to locate package g++-x86_64-linux-gnu
Public bug reported: In Trusty when I run the command: sudo click chroot -a amd64 -f ubuntu-sdk-14.04 -s trusty create it fails with: E: Unable to locate package g++-x86_64-linux-gnu E: Couldn't find any package by regex 'g++-x86_64-linux-gnu' E: Unable to locate package pkg-config-x86_64-linux-gnu Command returned 100: schroot -u root -c source:click-ubuntu-sdk-14.04-amd64 -- /finish.sh Click version: 0.4.21.1 ** Affects: click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1345606 Title: Can't create amd64 chroot - Unable to locate package g++-x86_64-linux- gnu Status in “click” package in Ubuntu: New Bug description: In Trusty when I run the command: sudo click chroot -a amd64 -f ubuntu-sdk-14.04 -s trusty create it fails with: E: Unable to locate package g++-x86_64-linux-gnu E: Couldn't find any package by regex 'g++-x86_64-linux-gnu' E: Unable to locate package pkg-config-x86_64-linux-gnu Command returned 100: schroot -u root -c source:click-ubuntu-sdk-14.04-amd64 -- /finish.sh Click version: 0.4.21.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1345606/+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 1329014] Re: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
Hello, I've found myself, and resolve the latest issue ... I've made a test with the guest account and i've noticed sound is working well. So i've made a backup of pulse folder (~/joe/.config/pulse/) and then i've delete all settings in the pulse folder, and restart the system. Now it seems to be fixed. Sound Panel is working again and have a list of all my soundcards. Joe -- 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/1329014 Title: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: newage@newage-desktop:~$ aplay -l Lista PLAYBACK de dispozitive placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 0: emu10k1 [ADC Capture/Standard PCM Playback] subdispozitive: 32/32 Subdispozitiv #0: subdevice #0 Subdispozitiv #1: subdevice #1 Subdispozitiv #2: subdevice #2 Subdispozitiv #3: subdevice #3 Subdispozitiv #4: subdevice #4 Subdispozitiv #5: subdevice #5 Subdispozitiv #6: subdevice #6 Subdispozitiv #7: subdevice #7 Subdispozitiv #8: subdevice #8 Subdispozitiv #9: subdevice #9 Subdispozitiv #10: subdevice #10 Subdispozitiv #11: subdevice #11 Subdispozitiv #12: subdevice #12 Subdispozitiv #13: subdevice #13 Subdispozitiv #14: subdevice #14 Subdispozitiv #15: subdevice #15 Subdispozitiv #16: subdevice #16 Subdispozitiv #17: subdevice #17 Subdispozitiv #18: subdevice #18 Subdispozitiv #19: subdevice #19 Subdispozitiv #20: subdevice #20 Subdispozitiv #21: subdevice #21 Subdispozitiv #22: subdevice #22 Subdispozitiv #23: subdevice #23 Subdispozitiv #24: subdevice #24 Subdispozitiv #25: subdevice #25 Subdispozitiv #26: subdevice #26 Subdispozitiv #27: subdevice #27 Subdispozitiv #28: subdevice #28 Subdispozitiv #29: subdevice #29 Subdispozitiv #30: subdevice #30 Subdispozitiv #31: subdevice #31 placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 2: emu10k1 efx [Multichannel Capture/PT Playback] subdispozitive: 8/8 Subdispozitiv #0: subdevice #0 Subdispozitiv #1: subdevice #1 Subdispozitiv #2: subdevice #2 Subdispozitiv #3: subdevice #3 Subdispozitiv #4: subdevice #4 Subdispozitiv #5: subdevice #5 Subdispozitiv #6: subdevice #6 Subdispozitiv #7: subdevice #7 placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 3: emu10k1 [Multichannel Playback] subdispozitive: 1/1 Subdispozitiv #0: subdevice #0 placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 4: p16v [p16v] subdispozitive: 1/1 Subdispozitiv #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: newage 2071 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 11 20:38:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-11 (0 days ago) InstallationMedia: It PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 failed Symptom_Card: SB0240 Audigy 2 Platinum 6.1 - SB Audigy 2 [SB0240] Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: newage 2071 F pulseaudio Symptom_Type: No sound at all Title: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2005 dmi.bios.vendor: Intel Corp. dmi.bios.version: BZ87510A.86A.0125.P34.0503312215 dmi.board.name: D875PBZ dmi.board.vendor: Intel Corporation dmi.board.version: AAC26680-205 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBZ87510A.86A.0125.P34.0503312215:bd03/31/2005:svn:pn:pvr:rvnIntelCorporation:rnD875PBZ:rvrAAC26680-205:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329014/+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
Now all of a sudden no sound from speakers, only from headphones... -- 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 1345658] [NEW] [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all
Public bug reported: sound not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti CurrentDesktop: Unity Date: Sun Jul 20 22:59:25 2014 InstallationDate: Installed on 2014-06-18 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti Symptom_Jack: Green Speaker, Rear Symptom_Type: No sound at all Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: PI945GCM dmi.board.vendor: Kobian dmi.board.version: ECS dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Kobian dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd08/16/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: PI945GCM dmi.product.version: 1.X dmi.sys.vendor: Kobian ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1345658 Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: sound not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti CurrentDesktop: Unity Date: Sun Jul 20 22:59:25 2014 InstallationDate: Installed on 2014-06-18 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti Symptom_Jack: Green Speaker, Rear Symptom_Type: No sound at all Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: PI945GCM dmi.board.vendor: Kobian dmi.board.version: ECS dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Kobian dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd08/16/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: PI945GCM dmi.product.version: 1.X dmi.sys.vendor: Kobian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1345658/+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 1345682] [NEW] fsck on 24TB ext4 keeps crashing
Public bug reported: date; fsck -vy /dev/mapper/raid61p1 ;date Thu Jul 17 11:54:21 PDT 2014 fsck from util-linux 2.20.1 I can't get my ext4 24TB to fsck clean. there came a whole bunch of file stat problems after a clean reboot. I tried 3 times so far, and each does something like segfault. I looked twice, and the errors were different, but was able to capture one output. The system has 6GB ram, and it used up all the memory. ended up adding 25GB of swap as fsck seems to use up a huge amount of memory. After a long while, usually after mem use is 90%, I come back to see the fsck has crashed and file system is still not clean. The reboot was clean and should not have caused any corruption. the system is using ubuntu-14.04 # uname -a Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@gigabyte133:~# I had to use the 64 bit version since the 32 bit version I couldn't get more than 15TB file system built and read that there were compatibility problems between 32bit version with the -O 64bit and the 64 bit version so just built the whole thing in 64 bit ubuntu.. e2fsck 1.42.9 (4-Feb-2014) /dev/mapper/raid61p1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 203167820 has compression flag set on filesystem without compression support. Clear? yes Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil) fsck.ext4[0x4266f1] /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670] fsck.ext4[0x4100f6]# lsb_release -va No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11c3d)[0x7fd38dc5fc3d] /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11f78)[0x7fd38dc5ff78] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_block_iterate3+0xa13)[0x7fd38dc60b13] fsck.ext4[0x4115c4] fsck.ext4[0x412699] fsck.ext4[0x412761] /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_get_next_inode_full+0x59)[0x7fd38dc6c9a9] fsck.ext4(e2fsck_pass1+0x8d8)[0x4130c8] fsck.ext4(e2fsck_run+0x52)[0x40deb2] fsck.ext4(main+0xd27)[0x40a0e7] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd38d072ec5] fsck.ext4[0x40bde6] Thu Jul 17 15:55:01 PDT 2014 # lsb_release -va No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu20.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sat Jul 19 18:49:32 2014 InstallationDate: Installed on 2014-07-11 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1345682 Title: fsck on 24TB ext4 keeps crashing Status in “util-linux” package in Ubuntu: New Bug description: date; fsck -vy /dev/mapper/raid61p1 ;date Thu Jul 17 11:54:21 PDT 2014 fsck from util-linux 2.20.1 I can't get my ext4 24TB to fsck clean. there came a whole bunch of file stat problems after a clean reboot. I tried 3 times so far, and each does something like segfault. I looked twice, and the errors were different, but was able to capture one output. The system has 6GB ram, and it used up all the memory. ended up adding 25GB of swap as fsck seems to use up a huge amount of memory. After a long while, usually after mem use is 90%, I come back to see the fsck has crashed and file system is still not clean. The reboot was clean and should not have caused any corruption. the system is using ubuntu-14.04 # uname -a Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@gigabyte133:~# I had to use the 64 bit version since the 32 bit version I couldn't get more than 15TB file system built and read that there were compatibility problems between 32bit version with the -O 64bit and the 64 bit version so just built the whole thing in 64 bit ubuntu.. e2fsck 1.42.9 (4-Feb-2014) /dev/mapper/raid61p1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 203167820 has compression flag set on
[Touch-packages] [Bug 1322784]
Could somebody running the Firefox that has this crash (i.e., 32-bit Ubuntu packages) attach the contents of about:buildconfig to this bug? (That is, just type about:buildconfig in the URL bar, save it to a file, and use the Add an attachment link above.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1322784 Title: Firefox crashes in flag_qsort during spellchecker initialization on x86 due to gcc bug Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Confirmed Status in “gcc-4.8” package in Ubuntu: Confirmed Bug description: The most common Firefox crash on Linux in Mozilla's crash-stats system is crashes in the function flag_qsort. These crashes occur: * only on x86 architecture * only on Ubuntu packages (and not on Mozilla's builds) * on precise and saucy and trusty (based on kernel versions reported with the crashes) and appear to be due to a compiler bug in the compiler used to generate Ubuntu's builds. (It could be a common compiler bug triggered by different compiler options or a compiler bug specific to Ubuntu's gcc.) The analysis that leads to the conclusion that this is a compiler bug is in https://bugzilla.mozilla.org/show_bug.cgi?id=983817 . In particular, the compiler is miscompiling an access to an element of an array of unsigned short as a 32-bit read, and when the unsigned short in question is the last one in the allocation and that allocation is aligned so that the byte following has a different 0x10 bit, this can lead to crashes. The most recent (whenever you follow the link) 7 days of crash reports are available at: https://crash- stats.mozilla.com/report/list?signature=flag_qsortproduct=Firefoxquery_type=containsrange_unit=weeks To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1322784/+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 1322784]
Er, never mind, I can extract it from the package in comment 23. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1322784 Title: Firefox crashes in flag_qsort during spellchecker initialization on x86 due to gcc bug Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Confirmed Status in “gcc-4.8” package in Ubuntu: Confirmed Bug description: The most common Firefox crash on Linux in Mozilla's crash-stats system is crashes in the function flag_qsort. These crashes occur: * only on x86 architecture * only on Ubuntu packages (and not on Mozilla's builds) * on precise and saucy and trusty (based on kernel versions reported with the crashes) and appear to be due to a compiler bug in the compiler used to generate Ubuntu's builds. (It could be a common compiler bug triggered by different compiler options or a compiler bug specific to Ubuntu's gcc.) The analysis that leads to the conclusion that this is a compiler bug is in https://bugzilla.mozilla.org/show_bug.cgi?id=983817 . In particular, the compiler is miscompiling an access to an element of an array of unsigned short as a 32-bit read, and when the unsigned short in question is the last one in the allocation and that allocation is aligned so that the byte following has a different 0x10 bit, this can lead to crashes. The most recent (whenever you follow the link) 7 days of crash reports are available at: https://crash- stats.mozilla.com/report/list?signature=flag_qsortproduct=Firefoxquery_type=containsrange_unit=weeks To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1322784/+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 1343020] Re: Realtek ALC889A No sound output
Okay, at least there is a workaround for this: Install alsa-tools-gui, start HDAJackRetask and override the Pin 0x1a with Headphone. Not a very nice solution, but its the only workaround I got to work. -- 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/1343020 Title: Realtek ALC889A No sound output Status in “alsa-driver” package in Ubuntu: New Bug description: I checked whole Google for this problem and tried very many things to solve it. Alsamixer does recognise if I plug in the headphones and does automute the speaker-sound but there is no sound on the headphones. The speakers work well. I installed some extern drivers by Realtek but this crashed the whole sound and I did a fresh installation of Ubuntu 14.04. The only thing I changed now is alsa- base.conf, I added the recommended line options snd-hda-intel model=mb5 for my Macbook. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tobias 1922 F pulseaudio tobias14404 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 17 01:29:33 2014 InstallationDate: Installed on 2014-07-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Internes Audio - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tobias 1922 F pulseaudio tobias14404 F pulseaudio Symptom_Jack: Green Headphone Out, Rear Symptom_Type: No sound at all Title: [MacBook5,2, Realtek ALC889A, Green Headphone Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB52.88Z.0088.B05.090416 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22788AA dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788AA dmi.modalias: dmi:bvnAppleInc.:bvrMB52.88Z.0088.B05.090416:bd04/16/09:svnAppleInc.:pnMacBook5,2:pvr1.0:rvnAppleInc.:rnMac-F22788AA:rvr:cvnAppleInc.:ct10:cvrMac-F22788AA: dmi.product.name: MacBook5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-07-16T22:29:29.018786 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1343020/+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 1345505] Re: lightdm leaks keystrokes to window behind greeter
It's actually unity showing a lock screen here, reassigning. ** Package changed: lightdm (Ubuntu) = unity (Ubuntu) ** Summary changed: - lightdm leaks keystrokes to window behind greeter + lock scren leaks keystrokes to window behind greeter -- 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/1345505 Title: lock scren leaks keystrokes to window behind greeter Status in “unity” package in Ubuntu: New Bug description: When my machine comes out of suspend, I am shown the lightdm greeter. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/+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 1345753] [NEW] [Aspire V5-552G, Realtek ALC282, Mic, Internal] No sound at all
Public bug reported: internal microphone will not register any sounds despite being turned on. the orange bars that usually record input level- this section shows orange bars but they do not move. I cannot use my program Rosetta Stone because it cannot get any sound input. This problem developed after I had been using rosetta stone successfully with their voice recognition feature. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bearcube 2800 F pulseaudio /dev/snd/pcmC1D0c: bearcube 2800 F...m pulseaudio /dev/snd/pcmC1D0p: bearcube 2800 F...m pulseaudio /dev/snd/controlC0: bearcube 2800 F pulseaudio CurrentDesktop: Unity Date: Sun Jul 20 16:42:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-15 (35 days ago) InstallationMedia: It PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bearcube 2800 F pulseaudio /dev/snd/pcmC1D0c: bearcube 2800 F...m pulseaudio /dev/snd/pcmC1D0p: bearcube 2800 F...m pulseaudio /dev/snd/controlC0: bearcube 2800 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [Aspire V5-552G, Realtek ALC282, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd05/28/2013:svnAcer:pnAspireV5-552G:pvrV2.02:rvnAcer:rnDazzle_RL:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-552G dmi.product.version: V2.02 dmi.sys.vendor: Acer ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1345753 Title: [Aspire V5-552G, Realtek ALC282, Mic, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: internal microphone will not register any sounds despite being turned on. the orange bars that usually record input level- this section shows orange bars but they do not move. I cannot use my program Rosetta Stone because it cannot get any sound input. This problem developed after I had been using rosetta stone successfully with their voice recognition feature. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bearcube 2800 F pulseaudio /dev/snd/pcmC1D0c: bearcube 2800 F...m pulseaudio /dev/snd/pcmC1D0p: bearcube 2800 F...m pulseaudio /dev/snd/controlC0: bearcube 2800 F pulseaudio CurrentDesktop: Unity Date: Sun Jul 20 16:42:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-15 (35 days ago) InstallationMedia: It PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bearcube 2800 F pulseaudio /dev/snd/pcmC1D0c: bearcube 2800 F...m pulseaudio /dev/snd/pcmC1D0p: bearcube 2800 F...m pulseaudio /dev/snd/controlC0: bearcube 2800 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [Aspire V5-552G, Realtek ALC282, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis
[Touch-packages] [Bug 1345766] [NEW] [1101HAGG, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound...
Public bug reported: when i run in terminal the next...ubuntu-bug -s audio everything is ok XUbuntu 14.04 Description:Ubuntu 14.04 LTS Release:14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dimitris 1849 F pulseaudio /dev/snd/pcmC0D0p: dimitris 1849 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Jul 21 00:19:20 2014 InstallationDate: Installed on 2014-07-12 (8 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Εσωτερικός ήχος - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or crackling sound Title: [1101HAGG, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0208 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1101HAGG dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0208:bd09/25/2009:svnASUSTeKComputerINC.:pn1101HAGG:pvrx.x:rvnASUSTeKComputerINC.:rn1101HAGG:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1101HAGG dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1345766 Title: [1101HAGG, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound... Status in “alsa-driver” package in Ubuntu: New Bug description: when i run in terminal the next...ubuntu-bug -s audio everything is ok XUbuntu 14.04 Description: Ubuntu 14.04 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dimitris 1849 F pulseaudio /dev/snd/pcmC0D0p: dimitris 1849 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Jul 21 00:19:20 2014 InstallationDate: Installed on 2014-07-12 (8 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Εσωτερικός ήχος - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or crackling sound Title: [1101HAGG, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0208 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1101HAGG dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0208:bd09/25/2009:svnASUSTeKComputerINC.:pn1101HAGG:pvrx.x:rvnASUSTeKComputerINC.:rn1101HAGG:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1101HAGG dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1345766/+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 1327007] Re: [Dell System Inspiron 15 7000 Series 7537, Realtek ALC3223, Speaker, Internal] Underruns, dropouts or crackling sound
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- 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/1327007 Title: [Dell System Inspiron 15 7000 Series 7537, Realtek ALC3223, Speaker, Internal] Underruns, dropouts or crackling sound Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: The audio constantly clicks overtop of what is played. This began occurring after fixing a previous bug where audio would not play through speakers. All that was done fixing this bug was uninstall and reinstall pulseaudio and the alsa-base. Occasionally the clicks will be replaced by random noise. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: seamus 1990 F pulseaudio /dev/snd/pcmC1D0p: seamus 1990 F...m pulseaudio /dev/snd/controlC0: seamus 1990 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 5 20:44:13 2014 InstallationDate: Installed on 2014-02-18 (107 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Underruns, dropouts, or crackling sound Title: [Dell System Inspiron 15 7000 Series 7537, Realtek ALC3223, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to trusty on 2014-03-23 (74 days ago) dmi.bios.date: 07/24/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0XJGC1 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.:bvrA01:bd07/24/2013:svnDellInc.:pnDellSystemInspiron157000Series7537:pvr:rvnDellInc.:rn0XJGC1:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron 15 7000 Series 7537 dmi.sys.vendor: Dell Inc. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-05T20:22:50.418923 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1327007/+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 1338183] Re: libpam-systemd and whoopsie upgrade failed from a clean install of Xubuntu 14.04
*** This bug is a duplicate of bug 1325142 *** https://bugs.launchpad.net/bugs/1325142 ** This bug has been marked a duplicate of bug 1325142 failure to update libpam-systemd in 14.04 due to missing logind init script -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1338183 Title: libpam-systemd and whoopsie upgrade failed from a clean install of Xubuntu 14.04 Status in “shadow” package in Ubuntu: Confirmed Bug description: System: Xubuntu 14.04 LTS Package info: PackageName CurrentUpgradeTo whoopsie 0.2.24.50.2.24.6 libpam-systemd 204-5ubuntu20 204-5ubuntu20.2 Error shown: Errors were encountered while processing: /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.3_i386.deb /var/cache/apt/archives/whoopsie_0.2.24.6_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) How to reproduce: 1. Run the following commands to prepare the image customization environment: sudo apt-get install squashfs-tools genisoimage mkdir ~/livecdtmp cp ~/Desktop/xubuntu-14.04-desktop-i386.iso ~/livecdtmp cd ~/livecdtmp mkdir mnt sudo mount -o loop xubuntu-14.04-desktop-i386.iso mnt mkdir extract-cd sudo rsync --exclude=/casper/filesystem.squashfs -a mnt/ extract-cd sudo unsquashfs mnt/casper/filesystem.squashfs sudo mv squashfs-root edit sudo cp /etc/resolv.conf edit/etc/ sudo cp /etc/hosts edit/etc/ sudo mount --bind /dev/ edit/dev sudo chroot edit mount -t proc none /proc mount -t sysfs none /sys mount -t devpts none /dev/pts export HOME=/root export LC_ALL=C dbus-uuidgen /var/lib/dbus/machine-id dpkg-divert --local --rename --add /sbin/initctl ln -s /bin/true /sbin/initctl 2. Enable the partner source by adding the following line to source.list: deb http://archive.canonical.com/ubuntu trusty partner deb-src http://archive.canonical.com/ubuntu trusty partner deb http://extras.ubuntu.com/ubuntu trusty main deb-src http://extras.ubuntu.com/ubuntu trusty main 3. apt-get update apt-get upgrade to get the error mentioned. Troubleshooting steps I have tried: 1. clean the apt cache folder and download the updates again, still failed. 2. empty the folder for customization environment(livecdtmp in this example), and do the steps again, tried at least 4 times, still failed. 3. tried to completely remove and reinstall whoopsie package, but failed to remove and reinstall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1338183/+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 1345658] Re: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all
13.068894] autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0) type:speaker [ 13.068901]speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.068904]hp_outs=1 (0xa/0x0/0x0/0x0/0x0) [ 13.068906]mono: mono_out=0x0 [ 13.068908]dig-out=0x10/0x0 [ 13.068910]inputs: [ 13.068914] Front Mic=0xb [ 13.068916] Rear Mic=0xc [ 13.068919] Line=0xf [ 13.068921] CD=0x15 Sysfs Files !!--- /sys/class/sound/hwC0D0/init_pin_configs: 0x0a 0x2221401f 0x0b 0x22a19020 0x0c 0x01119011 0x0d 0x01114010 0x0e 0x40f000f1 0x0f 0x01113012 0x10 0x01451130 0x11 0x40f000f2 0x15 0x9033012e 0x1b 0x40f000f3 /sys/class/sound/hwC0D0/driver_pin_configs: 0x0a 0x0221401f 0x0b 0x02a19020 0x0c 0x01a19020 0x0d 0x01114010 0x0e 0x408000f0 0x0f 0x01813022 0x10 0x074510a0 0x11 0x40c400f1 0x15 0x9037012e 0x1b 0x40e000f2 Advanced information - PCI Vendor/Device/Subsystem ID's !! 00:1b.0 0403: 8086:27d8 (rev 01) Subsystem: 1019:2633 seem driver fixup is still not correct for desktop , line out instead of speaker https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_sigmatel.c?id=0a4278464eba4bf98c0d6304c62a1116553125d3 try hda jack sense test to find the correct pin and use hda Jack retask to fix the pins -- 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/1345658 Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: sound not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti CurrentDesktop: Unity Date: Sun Jul 20 22:59:25 2014 InstallationDate: Installed on 2014-06-18 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti Symptom_Jack: Green Speaker, Rear Symptom_Type: No sound at all Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: PI945GCM dmi.board.vendor: Kobian dmi.board.version: ECS dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Kobian dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd08/16/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: PI945GCM dmi.product.version: 1.X dmi.sys.vendor: Kobian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1345658/+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 1125944] Re: (gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not root!
Van Halen's Maxwell Jump song is appreciated in comment #21. I too received this error today. I was guilty of running two terminal sessions a day or two ago and I am guilty of using gedit one time and sudo gedit another time on the same file if permission is denied the first time. Ubuntu 14.04 LTS, Kernel 3.15.6-blah blah-generic. -- 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/1125944 Title: (gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not root! Status in “ibus” package in Ubuntu: Won't Fix Bug description: RR i386 logged as gnome-classic (fallback) Seen that error for the first time while using a terminal: oem@oem-desktop:~$ sudo gedit /etc/default/grub (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! That one is own by Me (screenshot joined) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ibus 1.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Fri Feb 15 08:33:36 2013 MarkForUpload: True SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1125944/+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 1318954] Re: Error formatting disk Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0)
*** This bug is a duplicate of bug 1059872 *** https://bugs.launchpad.net/bugs/1059872 ** This bug has been marked a duplicate of bug 1059872 Error formatting disk using disk utility -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1318954 Title: Error formatting disk Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0) Status in GNOME Disks: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Confirmed Status in “udisks2” package in Ubuntu: Confirmed Status in “util-linux” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Debian: New Status in “util-linux” package in Debian: Fix Released Bug description: I get this error Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0) when I try to format a USB pendrive. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-disk-utility 3.10.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 13 10:34:46 2014 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2014-04-20 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1318954/+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 1243174] Re: updated to Ubuntu 13.10 'Power off warning' does go not turn off
*** This bug is a duplicate of bug 1345116 *** https://bugs.launchpad.net/bugs/1345116 ** This bug is no longer a duplicate of bug 1232454 Computer will suspend very soon because of inactivity. dialog when resuming from suspend ** This bug has been marked a duplicate of bug 1345116 Computer fails to autosuspend -- 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/1243174 Title: updated to Ubuntu 13.10 'Power off warning' does go not turn off Status in “indicator-power” package in Ubuntu: Incomplete Bug description: The power off warning indicator comes on automatically but does not turn off. This is a new something. is there a way to shut it down? Thanks Cliff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1243174/+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 1343971] Re: Scaling for high DPI mixes monitors
The windows content (for compliant applications) is scaled according to the Scale all windows contents setting in the Ubuntu Control Center. This is set by default to match the menu and title bars scale setting for the monitor with the smallest scale factor, but is selectable through the drop-down menu to choose another monitor or matching rule specifically. The content scale factor is not dependent on a primary or secndary screen. If the problem you are reporting is in the third-party Unity tweak tool you need to report it to the developers of that tool. ** Attachment added: screenshot of Displays panel in Control Center https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1343971/+attachment/4158362/+files/Displays_001.png -- 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/1343971 Title: Scaling for high DPI mixes monitors Status in “unity” package in Ubuntu: New Bug description: The scale factor of the primary screen only affects menus and titlebars (as expected, so far). The scale factor of the secondary screen affects menus and titlebars, PLUS application fonts. This behavior, in addition to not agree with the scale's label, is hard to handle. PS : I didn't touched unity tweaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1343971/+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 1345664] Re: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all
post pulseaudio verbose log seem pulseaudio remove line out / speaker path when there is only one pcm playback volume control Node 0x0d [Pin Complex] wcaps 0x400181: Stereo Control: name=Speaker Jack, index=0, device=0 Pincap 0x173f: IN OUT HP Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 Pin Default 0x01114010: [Jack] Speaker at Ext Rear Conn = 1/8, Color = Green DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x40: OUT VREF_HIZ Unsolicited: tag=06, enabled=1 Connection: 1 0x02 you have to fix the driver since there are enough volume controls at node 0x03, 0x04 and 0x05 Node 0x02 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Control: name=PCM Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=PCM Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name=STAC9221 A2 Analog, type=Audio, device=0 Amp-Out caps: N/A Amp-Out vals: [0x66 0x66] Converter: stream=0, channel=0 Power states: Power: setting=D0, actual=D0 Delay: 13 samples Node 0x03 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Converter: stream=0, channel=0 Power states: Power: setting=D0, actual=D0 Delay: 13 samples Node 0x04 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Converter: stream=0, channel=0 Power states: Power: setting=D0, actual=D0 Delay: 13 samples Node 0x05 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Converter: stream=0, channel=0 Power states: Power: setting=D0, actual=D0 Delay: 13 samples active profile: output:iec958-stereo+input:analog-stereo sinks: alsa_output.pci-_00_1b.0.iec958-stereo/#0: Built-in Audio Digital Stereo (IEC958) sources: alsa_output.pci-_00_1b.0.iec958-stereo.monitor/#0: Monitor of Built-in Audio Digital Stereo (IEC958) alsa_input.pci-_00_1b.0.analog-stereo/#1: Built-in Audio Analog Stereo ports: analog-input-microphone-front: Front Microphone (priority 8500, latency offset 0 usec, available: no) properties: device.icon_name = audio-input-microphone analog-input-microphone-rear: Rear Microphone (priority 8200, latency offset 0 usec, available: no) properties: device.icon_name = audio-input-microphone analog-input-linein: Line In (priority 8100, latency offset 0 usec, available: no) properties: analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: no) properties: device.icon_name = audio-headphones iec958-stereo-output: Digital Output (S/PDIF) (priority 0, latency offset 0 usec, available: unknown) properties: ** 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/1345664 Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I can't hear any sounds on the computer ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti /dev/snd/pcmC0D1p: vibhas 1745 F...m pulseaudio CurrentDesktop: Unity Date: Sun Jul 20 23:16:56 2014 InstallationDate: Installed on 2014-06-18 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti /dev/snd/pcmC0D1p: vibhas 1745 F...m pulseaudio Symptom_Jack: Green Speaker, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all
[Touch-packages] [Bug 1345664] Re: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all
should be Jack line out instead of Jack speaker if it is a desktop you need to file an upstream bug report 12.982457] snd_hda_intel :00:1b.0: irq 40 for MSI/MSI-X [ 13.068894] autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0) type:speaker [ 13.068901]speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 13.068904]hp_outs=1 (0xa/0x0/0x0/0x0/0x0) [ 13.068906]mono: mono_out=0x0 [ 13.068908]dig-out=0x10/0x0 [ 13.068910]inputs: [ 13.068914] Front Mic=0xb [ 13.068916] Rear Mic=0xc [ 13.068919] Line=0xf [ 13.068921] CD=0x15 /sys/class/sound/hwC0D0/init_pin_configs: 0x0a 0x2221401f 0x0b 0x22a19020 0x0c 0x01119011 0x0d 0x01114010 0x0e 0x40f000f1 0x0f 0x01113012 0x10 0x01451130 0x11 0x40f000f2 0x15 0x9033012e 0x1b 0x40f000f3 /sys/class/sound/hwC0D0/driver_pin_configs: 0x0a 0x0221401f 0x0b 0x02a19020 0x0c 0x01a19020 0x0d 0x01114010 0x0e 0x408000f0 0x0f 0x01813022 0x10 0x074510a0 0x11 0x40c400f1 0x15 0x9037012e 0x1b 0x40e000f2 -- 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/1345664 Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I can't hear any sounds on the computer ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti /dev/snd/pcmC0D1p: vibhas 1745 F...m pulseaudio CurrentDesktop: Unity Date: Sun Jul 20 23:16:56 2014 InstallationDate: Installed on 2014-06-18 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti /dev/snd/pcmC0D1p: vibhas 1745 F...m pulseaudio Symptom_Jack: Green Speaker, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: PI945GCM dmi.board.vendor: Kobian dmi.board.version: ECS dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Kobian dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd08/16/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: PI945GCM dmi.product.version: 1.X dmi.sys.vendor: Kobian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1345664/+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 1339610] Re: unity8 crashed with SIGSEGV in mir::frontend::ClientBufferTracker::client_has()
** Changed in: mir Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1339610 Title: unity8 crashed with SIGSEGV in mir::frontend::ClientBufferTracker::client_has() Status in Mir: Incomplete Status in “mir” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Bug description: This happened during UITK autopilot tests in smoketesting of image #121: http://ci.ubuntu.com/smokeng/utopic/touch/mako/121:20140709:20140709/8946/ubuntuuitoolkit/ ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity8 7.90+14.10.20140707-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu1 Architecture: armhf CurrentDesktop: Unity Date: Wed Jul 9 05:45:03 2014 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 1404736464 InstallationDate: Installed on 2014-07-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140709-020204) ProcCmdline: unity8 ProcCwd: /home/phablet Signal: 11 SourcePackage: unity8 StacktraceTop: mir::frontend::ClientBufferTracker::client_has(mir::graphics::BufferID const) const () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22 ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22 mir::compositor::BufferQueue::give_buffer_to_client(mir::graphics::Buffer*, std::unique_lockstd::mutex) () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22 mir::compositor::BufferQueue::release(mir::graphics::Buffer*, std::unique_lockstd::mutex) () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22 mir::compositor::BufferQueue::compositor_release(std::shared_ptrmir::graphics::Buffer const) () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22 Title: unity8 crashed with SIGSEGV in mir::frontend::ClientBufferTracker::client_has() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1339610/+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 1345533] Re: [hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on
** Changed in: mir Importance: Undecided = Critical ** Changed in: mir (Ubuntu) Importance: Undecided = Critical ** Changed in: mir Milestone: None = 0.6.0 ** Summary changed: - [hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on + [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on ** Tags added: regression ** Also affects: mir/0.5 Importance: Undecided Status: New ** Changed in: mir/0.5 Importance: Undecided = Critical ** Changed in: mir/0.5 Milestone: None = 0.5.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1345533 Title: [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on Status in Mir: New Status in Mir 0.5 series: New Status in “mir” package in Ubuntu: New Bug description: Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5 (hammerhead), as it fails to turn the vsync signal on. This is what I get from logcat: D/libEGL ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so D/libEGL ( 3038): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so D/libEGL ( 3038): loaded /vendor/lib/egl/libGLESv2_adreno.so I/qdutils ( 3038): Right Split=0 D/qdhwcomposer( 3038): int qhwc::adRead(): /sys/class/graphics/fb2/ad could not be opened : No such file or directory I/qdhwcomposer( 3038): Initializing Qualcomm Hardware Composer I/qdhwcomposer( 3038): MDP version: 500 I/Adreno-EGL( 3038): qeglDrvAPI_eglInitialize:320: EGL 1.4 QUALCOMM Build: I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13 D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, width = 1080 D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, height = 1920 I/Adreno-EGL( 3038): qeglDrvAPI_eglInitialize:320: EGL 1.4 QUALCOMM Build: I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13 I/qdhwcomposer( 3038): hwc_registerProcs I/qdhwcomposer( 3038): Initializing UEVENT Thread I/qdhwcomposer( 3038): Initializing VSYNC Thread I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=0 from /sys/class/graphics/fb0/vsync_event I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=1 from /sys/class/graphics/fb1/vsync_event D/qdhwcomposer( 3038): hwc_blank: Unblanking display: 0 D/qdhwcomposer( 3038): hwc_blank: Done unblanking display: 0 E/qdhwcomposer( 3038): hwc_vsync_control: vsync control failed. Dpy=0, enable=1 : Operation not supported W/libEGL ( 3038): eglTerminate() called w/ 1 objects remaining E/libEGL ( 3038): validate_display:263 error 3001 (EGL_NOT_INITIALIZED) I/ServiceManager( 913): service 'display.qservice' died The vsync control failed message was always there, and Mir 0.4 worked fine with it still. System compositor log: root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log ERROR: /build/buildd/mir-0.5.0+14.10.20140717/src/platform/graphics/android/real_hwc_wrapper.cpp(75): Throw in function virtual void mir::graphics::android::RealHwcWrapper::vsync_signal_on() const Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: error turning vsync signal on. rc = ffa1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1345533/+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 1162781] Re: bluez package out of date, 5.3 is available
Blocks gnome-bluetooth update (bug 1345884) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1162781 Title: bluez package out of date, 5.3 is available Status in “bluez” package in Ubuntu: Triaged Bug description: Looks like there have been a lot of improvements to bluez since the 4.x series. Would be nice to get the latest release pulled in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+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 1304363] Re: [UIFe] enable borderless windows under metacity (e.g. for ubiquity)
** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed = Won't Fix ** Summary changed: - [UIFe] enable borderless windows under metacity (e.g. for ubiquity) + enable borderless windows under metacity (e.g. for ubiquity) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1304363 Title: enable borderless windows under metacity (e.g. for ubiquity) Status in Ubuntu Documentation: Invalid Status in Themes for Ubuntu: New Status in Ubuntu Website Content: Invalid Status in “ubuntu-themes” package in Ubuntu: Won't Fix Status in “ubuntu-themes” source package in Trusty: Won't Fix Bug description: borderless windows was enabled in 14.04, but it looks like that was not enabled under metacity which ubiquity installer uses. This also fixes the ugly one pixel white border around the installer which all designers complained to me about. To match the compiz/unity7 theme we should disable borders in metacity as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-docs/+bug/1304363/+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 1059374] Re: Using Adwaita, many widgets are drawn with a solid black background
Disabling scrollbars do not help, I face the issue with certain themes like Moka and Orchis. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1059374 Title: Using Adwaita, many widgets are drawn with a solid black background Status in GTK+ GUI Toolkit: Fix Released Status in Overlay Scrollbar: Confirmed Status in “gnome-themes-standard” package in Ubuntu: Confirmed Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “overlay-scrollbar” package in Ubuntu: Triaged Bug description: When I use the Adwaita theme, some widgets end up being drawn with a black background after particular interactions. Here are two examples: If I open gedit, by default I see a new black document. The notebook widget is visible, and rendered correctly. As soon as I open another document (no matter if I close the existing one first), the entire widget starts being drawn with a black background. If I open System Settings, then click the (Ubuntu) Online Accounts panel, the box with the Remove account button has a solid black background. If, instead, I open Online Accounts directly from its launcher (run gnome-control-center credentials), everything is rendered correctly: there are no solid black backgrounds until I click All Settings and select the Online Accounts panel again. This has been happening consistently on two very different machines, both updated to Quantal from 12.04 using the upgrade tool. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libgtk-3-0 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 21:18:23 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110906) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to quantal on 2012-08-26 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1059374/+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 1342923] Re: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()
I experienced this for the first time immediately upon reboot. This was a required reboot after running an update for the first time in a couple weeks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1342923 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() Status in Meta-tracker: New Status in Ubuntu GNOME: New Status in “tracker” package in Ubuntu: Confirmed Bug description: i ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: tracker 1.0.2-1ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 16 21:39:09 2014 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-07-16 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x7f02dd2c9cb3 _IO_vfprintf_internal+7443: repnz scas %es:(%rdi),%al PC (0x7f02dd2c9cb3) ok source %es:(%rdi) (0xc0023630) not located in a known VMA region (needed readable region)! destination %al ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: tracker StacktraceTop: _IO_vfprintf_internal (s=s@entry=0x7f02d37fd600, format=optimized out, format@entry=0x7f02de5f5da0 Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s'), ap=ap@entry=0x7f02d37fd7a8) at vfprintf.c:1661 __GI___vasprintf_chk (result_ptr=0x7f02d37fd758, flags=1, format=0x7f02de5f5da0 Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s'), args=0x7f02d37fd7a8) at vasprintf_chk.c:66 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_new_valist () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() 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/tracker/+bug/1342923/+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 1343802] Re: Installation of cgmanager prevents booting with systemd
I see the same problem booting utopic with systemd and cgmanager. After enabling the debug shell, I found these messages in journalctl: Jul 20 23:54:03 fixed-disk cgmanager[682]: * Starting cgroup management daemon cgmanager Jul 20 23:54:03 fixed-disk cgmanager[682]: ...done. Jul 20 23:54:03 fixed-disk kernel: cgroup: new mount options do not match the existing superblock, will be ignored Jul 20 23:54:03 fixed-disk systemd[1]: cgmanager: cgm_get for controller=cpu, cgroup_path=system/cgmanager.service/control failed: invalid request Jul 20 23:54:03 fixed-disk systemd[1]: cgmanager: cgm_remove failed: systemd:system/cgmanager.service did not exist Jul 20 23:54:03 fixed-disk systemd[1]: Started LSB: Cgroup manager daemon. Jul 20 23:54:03 fixed-disk systemd[1]: cgmanager: cgm_get for controller=systemd, cgroup_path=system/cgmanager.service failed: invalid request Jul 20 23:54:03 fixed-disk systemd[1]: Failed to check whether cgroup is empty: Resource temporarily unavailable Jul 20 23:54:03 fixed-disk systemd[1]: Cannot add dependency job for unit systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-vconsole-setup.service' for details. Jul 20 23:54:03 fixed-disk systemd[1]: Starting ACPI event daemon... Jul 20 23:54:03 fixed-disk systemd[1]: cgmanager: cgm_get for controller=cpu, cgroup_path=system/acpid.service/control failed: invalid request Jul 20 23:54:03 fixed-disk systemd[1]: Started ACPI event daemon. Jul 20 23:54:03 fixed-disk systemd[861]: Failed at step CGROUP spawning /usr/sbin/acpid: Operation not permitted Jul 20 23:54:03 fixed-disk systemd[1]: acpid.service: main process exited, code=exited, status=219/CGROUP Jul 20 23:54:03 fixed-disk systemd[1]: Unit acpid.service entered failed state. etc. Lots of other services fail with similar cgm_get errors. -- 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/1343802 Title: Installation of cgmanager prevents booting with systemd Status in “cgmanager” package in Ubuntu: Confirmed Status in “systemd-shim” package in Ubuntu: Confirmed Bug description: I have a completely upgraded Ubuntu Utopic development branch setup, with proprietary nvidia drivers installed. I have set my booting system to boot with systemd instead of the upstart one. The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager. However, installation of cgmanager (versions 0.26-0ubuntu5 or 0.27-0ubuntu7) does not complete booting with systemd. Not even tty1 is created and thus gdm (which I use instead of lightdm) is not started. I have the newest systemd installed (version 204-14ubuntu2). Booting with upstart on the other hand goes just fine. If I downgrade systemd to version 6-3 (and remove package cgmanager) all is well again and systemd booting is fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1343802/+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 1275221] Re: Not sound when screensaving
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- 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/1275221 Title: Not sound when screensaving Status in “xorg” package in Ubuntu: Expired Bug description: Screensaver turns off sound. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.13.2-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 CurrentDesktop: Unity Date: Sat Feb 1 11:38:49 2014 DistUpgraded: 2014-01-27 12:12:23,747 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770 GHz Edition] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e244] InstallationDate: Installed on 2014-01-17 (14 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) JockeyStatus: kmod:fglrx - ATI Fire GL (Proprietary, Enabled, In use) kmod:fglrx_updates - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) MachineType: MSI MS-7640 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=c33c2abb-8df7-49fa-8190-5f0d00f7c47b ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-01-27 (4 days ago) dmi.bios.date: 10/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V19.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-GD65 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV19.9:bd10/08/2012:svnMSI:pnMS-7640:pvr3.0:rvnMSI:rn990FXA-GD65(MS-7640):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7640 dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sat Feb 1 11:07:44 2014 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 9 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1275221/+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 1304069] Re: package slapd 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
[Expired for openldap (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openldap (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1304069 Title: package slapd 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in “openldap” package in Ubuntu: Expired Bug description: During dist-upgrade encountered errors with slapd. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: slapd 2.4.31-1+nmu2ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Mon Apr 7 11:32:47 2014 DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-08-20 (595 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: openldap Title: package slapd 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1304069/+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 1343802] Re: Installation of cgmanager prevents booting with systemd
This seems to be fixed after upgrading to Martin’s systemd 208 packages. -- 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/1343802 Title: Installation of cgmanager prevents booting with systemd Status in “cgmanager” package in Ubuntu: Confirmed Status in “systemd-shim” package in Ubuntu: Confirmed Bug description: I have a completely upgraded Ubuntu Utopic development branch setup, with proprietary nvidia drivers installed. I have set my booting system to boot with systemd instead of the upstart one. The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager. However, installation of cgmanager (versions 0.26-0ubuntu5 or 0.27-0ubuntu7) does not complete booting with systemd. Not even tty1 is created and thus gdm (which I use instead of lightdm) is not started. I have the newest systemd installed (version 204-14ubuntu2). Booting with upstart on the other hand goes just fine. If I downgrade systemd to version 6-3 (and remove package cgmanager) all is well again and systemd booting is fine again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1343802/+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 1283551] Re: gjs-console crashed with signal 5
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1283551 Title: gjs-console crashed with signal 5 Status in GNOME Spidermonkey Javascript binding: Fix Released Status in The G Library - GLib: Fix Released Status in Ubuntu GNOME: Triaged Status in “gjs” package in Ubuntu: Triaged Status in “gobject-introspection” package in Ubuntu: Triaged Status in “gjs” source package in Trusty: Triaged Status in “gobject-introspection” source package in Trusty: Triaged Bug description: Connect Bluethooth ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gjs 1.39.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 22 17:44:13 2014 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2014-01-23 (30 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140122) ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ Main\ =\ imports.main;\ Main.start(); --no-default-window Signal: 5 SourcePackage: gjs StacktraceTop: ?? () from /usr/lib/libgjs.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 Title: gjs-console crashed with signal 5 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/gjs/+bug/1283551/+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 1293633] Re: alternate install sets up biosdevname by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1293633 Title: alternate install sets up biosdevname by default Status in “biosdevname” package in Ubuntu: Won't Fix Status in “ubuntu-meta” package in Ubuntu: Confirmed Bug description: Hi, Please create a symbolic link between ethernet interfaces from p1p1 to eth0. dmesg | grep eth0 [0.614926] systemd-udevd[102]: renamed network interface eth0 to p1p1 Because it breaks too much software. Add biosdevname = 0 in grub is not a good solution. Regards, ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDmesg: [ 10.180489] IPv6: ADDRCONF(NETDEV_CHANGE): p1p1: link becomes ready [ 12.553851] init: slim main process (856) terminated with status 1 [ 19.482607] audit_printk_skb: 9 callbacks suppressed [ 19.482610] type=1006 audit(1395069279.474:15): pid=1065 uid=0 old auid=4294967295 new auid=1000 old ses=4294967295 new ses=1 res=1 [ 206.343029] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead. Date: Mon Mar 17 16:20:50 2014 InstallationDate: Installed on 2014-03-17 (0 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha amd64 (20140316) MachineType: MSI MS-7798 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=0cc5c37b-0c94-4ba4-a328-2428848bcfac ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75MA-P45 (MS-7798) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd09/30/2013:svnMSI:pnMS-7798:pvr1.0:rvnMSI:rnB75MA-P45(MS-7798):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7798 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1293633/+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 1345963] [NEW] [TravelMate P243, Realtek ALC271X, Green Headphone Out, Left] Playback problem
Public bug reported:
The laptop speakers work fine but the headphone gives no sound at all.
The headphone uses to work not long before. It also works normally in
Windows 7 which is on this hardware system.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-67.101-generic-pae 3.2.60
Uname: Linux 3.2.0-67-generic-pae i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC271X Analog [ALC271X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: wijit 2788 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9071 irq 45'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10250721,00100100
HDA:80862806,10250721,0010'
Controls : 27
Simple ctrls : 13
Date: Mon Jul 21 12:09:38 2014
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Left
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [TravelMate P243, Realtek ALC271X, Green Headphone Out, Left] Playback
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA40_HC
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.01:bd04/20/2012:svnAcer:pnTravelMateP243:pvrV1.01:rvnAcer:rnBA40_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: TravelMate P243
dmi.product.version: V1.01
dmi.sys.vendor: Acer
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise
--
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/1345963
Title:
[TravelMate P243, Realtek ALC271X, Green Headphone Out, Left] Playback
problem
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
The laptop speakers work fine but the headphone gives no sound at all.
The headphone uses to work not long before. It also works normally in
Windows 7 which is on this hardware system.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-67.101-generic-pae 3.2.60
Uname: Linux 3.2.0-67-generic-pae i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC271X Analog [ALC271X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: wijit 2788 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9071 irq 45'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10250721,00100100
HDA:80862806,10250721,0010'
Controls : 27
Simple ctrls : 13
Date: Mon Jul 21 12:09:38 2014
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386
(20120423)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Left
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [TravelMate P243, Realtek ALC271X, Green Headphone Out, Left] Playback
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA40_HC
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
[Touch-packages] [Bug 1345707] Re: powerd crashed with SIGABRT in ua_sensors_proximity_new()
*** This bug is a duplicate of bug 1338925 *** https://bugs.launchpad.net/bugs/1338925 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 #1338925, 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/1345707/+attachment/4158163/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1345707/+attachment/4158165/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1345707/+attachment/4158166/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1345707/+attachment/4158167/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1345707/+attachment/4158168/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1345707/+attachment/4158169/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1345707/+attachment/4158170/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1338925 ** 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 powerd in Ubuntu. https://bugs.launchpad.net/bugs/1345707 Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() Status in “powerd” package in Ubuntu: New Bug description: error message on startup everytime ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: powerd 0.16+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 Date: Mon Jul 21 00:45:39 2014 ExecutablePath: /usr/bin/powerd ExecutableTimestamp: 1404768715 InstallationDate: Installed on 2014-05-04 (77 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140503) ProcCmdline: /usr/bin/powerd ProcCwd: / ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: powerd StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_sensors_proximity_new () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 powerd_sensors_init() () main () SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1345707/+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 1345706] Re: unity-panel-service crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 869816 *** https://bugs.launchpad.net/bugs/869816 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 #869816, 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/1345706/+attachment/4158152/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1345706/+attachment/4158154/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1345706/+attachment/4158157/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1345706/+attachment/4158158/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1345706/+attachment/4158159/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1345706/+attachment/4158160/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1345706/+attachment/4158161/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 869816 unity-panel-service crashed with SIGSEGV in panel_indicator_entry_accessible_get_n_children() ** 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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1345706 Title: unity-panel-service crashed with SIGSEGV in g_main_context_dispatch() Status in “unity” package in Ubuntu: New Bug description: completely out of the blue ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-services 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 NonfreeKernelModules: nvidia zfs zcommon znvpair zavl zunicode ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CheckboxSubmission: 48349af06a737bc39f5bd5104a6aec3f CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Jul 20 15:14:05 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0x4063bd: mov(%rbx),%rdx PC (0x004063bd) ok source (%rbx) (0x0002) not located in a known VMA region (needed readable region)! destination %rdx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/modules/libatk-bridge.so g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345706/+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 1241101]
So, after few tries in Virtual Machines to test different Debian/gtk versions, and other researches on the net, I found a workaround to make Luna work on my Debian laptop : export SWT_GTK3=0 That aims to fallback to the GTK2 SWT implementation and bring my Eclipse back! I was not on the right bug report, and found my way with a comment on bug #430736 https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736#c26 With that, it comes to me that the only solution, as i don't want to upgrade my glibc, is to fallback to GTK2... And thanks to http://www.eclipse.org/swt/R4_4/new_and_noteworthy.html#m3, the information was there... -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1345977] [NEW] [530U3C/530U4C, Realtek ALC269VC, Speaker, Internal] No sound at all
Public bug reported: Not go rhytmbox, not play music. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2852 F pulseaudio CurrentDesktop: GNOME Date: Mon Jul 21 01:43:36 2014 InstallationDate: Installed on 2014-04-27 (84 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_AlsaPlaybackTestStderr: A L S A l i b p c m _ h w . c : 1 6 6 7 : ( _ s n d _ p c m _ h w _ o p e n ) I n v a l i d v a l u e f o r c a r d Symptom_Card: Audio Interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2852 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Symptom_amixerStderr: a m i x e r : M i x e r a t t a c h h w : P C H e r r o r : N o s u c h d e v i c e Title: [530U3C/530U4C, Realtek ALC269VC, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 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.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1345977 Title: [530U3C/530U4C, Realtek ALC269VC, Speaker, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: Not go rhytmbox, not play music. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2852 F pulseaudio CurrentDesktop: GNOME Date: Mon Jul 21 01:43:36 2014 InstallationDate: Installed on 2014-04-27 (84 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_AlsaPlaybackTestStderr: A L S A l i b p c m _ h w . c : 1 6 6 7 : ( _ s n d _ p c m _ h w _ o p e n ) I n v a l i d v a l u e f o r c a r d Symptom_Card: Audio Interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2852 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Symptom_amixerStderr: a m i x e r : M i x e r a t t a c h h w : P C H e r r o r : N o s u c h d e v i c e Title: [530U3C/530U4C, Realtek ALC269VC, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 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.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1345977/+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
