045e:0745 A wrong hardware detection seems to crash Xorg

Bug #1191334 reported by babis x
58
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-input-evdev (Ubuntu)
Expired
Low
Unassigned

Bug Description

A wrong hardware detection seems to crash Xorg. This report is generated without a wireless mouse, which was connected to the laptop in the duplicate bug 1190987 but the mouse didn't make a difference to the system's stability. Both the xorg.log and the attachment refer to a "Microsoft Microsoft® Nano Transceiver" but the laptop is not connected a a wireless keyboard.

 From Xorg.log:

(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
(EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
(EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
(EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad]
(EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286]
(EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101]
(EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153]
(EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
(EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360]
(EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
(EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424]
(EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b]
(EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1]
(EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6]
(EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422]
(EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b]
(EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25]
(EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441]
(EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd]
(EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa]
(EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083]
(EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb]
(EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3]
(EE) 24: /usr/bin/X (mieqProcessInputEvents+0x1f4) [0xb76abd04]
(EE) 25: /usr/bin/X (ProcessInputEvents+0x14) [0xb759f1b4]
(EE) 26: /usr/bin/X (0xb751f000+0x3dd9d) [0xb755cd9d]
(EE) 27: /usr/bin/X (0xb751f000+0x2b525) [0xb754a525]
(EE) 28: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb7117935]
(EE) 29: /usr/bin/X (0xb751f000+0x2b8f9) [0xb754a8f9]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
[mi] Increasing EQ size to 512 to prevent dropped events.
[ 19459.082] [mi] EQ processing has resumed after 19 dropped events.
[ 19459.082] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[ 20581.964] (II) config/udev: removing device Microsoft Microsoft® Nano Transceiver v2.0
[ 20586.862] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Close
[ 20588.924] (II) UnloadModule: "evdev"

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Uname: Linux 3.8.0-25-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.9.2-0ubuntu8.1
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Jun 15 18:34:14 2013
DistUpgraded: 2013-05-14 19:51:16,898 DEBUG enabling apt cron job
DistroCodename: raring
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RC410M [Mobility Radeon Xpress 200M] [1002:5a62] (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Technology Solutions Device [1734:10fb]
InstallationDate: Installed on 2013-02-12 (123 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
Lsusb:
 Bus 003 Device 003: ID 046d:0a10 Logitech, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: FUJITSU SIEMENS AMILO Li 1718
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: 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

Revision history for this message
babis x (babisxanthopoulos) wrote :
Revision history for this message
papukaija (papukaija) wrote :

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
Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: Xorg freeze
Download full text (5.2 KiB)

Thank you for all these efforts you are doing to solve this problem,but no , i had already put out the mouse's transmitter from the usb plug.Is any possability this microsoft nano transceiver to be a software that they have install into my computer via internet?In the past ,i have been asked to give my ubuntu-password by a authorization window with the keys on it ,because was detected some kind of a problem and when i gave it, i DID NOT feel right about it.The same thing happened today but i didn't do it this time and i pressed cancel.This was not after an ''update software'' which sometimes has happened to ask me for this and i do it.Is this possible or i go throuh a nervous brakedown with all these problems and i have got too suspicius???
THANK YOU for all this and forgive me if i have tired you.
Babis Xanthopoulos

> Date: Sat, 15 Jun 2013 23:27:51 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1191334] Re: Xorg freeze
>
> Thank you for testing without the wireless mouse. However, the attached
> logs still mention "Microsoft MicrosoftR 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 subscribed to the bug
> report.
> 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
> M...

Read more...

Revision history for this message
papukaija (papukaija) wrote : 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.

Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: Xorg freeze
Download full text (5.8 KiB)

YES I HAD RESTERTED MY COMPUTER

Hi for once more,i used BRASERO and i
clicked to be able the copy for windows because i gave to some friends
who are still using the windows but a 30% of them were not opening.

You are a nice person and your help is gift from God.I am sorry if i
have tired you with all these but believe me it is very difficult for me
 all these problems which i face.As far for the wireless mouse i have
told you , i do not use it any more,but still
i have problems.As far for the libre office writer i have reported ,the
 computer -no wireless mouse - went crazy the screen got dark after the
 firefox window got smaller the libre office writer got dark and i was
not able to do anything not even to get ubuntu
help ,not even was reacting at "alt+f2" ,so i had to cut electricity.The
 saving which is done automatique was every single minute or two.As far
for the password ,which i don't give it except for ubuntu update if this
 was ask.these days a smll window pop up
telling me that the system has a problem and keep of asking me to give
the password (this happens 3-4 days now),but i didn't give it.I have
nothing wireless on my computer since you told me about .

> Date: Thu, 20 Jun 2013 13:03:40 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [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 subscribed to the bug
> report.
> 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 be...

Read more...

Revision history for this message
papukaija (papukaija) wrote : 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.

Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: Xorg freeze
Download full text (5.6 KiB)

Hi again,I AM NOT USING a wireless keybord,and i have never used ,my computer it is a laptot,the only wireless i used to use was a mouse but from the time you told me about it (few days ago)i do not use this one too.All the last apports i have sent you about crashing libre office writer and firefox were happening without this mouse,i use the touching pad on the laptop as you have told me to do it.I have told you that i have this feeling that some how (by software that has been placed via internet?or with another way-i do not know their abilities-)wherever work i do somehow they can see it and still a copy of it.Defenetily i do not use any wireless staff,AND ALL THE CRASHES HAVE HAPPENED lately were with only my laptop and nothing else.Is any possability they do all that by distanse on my computer thats why you ditect this wireless keybord???
Even this morning when i turned my laptop on a small window poped up "that a problem exist in my system and if i want to report it",when i press report it,then a biger window poped up "give my password to fix this",but i keep press cansel all the time.Any way the crashes happens without any wireless staff,keybord or mouse.
THANK YOU a lot for all this you do for me and for ubuntu users.I appreciate your efforts and i really talk to all my friends for your morality and your professionalism.
Babis Xanthopoulos

> Date: Thu, 20 Jun 2013 20:32:42 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [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 subscribed to the bug
> report.
> 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:...

Read more...

Revision history for this message
papukaija (papukaija) wrote : 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: updated
Revision history for this message
papukaija (papukaija) wrote :

By the way, I think it safe for you to start using the wireless mouse again as it didn't solve this issue.

summary: - Xorg freeze
+ A wrong hardware detection seems to crash Xorg
papukaija (papukaija)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
Download full text (8.7 KiB)

Hi and first of all i wish you a nice day,
I am very happy every time i see you Mr Papukaja answering to all these hassles i am doing to you in Ubuntu by my reports,but your are my last choise to come out of these blockings they are doing to me.
Yesterday all day long a script by "http:// s.yting ........js:10", sorry but i cannot find where i have write down this script,anyway was making my life very difficult and impossible to work.It appeared more than 20 times making the screen dark or corrupted.And even now at this moment where i write this to you Sir the screen gets dark every 5 seconds and i had again to press alt+f2 (several times until it appears the bug-report)and send you another apport Xorg freezes.Any way i started this answer to send you the informations you have asked me and i had not sent you yet.The windows program of my friend is windows 7 and my firefox is Firefox 22.0 mozilla Firefox for Ubuntu canonical-1.0 (this i got it from firefox help window)and pressing Troubleshooting information i got : User Agent Mozilla/5.0(x11;ubuntu;Linux i686;rv:22.0)Gecko/20100101 Firefox/22.0
During all this writing to you just above screen is getting every 5 sec dark for few seconds gets lighted and dark again It is very hard to rwrite all these,and with difficulty it just opened the launchpad window about the bug report i had to do during this writting.I send you this email hopping that you will receive it,and i will continue in the launchpad to send you some more information about.Please Mr Ppukaja chek this apport i will send in few minutes if all these darked and lighted screen allows me to do.
Thank YOU so much for your kindness and proffecionalism
Babis Xanthopoulos

> Date: Tue, 2 Jul 2013 11:35:51 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [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 subscribed to the bug
> report.
> 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 MicrosoftR Nano Transceiver" but the laptop is not
> connected a a wireless keyboard.
>
>
> From Xorg.log:
>
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
> (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
> (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
> (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
> (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad]
> (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286]
> (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101]
> (EE) ...

Read more...

Revision history for this message
papukaija (papukaija) wrote : 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.

affects: xorg (Ubuntu) → xserver-xorg-input-synaptics (Ubuntu)
papukaija (papukaija)
tags: added: crash
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
papukaija (papukaija)
tags: added: kernel-input
Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg

Hi Mr Papukaijia,
i am sorry that i use your email from yesterday to me , but i have to communicate with you ,so i can get your help for one more time.If this is too much , i will understand it and you do not have to answer back.
As i have told you already , days now every time i turn my laptop on, appears this following message which i send you in the first 2 screen photos.The same keep on today too and as i have told you , i ignore it,because didn't and still doesn't feel right.
Today there is a different issue with the "asking my password"!!
Every time ,since all these problems have started,when i turn on my laptop and before open Firefox,i am checking for any software UPDATES,the same i did it just before.Today when i started the updating ,i was asked to give my password,this was not happening until today even you have ,from Ubuntu i mean,sent my so many secutity updates.
So i did not update because i press cancel to authorization,and i am asking you to TRUST THIS OR NOT.
Isend you these 2 additional screen photos of this,right after the 2 first i told you about it.
Hopping that i can send you all these screen-photos in an email,i am going to try to send you at the end of the above screen photos(2+2) i have already mention to you,ONE more AT THE END, about what happened yesterday,about some files which appeared (has happened once more one or two days ago,i have sent you already the screen photos),and AGAIN i moved them to trush for one more time.

THANK YOU SO MUCH PERSONALLY MR PAPUKAIJIA AND UBUNTU AS WELL.
HOPEFULLY NOT ABUSED OF YOUR KINDNESS AND YOUR PROFFESSIONALISM
BABIS XANTHOPOULOS

Revision history for this message
papukaija (papukaija) wrote : 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)?

Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
Download full text (8.9 KiB)

Hi again Mr Papukijia,yes i used to have similar problems before the new Ubuntu version.
I have to tell you , i always forget this,that my usb plags 2 on the left side of the keybord and 2 more at the right back of the keybord ,ALL of them have problems the last days at least.
I am trying to plug in logitech -with wire-speakers but the light on them does not turn on,i have to change all the usb plugs several times until some time turns on,and at the sound settings does not appear ,the same as the light on them.When finally appears the sound control does not obay easily and a strange sound comes out during the process of higher or lower sound.
The last few days not even the printer does not obay when i plug it in the usb plugs and when gets the order to print finally prints in a very small percents,but very small.It has happened few times the last 2 or 3 days.(this with the printer or the wired speakers was not happening at least to this extent)
Also the switching to the language (en to Gr) still does not obay all the time as i have mention to you.
and finally the touch pad has a lot of problems but still i don't use the wireless mouse since the first time you have told me,just in case!!
What can i say?THANK YOU is not enough for all these efforts you are doing.
Babis Xanthopoulos

> Date: Fri, 5 Jul 2013 10:08:31 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [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 subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1191334
>
> Title:
> A wrong hardware detection seems to crash Xorg
>
> Status in "linux" package in Ubuntu:
> 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 MicrosoftR Nano Transceiver" but the laptop is not
> connected a a wireless keyboard.
>
>
> From Xorg.log:
>
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
> (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
> (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
> (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
> (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0x...

Read more...

Revision history for this message
papukaija (papukaija) wrote : 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.

Revision history for this message
penalvch (penalvch) wrote :

babis x, could you please unplug all USB devices, plug in just the Microsoft Wireless Mouse, and then immediately place the following in a terminal and attach the results:
lsusb -v > lsusb-v.log

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
Download full text (8.2 KiB)

Hi Mr Cr.Penalver
I cannot use my wireless mouse any more ,just because i have put it away long time ago and even i found the mouse it seems that i cannot find any more the small device i had and i was plugged it in to usb plug so this wireless mouse could work -wirelessly-as i used to do.
I am sorry for that ,but my office room is full of books,papers and a lot of drawers and i do not remember were i have place it ...for no loosing it !!!!
What can i do to do the test you are proposing ?
Also when you saying to place " lsusb -v > lsusb-v.log " in a terminal ,what do you mean ?
I have just a laptop ,so do i place this " lsusb -v > lsusb-v.log " in a firefox window or on the black window wich i open by pressing alt+f2 (as i do for ubuntu-bug )
I am really sorry if my questions are not very ...smart ,but my knowlege on the computers is not ,let say politly , very good.

Babis Xanthopoulos

> Date: Sun, 14 Jul 2013 16:43:38 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
>
> babis x, could you please unplug all USB devices, plug in just the Microsoft Wireless Mouse, and then immediately place the following in a terminal and attach the results:
> lsusb -v > lsusb-v.log
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1191334
>
> Title:
> A wrong hardware detection seems to crash Xorg
>
> Status in "linux" package in Ubuntu:
> Incomplete
> Status in "xserver-xorg-input-synaptics" package in Ubuntu:
> New
>
> Bug description:
> A wrong hardware detection seems to crash Xorg. This report is
> generated without a wireless mouse, which was connected to the laptop
> in the duplicate bug 1190987 but the mouse didn't make a difference to
> the system's stability. Both the xorg.log and the attachment refer to
> a "Microsoft MicrosoftR Nano Transceiver" but the laptop is not
> connected a a wireless keyboard.
>
>
> From Xorg.log:
>
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
> (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
> (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
> (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
> (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad]
> (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286]
> (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101]
> (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153]
> (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360]
> (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424]
> (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b]
> (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1]
> (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f...

Read more...

Revision history for this message
penalvch (penalvch) wrote : Re: A wrong hardware detection seems to crash Xorg

Babis, if you are having an issue finding the device, we can close this report until you do.

If you do find the device, regarding the terminal command, one would open a terminal window, and type verbatim:
lsusb -v > lsusb-v.log

and post the file to this report.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: New → Invalid
Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
Download full text (8.3 KiB)

Hi ,finally i found this small device which was necessary to plug it into usb plug so this wireless mouse could work again.
I did write wherever you have told to,and i got these 2 screen photos (i hope this was what you have ask me to do)
Also i would like to ask you about this UBUNTU ONE and this personal cloud which is located on the right top of my screen,IS THIS SAVE??Can you take away from my system or what to i have to do to do it by my self ??Every time i copy paste on libre office writer and i take it out as PDF it seems that there no privacy about , is it just my idea or is it like that??
Any way i send you the 2 photos screen,hopping that this is what you have ask me and i will not plug in this wireless mouse until you tell me to.
I am really thankfull for your efforts
Babis Xanthopoulos

> Date: Sun, 14 Jul 2013 20:21:28 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
>
> Babis, if you are having an issue finding the device, we can close this
> report until you do.
>
> If you do find the device, regarding the terminal command, one would open a terminal window, and type verbatim:
> lsusb -v > lsusb-v.log
>
> and post the file to this report.
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Invalid
>
> ** Changed in: xserver-xorg-input-synaptics (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1191334
>
> Title:
> A wrong hardware detection seems to crash Xorg
>
> Status in "linux" package in Ubuntu:
> Invalid
> Status in "xserver-xorg-input-synaptics" package in Ubuntu:
> Invalid
>
> Bug description:
> A wrong hardware detection seems to crash Xorg. This report is
> generated without a wireless mouse, which was connected to the laptop
> in the duplicate bug 1190987 but the mouse didn't make a difference to
> the system's stability. Both the xorg.log and the attachment refer to
> a "Microsoft MicrosoftR Nano Transceiver" but the laptop is not
> connected a a wireless keyboard.
>
>
> From Xorg.log:
>
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
> (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
> (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
> (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
> (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad]
> (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286]
> (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101]
> (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153]
> (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360]
> (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424]
> (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b]
> (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_writ...

Read more...

papukaija (papukaija)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Invalid → New
Revision history for this message
papukaija (papukaija) wrote : 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
papukaija (papukaija)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: New → Incomplete
Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
Download full text (8.0 KiB)

> Date: Mon, 15 Jul 2013 09:00:23 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1191334] Re: A wrong hardware detection seems to crash Xorg
>
> Could you please unplug all USB devices, plug in just the Microsoft
> Wireless Mouse, and then immediately open the Terminal (hit the Windows
> key in your keyboard and type Terminal) and paste the following command
> there?
>
> lsusb -v > lsusb-v.log
>
> You will then find a called lsusb-v.log in your home folder. Could you
> attach that file to this report please?
>
> You can remove Ubuntu One by following the instructions at
> http://askubuntu.com/q/309122/8973. As for LibreOffice, you can find
> help with your problem in the support forum of your local Ubuntu
> community at http://loco.ubuntu.com/ or asking at http://askubuntu.com ,
> https://answers.launchpad.net/ubuntu or http://ubuntuforums.org. Please
> do not use this bug report for further support requests, as this is not
> the best place for it. Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: Invalid => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1191334
>
> Title:
> A wrong hardware detection seems to crash Xorg
>
> Status in "linux" package in Ubuntu:
> Incomplete
> Status in "xserver-xorg-input-synaptics" package in Ubuntu:
> New
>
> Bug description:
> A wrong hardware detection seems to crash Xorg. This report is
> generated without a wireless mouse, which was connected to the laptop
> in the duplicate bug 1190987 but the mouse didn't make a difference to
> the system's stability. Both the xorg.log and the attachment refer to
> a "Microsoft MicrosoftR Nano Transceiver" but the laptop is not
> connected a a wireless keyboard.
>
>
> From Xorg.log:
>
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
> (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
> (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
> (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
> (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad]
> (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286]
> (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101]
> (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153]
> (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360]
> (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424]
> (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b]
> (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1]
> (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6]
> (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422]
> (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b]
> (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25]
> (EE) 18: /lib/i386-li...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

babis x, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an update is available for your BIOS (1.90). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

summary: - A wrong hardware detection seems to crash Xorg
+ 045e:0745 A wrong hardware detection seems to crash Xorg
tags: added: bios-outdated-v1.9 needs-upstream-testing regression-potential
Revision history for this message
babis x (babisxanthopoulos) wrote : RE: [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to crash Xorg
Download full text (9.7 KiB)

Hi Mr Cristopher .M. Penalver
I did update yesterday ,my BIOS (1.90) as you have told me to do , but i faced later at night problems again with the screen (was getting darker and i was not able to do anything on my computer even alt+f2 was not stable on the screen ,was coming out and disappearing right away before do anything on it,and when ,after a lot of pressing alt+f2 came out and stable ,during the collecting informations got even this window dark and stop collecting any information)
I had to turn off the electricity.
Today in the morning the computer was not connected to ubuntu and i had to turn off the electricity twice and start it again until i got connected.
So i decided to open the terminal as you have told me and put the command "sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date" as you had told me to do in case that i face again after the BIOS (1.90) updated.
I did so and i was ask in the terminal to put my ubuntu password !! I did PUT it ,i press enter after but i do not have anything in my home folder to attach on this ANSWER which i send you right now ,as it had happenned with the other command i had put in the terminal ,"lsusb -v > lsusb-v.log" ,
i think 2 days ago.
Is it ok that i gave my password to the terminal??
Is it normal that i have nothing in my home folder after that , so i can attach it to you ,as i did last time??
What is really happens in my laptop by these people??
What are proposing me to do??
Please i need your help even i know that i do have overtired you about my case.
I WAS LOOKING ONE MORE TIME TO SEE IF ANYTHING HAS BEEN IN MY FOLDERS OUT OF THIS TERMINAL COMMAND AND I FOUND IN MY DOWNLOADS THE
/home/ubuntu/Downloads/FTS_FLASHBIOSUPDATEMSIMS6178MVER19032301_19_23206.EXE
but i cannot attach it says this kind of file so i got a screen photo of it and i attach it to you!!!
  THANK YOU one more time
Babis Xanthopoulos
-------------------------------------------------------------------------------------------------------------------------------------

> Date: Mon, 15 Jul 2013 11:03:06 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to crash Xorg
>
> babis x, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an
> update is available for your BIOS (1.90). If you update to this, does it
> change anything?
>
> If not, could you please both specify what happened, and provide the output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> Thank you for your understanding.
>
> ** Summary changed:
>
> - A wrong hardware detection seems to crash Xorg
> + 045e:0745 A wrong hardware detection seems to crash Xorg
>
> ** Tags added: bios-outdated-v1.9 needs-upstream-testing regression-
> potential
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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 "x...

Read more...

Revision history for this message
papukaija (papukaija) wrote :

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.

Revision history for this message
babis x (babisxanthopoulos) wrote :
Download full text (7.9 KiB)

Hi Mr Papukija,
i am so glad talking to you from ubuntu people again.
Anyway this is what came out today in the terminal ,

ubuntu@ubuntu-AMILO-Li-1718:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for ubuntu:
V1.8
06/25/07
ubuntu@ubuntu-AMILO-Li-1718:~$

Thank you
Babis Xanthopoulos

-------------------------------------------------------------------------------------------------------------------
> Date: Tue, 16 Jul 2013 21:16:48 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [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 subscribed to the bug
> report.
> 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 MicrosoftR Nano Transceiver" but the laptop is not
> connected a a wireless keyboard.
>
>
> From Xorg.log:
>
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
> (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
> (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
> (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
> (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad]
> (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286]
> (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101]
> (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153]
> (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360]
> (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424]
> (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b]
> (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1]
> (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6]
> (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422]
> (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b]
> (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25]
> (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441]
> (EE) 19: /us...

Read more...

Revision history for this message
papukaija (papukaija) wrote :

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.

Revision history for this message
babis x (babisxanthopoulos) wrote :
Download full text (7.6 KiB)

Hi again Mr Papukija,
I got no errors or any other issues during the updating,i felt i difference on the screen for a sec but nothing that i could really see or talk about it.
After the updating ,few hours , similar problems came out on the screen (darker and blocked)as before and as i already have reported.
THANK YOU
Babis Xanthopoulos

> Date: Wed, 17 Jul 2013 09:02:51 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [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 subscribed to the bug
> report.
> 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 MicrosoftR Nano Transceiver" but the laptop is not
> connected a a wireless keyboard.
>
>
> From Xorg.log:
>
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
> (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
> (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
> (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
> (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad]
> (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286]
> (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101]
> (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153]
> (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360]
> (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424]
> (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b]
> (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1]
> (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6]
> (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422]
> (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b]
> (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25]
> (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441]
> (EE) 19: /usr/bin/X (0xb751f000+0x1ba5bd) [0xb76d95bd]
> (EE) 20: /usr/bin/X (LogVMessageVerb+0xda) [0xb76d8eaa]
> (EE) 21: /usr/bin/X (LogVWrite+0x33) [0xb76d9083]
> (EE) 22: /usr/bin/X (VErrorF+0x2b) [0xb76d90bb]
> (EE) 23: /usr/bin/X (ErrorF+0x23) [0xb76d90e3]
> (EE) 24: /usr/bin/X (mi...

Read more...

papukaija (papukaija)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → New
Revision history for this message
papukaija (papukaija) wrote :

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.

Revision history for this message
penalvch (penalvch) wrote :

babis x, when you attempted the BIOS update, were you doing this in Windows?

Revision history for this message
babis x (babisxanthopoulos) wrote :
Download full text (7.9 KiB)

Hi Mr Cristopher,
I can not tell you certainly if i did or didnot uptade the BIOS in windows,i hope not but i am not sure
I do remember that i went to the page "http://support.ts.fujitsu.com/Download/ShowFiles.asp",after on right top of this page in the "search" i put BIOS 1.90 and came out the following page "http://support.ts.fujitsu.com/content/QuicksearchResult.asp?lng=EN&q=BIOS+%281.90%29&btnG.x=18&btnG.y=16 " and i press one - i don't remember which one exactly- of the five first which are showing 1.9
I am sorry if i mixed up the process , but i have not good knowlege in the computers!!!
I am ready to fix any mistakes i probably have done and i feel sorry if i cause troubles to you by my any mistake.
Thank you
Babis Xanthopoulos

> Date: Wed, 17 Jul 2013 23:39:12 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1191334] Re: 045e:0745 A wrong hardware detection seems to crash Xorg
>
> babis x, when you attempted the BIOS update, were you doing this in
> Windows?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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 MicrosoftR Nano Transceiver" but the laptop is not
> connected a a wireless keyboard.
>
>
> From Xorg.log:
>
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76ccf49]
> (EE) 1: /usr/bin/X (mieqEnqueue+0x223) [0xb76ab6b3]
> (EE) 2: /usr/bin/X (0xb751f000+0x54325) [0xb7573325]
> (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75afffb]
> (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x3bad) [0xb6ee9bad]
> (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee6000+0x5286) [0xb6eeb286]
> (EE) 6: /usr/bin/X (0xb751f000+0x80101) [0xb759f101]
> (EE) 7: /usr/bin/X (0xb751f000+0xac153) [0xb75cb153]
> (EE) 8: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 9: /usr/bin/X (0xb751f000+0x1b2360) [0xb76d1360]
> (EE) 10: (vdso) (__kernel_sigreturn+0x0) [0xb74fc400]
> (EE) 11: (vdso) (__kernel_vsyscall+0x10) [0xb74fc424]
> (EE) 12: /lib/i386-linux-gnu/libc.so.6 (__write+0x4b) [0xb71ddd1b]
> (EE) 13: /lib/i386-linux-gnu/libc.so.6 (_IO_file_write+0x41) [0xb716f7e1]
> (EE) 14: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x716c6) [0xb716f6c6]
> (EE) 15: /lib/i386-linux-gnu/libc.so.6 (_IO_file_xsputn+0x182) [0xb7170422]
> (EE) 16: /lib/i386-linux-gnu/libc.so.6 (0xb70fe000+0x49a4b) [0xb7147a4b]
> (EE) 17: /lib/i386-linux-gnu/libc.so.6 (_IO_vfprintf+0x245) [0xb7142b25]
> (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__fprintf_chk+0x81) [0xb7203441]
> (EE) 19...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

babis x, could you please boot into Windows, find the file:
BIOS Windows Flash () - Winflash_AMILO Li1718
1.90
12.11.2007

Update to this, and advise if it changes anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

Revision history for this message
papukaija (papukaija) wrote :

Just to clarify that I don't have this laptop - I only helped triaging this bug. Thanks.

penalvch (penalvch)
no longer affects: linux (Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

babis x, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-input-evdev REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

affects: xserver-xorg-input-synaptics (Ubuntu) → xserver-xorg-input-evdev (Ubuntu)
Changed in xserver-xorg-input-evdev (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-input-evdev (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-input-evdev (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.