[Desktop-packages] [Bug 1173764] Re: software-center returns error
** Changed in: software-center (Debian) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1173764 Title: software-center returns error Status in “software-center” package in Ubuntu: Confirmed Status in “software-center” package in Debian: Confirmed Bug description: 1) Ubuntu 13.04 2) tim@tim-desktop:~$ apt-cache policy software-center software-center: Installed: 5.6.0-0ubuntu2 Candidate: 5.6.0-0ubuntu2 Version table: *** 5.6.0-0ubuntu2 0 500 http://za.archive.ubuntu.com/ubuntu/ raring/main i386 Packages 100 /var/lib/dpkg/status 3) I expected Software Center to launch when I clicked the icon in the Unity Launcher. When it did not, I expected it to launch after entering software-center in the terminal. 4) On clicking Unity launcher, icon flashed; Software Center did not launch. On trying to start from terminal, the attached error report was generated. tim@tim-desktop:~$ software-center 2013-04-27 22:14:17,302 - softwarecenter.ui.gtk3.app - INFO - setting up proxy 'None' Traceback (most recent call last): File /usr/bin/software-center, line 130, in module app = SoftwareCenterAppGtk3(options, args) File /usr/share/software-center/softwarecenter/ui/gtk3/app.py, line 291, in __init__ self.cache = get_pkg_info() File /usr/share/software-center/softwarecenter/db/pkginfo.py, line 245, in get_pkg_info from softwarecenter.db.pkginfo_impl.aptcache import AptCache File /usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py, line 30, in module from aptdaemon.client import AptClient File /usr/lib/python2.7/dist-packages/aptdaemon/client.py, line 70, in module class MemoizedMixInMeta(MemoizedTransaction, GObject.GObjectMeta): File /usr/lib/python2.7/dist-packages/gi/module.py, line 316, in __getattr__ return getattr(self._introspection_module, name) File /usr/lib/python2.7/dist-packages/gi/module.py, line 135, in __getattr__ self.__name__, name)) AttributeError: 'gi.repository.GObject' object has no attribute 'GObjectMeta' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1173764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 982889] Re: X trying to start before plymouth has finished using the drm driver
** Branch linked: lp:ubuntu/precise-proposed/lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in “gdm” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: New Status in “lightdm” package in Ubuntu: Fix Released Status in “plymouth” package in Ubuntu: Fix Released Status in “gdm” source package in Precise: New Status in “kde-workspace” source package in Precise: New Status in “lightdm” source package in Precise: Fix Released Status in “plymouth” source package in Precise: Fix Released Status in “gdm” source package in Raring: Fix Committed Status in “kde-workspace” source package in Raring: New Status in “lightdm” source package in Raring: Fix Released Status in “plymouth” source package in Raring: Fix Released Status in “gdm” source package in Saucy: Fix Released Status in “kde-workspace” source package in Saucy: New Status in “lightdm” source package in Saucy: Fix Released Status in “plymouth” source package in Saucy: Fix Released Bug description: X server fails to start the first time after boot, it works fine when I start it again. Looks like a race condition with intel drm initialization, i guess X tries to start faster than drm driver is initialized so it fails. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 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] CompositorRunning: compiz Date: Mon Apr 16 10:35:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7750] Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21fa] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: MSI MS-7750 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68A-G43 (G3) (MS-7750) 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.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7750 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/982889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 951000] Re: disable guest session screen lock using gsettings
** Branch linked: lp:ubuntu/lightdm ** Branch linked: lp:ubuntu/raring-proposed/lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: New Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Precise: In Progress Status in “lightdm” source package in Raring: Fix Committed Bug description: * Impact: sometime screen locking doesn't get disabled in guest session * Test Case: - log into a guest session - try locking the screen screen locking should be disabled * Impact: check that screen locking is well disabled in guest sessions To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 577919] Re: chromium-browser fails to start (guest account, OpenVZ): Failed to move to new PID namespace: Operation not permitted
** Branch linked: lp:ubuntu/precise-proposed/lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm-guest-session in Ubuntu. https://bugs.launchpad.net/bugs/577919 Title: chromium-browser fails to start (guest account, OpenVZ): Failed to move to new PID namespace: Operation not permitted Status in Chromium Browser: Unknown Status in Light Display Manager: Fix Released Status in OpenVZ kernel (patchset): Confirmed Status in “gdm-guest-session” package in Ubuntu: Confirmed Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm-remote-session-freerdp” package in Ubuntu: Fix Released Status in “lightdm-remote-session-uccsconfigure” package in Ubuntu: Fix Released Status in “gdm-guest-session” source package in Precise: Won't Fix Status in “lightdm” source package in Precise: Fix Released Status in “lightdm-remote-session-freerdp” source package in Precise: Invalid Status in “lightdm-remote-session-uccsconfigure” source package in Precise: Invalid Bug description: Binary package hint: chromium-browser [Impact] Chromium-browser does not launch from guest session. Fix by Jamie Strandboge: It would be nice if AppArmor could merge profiles, but we can't yet, so we need to do like you initially did: have two mostly identical profiles. Because the lightdm remote sessions are shipping policy copies, the maintenance cost is getting high. I will be abstracting out the guest rules into abstracations/lightdm and then have a small snippet using a child profile in abstractions/lightdm_chromium-browser. The guest and remote lightdm profiles can just include these and all the policy is in the abstractions. Using a lightdm.d directory is a good idea, but upstream AppArmor is currently discussing how to best handle .d directories like this, and I'd rather not add another one until that discussions is finished. [Test Case] 1. install chromium-browser 2. login to the guest account 3. login to vt1 or login via ssh as a regular user and verify that the lightdm profile is loaded and guest session applications are confined: $ sudo aa-status apparmor module is loaded. ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1378) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1414) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1417) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1418) ... Note: number of profiles and pids will vary. 4. try to start chromium-browser either via the Dash or a terminal Prior to upgrading, chromium-browser will fail to start with: Failed to move to new PID namespace: Operation not permitted After upgrading, the guest session should be functional and chromium-browser should start. In addition, aa-status should report a child profile for chromium-browser and chromium-browser should be under that confinement with other guest session applications under the lightdm-guest-session-wrapper confinement: $ sudo aa-status apparmor module is loaded. ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2667) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2672) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2682) ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser (3090) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser (3092) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser (3093) ... [Regression Potential] As mentioned in the Impact, the apparmor profile for lightdm has necessarily been broken out into multiple parts. As such, there is potential that the guest session profile won't work correctly, however, this is easily seen in the test cases and these changes have been in place since 12.10. [Other Info] Attached is a debdiff for 12.04. It: - adds debian/patches/05_lp577919-fix-chromium-launch.patch which is the same as debian/patches/09_lp577919-fix-chromium-launch.patch from quantal, except it a) does not include the fix for bug #1059510, which is uneeded on precise and b) includes the fix for bug #1189948 to install the abstractions with the correct permissions - additionally, debian/lightdm.postinst is updated to reload the apparmor profile on upgrade to this version of lightdm. The code in question uses the same logic as dh_apparmor, and I'm not sure why lightdm doesn't use dh_apparmor. Rather than making several packaging changes to use dh_apparmor, I chose this option to reduce change. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: chromium-browser
[Desktop-packages] [Bug 1185035] Re: Crash in RRCrtcDetachScanoutPixmap on xserver shutdown.
** Branch linked: lp:ubuntu/xorg-server -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1185035 Title: Crash in RRCrtcDetachScanoutPixmap on xserver shutdown. Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Raring: New Bug description: [Impact] * Normal server shutdown will crash when using nvidia in the 319 recommended optimus setup, or when using usb displaylink output. [Test Case] * Start X on an Intel system with a DisplayLink device attached, or nvidia in optimus configuration. * xrandr --setprovideroutputsource modesetting NVIDIA-0, or xrandr --setprovideroutputsource modsetting Intel *. xrandr --output DVI-0 --off (bug #1185014 workaround) * xrandr --auto * Shutdown xserver, no crash should happen. [Regression Potential] * Low, the codepath affected only happens on server shutdown, which is already crashing anyway. * Considering the code affected, xrandr --setprovideroutputsource and --setprovideroffloadsink will be the most likely candidates if regressions do occur. [Other Info] * Not upstream yet, but expected there soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1185035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1094473] Re: Remote logon support for wicd/tray icon
** Changed in: unity-greeter (Ubuntu) Importance: Undecided = Wishlist ** Changed in: unity-greeter (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1094473 Title: Remote logon support for wicd/tray icon Status in “unity-greeter” package in Ubuntu: Triaged Bug description: LightDM at the moment only supports an icon for Network-Manager and Network-Manager-Gnome, but has no support for network-menu or Wicd. This can (and does) prevent Users from selecting a network for remote login if they do not use the gnome packages. Ubuntu 12.10 lightdm Installed: 1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1094473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1083032] Re: Video driver not working for Savage chipset
** Branch linked: lp:ubuntu/xorg-server -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1083032 Title: Video driver not working for Savage chipset Status in X.Org X server: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Status in “xserver-xorg-video-savage” package in Ubuntu: Fix Released Status in “xorg-server” source package in Raring: New Status in “xserver-xorg-video-savage” source package in Raring: Fix Committed Bug description: [Impact] For xserver-xorg-video-savage: Display corruption in X on all Savage-equipped laptops such as Thinkpad T22, making the system unusable. For xorg-server: System lockup on boot. [Test Case] Attempt to boot a system with one of the affected Savage cards; the Thinkpad T22 is at least one such system. The display will be corrupted beyond usability. Install xserver-xorg-video-savage and xserver-xorg-core from proposed, and you should have a usable X session. [Regression Potential] The X server patch touches only the DRI1 initialisation codepath; this is not used for the vast majority of systems, so breakage is low-impact. Breakage here would most likely manifest as an Xserver crash on startup. (Most likely any driver using DRI1 is broken without this patch, but since DRI1 is mostly used for mesa and our mesa does not support DRI1 any longer, this is not very visible. However, the savage driver uses DRI1 for 2D acceleration as well.) The savage patch switches the default acceleration method to EXA (from XAA) and adds some fixes to EXA support. We don't build XAA support into the X server any more, so switching away from it means enabling EXA acceleration(*), which can cause pretty much arbitrary problems, but is unlikely to. In any case, problems would be restricted to users of xserver-xorg-video-savage. *) The build-without-XAA fallback to no acceleration is broken, so EXA is the best way out of this. EXA has been reported to work well, and is now enabled by default upstream (the patches in this report are from upstream). The user can still disable (EXA) acceleration in xorg.conf, which should work out fine when done this way. [Original Report] When installing 12.10 on our Thinkpad T22 laptops the display does not work. 12.04 works fine. xserver-xorg-video-s3 is version 1:0.6.5-0ubuntu1 xserver-xorg-video-savage is version 1:2.3.6-0ubuntu1 I don't know if these are the packages involved but they are the ones that I suspect may be involved. This T22 model (and many other thinkpads from that era) use the S3 Savage IX8 chipsets. Using the info from this link makes the display work. = http://www.physics.wustl.edu/~alford/thinkpad/T23_F17.html Xorg :1 -configure # ignore Configuration Failed message cp xorg.conf.new /etc/X11/xorg.conf Edit the /etc/X11/xorg.conf file: uncomment Option DisableTile in the Section Device that contains the Savage driver options. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1083032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201067] Re: Update Liferea to Debian version 1.8.15-1
liferea (1.8.15-1ubuntu1) saucy; urgency=low . * Merge from Debian unstable. Remaining changes: * debian/patches: - port-to-libindicate-0.7.patch: dropped as obsolete - port-to-messaging-menu.patch: rebased - ubuntu-example-feeds.patch: removed feedlist_ru.oplm changes added .patch extension - add_X-Ubuntu-Gettext-Domain.patch: Added .patch extension - libunity.patch * debian/control: libunity-dev, libmessaging-menu-dev * debian/liferea.indicate: Removed as obsolete * debian/rules: enable messaging-menu . liferea (1.8.15-1) unstable; urgency=low . [ Dmitry Smirnov ] * New upstream release [January 2013] * Dropped patches (applied-upstream): - fix-browser-selections - fix-crash-when-dragging-feeds-outside-google-reader - fix-crash-when-online-status-changes - fix-crash-when-removing-google-reader-folders - fix-crash-in-empty-launch-url * Remaining patches are renamed to end with .patch. * Removed README.source with instructions how to use `quilt`. * debian/control: - dropped redundant autotools-dev from Build-Depends. - dropped ${shlibs:Depends} from (data|dbg) packages. + moved packaging Build-Deps to first line of Build-Depends. + Standards to 3.9.4. * debian/copyright to copyright-format-1.0 + audit/update. * debian/rules re-written in dh style: - dropped unsupported build options --enable-gnutls --enable-lua. - dropped redundant invocation of intltool-update -p. - dropped patch libtool-dont-rearange-as-needed (obsoleted by dh_autoreconf --as-needed). + increased log verbosity with --disable-silent-rules. + enabled parallel build. + debhelper to version 9. * debian/compat to version 9. * Lintianisation: + added set -e to postinit scripts (maintainer-script-without-set-e). + updated Vcs fields (vcs-field-not-canonical). * xz compression for source and binary packages. * Added myself to Uploaders. * debian/watch is corrected to mangle RC versions in case insensitive way and to look for .bz2 and .xz archives (thanks, Barak). . [ David Michael Smith ] * New upstream release [June 2013] * Fix segfault opening attachment due to incorrect g_free() (Closes: #714074) * Fix FTBFS in jessie, sid. (Closes: #713322) * Refreshed debian-example-feeds.patch. * Added myself to Uploaders. ** Changed in: liferea (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1201067 Title: Update Liferea to Debian version 1.8.15-1 Status in “liferea” package in Ubuntu: Fix Released Bug description: Liferea should be updated to the Debian version 1.8.15-1. See https://merges.ubuntu.com/l/liferea/ and here https://launchpad.net/debian/sid/+source/liferea. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1201067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 773269] Re: liferea icon is very low-res
I think it was a problem in gnome-icon-theme, but I can't reproduce it. Do you still have this problem in newer Ubuntu releases? ** Changed in: liferea (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/773269 Title: liferea icon is very low-res Status in “liferea” package in Ubuntu: Incomplete Bug description: Binary package hint: liferea the liferea icon appears to be 16x16 or something -- this is especially noticable with the new unity taskbar, where it is in contrast to all the other apps with clean crisp 64x64(?) icons. The liferea.sf.net website has a nice 48x48 icon, so I would hope that at a minimum that could be thrown into the package in a few seconds... ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: liferea 1.6.4-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Apr 29 14:57:34 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: liferea UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/773269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
Hi ,finally i found this small device which was necessary to plug it into usb plug so this wireless mouse could work again. I did write wherever you have told to,and i got these 2 screen photos (i hope this was what you have ask me to do) Also i would like to ask you about this UBUNTU ONE and this personal cloud which is located on the right top of my screen,IS THIS SAVE??Can you take away from my system or what to i have to do to do it by my self ??Every time i copy paste on libre office writer and i take it out as PDF it seems that there no privacy about , is it just my idea or is it like that?? Any way i send you the 2 photos screen,hopping that this is what you have ask me and i will not plug in this wireless mouse until you tell me to. I am really thankfull for your efforts Babis Xanthopoulos Date: Sun, 14 Jul 2013 20:21:28 + From: christopher.m.penal...@gmail.com To: babisxanthopou...@hotmail.com Subject: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg Babis, if you are having an issue finding the device, we can close this report until you do. If you do find the device, regarding the terminal command, one would open a terminal window, and type verbatim: lsusb -v lsusb-v.log and post the file to this report. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1191334 Title: A wrong hardware detection seems to crash Xorg Status in linux package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Bug description: A wrong hardware detection seems to crash Xorg. This report is generated without a wireless mouse, which was connected to the laptop in the duplicate bug 1190987 but the mouse didn't make a difference to the system's stability. Both the xorg.log and the attachment refer to a Microsoft MicrosoftR Nano Transceiver but the laptop is not connected a a wireless keyboard. From Xorg.log: (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3] (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286] (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101] (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424] (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b] (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1] (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6] (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422] (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b] (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25] (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441] (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd] (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa] (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083] (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb] (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3] (EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04] (EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4] (EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d] (EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525] (EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935] (EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. [mi] Increasing EQ size to 512 to prevent dropped events. [ 19459.082] [mi] EQ processing has resumed after 19 dropped events. [ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 20581.964] (II) config/udev: removing device Microsoft MicrosoftR Nano Transceiver v2.0 [ 20586.862] (II) evdev: Microsoft MicrosoftR Nano Transceiver v2.0: Close [ 20588.924] (II) UnloadModule: evdev ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1
[Desktop-packages] [Bug 1192002] Re: Menu config file merges menus from standard locations too soon so defaults override merges.
** Changed in: gnome-menus (Ubuntu) Status: New = Triaged ** Changed in: gnome-menus (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1192002 Title: Menu config file merges menus from standard locations too soon so defaults override merges. Status in gnome-menus: New Status in “gnome-menus” package in Ubuntu: Triaged Bug description: Merged files from /etc/xdg/menus/applications-merged/ or the user's home directory are supposed to be able to override the default file settings. According to the freedesktop standard the merge files should therefore be read in last. However, the DefaultMergeDirs/ element is at the top of /etc/xdg/menus/applications.menu and so the default overrides the merge. The best way to test this is with a layout portion in the merge file. The DefaultMergeDirs/ should be the last entry before the last /Menu. This bug breaks packages that add files to /etc/xdg/menus /applications-merged/ directory like ubuntustudio-menu and menu editors such as alacarte (this is not a full list, just examples) and it breaks the freedesktop standard as well. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-menus 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11 Uname: Linux 3.8.0-22-lowlatency i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Mon Jun 17 16:48:37 2013 InstallationDate: Installed on 2013-04-21 (57 days ago) InstallationMedia: Ubuntu-Studio 13.04 Raring Ringtail - Release i386 (20130420) MarkForUpload: True SourcePackage: gnome-menus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-menus/+bug/1192002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201229] Re: Should be a choice for one graph on multicore CPUs
Which version of gnome-system-monitor are you running? You can check it in the menu by clicking Help-About. The 3.8 version has an option in Edit-Preferences-Resources tab to draw a stacked area chart. Toggling that option maybe shows what you would like to see, with a twist: all core usages are shown on one graph, but summed up as a stacked area chart, so that you can see how each core contributes to the total usage, but you can also see the total usage. See the attached image from my System Monitor 3.8 (available in the stable 13.04 and the development 13.10 version) Would that help you, or you would like to see something else? ** Attachment added: Stacked area chart in Gnome System Monitor 3.8 https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1201229/+attachment/3737225/+files/stacked.png ** Changed in: gnome-system-monitor (Ubuntu) Assignee: (unassigned) = Robert Roth (evfool) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1201229 Title: Should be a choice for one graph on multicore CPUs Status in “gnome-system-monitor” package in Ubuntu: Confirmed Bug description: It is more than a feature missing than a bug. System monitor should be able to set to display the CPU load in one graph even in multicore CPU. For exaple in a 4 core CPU when one core is loaded 100% and the other 3 are idle, it should be the choice to display that with a number of CPU load 25%. Windows task manager has this ability. System Monitor should have this ability too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1201229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1025839]
*** Bug 5 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1025839 Title: Printing multiple copies submits multiple separate jobs (should submit one job) Status in LibreOffice Productivity Suite: In Progress Status in “libreoffice” package in Ubuntu: Confirmed Bug description: In the print dialog, if Number of Copies is set to 50 then 50 separate, independent print jobs are spooled. It should submit a single print job, specifying 50 copies. This will allow the printer to do the replication if it can (all Postscript printers can). This is important because: 1) Submitting a separate jobs for each copy causes the page(s) to be rendered again and again, with a drastic reduction in through-put. This is CRUCIAL if the pages contain complex graphics or images which take a long time to render or transmit to the printer: A one-minute delay for the first of 50 copies is okay, but 1 minute for *each* of 50 copies is intolerable. 2) If the print job was a mistake, it is virtually impossible to stop the printer. Pressing the cancel button on the printer cancels just one copy, but after a little while the next one starts printing... 3) It is very inconvenient to cancel the job in CUPS, with 50 separate jobs, without affecting other unrelated jobs in the queue (you can cancel all jobs in the queue at once, or one at a time). Note that CUPS has always supported a number of copies option at the command-line level. For example lpr '-#50' file.pdf prints 50 copies of the file, rendering it once only. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice-writer 1:3.4.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33 Uname: Linux 3.0.0-22-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Jul 17 11:49:58 2012 InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1025839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1191334 Title: A wrong hardware detection seems to crash Xorg Status in “linux” package in Ubuntu: Invalid Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: A wrong hardware detection seems to crash Xorg. This report is generated without a wireless mouse, which was connected to the laptop in the duplicate bug 1190987 but the mouse didn't make a difference to the system's stability. Both the xorg.log and the attachment refer to a Microsoft Microsoft® Nano Transceiver but the laptop is not connected a a wireless keyboard. From Xorg.log: (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3] (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286] (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101] (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424] (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b] (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1] (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6] (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422] (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b] (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25] (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441] (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd] (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa] (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083] (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb] (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3] (EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04] (EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4] (EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d] (EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525] (EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935] (EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. [mi] Increasing EQ size to 512 to prevent dropped events. [ 19459.082] [mi] EQ processing has resumed after 19 dropped events. [ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 20581.964] (II) config/udev: removing device Microsoft Microsoft® Nano Transceiver v2.0 [ 20586.862] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Close [ 20588.924] (II) UnloadModule: evdev ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jun 15 18:34:14 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices [AMD] nee ATI RC410M [Mobility Radeon Xpress 200M] [1002:5a62] (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions Device [1734:10fb] InstallationDate: Installed on 2013-02-12 (123 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) Lsusb: Bus 003 Device 003: ID 046d:0a10 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS AMILO Li 1718 MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Desktop-packages] [Bug 1123107] Re: Jockey should install the linux-$flavour metapackage
I can confirm that 0.9.7-0ubuntu7.9 works correctly. I thought this had already made it into -updates. Please approve it ASAP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1123107 Title: Jockey should install the linux-$flavour metapackage Status in “jockey” package in Ubuntu: Fix Committed Status in “software-properties” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “jockey” source package in Precise: Fix Committed Status in “software-properties” source package in Quantal: Fix Committed Status in “ubuntu-drivers-common” source package in Quantal: Fix Committed Bug description: Neither binary graphics drivers nor dkms depends on the linux-headers any longer. This means that we need Jockey to at least try to install the correct linux-$flavour metapackage so that users get the correct linux headers together with linux updates. In raring we already do this in ubuntu-drivers-common and software- properties-gtk. In precise we could build upon what we have thanks to LP: #567699 and reuse the code from u-d-c. Note: while it's true that Ubiquity already does the right thing, this bug report aims to cover cases in which, for example, the metapackages are not there any more for some reason or because users have installed a different kernel flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1123107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
Could you please unplug all USB devices, plug in just the Microsoft Wireless Mouse, and then immediately open the Terminal (hit the Windows key in your keyboard and type Terminal) and paste the following command there? lsusb -v lsusb-v.log You will then find a called lsusb-v.log in your home folder. Could you attach that file to this report please? You can remove Ubuntu One by following the instructions at http://askubuntu.com/q/309122/8973. As for LibreOffice, you can find help with your problem in the support forum of your local Ubuntu community at http://loco.ubuntu.com/ or asking at http://askubuntu.com , https://answers.launchpad.net/ubuntu or http://ubuntuforums.org. Please do not use this bug report for further support requests, as this is not the best place for it. Thanks. ** Changed in: linux (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1191334 Title: A wrong hardware detection seems to crash Xorg Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-input-synaptics” package in Ubuntu: New Bug description: A wrong hardware detection seems to crash Xorg. This report is generated without a wireless mouse, which was connected to the laptop in the duplicate bug 1190987 but the mouse didn't make a difference to the system's stability. Both the xorg.log and the attachment refer to a Microsoft Microsoft® Nano Transceiver but the laptop is not connected a a wireless keyboard. From Xorg.log: (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3] (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286] (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101] (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424] (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b] (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1] (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6] (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422] (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b] (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25] (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441] (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd] (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa] (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083] (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb] (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3] (EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04] (EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4] (EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d] (EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525] (EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935] (EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. [mi] Increasing EQ size to 512 to prevent dropped events. [ 19459.082] [mi] EQ processing has resumed after 19 dropped events. [ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 20581.964] (II) config/udev: removing device Microsoft Microsoft® Nano Transceiver v2.0 [ 20586.862] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Close [ 20588.924] (II) UnloadModule: evdev ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jun 15 18:34:14 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced
[Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1191334 Title: A wrong hardware detection seems to crash Xorg Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: A wrong hardware detection seems to crash Xorg. This report is generated without a wireless mouse, which was connected to the laptop in the duplicate bug 1190987 but the mouse didn't make a difference to the system's stability. Both the xorg.log and the attachment refer to a Microsoft Microsoft® Nano Transceiver but the laptop is not connected a a wireless keyboard. From Xorg.log: (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3] (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286] (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101] (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424] (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b] (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1] (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6] (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422] (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b] (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25] (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441] (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd] (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa] (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083] (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb] (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3] (EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04] (EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4] (EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d] (EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525] (EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935] (EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. [mi] Increasing EQ size to 512 to prevent dropped events. [ 19459.082] [mi] EQ processing has resumed after 19 dropped events. [ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 20581.964] (II) config/udev: removing device Microsoft Microsoft® Nano Transceiver v2.0 [ 20586.862] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Close [ 20588.924] (II) UnloadModule: evdev ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jun 15 18:34:14 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices [AMD] nee ATI RC410M [Mobility Radeon Xpress 200M] [1002:5a62] (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions Device [1734:10fb] InstallationDate: Installed on 2013-02-12 (123 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) Lsusb: Bus 003 Device 003: ID 046d:0a10 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS AMILO Li 1718 MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Desktop-packages] [Bug 1200185] Re: failed to execute '/lib/udev/usb-db'
Thanks, pitti. Will see if I can fix above rules as per your recommendation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1200185 Title: failed to execute '/lib/udev/usb-db' Status in “argyll” package in Ubuntu: New Status in “colord” package in Ubuntu: New Status in “systemd” package in Ubuntu: Invalid Bug description: systemd-udev reports failure to execute usb-db, indeed there is no /lib/udev/usb-db on my system, yet argyll and colord reference those in the udev rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argyll/+bug/1200185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1200827] Re: Enable GOA backend
that gvfs-backends is not installed by default in ubuntu-touch. it's not a the moment but it might be in the futur, please don't add extra goa depends to Ubuntu default desktop/unity session, that backend should be split in its own binary ** Changed in: gvfs (Ubuntu) Importance: Undecided = Wishlist ** Changed in: gvfs (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1200827 Title: Enable GOA backend Status in GVFS: Fix Released Status in “gvfs” package in Ubuntu: Triaged Bug description: The GNOME Online Accounts backend is needed for full ownCloud support with GNOME Online Accounts. This feature was not previously enabled in Ubuntu because we didn't have GOA 3.8 until last month. I verified that only gvfs-backends get the new libgoa-1.0-0 dependency. But seeded-in-ubuntu reports that gvfs-backends is not installed by default in ubuntu-touch. (See bug 1193018 for concerns about ubuntu-touch having a dependency on libgoa.) I'm attaching a patch that pulls the goa-enablement changes from Debian since I'll need sponsorship for this update. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Fri Jul 12 23:51:41 2013 InstallationDate: Installed on 2013-06-14 (28 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1200827/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1187889] Re: Empathy accounts window crashes when I click on my gmail account
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: empathy (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1187889 Title: Empathy accounts window crashes when I click on my gmail account Status in “empathy” package in Ubuntu: Confirmed Bug description: Running 12.04 LTS empathy 3.4.2.3-0ubuntu1 I expected to see the account information when I clicked on my gmail account Instead of that, the window closes itself rather quickly P.S. If I forgot anything, let me know (I am a NOOB when it comes to bug reporting) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.4.2.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-45.70-generic 3.2.44 Uname: Linux 3.2.0-45-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Wed Jun 5 14:06:21 2013 ExecutablePath: /usr/bin/empathy-accounts InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-10-13 (235 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1187889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
Date: Mon, 15 Jul 2013 09:00:23 + From: 1191...@bugs.launchpad.net To: babisxanthopou...@hotmail.com Subject: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg Could you please unplug all USB devices, plug in just the Microsoft Wireless Mouse, and then immediately open the Terminal (hit the Windows key in your keyboard and type Terminal) and paste the following command there? lsusb -v lsusb-v.log You will then find a called lsusb-v.log in your home folder. Could you attach that file to this report please? You can remove Ubuntu One by following the instructions at http://askubuntu.com/q/309122/8973. As for LibreOffice, you can find help with your problem in the support forum of your local Ubuntu community at http://loco.ubuntu.com/ or asking at http://askubuntu.com , https://answers.launchpad.net/ubuntu or http://ubuntuforums.org. Please do not use this bug report for further support requests, as this is not the best place for it. Thanks. ** Changed in: linux (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1191334 Title: A wrong hardware detection seems to crash Xorg Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: A wrong hardware detection seems to crash Xorg. This report is generated without a wireless mouse, which was connected to the laptop in the duplicate bug 1190987 but the mouse didn't make a difference to the system's stability. Both the xorg.log and the attachment refer to a Microsoft MicrosoftR Nano Transceiver but the laptop is not connected a a wireless keyboard. From Xorg.log: (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3] (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286] (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101] (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424] (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b] (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1] (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6] (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422] (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b] (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25] (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441] (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd] (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa] (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083] (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb] (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3] (EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04] (EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4] (EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d] (EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525] (EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935] (EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. [mi] Increasing EQ size to 512 to prevent dropped events. [ 19459.082] [mi] EQ processing has resumed after 19 dropped events. [ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 20581.964] (II) config/udev: removing device Microsoft MicrosoftR Nano Transceiver v2.0 [ 20586.862] (II) evdev: Microsoft MicrosoftR Nano Transceiver v2.0: Close [ 20588.924] (II) UnloadModule: evdev ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jun 15 18:34:14 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring
[Desktop-packages] [Bug 1166916] Re: temperature overheating of cpu and radeon in 12.10 and above
The better power management for AMD/ATI Radeon R600 and newer hardware (as described in comment #6) is finally available in the upstream 3.11 linux kernel. The first release candidate (3.11-rc1) of the 3.11 kernel is available at http://kernel.ubuntu.com/~kernel-ppa/mainline/ and instructions on how to install and uninstall it are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds To use this power management for the AMD/ATI Radeon you will need to select it at boot by adding radeon.dpm=1 to your GRUB kernel boot options as described at https://help.ubuntu.com/community/Grub2/Troubleshooting#Editing_the_GRUB_2_Menu_During_Boot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1166916 Title: temperature overheating of cpu and radeon in 12.10 and above Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: 13.04 Ubuntustudio 64 bit under moderate load temperature is around 81c under high load (playing video inside a virtualbox) temperature hit 94c at which point I turned it off I have tested this with all 3 of the radeon drivers, with no significant difference. The radeon temp is always about 2-3 degrees hotter than the rest, so suspect that is souce of problem. 10.10 does not have this problem at all 12.04 runs 5-10 degrees hotter on average than does 10.10 but starting with 12.10 the temperature gets unusably hot ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-14-lowlatency 3.8.0-14.9 ProcVersionSignature: Ubuntu 3.8.0-14.9-lowlatency 3.8.4 Uname: Linux 3.8.0-14-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CasperVersion: 1.330 Date: Tue Apr 9 17:11:07 2013 LiveMediaBuild: Ubuntu-Studio 13.04 Raring Ringtail - Alpha amd64 (20130403) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lowlatency UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1166916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1155141] Re: nmcli crashed with SIGSEGV in g_ptr_array_foreach()
*** This bug is a duplicate of bug 1155139 *** https://bugs.launchpad.net/bugs/1155139 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1155141 Title: nmcli crashed with SIGSEGV in g_ptr_array_foreach() Status in “network-manager” package in Ubuntu: Confirmed Bug description: During checkbox system testing. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 CRDA: country NO: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Thu Mar 14 14:35:15 2013 ExecutablePath: /usr/bin/nmcli IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-03 (69 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IpRoute: default via 192.168.10.1 dev wlan1 proto static 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.10.0/24 dev wlan1 proto kernel scope link src 192.168.10.24 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nmcli dev list RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SegvAnalysis: Segfault happened at: 0x41331e: mov0x8(%r13),%edi PC (0x0041331e) ok source 0x8(%r13) (0x0008) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () g_ptr_array_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 do_devices () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nmcli crashed with SIGSEGV in g_ptr_array_foreach() UpgradeStatus: Upgraded to raring on 2013-03-13 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-01-04T09:39:07.434361 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1155141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1032612] Re: Xorg crash in BasicComputeAcceleration
I wonder if: Jul 15 10:24:45 localhost kernel: [ 6828.883008] plugin-containe[10838]: segfault at 7feb75f64ac0 ip 7feb89c9c0f5 sp 7feb70872b20 error 6 in libpthread-2.17.so[7feb89c8f000+18000] is related? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1032612 Title: Xorg crash in BasicComputeAcceleration Status in “xserver-xorg-input-synaptics” package in Ubuntu: Fix Released Bug description: Since about 2 weeks, my Xorg randomly crashes on my Thinkpad T410s (jumping back to login screen). Happens mainly during wakeup, but not only. I was running 12.04 for several weeks without this issue before. Initially I thought this is the same as #1026777, but the segfault seems to occur in a different function. Seeing that synaptics_drv.so is involved, I already tried to deactivate the touchpad (with synclient TouchpadOff=1), but didn't help. However the trackpoint is still on and I don't know if that's handled by the same driver. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Fri Aug 3 14:31:52 2012 DistroCodename: precise DistroVariant: kubuntu EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to precise on 2012-05-17 (77 days ago) --- .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,snap,wall,grid,resize,imgpng,vpswitch,compiztoolbox,regex,move,place,animation,gnomecompat,expo,session,unitymtgrabhandles,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: kwin DistUpgraded: 2012-05-17 23:24:51,430 DEBUG enabling apt cron job DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21c1] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 29124NG Package: xorg 1:7.6+12ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic root=UUID=e56748e9-2b6d-4d64-81e2-cd1f2a6ab6d6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Tags: precise kubuntu Uname: Linux 3.2.0-27-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-05-17 (77 days ago) UserGroups: adm admin cdrom davfs2 dialout libvirtd lpadmin plugdev sambashare dmi.bios.date: 05/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET64WW (1.44 ) dmi.board.name: 29124NG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET64WW(1.44):bd05/10/2011:svnLENOVO:pn29124NG:pvrThinkPadT410s:rvnLENOVO:rn29124NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 29124NG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1.2 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1032612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 858775] Re: gnome-keyring-daemon hogs CPU
This happens to me with google chrome, but not with chromiun-browser. If i make sure all google chrome processes are killed and restart gnome- keyring-d, it doesn't happen any more. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/858775 Title: gnome-keyring-daemon hogs CPU Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: I just upgraded my Nokia Booklet to Oneiric, and noticed that gnome- keyring-daemon is using about 40% CPU all the time. Here's a snippet from strace: time(NULL) = 1316942473 times({tms_utime=10433, tms_stime=907, tms_cutime=112, tms_cstime=7}) = 1718106444 gettimeofday({1316942473, 940560}, NULL) = 0 getrusage(RUSAGE_SELF, {ru_utime={104, 338520}, ru_stime={9, 72567}, ...}) = 0 time(NULL) = 1316942473 times({tms_utime=10433, tms_stime=907, tms_cutime=112, tms_cstime=7}) = 1718106444 gettimeofday({1316942473, 941462}, NULL) = 0 getrusage(RUSAGE_SELF, {ru_utime={104, 338520}, ru_stime={9, 72567}, ...}) = 0 time(NULL) = 1316942473 times({tms_utime=10433, tms_stime=907, tms_cutime=112, tms_cstime=7}) = 1718106444 gettimeofday({1316942473, 942363}, NULL) = 0 getrusage(RUSAGE_SELF, {ru_utime={104, 338520}, ru_stime={9, 72567}, ...}) = 0 time(NULL) = 1316942473 times({tms_utime=10433, tms_stime=907, tms_cutime=112, tms_cstime=7}) = 1718106444 gettimeofday({1316942473, 943249}, NULL) = 0 getrusage(RUSAGE_SELF, {ru_utime={104, 342521}, ru_stime={9, 72567}, ...}) = 0 time(NULL) = 1316942473 times({tms_utime=10434, tms_stime=907, tms_cutime=112, tms_cstime=7}) = 1718106444 gettimeofday({1316942473, 944096}, NULL) = 0 getrusage(RUSAGE_SELF, {ru_utime={104, 342521}, ru_stime={9, 72567}, ...}) = 0 time(NULL) = 1316942473 times({tms_utime=10434, tms_stime=907, tms_cutime=112, tms_cstime=7}) = 1718106444 gettimeofday({1316942473, 944909}, NULL) = 0 getrusage(RUSAGE_SELF, {ru_utime={104, 342521}, ru_stime={9, 72567}, ...}) = 0 It seems to be spinning within dbus_connection_dispatch, I'll see if I can come up with a backtrace. gnome-keyring is version 3.1.92-0ubuntu1. The system differs from a normal Oneiric install in one regard: for some reason I can't get gdm to start on login, so it actually boots into a console and I sudo start gdm from there. Don't know if it affects anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/858775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201372] [NEW] Loosing sound in Windows after rebooting from Linux (Realtek ALC269VB)
Public bug reported: When I reboot from Xubuntu 12.10 to Windows 7 I loose headphone sound in Windows. I checked the volume levels and even reinstalled Realtek audio drivers in Windows, but nothing has helped so far. Only workaround is to shutdown notebook from Xubuntu 12.10 rather than rebooting directly to Windows. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu11 Architecture: amd64 Date: Mon Jul 15 13:18:40 2013 InstallationDate: Installed on 2013-01-17 (178 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53BR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd04/25/2012:svnASUSTeKComputerInc.:pnK53BR:pvr1.0:rvnASUSTeKComputerInc.:rnK53BR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53BR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-07-15T12:54:29.052652 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201372 Title: Loosing sound in Windows after rebooting from Linux (Realtek ALC269VB) Status in “alsa-driver” package in Ubuntu: New Bug description: When I reboot from Xubuntu 12.10 to Windows 7 I loose headphone sound in Windows. I checked the volume levels and even reinstalled Realtek audio drivers in Windows, but nothing has helped so far. Only workaround is to shutdown notebook from Xubuntu 12.10 rather than rebooting directly to Windows. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu11 Architecture: amd64 Date: Mon Jul 15 13:18:40 2013 InstallationDate: Installed on 2013-01-17 (178 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53BR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd04/25/2012:svnASUSTeKComputerInc.:pnK53BR:pvr1.0:rvnASUSTeKComputerInc.:rnK53BR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53BR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-07-15T12:54:29.052652 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
** Attachment added: lsusb-v.log https://bugs.launchpad.net/bugs/1191334/+attachment/3737314/+files/lsusb-v.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1191334 Title: A wrong hardware detection seems to crash Xorg Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: A wrong hardware detection seems to crash Xorg. This report is generated without a wireless mouse, which was connected to the laptop in the duplicate bug 1190987 but the mouse didn't make a difference to the system's stability. Both the xorg.log and the attachment refer to a Microsoft Microsoft® Nano Transceiver but the laptop is not connected a a wireless keyboard. From Xorg.log: (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3] (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286] (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101] (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424] (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b] (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1] (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6] (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422] (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b] (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25] (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441] (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd] (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa] (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083] (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb] (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3] (EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04] (EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4] (EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d] (EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525] (EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935] (EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. [mi] Increasing EQ size to 512 to prevent dropped events. [ 19459.082] [mi] EQ processing has resumed after 19 dropped events. [ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 20581.964] (II) config/udev: removing device Microsoft Microsoft® Nano Transceiver v2.0 [ 20586.862] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Close [ 20588.924] (II) UnloadModule: evdev ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jun 15 18:34:14 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices [AMD] nee ATI RC410M [Mobility Radeon Xpress 200M] [1002:5a62] (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions Device [1734:10fb] InstallationDate: Installed on 2013-02-12 (123 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) Lsusb: Bus 003 Device 003: ID 046d:0a10 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS AMILO Li 1718 MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash
[Desktop-packages] [Bug 1195662] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evolution-data-server (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1195662 Title: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head() Status in “evolution-data-server” package in Ubuntu: Confirmed Bug description: Crashed at login ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evolution-data-server 3.8.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Fri Jun 28 19:52:38 2013 ExecutablePath: /usr/lib/evolution/evolution-source-registry InstallationDate: Installed on 2013-06-22 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621) MarkForUpload: True ProcCmdline: /usr/lib/evolution/evolution-source-registry ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0x7f6da1c4375a g_slice_alloc+154:mov 0x8(%rdx),%rbx PC (0x7f6da1c4375a) ok source 0x8(%rdx) (0x15c11207f) not located in a known VMA region (needed readable region)! destination %rbx ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_bytes_new_with_free_func () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_byte () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1195662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201372] Re: Loosing sound in Windows after rebooting from Linux (Realtek ALC269VB)
`echo options snd-hda-intel model=asus | sudo tee -a /etc/modprobe.d /alsa-base.conf` doesn't help -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201372 Title: Loosing sound in Windows after rebooting from Linux (Realtek ALC269VB) Status in “alsa-driver” package in Ubuntu: New Bug description: When I reboot from Xubuntu 12.10 to Windows 7 I loose headphone sound in Windows. I checked the volume levels and even reinstalled Realtek audio drivers in Windows, but nothing has helped so far. Only workaround is to shutdown notebook from Xubuntu 12.10 rather than rebooting directly to Windows. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu11 Architecture: amd64 Date: Mon Jul 15 13:18:40 2013 InstallationDate: Installed on 2013-01-17 (178 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53BR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd04/25/2012:svnASUSTeKComputerInc.:pnK53BR:pvr1.0:rvnASUSTeKComputerInc.:rnK53BR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53BR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-07-15T12:54:29.052652 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
So much about LTS. Can anyone confirm this will ever be fixed or should we just abandon Linux since this is total showstopper in my company and I ran out of options and excuses :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 completely freezes frequently. Status in “linux” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “xserver-xorg-video-intel” source package in Precise: Fix Released Bug description: Update: 6/12/2012 This bug is about a complete system lock-up. No other TTYs can be started. Mouse doesn't move. Keyboard doesn't react. The only solution is hard reset. Seems to happen on a variety of configurations, including nVidia, ATI and Intel graphics. If you are still able to TTY or SSH into other sessions, move the mouse or use the keyboard, file another bug. Thx. Joris V. (brains). Update: 5/21/2012 Updating the kernel to 3.3.6 as suggested by Michael in #91, the system seems stable, no freezes yet in 5-6 hrs of using and watching videos for couple of hrs. Original description: I recently installed newly released ubuntu 12.04 LTS 64 bit version on my desktop. And it is frequently freezing, for the first few hours it ran smoothly and when I started watching videos it started freezing randomly. I have to use hard restart every time. Initially it was only during videos but now even during normal browsing it is freezing. I am using on board graphics and do not have any graphics card installed. Can someone please help me here, I really love the new looks of 12.04 and it bugs me not being able to use :( Below is my hardware configuration: Processor: Intel CORE i3 processor (2nd generation) Board: Intel® Desktop Board DH67BL Ram: 4GB Graphics: On board HDD: 500 GB Please let me know if you need more information, or any specific logs I can capture (and how). Thanks, Ketan Patil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm
A work around that works for me is killing the NetworkManager process using sudo killall NetworkManager. The daemon re-starts and the network is restored. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: network-manager has decided that networking is disabled, cannot be re- enabled from lightdm Status in “network-manager” package in Ubuntu: Confirmed Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1199186] Re: Back and foward keys doesn't work in Software Center
*** This bug is a duplicate of bug 936583 *** https://bugs.launchpad.net/bugs/936583 ** This bug has been marked a duplicate of bug 936583 Back and foward keys doesn't work in Software Center -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1199186 Title: Back and foward keys doesn't work in Software Center Status in “software-center” package in Ubuntu: New Bug description: When I browse in Ubuntu Software it possible by going back and foward in my operations by clicking on the back and forward keys on the left side in the topbar. I can olso navigate using Alt + Left or Right allow key, but when I try to use the speciel keys on my Thinkpad for Go back and go forward nothing happens. They work in most other applications like Firefox, Chromium, Opera and more. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: software-center 5.2.9 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Tue Jul 9 01:31:51 2013 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MarkForUpload: True PackageArchitecture: all SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1199186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201387] [NEW] Banshee crashes with locked database message
Public bug reported: I was running banshee in debug mode when it crashed with a message about a locked databse. a john@W530$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 13.04 Release:13.04 Codename: raring john@W530$ dpkg -l | grep banshee ii banshee 2.6.1-1ubuntu1 amd64Media Management and Playback application ii banshee-extension-soundmenu 2.6.1-1ubuntu1 amd64Media Management and Playback application - sound menu extension The output is attached. ** Affects: banshee (Ubuntu) Importance: Undecided Status: New ** Attachment added: debug output https://bugs.launchpad.net/bugs/1201387/+attachment/3737339/+files/bug.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1201387 Title: Banshee crashes with locked database message Status in “banshee” package in Ubuntu: New Bug description: I was running banshee in debug mode when it crashed with a message about a locked databse. a john@W530$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring john@W530$ dpkg -l | grep banshee ii banshee 2.6.1-1ubuntu1 amd64Media Management and Playback application ii banshee-extension-soundmenu 2.6.1-1ubuntu1 amd64Media Management and Playback application - sound menu extension The output is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1201387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to crash Xorg
babis x, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an update is available for your BIOS (1.90). If you update to this, does it change anything? If not, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date Thank you for your understanding. ** Summary changed: - A wrong hardware detection seems to crash Xorg + 045e:0745 A wrong hardware detection seems to crash Xorg ** Tags added: bios-outdated-v1.9 needs-upstream-testing regression- potential -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1191334 Title: 045e:0745 A wrong hardware detection seems to crash Xorg Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: A wrong hardware detection seems to crash Xorg. This report is generated without a wireless mouse, which was connected to the laptop in the duplicate bug 1190987 but the mouse didn't make a difference to the system's stability. Both the xorg.log and the attachment refer to a Microsoft Microsoft® Nano Transceiver but the laptop is not connected a a wireless keyboard. From Xorg.log: (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3] (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286] (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101] (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400] (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424] (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b] (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1] (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6] (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422] (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b] (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25] (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441] (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd] (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa] (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083] (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb] (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3] (EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04] (EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4] (EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d] (EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525] (EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935] (EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. [mi] Increasing EQ size to 512 to prevent dropped events. [ 19459.082] [mi] EQ processing has resumed after 19 dropped events. [ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 20581.964] (II) config/udev: removing device Microsoft Microsoft® Nano Transceiver v2.0 [ 20586.862] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Close [ 20588.924] (II) UnloadModule: evdev ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jun 15 18:34:14 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices [AMD] nee ATI RC410M [Mobility Radeon Xpress 200M] [1002:5a62] (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions Device [1734:10fb] InstallationDate: Installed on 2013-02-12 (123 days ago) InstallationMedia: Ubuntu
[Desktop-packages] [Bug 1201390] [NEW] Window moves up and down continuously
Public bug reported: Expected normal window display with no movement. For example, launching gedit from launchbar produces application window which moves up and down continuously. Running on Virtual Box 4.2.16 r86992 with 3d Acceleration enabled. Host machine Windows 8. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Mon Jul 15 11:46:09 2013 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2013-05-07 (68 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Attachment added: Video of launching gedit and window shaking https://bugs.launchpad.net/bugs/1201390/+attachment/3737352/+files/Ubuntu_13.04_Window_Shakes.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1201390 Title: Window moves up and down continuously Status in “gedit” package in Ubuntu: New Bug description: Expected normal window display with no movement. For example, launching gedit from launchbar produces application window which moves up and down continuously. Running on Virtual Box 4.2.16 r86992 with 3d Acceleration enabled. Host machine Windows 8. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Mon Jul 15 11:46:09 2013 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2013-05-07 (68 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1201390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1201387] [NEW] Banshee crashes with locked database message
On Mon, Jul 15, 2013 at 10:53:08AM -, John Reid wrote: Public bug reported: I was running banshee in debug mode when it crashed with a message about a locked databse. Sounds like the issue we had in the past with unity-music-daemon. Could you check the output of `lsof ~/.config/banshee-1/banshee.db` please? status incomplete -- Kind regards, Loong Jin ** Changed in: banshee (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1201387 Title: Banshee crashes with locked database message Status in “banshee” package in Ubuntu: Incomplete Bug description: I was running banshee in debug mode when it crashed with a message about a locked databse. a john@W530$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring john@W530$ dpkg -l | grep banshee ii banshee 2.6.1-1ubuntu1 amd64Media Management and Playback application ii banshee-extension-soundmenu 2.6.1-1ubuntu1 amd64Media Management and Playback application - sound menu extension The output is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1201387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1178248] Re: LO (4.0.3) hangs when testing mail merge settings in writer
Gilles Gravier, as per Google https://support.google.com/mail/troubleshooter/1668960?hl=enfrom=75726rd=1#ts=1665018,1665144 if port 465 doesn't work, then one would use 587 as an alternative. Thank you for reporting this and helping make Ubuntu better. Please feel free to report any future bugs you may find. ** Changed in: libreoffice (Ubuntu) Status: Expired = New ** Changed in: libreoffice (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1178248 Title: LO (4.0.3) hangs when testing mail merge settings in writer Status in “libreoffice” package in Ubuntu: Invalid Bug description: It hangs when I Launch Writer: - Tools-Options-LibreOffice Writer-Mail Merge E-mail - Fill in the details (I use Gmail's smtp.gmail.com, with SSL enabled and port 465). - Select Server Authentication, check Server requires authentication. - Enter Username (@gmail.com address) and password. - Click OK. - Close the settings by clicking OK. - Open Tools-Options-LibreOffice Writer-Mail Merge E-mail - Check settings are properly memorized. - Click Test settings... and that hangs. WORKAROUND: If you change the port from 465 to 587 it works fine. --- ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True Package: libreoffice 1:3.5.7-0ubuntu4 PackageArchitecture: i386 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-28.48~precise1-generic 3.5.7.9 Tags: precise running-unity Uname: Linux 3.5.0-28-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1178248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1189645] Re: TLP causing lag under desktop environments
I would suggest going through the TLP configuration option and turning each one on individually to see which causes the slowdown (if it is indeed just one option). If you are really good, you can use a bisect on the config options. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1189645 Title: TLP causing lag under desktop environments Status in X.org xf86-video-intel: New Status in “flashplugin-nonfree” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Status in “tlp” package in Ubuntu: New Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Status in “flashplugin-nonfree” source package in Raring: New Status in “linux” source package in Raring: Confirmed Status in “tlp” source package in Raring: New Status in “xserver-xorg-video-intel” source package in Raring: New Status in “flashplugin-nonfree” source package in Saucy: New Status in “linux” source package in Saucy: Confirmed Status in “tlp” source package in Saucy: New Status in “xserver-xorg-video-intel” source package in Saucy: Incomplete Bug description: A while after logging on, the system gets really slow. Menus and window movements take a while to respond, switching windows is slow, etc. This is a regression, it was not like this using Ubuntu 12.10, it just started on 13.04. Tried different desktops (Unity, GnomeFaillback, Lxde). They all have the same issue. Testing showed the issue is triggered by the TLP power management package. TLP was installed in an attempt to resolve issue of fan running constantly. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-23-generic 3.8.0-23.34 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 2357 F pulseaudio Date: Mon Jun 10 16:35:22 2013 HibernationDevice: RESUME=UUID=08003f81-dc4b-4697-adb9-c4f28291be17 InstallationDate: Installed on 2012-08-17 (297 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120724.2) MachineType: Dell Inc. Latitude D420 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=84ceb2d5-8fea-40c7-8d75-337c174735ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-23-generic N/A linux-backports-modules-3.8.0-23-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-05-04 (37 days ago) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0TJ984 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd12/18/2006:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0TJ984:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1189645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 894085] Re: On newly installed Firefox, spell checking is enabled but no language is selected
** Tags added: raring saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/894085 Title: On newly installed Firefox, spell checking is enabled but no language is selected Status in “firefox” package in Ubuntu: Confirmed Bug description: Test Case Install current daily, using the 11/26 for current test Open FF, go to a page you can type in Type a word, mis-spell it, No spell correction is done Highlight the word, Check spelling is enabled Click on Languages no language will be selected Selecting the language will then start spell checking, language should be slected by default Attaching image in comment 5 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 9.0~b2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0 Uname: Linux 3.1.0-2-generic i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.26-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1448 F pulseaudio BuildID: 2017222449 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 47' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:83847616,10280209,00100201' Controls : 27 Simple ctrls : 18 Channel: beta Date: Wed Nov 23 12:28:22 2011 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (2022) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.102 metric 2 Plugins: QuickTime Plug-in 7.6.6 - Lib=libtotem-narrowspace-plugin.so, Location=/usr/lib/mozilla/plugins DivX® Web Player - Lib=libtotem-mully-plugin.so, Location=/usr/lib/mozilla/plugins Windows Media Player Plug-in 10 (compatible; Totem) - Lib=libtotem-gmp-plugin.so, Location=/usr/lib/mozilla/plugins VLC Multimedia Plugin (compatible Totem 3.0.1) - Lib=libtotem-cone-plugin.so, Location=/usr/lib/mozilla/plugins ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=9.0/2017222449 (Running) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Nov 23 11:47:28 doug-XPS-M1330 kernel: [ 2485.996721] nautilus[1455]: segfault at 60 ip 080cc9a7 sp bfbda390 error 4 in nautilus[8048000+169000] Nov 23 11:54:02 doug-XPS-M1330 kernel: [ 2879.788096] CE: hpet increased min_delta_ns to 20113 nsec Nov 23 12:18:44 doug-XPS-M1330 kernel: [ 4362.073947] nautilus[3435]: segfault at 60 ip 080cc9a7 sp bfac3ff0 error 4 in nautilus[8048000+169000] dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/894085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1200866] Re: multi-touch screen functions break when using chromium
Very likely a dupe of bug #1068994 -- but if lucky it's http://bugs.freedesktop.org/show_bug.cgi?id=66720 I uploaded the fix for the second bug to ppa:canonical-x/x-staging -- can you test when it finishes building? ** Bug watch added: freedesktop.org Bugzilla #66720 https://bugs.freedesktop.org/show_bug.cgi?id=66720 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1200866 Title: multi-touch screen functions break when using chromium Status in “xorg” package in Ubuntu: New Bug description: Steps: 1. Have a multi-touch monitor 2. run terminal 3. use 3 finger swipe to put it into resize and resposition window, note that it works using multi-touch on the screen 4. run chromium 5. go to http://reddpics.com/r/cats (or similar) 6. click 3 cat pictures with your finger on touch screen 7. use your finger on the screen to click between the open tabs Result: After a few clicks the taps stop working ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu4 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: Sat Jul 13 09:26:27 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3903] InstallationDate: Installed on 2013-06-18 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130617) MachineType: LENOVO Lenovo IdeaPad U310 Touch MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic.efi.signed root=UUID=f26c50a8-eb98-479c-ad80-1906e5d1e626 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 65CN97WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad U310 Touch dmi.modalias: dmi:bvnLENOVO:bvr65CN97WW:bd01/29/2013:svnLENOVO:pnLenovoIdeaPadU310Touch:pvrLenovoIdeaPadU310Touch:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadU310Touch: dmi.product.name: Lenovo IdeaPad U310 Touch dmi.product.version: Lenovo IdeaPad U310 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Sat Jul 13 09:25:12 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.1-0ubuntu1 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1200866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 879473] Re: Document viewer does not support OpenType features
** Changed in: evince (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/879473 Title: Document viewer does not support OpenType features Status in “evince” package in Ubuntu: New Bug description: Document viewer does display alternative glyphs activated through the OpenType tables but when I try to copy/paste outside of it, instead of the glyphs I only see a blank space. Most probably, that means that Document Viewer isn't able to connect the glyph with the underlying character code. Example: in a Serbian text U+0431 CYRILLIC SMALL LETTER BE has a Serbian localized glyph, which is different from the standard glyph, but when I copy that text, in the worst case scenario I should still be able to see a standard BE, leaving to the receiving program (Text Editor, Writer etc...) the capability (or incapability) to process OpenType features. But I only get a blank space instead. The right panel (with indexes etc...) doesn't even display the weird glyphs, only standard ones, and this is an additional nuisance, as the appearance turns out to be different from the main text. Another example: ligatures ct, ff, fi, etc... I get the same problem, they disappear, not just the ligatures, but the characters themselves, when I copy/paste. This is a very complicated issue, but I hope I've been able to make my point reasonably clear. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evince 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 21 16:27:46 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/879473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201387] Re: Banshee crashes with locked database message
john@W530$ lsof ~/.config/banshee-1/banshee.db COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME unity-mus 2969 john9u REG 252,1 45050880 401760 /home/john/.config/banshee-1/banshee.db banshee 25995 john9u REG 252,1 45050880 401760 /home/john/.config/banshee-1/banshee.db -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1201387 Title: Banshee crashes with locked database message Status in “banshee” package in Ubuntu: Incomplete Bug description: I was running banshee in debug mode when it crashed with a message about a locked databse. a john@W530$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring john@W530$ dpkg -l | grep banshee ii banshee 2.6.1-1ubuntu1 amd64Media Management and Playback application ii banshee-extension-soundmenu 2.6.1-1ubuntu1 amd64Media Management and Playback application - sound menu extension The output is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1201387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1189014] Re: Ubuntu 13.10 doesn't see USB sound card
** Changed in: alsa-utils (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1189014 Title: Ubuntu 13.10 doesn't see USB sound card Status in “alsa-utils” package in Ubuntu: Invalid Bug description: I have USB headset Platronics Gamecom 777. It worked fine in Ubuntu 13.04, but with 13.10 I don't see it in the list of sound devices, however it is listed correctly in lsusb: Bus 003 Device 003: ID 047f:ad01 Plantronics, Inc. GameCom 777 5.1 Headset I'm not sure, what caused this, but now on my desktop only integrated sound works. --- ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-04-27 (406 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) MarkForUpload: True Package: alsa-utils 1.0.25-4ubuntu2 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.10.0-rc4-bulldozer x86_64 UpgradeStatus: Upgraded to saucy on 2013-05-12 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1189014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201403] [NEW] Unity performance issue on intel gpu
Public bug reported: The overall performance of my notebook feels worse when I Use unity. After starting my computer everything seems to be fast, however in a short time (in 1 hour, or less based on usage) things became slow, and sometimes sluggish. A reboot seems to solve this. Suspend/resume seems to make things slower a bit For comparison I tried using XFCE for a while (compositing disabled). The overall performance felt better. Webpages tend to scroll smoother, intellij IDEA used to slow down (noticable lag when typing), I didn't notice this behaviour while I used xfce, even when the IDE did some cpu intensive like rebuilding indexes. When I use Unity the cpu usage of compiz grows over time even if nothing happens on the screen, and I close every application. Also my battery seems to drain faster ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu4 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: Mon Jul 15 13:38:02 2013 DistUpgraded: 2013-06-24 19:15:01,815 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.16, 3.10.0-2-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2013-04-29 (77 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: TOSHIBA PORTEGE Z830 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.0-2-generic root=/dev/mapper/hostname-root ro quiet libata.force=noncq splash pcie_aspm=force i915.i915_enable_fbc=1 i915.lvds_downclock=1 acpi_osi=Linux acpi_backlight=vendor elevator=noop vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to saucy on 2013-06-24 (20 days ago) dmi.bios.date: 04/18/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.80 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.80:bd04/18/2013:svnTOSHIBA:pnPORTEGEZ830:pvrPT224E-017014HU:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z830 dmi.product.version: PT224E-017014HU dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Mon Jul 15 13:34:43 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.1-0ubuntu1 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 performance saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1201403 Title: Unity performance issue on intel gpu Status in “xorg” package in Ubuntu: New Bug description: The overall performance of my notebook feels worse when I Use unity. After starting my computer everything seems to be fast, however in a short time (in 1 hour, or less based on usage) things became slow, and sometimes sluggish. A reboot seems to solve this. Suspend/resume seems to make things slower a bit For comparison I tried using XFCE for a while (compositing disabled). The overall performance felt better. Webpages tend to scroll smoother, intellij IDEA used to slow down (noticable lag when typing), I didn't notice this behaviour while I used xfce, even when the IDE did some cpu intensive like rebuilding indexes. When I use Unity the cpu usage of compiz grows over time even if nothing happens on the screen, and I close every application. Also my battery seems to drain faster ProblemType: Bug
[Desktop-packages] [Bug 681425] Re: quadrapassel will not run
This issue was last confirmed against Ubuntu 11.04 which reached end of life on October 28, 2012. (See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases) When I tried just now, quadrapassel runs without any problems on Ubuntu 12.04. Are anyone still able to reproduce this issue on a later release, or can it be closed? ** Changed in: gnome-games (Ubuntu) Status: Confirmed = Incomplete ** Tags added: natty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/681425 Title: quadrapassel will not run Status in “gnome-games” package in Ubuntu: Incomplete Bug description: Binary package hint: software-center On newly installed Ubuntu 10.10, all games startup ok from Apps/Games menu APART from Quadrapassel? This tries to launch (spinning disc for a while) but nothing else happens ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: software-center 3.0.5 ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic i686 Architecture: i386 Date: Thu Nov 25 15:02:32 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: software-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/681425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1194410] Re: Apply upstream patch to close XXE vulnerability in precise
This bug was fixed in the package libxml2 - 2.7.8.dfsg-5.1ubuntu4.5 --- libxml2 (2.7.8.dfsg-5.1ubuntu4.5) precise-security; urgency=low * SECURITY UPDATE: external entity expansion attack (LP: #1194410) - do not fetch external parsed entities in parser.c, added test to test/errors/extparsedent.xml, result/errors/extparsedent.xml. - https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f - CVE-2013-0339 * SECURITY UPDATE: denial of service via incomplete document - try to stop parsing as quickly as possible in parser.c, include/libxml/xmlerror.h. - https://git.gnome.org/browse/libxml2/commit/?id=48b4cdde3483e054af8ea02e0cd7ee467b0e9a50 - https://git.gnome.org/browse/libxml2/commit/?id=e50ba8164eee06461c73cd8abb9b46aa0be81869 - CVE-2013-2877 -- Marc Deslauriers marc.deslauri...@ubuntu.com Thu, 11 Jul 2013 14:57:48 -0400 ** Changed in: libxml2 (Ubuntu Precise) Status: In Progress = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-2877 ** Changed in: libxml2 (Ubuntu Lucid) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1194410 Title: Apply upstream patch to close XXE vulnerability in precise Status in “libxml2” package in Ubuntu: Fix Released Status in “libxml2” source package in Lucid: Fix Released Status in “libxml2” source package in Precise: Fix Released Status in “libxml2” source package in Quantal: Fix Released Status in “libxml2” source package in Raring: Fix Released Status in “libxml2” source package in Saucy: Fix Released Bug description: In version 2.7.8 there is no way to avoid opening and reading a file if it is specified in the ENTITY section of the document. The issue has been raised in: https://mail.gnome.org/archives/xml/2012-October/msg2.html https://github.com/sparklemotion/nokogiri/issues/693 An upstream fix has been released: https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1194410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1194410] Re: Apply upstream patch to close XXE vulnerability in precise
This bug was fixed in the package libxml2 - 2.7.6.dfsg-1ubuntu1.9 --- libxml2 (2.7.6.dfsg-1ubuntu1.9) lucid-security; urgency=low * SECURITY UPDATE: external entity expansion attack (LP: #1194410) - do not fetch external parsed entities in parser.c, added test to test/errors/extparsedent.xml, result/errors/extparsedent.xml. - https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f - CVE-2013-0339 * SECURITY UPDATE: denial of service via incomplete document - try to stop parsing as quickly as possible in parser.c, include/libxml/xmlerror.h. - https://git.gnome.org/browse/libxml2/commit/?id=48b4cdde3483e054af8ea02e0cd7ee467b0e9a50 - https://git.gnome.org/browse/libxml2/commit/?id=e50ba8164eee06461c73cd8abb9b46aa0be81869 - CVE-2013-2877 -- Marc Deslauriers marc.deslauri...@ubuntu.com Thu, 11 Jul 2013 15:07:11 -0400 ** Changed in: libxml2 (Ubuntu Quantal) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1194410 Title: Apply upstream patch to close XXE vulnerability in precise Status in “libxml2” package in Ubuntu: Fix Released Status in “libxml2” source package in Lucid: Fix Released Status in “libxml2” source package in Precise: Fix Released Status in “libxml2” source package in Quantal: Fix Released Status in “libxml2” source package in Raring: Fix Released Status in “libxml2” source package in Saucy: Fix Released Bug description: In version 2.7.8 there is no way to avoid opening and reading a file if it is specified in the ENTITY section of the document. The issue has been raised in: https://mail.gnome.org/archives/xml/2012-October/msg2.html https://github.com/sparklemotion/nokogiri/issues/693 An upstream fix has been released: https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1194410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1194410] Re: Apply upstream patch to close XXE vulnerability in precise
This bug was fixed in the package libxml2 - 2.8.0+dfsg1-5ubuntu2.3 --- libxml2 (2.8.0+dfsg1-5ubuntu2.3) quantal-security; urgency=low * SECURITY UPDATE: external entity expansion attack (LP: #1194410) - debian/patches/CVE-2013-0339.patch: do not fetch external parsed entities in parser.c, added test to test/errors/extparsedent.xml, result/errors/extparsedent.xml. - CVE-2013-0339 * SECURITY UPDATE: denial of service via incomplete document - debian/patches/CVE-2013-2877.patch: try to stop parsing as quickly as possible in parser.c, include/libxml/xmlerror.h. - CVE-2013-2877 -- Marc Deslauriers marc.deslauri...@ubuntu.com Thu, 11 Jul 2013 14:53:41 -0400 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1194410 Title: Apply upstream patch to close XXE vulnerability in precise Status in “libxml2” package in Ubuntu: Fix Released Status in “libxml2” source package in Lucid: Fix Released Status in “libxml2” source package in Precise: Fix Released Status in “libxml2” source package in Quantal: Fix Released Status in “libxml2” source package in Raring: Fix Released Status in “libxml2” source package in Saucy: Fix Released Bug description: In version 2.7.8 there is no way to avoid opening and reading a file if it is specified in the ENTITY section of the document. The issue has been raised in: https://mail.gnome.org/archives/xml/2012-October/msg2.html https://github.com/sparklemotion/nokogiri/issues/693 An upstream fix has been released: https://git.gnome.org/browse/libxml2/commit/?id=4629ee02ac649c27f9c0cf98ba017c6b5526070f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1194410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1030573] Re: Problem selecting destination folder
*** This bug is a duplicate of bug 915165 *** https://bugs.launchpad.net/bugs/915165 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1030573 Title: Problem selecting destination folder Status in “transmission” package in Ubuntu: Confirmed Bug description: Everytime i open a new torrent file with transmission i have problem to choose the correct destination folder. The program suggest as destination folder the default dir and all recent dir but if i select one of the recent dir it automatically select the first subdir in it. I need always choose other and then select the correct dir. I'm using TRANSMISSION v. 2.51 on ubuntu 12.04 64 bit in failback mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1030573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1113420] Re: Alt+key window menu shortcuts cannot be disabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1113420 Title: Alt+key window menu shortcuts cannot be disabled Status in “nautilus” package in Ubuntu: Confirmed Bug description: I find the alt key ergonomically very useful (it can be pressed with a thumb without moving any of the letter fingers) and I would like to use it for many custom keyboard shortcuts (there is a reason why it plays such a big role in Emacs and the whole OS X for that matter). Currently, though, alt is hardcoded to activate window menu entries (such as alt+F for the file menu, alt+E for the edit menu) and there is no way to surpass this functionality in all the applications. Personally, I find these shortcuts quite useless - they take you to copy, paste, and open file which have standard shortcuts anyway (with the exception of preferences, which for some reason don't have a standardized shortcut even though that's often the only thing a person looks for up there). Expected behaviour - What I would like to see is a global option to disable these alt+key menu shortcuts to free up the alt key for other uses (similar to the option already available in gnome-terminal, only global). Preferably, activating this option would also remove the first-letter underlining in the menu to indicate to users that they can't acess it through shortcuts. (I marked nautilus for apport to collect my version numbers, but this affects most applications - didn't know what the right target is) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Feb 2 13:22:32 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'931x626+1+80' b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true' InstallationDate: Installed on 2012-10-19 (106 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1113420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170783] Re: Opening shutdown dialog immediately triggers reboot
My problem seems similar, except that in my case it seems to automatically opt for the shutdown option. Happens once in a while too, but not consistently, so really hard to figure out how to reproduce it. Pretty horrible bug when you're thinking about hibernating/suspending but instead get a forced shutdown... :| -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1170783 Title: Opening shutdown dialog immediately triggers reboot Status in “gnome-session” package in Ubuntu: Confirmed Bug description: gnome-session package version: 3.8.0-0ubuntu1~raring1 Since switching to Ubuntu 13.04, clicking on Shutdown ... from the menu makes the shutdown dialog pop up for a second and automatically triggers a system reboot. This behavior can be seen in about four out of five times. The same problem occurs when the power button of the PC is pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1170783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170783] Re: Opening shutdown dialog immediately triggers reboot
Edit to #3: oops, in my case it isn't the shutdown dialog per se, but the dialog whatever it is called, that open e.g. when pressing laptop's power button (the one that shows all five options: lock / suspend / hibernate / restart / shutdown). But it sounds like the same sort of bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1170783 Title: Opening shutdown dialog immediately triggers reboot Status in “gnome-session” package in Ubuntu: Confirmed Bug description: gnome-session package version: 3.8.0-0ubuntu1~raring1 Since switching to Ubuntu 13.04, clicking on Shutdown ... from the menu makes the shutdown dialog pop up for a second and automatically triggers a system reboot. This behavior can be seen in about four out of five times. The same problem occurs when the power button of the PC is pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1170783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1154049] Re: Crashes with GLib-GIO-CRITICAL. UnknownMethod: Method DescribeAll
I have the same issue, also under 13.04, with seahorse version 3.6.3. The bug has been fixed in seahorse, apparently, although I haven't figured out yet what version (they helpfully say HEAD). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1154049 Title: Crashes with GLib-GIO-CRITICAL. UnknownMethod: Method DescribeAll Status in Seahorse: Fix Released Status in “seahorse” package in Ubuntu: Confirmed Bug description: I cannot open seahorse anymore, even from the terminal: (seahorse:23605): GLib-GIO-CRITICAL **: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method DescribeAll with signature on interface org.gtk.Actions doesn't exist I'm on GNOME Shell 3.6.2 with Ubunut 12.10 on 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1154049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1177283] Re: Xorg crash
** Description changed: After yesterday's upgrades xorg started crashing randomly, as of now, only when surfing the net with firefox. Ubuntu 13.04 xorg: - Installed: 1:7.7+1ubuntu4 - Candidate: 1:7.7+1ubuntu4 - Version table: - *** 1:7.7+1ubuntu4 0 - 500 http://pl.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.7+1ubuntu4 + Candidate: 1:7.7+1ubuntu4 + Version table: + *** 1:7.7+1ubuntu4 0 + 500 http://pl.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 7 10:07:19 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: - oem-audio-hda-daily, 0.201304220024~raring1, 3.8.0-17-generic, x86_64: installed - oem-audio-hda-daily, 0.201304220024~raring1, 3.8.0-19-generic, x86_64: installed + oem-audio-hda-daily, 0.201304220024~raring1, 3.8.0-17-generic, x86_64: installed + oem-audio-hda-daily, 0.201304220024~raring1, 3.8.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:1702] + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:1702] InstallationDate: Installed on 2013-02-21 (74 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130221.1) MachineType: ASUSTeK Computer Inc. U50F MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=f97a5e61-20f1-4f04-973f-e76ff58a9c11 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U50F.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U50F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU50F.202:bd11/27/2009:svnASUSTeKComputerInc.:pnU50F:pvr1.0:rvnASUSTeKComputerInc.:rnU50F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U50F dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.44+git20130502.0112-0ubuntu0sarvatt version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.0~git20130503.e495d884-0ubuntu0sarvatt version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.0~git20130503.e495d884-0ubuntu0sarvatt version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.99+git20130315.3e5350be-0ubuntu0sarvatt version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6+git20130502.5637c173-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Tue May 7 09:37:41 2013 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1177283 Title: Xorg crash Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After yesterday's upgrades xorg started crashing randomly, as of now, only when surfing the net with firefox. Ubuntu 13.04 xorg: Installed: 1:7.7+1ubuntu4 Candidate: 1:7.7+1ubuntu4 Version table: *** 1:7.7+1ubuntu4 0 500 http://pl.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8
[Desktop-packages] [Bug 1199966] Re: xmir: i have two cursors!
This seems to be fixed with the latest update. ** Changed in: xorg (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1199966 Title: xmir: i have two cursors! Status in “xorg” package in Ubuntu: Invalid Bug description: I have two cursors on the screen after updating the xmir version of xorg. Using intel drivers. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.10.0-2.9~lp1189998v201307100907-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu4 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: Wed Jul 10 15:19:18 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-06-05 (34 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605) MachineType: LENOVO 42872WU MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=94d4ed1f-8182-4805-8d5b-6944f6f1c428 ro crashkernel=384M-2G:64M,2G-:128M debug ignore_loglevel SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET55WW (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 42872WU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET55WW(1.25):bd11/01/2011:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42872WU dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2~git20130628.g6b676e6-0ubuntu0+mir4-jenkins86saucy0 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2~git20130628.g6b676e6-0ubuntu0+mir4-jenkins86saucy0 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu0.8+xmir1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0+xmir2537-0~saucy1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9+xmir5865-0~saucy1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8+xmir2340-0~saucy1 xserver.bootTime: Wed Jul 10 15:16:20 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.1-0ubuntu0.8+xmir1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1199966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163999] Re: Libcroco uses wrong green color
This bug was fixed in the package libcroco - 0.6.5-1ubuntu0.1 --- libcroco (0.6.5-1ubuntu0.1) precise; urgency=low * debian/patches/git-revert-green-change.patch: - Revert change to the green color since it violates the CSS and SVG standards (LP: #1163999) -- Jeremy Bicha jbi...@ubuntu.com Tue, 09 Apr 2013 13:43:15 +0100 ** Changed in: libcroco (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcroco in Ubuntu. https://bugs.launchpad.net/bugs/1163999 Title: Libcroco uses wrong green color Status in Libcroco - C Library to suppost CSS parsing and manipulation: Fix Released Status in “libcroco” package in Ubuntu: Fix Released Status in “libcroco” source package in Precise: Fix Released Status in “libcroco” source package in Quantal: Fix Released Bug description: [Impact] libcroco [1] had a bug [2] in its versions 0.6.5 and 0.6.6, which results in e.g. librsvg rendering wrong green color. The bug has been fixed since 0.6.7 [3], but the Ubuntu 12.04 Precise LTS version contains the broken version 0.6.5-1 (and Quantal uses a newer, but still broken, 0.6.6-1; Raring seems to use the current (fixed) 0.6.8-1). [4] Because Wikimedia Foundation wikis (including Wikipedia and Wikimedia Commons) suffer from this bug in SVG rendering [5], I was referred to here to report it/ask for the library to be updated, prior to patching it locally. This fix libcroco so that it again complies with the CSS SVG standards. [Test Case] [Regression Potential] This is a one line patch that has been shipped in libcroco 0.6.7 for six months. [Rest of original bug report] As I am not acquainted with Ubuntu/Debian policies/requirements/workflow for such changes, I hope I am not reporting it in a _completely_ wrong place… If so, feel free to forward this, or point me to a better place. Thanks. [1] https://launchpad.net/ubuntu/+source/libcroco [2] https://bugzilla.gnome.org/show_bug.cgi?id=672332#c4 [3] https://git.gnome.org/browse/libcroco/log/ [4] https://launchpad.net/libcroco/+packages [5] https://bugzilla.wikimedia.org/show_bug.cgi?id=46540 To manage notifications about this bug go to: https://bugs.launchpad.net/libcroco/+bug/1163999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163999] Re: Libcroco uses wrong green color
This bug was fixed in the package libcroco - 0.6.6-1ubuntu0.1 --- libcroco (0.6.6-1ubuntu0.1) quantal; urgency=low * debian/patches/git-revert-green-change.patch: - Revert change to the green color since it violates the CSS and SVG standards (LP: #1163999) -- Jeremy Bicha jbi...@ubuntu.com Tue, 09 Apr 2013 13:37:11 +0100 ** Changed in: libcroco (Ubuntu Quantal) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcroco in Ubuntu. https://bugs.launchpad.net/bugs/1163999 Title: Libcroco uses wrong green color Status in Libcroco - C Library to suppost CSS parsing and manipulation: Fix Released Status in “libcroco” package in Ubuntu: Fix Released Status in “libcroco” source package in Precise: Fix Released Status in “libcroco” source package in Quantal: Fix Released Bug description: [Impact] libcroco [1] had a bug [2] in its versions 0.6.5 and 0.6.6, which results in e.g. librsvg rendering wrong green color. The bug has been fixed since 0.6.7 [3], but the Ubuntu 12.04 Precise LTS version contains the broken version 0.6.5-1 (and Quantal uses a newer, but still broken, 0.6.6-1; Raring seems to use the current (fixed) 0.6.8-1). [4] Because Wikimedia Foundation wikis (including Wikipedia and Wikimedia Commons) suffer from this bug in SVG rendering [5], I was referred to here to report it/ask for the library to be updated, prior to patching it locally. This fix libcroco so that it again complies with the CSS SVG standards. [Test Case] [Regression Potential] This is a one line patch that has been shipped in libcroco 0.6.7 for six months. [Rest of original bug report] As I am not acquainted with Ubuntu/Debian policies/requirements/workflow for such changes, I hope I am not reporting it in a _completely_ wrong place… If so, feel free to forward this, or point me to a better place. Thanks. [1] https://launchpad.net/ubuntu/+source/libcroco [2] https://bugzilla.gnome.org/show_bug.cgi?id=672332#c4 [3] https://git.gnome.org/browse/libcroco/log/ [4] https://launchpad.net/libcroco/+packages [5] https://bugzilla.wikimedia.org/show_bug.cgi?id=46540 To manage notifications about this bug go to: https://bugs.launchpad.net/libcroco/+bug/1163999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163999] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcroco in Ubuntu. https://bugs.launchpad.net/bugs/1163999 Title: Libcroco uses wrong green color Status in Libcroco - C Library to suppost CSS parsing and manipulation: Fix Released Status in “libcroco” package in Ubuntu: Fix Released Status in “libcroco” source package in Precise: Fix Released Status in “libcroco” source package in Quantal: Fix Released Bug description: [Impact] libcroco [1] had a bug [2] in its versions 0.6.5 and 0.6.6, which results in e.g. librsvg rendering wrong green color. The bug has been fixed since 0.6.7 [3], but the Ubuntu 12.04 Precise LTS version contains the broken version 0.6.5-1 (and Quantal uses a newer, but still broken, 0.6.6-1; Raring seems to use the current (fixed) 0.6.8-1). [4] Because Wikimedia Foundation wikis (including Wikipedia and Wikimedia Commons) suffer from this bug in SVG rendering [5], I was referred to here to report it/ask for the library to be updated, prior to patching it locally. This fix libcroco so that it again complies with the CSS SVG standards. [Test Case] [Regression Potential] This is a one line patch that has been shipped in libcroco 0.6.7 for six months. [Rest of original bug report] As I am not acquainted with Ubuntu/Debian policies/requirements/workflow for such changes, I hope I am not reporting it in a _completely_ wrong place… If so, feel free to forward this, or point me to a better place. Thanks. [1] https://launchpad.net/ubuntu/+source/libcroco [2] https://bugzilla.gnome.org/show_bug.cgi?id=672332#c4 [3] https://git.gnome.org/browse/libcroco/log/ [4] https://launchpad.net/libcroco/+packages [5] https://bugzilla.wikimedia.org/show_bug.cgi?id=46540 To manage notifications about this bug go to: https://bugs.launchpad.net/libcroco/+bug/1163999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1059449] Re: Set Airplane Mode On, Bluetooth still work properly .
** Also affects: gnome-control-center (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: oem-priority Status: New = Confirmed ** Changed in: oem-priority Assignee: (unassigned) = Ara Pulido (apulido) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1059449 Title: Set Airplane Mode On, Bluetooth still work properly . Status in GNOME Control Center: Fix Released Status in OEM Priority Project: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: New Bug description: Ubuntu version : 12.04 Enable Airplane Mode from System Setting -- Network . Bluetooth can not be disabled and only disable WLAN. Addition information : The issue is similar as below . https://bugzilla.gnome.org/show_bug.cgi?id=675778 https://bugzilla.redhat.com/show_bug.cgi?id=821422 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1059449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1198375] Re: rhythmbox crashed with SIGSEGV in sem_post()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rhythmbox (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1198375 Title: rhythmbox crashed with SIGSEGV in sem_post() Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: radio absolute 90 s nao funciona ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Fri Jul 5 21:06:14 2013 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2013-06-17 (18 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130529) MarkForUpload: True ProcCmdline: rhythmbox ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 SegvAnalysis: Segfault happened at: 0x7f100a8f21e0 sem_post: mov(%rdi),%eax PC (0x7f100a8f21e0) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %eax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0 PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in sem_post() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1198375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 908466] Re: IPv6 avahi servers are not discovered
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/908466 Title: IPv6 avahi servers are not discovered Status in “nautilus” package in Ubuntu: Confirmed Bug description: When I click 'Browse Network' in nautilus, I get a list of computers advertising SFTP on my network. My laptop doesn't show up in the list. Here is the avahi output for my laptop (the MAC address has been removed): chris@chris-iMac:~$ avahi-browse -ta | grep M3 + wlan0 IPv6 chris@chris-Inspiron-M301ZiChat Presence local + eth0 IPv6 chris@chris-Inspiron-M301ZiChat Presence local + wlan0 IPv6 chris-Inspiron-M301Z SFTP File Transfer local + eth0 IPv6 chris-Inspiron-M301Z SFTP File Transfer local + wlan0 IPv6 chris-Inspiron-M301Z SSH Remote Terminal local + eth0 IPv6 chris-Inspiron-M301Z SSH Remote Terminal local + wlan0 IPv6 chris-Inspiron-M301Z Apple File Sharing local + eth0 IPv6 chris-Inspiron-M301Z Apple File Sharing local + wlan0 IPv6 chris-Inspiron-M301Z [**:**:**:**:**:**] Workstation local + eth0 IPv6 chris-Inspiron-M301Z [**:**:**:**:**:**] Workstation local + wlan0 IPv6 chris-Inspiron-M301Z Remote Disk Management local + eth0 IPv6 chris-Inspiron-M301Z Remote Disk Management local Here is a computer that does show up: chris@chris-iMac:~$ avahi-browse -ta | grep michael + wlan0 IPv6 michael-test SFTP File Transfer local + eth0 IPv6 michael-test SFTP File Transfer local + eth0 IPv4 michael-test SFTP File Transfer local + wlan0 IPv6 michael-test SSH Remote Terminal local + eth0 IPv6 michael-test SSH Remote Terminal local + eth0 IPv4 michael-test SSH Remote Terminal local + wlan0 IPv6 michael-test [**:**:**:**:**:**] Workstation local + eth0 IPv6 michael-test [**:**:**:**:**:**] Workstation local + eth0 IPv4 michael-test [**:**:**:**:**:**] Workstation local + wlan0 IPv6 michael-test Remote Disk Management local + eth0 IPv6 michael-test Remote Disk Management local + eth0 IPv4 michael-test Remote Disk Management local There are 2 differences (that I think are significant) between my laptop and the computers showing up. My laptop is only connected over wifi. My laptop is only showing up as IPv6 (presumably because of the wifi network). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.2.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6 Uname: Linux 3.2.0-6-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Sat Dec 24 21:28:25 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to precise on 2011-12-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/908466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1059449] Re: Set Airplane Mode On, Bluetooth still work properly .
** Description changed: Ubuntu version : 12.04 Enable Airplane Mode from System Setting -- Network . Bluetooth can not be disabled and only disable WLAN. - Addition information : The issue is similar as below . https://bugzilla.gnome.org/show_bug.cgi?id=675778 https://bugzilla.redhat.com/show_bug.cgi?id=821422 + + [Impact] + + * Airplane mode goal is to switch off every radio signal that can conflict with the airplane functioning. + * In gnome-control-center 3.4, only the Wifi is switched off, making the feature almost useless + * 12.04 LTS is an LTS, and it is currently used for pre-installed Ubuntu projects, so this is currently affecting everyone buying a pre-installed Ubuntu system or running the latest LTS + + [Test Case] + + Steps to reproduce: + + * Switch on both wireless and bluetooth + * Enable Airplane Mode under System Settings - Network + + Expected behaviour: + + * Both the wi-fi and bluetooth are switched off + + Actual behaviour: + + * Only Wi-fi is switch off. The user can still use bluetooth devices + + [Regression Potential] ** Description changed: Ubuntu version : 12.04 Enable Airplane Mode from System Setting -- Network . Bluetooth can not be disabled and only disable WLAN. Addition information : The issue is similar as below . https://bugzilla.gnome.org/show_bug.cgi?id=675778 https://bugzilla.redhat.com/show_bug.cgi?id=821422 + == Request to backport to 12.04 LTS == + [Impact] - * Airplane mode goal is to switch off every radio signal that can conflict with the airplane functioning. - * In gnome-control-center 3.4, only the Wifi is switched off, making the feature almost useless - * 12.04 LTS is an LTS, and it is currently used for pre-installed Ubuntu projects, so this is currently affecting everyone buying a pre-installed Ubuntu system or running the latest LTS + * Airplane mode goal is to switch off every radio signal that can conflict with the airplane functioning. + * In gnome-control-center 3.4, only the Wifi is switched off, making the feature almost useless + * 12.04 LTS is an LTS, and it is currently used for pre-installed Ubuntu projects, so this is currently affecting everyone buying a pre-installed Ubuntu system or running the latest LTS [Test Case] Steps to reproduce: - * Switch on both wireless and bluetooth - * Enable Airplane Mode under System Settings - Network + * Switch on both wireless and bluetooth + * Enable Airplane Mode under System Settings - Network Expected behaviour: - * Both the wi-fi and bluetooth are switched off + * Both the wi-fi and bluetooth are switched off Actual behaviour: - - * Only Wi-fi is switch off. The user can still use bluetooth devices + + * Only Wi-fi is switch off. The user can still use bluetooth devices [Regression Potential] + + To be defined by a desktop developer. The actual patch in GNOME 3.6 that + fixes this bug is: + + https://git.gnome.org/browse/gnome-control- + center/commit/?h=gnome-3-6id=7aef2fb307a9ff9c32fbe9dc6bc36e1eef5e72ab ** Changed in: oem-priority Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1059449 Title: Set Airplane Mode On, Bluetooth still work properly . Status in GNOME Control Center: Fix Released Status in OEM Priority Project: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: New Bug description: Ubuntu version : 12.04 Enable Airplane Mode from System Setting -- Network . Bluetooth can not be disabled and only disable WLAN. Addition information : The issue is similar as below . https://bugzilla.gnome.org/show_bug.cgi?id=675778 https://bugzilla.redhat.com/show_bug.cgi?id=821422 == Request to backport to 12.04 LTS == [Impact] * Airplane mode goal is to switch off every radio signal that can conflict with the airplane functioning. * In gnome-control-center 3.4, only the Wifi is switched off, making the feature almost useless * 12.04 LTS is an LTS, and it is currently used for pre-installed Ubuntu projects, so this is currently affecting everyone buying a pre-installed Ubuntu system or running the latest LTS [Test Case] Steps to reproduce: * Switch on both wireless and bluetooth * Enable Airplane Mode under System Settings - Network Expected behaviour: * Both the wi-fi and bluetooth are switched off Actual behaviour: * Only Wi-fi is switch off. The user can still use bluetooth devices [Regression Potential] To be defined by a desktop developer. The actual patch in GNOME 3.6 that fixes this bug is: https://git.gnome.org/browse/gnome-control- center/commit/?h=gnome-3-6id=7aef2fb307a9ff9c32fbe9dc6bc36e1eef5e72ab To manage notifications about this
[Desktop-packages] [Bug 1200827] Re: Enable GOA backend
Ok, here's another try; this time the goa support is in a separate package and is the only thing depending on libgoa-1.0-0. ** Patch added: enable-goa-backend-split.debdiff https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1200827/+attachment/3737624/+files/enable-goa-backend-split.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1200827 Title: Enable GOA backend Status in GVFS: Fix Released Status in “gvfs” package in Ubuntu: Triaged Bug description: The GNOME Online Accounts backend is needed for full ownCloud support with GNOME Online Accounts. This feature was not previously enabled in Ubuntu because we didn't have GOA 3.8 until last month. I verified that only gvfs-backends get the new libgoa-1.0-0 dependency. But seeded-in-ubuntu reports that gvfs-backends is not installed by default in ubuntu-touch. (See bug 1193018 for concerns about ubuntu-touch having a dependency on libgoa.) I'm attaching a patch that pulls the goa-enablement changes from Debian since I'll need sponsorship for this update. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Fri Jul 12 23:51:41 2013 InstallationDate: Installed on 2013-06-14 (28 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1200827/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201489] [NEW] gnome-terminal hangs after executing tail -f for some time with plenty of output
Public bug reported: Steps to reproduce: 1) Open gnome-terminal with bash shell. 2) type tail -f someLogFile 3) Let it run with plenty of output for a long time. Result: Tail output will suddenly stop. Stracing the bash process shows: mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, Stracing the tail process shows: sudo strace -p 17298 [sudo] password for mm: Process 17298 attached - interrupt to quit write(1, ull;null;null;null;0;null;eurex;..., 4515^C unfinished ... Process 17298 detached It seems that the processes are somehow deadlocked. After killing the tail process, the tail died, but the gnome-terminal stayed unusable. mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, [{WIFSIGNALED(s) WTERMSIG(s) == SIGTERM}], WSTOPPED|WCONTINUED, NULL) = 17298 rt_sigprocmask(SIG_BLOCK, [CHLD TSTP TTIN TTOU], [CHLD], 8) = 0 ioctl(255, TIOCSPGRP, [31412]) = 0 rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, TIOCGWINSZ, {ws_row=63, ws_col=211, ws_xpixel=0, ws_ypixel=0}) = 0 write(2, Terminated\n, 11 Choosing Terminal-Reset from gnome-terminal menu did not help. Choosing Terminal-Reset And Clear from gnome-terminal menu made the window usable again.. Probably there is a problem with a buffer overflow, etc. I am using a scrollback of 100 lines. The output should have been sufficient to fill this buffer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46 Uname: Linux 3.2.0-48-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Mon Jul 15 18:05:39 2013 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1201489 Title: gnome-terminal hangs after executing tail -f for some time with plenty of output Status in “gnome-terminal” package in Ubuntu: New Bug description: Steps to reproduce: 1) Open gnome-terminal with bash shell. 2) type tail -f someLogFile 3) Let it run with plenty of output for a long time. Result: Tail output will suddenly stop. Stracing the bash process shows: mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, Stracing the tail process shows: sudo strace -p 17298 [sudo] password for mm: Process 17298 attached - interrupt to quit write(1, ull;null;null;null;0;null;eurex;..., 4515^C unfinished ... Process 17298 detached It seems that the processes are somehow deadlocked. After killing the tail process, the tail died, but the gnome-terminal stayed unusable. mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, [{WIFSIGNALED(s) WTERMSIG(s) == SIGTERM}], WSTOPPED|WCONTINUED, NULL) = 17298 rt_sigprocmask(SIG_BLOCK, [CHLD TSTP TTIN TTOU], [CHLD], 8) = 0 ioctl(255, TIOCSPGRP, [31412]) = 0 rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, TIOCGWINSZ, {ws_row=63, ws_col=211, ws_xpixel=0, ws_ypixel=0}) = 0 write(2, Terminated\n, 11 Choosing Terminal-Reset from gnome-terminal menu did not help. Choosing Terminal-Reset And Clear from gnome-terminal menu made the window usable again.. Probably there is a problem with a buffer overflow, etc. I am using a scrollback of 100 lines. The output should have been sufficient to fill this buffer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46 Uname: Linux 3.2.0-48-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Mon Jul 15 18:05:39 2013 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1201493] [NEW] apple wireless trackpad stops respond after touching it with more then two fingers
Public bug reported: I can use it like a normal trackpad and use two finger scrolling, but if I try and use any of the gestures that require more then two fimgers, it stops responding entirely. In order to get it to respond again I have to either restart X or by clicking one of the hardware buttons on the trackpad. As a result of this, you cannot perform a middle button click as that takes 3 fingers or use any of the old multi-touch gesture features that were available in previous versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jul 15 12:10:14 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Juniper XT [Radeon HD 6770] [1002:68ba] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03fe] InstallationDate: Installed on 2013-07-08 (7 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-26-generic root=UUID=dd1185e9-a17e-428d-bd3c-dd49bc96bf28 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3027 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Crosshair IV Formula dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3027:bd10/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCrosshairIVFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Mon Jul 15 09:12:24 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1201493 Title: apple wireless trackpad stops respond after touching it with more then two fingers Status in “xorg” package in Ubuntu: New Bug description: I can use it like a normal trackpad and use two finger scrolling, but if I try and use any of the gestures that require more then two fimgers, it stops responding entirely. In order to get it to respond again I have to either restart X or by clicking one of the hardware buttons on the trackpad. As a result of this, you cannot perform a middle button click as that takes 3 fingers or use any of the old multi-touch gesture features that were available in previous versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jul 15 12:10:14 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee
[Desktop-packages] [Bug 1201489] Re: gnome-terminal hangs after executing tail -f for some time with plenty of output
** Also affects: gnome-terminal Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1201489 Title: gnome-terminal hangs after executing tail -f for some time with plenty of output Status in GNOME Terminal: New Status in “gnome-terminal” package in Ubuntu: New Bug description: Steps to reproduce: 1) Open gnome-terminal with bash shell. 2) type tail -f someLogFile 3) Let it run with plenty of output for a long time. Result: Tail output will suddenly stop. Stracing the bash process shows: mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, Stracing the tail process shows: sudo strace -p 17298 [sudo] password for mm: Process 17298 attached - interrupt to quit write(1, ull;null;null;null;0;null;eurex;..., 4515^C unfinished ... Process 17298 detached It seems that the processes are somehow deadlocked. After killing the tail process, the tail died, but the gnome-terminal stayed unusable. mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, [{WIFSIGNALED(s) WTERMSIG(s) == SIGTERM}], WSTOPPED|WCONTINUED, NULL) = 17298 rt_sigprocmask(SIG_BLOCK, [CHLD TSTP TTIN TTOU], [CHLD], 8) = 0 ioctl(255, TIOCSPGRP, [31412]) = 0 rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, TIOCGWINSZ, {ws_row=63, ws_col=211, ws_xpixel=0, ws_ypixel=0}) = 0 write(2, Terminated\n, 11 Choosing Terminal-Reset from gnome-terminal menu did not help. Choosing Terminal-Reset And Clear from gnome-terminal menu made the window usable again.. Probably there is a problem with a buffer overflow, etc. I am using a scrollback of 100 lines. The output should have been sufficient to fill this buffer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46 Uname: Linux 3.2.0-48-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Mon Jul 15 18:05:39 2013 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1201489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201489] Re: gnome-terminal hangs after executing tail -f for some time with plenty of output
Reported bug upstream: https://bugzilla.gnome.org/show_bug.cgi?id=704270. ** Bug watch added: GNOME Bug Tracker #704270 https://bugzilla.gnome.org/show_bug.cgi?id=704270 ** Changed in: gnome-terminal Importance: Undecided = Unknown ** Changed in: gnome-terminal Status: New = Unknown ** Changed in: gnome-terminal Remote watch: None = GNOME Bug Tracker #704270 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1201489 Title: gnome-terminal hangs after executing tail -f for some time with plenty of output Status in GNOME Terminal: Unknown Status in “gnome-terminal” package in Ubuntu: New Bug description: Steps to reproduce: 1) Open gnome-terminal with bash shell. 2) type tail -f someLogFile 3) Let it run with plenty of output for a long time. Result: Tail output will suddenly stop. Stracing the bash process shows: mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, Stracing the tail process shows: sudo strace -p 17298 [sudo] password for mm: Process 17298 attached - interrupt to quit write(1, ull;null;null;null;0;null;eurex;..., 4515^C unfinished ... Process 17298 detached It seems that the processes are somehow deadlocked. After killing the tail process, the tail died, but the gnome-terminal stayed unusable. mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, [{WIFSIGNALED(s) WTERMSIG(s) == SIGTERM}], WSTOPPED|WCONTINUED, NULL) = 17298 rt_sigprocmask(SIG_BLOCK, [CHLD TSTP TTIN TTOU], [CHLD], 8) = 0 ioctl(255, TIOCSPGRP, [31412]) = 0 rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, TIOCGWINSZ, {ws_row=63, ws_col=211, ws_xpixel=0, ws_ypixel=0}) = 0 write(2, Terminated\n, 11 Choosing Terminal-Reset from gnome-terminal menu did not help. Choosing Terminal-Reset And Clear from gnome-terminal menu made the window usable again.. Probably there is a problem with a buffer overflow, etc. I am using a scrollback of 100 lines. The output should have been sufficient to fill this buffer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46 Uname: Linux 3.2.0-48-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Mon Jul 15 18:05:39 2013 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1201489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1201387] Re: Banshee crashes with locked database message
On Mon, Jul 15, 2013 at 12:15:05PM -, John Reid wrote: john@W530$ lsof ~/.config/banshee-1/banshee.db COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME unity-mus 2969 john9u REG 252,1 45050880 401760 /home/john/.config/banshee-1/banshee.db banshee 25995 john9u REG 252,1 45050880 401760 /home/john/.config/banshee-1/banshee.db Bleah, yeah I thought so. Just kill both of the above processes and restart Banshee, then see if it happens again. -- Kind regards, Loong Jin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1201387 Title: Banshee crashes with locked database message Status in “banshee” package in Ubuntu: Incomplete Bug description: I was running banshee in debug mode when it crashed with a message about a locked databse. a john@W530$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring john@W530$ dpkg -l | grep banshee ii banshee 2.6.1-1ubuntu1 amd64Media Management and Playback application ii banshee-extension-soundmenu 2.6.1-1ubuntu1 amd64Media Management and Playback application - sound menu extension The output is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1201387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196828] Re: Cannot restart banshee after crash
Here is the current ps output: john@W530$ ps -ef|grep banshee john 2170 1711 0 17:58 pts/21 00:00:00 grep --color=auto banshee john 25995 15673 4 13:00 pts/700:14:35 [banshee] defunct -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash Status in “banshee” package in Ubuntu: Incomplete Bug description: If banshee crashes the sound/audio system menu still shows it as available but nothing happens if I click on it. With ps I can see a defunct banshee process that cannot be removed. If I try to run banshee from the command line nothing happens. Restarting gdm and/or unity also has no effect. As far as I can tell there is now no way to start banshee short of rebooting which is annoying. Does anyone know how I can start banshee without closing everything down and rebooting? Perhaps there is some part of Ubuntu that controls the sound menu and I can restart that? I was hoping it was part of gdm or unity but restarting them didn't help. Description: Ubuntu 13.04 Release: 13.04 but I have seen the same behaviour in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196828] Re: Cannot restart banshee after crash
Banshee crashed again but the process didn't disappear. Here's the log for the banshee I'm trying to start. john@W530$ banshee --debug ** Running Mono with --debug ** [1 Debug 17:54:39.785] Bus.Session.RequestName ('org.bansheeproject.Banshee') replied with InQueue I've attached the log for the banshee that crashed. ** Attachment added: Log for banshee that crashed causing the problem https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+attachment/3737686/+files/banshee.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash Status in “banshee” package in Ubuntu: Incomplete Bug description: If banshee crashes the sound/audio system menu still shows it as available but nothing happens if I click on it. With ps I can see a defunct banshee process that cannot be removed. If I try to run banshee from the command line nothing happens. Restarting gdm and/or unity also has no effect. As far as I can tell there is now no way to start banshee short of rebooting which is annoying. Does anyone know how I can start banshee without closing everything down and rebooting? Perhaps there is some part of Ubuntu that controls the sound menu and I can restart that? I was hoping it was part of gdm or unity but restarting them didn't help. Description: Ubuntu 13.04 Release: 13.04 but I have seen the same behaviour in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1131664] Re: Patch the menus of the 'Calculator' and 'System Settings' apps to fit with Unity
@andyrock: thanks for the work, some comments: - could you try opening an upstream bug for the list help item for the current selected panel, who knows they might like the idea there - the patch doesn't build: shell/control-center.c:239: undefined reference to `cc_panel_get_display_name' this function doesn't seem to be defined in the upstream source? - Close should be Quit (I said I would change it locally but if you update the patch you can as well do that with the update) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1131664 Title: Patch the menus of the 'Calculator' and 'System Settings' apps to fit with Unity Status in Ayatana Design: Fix Committed Status in “gnome-calculator” package in Ubuntu: Fix Released Status in “gnome-control-center” package in Ubuntu: In Progress Bug description: When fixing this bug, also take a look at bug #1130722 at the same time if possible. -- In Raring, the 'Calculator' app should have the following menu items: === Edit === Copy Paste - Undo Redo - Preferences - Quit === Mode === Basic Advanced Financial Programming === Help === Contents About In Raring, the 'System Settings' app should have the following menu items: === Help === Contents [Optional link to help doc for the currently selected settings panel] - Quit To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201470] [NEW] Intel wireless microcode driver failure in Saucy causes disconnects
You have been subscribed to a public bug: The connection slowly degrades until dropping. Disabling 11n seems to workaround the issue. With the last disconnect, the following messages were in dmesg: [ 2458.121218] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. [ 2458.121229] iwlwifi :03:00.0: CSR values: [ 2458.121234] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [ 2458.121265] iwlwifi :03:00.0:CSR_HW_IF_CONFIG_REG: 0X00488700 [ 2458.121296] iwlwifi :03:00.0: CSR_INT_COALESCING: 0Xff40 [ 2458.121328] iwlwifi :03:00.0: CSR_INT: 0X [ 2458.121361] iwlwifi :03:00.0:CSR_INT_MASK: 0X [ 2458.121393] iwlwifi :03:00.0: CSR_FH_INT_STATUS: 0X [ 2458.121426] iwlwifi :03:00.0: CSR_GPIO_IN: 0X0030 [ 2458.121455] iwlwifi :03:00.0: CSR_RESET: 0X [ 2458.121486] iwlwifi :03:00.0:CSR_GP_CNTRL: 0X080403c5 [ 2458.121516] iwlwifi :03:00.0: CSR_HW_REV: 0X00b0 [ 2458.121547] iwlwifi :03:00.0: CSR_EEPROM_REG: 0X62390ffd [ 2458.121576] iwlwifi :03:00.0: CSR_EEPROM_GP: 0X9001 [ 2458.121609] iwlwifi :03:00.0: CSR_OTP_GP_REG: 0X00030001 [ 2458.121641] iwlwifi :03:00.0: CSR_GIO_REG: 0X00080042 [ 2458.121674] iwlwifi :03:00.0:CSR_GP_UCODE_REG: 0X71af [ 2458.121706] iwlwifi :03:00.0: CSR_GP_DRIVER_REG: 0X [ 2458.121735] iwlwifi :03:00.0: CSR_UCODE_DRV_GP1: 0X [ 2458.121767] iwlwifi :03:00.0: CSR_UCODE_DRV_GP2: 0X [ 2458.121796] iwlwifi :03:00.0: CSR_LED_REG: 0X0040 [ 2458.121828] iwlwifi :03:00.0:CSR_DRAM_INT_TBL_REG: 0X88210a3e [ 2458.121860] iwlwifi :03:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200 [ 2458.121893] iwlwifi :03:00.0: CSR_ANA_PLL_CFG: 0X [ 2458.121925] iwlwifi :03:00.0: CSR_HW_REV_WA_REG: 0X0001001a [ 2458.121955] iwlwifi :03:00.0:CSR_DBG_HPET_MEM_REG: 0X [ 2458.121959] iwlwifi :03:00.0: FH register values: [ 2458.122019] iwlwifi :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X210f5200 [ 2458.122077] iwlwifi :03:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X02115ed0 [ 2458.122138] iwlwifi :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X [ 2458.122196] iwlwifi :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [ 2458.122257] iwlwifi :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [ 2458.122315] iwlwifi :03:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [ 2458.122376] iwlwifi :03:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [ 2458.122435] iwlwifi :03:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff0001 [ 2458.122495] iwlwifi :03:00.0: FH_TSSR_TX_ERROR_REG: 0X [ 2458.122504] iwlwifi :03:00.0: Loaded firmware version: 18.168.6.1 [ 2458.122902] iwlwifi :03:00.0: Start IWL Error Log Dump: [ 2458.122907] iwlwifi :03:00.0: Status: 0x004C, count: 6 [ 2458.122912] iwlwifi :03:00.0: 0x19A8 | ADVANCED_SYSASSERT [ 2458.122917] iwlwifi :03:00.0: 0x000166CC | uPc [ 2458.122921] iwlwifi :03:00.0: 0x962A | branchlink1 [ 2458.122925] iwlwifi :03:00.0: 0x962A | branchlink2 [ 2458.122929] iwlwifi :03:00.0: 0xD6BE | interruptlink1 [ 2458.122933] iwlwifi :03:00.0: 0x | interruptlink2 [ 2458.122937] iwlwifi :03:00.0: 0x0001 | data1 [ 2458.122941] iwlwifi :03:00.0: 0x20ED7F5E | data2 [ 2458.122946] iwlwifi :03:00.0: 0x0138 | line [ 2458.122950] iwlwifi :03:00.0: 0x00018EAD | beacon time [ 2458.122954] iwlwifi :03:00.0: 0x0153 | tsf low [ 2458.122958] iwlwifi :03:00.0: 0x | tsf hi [ 2458.122962] iwlwifi :03:00.0: 0x | time gp1 [ 2458.122966] iwlwifi :03:00.0: 0x8F09138F | time gp2 [ 2458.122970] iwlwifi :03:00.0: 0x | time gp3 [ 2458.122974] iwlwifi :03:00.0: 0x754312A8 | uCode version [ 2458.122979] iwlwifi :03:00.0: 0x00B0 | hw version [ 2458.122983] iwlwifi :03:00.0: 0x00488700 | board version [ 2458.122987] iwlwifi :03:00.0: 0x094E | hcmd [ 2458.122991] iwlwifi :03:00.0: 0xAF863080 | isr0 [ 2458.122995] iwlwifi :03:00.0: 0x1141E000 | isr1 [ 2458.122999] iwlwifi :03:00.0: 0x0F1A | isr2 [ 2458.123003] iwlwifi :03:00.0: 0x0147FCC3 | isr3 [ 2458.123007] iwlwifi :03:00.0: 0x | isr4 [ 2458.123011] iwlwifi :03:00.0: 0x01000112 | isr_pref [ 2458.123015] iwlwifi :03:00.0: 0x00024B96 | wait_event [ 2458.123019] iwlwifi :03:00.0: 0x0094 | l2p_control [ 2458.123023] iwlwifi :03:00.0: 0x | l2p_duration [ 2458.123027] iwlwifi :03:00.0: 0x000F | l2p_mhvalid [ 2458.123031]
[Desktop-packages] [Bug 1123107] Re: Jockey should install the linux-$flavour metapackage
** Tags added: verification-done-precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1123107 Title: Jockey should install the linux-$flavour metapackage Status in “jockey” package in Ubuntu: Fix Committed Status in “software-properties” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “jockey” source package in Precise: Fix Committed Status in “software-properties” source package in Quantal: Fix Committed Status in “ubuntu-drivers-common” source package in Quantal: Fix Committed Bug description: Neither binary graphics drivers nor dkms depends on the linux-headers any longer. This means that we need Jockey to at least try to install the correct linux-$flavour metapackage so that users get the correct linux headers together with linux updates. In raring we already do this in ubuntu-drivers-common and software- properties-gtk. In precise we could build upon what we have thanks to LP: #567699 and reuse the code from u-d-c. Note: while it's true that Ubiquity already does the right thing, this bug report aims to cover cases in which, for example, the metapackages are not there any more for some reason or because users have installed a different kernel flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1123107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201470] Re: Intel wireless microcode driver failure in Saucy causes disconnects
Joseph, So the problem is also occurring with a Precise installed Dell laptop with a Broadcom card. Feels like the issue is related to multiple access points with the same SID, and possibly Network Manager related. ** Package changed: linux-firmware (Ubuntu Saucy) = network-manager (Ubuntu Saucy) ** Changed in: network-manager (Ubuntu Saucy) Status: Confirmed = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1201470 Title: Intel wireless microcode driver failure in Saucy causes disconnects Status in “network-manager” package in Ubuntu: New Status in “network-manager” source package in Saucy: New Bug description: The connection slowly degrades until dropping. Disabling 11n seems to workaround the issue. With the last disconnect, the following messages were in dmesg: [ 2458.121218] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. [ 2458.121229] iwlwifi :03:00.0: CSR values: [ 2458.121234] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [ 2458.121265] iwlwifi :03:00.0:CSR_HW_IF_CONFIG_REG: 0X00488700 [ 2458.121296] iwlwifi :03:00.0: CSR_INT_COALESCING: 0Xff40 [ 2458.121328] iwlwifi :03:00.0: CSR_INT: 0X [ 2458.121361] iwlwifi :03:00.0:CSR_INT_MASK: 0X [ 2458.121393] iwlwifi :03:00.0: CSR_FH_INT_STATUS: 0X [ 2458.121426] iwlwifi :03:00.0: CSR_GPIO_IN: 0X0030 [ 2458.121455] iwlwifi :03:00.0: CSR_RESET: 0X [ 2458.121486] iwlwifi :03:00.0:CSR_GP_CNTRL: 0X080403c5 [ 2458.121516] iwlwifi :03:00.0: CSR_HW_REV: 0X00b0 [ 2458.121547] iwlwifi :03:00.0: CSR_EEPROM_REG: 0X62390ffd [ 2458.121576] iwlwifi :03:00.0: CSR_EEPROM_GP: 0X9001 [ 2458.121609] iwlwifi :03:00.0: CSR_OTP_GP_REG: 0X00030001 [ 2458.121641] iwlwifi :03:00.0: CSR_GIO_REG: 0X00080042 [ 2458.121674] iwlwifi :03:00.0:CSR_GP_UCODE_REG: 0X71af [ 2458.121706] iwlwifi :03:00.0: CSR_GP_DRIVER_REG: 0X [ 2458.121735] iwlwifi :03:00.0: CSR_UCODE_DRV_GP1: 0X [ 2458.121767] iwlwifi :03:00.0: CSR_UCODE_DRV_GP2: 0X [ 2458.121796] iwlwifi :03:00.0: CSR_LED_REG: 0X0040 [ 2458.121828] iwlwifi :03:00.0:CSR_DRAM_INT_TBL_REG: 0X88210a3e [ 2458.121860] iwlwifi :03:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200 [ 2458.121893] iwlwifi :03:00.0: CSR_ANA_PLL_CFG: 0X [ 2458.121925] iwlwifi :03:00.0: CSR_HW_REV_WA_REG: 0X0001001a [ 2458.121955] iwlwifi :03:00.0:CSR_DBG_HPET_MEM_REG: 0X [ 2458.121959] iwlwifi :03:00.0: FH register values: [ 2458.122019] iwlwifi :03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X210f5200 [ 2458.122077] iwlwifi :03:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X02115ed0 [ 2458.122138] iwlwifi :03:00.0: FH_RSCSR_CHNL0_WPTR: 0X [ 2458.122196] iwlwifi :03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [ 2458.122257] iwlwifi :03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [ 2458.122315] iwlwifi :03:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [ 2458.122376] iwlwifi :03:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [ 2458.122435] iwlwifi :03:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff0001 [ 2458.122495] iwlwifi :03:00.0: FH_TSSR_TX_ERROR_REG: 0X [ 2458.122504] iwlwifi :03:00.0: Loaded firmware version: 18.168.6.1 [ 2458.122902] iwlwifi :03:00.0: Start IWL Error Log Dump: [ 2458.122907] iwlwifi :03:00.0: Status: 0x004C, count: 6 [ 2458.122912] iwlwifi :03:00.0: 0x19A8 | ADVANCED_SYSASSERT [ 2458.122917] iwlwifi :03:00.0: 0x000166CC | uPc [ 2458.122921] iwlwifi :03:00.0: 0x962A | branchlink1 [ 2458.122925] iwlwifi :03:00.0: 0x962A | branchlink2 [ 2458.122929] iwlwifi :03:00.0: 0xD6BE | interruptlink1 [ 2458.122933] iwlwifi :03:00.0: 0x | interruptlink2 [ 2458.122937] iwlwifi :03:00.0: 0x0001 | data1 [ 2458.122941] iwlwifi :03:00.0: 0x20ED7F5E | data2 [ 2458.122946] iwlwifi :03:00.0: 0x0138 | line [ 2458.122950] iwlwifi :03:00.0: 0x00018EAD | beacon time [ 2458.122954] iwlwifi :03:00.0: 0x0153 | tsf low [ 2458.122958] iwlwifi :03:00.0: 0x | tsf hi [ 2458.122962] iwlwifi :03:00.0: 0x | time gp1 [ 2458.122966] iwlwifi :03:00.0: 0x8F09138F | time gp2 [ 2458.122970] iwlwifi :03:00.0: 0x | time gp3 [
[Desktop-packages] [Bug 1200821] Re: gnome-control-center crashed with SIGSEGV in ap_plugin_set_user_cancelled()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1200821 Title: gnome-control-center crashed with SIGSEGV in ap_plugin_set_user_cancelled() Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Something to do with online accounts? ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu30 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Fri Jul 12 21:42:16 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-06-22 (20 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621) MarkForUpload: True ProcCmdline: gnome-control-center credentials ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0x7fb1311d9a1d ap_plugin_set_user_cancelled+29: cmp%rax,(%rdx) PC (0x7fb1311d9a1d) ok source %rax ok destination (%rdx) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ap_plugin_set_user_cancelled () from /usr/lib/libaccount-plugin-1.0.so.0 ?? () from /usr/lib/libaccount-plugin-1.0.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in ap_plugin_set_user_cancelled() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager0.9.7-0ubuntu2 deja-dup27.3.1-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130625-0ubuntu1 gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1 indicator-datetime 12.10.3+13.10.20130708-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1200821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1173551] Re: Evolution crashes on opening
Worked for me, too. I ran $ sudo apt-get purge evolution $ sudo apt-get autoclean I then installed evolution (from the Software Centre) and restarted (to ensure all the Evo' related daemons were restarted). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1173551 Title: Evolution crashes on opening Status in “evolution” package in Ubuntu: Confirmed Bug description: Hi, I upgraded this morning, 27/4/2013, and now the mail application, Evolution, is not working. The problem is that if I open Evolution it displays my mails and then closes immediately. I cannot do anything ie open a mail, make a back up etc. It doesnt give me a chance to. 1 - Ubuntu Release: michael@Home:~$ lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 2 - Evolution version: 3.6.4-0ubuntu1 3 - I expected Evolution to open and allow me to retrieve mails etc 4 - Evolution closed on its own without giving me a chance to perform any functions ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sat Apr 27 12:37:40 2013 InstallationDate: Installed on 2011-11-27 (517 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MarkForUpload: True SourcePackage: evolution UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1173551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201489] Re: gnome-terminal hangs after executing tail -f for some time with plenty of output
** Changed in: gnome-terminal Status: Unknown = New ** Changed in: gnome-terminal Importance: Unknown = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1201489 Title: gnome-terminal hangs after executing tail -f for some time with plenty of output Status in GNOME Terminal: New Status in “gnome-terminal” package in Ubuntu: New Bug description: Steps to reproduce: 1) Open gnome-terminal with bash shell. 2) type tail -f someLogFile 3) Let it run with plenty of output for a long time. Result: Tail output will suddenly stop. Stracing the bash process shows: mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, Stracing the tail process shows: sudo strace -p 17298 [sudo] password for mm: Process 17298 attached - interrupt to quit write(1, ull;null;null;null;0;null;eurex;..., 4515^C unfinished ... Process 17298 detached It seems that the processes are somehow deadlocked. After killing the tail process, the tail died, but the gnome-terminal stayed unusable. mm@musca:~ $ sudo strace -p 31412 [sudo] password for mm: Process 31412 attached - interrupt to quit wait4(-1, [{WIFSIGNALED(s) WTERMSIG(s) == SIGTERM}], WSTOPPED|WCONTINUED, NULL) = 17298 rt_sigprocmask(SIG_BLOCK, [CHLD TSTP TTIN TTOU], [CHLD], 8) = 0 ioctl(255, TIOCSPGRP, [31412]) = 0 rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(255, TIOCGWINSZ, {ws_row=63, ws_col=211, ws_xpixel=0, ws_ypixel=0}) = 0 write(2, Terminated\n, 11 Choosing Terminal-Reset from gnome-terminal menu did not help. Choosing Terminal-Reset And Clear from gnome-terminal menu made the window usable again.. Probably there is a problem with a buffer overflow, etc. I am using a scrollback of 100 lines. The output should have been sufficient to fill this buffer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46 Uname: Linux 3.2.0-48-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Mon Jul 15 18:05:39 2013 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1201489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1201387] Re: Banshee crashes with locked database message
*** This bug is a duplicate of bug 768248 *** https://bugs.launchpad.net/bugs/768248 On Tue, Jul 16, 2013 at 01:00:09AM +0800, Chow Loong Jin wrote: On Mon, Jul 15, 2013 at 12:15:05PM -, John Reid wrote: john@W530$ lsof ~/.config/banshee-1/banshee.db COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME unity-mus 2969 john9u REG 252,1 45050880 401760 /home/john/.config/banshee-1/banshee.db banshee 25995 john9u REG 252,1 45050880 401760 /home/john/.config/banshee-1/banshee.db Bleah, yeah I thought so. Just kill both of the above processes and restart Banshee, then see if it happens again. duplicate 768248 -- Kind regards, Loong Jin ** This bug has been marked a duplicate of bug 768248 Lens should not access Banshee's sqlite database ** This bug has been marked a duplicate of bug 768248 Lens should not access Banshee's sqlite database -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1201387 Title: Banshee crashes with locked database message Status in “banshee” package in Ubuntu: Incomplete Bug description: I was running banshee in debug mode when it crashed with a message about a locked databse. a john@W530$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.04 Release: 13.04 Codename: raring john@W530$ dpkg -l | grep banshee ii banshee 2.6.1-1ubuntu1 amd64Media Management and Playback application ii banshee-extension-soundmenu 2.6.1-1ubuntu1 amd64Media Management and Playback application - sound menu extension The output is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1201387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201528] [NEW] [Realtek ALC889] - Audio Playback Unavailable
Public bug reported: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201528 Title: [Realtek ALC889] - Audio Playback Unavailable Status in “alsa-driver” package in Ubuntu: New Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front
[Desktop-packages] [Bug 1201528] Re: [Realtek ALC889] - Audio Playback Unavailable
** Summary changed: - [, Realtek ALC889, Green Headphone Out, Front] Playback problem + [Realtek ALC889] - Audio Playback Unavailable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201528 Title: [Realtek ALC889] - Audio Playback Unavailable Status in “alsa-driver” package in Ubuntu: New Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196828] Re: Cannot restart banshee after crash
What's process 15673? That's Banshee's current parent process. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash Status in “banshee” package in Ubuntu: Incomplete Bug description: If banshee crashes the sound/audio system menu still shows it as available but nothing happens if I click on it. With ps I can see a defunct banshee process that cannot be removed. If I try to run banshee from the command line nothing happens. Restarting gdm and/or unity also has no effect. As far as I can tell there is now no way to start banshee short of rebooting which is annoying. Does anyone know how I can start banshee without closing everything down and rebooting? Perhaps there is some part of Ubuntu that controls the sound menu and I can restart that? I was hoping it was part of gdm or unity but restarting them didn't help. Description: Ubuntu 13.04 Release: 13.04 but I have seen the same behaviour in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196828] Re: Cannot restart banshee after crash
Good point, I didn't check the output too closely. 15673 is the bash shell I started banshee from: ~/Downloads john@W530$ ps -ef|grep 15673 john 4724 4624 0 18:59 pts/21 00:00:00 grep --color=auto 15673 john 15673 10712 0 Jul09 pts/700:00:00 bash john 25995 15673 4 13:00 pts/700:14:35 [banshee] defunct However banshee is not responding to Ctrl-C in the bash terminal nor to kills so what to do? ~/Downloads john@W530$ kill -9 25995 ~/Downloads john@W530$ kill -15 25995 ~/Downloads john@W530$ kill 25995 ~/Downloads john@W530$ ps -ef|grep 15673 john 4780 4624 0 19:00 pts/21 00:00:00 grep --color=auto 15673 john 15673 10712 0 Jul09 pts/700:00:00 bash john 25995 15673 4 13:00 pts/700:14:35 [banshee] defunct -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash Status in “banshee” package in Ubuntu: Incomplete Bug description: If banshee crashes the sound/audio system menu still shows it as available but nothing happens if I click on it. With ps I can see a defunct banshee process that cannot be removed. If I try to run banshee from the command line nothing happens. Restarting gdm and/or unity also has no effect. As far as I can tell there is now no way to start banshee short of rebooting which is annoying. Does anyone know how I can start banshee without closing everything down and rebooting? Perhaps there is some part of Ubuntu that controls the sound menu and I can restart that? I was hoping it was part of gdm or unity but restarting them didn't help. Description: Ubuntu 13.04 Release: 13.04 but I have seen the same behaviour in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1088333] Re: After uploading to Facebook, via ubuntu tag has dead link
Ubuntu patched Shotwell to make it work with their Online Accounts system, and this link is created by their plugin / Facebook application. I've added that project to this ticket. ** Also affects: online-accounts-shotwell Importance: Undecided Status: New ** Changed in: shotwell Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1088333 Title: After uploading to Facebook, via ubuntu tag has dead link Status in Online Accounts: Shotwell: New Status in Shotwell: Invalid Status in “shotwell” package in Ubuntu: New Bug description: After a photo has been uploaded to facebook from Shotwell, a tag is added indicating it had been uploaded via ubuntu. The word ubuntu is clickable, but the link is 404 (https://www.facebook.com/apps/application.php?id=302061903208115). I'm not sure how you'd go about doing it - obviously through facebook - but replaceing the dead link with info on ubuntu/Shotwell would be ideal - others (friends of ubuntu users) who see that tag on an uploaded image can follow the link and learn more about the project. To manage notifications about this bug go to: https://bugs.launchpad.net/online-accounts-shotwell/+bug/1088333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201535] [NEW] evolution-addressbook-factory crashed with SIGABRT in raise()
Public bug reported: evolution has crashed while alone chatted with empathy ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evolution-data-server 3.8.3-0ubuntu5 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 Date: Mon Jul 15 20:08:40 2013 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory InstallationDate: Installed on 2013-07-08 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130707) MarkForUpload: True ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 Signal: 6 SourcePackage: evolution-data-server StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: evolution-addressbook-factory crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1201535 Title: evolution-addressbook-factory crashed with SIGABRT in raise() Status in “evolution-data-server” package in Ubuntu: New Bug description: evolution has crashed while alone chatted with empathy ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evolution-data-server 3.8.3-0ubuntu5 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 Date: Mon Jul 15 20:08:40 2013 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory InstallationDate: Installed on 2013-07-08 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130707) MarkForUpload: True ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 Signal: 6 SourcePackage: evolution-data-server StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: evolution-addressbook-factory crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1201535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1198659] Re: PCI/internal sound card not detected
Any update? ** Description changed: Hi I have intalled ubuntu 13.04 recently. But sound not working. In sound settings. output is showing : Dummy Output. Tried few things but no result. aplay shows - no sound card. sudo aplay -l aplay: device_list:252: no soundcards found... lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI Radeon Xpress 200 Host Bridge (rev 01) 00:01.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS480 PCI Bridge 00:11.0 IDE interface: Advanced Micro Devices [AMD] nee ATI IXP SB400 Serial ATA Controller (rev 80) 00:12.0 IDE interface: Advanced Micro Devices [AMD] nee ATI IXP SB400 Serial ATA Controller (rev 80) 00:13.0 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB Host Controller (rev 80) 00:13.1 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB Host Controller (rev 80) 00:13.2 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB2 Host Controller (rev 80) 00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI IXP SB400 SMBus Controller (rev 82) 00:14.1 IDE interface: Advanced Micro Devices [AMD] nee ATI IXP SB400 IDE Controller (rev 80) 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI IXP SB4x0 High Definition Audio Controller (rev 01) 00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI IXP SB400 PCI-ISA Bridge (rev 80) 00:14.4 PCI bridge: Advanced Micro Devices [AMD] nee ATI IXP SB400 PCI-PCI Bridge (rev 80) 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RC410 [Radeon Xpress 200/1100] 02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) - I have also tried to reinstall sound. but still not working. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jul 8 00:07:54 2013 InstallationDate: Installed on 2013-07-07 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2006 dmi.bios.vendor: Award BIOS for Intel dmi.bios.version: GC11010N.86A.0313.2006.0915.1840 dmi.board.name: D101GGC dmi.board.vendor: Intel Corporation dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardBIOSforIntel:bvrGC11010N.86A.0313.2006.0915.1840:bd09/15/2006:svn:pn:pvr:rvnIntelCorporation:rnD101GGC:rvr:cvn:ct3:cvr: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1198659 Title: PCI/internal sound card not detected Status in “alsa-driver” package in Ubuntu: New Bug description: Hi I have intalled ubuntu 13.04 recently. But sound not working. In sound settings. output is showing : Dummy Output. Tried few things but no result. aplay shows - no sound card. sudo aplay -l aplay: device_list:252: no soundcards found... lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI Radeon Xpress 200 Host Bridge (rev 01) 00:01.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS480 PCI Bridge 00:11.0 IDE interface: Advanced Micro Devices [AMD] nee ATI IXP SB400 Serial ATA Controller (rev 80) 00:12.0 IDE interface: Advanced Micro Devices [AMD] nee ATI IXP SB400 Serial ATA Controller (rev 80) 00:13.0 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB Host Controller (rev 80) 00:13.1 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB Host Controller (rev 80) 00:13.2 USB controller: Advanced Micro Devices [AMD] nee ATI IXP SB400 USB2 Host Controller (rev 80) 00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI IXP SB400 SMBus Controller (rev 82) 00:14.1 IDE interface: Advanced Micro Devices [AMD] nee ATI IXP SB400 IDE Controller (rev 80) 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI IXP SB4x0 High Definition Audio Controller (rev 01) 00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI IXP SB400 PCI-ISA Bridge (rev 80) 00:14.4 PCI bridge: Advanced Micro Devices [AMD] nee ATI IXP SB400 PCI-PCI Bridge (rev 80) 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RC410 [Radeon Xpress 200/1100] 02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) I have also tried to reinstall sound. but still not working. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux
[Desktop-packages] [Bug 1196177] Re: Gnome-Panel White Square (Gnome-Fallback-Session/Flashback)
** Changed in: gnome-panel Status: Unknown = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1196177 Title: Gnome-Panel White Square (Gnome-Fallback-Session/Flashback) Status in Compiz: Confirmed Status in Desktop panel for GNOME: New Status in Themes for Ubuntu: New Status in “gnome-panel” package in Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Confirmed Bug description: Description: White squares appears in blank sections of gnome panel at Ubuntu Startup and during window Minimize / Maximize Actions. Gnome-Flashback with Compiz (Effects) only. Distribution: Ubuntu Saucy Salamander (development branch) Release: 13.10 Packages: compiz: Installed: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 Candidate: 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 Version table: *** 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-fallback formerly gnome-session-flashback in ubuntu 13.10: Installed: 1:3.6.2-0ubuntu11 Candidate: 1:3.6.2-0ubuntu11 Version table: *** 1:3.6.2-0ubuntu11 0 500 http://archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages 100 /var/lib/dpkg/status How to Reproduce: Normally after distro-upgrade or a clean install, since the 1st Boot you'll see a white square in unussed portion of gnome panels (totally white if the panel is clean) Steps: 1.- Launch some application (firefox in this case) 2.- Left Mouse Click on Firefo's Window List Box (This Will Minimize Firefox to Panel) 3.- At this Step, maybe the White panell has disappeared ( Now the color is normal according to Ambiance Theme ) 4.- Click Again in Firefox's Windows List Box ( The Window must Maximize and the White Square in Gnome Panel appears Again. If its not, repeat the Minimize and Maximize actios to rise up the bug) Temporary WorkArround: Enable Show Hide Buttons under Panel Properties. This will transfer the buggy white color effect to the sidebuttons in the panel. How to Reproduce with Adwaita theme: 1) Open file for edit: /usr/share/themes/Adwaita/gtk-3.0/gtk.css 2) Add these lines end of file: .gnome-panel-menu-bar, PanelApplet GtkMenuBar.menubar, PanelToplevel, PanelWidget, PanelAppletFrame, PanelApplet { background-image: -gtk-gradient(linear, left top, left bottom, from(shade(#3c3b37, 1.5)), to(shade(#3c3b37, 1.05))); } 3. Switch gtk theme to Adwaita. If already using it, restart gnome- panel. 4. gnome-panel has black background instead of gradient. menu bar and indicator applet complete looks like it should. 5. Opening panel properties and switching background from none to solid color and back will bring gradient to whole panel. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1196177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1196828] Re: Cannot restart banshee after crash
On Mon, Jul 15, 2013 at 06:01:36PM -, John Reid wrote: Good point, I didn't check the output too closely. 15673 is the bash shell I started banshee from: ~/Downloads john@W530$ ps -ef|grep 15673 john 4724 4624 0 18:59 pts/21 00:00:00 grep --color=auto 15673 john 15673 10712 0 Jul09 pts/700:00:00 bash john 25995 15673 4 13:00 pts/700:14:35 [banshee] defunct However banshee is not responding to Ctrl-C in the bash terminal nor to kills so what to do? ~/Downloads john@W530$ kill -9 25995 ~/Downloads john@W530$ kill -15 25995 ~/Downloads john@W530$ kill 25995 ~/Downloads john@W530$ ps -ef|grep 15673 john 4780 4624 0 19:00 pts/21 00:00:00 grep --color=auto 15673 john 15673 10712 0 Jul09 pts/700:00:00 bash john 25995 15673 4 13:00 pts/700:14:35 [banshee] defunct Try killing the bash process itself. If that doesn't work, keep following the trail up until you reach 1. There seems to be a parent process of that bash process. -- Kind regards, Loong Jin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash Status in “banshee” package in Ubuntu: Incomplete Bug description: If banshee crashes the sound/audio system menu still shows it as available but nothing happens if I click on it. With ps I can see a defunct banshee process that cannot be removed. If I try to run banshee from the command line nothing happens. Restarting gdm and/or unity also has no effect. As far as I can tell there is now no way to start banshee short of rebooting which is annoying. Does anyone know how I can start banshee without closing everything down and rebooting? Perhaps there is some part of Ubuntu that controls the sound menu and I can restart that? I was hoping it was part of gdm or unity but restarting them didn't help. Description: Ubuntu 13.04 Release: 13.04 but I have seen the same behaviour in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201551] [NEW] totem-video-thumbnailer crashed with SIGSEGV
Public bug reported: i just open a *.avi video and it crash ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: totem 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 Date: Mon Jul 15 13:51:40 2013 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2013-07-03 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130702) MarkForUpload: True ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///mnt/2F2713FA41E051C4/camaras/SIBK130607/Cam01/0615/Event20130615075435001.avi /tmp/.gnome_desktop_thumbnail.6TTO0W ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CO.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb2f5bf6a: cmpl $0x42535844,0x10(%eax) PC (0xb2f5bf6a) ok source $0x42535844 ok destination 0x10(%eax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstavi.so ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstavi.so ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: totem-video-thumbnailer crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1201551 Title: totem-video-thumbnailer crashed with SIGSEGV Status in “totem” package in Ubuntu: New Bug description: i just open a *.avi video and it crash ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: totem 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 Date: Mon Jul 15 13:51:40 2013 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2013-07-03 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130702) MarkForUpload: True ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///mnt/2F2713FA41E051C4/camaras/SIBK130607/Cam01/0615/Event20130615075435001.avi /tmp/.gnome_desktop_thumbnail.6TTO0W ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CO.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb2f5bf6a:cmpl $0x42535844,0x10(%eax) PC (0xb2f5bf6a) ok source $0x42535844 ok destination 0x10(%eax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstavi.so ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstavi.so ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: totem-video-thumbnailer crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1201551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1081819] Re: (12.10) intermittent boot failure / black screen
I have the same problem, I have a E6419 dell laptop, the funny think is that this does not happen all the time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1081819 Title: (12.10) intermittent boot failure / black screen Status in “xorg” package in Ubuntu: Confirmed Bug description: Ubuntu 12.10 (Xubuntu) HP p2-1033w - AMD E-300 APU with Radeon 6310 integrated graphics My pc sometimes will not boot properly and will stay at a black screen with blinking cursor. It usually displays the GRUB bootloader and boots normally. After disconnecting and reconnecting power, I am able to boot Ubuntu but the intermittent booting problem continues. edit - log from boot-repair http://paste.ubuntu.com/1378561/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1081819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174789] Re: Restore failure with librsync error 103
*** This bug is a duplicate of bug 662442 *** https://bugs.launchpad.net/bugs/662442 I believe based on the little information I have, that this is a software issue and not a problem with the backup data itself. I think. So there's hope to restore the data if we can fix this stuff. But I haven't been able to get my hand on a backup set that reproduces the problem. :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1174789 Title: Restore failure with librsync error 103 Status in “deja-dup” package in Ubuntu: Confirmed Bug description: I'm trying to restore my Thunderbird profile from a recent (2 week old) backup. The restore failed with a set of errors. To reproduce: 0) Backup ~/ to a local disk using deja-dup 1) Quit Thunderbird then navigate to the .thunderbird directory in nautilus 2) Right-click the Thunderbird profile directory (e.g. .default) in nautilus and choose, Revert to previous version 3) Choose the backup location (an external disk in my case) 4) Choose the backup to restore from 5) On the Summary screen of the Restore window, choose Restore Expected results: Deja-dup restores the previous version of the folder Actual results: After some time, the Restore window shows the message, Restore Failed with the following additional data: Failed with an unknown error. Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 526, in Write_ROPaths for ropath in rop_iter: File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 499, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 479, in patch_seq2ropath misc.copyfileobj( current_file, tempfp ) File /usr/lib/python2.7/dist-packages/duplicity/misc.py, line 166, in copyfileobj buf = infp.read(blocksize) File /usr/lib/python2.7/dist-packages/duplicity/librsync.py, line 80, in read self._add_to_outbuf_once() File /usr/lib/python2.7/dist-packages/duplicity/librsync.py, line 94, in _add_to_outbuf_once raise librsyncError(str(e)) librsyncError: librsync error 103 while in patch cycle ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 30 10:54:03 2013 InstallationDate: Installed on 2010-09-17 (956 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to raring on 2013-01-25 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1174789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201547] Re: bug
xorg 1:7.6+12ubuntu1 show bug in x Diagnostic settting. please help me what to do? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1201547 Title: bug Status in “xorg” package in Ubuntu: Fix Released Bug description: xorg 1:7.6+12ubuntu1 package show bug when scan from x Diagnostics setting application. so,please debuging it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,resize,place,compiztoolbox,mousepoll,move,vpswitch,animation,gnomecompat,imgpng,grid,session,wobbly,workarounds,fade,cube,expo,ezoom,rotate,scale,unityshell,unitymtgrabhandles] CompositorRunning: compiz Date: Tue Jul 16 00:07:37 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:0036] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=5442D42D42D41618 loop=/ubuntu/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0035.2010.0429.1516 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-301 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0035.2010.0429.1516:bd04/29/2010:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-301:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1201547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201547] [NEW] bug
Public bug reported: xorg 1:7.6+12ubuntu1 package show bug when scan from x Diagnostics setting application. so,please debuging it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,resize,place,compiztoolbox,mousepoll,move,vpswitch,animation,gnomecompat,imgpng,grid,session,wobbly,workarounds,fade,cube,expo,ezoom,rotate,scale,unityshell,unitymtgrabhandles] CompositorRunning: compiz Date: Tue Jul 16 00:07:37 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:0036] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=5442D42D42D41618 loop=/ubuntu/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0035.2010.0429.1516 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-301 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0035.2010.0429.1516:bd04/29/2010:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-301:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Assignee: ashutosh (nexushome7) Status: Fix Released ** Tags: amd64 apport-bug compiz-0.9 patch precise ubuntu ** Changed in: xorg (Ubuntu) Status: New = Fix Released ** Changed in: xorg (Ubuntu) Assignee: (unassigned) = ashutosh (nexushome7) ** Changed in: xorg (Ubuntu) Assignee: ashutosh (nexushome7) = (unassigned) ** Changed in: xorg (Ubuntu) Assignee: (unassigned) = ashutosh (nexushome7) ** Changed in: xorg (Ubuntu) Assignee: ashutosh (nexushome7) = (unassigned) ** Description changed: xorg 1:7.6+12ubuntu1 package show bug when scan from x Diagnostics setting application. so,please debuging it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,resize,place,compiztoolbox,mousepoll,move,vpswitch,animation,gnomecompat,imgpng,grid,session,wobbly,workarounds,fade,cube,expo,ezoom,rotate,scale,unityshell,unitymtgrabhandles] CompositorRunning: compiz Date: Tue Jul 16 00:07:37 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Intel Corporation Device [8086:0036] + Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Intel Corporation Device [8086:0036] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=5442D42D42D41618 loop=/ubuntu/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0035.2010.0429.1516 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-301 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0035.2010.0429.1516:bd04/29/2010:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-301:cvn:ct3:cvr: version.compiz:
[Desktop-packages] [Bug 1201554] [NEW] brasero crashed with SIGABRT in raise()
Public bug reported: Brasero crashed while finishing the process of burning a CD-RW. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: brasero 3.8.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Mon Jul 15 20:38:52 2013 ExecutablePath: /usr/bin/brasero InstallationDate: Installed on 2013-02-27 (138 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) MarkForUpload: True ProcCmdline: brasero Signal: 6 SourcePackage: brasero StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: brasero crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1201554 Title: brasero crashed with SIGABRT in raise() Status in “brasero” package in Ubuntu: New Bug description: Brasero crashed while finishing the process of burning a CD-RW. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: brasero 3.8.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Mon Jul 15 20:38:52 2013 ExecutablePath: /usr/bin/brasero InstallationDate: Installed on 2013-02-27 (138 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) MarkForUpload: True ProcCmdline: brasero Signal: 6 SourcePackage: brasero StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: brasero crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1201554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196828] Re: Cannot restart banshee after crash
OK I can try and kill bash but I'd like to know what to do when the parent is 1. That is the problem and forces me to reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash Status in “banshee” package in Ubuntu: Incomplete Bug description: If banshee crashes the sound/audio system menu still shows it as available but nothing happens if I click on it. With ps I can see a defunct banshee process that cannot be removed. If I try to run banshee from the command line nothing happens. Restarting gdm and/or unity also has no effect. As far as I can tell there is now no way to start banshee short of rebooting which is annoying. Does anyone know how I can start banshee without closing everything down and rebooting? Perhaps there is some part of Ubuntu that controls the sound menu and I can restart that? I was hoping it was part of gdm or unity but restarting them didn't help. Description: Ubuntu 13.04 Release: 13.04 but I have seen the same behaviour in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196828] Re: Cannot restart banshee after crash
Killing bash make the PPID 1 and banshee won't start ~/Downloads john@W530$ kill 15673 ~/Downloads john@W530$ kill -9 15673 ~/Downloads john@W530$ ps -ef|grep banshee john 6435 4624 0 20:04 pts/21 00:00:00 grep --color=auto banshee john 25995 1 3 13:00 ?00:14:35 [banshee] defunct ~/Downloads john@W530$ banshee --debug ** Running Mono with --debug ** [1 Debug 20:05:23.875] Bus.Session.RequestName ('org.bansheeproject.Banshee') replied with InQueue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash Status in “banshee” package in Ubuntu: Incomplete Bug description: If banshee crashes the sound/audio system menu still shows it as available but nothing happens if I click on it. With ps I can see a defunct banshee process that cannot be removed. If I try to run banshee from the command line nothing happens. Restarting gdm and/or unity also has no effect. As far as I can tell there is now no way to start banshee short of rebooting which is annoying. Does anyone know how I can start banshee without closing everything down and rebooting? Perhaps there is some part of Ubuntu that controls the sound menu and I can restart that? I was hoping it was part of gdm or unity but restarting them didn't help. Description: Ubuntu 13.04 Release: 13.04 but I have seen the same behaviour in 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1075923] Re: nautilus hangs copying large directories from a samba share
@ Artyom Pavlichenko (artyompyandex) check out with dpkg -l | grep gvfs that all versions and deps of gvfs-1.16 are removed !!! then do changes and reinstall gvfs-1.12 (same default on Debian Wheezy) i tested 2 Acer fresh installed Laptops P253-E please mail me errors.. Remark: Possible that Mint uses more deps (added Programs/Libs) for gvfs than Default Ubuntu Hope the Maintainer of gvfs solve this BIG Bug!!! Most People lost DATA if they save to Samba Servers!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1075923 Title: nautilus hangs copying large directories from a samba share Status in GVFS: Confirmed Status in “gvfs” package in Ubuntu: Triaged Bug description: Problem === Copying files to and from samba shares (this includes Windows shares) is unreliable in Ubuntu 12.10 and Ubuntu 13.04 when using nautilus' integrated samba client (gvfs-smb): The copy randomly hangs after a few files or a few GB. Workaround == Until gvfs-smb is fixed, use the kernel samba client (cifs) that works reliably, is faster, but needs some terminal commands to get going: # sudo -s # mkdir /mnt/cifs # mount -t cifs -o user=YOUR_SAMBA_USER -o uid=YOUR_LINUX_USER //SAMBA_SERVER/SAMBA_SHARE /mnt/cifs It will ask for you password, you can then access the shared files at /mnt/cifs. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 166371] Re: Illustrator CS SVG won't load: namespace URIs in entities
I added XML_PARSE_NONET to try and test the effects with bug 1025185, but while I could get this file to work, I couldn't test the failure in that bug. Is there any more details so we could test how to parse the xml while walking this line? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/166371 Title: Illustrator CS SVG won't load: namespace URIs in entities Status in Inkscape: A Vector Drawing Tool: Triaged Status in “inkscape” package in Ubuntu: Confirmed Bug description: Opening an SVG exported from Illustrator CS on Windows XP crashes Inkscape on Windows XP with the message: inkscape.exe:2296: Warning **: SVGView: error loading document To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/166371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201560] [NEW] software-center crashed with SIGSEGV in g_slist_foreach()
Public bug reported: Software-center was unexpectedly closed during the installation of the program (MyPaint 1.1.0 from the official repositories). Installing a success. Software-center został niespodziewanie zamknięty, w trakcie instalowania programu (MyPaint 1.1.0 z oficjalnych repozytoriów). Instalacja programu zakonczyła się sukcesem. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Mon Jul 15 20:55:28 2013 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-07-13 (2 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130713) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9a01ce2d5b g_slist_foreach+27: mov 0x8(%rdi),%rbx PC (0x7f9a01ce2d5b) ok source 0x8(%rdi) (0x0069) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: software-center StacktraceTop: g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 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 Title: software-center crashed with SIGSEGV in g_slist_foreach() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace package-from-proposed saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1201560 Title: software-center crashed with SIGSEGV in g_slist_foreach() Status in “software-center” package in Ubuntu: New Bug description: Software-center was unexpectedly closed during the installation of the program (MyPaint 1.1.0 from the official repositories). Installing a success. Software-center został niespodziewanie zamknięty, w trakcie instalowania programu (MyPaint 1.1.0 z oficjalnych repozytoriów). Instalacja programu zakonczyła się sukcesem. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Mon Jul 15 20:55:28 2013 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-07-13 (2 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130713) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9a01ce2d5b g_slist_foreach+27: mov 0x8(%rdi),%rbx PC (0x7f9a01ce2d5b) ok source 0x8(%rdi) (0x0069) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: software-center StacktraceTop: g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 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 Title: software-center crashed with SIGSEGV in g_slist_foreach() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1201560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201372] Re: Losing sound in Windows after rebooting from Linux (Realtek ALC269VB)
** Summary changed: - Loosing sound in Windows after rebooting from Linux (Realtek ALC269VB) + Losing sound in Windows after rebooting from Linux (Realtek ALC269VB) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201372 Title: Losing sound in Windows after rebooting from Linux (Realtek ALC269VB) Status in “alsa-driver” package in Ubuntu: New Bug description: When I reboot from Xubuntu 12.10 to Windows 7 I loose headphone sound in Windows. I checked the volume levels and even reinstalled Realtek audio drivers in Windows, but nothing has helped so far. Only workaround is to shutdown notebook from Xubuntu 12.10 rather than rebooting directly to Windows. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu11 Architecture: amd64 Date: Mon Jul 15 13:18:40 2013 InstallationDate: Installed on 2013-01-17 (178 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53BR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd04/25/2012:svnASUSTeKComputerInc.:pnK53BR:pvr1.0:rvnASUSTeKComputerInc.:rnK53BR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53BR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-07-15T12:54:29.052652 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201193] Re: Ubuntu-12.10 installing packages error
** Package changed: xorg (Ubuntu) = dell-recovery (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1201193 Title: Ubuntu-12.10 installing packages error Status in “dell-recovery” package in Ubuntu: New Bug description: nstallArchives() failed: Selecting previously unselected package gir1.2-gucharmap-2.90. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 223899 files and directories currently installed.) Unpacking gir1.2-gucharmap-2.90 (from .../gir1.2-gucharmap-2.90_1%3a3.5.99-0ubuntu1_amd64.deb) ... Selecting previously unselected package gedit-plugins. Unpacking gedit-plugins (from .../gedit-plugins_3.6.0-0ubuntu1_amd64.deb) ... Processing triggers for libglib2.0-0:i386 ... Processing triggers for libglib2.0-0:amd64 ... Setting up dell-recovery-bootloader (1.27) ... Creating factory grub.cfg Building bootloader installer for mingw32 (quantal) gpgv: Signature made Sun 14 Oct 2012 04:32:12 PM MYT using RSA key ID 7D86500B gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./grub2_2.00-7ubuntu11.dsc dpkg-source: info: extracting grub2 in grub2-2.00 dpkg-source: info: unpacking grub2_2.00.orig.tar.xz dpkg-source: info: unpacking grub2_2.00-7ubuntu11.debian.tar.gz dpkg-source: info: applying upstream-extra-dist.patch dpkg-source: info: applying olpc_prefix_hack.patch dpkg-source: info: applying core_in_fs.patch dpkg-source: info: applying dpkg_version_comparison.patch dpkg-source: info: applying grub_legacy_0_based_partitions.patch dpkg-source: info: applying disable_floppies.patch dpkg-source: info: applying grub.cfg_400.patch dpkg-source: info: applying gfxpayload_keep_default.patch dpkg-source: info: applying mkrescue_diet.patch dpkg-source: info: applying mkconfig_skip_dmcrypt.patch dpkg-source: info: applying install_stage2_confusion.patch dpkg-source: info: applying mkrescue_efi_modules.patch dpkg-source: info: applying mkconfig_loopback.patch dpkg-source: info: applying efi_disk_cache.patch dpkg-source: info: applying restore_mkdevicemap.patch dpkg-source: info: applying efi_mmap_size.patch dpkg-source: info: applying gettext_quiet.patch dpkg-source: info: applying mkconfig_mid_upgrade.patch dpkg-source: info: applying fix_powerpc_emu.patch dpkg-source: info: applying install_efi_fallback.patch dpkg-source: info: applying mkconfig_overescaping.patch dpkg-source: info: applying efifwsetup.patch dpkg-source: info: applying mkconfig_ubuntu_recovery.patch dpkg-source: info: applying msdos_embed_off_by_one.patch dpkg-source: info: applying emu_freebsd.patch dpkg-source: info: applying mkconfig_stderr_handling.patch dpkg-source: info: applying tftp_endianness.patch dpkg-source: info: applying install_locale_langpack.patch dpkg-source: info: applying mkconfig_nonexistent_loopback.patch dpkg-source: info: applying ubuntu_grub_standards.patch dpkg-source: info: applying ubuntu_crashkernel.patch dpkg-source: info: applying ubuntu_quick_boot.patch dpkg-source: info: applying ubuntu_sleep_shift.patch dpkg-source: info: applying ubuntu_normal_quiet.patch dpkg-source: info: applying ubuntu_really_quiet.patch dpkg-source: info: applying ubuntu_linux_quiet.patch dpkg-source: info: applying ubuntu_failed_boot_menu.patch dpkg-source: info: applying ubuntu_quiet_grub_loading.patch dpkg-source: info: applying ubuntu_gfxpayload_filter.patch dpkg-source: info: applying ubuntu_vt_handoff.patch dpkg-source: info: applying ubuntu_blacklist_1440x900x32.patch dpkg-source: info: applying ubuntu_recovery_nomodeset.patch dpkg-source: info: applying ubuntu_recovery_nosingle.patch dpkg-source: info: applying ubuntu_wubi_no_windows.patch dpkg-source: info: applying ubuntu_probe_dmraid.patch dpkg-source: info: applying ubuntu_no_insmod_on_sb.patch dpkg-source: info: applying ubuntu_linuxefi.patch dpkg-source: info: applying ubuntu_linuxefi_amd64_only.patch dpkg-source: info: applying ubuntu_linuxefi_require_shim.patch dpkg-source: info: applying ubuntu_linuxefi_non_sb_fallback.patch dpkg-source: info: applying ubuntu_default_grub_d.patch dpkg-source: info: applying ubuntu_use_signed_kernel.patch dpkg-source: info: applying ubuntu_install_signed.patch dpkg-source: info: