[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
** Changed in: ibus (Ubuntu) Assignee: Maja Gołuszko (mayonezas) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Trusty: Fix Released Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+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 226436]
Let's not mix bug fixes and feature requests. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/226436 Title: Home folder names don't change after changing language if folder not empty Status in xdg-user-dirs package in Ubuntu: Confirmed Status in xdg-user-dirs package in Debian: Unknown Bug description: Changed my language and restared ubuntu. New window came up asking if I want to change the names of folders inside "Home" to names in the other language. Confirmed. When changed the language back to english and restared the folders didn't change back to english names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/226436/+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 49579] Re: screen doesn't lock when some menu is open
** Changed in: gnome-screensaver (Ubuntu Precise) Assignee: Rahul (rahulshantagiri) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Confirmed Status in gnome-screensaver package in Ubuntu: Fix Released Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Triaged Status in unity source package in Precise: Triaged Status in gnome-screensaver source package in Xenial: Fix Released Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+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 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
This bug should be fixed in Ubuntu 15.04, as it currently has systemd 215. The fix is in systemd 209, source: https://bugzilla.gnome.org/show_bug.cgi?id=638117#c50 ** Bug watch added: GNOME Bug Tracker #638117 https://bugzilla.gnome.org/show_bug.cgi?id=638117 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1073669 Title: Bluetooth won't stay disabled after reboot due to early upstart job Status in rfkill package in Ubuntu: Confirmed Bug description: Using a Dell XPS 13 with Ubuntu 12.04. In order to restore RF interfaces to their previous state between boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill- store.conf (run while shutting down) and rfkill-restore.conf (run when starting up). However, while rfkill-restore.conf starts on the Upstart local-filesystems signal, there is a high probability that the RF kill switches in /sys/class/rfkill/ still won't yet be populated (i.e. every time on the Dell XPS 13). This results in behavior like the following: 1. Disable bluetooth via applet. 2. Reboot. 3. Login. 4. Observe bluetooth is re-enabled! Bluetooth should have stayed disabled, but since the kill switches weren't present when rfkill-restore was run, the kill switch states were not restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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 1135419] Re: replaygain plugin fails to load
The plugin seems to load fine in Trusty. Could anyone, especially the
bug's reporter, confirm this? Thanks.
--
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/1135419
Title:
replaygain plugin fails to load
Status in “rhythmbox” package in Ubuntu:
Incomplete
Bug description:
With a fresh raring install, I am unable to activate the replaygain
plugin in rhythmbox. The following is emitted to the console:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Traceback (most recent
call last):
File "/usr/lib/rhythmbox/plugins/replaygain/replaygain.py", line 33, in
from player import ReplayGainPlayer
File "/usr/lib/rhythmbox/plugins/replaygain/player.py", line 31, in
gi.require_version("Gst", "0.11")
File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 65, in
require_version
(namespace, loaded_version))
ValueError: Namespace Gst is already loaded with version 1.0
(rhythmbox:29180): libpeas-WARNING **: Error loading plugin
'replaygain'
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: rhythmbox-plugins 2.98-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Thu Feb 28 15:29:45 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-02-26 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130225)
MarkForUpload: True
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1135419/+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 1292970] Re: compiz crashed with SIGSEGV in ObjectPtr()
I was few weeks without a working internet. After downloading all updates, I've been unable to reproduce this bug. ** Changed in: unity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1292970 Title: compiz crashed with SIGSEGV in ObjectPtr() Status in “unity” package in Ubuntu: Invalid Bug description: I just installed all updates for Trusty from the past two weeks (over 300Mb to download, included updated Kernel and Unity). After restart, I got the usual LightDM log in screen. However, the desktop didn't load after logging in. Instead, I got a black screen with Apport's error message saying that there was an internal error in my system. Both Apport and Firefox that got opened by it are displayed on the screen without a window and its buttons/menus. This issue seems to be persistent after reboots. I managed to get to the desktop by logging to tty1 and then running the startx command. Applications' windows are now visible with menus but Unity still doesn't load. Also, the desktop is shown without the background image but all files/folders are visible and right clicking on the desktop works. This bug could be related to bug 1277382 (I got a new Apport window about an Xorg crash). ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sat Mar 15 22:25:46 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-19 (269 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7fb5ff8baa0f <_ZN3nux11BaseTexture16GetDeviceTextureEv+127>: mov0xb0(%rbx),%rax PC (0x7fb5ff8baa0f) ok source "0xb0(%rbx)" (0x00b0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: nux::BaseTexture::GetDeviceTexture() () from /usr/lib/x86_64-linux-gnu/libnux-graphics-4.0.so.0 unity::panel::PanelView::PanelView(unity::MockableBaseWindow*, std::shared_ptr const&, char const*, int) () from /usr/lib/compiz/libunityshell.so unity::panel::Controller::Impl::CreatePanel() () from /usr/lib/compiz/libunityshell.so unity::panel::Controller::Impl::OnScreenChanged(unsigned int, std::vector > const&) () from /usr/lib/compiz/libunityshell.so unity::panel::Controller::Impl::Impl(unity::panel::Controller*, std::shared_ptr const&, std::shared_ptr const&) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in nux::BaseTexture::GetDeviceTexture() UpgradeStatus: Upgraded to trusty on 2014-02-28 (15 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292970/+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 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
@Khalid: Please do not change bugs' statuses without a comment. Thanks
in advance.
@bug-control: Could you please reset this bug's status to Triaged for
libx11 (Ubuntu)? Thanks in advance.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/507062
Title:
synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
Status in Modular X11 Libraries:
Confirmed
Status in “libx11” package in Ubuntu:
New
Status in “libx11” source package in Lucid:
Triaged
Status in “libx11” source package in Natty:
Invalid
Status in “libx11” source package in Oneiric:
Invalid
Bug description:
Binary package hint: synaptic
1) The release of Ubuntu you are using, via 'lsb_release -rd' or
System -> About Ubuntu.
Description: Ubuntu lucid (development branch)
Release: 10.04
2) The version of the package you are using, via 'apt-cache policy
packagename' or by checking in Synaptic.
synaptic:
Installed: 0.63ubuntu2
Candidate: 0.63ubuntu2
Version table:
*** 0.63ubuntu2 0
500 http://archive.ubuntu.com lucid/main Packages
100 /var/lib/dpkg/status
3) What you expected to happen
filter package list for packages matching some criteria
4) What happened instead
application crashes
#0 0x007d9422 in __kernel_vsyscall ()
No symbol table info available.
#1 0x05cfa5b1 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
resultvar =
pid = 98648052
selftid = 6040
#2 0x05cfda12 in *__GI_abort () at abort.c:92
act = {__sigaction_handler = {sa_handler = 0xbffa00b0,
sa_sigaction = 0xbffa00b0}, sa_mask = {__val = {97783645, 104, 88,
3220832672, 3220832460, 104, 88, 82, 157336880, 98648052, 82, 81,
3220832632, 97714674, 157336888, 82, 3220832672, 157336888, 0,
4222451712, 157336888, 157336888, 157336888, 157336888, 157336969,
157336988, 157336888, 157336988, 0, 0, 0, 0}}, sa_flags = 0,
sa_restorer = 0x20}
sigs = {__val = {32, 0 }}
#3 0x05cf3718 in *__GI___assert_fail (assertion=0x16927e5 "ret != inval_id",
file=0x16927a9 "../../src/xcb_io.c", line=385,
function=0x1692964 "_XAllocID") at assert.c:81
buf = 0x960c538 "synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion
`ret != inval_id' failed.\n"
#4 0x01622cf9 in _XAllocID (dpy=0x9385600) at ../../src/xcb_io.c:385
ret = 4294967295
__PRETTY_FUNCTION__ = "_XAllocID"
#5 0x015f8288 in XCreatePixmap (dpy=0x9385600, d=56788585, width=252,
height=24, depth=32) at ../../src/CrPixmap.c:58
No locals.
#6 0x00455e39 in _cairo_xlib_surface_create_similar_with_format (
abstract_src=0x944c230, format=, width=252,
height=24) at /build/buildd/cairo-1.8.8/src/cairo-xlib-surface.c:155
dpy = (Display *) 0x9385600
pix = 154686976
xrender_format =
#7 0x0045ad6c in _cairo_xlib_surface_clone_similar (
abstract_surface=0x944c230, src=0x955e648, src_x=0, src_y=0, width=252,
height=24, clone_offset_x=0xbffa0568, clone_offset_y=0xbffa056c,
clone_out=0xbffa08bc)
at /build/buildd/cairo-1.8.8/src/cairo-xlib-surface.c:1201
status =
ProblemType: Crash
Architecture: i386
AssertionMessage: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret
!= inval_id' failed.
Date: Wed Jan 13 11:52:41 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/synaptic
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: synaptic 0.63ubuntu2
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
Signal: 6
SourcePackage: synaptic
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libc.so.6
abort () from /lib/tls/i686/cmov/libc.so.6
__assert_fail () from /lib/tls/i686/cmov/libc.so.6
_XAllocID () from /usr/lib/libX11.so.6
Tags: lucid
Title: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
Uname: Linux 2.6.32-10-generic i686
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/xlibs/+bug/507062/+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 1277382] Re: Xorg crashed with SIGABRT in __GI_raise()
This could be related to bug 1292970 (you may get an access error as it's a private bug) in my case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1277382 Title: Xorg crashed with SIGABRT in __GI_raise() Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: desktop failsto come up on boot ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Fri Feb 7 09:51:21 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3568] InstallationDate: Installed on 2013-12-06 (62 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=3c10cf20-751f-40d1-a802-e4712c5118ba ro apparmor=0 quiet splash Signal: 6 SourcePackage: fglrx-installer Stacktrace: #0 0x7ff09b931f39 in __GI_raise (sig=6, sig@entry=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 1501 selftid = 1501 Cannot access memory at address 0x7fff521c4cf8 StacktraceTop: __GI_raise (sig=6, sig@entry=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3568 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn3568:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g7 Notebook PC dmi.product.version: 06901320461620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Feb 7 09:53:53 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu3 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1277382/+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 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'
** Summary changed: - multiple warnings during installation + GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/619003 Title: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib /gdk-pixbuf-2.0/2.10.0/loaders.cache' Status in “gdk-pixbuf” package in Ubuntu: Confirmed Status in “gdk-pixbuf” package in Debian: New Bug description: During installation of updated version of libgdk-pixbuf2.0-0 on August 10th 2010, the apt term.log contained multiple (>300) copies of the following warning: (gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory Nevertheless, the file complained about exists, and is readable in gedit. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic x86_64 Architecture: amd64 CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 Date: Mon Aug 16 18:13:29 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdk-pixbuf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+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 1156927] Re: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
*** This bug is a duplicate of bug 619003 *** https://bugs.launchpad.net/bugs/619003 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 619003, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: trusty ** This bug has been marked a duplicate of bug 619003 multiple warnings during installation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1156927 Title: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory Status in “gdk-pixbuf” package in Ubuntu: Confirmed Bug description: When upgrading from 12.10 to Raring I saw several of these error messages scroll past: Processing triggers for hicolor-icon-theme ... (gtk-update-icon-cache:2606): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:2607): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for bamfdaemon ... ... Processing triggers for hicolor-icon-theme ... (gtk-update-icon-cache:11368): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:11369): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgtk2.0-0 2.24.16-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Mon Mar 18 17:18:49 2013 InstallationDate: Installed on 2012-10-18 (151 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to raring on 2013-03-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1156927/+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 1282050] Re: In spreadsheet, comment shown partialy
Could you please explain why you subscribed me to this bug report? Thanks. -- 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/1282050 Title: In spreadsheet, comment shown partialy Status in Unity: New Status in “libreoffice” package in Ubuntu: New Bug description: 1) Open a spreadsheet. 2) Add comment in cell 3) Go back to the cell, comment shown Resultat: comment show partial, need press alt to see well the comment Expect: show correctly the comment without need to press alt ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice 1:3.5.7-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-17.31~precise1-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Feb 19 12:27:28 2014 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1282050/+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 1254442] Re: [SRU] Please upgrade Saucy's fglrx to new upstream release v.13.12 (has support for Kernel 3.11)
I adapted the wording on this bug to make it clearer that this is a SRU request for Saucy and not a request to upgrade fglrx's version in Trusty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1254442 Title: [SRU] Please upgrade Saucy's fglrx to new upstream release v.13.12 (has support for Kernel 3.11) Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Bug description: Please upgrade Saucy's fglrx-installer (and/or -updates) to the new upstream release v. 13.12. [Impact] This driver supports Kernel up to 3.11 and Xorg up to 1.14; ie. it should fully work on Ubuntu 13.10. The version 13.11 Beta V9.4 also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running The change log for the v. 13.12 is in comment 3 below. It might make sense to also upgrade the stable package, as the v. 13.11 beta 9.4. is the first version that has native support for Saucy's Kernel. Source and more information can be found from http://support.amd.com /en-us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx and http://support.amd.com/en-us/kb- articles/Pages/amdcatalyst13-12linreleasenotes.aspx [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. [Regression Potential] Low. The new driver version doesn't add any new features apart from having a native support for Kernel 3.11. All other changes are bug fixes. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1254442/+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 1254442] Re: [SRU] Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11)
** Tags removed: upgrade-software-version ** Tags added: saucy ** Description changed: - Please upgrade to new upstream release v. 13.12. + Please upgrade Saucy's fglrx-installer (and/or -updates) to the new + upstream release v. 13.12. [Impact] This driver supports Kernel up to 3.11 and Xorg up to 1.14; ie. it should fully work on Ubuntu 13.10. The version 13.11 Beta V9.4 also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running The change log for the v. 13.12 is in comment 3 below. It might make sense to also upgrade the stable package, as the v. 13.11 beta 9.4. is the first version that has native support for Saucy's Kernel. Source and more information can be found from http://support.amd.com/en- us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx and http://support.amd.com/en-us/kb- articles/Pages/amdcatalyst13-12linreleasenotes.aspx - [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. [Regression Potential] Low. The new driver version doesn't add any new features apart from having a native support for Kernel 3.11. All other changes are bug fixes. - Thanks. ** Summary changed: - [SRU] Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) + [SRU] Please upgrade Saucy's fglrx to new upstream release v.13.12 (has support for Kernel 3.11) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1254442 Title: [SRU] Please upgrade Saucy's fglrx to new upstream release v.13.12 (has support for Kernel 3.11) Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Bug description: Please upgrade Saucy's fglrx-installer (and/or -updates) to the new upstream release v. 13.12. [Impact] This driver supports Kernel up to 3.11 and Xorg up to 1.14; ie. it should fully work on Ubuntu 13.10. The version 13.11 Beta V9.4 also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running The change log for the v. 13.12 is in comment 3 below. It might make sense to also upgrade the stable package, as the v. 13.11 beta 9.4. is the first version that has native support for Saucy's Kernel. Source and more information can be found from http://support.amd.com /en-us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx and http://support.amd.com/en-us/kb- articles/Pages/amdcatalyst13-12linreleasenotes.aspx [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. [Regression Potential] Low. The new driver version doesn't add any new features apart from having a native support for Kernel 3.11. All other changes are bug fixes. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1254442/+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 16492] Re: Mouse pointer should disappear when keyboard is in use and mouse isn't
** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/16492 Title: Mouse pointer should disappear when keyboard is in use and mouse isn't Status in GTK+ GUI Toolkit: New Status in One Hundred Papercuts: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Click near the top left of a text field to focus it. 2. Start typing. Or: 1. Click in a browser window to focus the page. 2. Read the page, scrolling with the arrow keys. Or: 1. Click in an e-mail message window to focus the message. 2. Read the message, scrolling with the arrow keys. What happens: * The mouse pointer gets in the way of what you're typing/reading. What should happen: * Whenever you press a non-modifier key on the keyboard, if the pointing device has been neither moved nor clicked in the past ~0.25 seconds, the pointer should disappear until the pointing device is next moved or clicked. But won't this make people lose the pointer? * No. For human eyes, such a small object is much easier to find by movement than by searching the entire screen. As soon as they grab the mouse again, the pointer will appear, and they'll see where it is. This is nuts! * It's worked on the Mac for over two decades. Most people haven't noticed. They just get slightly irritated on *other* platforms when the pointer gets in the way. (Apologies if this is filed under the wrong product.) http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/PointerObscuring.html: http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/PointerObscuring.html To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/16492/+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 1276914] Re: does not work for ATI mobility radeon HD 4500 and 4650
** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1276914 Title: does not work for ATI mobility radeon HD 4500 and 4650 Status in “fglrx-installer-updates” package in Ubuntu: New Bug description: Hardware: Dell Studio 1555 ATI mobility radeon HD 4500 Soft: Ubuntu 12.04 LTS Effects: -unrecognised GPU -max. fan speed -GPU overheat Other users complaining: http://ubuntuforums.org/showthread.php?t=2203866&p=12921237#post12921237 Please consider to do something about it since everyone is getting this via automatic update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1276914/+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 1254442] Re: Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11)
Agreed. I added the SRU details, so this bug report should get more attention. ** Description changed: - Please upgrade to new upstream release v. 13.12. This driver supports - Kernels up to 3.12 and Xorg up to 1.14; ie. it should fully work on - Ubuntu 13.10. + Please upgrade to new upstream release v. 13.12. + + [Impact] + + This driver supports Kernel up to 3.11 and Xorg up to 1.14; ie. it + should fully work on Ubuntu 13.10. The version 13.11 Beta V9.4 also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running - The changelog for the v. 13.12 is in comment 3 below. - It might make sense to also upgrade the stable package, as the v. 13.11 beta 9.4. is the first version that has native support (without DKMS drivers) for Saucy's Kernel. + The change log for the v. 13.12 is in comment 3 below. + + It might make sense to also upgrade the stable package, as the v. 13.11 + beta 9.4. is the first version that has native support for Saucy's + Kernel. Source and more information can be found from http://support.amd.com/en- - us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx + us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx and + http://support.amd.com/en-us/kb- + articles/Pages/amdcatalyst13-12linreleasenotes.aspx + + + [Test Case] + + After installing the update, users should be able to boot the system as + usual, with no regressions of any kind. + + [Regression Potential] + + Low. The new driver version doesn't add any new features apart from + having a native support for Kernel 3.11. All other changes are bug + fixes. + Thanks. ** Summary changed: - Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) + [SRU] Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1254442 Title: [SRU] Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Bug description: Please upgrade to new upstream release v. 13.12. [Impact] This driver supports Kernel up to 3.11 and Xorg up to 1.14; ie. it should fully work on Ubuntu 13.10. The version 13.11 Beta V9.4 also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running The change log for the v. 13.12 is in comment 3 below. It might make sense to also upgrade the stable package, as the v. 13.11 beta 9.4. is the first version that has native support for Saucy's Kernel. Source and more information can be found from http://support.amd.com /en-us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx and http://support.amd.com/en-us/kb- articles/Pages/amdcatalyst13-12linreleasenotes.aspx [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. [Regression Potential] Low. The new driver version doesn't add any new features apart from having a native support for Kernel 3.11. All other changes are bug fixes. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1254442/+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 1262238] Re: [SRU] Add support for the lts-saucy stack
Precise will have newer version of fglrx-installer-updates than Saucy after this change. Could you please update Saucy's package too? Please see bug 1254442 for the SRU request. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1262238 Title: [SRU] Add support for the lts-saucy stack Status in “fglrx-installer” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-13” package in Ubuntu: Invalid Status in “fglrx-installer-updates” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: Fix Committed Status in “fglrx-installer-experimental-13” source package in Precise: Fix Committed Status in “fglrx-installer-updates” source package in Precise: Fix Committed Bug description: SRU request: Please accept fglrx and fglrx-updates into precise-proposed. [Rationale] The packages need to be compatible with the lts-saucy stack in 12.04.4. [Impact] Without this work, the packages won't build against Linux 3.11 and won't be installable when using the backported X stack. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * without the lts-saucy stack * with the lts-saucy stack installed [Regression Potential] Low. The non -updates flavour is the same driver that we shipped in Saucy. As for the -updates flavour, users expect to receive new drivers if they chose that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+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 1267650] Re: fglrx causes segmentation fault on boot
** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1267650 Title: fglrx causes segmentation fault on boot Status in “fglrx-installer-updates” package in Ubuntu: New Bug description: With fglrx-updates installed Ubuntu 14.04 freezes while the bootscreen (shiny ubuntu logo). Can't get into TTY and have to turn the computer off with the powerbutton. I'm on Ubuntu 14.04 freshly updated. Graphics card is a Mobility Radeon 5650. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1267650/+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 379367] Re: Gedit adding a newline at the end of file should be configurable
This bug is fixed in Ubuntu 12.04 Precise Pangolin and newer (earlier releases are no longer supported expect for some server releases). This bug is only marked invalid for Ubuntu because it is unknown in which release this bug was fixed. The fix released status for the non-Ubuntu Gedit means that this bug is also fixed by Gedit's developers (Gnome). There is no GUI option in Gedit itself, but you can use the Dconf Editor which is fully graphical. You may need to install it first (eg. from the Software Centre) if you cannot find it from your system's menus. Once you have opened Dconf Editor, navigate to the /org/gnome/gedit/preferences/editor folder and uncheck the "ensure- trailing-newline" option. The default value for this option is checked; ie. to add a new line to the file's end. I hope this answers your questions. Please do not hesitate to ask for further help or clarification about this bug. Thanks. -- 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/379367 Title: Gedit adding a newline at the end of file should be configurable Status in Light-Weight Text Editor for Gnome: Fix Released Status in “gedit” package in Ubuntu: Invalid Bug description: Binary package hint: gedit Ggedit auto adds a newline at the end of file.I hope it can be configurable. I'm not a c/c++ developer, i'm php developer. but I use gedit for my php developing. Gedit auto adds a new line at the end of file, which will cause a problem when the program runs. I hope this action can be configurable. thanks~! ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/gedit Package: gedit 2.24.2-0ubuntu1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: gedit Uname: Linux 2.6.27-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/379367/+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 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
@W1zz4r: Please do not assign this bug to yourself unless you're working on a fix for this bug. Please use "this bug affects me too" link above this bug's description to mark this bug as affecting you. Thanks in advance. -- 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/905686 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. Status in Modular X11 Libraries: Confirmed Status in “libx11” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Bug description: Here is a backtrace from Ubuntu Precise. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.2.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-5.11-generic-pae 3.2.0-rc5 Uname: Linux 3.2.0-5-generic-pae i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 AssertionMessage: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. Date: Sat Dec 17 14:16:03 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1324036665 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: nautilus -n ProcCwd: / Signal: 6 SourcePackage: nautilus StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 __assert_fail () from /lib/i386-linux-gnu/libc.so.6 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. UpgradeStatus: Upgraded to precise on 2011-12-16 (1 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/905686/+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 1254442] Re: Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11)
The - updates package has been updated for Trusty 1 hour ago, I hope that it'll come to older releases soon. ** Description changed: - Please upgrade to new upstream release 13.11 Beta V9.4. This driver - supports Kernels up to 3.12 and Xorg up to 1.14; ie. it should fully - work on Ubuntu 13.10. + Please upgrade to new upstream release v. 13.12. This driver supports + Kernels up to 3.12 and Xorg up to 1.14; ie. it should fully work on + Ubuntu 13.10. - This version also fixes the following issues: + The version 13.11 Beta V9.4 also fixes the following issues: - [372656] : Resolves crash when resizing Konsole - [388325] : Resolves brightness adjustment issues - [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled - [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support - [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running + [372656] : Resolves crash when resizing Konsole + [388325] : Resolves brightness adjustment issues + [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled + [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support + [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running - It might make sense to also upgrade the stable package, as the beta - v9.4. is the first version that has native support (without DKMS - drivers) for Saucy's Kernel. + The changelog for the v. 13.12 is in comment 3 below. + It might make sense to also upgrade the stable package, as the v. 13.11 beta 9.4. is the first version that has native support (without DKMS drivers) for Saucy's Kernel. Source and more information can be found from http://support.amd.com/en- us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1254442 Title: Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Bug description: Please upgrade to new upstream release v. 13.12. This driver supports Kernels up to 3.12 and Xorg up to 1.14; ie. it should fully work on Ubuntu 13.10. The version 13.11 Beta V9.4 also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running The changelog for the v. 13.12 is in comment 3 below. It might make sense to also upgrade the stable package, as the v. 13.11 beta 9.4. is the first version that has native support (without DKMS drivers) for Saucy's Kernel. Source and more information can be found from http://support.amd.com /en-us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1254442/+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 1259467] Re: Fglrx-updates backfire
** Tags added: trusty ** Description changed: - when i Installed "fglrx-updates" drivers it back fired on me as in not able to see the screen when i booted up the computer it showed Ubuntu booting screen a lot bigger then normal and after that it lost connection with the screen and was not running monitor and could not do any thing... but when i Purged fglrx-updates it seemed to go back to normal - computer specs + When I installed "fglrx-updates" driver, it back fired on me as in not + able to see the screen when i booted up the computer. It showed Ubuntu + booting screen a lot bigger than normal and after that it lost + connection with the screen and was not running monitor and could not do + any thing... But when I purged fglrx-updates it seemed to go back to + normal. + + Ubuntu: 14.04 Kernel: 3.12.0-7 Graphic chip set: AMD/ATI: Wrestler [Radeon 6310] 1 chip - this has actually worked b4 with the issue not 100% sure what it maybe but i surely have a idea of the cause of the problem will put another comment below of saying what it maybe when i know for sure + + This has actually worked before. I'm not 100% sure what it maybe but I + surely have an idea of the cause of the problem. I will put another + comment below of saying what it maybe when I know for sure. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1259467 Title: Fglrx-updates backfire Status in “fglrx-installer-updates” package in Ubuntu: New Bug description: When I installed "fglrx-updates" driver, it back fired on me as in not able to see the screen when i booted up the computer. It showed Ubuntu booting screen a lot bigger than normal and after that it lost connection with the screen and was not running monitor and could not do any thing... But when I purged fglrx-updates it seemed to go back to normal. Ubuntu: 14.04 Kernel: 3.12.0-7 Graphic chip set: AMD/ATI: Wrestler [Radeon 6310] 1 chip This has actually worked before. I'm not 100% sure what it maybe but I surely have an idea of the cause of the problem. I will put another comment below of saying what it maybe when I know for sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1259467/+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 1176803] Re: [packaging]fglrx-* shouldn't conflict with nvidia-*
** Tags added: packaging ** Summary changed: - [packaging]fglrx-* shouldn't conflict with nvidia-* + fglrx-* shouldn't conflict with nvidia-* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1176803 Title: fglrx-* shouldn't conflict with nvidia-* Status in “fglrx-installer” package in Ubuntu: New Bug description: We can use alternatives system to switch between GL related stuff etc. So it supposed to be possible to install fglrx simultaneously with nvidia? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1176803/+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 1254442] [NEW] Please upgrade to new upstream release v.13.11 Beta V9.4 (has support for Saucy's Kernel 3.11)
Public bug reported: Please upgrade to new upstream release 13.11 Beta V9.4. This driver supports Kernels up to 3.12 and Xorg up to 1.14; ie. it should fully work on Ubuntu 13.10. This version also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running It might make sense to also upgrade the stable package, as the beta v9.4. is the first version that has native support (without DKMS drivers) for Saucy's Kernel. Source and more information can be found from http://support.amd.com/en- us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx Thanks. ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Also affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Please upgrade to new upstream release 13.11 Beta V9.4 (has support for Kernel 3.11) + Please upgrade to new upstream release 13.11 Beta V9.4 (has support for Saucy's Kernel 3.11) ** Summary changed: - Please upgrade to new upstream release 13.11 Beta V9.4 (has support for Saucy's Kernel 3.11) + Please upgrade to new upstream release v.13.11 Beta V9.4 (has support for Saucy's Kernel 3.11) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1254442 Title: Please upgrade to new upstream release v.13.11 Beta V9.4 (has support for Saucy's Kernel 3.11) Status in “fglrx-installer” package in Ubuntu: New Status in “fglrx-installer-updates” package in Ubuntu: New Bug description: Please upgrade to new upstream release 13.11 Beta V9.4. This driver supports Kernels up to 3.12 and Xorg up to 1.14; ie. it should fully work on Ubuntu 13.10. This version also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running It might make sense to also upgrade the stable package, as the beta v9.4. is the first version that has native support (without DKMS drivers) for Saucy's Kernel. Source and more information can be found from http://support.amd.com /en-us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1254442/+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 1069749] Re: Bluetooth always open after starting doesn't respect user last settings
*** This bug is a duplicate of bug 446657 *** https://bugs.launchpad.net/bugs/446657 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 446657, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 446657 Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1069749 Title: Bluetooth always open after starting doesn't respect user last settings Status in “gnome-bluetooth” package in Ubuntu: New Bug description: Bluetooth is always open or activated after starting, While it should respect the user last settings, If I disabled it before restarting or shutting down, When I start or restart my machine the bluetooth should be disabled. (Like what happen with the wireless settings applet) Reproduce: - Start your machine Bluetooth is enabled - Disable it - Logout, Restart or Shutdown - After logging in to same account Bluetooth is enabled (Didn't respect the last status before restart). Not new to quantal happens from precise. I think not related to distro. Maybe a feature request. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 12:45:16 2012 ExecutablePath: /usr/bin/bluetooth-applet InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-10-19 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1069749/+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 969860] Re: fglrx uses 100% CPU when screen turns off (spinning in glXWaitVideoSyncSGI or glXSwapBuffers)
** Tags added: battery-power-consumption quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/969860 Title: fglrx uses 100% CPU when screen turns off (spinning in glXWaitVideoSyncSGI or glXSwapBuffers) Status in Compiz: Invalid Status in Compiz 0.9.8 series: Invalid Status in Compiz Core: Invalid Status in AMD fglrx video driver: Confirmed Status in The Ubuntu Power Consumption Project: Fix Released Status in “compiz” package in Ubuntu: Invalid Status in “fglrx-installer” package in Ubuntu: Confirmed Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Status in “gnome-shell” package in Ubuntu: Invalid Bug description: WORKAROUND (1): 1. Open Catalyst Control Center. 2. Go to 3D > More Settings. 3. Set "Wait for vertical refresh" to "On, unless application specifies". And if that doesn't work, then also do: 4. Run "ccsm" 5. In Workarounds, enable "Force full screen redraw (buffer swap) on repaint". WORKAROUND (2): 1. Run ccsm (from package compizconfig-settings-manager) 2. In OpenGL > Sync To VBlank = OFF TEST CASE: 1. Monitor compiz CPU usage (from /proc//stat or top in batch mode) 2. In "brightness and lock" settings set "Turn screen off when inactive" to 1 minute 3. Wait until screen turns off 4. Move mouse or press a key to turn screen back on 5. Check the CPU usage from the monitor ACTUAL RESULT: When screen turns off compiz goes to 100% When the screen turns back on, cpu usage drops immediately to a normal value The graph attached shows %CPU of compiz with a sample per second. The graph has been captured on a system with a Radeon HD5770 and fglrx if that matter ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: compiz 1:0.9.7.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu1 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: Sat Mar 31 10:17:48 2012 DistUpgraded: 2012-02-01 00:15:24,616 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=cf89ba34-108b-404d-9804-32d54a1df2ea ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to precise on 2012-01-31 (59 days ago) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.fglrx-installer: fglrx-installer N/A 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-0ubuntu8 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/compiz/+bug/969860/+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 1069186] Re: Backlight level reset to minimum on boot
** Summary changed: - problem with backlight + Backlight level reset to minimum on boot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1069186 Title: Backlight level reset to minimum on boot Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: The main problem is with the brigthness of the screen. The system doesn't keep the custom settings of the backlight, so after restart, the brightness is again at the minimum level. That happens after every rstart. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 22.485916] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 104.994787] audit_printk_skb: 33 callbacks suppressed [ 104.994800] type=1701 audit(1350759180.462:34): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2255 comm="chromium-browse" reason="seccomp" sig=0 syscall=39 compat=0 ip=0x7fdd9d8f0ed9 code=0x5 [ 1625.376860] type=1701 audit(1350760702.976:35): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=4309 comm="chromium-browse" reason="seccomp" sig=0 syscall=39 compat=0 ip=0x7f08e871ded9 code=0x5 Date: Sat Oct 20 22:19:29 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3577] InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard Presario CQ57 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=153f70b4-3466-49e4-81ed-b87a2d4a7374 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.48 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.43:bd12/13/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.48:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Presario CQ57 Notebook PC dmi.product.version: 068E1220491620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1069186/+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 682788] Re: Improve Unity Global Menu
It means that the work/fix has been postponed to a later release of Compiz. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any "me too message"; use the "Does this bug affect you?" feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. Please try to find a solution for it that works. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+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 1138104] Re: Backup fails with Error 19 / "~/.cache/deja-dup/metadata not found in archive, no files restored."
I get this issue when trying to backup to a local folder or to Ubuntu One storage space. -- 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/1138104 Title: Backup fails with Error 19 / "~/.cache/deja-dup/metadata not found in archive, no files restored." Status in Déjà Dup Backup Tool: New Status in “deja-dup” package in Ubuntu: Confirmed Bug description: System Info: Linux Mint 14 Nadia deja-dup 24.0-0ubuntu1 duplicity 0.6.19-0ubuntu2.2 deja-dup.gsettings > http://pastebin.com/raw.php?i=RKgFMwEq debug output (tail -n 200) > http://pastebin.com/raw.php?i=GEhFz9yi Home folder is /users/ygal/ (corporate reasons) - Backup seems to run/restore successfully. No problems using duplicity. However, running deja-dup --backup yields: DUPLICITY: ERROR 19 DUPLICITY: . users/ygal/.cache/deja-dup/metadata not found in archive, no files restored. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1138104/+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
Just to clarify that I don't have this laptop - I only helped triaging this bug. Thanks. -- 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: 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_
[Desktop-packages] [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to crash Xorg
Thank you for your reply, it looks like that the Kernel doesn't detect the new BIOS version. Christopher, can you suggest of the next step to triage this bug? Thanks. -- 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: 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
[Desktop-packages] [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to crash Xorg
** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Incomplete => 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: 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: 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMA
[Desktop-packages] [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to crash Xorg
Thank you for your reply . Could you tell if you got any errors or issues while updating the BIOS as the output from the terminal states that you're using an older BIOS version? Thanks. -- 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 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
[Desktop-packages] [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to crash Xorg
The command require your password as it has sudo in front of it (and it will not work without sudo). The command was not meant to create any files to your home folder, instead the output should appear in the terminal after you press the Enter key. Could you please copy and paste the output from the terminal as a comment to this report? Thanks. -- 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 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 roo
[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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=
[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: Advan
[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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz
[Desktop-packages] [Bug 1138104] Re: Backup fails with Error 19 / "~/.cache/deja-dup/metadata not found in archive, no files restored."
** Tags added: raring -- 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/1138104 Title: Backup fails with Error 19 / "~/.cache/deja-dup/metadata not found in archive, no files restored." Status in Déjà Dup Backup Tool: New Status in “deja-dup” package in Ubuntu: Confirmed Bug description: System Info: Linux Mint 14 Nadia deja-dup 24.0-0ubuntu1 duplicity 0.6.19-0ubuntu2.2 deja-dup.gsettings > http://pastebin.com/raw.php?i=RKgFMwEq debug output (tail -n 200) > http://pastebin.com/raw.php?i=GEhFz9yi Home folder is /users/ygal/ (corporate reasons) - Backup seems to run/restore successfully. No problems using duplicity. However, running deja-dup --backup yields: DUPLICITY: ERROR 19 DUPLICITY: . users/ygal/.cache/deja-dup/metadata not found in archive, no files restored. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1138104/+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 739184] Re: [Libreoffice] Mnemonics do not work in Unity
@Paul: I think it's already covered by the indicator-appmenu task. -- 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/739184 Title: [Libreoffice] Mnemonics do not work in Unity Status in LibreOffice Productivity Suite: Won't Fix Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Triaged Bug description: When lo-menubar is installed and LibreOffice is open with a document, the keyboard shortcuts to access menus like Alt + F for file etc do not work. Menu keyboard shortcuts are working for other apps via indicator-menu. WORKAROUND: Disable the global menu by removing the package "libreoffice-gtk". To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/739184/+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 1198602] Re: Selected language is not applied
Thank you for your reply. Could you clarify if the Greek language is applied correctly? Thanks in advance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1198602 Title: Selected language is not applied Status in “language-selector” package in Ubuntu: Incomplete Bug description: The language selector on top of my screen does not obey to my commands when I do them straight on the sign or change without this to be shown. The most of the time, the Alt+Shift does not change the language either. During this apport process, very strange behaviour of my laptop,suddenly a lot of collecting informations windows appeared after they were closing to one and again in a lot. I have some screen shots of this strange behaviour. If you answer to me in my email, I will be able to send them to you in case that they will help. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: language-selector-gnome 0.110 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Sun Jul 7 07:47:26 2013 InstallationDate: Installed on 2013-02-12 (144 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to raring on 2013-05-14 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1198602/+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 1198602] Re: Selected language is not applied
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Have tried to drag and drop the Greek language above English language in the list? * What specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: language-selector (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1198602 Title: Selected language is not applied Status in “language-selector” package in Ubuntu: Incomplete Bug description: The language selector on top of my screen does not obey to my commands when I do them straight on the sign or change without this to be shown. The most of the time, the Alt+Shift does not change the language either. During this apport process, very strange behaviour of my laptop,suddenly a lot of collecting informations windows appeared after they were closing to one and again in a lot. I have some screen shots of this strange behaviour. If you answer to me in my email, I will be able to send them to you in case that they will help. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: language-selector-gnome 0.110 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Sun Jul 7 07:47:26 2013 InstallationDate: Installed on 2013-02-12 (144 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to raring on 2013-05-14 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1198602/+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 366951] Re: ValueError: too many values to unpack
** Summary changed: - [jaunty] ValueError: too many values to unpack + ValueError: too many values to unpack ** Tags added: jaunty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/366951 Title: ValueError: too many values to unpack Status in Ubuntu language selector: Invalid Status in “language-selector” package in Ubuntu: Triaged Bug description: The language-selector fails to launch after upgrade to Ubuntu 9.04. (Although I have not run it before the upgrade for long time.) The log is as follows: $ /usr/bin/gnome-language-selector /usr/lib/python2.6/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py:837: GtkWarning: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed cell = combo.get_child().get_cell_renderers()[0] Traceback (most recent call last): File "/usr/bin/gnome-language-selector", line 34, in options=options) File "/usr/lib/python2.6/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", line 171, in __init__ self.updateUserDefaultCombo() File "/usr/lib/python2.6/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", line 58, in wrapper res = f(*args, **kwargs) File "/usr/lib/python2.6/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", line 856, in updateUserDefaultCombo COMBO_LANGUAGE,self._localeinfo.translate(locale), File "/usr/lib/python2.6/dist-packages/LanguageSelector/LocaleInfo.py", line 135, in translate (lang, country) = string.split(locale, "_") ValueError: too many values to unpack $ lsb_release -d Description:Ubuntu 9.04 Which config files should I to attach? To manage notifications about this bug go to: https://bugs.launchpad.net/language-selector/+bug/366951/+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 922735] Re: additions to Depends for the Estonian language
** Tags added: unmet-deps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/922735 Title: additions to Depends for the Estonian language Status in “language-selector” package in Ubuntu: Confirmed Bug description: The Estonian national ID card is used daily to access public services and to perform online banking transactions by Estonian citizens all around the globe and by foreigners living in Estonia. It therefore is expected that whoever installs support for this language would also require support for the national ID card by standard. Packages to provide Estonian national ID card support have been developped over the last two years via the PPA for team "esteid" and have recently entered NEW for the Precise release. It would be desirable for these packages to be added to language-selector's dependencies for Estonian, starting with Precise Beta 2. Depends: browser-plugin-esteid, xul-ext-esteid, qesteidutil, qdigidoc Additionally, it would be desirable for myself to have PPU rights for the related source packages (smartcardpp, libdigidoc, libdigidocpp, qdigidoc, qesteidutil, esteid-browser-plugin) so that I can continue uploading the team's packages in the future. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: language-selector (not installed) ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1 Uname: Linux 3.2.0-11-generic i586 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Fri Jan 27 19:36:55 2012SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/922735/+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 1198602] Re: Selected language is not applied
** Description changed: - THE language selector on top of my screen does not obay to my commants ,when i do them strate on the sign or change without this to be shown,the most of the timesThe alt+swicth does not change the language too. - dURING THIS APPORT very strange behavior of my laptop,suddenly a lot of collecting informations windows appeard,after they were closing to one and again in a lot .I HAVE GOTTEN FEW SCREEN PHOTOS during this strange behavior If yoy answer to me in my email ,i will be able to send them to you in case that they will help. + The language selector on top of my screen does not obey to my commands + when I do them straight on the sign or change without this to be shown. + The most of the time, the Alt+Shift does not change the language either. + + + During this apport process, very strange behaviour of my laptop,suddenly a lot of collecting informations windows appeared after they were closing to one and again in a lot. I have some screen shots of this strange behaviour. If you answer to me in my email, I will be able to send them to you in case that they will help. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: language-selector-gnome 0.110 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Sun Jul 7 07:47:26 2013 InstallationDate: Installed on 2013-02-12 (144 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to raring on 2013-05-14 (53 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1198602 Title: Selected language is not applied Status in “language-selector” package in Ubuntu: New Bug description: The language selector on top of my screen does not obey to my commands when I do them straight on the sign or change without this to be shown. The most of the time, the Alt+Shift does not change the language either. During this apport process, very strange behaviour of my laptop,suddenly a lot of collecting informations windows appeared after they were closing to one and again in a lot. I have some screen shots of this strange behaviour. If you answer to me in my email, I will be able to send them to you in case that they will help. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: language-selector-gnome 0.110 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Sun Jul 7 07:47:26 2013 InstallationDate: Installed on 2013-02-12 (144 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to raring on 2013-05-14 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1198602/+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 1198602] Re: Selected language is not applied
** Summary changed: - language selector BUT NOT ONLY PROBLEM + Selected language is not applied -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1198602 Title: Selected language is not applied Status in “language-selector” package in Ubuntu: New Bug description: THE language selector on top of my screen does not obay to my commants ,when i do them strate on the sign or change without this to be shown,the most of the timesThe alt+swicth does not change the language too. dURING THIS APPORT very strange behavior of my laptop,suddenly a lot of collecting informations windows appeard,after they were closing to one and again in a lot .I HAVE GOTTEN FEW SCREEN PHOTOS during this strange behavior If yoy answer to me in my email ,i will be able to send them to you in case that they will help. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: language-selector-gnome 0.110 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Sun Jul 7 07:47:26 2013 InstallationDate: Installed on 2013-02-12 (144 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to raring on 2013-05-14 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1198602/+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 1198337] Re: Software Center does not open any more
Thanks. A developer will look at this issue.
** Changed in: software-center (Ubuntu)
Status: Incomplete => New
--
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/1198337
Title:
Software Center does not open any more
Status in “software-center” package in Ubuntu:
New
Bug description:
# software-center --debug
2013-07-05 17:39:24,471 - softwarecenter.ui.gtk3.em - DEBUG - EM's: 17 15 21
2013-07-05 17:39:24,528 - softwarecenter.performance - DEBUG - import
SoftwareCenterApp: 0.168025970459
2013-07-05 17:39:24,555 - softwarecenter.ui.gtk3.app - INFO - setting up
proxy 'None'
2013-07-05 17:39:24,563 - softwarecenter.db.database - DEBUG - open()
database: path=None use_axi=True use_agent=True
2013-07-05 17:39:24,576 - softwarecenter.backend.login_impl.login_sso - DEBUG
- find_credentials()
2013-07-05 17:39:24,613 - softwarecenter.fixme - WARNING - logs to the root
logger: '('/usr/lib/python2.7/dist-packages/dbus/proxies.py', 410,
'_introspect_error_handler')'
2013-07-05 17:39:24,613 - dbus.proxies - ERROR - Introspect error on
com.ubuntu.sso:/com/ubuntu/sso/credentials: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.Spawn.ChildExited: Process
/usr/lib/ubuntu-sso-client/ubuntu-sso-login exited with status 1
2013-07-05 17:39:24,614 - softwarecenter.fixme - WARNING - logs to the root
logger: '('/usr/lib/python2.7/dist-packages/dbus/proxies.py', 413,
'_introspect_error_handler')'
2013-07-05 17:39:24,614 - dbus.proxies - DEBUG - Executing introspect queue
due to error
2013-07-05 17:39:24,651 - softwarecenter.performance - DEBUG - create
SoftwareCenterApp: 0.122879981995
Traceback (most recent call last):
File "/usr/bin/software-center", line 130, in
app = SoftwareCenterAppGtk3(options, args)
File "/usr/share/software-center/softwarecenter/ui/gtk3/app.py", line 338,
in __init__
self.icons)
File
"/usr/share/software-center/softwarecenter/ui/gtk3/session/appmanager.py", line
66, in __init__
self.oauth_token = helper.find_oauth_token_sync()
File "/usr/share/software-center/softwarecenter/backend/ubuntusso.py", line
141, in find_oauth_token_sync
sso.find_credentials()
File
"/usr/share/software-center/softwarecenter/backend/login_impl/login_sso.py",
line 75, in find_credentials
self.proxy.find_credentials(self.appname, self._get_params())
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in
__call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in
__call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited:
Process /usr/lib/ubuntu-sso-client/ubuntu-sso-login exited with status 1
---
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: i386
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2013-06-29 (6 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: software-center 5.6.0-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANGUAGE=es_UY:es
TERM=xterm
PATH=(custom, no user)
LANG=es_UY.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Tags: raring
Uname: Linux 3.8.0-25-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1198337/+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 1198337] Re: Software center dont open any more
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1198337
Could you also please advice whether this issue started after an update
or randomly?
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.
** Tags removed: dbus python
** Summary changed:
- Software center dont open any more
+ Software Center does not open any more
** Changed in: software-center (Ubuntu)
Status: New => Incomplete
--
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/1198337
Title:
Software Center does not open any more
Status in “software-center” package in Ubuntu:
Incomplete
Bug description:
# software-center --debug
2013-07-05 17:39:24,471 - softwarecenter.ui.gtk3.em - DEBUG - EM's: 17 15 21
2013-07-05 17:39:24,528 - softwarecenter.performance - DEBUG - import
SoftwareCenterApp: 0.168025970459
2013-07-05 17:39:24,555 - softwarecenter.ui.gtk3.app - INFO - setting up
proxy 'None'
2013-07-05 17:39:24,563 - softwarecenter.db.database - DEBUG - open()
database: path=None use_axi=True use_agent=True
2013-07-05 17:39:24,576 - softwarecenter.backend.login_impl.login_sso - DEBUG
- find_credentials()
2013-07-05 17:39:24,613 - softwarecenter.fixme - WARNING - logs to the root
logger: '('/usr/lib/python2.7/dist-packages/dbus/proxies.py', 410,
'_introspect_error_handler')'
2013-07-05 17:39:24,613 - dbus.proxies - ERROR - Introspect error on
com.ubuntu.sso:/com/ubuntu/sso/credentials: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.Spawn.ChildExited: Process
/usr/lib/ubuntu-sso-client/ubuntu-sso-login exited with status 1
2013-07-05 17:39:24,614 - softwarecenter.fixme - WARNING - logs to the root
logger: '('/usr/lib/python2.7/dist-packages/dbus/proxies.py', 413,
'_introspect_error_handler')'
2013-07-05 17:39:24,614 - dbus.proxies - DEBUG - Executing introspect queue
due to error
2013-07-05 17:39:24,651 - softwarecenter.performance - DEBUG - create
SoftwareCenterApp: 0.122879981995
Traceback (most recent call last):
File "/usr/bin/software-center", line 130, in
app = SoftwareCenterAppGtk3(options, args)
File "/usr/share/software-center/softwarecenter/ui/gtk3/app.py", line 338,
in __init__
self.icons)
File
"/usr/share/software-center/softwarecenter/ui/gtk3/session/appmanager.py", line
66, in __init__
self.oauth_token = helper.find_oauth_token_sync()
File "/usr/share/software-center/softwarecenter/backend/ubuntusso.py", line
141, in find_oauth_token_sync
sso.find_credentials()
File
"/usr/share/software-center/softwarecenter/backend/login_impl/login_sso.py",
line 75, in find_credentials
self.proxy.find_credentials(self.appname, self._get_params())
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in
__call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in
__call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited:
Process /usr/lib/ubuntu-sso-client/ubuntu-sso-login exited with status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1198337/+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
Thank you for your reply. Please open a new report for the USB issue by running the command below from a terminal, as it will automatically gather debugging information: ubuntu-bug linux As for the Language Selector, you'll probably get the fastest support/reply from http://askubuntu.com or http://ubuntuforums.org/. You may also wish to write a bug report by running the command below: ubuntu-bug language-selector-gnome It should safe to use the wireless mouse, as it does not seem to cause the crashes. It might actually help to disable the touchpad by following the instructions from http://askubuntu.com/a/70978/8973. Thanks in advance. -- 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: Confirmed 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
[Desktop-packages] [Bug 1198214] Re: Language Selector Crash if i wish to add a Language
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding. ** Changed in: language-selector (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1198214 Title: Language Selector Crash if i wish to add a Language Status in “language-selector” package in Ubuntu: Invalid Bug description: If I click on the Button to select a new Language to add. the Program is crashing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: language-selector-gnome 0.110 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: Fri Jul 5 16:34:51 2013 ExecutablePath: /usr/bin/gnome-language-selector InstallationDate: Installed on 2012-01-10 (542 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to raring on 2013-05-02 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1198214/+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
It is safe to write your password when the you install updates as the tool will overwrite system files. Please use the support tracker at https://answers.launchpad.net/ubuntu for future support request as, bug reports are not the most efficient way to get support. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at http://askubuntu.com or http://ubuntuforums.org. Could you confirm if the crashes occurred in earlier Ubuntu version (like 12.04 or 12.10)? -- 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: Confirmed 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
[Desktop-packages] [Bug 1188197] Re: Xorg freeze on Toshiba Tecra M9 after upgrade to 12.04 during any ACPI opertions - plugging power
** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1188197 Title: Xorg freeze on Toshiba Tecra M9 after upgrade to 12.04 during any ACPI opertions - plugging power Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: Hi This laptop is having serious problems with Nvidia graphic which makes ACPI completely unusable. I have tried bot 32 and 64 release of both 12.04, 13.04 and 13.10 Aplha - all behave the same: any ACPI related operation hangs system. Those operations include: plugging in / removing power supply (every time) switching of display (after screen inactivity or when closing lid) While booting with “acpi=off” none of mentioned operations hang computer, but resolution is lower from nominal making it difficult to work on. While PC is in this “hang” state, you can move mouse, but can not click / select anything. Keyboard also doesn't work, so you can not switch to TTY console or send REISUB Luckily I have tried nightly builds 3.10.0-999-generic kernel and it works fine with it. So this ticket is just to acknowledge this problem and hopefully help any other Linux users who tried to install Ubuntu on Toshiba Tecra M9. I have also tried to run Mint Debian edition on this laptop and it runs fine without any tuning. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-45.70-generic-pae 3.2.44 Uname: Linux 3.2.0-45-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 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: Thu Jun 6 14:45:41 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation G86M [Quadro NVS 130M] [10de:042a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0001] InstallationMedia: This MachineType: TOSHIBA TECRA M9 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-45-generic-pae root=UUID=fbc0f972-0989-4b8f-a6e8-f12d4a41e9e3 ro rd.md=0 rd.lvm=0 rd.dm=0 quiet splash SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 KEYTABLE=br-abnt2i ipv6.disable=1 noresume quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/29/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.90 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.90:bd02/29/2008:svnTOSHIBA:pnTECRAM9:pvrPTM91E-04T03TEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA M9 dmi.product.version: PTM91E-04T03TEN dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.13 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1188197/+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 1037915] Re: Xorg freeze when trying to install Ubuntu
** Tags added: raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1037915 Title: Xorg freeze when trying to install Ubuntu Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: I just can't install Ubuntu 12.04 x64 from a Desktop CD. Installation and attemt to boot from a Live CD lead to a hang. I have an Nvidia GTX 580 videocard and I think the problem is in a video driver. I can install the system with an "nomodeset" mode. But it realy don't fix the problem. I don't know how to find a problem package in this case. I'm filling the bug report from a the current version of Live CD (with "nomodeset" mode) downloaded from cdimage.ubuntu.com ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CasperVersion: 1.315 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 17 06:10:49 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1203] LiveMediaBuild: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- nomodeset debian-installer/language=ru keyboard-configuration/layoutcode?=ru SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 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.:bvr1304:bd08/02/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58: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.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 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.1 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-video-nouveau/+bug/1037915/+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
** Tags added: kernel-input -- 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: Confirmed 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-
[Desktop-packages] [Bug 1197245] Re: Xorg freeze
** Tags added: likely-dup -- 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/1197245 Title: Xorg freeze Status in “xorg” package in Ubuntu: New Bug description: All these started when yesterday, as i have reported already to Mr Papukaja in ubuntu this right moment by email answer to him,i was trying to read from this page "http://anti-researcher.blogspot.gr/2012/01/blog-post_6693.html",the screen was every ,but every 5 seconds dark and only when i was pressing under help the Submit feedback was getting light and all this was happining for more than one hour until i had to turn off the laptop.When today i turned it on i did my updates you have sent me ,i restarted the computer and by my hotmail account i was trying to answer to Mr Ppukaja,again the same thing happened.A script appeared today "crome://global/content/bindings/browser.xml:236" I press "stop" but again the screen got dark , so again i had to press alt+f2 (was not even this easy,i had to repress several times until the bug-report appeared.Another script came out "http://choise.truste.com/ca?aid=tradedesk01&pid=tradedesk01&cid=0511td300x250&w=300&h=250&plc=tr&c=tradedesk01cont1&js=2:22 " During exactly this moment where i am writing this FURTHER INFORMATION this script threw me out of the launchpad window twice BUT i still insiste to write this to you.At this moment my screen goes almost every second darker but i will try to send you IT IS VERY VERY HARD TO COMPLETE THIS 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 CurrentDmesg: [ 28.997038] ppdev: user-space parallel port driver [ 29.902178] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 29.906326] 8139too :0a:07.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Date: Wed Jul 3 07:11:31 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: Within the last few days 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 (140 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to raring on 2013-05-14 (49 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: dmi.product.name: AMILO Li 1718 dmi.product.version: -1 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed Jul 3 06:41:22 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower B
[Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
** Tags added: crash -- 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: New 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3
[Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
I also opened this bug for the linix package as the actual harware detection is done by the Kernel. However, I'm leaving the Xorg part open too since the crash occurs in Xorg. The duplicate bug 1197301 (reported by the same person than this bug on the same hardware) no longer mentions the "MS Nano Receiver" but still has the "mi EQ" error and the log also has confusion about the HW detection of the touchpad. ** Package changed: xorg (Ubuntu) => xserver-xorg-input-synaptics (Ubuntu) -- 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: New 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 00
[Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1191334 Title: A wrong hardware detection seems to crash Xorg Status in “linux” package in Ubuntu: New 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a
[Desktop-packages] [Bug 1171666] Re: xserver-xorg-core not installed on update from 12.04 to 12.10
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1171666 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: quantal ** Package changed: xserver-xorg (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1171666 Title: xserver-xorg-core not installed on update from 12.04 to 12.10 Status in “xorg” package in Ubuntu: Incomplete Bug description: I installed 12.04 LTS on 2013-04-18, and everything was running fine. I updated to 12.10 Quantal on 2013-04-21 and once the upgrade was complete, I rebooted. Bug: 1. Upon reboot, I couldn't get past the Ubuntu loading screen (never got to login, went to a black screen instead). 2. I rebooted again and this time I pressed ESC to get to the console and logged in the console 3. I tried "startx" and it failed with "No Screen Found" 4. I looked at /var/log/xorg.0.log and found that it was trying to load a bunch of modules "intel", "vesa", and a few others... seems like it was trying to find a drivers to load but couldn't find any. At the bottom of the log it gave up with "No Drivers Available" or something. Workaround: 5. I found that I had a bunch of xserver-*-lts-quantal packages, and I thought those weren't supposed to be there so I "apt-get install xserver-xorg-video-intel" and it replaced the xserver-*-lts-quantal packages with just xserver-xorg. 6. Rebooted, and the problem was gone (X started fine). So everything is working now, but I thought I'd file this somewhere since I had a very stock install (~3 days old) and it seems like it failed to update xserver packages during the 12.04->12.10 upgrade. I'm on a ThinkPad T410s and my video card is: VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) Please let me know if I filed this in the wrong place :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1171666/+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 1197301] Re: Xorg freeze
*** This bug is a duplicate of bug 1191334 *** https://bugs.launchpad.net/bugs/1191334 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1191334, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1191334 A wrong hardware detection seems to crash Xorg -- 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/1197301 Title: Xorg freeze Status in “xorg” package in Ubuntu: New Bug description: file:///home/ubuntu/Pictures/Screenshot%20from%202013-07-03%2011:46:22.png file:///home/ubuntu/Pictures/Screenshot%20from%202013-07-03%2011:50:46.png file:///home/ubuntu/Pictures/Screenshot%20from%202013-07-03%2011:56:11.png I HOPE YOU CAN GET THESE PICTURES FROM THE SCREEN .IT SHOWS A "WINDOW" ITEM WHICH CONTAINS 82 ITEMS WHICH I AM TRYING TO THROW AWAY BY TRASH BUT IT SEEMS THAT TRASH CANNOT GET EMPTY. IT APPEARS SUDENLY WHILE I WAS WORKING ON THE COMPUTER WITH LIBRE OFFICE WRITTER ON THE LEFT SIDE OF THE SCREEN.WAS WITH SOME OTHER STRANGE FILES WHICH I WAS NOT ABLE TO OPEN SO I SEND THEM TO TRASH BUT WHEN I TRIED TO EMPTY THE TRASH LAPTOP WAS BLOCKED .I COULDN'T DO ANY ACTION.I CALL A FRIEND ASKING HOW TO TAKE A PHOTO FROM THE SCREEN AND WHILE I WAS OPENNING AND CLOSSING THE DOOR ON THE SIDE OF THE DISC DRIVER (THIS ACTION ALWAYS HELPS ME) AND PRESSING ALT+F2 IT UNBLOCKED.I SAVE THESE PICTURES AND I SEND YOU .IF THIS IS NOT A GOOD HELP TO FIGUER OUT WHAT IS HAPPENNING HERE I AM GOING TO TRY TO SEND THEM BY EMAIL TO MR PAPUKAJA AS ATTACHEMENTS ON THE EMAIL. THANK YOU A LOT ALL OF YOU THERE . SPECIAL THANKS TO THE EXCELLENT MR PAPUKAJA. 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: Wed Jul 3 11:49:18 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: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days 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 (140 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 002 Device 005: 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to raring on 2013-05-14 (49 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: dmi.product.name: AMILO Li 1718 dmi.product.version: -1 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:
[Desktop-packages] [Bug 1197245] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. There are couple of things to note here. Firstly, the web page that you are trying to access is very long and resource heavy with the multiple Flash adverts and javascript codes. It hangs (ie. the screen gets darker) my Firefox too but Firefox becomes responsive after a while. Perhaps you could provide feedback to the author of the website and tell them that the pages in the website should be less resource heavy. Secondly, the log files show that the driver for your laptop's touchpad gets unloaded. The reason for it is unclear but it explains why your system is so unresponsive and difficult to control. Finally, it is clear from this and your other bug reports that there is definitely a crash in the graphics system in your computer. This issue seems to be worsened with any resource heavy applications or websites. I am leaving this report open for now but it might be classified later as a duplicate of bug 1191334. Thanks. -- 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/1197245 Title: Xorg freeze Status in “xorg” package in Ubuntu: New Bug description: All these started when yesterday, as i have reported already to Mr Papukaja in ubuntu this right moment by email answer to him,i was trying to read from this page "http://anti-researcher.blogspot.gr/2012/01/blog-post_6693.html",the screen was every ,but every 5 seconds dark and only when i was pressing under help the Submit feedback was getting light and all this was happining for more than one hour until i had to turn off the laptop.When today i turned it on i did my updates you have sent me ,i restarted the computer and by my hotmail account i was trying to answer to Mr Ppukaja,again the same thing happened.A script appeared today "crome://global/content/bindings/browser.xml:236" I press "stop" but again the screen got dark , so again i had to press alt+f2 (was not even this easy,i had to repress several times until the bug-report appeared.Another script came out "http://choise.truste.com/ca?aid=tradedesk01&pid=tradedesk01&cid=0511td300x250&w=300&h=250&plc=tr&c=tradedesk01cont1&js=2:22 " During exactly this moment where i am writing this FURTHER INFORMATION this script threw me out of the launchpad window twice BUT i still insiste to write this to you.At this moment my screen goes almost every second darker but i will try to send you IT IS VERY VERY HARD TO COMPLETE THIS 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 CurrentDmesg: [ 28.997038] ppdev: user-space parallel port driver [ 29.902178] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 29.906326] 8139too :0a:07.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Date: Wed Jul 3 07:11:31 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: Within the last few days 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 (140 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to raring on 2013-05-14 (49 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSU
[Desktop-packages] [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
** Changed in: xorg (Ubuntu) Status: Incomplete => New -- 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/1191334 Title: A wrong hardware detection seems to crash Xorg Status in “xorg” 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg
[Desktop-packages] [Bug 1195965] Re: Firefox not responding in AOL Inbox
It should be noted that this bug is very likely related to the crash in Xorg, please see bug 1191334 for more information. Thanks. ** Tags added: likely-dup -- 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/1195965 Title: Firefox not responding in AOL Inbox Status in The Mozilla Firefox Browser: New Status in “firefox” package in Ubuntu: New Bug description: When I turned on my laptop today for once, a small window opened telling me that my system has a problem. Usually, lately, I ignore these messages because they ask me to give my Ubuntu password and for security reasons [I don't normally give it], but this time I checked it little bit more. So I pressed report the problem and another window appeared. This new window had the name "authenticate" and the following writing: Please enter your password to access problem reports of system programs. An application is attempting to perform an action that requires privileges. AUTHENTICATION IS REQUIRED TO PERFORM THIS ACTION. Password... Under this on the left bottom was a small upside down triangle and the word Details. I pressed the Details and appeared: Action :com.ubuntu.apport.apport-gtk-root Vendor : Apport} Pressing the Vendor word SOMETHING VERY STRANGE HAPPENNED: A new window came out: "Close Firefox. Firefox is already running,but is not responding.To open a new window , you must first close the existing Firefox process, or restart your system .OK ." BUT FIREFOX WAS NOT OPENED / AND THIS HAS HAPPENED IN THE PAST FEW TIMES. I mean that quite few times has happened that WITHOUT Firefox opened the system tells me THAT FIREFOX IS ALREADY RUNNING!!! Anyway I had to press OK to that so Firefox opened by itself on https://wiki.ubuntu.com/Apport. I stop everything there and I put on the side this Authenticate window. I did not give my password (Please tell me if this comes out to you in UBUNTU, and WHY FIREFOX seems to be open when it is not). After that I checked my Hotmail account to see if you have sent me something from the yesterday problems I had faced and reported to you. I had no answer so I logged out from hotmail and I went to my other email account in AOL. I succesfully logged in BUT when I tried to check my inbox the screen (I only had this window in AOL opened) got dark and was not responding. I pressed Ubuntu Help and after while the screen got lighter but I could check my emails, AGAIN got darker and I had to press alt+f2 several times (was not openning) and finally got to send this report to you with all of these details. PLEASE ONCE MORE I NEED YOUR HELP. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Sat Jun 29 09:39:58 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 3600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-02-12 (136 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to raring on 2013-05-14 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1195965/+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 1196309] Re: the screen got strange
*** This bug is a duplicate of bug 1195965 *** https://bugs.launchpad.net/bugs/1195965 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1195965, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1195965 Firefox not responding in AOL Inbox -- 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/1196309 Title: the screen got strange Status in “xorg” package in Ubuntu: New Bug description: I am sorry but i don't know how to photo the screen so i can attach it .But the firefox window got really down on the screen ,the bookmarks page appeared on top and ubuntu help window got slim and long. 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: Sun Jun 30 22:29:33 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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 (138 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 002 Device 002: 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to raring on 2013-05-14 (47 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: dmi.product.name: AMILO Li 1718 dmi.product.version: -1 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Jun 30 18:39:33 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1196309/+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 1192202] Re: Discs burnt with Brasero cannot always be opened in Windows
** Attachment removed: "Test file" https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1192202/+attachment/3716030/+files/TnIN3q%3F%3D%0A%20%3D%3Fiso-8859-7%3FB%3F6OXz5yAucGRm%3F%3D -- 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/1192202 Title: Discs burnt with Brasero cannot always be opened in Windows Status in “brasero” package in Ubuntu: New Bug description: CDs burnt with Brasero fails to open in friends' computuers on Windows but open fine on my computer. The filename of the PDF file on the CD has a rhombus between the letters meaning that something is wrong. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 17:44:29 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1192202/+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 1192202] Re: Discs burnt with Brasero cannot always be opened in Windows
Thanks. I removed the first attachment as it did not work. ** Changed in: brasero (Ubuntu) Status: Incomplete => New -- 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/1192202 Title: Discs burnt with Brasero cannot always be opened in Windows Status in “brasero” package in Ubuntu: New Bug description: CDs burnt with Brasero fails to open in friends' computuers on Windows but open fine on my computer. The filename of the PDF file on the CD has a rhombus between the letters meaning that something is wrong. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 17:44:29 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1192202/+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 1192202] Re: Discs burnt with Brasero cannot always be opened in Windows
Thank you for your reply. Unfortunately the file did not get attached properly. Could you try to attach the file from the web interface at https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1192202/+addcomment ? Thanks. -- 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/1192202 Title: Discs burnt with Brasero cannot always be opened in Windows Status in “brasero” package in Ubuntu: Incomplete Bug description: CDs burnt with Brasero fails to open in friends' computuers on Windows but open fine on my computer. The filename of the PDF file on the CD has a rhombus between the letters meaning that something is wrong. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 17:44:29 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1192202/+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 1185120] Re: Crash when trying to access certain websites
This issue is very likely to be related to the crash in your graphics driver, which is reported as bug 1191334. If you believe that they are separate issues (or if you just want to check it, you may wish to follow the instructions at https://wiki.ubuntu.com/MozillaTeam/Bugs#Hangs.2C_or_excessive_CPU_usage. However, if you decide follow the linked guidance, you would need to open a new bug with apport as required at https://wiki.ubuntu.com/MozillaTeam/Bugs#Use_Apport. Therefore, I am closing this bug report. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Package changed: ubuntu => firefox (Ubuntu) ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- 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/1185120 Title: Crash when trying to access certain websites Status in “firefox” package in Ubuntu: Invalid Bug description: Hi people in Ubuntu one more time today. So I cannot work anymore on this computer, I got at least 15 scripts trying to block me: 1) crome://global/content/bindings/tabbox.xml:73 , this was one time 2) http://www.blogblog.com/dynamicviews/2556441d71ff161/js/common.js:77 , this was twice 3) resource://gre/components/nsPrompter.js:434 , this was one time 4) http://www.blogblog.com/dynamicviews/2556441d71ff161/js/common.js:88 , this was once again 5) http://www.blogblog.com/dynamicviews/2556441d71ff161/js/common.js:79 , again one time 6) http://www.blogblog.com/dynamicviews/2556441d71ff161/js/thirdparty/jquery.js:14 , this was at least 8 TIMES until was able to block me for good. Unable to do anything else, not even alt+f2. I turned off the electricity (I couldn't do any other way). The moment was going off I saw on the side the ubuntu software center,which I had not open. So after few time I turned on again my computer and i saw that just before close down were installed some software ( at 7:50) WHAT is this? If is it from you , is ok,but is it? Also I want to write that the Libreoffice has been very very slow from opening to saving or exporting PDF.If it help in your efforts to help me at the time all this was happenning i was visiting the www.chaos.crisis.blodspot.gr , enikos.gr and antipliroforisi.blogspot.gr and zougla.gr. Thank you again ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Tue May 28 20:08:48 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 3600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-02-12 (105 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to raring on 2013-05-14 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1185120/+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 1192212] Re: Problems in LibreOffice Writer
** Tags added: likely-dup -- 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/1192212 Title: Problems in LibreOffice Writer Status in “libreoffice” package in Ubuntu: Incomplete Bug description: I face too many problems in LibreOffice Writer (and Firefox too). All are blocked. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 18:06:10 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192212/+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 1192202] Re: LibreOffice doesn't work right
Thank you for your reply. The crash is most likely related to the crash in your graphics driver (ie. bug 1191334) so I'm moving this bug to the brasero package as it looks like that Brasero fails to burn the CD correctly. Thanks. ** Package changed: libreoffice (Ubuntu) => brasero (Ubuntu) ** Changed in: brasero (Ubuntu) Status: Incomplete => New ** Summary changed: - LibreOffice doesn't work right + Discs burnt with Brasero cannot always be opened in Windows ** Description changed: - Every time i try to work with libre office seems it is very difficult - and no secure. The libre office writer window gets dark ,freezes and - saves the document without me asking for and not even showing that it is - saved. Who saves my writting and puts in stuff that when i transfer this - on a cd doesn't work the most of the times. + CDs burnt with Brasero fails to open in friends' computuers on Windows + but open fine on my computer. The filename of the PDF file on the CD has + a rhombus between the letters meaning that something is wrong. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 17:44:29 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) -- 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/1192202 Title: Discs burnt with Brasero cannot always be opened in Windows Status in “brasero” package in Ubuntu: New Bug description: CDs burnt with Brasero fails to open in friends' computuers on Windows but open fine on my computer. The filename of the PDF file on the CD has a rhombus between the letters meaning that something is wrong. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 17:44:29 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1192202/+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: Xorg freeze
By the way, I think it safe for you to start using the wireless mouse again as it didn't solve this issue. ** Summary changed: - Xorg freeze + A wrong hardware detection seems to crash Xorg -- 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/1191334 Title: A wrong hardware detection seems to crash Xorg Status in “xorg” 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOO
[Desktop-packages] [Bug 1191334] Re: Xorg freeze
Thank you for your reply. Ubuntu does not really have any viruses or spyware so the probability that someone has cracked your system is very. I tried googling the specifications of your laptop and it looks like that your computer does not have an internal bluetooth device. Therefore, it is much more probable that the system simply does not detect your hardware correctly. I'm linking the previous Xorg report to this report. Thanks. ** Description changed: - This time i didn't use the wireless mouse + 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] + 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
[Desktop-packages] [Bug 1190987] Re: Microsoft Wireless Mouse crashes Xorg
*** This bug is a duplicate of bug 1191334 *** https://bugs.launchpad.net/bugs/1191334 I'm marking this bug as a duplicating of bug 1191334 as the mouse does not seem to cause the crash. That bug report has the logs without the mouse being used. For anyone reading this bug report: The answer to the question from the comment above and some further troubleshooting is in the bug 1191334. Thanks. ** This bug has been marked a duplicate of bug 1191334 Xorg freeze -- 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/1190987 Title: Microsoft Wireless Mouse crashes Xorg Status in “xorg-server” package in Ubuntu: Incomplete Bug description: Too many problems,the screen locks, the internet crash, the help does not open, the bug report opened after several efforts or stops, not even the email account works (babisxanthopou...@hotmail.com). --- From Xorg.log: [ 10064.405] [mi] Increasing EQ size to 512 to prevent dropped events. (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76adf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb768c6b3] (EE) 2: /usr/bin/X (0xb750+0x54325) [0xb7554325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb7590ffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x3bad) [0xb6ecabad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x5286) [0xb6ecc286] (EE) 6: /usr/bin/X (0xb750+0x80101) [0xb7580101] (EE) 7: /usr/bin/X (0xb750+0xac153) [0xb75ac153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] (EE) 9: /usr/bin/X (0xb750+0x1b2360) [0xb76b2360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] (EE) 11: /lib/i386-linux-gnu/libc.so.6 (sigemptyset+0x0) [0xb710e5f0] (EE) 12: /usr/bin/X (OsBlockSIGIO+0x50) [0xb76b4330] (EE) 13: /usr/bin/X (OsBlockSignals+0x3f) [0xb76b43bf] (EE) 14: /usr/bin/X (0xb750+0x18c239) [0xb768c239] (EE) 15: /usr/bin/X (mieqProcessInputEvents+0x201) [0xb768cd11] (EE) 16: /usr/bin/X (ProcessInputEvents+0x14) [0xb75801b4] (EE) 17: /usr/bin/X (0xb750+0x3de3c) [0xb753de3c] (EE) 18: /usr/bin/X (0xb750+0x2b525) [0xb752b525] (EE) 19: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb70f8935] (EE) 20: /usr/bin/X (0xb750+0x2b8f9) [0xb752b8f9] (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. [ 10066.903] [mi] EQ processing has resumed after 29 dropped events. [ 10066.903] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 14062.928] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: initialized for relative axes. [ 14062.928] (WW) evdev: Microsoft Microsoft® Nano Transceiver v2.0: ignoring absolute axes. 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: Fri Jun 14 15:03:32 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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 (121 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 003 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to raring on 2013-05-14 (30 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi
[Desktop-packages] [Bug 1192202] Re: LibreOffice doesn't work right
Thank you for your reply. Could you clarify whether the problematic CDs (that don't work in your friends computers) work in your computer? I'm not sure about the LO's auto saving, it could just be related to the crash which interrupts the normal functioning of LO. Thanks. -- 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/1192202 Title: LibreOffice doesn't work right Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Every time i try to work with libre office seems it is very difficult and no secure. The libre office writer window gets dark ,freezes and saves the document without me asking for and not even showing that it is saved. Who saves my writting and puts in stuff that when i transfer this on a cd doesn't work the most of the times. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 17:44:29 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192202/+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: Xorg freeze
Thank you for your reply. I looked at the attached logs in more details and it looks like that you are using a wireless keyboard. Could you try using your computer without it and check whether Firefox or LibreOffice still crashes? Thanks. -- 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/1191334 Title: Xorg freeze Status in “xorg” package in Ubuntu: Incomplete Bug description: This time i didn't use the wireless mouse 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to raring on 2013-05-14 (31 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: dmi.product.name: AMILO Li 1718 dmi.product.version: -1 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 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: Sat Jun 15 11:25:40 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1191334/+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: Xorg freeze
Thank you for your reply. The driver for the mouse is included in the default install (as part of the Kernel). Can you confirm if you restarted your computer before writing this report as the some of the log files in this report are created when the sytem starts? It is often safe to type your password to the dialogue but check wwhat application is asking for the password. Its name is shown in the title of that dialogue, for example Apport (the bug reporting tool) is safe and often requires your password to access some system log files. if you are unsure whether it is safe to type your password, do not type it. Thanks. -- 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/1191334 Title: Xorg freeze Status in “xorg” package in Ubuntu: Incomplete Bug description: This time i didn't use the wireless mouse 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to raring on 2013-05-14 (31 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: dmi.product.name: AMILO Li 1718 dmi.product.version: -1 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 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: Sat Jun 15 11:25:40 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1191334/+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 1192202] Re: LIBRE OFFICE doesn't works right
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * What application do you you se to burn the file to the CD? * Are you to access the content of the CD on a different computer? * If yes, what operating system does it use? This will help us to find and resolve the problem. LibreOffice saves by default the current document every 15 minutes and it should also be able to restore the document in case of a crash. Thanks. ** Description changed: Every time i try to work with libre office seems it is very difficult - and no secure.The libre office writer window gets dark ,freezes and + and no secure. The libre office writer window gets dark ,freezes and saves the document without me asking for and not even showing that it is - saved.Who saves my writting and puts in stuff that when i transfer this + saved. Who saves my writting and puts in stuff that when i transfer this on a cd doesn't work the most of the times. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 17:44:29 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete ** Summary changed: - LIBRE OFFICE doesn't works right + LibreOffice doesn't work right -- 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/1192202 Title: LibreOffice doesn't work right Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Every time i try to work with libre office seems it is very difficult and no secure. The libre office writer window gets dark ,freezes and saves the document without me asking for and not even showing that it is saved. Who saves my writting and puts in stuff that when i transfer this on a cd doesn't work the most of the times. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 17:44:29 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192202/+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 1192212] Re: Problems in LibreOffice Writer
I removed the reference to Firefox as it is being tracked in bug 1185120. ** Summary changed: - Problems in LibreOffice Writer and Firefox + Problems in LibreOffice Writer ** Description changed: - I face too many problems in LibreOffice Writer and Firefox too. All are - blocked. + I face too many problems in LibreOffice Writer (and Firefox too). All + are blocked. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 18:06:10 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) -- 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/1192212 Title: Problems in LibreOffice Writer Status in “libreoffice” package in Ubuntu: Incomplete Bug description: I face too many problems in LibreOffice Writer (and Firefox too). All are blocked. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 18:06:10 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192212/+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 1192212] Re: Problems in LibreOffice Writer and Firefox
It's likely due to to crash in X server. Please see bug 1190987 for more details. Thanks. -- 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/1192212 Title: Problems in LibreOffice Writer and Firefox Status in “libreoffice” package in Ubuntu: Incomplete Bug description: I face too many problems in LibreOffice Writer and Firefox too. All are blocked. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Tue Jun 18 18:06:10 2013 InstallationDate: Installed on 2013-02-12 (126 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-05-14 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1192212/+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 1169664] Re: Ubuntu 13.4, Rhythmbox. Audiofiles .wav sound distorted.
The requested information has been provided and the issue seems to be Rhythmbox specific. ** Tags added: raring ** Package changed: ubuntu => rhythmbox (Ubuntu) ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => New ** Summary changed: - Ubuntu 13.4, Rhythmbox. Audiofiles .wav sound distorted. + Distorted sound with wav files in Rhythmbox -- 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/1169664 Title: Distorted sound with wav files in Rhythmbox Status in “rhythmbox” package in Ubuntu: New Bug description: I just installed Ubuntu 13.4 and updated it. When I tried with Rhythmbox to play audio-files with extention .wav they sound distorted. With VLC it sounds good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1169664/+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 1138251] Re: Desktop wallpaper Colors & Gradients will not change color
*** This bug is a duplicate of bug 1173818 *** https://bugs.launchpad.net/bugs/1173818 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1173818, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1173818 Unable to set solid colors and gradients as desktop background in gnome-control-center -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1138251 Title: Desktop wallpaper Colors & Gradients will not change color Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: To reproduce - System Settings - Appearances - Background > Colors & Gradients - Set a new sold color What happens - Background remains black. This is the same for solid colors and gradients What should happen - Background should change to new color ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0 Uname: Linux 3.8.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 1 17:43:58 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0446] NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0446] InstallationDate: Installed on 2013-02-11 (18 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130210) MachineType: Dell Inc. Dell System XPS 15Z MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-8-generic root=UUID=93acc5a7-d531-4af3-a215-472a7bd065d6 ro acpi_backlight=vendor dell_laptop.backlight=0 quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 060G42 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd07/27/2011:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn060G42:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS 15Z dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.03.01-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1138251/+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 1153902] Re: desktop background - colors & gradients not working
*** This bug is a duplicate of bug 1173818 *** https://bugs.launchpad.net/bugs/1173818 ** This bug is no longer a duplicate of bug 1138251 Desktop wallpaper Colors & Gradients will not change color ** This bug has been marked a duplicate of bug 1173818 Unable to set solid colors and gradients as desktop background in gnome-control-center -- 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/1153902 Title: desktop background - colors & gradients not working Status in “gnome-control-center” package in Ubuntu: New Bug description: Gnome-control-center >> Appearance >> Look >> Color & Gradients I can't pick solid colors except from black & dark purple. In the screenshot attached, I chose "Blue" as background color, but the desktop remained "black". "Vertical gradient" and "Horizontal gradient" are not working too. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic i686 ApportVersion: 2.9.1-0ubuntu1 Architecture: i386 Date: Mon Mar 11 21:57:31 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-03-11 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130310) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1153902/+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: Xorg freeze
Thank you for testing without the wireless mouse. However, the attached logs still mention "Microsoft Microsoft® Nano Transceiver v2.0", which seems to be related to the wireless mouse. Could you confirm if the mouse's receiver/transmitter was attached to your computer when the crash happened? Thanks. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1191334 Title: Xorg freeze Status in “xorg” package in Ubuntu: Incomplete Bug description: This time i didn't use the wireless mouse 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to raring on 2013-05-14 (31 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: dmi.product.name: AMILO Li 1718 dmi.product.version: -1 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 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: Sat Jun 15 11:25:40 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1191334/+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 1190987] Re: Microsoft Wireless Mouse crashes Xorg
Thank you for your reply. I think that it is reasonable to assume that the crash would not occur without the wireless mouse. You don't need a buy a new mouse with a wire. Could you try booting your computer without the wireless mouse and using the touchpad of your laptop instead? Thanks. ** Summary changed: - Xorg crash, possibly due to a Microsft Wireless Keyboard + Microsoft Wireless Mouse crashes Xorg -- 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/1190987 Title: Microsoft Wireless Mouse crashes Xorg Status in “xorg” package in Ubuntu: Incomplete Bug description: Too many problems,the screen locks, the internet crash, the help does not open, the bug report opened after several efforts or stops, not even the email account works (babisxanthopou...@hotmail.com). --- From Xorg.log: [ 10064.405] [mi] Increasing EQ size to 512 to prevent dropped events. (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76adf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb768c6b3] (EE) 2: /usr/bin/X (0xb750+0x54325) [0xb7554325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb7590ffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x3bad) [0xb6ecabad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x5286) [0xb6ecc286] (EE) 6: /usr/bin/X (0xb750+0x80101) [0xb7580101] (EE) 7: /usr/bin/X (0xb750+0xac153) [0xb75ac153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] (EE) 9: /usr/bin/X (0xb750+0x1b2360) [0xb76b2360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] (EE) 11: /lib/i386-linux-gnu/libc.so.6 (sigemptyset+0x0) [0xb710e5f0] (EE) 12: /usr/bin/X (OsBlockSIGIO+0x50) [0xb76b4330] (EE) 13: /usr/bin/X (OsBlockSignals+0x3f) [0xb76b43bf] (EE) 14: /usr/bin/X (0xb750+0x18c239) [0xb768c239] (EE) 15: /usr/bin/X (mieqProcessInputEvents+0x201) [0xb768cd11] (EE) 16: /usr/bin/X (ProcessInputEvents+0x14) [0xb75801b4] (EE) 17: /usr/bin/X (0xb750+0x3de3c) [0xb753de3c] (EE) 18: /usr/bin/X (0xb750+0x2b525) [0xb752b525] (EE) 19: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb70f8935] (EE) 20: /usr/bin/X (0xb750+0x2b8f9) [0xb752b8f9] (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. [ 10066.903] [mi] EQ processing has resumed after 29 dropped events. [ 10066.903] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 14062.928] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: initialized for relative axes. [ 14062.928] (WW) evdev: Microsoft Microsoft® Nano Transceiver v2.0: ignoring absolute axes. 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: Fri Jun 14 15:03:32 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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 (121 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 003 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to raring on 2013-05-14 (30 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor:
[Desktop-packages] [Bug 1190987] Re: Xorg crash, possibly due to a Microsft Wireless Keyboard
Thank you for your reply. Could you confirm if you get this issue is you unplug the wireless mouse from your computer? -- 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/1190987 Title: Xorg crash, possibly due to a Microsft Wireless Keyboard Status in “xorg” package in Ubuntu: Incomplete Bug description: Too many problems,the screen locks, the internet crash, the help does not open, the bug report opened after several efforts or stops, not even the email account works (babisxanthopou...@hotmail.com). --- From Xorg.log: [ 10064.405] [mi] Increasing EQ size to 512 to prevent dropped events. (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76adf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb768c6b3] (EE) 2: /usr/bin/X (0xb750+0x54325) [0xb7554325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb7590ffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x3bad) [0xb6ecabad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x5286) [0xb6ecc286] (EE) 6: /usr/bin/X (0xb750+0x80101) [0xb7580101] (EE) 7: /usr/bin/X (0xb750+0xac153) [0xb75ac153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] (EE) 9: /usr/bin/X (0xb750+0x1b2360) [0xb76b2360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] (EE) 11: /lib/i386-linux-gnu/libc.so.6 (sigemptyset+0x0) [0xb710e5f0] (EE) 12: /usr/bin/X (OsBlockSIGIO+0x50) [0xb76b4330] (EE) 13: /usr/bin/X (OsBlockSignals+0x3f) [0xb76b43bf] (EE) 14: /usr/bin/X (0xb750+0x18c239) [0xb768c239] (EE) 15: /usr/bin/X (mieqProcessInputEvents+0x201) [0xb768cd11] (EE) 16: /usr/bin/X (ProcessInputEvents+0x14) [0xb75801b4] (EE) 17: /usr/bin/X (0xb750+0x3de3c) [0xb753de3c] (EE) 18: /usr/bin/X (0xb750+0x2b525) [0xb752b525] (EE) 19: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb70f8935] (EE) 20: /usr/bin/X (0xb750+0x2b8f9) [0xb752b8f9] (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. [ 10066.903] [mi] EQ processing has resumed after 29 dropped events. [ 10066.903] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 14062.928] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: initialized for relative axes. [ 14062.928] (WW) evdev: Microsoft Microsoft® Nano Transceiver v2.0: ignoring absolute axes. 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: Fri Jun 14 15:03:32 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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 (121 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 003 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to raring on 2013-05-14 (30 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.8:bd06/25/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: dmi.product.name: AMILO Li 1718 dmi.product.version: -1 dmi.sys.vendor: FUJITSU SIEMEN
[Desktop-packages] [Bug 1190987] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you kindly confirm if you encounter this issue if you unplug the wireless keyboard (if you have one)from your computer? This will help us to find and resolve the problem. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg crash + Xorg crash, possibly due to a Microsft Wireless Keyboard -- 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/1190987 Title: Xorg crash, possibly due to a Microsft Wireless Keyboard Status in “xorg” package in Ubuntu: Incomplete Bug description: Too many problems,the screen locks, the internet crash, the help does not open, the bug report opened after several efforts or stops, not even the email account works (babisxanthopou...@hotmail.com). --- From Xorg.log: [ 10064.405] [mi] Increasing EQ size to 512 to prevent dropped events. (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76adf49] (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb768c6b3] (EE) 2: /usr/bin/X (0xb750+0x54325) [0xb7554325] (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb7590ffb] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x3bad) [0xb6ecabad] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x5286) [0xb6ecc286] (EE) 6: /usr/bin/X (0xb750+0x80101) [0xb7580101] (EE) 7: /usr/bin/X (0xb750+0xac153) [0xb75ac153] (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] (EE) 9: /usr/bin/X (0xb750+0x1b2360) [0xb76b2360] (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] (EE) 11: /lib/i386-linux-gnu/libc.so.6 (sigemptyset+0x0) [0xb710e5f0] (EE) 12: /usr/bin/X (OsBlockSIGIO+0x50) [0xb76b4330] (EE) 13: /usr/bin/X (OsBlockSignals+0x3f) [0xb76b43bf] (EE) 14: /usr/bin/X (0xb750+0x18c239) [0xb768c239] (EE) 15: /usr/bin/X (mieqProcessInputEvents+0x201) [0xb768cd11] (EE) 16: /usr/bin/X (ProcessInputEvents+0x14) [0xb75801b4] (EE) 17: /usr/bin/X (0xb750+0x3de3c) [0xb753de3c] (EE) 18: /usr/bin/X (0xb750+0x2b525) [0xb752b525] (EE) 19: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb70f8935] (EE) 20: /usr/bin/X (0xb750+0x2b8f9) [0xb752b8f9] (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. [ 10066.903] [mi] EQ processing has resumed after 29 dropped events. [ 10066.903] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 14062.928] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: initialized for relative axes. [ 14062.928] (WW) evdev: Microsoft Microsoft® Nano Transceiver v2.0: ignoring absolute axes. 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: Fri Jun 14 15:03:32 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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 (121 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 003 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth 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= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to raring on 2013-05-14 (30 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.typ
[Desktop-packages] [Bug 1190987] Re: Xorg crash
** Description changed: - too many problems,the sreen locks,the internet crash,the help does not - open,the bug report opened after several efforts or stops,not even the - email account works (babisxanthopou...@hotmail.com) + Too many problems,the screen locks, the internet crash, the help does not open, the bug report opened after several efforts or stops, not even the email account works (babisxanthopou...@hotmail.com). + --- + + From Xorg.log: + + [ 10064.405] [mi] Increasing EQ size to 512 to prevent dropped events. + (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. + (EE) + (EE) Backtrace: + (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76adf49] + (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb768c6b3] + (EE) 2: /usr/bin/X (0xb750+0x54325) [0xb7554325] + (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb7590ffb] + (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x3bad) [0xb6ecabad] + (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ec7000+0x5286) [0xb6ecc286] + (EE) 6: /usr/bin/X (0xb750+0x80101) [0xb7580101] + (EE) 7: /usr/bin/X (0xb750+0xac153) [0xb75ac153] + (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] + (EE) 9: /usr/bin/X (0xb750+0x1b2360) [0xb76b2360] + (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74dd400] + (EE) 11: /lib/i386-linux-gnu/libc.so.6 (sigemptyset+0x0) [0xb710e5f0] + (EE) 12: /usr/bin/X (OsBlockSIGIO+0x50) [0xb76b4330] + (EE) 13: /usr/bin/X (OsBlockSignals+0x3f) [0xb76b43bf] + (EE) 14: /usr/bin/X (0xb750+0x18c239) [0xb768c239] + (EE) 15: /usr/bin/X (mieqProcessInputEvents+0x201) [0xb768cd11] + (EE) 16: /usr/bin/X (ProcessInputEvents+0x14) [0xb75801b4] + (EE) 17: /usr/bin/X (0xb750+0x3de3c) [0xb753de3c] + (EE) 18: /usr/bin/X (0xb750+0x2b525) [0xb752b525] + (EE) 19: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb70f8935] + (EE) 20: /usr/bin/X (0xb750+0x2b8f9) [0xb752b8f9] + (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. + [ 10066.903] [mi] EQ processing has resumed after 29 dropped events. + [ 10066.903] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. + + [ 14062.928] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: initialized for relative axes. + [ 14062.928] (WW) evdev: Microsoft Microsoft® Nano Transceiver v2.0: ignoring absolute axes. + + 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: Fri Jun 14 15:03:32 2013 DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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] + 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 (121 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: - Bus 003 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth - 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 + Bus 003 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth + 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= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=61ec7a1e-f124-4468-a7f3-d07d86ce34e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to raring on 2013-05-14 (30 days ago) dmi.bios.date: 06/25/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.8 dmi.board.name: A
[Desktop-packages] [Bug 1190138] Re: Screen locking issue
*** This bug is a duplicate of bug 1185120 *** https://bugs.launchpad.net/bugs/1185120 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1185120, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. Ps. The URL that you gave in the report is not working and leads to a 404 error. Please answer the questions from bug 1185120 so that we can help you. ** This bug has been marked a duplicate of bug 1185120 Crash when trying to access certain websites -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1190138 Title: Screen locking issue Status in “gnome-screensaver” package in Ubuntu: New Bug description: I know that i have sent you a lot of reports about the problems i face these last weeks and i thank all of you people in ubuntu for your efforts to help me in this ,but since this morning i face a new and worst problem my screen gets blocked even in opening pages that so far i never had problem,as this right now the www.zougla.gr , a very popular web site.I COULD OPEN THE alt+f2,i couldn't open launcgpad,unable even when it opened to send you these informations,i had to cut electricity and start again,the connection was reset and even now i am writing to you with a lot of stops ,it is VERY HARD.The scripts that appear during my efforts to write this report to you were: http://www.zougla.gr/_js/jquery-1.7.2.min.js:4 , and , script:resource://gre/components/nsPrompter.js:434 THIS IS DIFFERENT THAN THE BUG BEFORE. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 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 Date: Wed Jun 12 07:42:27 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 3600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-02-12 (119 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to raring on 2013-05-14 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1190138/+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 1190124] Re: Screen locking issue
*** This bug is a duplicate of bug 1185120 *** https://bugs.launchpad.net/bugs/1185120 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1185120, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. Ps. The URL that you gave in the report is not working and leads to a 404 error. Please answer the questions from bug 1185120 so that we can help you. ** This bug has been marked a duplicate of bug 1185120 Crash when trying to access certain websites -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1190124 Title: Screen locking issue Status in “gnome-screensaver” package in Ubuntu: New Bug description: THIS IS NOT A PROBLEM AS THE OTHER BUGS . DASH DOES NOT OPEN OR TAKES LONGTIME TO OPEN,IT IS NOT FOR SOME PAGES AS IT WAS UNTIL YESTERDAY.IT IS A HUGE PROBLEM AND HAPPENS TO ANY PAGE I TRY TO OPEN.THE SCRIPT THAT APPEARED SOMETIME WAS THIS : Script:http://connect.facebook.net/en_US/all.js#appld=306435309453853&xfbml=1:123 WHO ARE THESE PEOPLE???AND WHY??WHAT YOU CAN DO ABOUT IT???WHAT CAN I DO ABOUT IT???IS THE NET AND ALL THESE SCRIPTS FROM YOUTUBE-FACEBOOK-GOOGLE -CHROME OR WHATEVER ELSE ARE A DICTATOR ON WHAT AND WHEN PEOPLE WANT TO READ AND LEARN??IT IS VERY DIFFICULT EVEN TO WRITE THIS MESSAGE TO YOU!!!I HOPE I WILL BE ABLE TO SEND IT TO YOU. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 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 Date: Wed Jun 12 06:33:13 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 3600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-02-12 (119 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to raring on 2013-05-14 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1190124/+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 1190228] Re: Screen locking issue
*** This bug is a duplicate of bug 1185120 *** https://bugs.launchpad.net/bugs/1185120 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1185120, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. Ps. The URL that you gave in the report is not working and leads to a 404 error. Please answer the questions from bug 1185120 so that we can help you. ** This bug has been marked a duplicate of bug 1185120 Crash when trying to access certain websites -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1190228 Title: Screen locking issue Status in “gnome-screensaver” package in Ubuntu: New Bug description: It is unbelievable what these people can do to ubuntu and to my compiuter.It is a different problem ,it is blocked my screen from the opening ,dash does not function properly ,i cannot open with alt+f2,very very difficult to open launchpad The script that appears just now is : script:http://static.reembedit.com/data/scripts/g_2_1ad85b1a2da254b5de703b82b84a0e.js:327 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 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 Date: Wed Jun 12 16:03:07 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 3600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-02-12 (120 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to raring on 2013-05-14 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1190228/+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 1054434] Re: spdif audio cuts off when pausing audio
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in pulseaudio. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs. ** Package changed: ubuntu => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1054434 Title: spdif audio cuts off when pausing audio Status in “pulseaudio” package in Ubuntu: New Bug description: when audio stops playing, it sometimes won't start again when using spdif output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1054434/+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 1189583] Re: Screen locking issue
*** This bug is a duplicate of bug 1185120 *** https://bugs.launchpad.net/bugs/1185120 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1185120, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1185120 Crash when trying to access certain websites -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1189583 Title: Screen locking issue Status in “gnome-screensaver” package in Ubuntu: New Bug description: a lot of scripts are blocking me ALL THE TIME i could have access to alt + f2 was collecting informaions but was not sending them TOTTALY BLACK OUT PLEASE it is every day worst ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 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 Date: Mon Jun 10 20:58:33 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 3600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-02-12 (118 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to raring on 2013-05-14 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1189583/+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 1189587] Re: Screen locking issue
*** This bug is a duplicate of bug 1185120 *** https://bugs.launchpad.net/bugs/1185120 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1185120, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1185120 Crash when trying to access certain websites -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1189587 Title: Screen locking issue Status in “gnome-screensaver” package in Ubuntu: New Bug description: Scripts 1) script:http://cdn.widgetserver.com/syndication/subscriber/Main.js?60750:1 2) script:http://www.youtube.com/embed/l8bQqp9-rus:0 3) script:resource://gre/components/nsPrompter.js:434 and many many more but i had to stop them right away because after i would not be able to report to you at all. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 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 Date: Mon Jun 10 21:17:08 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 3600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-02-12 (118 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to raring on 2013-05-14 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1189587/+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 1187306] Re: Screen locking issue
*** This bug is a duplicate of bug 1185120 *** https://bugs.launchpad.net/bugs/1185120 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1185120, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1185120 Crash when trying to access certain websites -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1187306 Title: Screen locking issue Status in “gnome-screensaver” package in Ubuntu: New Bug description: I am very-very sorry if i have tired you with all these reports,but the problems keep on.The informations you have asked me are these DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.04 DISTRIB_CODENAME=raring DISTRIB_DESCRIPTION="Ubuntu 13.04" gnome-screensaver 3.6.1-0ubuntu3 Sorry for still using the same bug but i am trying to finguer out how to do all these about cancel and the rest you have told me.Ihope next time to be able to correct it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Tue Jun 4 11:40:17 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 3600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-02-12 (111 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to raring on 2013-05-14 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1187306/+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 702451] Re: Tooltips are white on yellow when editing XLS file, making them unreadable
*** This bug is a duplicate of bug 1022640 ***
https://bugs.launchpad.net/bugs/1022640
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1022640, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** Changed in: libreoffice (Ubuntu)
Status: Confirmed => Invalid
** This bug has been marked a duplicate of bug 1022640
[Upstream] VIEWING: Comments are not readable (shown in white over yellow)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to openoffice.org in Ubuntu.
https://bugs.launchpad.net/bugs/702451
Title:
Tooltips are white on yellow when editing XLS file, making them
unreadable
Status in The OpenOffice.org Suite:
Unknown
Status in “libreoffice” package in Ubuntu:
Invalid
Status in “openoffice.org” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: openoffice.org
Papercut incident.
This is exactly the same as this bug
http://qa.openoffice.org/issues/show_bug.cgi?id=57226
Yet it still exists in the Ubuntu version of OpenOffice Calc.
The former bug was not solved due to insufficient information I can
now provide sufficient information. But since this affects Ubuntu due
to the standard Ubuntu theme I am reporting it here.
When you open an OpenOffice spreadsheet or excel document with
comments in the fields the tooltips are white text on a yellow
background making them impossible to read.
This is because the Ambiance theme (which is standard in Lucid) has
white text as standard.
The solution is to add the following code to
.gtkrc-2.0
style "tooltips" {
fg[NORMAL] = { 0.0, 0.0, 0.0 }
text[NORMAL] = { 0.0, 0.0, 0.0 }
}
widget "gtk-tooltips*" style "tooltips"
This needs to be added to the standard install of Ubuntu so that users
do not run into this issue.
I have attached a screen shot so you can see the issue.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: openoffice.org-calc 1:3.2.0-7ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic x86_64
NonfreeKernelModules: fglrx wl
Architecture: amd64
CheckboxSubmission: a3a053998eb48623dd168c329c2dfc37
CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
Date: Thu Jan 13 16:26:18 2011
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
ProcEnviron:
LANG=nl_NL.utf8
SHELL=/bin/bash
SourcePackage: openoffice.org
To manage notifications about this bug go to:
https://bugs.launchpad.net/openoffice/+bug/702451/+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 932229] Re: Unity drag causes video repaint problem.
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: xserver-xorg-driver-nv (Ubuntu) Status: New => Invalid ** Package changed: xserver-xorg-driver-nv (Ubuntu) => nvidia-graphics- drivers (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/932229 Title: Unity drag causes video repaint problem. Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Bug description: I am on a Mac Book Pro with an external monitor attached as well. monitor 0 is the laptop LCD and monitor 1 is the external display. monitor 0 is 1440x900 and monitor 1 is 1920x1200. Everything was working with no changes on my end. The bug seems to have been introduced in the last few days. I am sorry I dont know what was updated to cause the bug. When I move an icon in nautilus, thunderbird, firefox, etc. Basically anything that allows a "drag" state on my monitor 0 (laptop) screen moves up. The bottom of the monitor shows black and the top shows the bottom of the old window. (ie the entire desktop moves up about 450px). I have deleted the monitor.xml and removed and re-installed the nvidia 173 drivers to no effect. I can minimize the effect by enabling "Force full screen redraws (buuffer swap) on repaint" in "Work Arounds" in CCSM. gnome classic and unity 2d work fine. My thoughts are that either CCSM, Nvidia, or a unity update has caused this. I am not a linux pro, so please feel free to instruct me on how to attach whatever info you need. - User reports: here is a video: http://www.youtube.com/watch?v=dMc1t3G7qvA&list=UUuUEwxgNMLveCAcYFS4iOaA&index=1&feature=plcp&hd=1 uname -a: Linux Laptop-Ubuntu 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric lsmod: Module Size Used by rfcomm 47946 8 bnep 18436 2 parport_pc 36962 0 ppdev 17113 0 vesafb 13809 1 nvidia 11713772 44 snd_hda_codec_cirrus 18601 1 snd_hda_intel 33390 5 snd_hda_codec 104931 2 snd_hda_codec_cirrus,snd_hda_intel snd_hwdep 13668 1 snd_hda_codec lib80211_crypt_tkip 17390 0 wl 2568210 0 snd_pcm 96714 3 snd_hda_intel,snd_hda_codec snd_seq_midi 13324 0 snd_rawmidi 30547 1 snd_seq_midi snd_seq_midi_event 14899 1 snd_seq_midi coretemp 13420 0 snd_seq 61896 2 snd_seq_midi,snd_seq_midi_event uvcvideo 72711 0 videodev 92992 1 uvcvideo snd_timer 29991 2 snd_pcm,snd_seq snd_seq_device 14540 3 snd_seq_midi,snd_rawmidi,snd_seq hid_apple 13375 0 binfmt_misc 17540 1 snd 68266 18 snd_hda_codec_cirrus,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device joydev 17693 0 bcm5974 17399 0 btusb 18600 2 bluetooth 166112 23 rfcomm,bnep,btusb i2c_nforce2 13058 0 usbhid 47198 0 hid 95463 2 hid_apple,usbhid lib80211 14991 2 lib80211_crypt_tkip,wl soundcore 12680 1 snd lp 17799 0 applesmc 19554 0 snd_page_alloc 18529 2 snd_hda_intel,snd_pcm input_polldev 13896 1 applesmc v4l2_compat_ioctl32 17083 1 videodev apple_bl 13225 0 parport 46562 3 parport_pc,ppdev,lp usb_storage 57901 0 uas 18027 0 firewire_ohci 40722 0 ahci 26002 2 libahci 26861 1 ahci firewire_core 63626 1 firewire_ohci crc_itu_t 12707 1 firewire_core forcedeth 67563 0 lspci: 00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1) 00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1) 00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b3) 00:03.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1) 00:03.2 SMBus: nVidia Corporation MCP79 SMBus (rev b1) 00:03.3 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1) 00:03.4 RAM memory: nVidia Corporation Device 0a98 (rev b1) 00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1) 00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1) 00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1) 00:06.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1) 00:06.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1) 00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1) 00:09.0 PCI bridge: nVid
[Desktop-packages] [Bug 373738] Re: Fonts becomes ugly after playing 3D games (tremulous)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 373738 and any other logs that are relevant for this particular issue. ** Package changed: xserver-xorg-driver-nv (Ubuntu) => nvidia-graphics- drivers (Ubuntu) ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/373738 Title: Fonts becomes ugly after playing 3D games (tremulous) Status in “nvidia-graphics-drivers” package in Ubuntu: Incomplete Bug description: http://img381.imageshack.us/img381/5484/launchpadmozillafirefox.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/373738/+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 378823] Re: certain windows have their contents transparent
** Package changed: xserver-xorg-driver-nv (Ubuntu) => nvidia-graphics- drivers (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/378823 Title: certain windows have their contents transparent Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: I've had this problem before in intrepid, but it dissapears and returns at will. Now it's back. The symptoms are these: in virtualbox or smplayer, the contents are transparent in the window. smplayer plays the video but nothing is visible because its transparent. In virtualbox only certain things are transparent, for example during the BIOS black background when booting a machine is transparent (but not the text) or certain applications colors (see screenshot). When compiz is turned off, contents inside virtualbox shows. However, the video in smplayer is blank instead (this is with xv output module). I tried setting it to GL2, then the video output would work, but the starting screen is as transparent as with xv.This is with nvidia version 185.18.04, but occured with other versions of the nvidia driver, and Xserver 1.6.0 I tried a restart, and the problem problem is gone for now - windows contents in virtualbox and smplayer are showing normally now. Any suggestions to logs i could look into to get clues on this problem? ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: ubuntu-desktop None [modified: /var/lib/dpkg/info/ubuntu-desktop.list] ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta Uname: Linux 2.6.30-020630rc4-generic i686 UnreportableReason: This is not a genuine Ubuntu package == There is a workaround for this bug, before launching an application enter this command: export XLIB_SKIP_ARGB_VISUALS=1 And execute your application. You can also make a script which would look something like this: #!/bin/bash export XLIB_SKIP_ARGB_VISUALS=1 exec /usr/bin/smplayer.bin "$@" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/378823/+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 641432] Re: Please check your BIOYour CPU appears to be lacking expected security protections. Please check your BIOS settings, or for more information, run: /usr/bin/check-bio
** Package changed: xserver-xorg-driver-nv (Ubuntu) => nvidia-graphics- drivers (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/641432 Title: Please check your BIOYour CPU appears to be lacking expected security protections. Please check your BIOS settings, or for more information, run: /usr/bin/check-bios-nx --verbose Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: After installing nvidia drivers 260.19 from ppa:ubuntu-x-swat/x-updates i get the following message while booting: Your CPU appears to be lacking expected security protections. Please check your BIOS settings, or for more information, run: /usr/bin/check-bios-nx --verbose there someone could help me thank you all I am using ubuntu 10.10 64 bit daily build from 17th September 2010. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/641432/+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 1019495] Re: vino remote desktop server does not function correctly
Thank you for proving the requested information. However, I am setting this bug's status to new as this bug has not been confirmed by someone else. ** Changed in: vino (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1019495 Title: vino remote desktop server does not function correctly Status in “vino” package in Ubuntu: New Bug description: When connecting to a server running vino, some of the keyboard keys do not work and the screen is constantly going black every few seconds unless you are constantly moving the mouse around. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2012-04-28 (403 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MarkForUpload: True NonfreeKernelModules: nvidia Package: vino 3.6.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Tags: raring Uname: Linux 3.8.0-23-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-26 (40 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1019495/+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 997370] Re: Totem does not use the va-api gstreamer backend
I opened the tomtem task because of comment 6. ** Also affects: totem (Ubuntu) Importance: Undecided Status: New ** Changed in: totem (Ubuntu) Status: New => Confirmed -- 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/997370 Title: Totem does not use the va-api gstreamer backend Status in Totem Movie Player: New Status in “gstreamer-vaapi” package in Ubuntu: Confirmed Status in “totem” package in Ubuntu: Confirmed Bug description: installing gstreamer -vaapi from ubuntu repos breaks thumbnail generation in nautilus furthermore acceleration does not work in totem - cpu usage is as high as with software rendering. mplayer-vaapi works perfectly on the same system. gst-launch-0.10 -v filesrc location=~/test.mkv ! matroskademux ! vaapidecode ! vaapisink makes it possible to use vaapi via commandline i did not find a way to use vaapi for mpeg4 part 2 video streams. and i wasnt able to find proper values for gstreamer-properties that fix thumbnails and acceleration in totem. id like to share debug information. just tell me what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/997370/+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
