[Desktop-packages] [Bug 1228494] Re: pacman crashed with SIGSEGV in __libc_start_main()
*** This bug is a duplicate of bug 1196251 *** https://bugs.launchpad.net/bugs/1196251 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196251, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1228494/+attachment/3832818/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1228494/+attachment/3832820/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1228494/+attachment/3832822/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1228494/+attachment/3832823/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1228494/+attachment/3832824/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1228494/+attachment/3832825/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1228494/+attachment/3832826/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1196251 pacman crashed with SIGSEGV in is_bonus_dot() ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1228494 Title: pacman crashed with SIGSEGV in __libc_start_main() Status in “xscreensaver” package in Ubuntu: New Bug description: scrash from xscreensaver looking at previews ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xscreensaver-data-extra 5.15-3ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.4-0ubuntu1 Architecture: i386 Date: Fri Sep 20 23:09:39 2013 ExecutablePath: /usr/lib/xscreensaver/pacman InstallationDate: Installed on 2012-07-13 (434 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: pacman -root -window-id 0x2A0C21E SegvAnalysis: Segfault happened at: 0x804fbce: cmp0xc60(%eax),%ecx PC (0x0804fbce) ok source 0xc60(%eax) (0x08953000) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: xscreensaver StacktraceTop: ?? () ?? () ?? () ?? () __libc_start_main (main=0x8049c80, argc=4, ubp_av=0xbfe84c64, init=0x8055c20, fini=0x8055c90, rtld_fini=0xb770a5f0 _dl_fini, stack_end=0xbfe84c5c) at libc-start.c:260 Title: pacman crashed with SIGSEGV in __libc_start_main() UpgradeStatus: Upgraded to saucy on 2013-08-26 (25 days ago) UserGroups: adm backup bluetooth cdrom dialout dip disk fax floppy fuse games lp lpadmin netdev plugdev sambashare saned scanner staff sudo tape users voice www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1228494/+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 1069331] Re: [ASRock Z77 Extreme4, Realtek ALC898, Green Headphone Out, Front] Underruns, dropouts or crackling sound
Hi, Actually I can no longer reproduce this issue. When I started experiencing this I started using another soundcard instead of the motherboard one. I upgraded the box to Quantal and I've been trying to reproduce this since then and I've been unable to, hence this must have been fixed at some point, presumably when I upgraded to Quantal. Cheers, Carlos -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1069331 Title: [ASRock Z77 Extreme4, Realtek ALC898, Green Headphone Out, Front] Underruns, dropouts or crackling sound Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: I just upgraded to Quantal but I had the same issue on precise pandolin. Sound randomly stutters. Sometimes it takes 5 minutes to happen sometimes it will happen twice in a 10 second interval. I have version 1.0.25-3ubuntu3 of alsa. I tried the workarounds outlined in https://wiki.ubuntu.com/Audio/PositionReporting hence my modified alsa file. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carlos 2308 F xfce4-volumed carlos 2314 F pulseaudio /dev/snd/pcmC0D0p: carlos 2314 F...m pulseaudio Date: Sun Oct 21 10:15:47 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or crackling sound Title: [To Be Filled By O.E.M., Realtek ALC898, Green Headphone Out, Front] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to quantal on 2012-10-21 (0 days ago) dmi.bios.date: 09/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd09/13/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-10-20T09:41:41.486517 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1069331/+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 1228506] [NEW] Frequent display artifacts, take 2
Public bug reported: Symptoms are the same as in bug https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1221399 For example, see attached photo, replicable 100% just by moving the mouse fast. In bug https://bugs.launchpad.net/xmir/+bug/1218735 I was told to fill a new bug. Note that this Thinkpad has two video cards. I don't know how to tell if Intel or Nvidia is being used. I'm using the default saucy install, no additional drivers. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 21 10:35:28 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f5] NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f5] InstallationDate: Installed on 2013-09-13 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130909) MachineType: LENOVO 2449A22 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=d9f16f85-5511-470f-972f-687054e80e8f ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 2449A22 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET90WW(2.50):bd12/21/2012:svnLENOVO:pn2449A22:pvrThinkPadW530:rvnLENOVO:rn2449A22:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2449A22 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Sep 20 13:38:20 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2.901-2ubuntu4 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu ** Attachment added: mouse cursor artifacts https://bugs.launchpad.net/bugs/1228506/+attachment/3832916/+files/2013-09-21%2010.32.20.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228506 Title: Frequent display artifacts, take 2 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Symptoms are the same as in bug https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1221399 For example, see attached photo, replicable 100% just by moving the mouse fast. In bug https://bugs.launchpad.net/xmir/+bug/1218735 I was told to fill a new bug. Note that this Thinkpad has two video cards. I don't know how to tell if Intel or Nvidia is being used. I'm using the default saucy install, no additional drivers. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 21 10:35:28
[Desktop-packages] [Bug 1184451] Re: Ubuntu 13.10 random screen freeze while Normal OS activites
Update: I downgraded back to 13.04 and the problem vanished, thus confirming that one of the upgraded packages is causing it. However, I am still running the 3.11.0-7-generic kernel, so it's something else. One way to uncover the culprit would be to update to 13.10 incrementally just a few packages at a time and see which one brings back the freezes. I don't have much time these next few days but if somebody could try it, it would save all of us a lot of pain (really can't work like this). I will have a go at it next week. I don't see any other solution unless someone finally finds an error message in a log somewhere. -- 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/1184451 Title: Ubuntu 13.10 random screen freeze while Normal OS activites Status in “xorg-server” package in Ubuntu: Confirmed Bug description: I have recently, re-installed fresh ubuntu 13.10 distribution release. But everything worked fine. until recently i had strange problem of my display screen getting freezed randomly; but no response to either mouse/keyboard. But i want to point it out; it happens randomly and is not specific ? Other day, i had music player playing in background, but screen freezed. but my music was still running. Kindly note, i used multiple monitor setup and same issue of screen freeze also cropped up. I,am not sure, whether it is bug ? thanks for the expertise support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1184451/+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 1227491] Re: [IdeaPad U310, Conexant CX20590, Mic, Internal] No sound at all
Same situation with the update to Kernel 3.11.0-8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1227491 Title: [IdeaPad U310, Conexant CX20590, Mic, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: The sound worked fine under ubuntu 12.10. Alsamixer maxed out, nothing muted. Running the command arecord test.wav produces no sound, no sound in skype. Attempted posted work arounds by editing /etc/modprobe.d/alsa- base.conf with snd-hda-intel model=basic, snd-hda-intel model=default, snd-hda-intel model=azus nothing helped. Audio Card Data output from: lspci -v | grep -A7 -i audio 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Lenovo Device 3977 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at f061 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel output from: cat /proc/asound/card0/codec* Codec: Conexant CX20590 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x14f1506e Subsystem Id: 0x17aa4009 Revision Id: 0x13 No Modem Function Group found Default PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=4, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x10 [Audio Output] wcaps 0xc1d: Stereo Amp-Out R/L Control: name=Headphone Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Headphone Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name=CX20590 Analog, type=Audio, device=0 Amp-Out caps: ofs=0x4a, nsteps=0x4a, stepsize=0x03, mute=1 Amp-Out vals: [0x4a 0x4a] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x11 [Audio Output] wcaps 0xc1d: Stereo Amp-Out R/L Control: name=Speaker Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Speaker Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x4a, nsteps=0x4a, stepsize=0x03, mute=1 Amp-Out vals: [0x4a 0x4a] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x12 [Audio Output] wcaps 0x611: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x13 [Beep Generator Widget] wcaps 0x7c: Mono Amp-Out Control: name=Beep Playback Volume, index=0, device=0 ControlAmp: chs=1, dir=Out, idx=0, ofs=0 Control: name=Beep Playback Switch, index=0, device=0 ControlAmp: chs=1, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x07, nsteps=0x07, stepsize=0x0f, mute=0 Amp-Out vals: [0x07] Node 0x14 [Audio Input] wcaps 0x100d1b: Stereo Amp-In R/L Control: name=Capture Volume, index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name=Capture Switch, index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Device: name=CX20590 Analog, type=Audio, device=0 Amp-In caps: ofs=0x4a, nsteps=0x50, stepsize=0x03, mute=1 Amp-In vals: [0x4b 0x4b] [0x80 0x80] [0x4b 0x4b] [0x80 0x80] Converter: stream=4, channel=0 SDI-Select: 0 PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Connection: 4 0x17 0x18 0x23* 0x24 Node 0x15 [Audio Input] wcaps 0x100d1b: Stereo Amp-In R/L Amp-In caps: ofs=0x4a, nsteps=0x50, stepsize=0x03, mute=1 Amp-In vals: [0x4a 0x4a] [0x4a 0x4a] [0x4a 0x4a] [0x4a 0x4a] Converter: stream=0, channel=0 SDI-Select: 0 PCM: rates
[Desktop-packages] [Bug 1004841] Re: Thunderbird Icon set is broken (ugly, black and white icons)
See http://home.roadrunner.com/~grizzly/images/thunderbird/standard- toolbar-2.6.1-tb.xpi. I contacted him because it seems not comptible with Thunderbird 24 (Dutch). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1004841 Title: Thunderbird Icon set is broken (ugly, black and white icons) Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Since Oneiric the standard theme in thunderbird is broken. In Oneiric (and Precise) some of the coloured Icons were replaced by blackwhite pictograms, but not consistently all. For example the Lightning Icons still remain coloured, as they were before. I don't know why some Icons were replaced by pictograms (is this because of a new GTK-Theme?) , this is only in the Linux version of TB, the Windows version still has the coloured icons. It would have been better if the old standard theme remains untouched, and a new theme would have been created for the new blackwhite pictograms. See attached screenshot for the weird icons. Possible work-around: Download Thunderbird from mozilla, extract a file called omni.ja and overwrite the copy at /usr/lib/thunderbird/. Not sure if this has undesired effects (it may delete all your email, so be careful!), but it works for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1004841/+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 381017]
Still in Thunderbird 24 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in SeaMonkey: all-in-one Internet application suite: Confirmed Status in Mozilla Thunderbird Mail and News: Confirmed Status in “gnome-common” package in Ubuntu: Confirmed Status in “kde-baseapps” package in Ubuntu: Confirmed Status in “seamonkey” package in Ubuntu: Confirmed Status in “thunderbird” package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about fetchUID.voicemail1784. The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/381017/+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 1228510] [NEW] Problems after installing Mir
Public bug reported: morten@ASUS-UBU131064:~$ ps ax | grep unity 1278 tty7 Ssl+ 0:00 /usr/sbin/unity-system-compositor --from-dm-fd 10 --to-dm-fd 13 --vt 7 1510 ?Ssl0:00 /usr/lib/unity/unity-panel-service 2289 ?Sl 0:00 /usr/lib/libunity-webapps/unity-webapps-service 2488 pts/1S+ 0:00 grep --color=auto unity morten@ASUS-UBU131064:~$ ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 21 09:43:14 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: GPU lockup IPEHR: 0x0b160001 EIR: 0x0008 IPEHR: 0x40c1 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8534] InstallationDate: Installed on 2013-08-12 (39 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130812) InterpreterPath: /usr/bin/python3.3 MachineType: ASUS All Series MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-8-generic root=UUID=b318c159-93e3-4c07-87be-015bcaa4cfe1 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: False GPU lockup IPEHR: 0x0b160001 EIR: 0x0008 IPEHR: 0x40c1 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0306 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0306:bd04/15/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87I-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Sep 21 10:07:00 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output XMIR-1 XMIR-3 XMIR-4 xserver.version: 2:1.14.2.901-2ubuntu4 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 false-gpu-hang freeze saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228510 Title: Problems after installing Mir Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: morten@ASUS-UBU131064:~$ ps ax | grep unity 1278 tty7 Ssl+ 0:00 /usr/sbin/unity-system-compositor --from-dm-fd 10 --to-dm-fd 13 --vt 7 1510 ?Ssl0:00 /usr/lib/unity/unity-panel-service 2289 ?Sl 0:00 /usr/lib/libunity-webapps/unity-webapps-service 2488 pts/1S+ 0:00 grep --color=auto unity morten@ASUS-UBU131064:~$ ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for
[Desktop-packages] [Bug 1227491] Re: [IdeaPad U310, Conexant CX20590, Mic, Internal] No sound at all
when internal mic (0x23) is selected, the amp -in value from node 0x17 (mux) must be muted (similar to the value [0x80 0x80] from node 0x18 ) Node 0x14 [Audio Input] wcaps 0x100d1b: Stereo Amp-In R/L Control: name=Capture Volume, index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name=Capture Switch, index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Device: name=CX20590 Analog, type=Audio, device=0 Amp-In caps: ofs=0x4a, nsteps=0x50, stepsize=0x03, mute=1 Amp-In vals: [0x4b 0x4b] [0x80 0x80] [0x4b 0x4b] [0x80 0x80] Converter: stream=4, channel=0 SDI-Select: 0 PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Connection: 4 0x17 0x18 0x23* 0x24 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1227491 Title: [IdeaPad U310, Conexant CX20590, Mic, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: The sound worked fine under ubuntu 12.10. Alsamixer maxed out, nothing muted. Running the command arecord test.wav produces no sound, no sound in skype. Attempted posted work arounds by editing /etc/modprobe.d/alsa- base.conf with snd-hda-intel model=basic, snd-hda-intel model=default, snd-hda-intel model=azus nothing helped. Audio Card Data output from: lspci -v | grep -A7 -i audio 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Lenovo Device 3977 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at f061 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel output from: cat /proc/asound/card0/codec* Codec: Conexant CX20590 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x14f1506e Subsystem Id: 0x17aa4009 Revision Id: 0x13 No Modem Function Group found Default PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=4, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x10 [Audio Output] wcaps 0xc1d: Stereo Amp-Out R/L Control: name=Headphone Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Headphone Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name=CX20590 Analog, type=Audio, device=0 Amp-Out caps: ofs=0x4a, nsteps=0x4a, stepsize=0x03, mute=1 Amp-Out vals: [0x4a 0x4a] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x11 [Audio Output] wcaps 0xc1d: Stereo Amp-Out R/L Control: name=Speaker Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Speaker Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x4a, nsteps=0x4a, stepsize=0x03, mute=1 Amp-Out vals: [0x4a 0x4a] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x12 [Audio Output] wcaps 0x611: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x13 [Beep Generator Widget] wcaps 0x7c: Mono Amp-Out Control: name=Beep Playback Volume, index=0, device=0 ControlAmp: chs=1, dir=Out, idx=0, ofs=0 Control: name=Beep Playback Switch, index=0, device=0 ControlAmp: chs=1, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x07, nsteps=0x07, stepsize=0x0f, mute=0 Amp-Out vals: [0x07] Node 0x14 [Audio Input] wcaps 0x100d1b: Stereo Amp-In R/L Control: name=Capture Volume, index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name=Capture Switch, index=0, device=0
[Desktop-packages] [Bug 1228510] Re: Problems after installing Mir
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228510 Title: Problems after installing Mir Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: morten@ASUS-UBU131064:~$ ps ax | grep unity 1278 tty7 Ssl+ 0:00 /usr/sbin/unity-system-compositor --from-dm-fd 10 --to-dm-fd 13 --vt 7 1510 ?Ssl0:00 /usr/lib/unity/unity-panel-service 2289 ?Sl 0:00 /usr/lib/libunity-webapps/unity-webapps-service 2488 pts/1S+ 0:00 grep --color=auto unity morten@ASUS-UBU131064:~$ ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 21 09:43:14 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: GPU lockup IPEHR: 0x0b160001 EIR: 0x0008 IPEHR: 0x40c1 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8534] InstallationDate: Installed on 2013-08-12 (39 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130812) InterpreterPath: /usr/bin/python3.3 MachineType: ASUS All Series MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-8-generic root=UUID=b318c159-93e3-4c07-87be-015bcaa4cfe1 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: False GPU lockup IPEHR: 0x0b160001 EIR: 0x0008 IPEHR: 0x40c1 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0306 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0306:bd04/15/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87I-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Sep 21 10:07:00 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output XMIR-1 XMIR-3 XMIR-4 xserver.version: 2:1.14.2.901-2ubuntu4 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1228510/+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 1227491] Re: [IdeaPad U310, Conexant CX20590, Mic, Internal] No sound at all
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_conexant.c?id=e4db0952e542090c605fd41d31d761f1b4624f4a -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1227491 Title: [IdeaPad U310, Conexant CX20590, Mic, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: The sound worked fine under ubuntu 12.10. Alsamixer maxed out, nothing muted. Running the command arecord test.wav produces no sound, no sound in skype. Attempted posted work arounds by editing /etc/modprobe.d/alsa- base.conf with snd-hda-intel model=basic, snd-hda-intel model=default, snd-hda-intel model=azus nothing helped. Audio Card Data output from: lspci -v | grep -A7 -i audio 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Lenovo Device 3977 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at f061 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel output from: cat /proc/asound/card0/codec* Codec: Conexant CX20590 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x14f1506e Subsystem Id: 0x17aa4009 Revision Id: 0x13 No Modem Function Group found Default PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=4, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x10 [Audio Output] wcaps 0xc1d: Stereo Amp-Out R/L Control: name=Headphone Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Headphone Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name=CX20590 Analog, type=Audio, device=0 Amp-Out caps: ofs=0x4a, nsteps=0x4a, stepsize=0x03, mute=1 Amp-Out vals: [0x4a 0x4a] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x11 [Audio Output] wcaps 0xc1d: Stereo Amp-Out R/L Control: name=Speaker Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Speaker Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x4a, nsteps=0x4a, stepsize=0x03, mute=1 Amp-Out vals: [0x4a 0x4a] Converter: stream=8, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x12 [Audio Output] wcaps 0x611: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Node 0x13 [Beep Generator Widget] wcaps 0x7c: Mono Amp-Out Control: name=Beep Playback Volume, index=0, device=0 ControlAmp: chs=1, dir=Out, idx=0, ofs=0 Control: name=Beep Playback Switch, index=0, device=0 ControlAmp: chs=1, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x07, nsteps=0x07, stepsize=0x0f, mute=0 Amp-Out vals: [0x07] Node 0x14 [Audio Input] wcaps 0x100d1b: Stereo Amp-In R/L Control: name=Capture Volume, index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name=Capture Switch, index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Device: name=CX20590 Analog, type=Audio, device=0 Amp-In caps: ofs=0x4a, nsteps=0x50, stepsize=0x03, mute=1 Amp-In vals: [0x4b 0x4b] [0x80 0x80] [0x4b 0x4b] [0x80 0x80] Converter: stream=4, channel=0 SDI-Select: 0 PCM: rates [0x160]: 44100 48000 96000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 D3cold EPSS Power: setting=D0, actual=D0 Connection: 4 0x17 0x18 0x23* 0x24 Node 0x15 [Audio Input] wcaps 0x100d1b: Stereo Amp-In R/L Amp-In caps: ofs=0x4a, nsteps=0x50, stepsize=0x03, mute=1 Amp-In vals: [0x4a 0x4a] [0x4a 0x4a] [0x4a 0x4a]
[Desktop-packages] [Bug 1228527] [NEW] install-default-webapps-in-launcher.py crashed with signal 5 in g_object_new_valist()
Public bug reported: Nothing more ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-webapps-common 2.4.16+13.10.20130907-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 21 11:16:08 2013 ExecutablePath: /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py InstallationDate: Installed on 2013-09-14 (6 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130903) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_ES.UTF-8 Signal: 5 SourcePackage: webapps-applications StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: webapps-applications (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webapps-applications in Ubuntu. https://bugs.launchpad.net/bugs/1228527 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_object_new_valist() Status in “webapps-applications” package in Ubuntu: New Bug description: Nothing more ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-webapps-common 2.4.16+13.10.20130907-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 21 11:16:08 2013 ExecutablePath: /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py InstallationDate: Installed on 2013-09-14 (6 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130903) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_ES.UTF-8 Signal: 5 SourcePackage: webapps-applications StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1228527/+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 1228095] Re: Enable default options for non-seat0 seats (no need of systemd-multi-seat-x wrapper)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New = Confirmed -- 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/1228095 Title: Enable default options for non-seat0 seats (no need of systemd-multi- seat-x wrapper) Status in X.Org X server: Confirmed Status in “xorg-server” package in Ubuntu: Confirmed Bug description: This patch contributes to fill the remaining gaps in X.Org which still make systemd-multi-seat-x wrapper needed for some multiseat setups. When -seat option is passed to Xorg with an argument other than seat0, the following options are enabled by default: * Disable VT switching --- no need of setting Option DontVTSwitch in xorg.conf's ServerFlags section. * Enable VT sharing --- no need of passing option -sharevts to Xorg command line. * Enable option GrabDevice for input drivers (e.g. evdev) --- no need of setting this option in xorg.conf's InputClass section. Related upstream bugs: https://bugs.freedesktop.org/show_bug.cgi?id=69477 https://bugs.freedesktop.org/show_bug.cgi?id=69478 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1228095/+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 1228526] Re: install-default-webapps-in-launcher.py crashed with signal 5 in g_object_new_valist()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webapps-applications in Ubuntu. https://bugs.launchpad.net/bugs/1228526 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_object_new_valist() Status in “webapps-applications” package in Ubuntu: New Bug description: Nothing more ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-webapps-common 2.4.16+13.10.20130907-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 21 11:18:59 2013 ExecutablePath: /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py InstallationDate: Installed on 2013-09-14 (6 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130903) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/session-migration/scripts/install-default-webapps-in-launcher.py ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=es_ES.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: webapps-applications StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: install-default-webapps-in-launcher.py crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio bluetooth cdrom dialout dip disk fax floppy fuse games lpadmin plugdev sambashare saned scanner src sudo tape tty users video voice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1228526/+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 1225713] Re: After upgrading from 13.04 to 13.10, user unable to control networking via nm-applet
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1225713 Title: After upgrading from 13.04 to 13.10, user unable to control networking via nm-applet Status in “network-manager” package in Ubuntu: Confirmed Bug description: After upgrading from 13.04 to 13.10, I am no longer able to control networking at all as an average user. My user is unable to change any aspect of the network via nm-applet including starting system connections. IMHO, this is a critical regression, as it prevents users from connecting to any network. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu20 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Sun Sep 15 10:10:54 2013 InstallationDate: Installed on 2013-04-19 (149 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130418) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-09-12 (2 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 157d68e9d-96e8-401d-b896-da55b3da522f 802-3-ethernet1379261386 Sun 15 Sep 2013 10:09:46 AM MDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1225713/+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 1111397] Re: Executable files do not launch in 13.04
We should pay attention to this indeed. This is a radical change for many users acquainted to execute shell scripts or having them written by friends to fix things. Believe me, this happens *all the time*. Changing this behavior without any notice is irresponsible, a very conservative step that disempower users. At the very least, on the first execution of a shell script this way, a dialog should pop-up asking about the user's intention: - do not execute - execute this shell script once and ask again next time - execute any shell script (and/or open preferences) Ideally there could be a per-script configuration that can be tuned this way on first execution. -- 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/397 Title: Executable files do not launch in 13.04 Status in “nautilus” package in Ubuntu: Confirmed Bug description: If I make a text file executable - I can launch it in 12.10, or 12.04 . But in 13.04 it is just opening in gedit . I need to use terminal to launch it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu3 Architecture: amd64 Date: Thu Jan 31 14:05:23 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x550+261+167' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-01-28 (2 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-01-28 (2 days ago) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-01-28T16:57:30.718877 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/397/+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 1222261] Re: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
*** This bug is a duplicate of bug 1041790 *** https://bugs.launchpad.net/bugs/1041790 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/161 Title: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Upgraded to saucy. Removed nvidia card (fan issue) and am now back on Intel and got a couple of lockups today already. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Chipset: sandybridge-gt1 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 Sep 7 17:23:53 2013 DistUpgraded: 2013-09-07 13:04:37,558 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7680] InstallationDate: Installed on 2012-01-02 (614 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120102) InterpreterPath: /usr/bin/python3.3 MachineType: MSI MS-7680 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=3d53ca44-6af4-422d-b1b0-adf30c679a2f ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu3 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UpgradeStatus: Upgraded to saucy on 2013-09-07 (0 days ago) UserGroups: dmi.bios.date: 05/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-E23 (MS-7680) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.8:bd05/23/2011:svnMSI:pnMS-7680:pvr2.0:rvnMSI:rnH61M-E23(MS-7680):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7680 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Sep 7 13:20:51 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 49257 vendor PHL xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/161/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
Hi Marco, 13.9 is supposedly based on an older fglrx driver according to this post: http://devgurus.amd.com/message/132 I will not be filing a bug on Ubuntu as I don't use fglrx-updates package from Ubuntu. Last time I tried those drivers on 12.10, the results were disastrous. -- 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/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade Status in X.org xf86-video-intel: Won't Fix Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: Triaged Status in “fglrx-installer” source package in Quantal: Confirmed Status in “fglrx-installer-updates” source package in Quantal: Triaged Status in “xserver-xorg-video-intel” package in openSUSE: In Progress Bug description: [Impact] * Hybrid systems with ATI/intel GPUs using fglrx get a segmentation fault in X when using 12.10. In stock 12.04.1 these systems were working fine. * This bug represents a severe regression from precise to quantal, since is crashing on startup * The proposed patch updates the driver to version 13.2beta3 of upstream which seems to resolve this issue [Test Case] * Get an hybrid ATI/intel system. Install quantal: The system should boot fine Install the proprietary fglrx package and reboot: The X server crashes on startup [Regression Potential] * This solution does not need any change on the intel driver (as a previous workaround needed). * No regressions have been reported so far using this most recent fglrx upstream, by the people affected by this bug == After installing the latest fglrx-updates package on Ubuntu 12.10 (fglrx-updates_9.000-0ubuntu3_amd64) I have the same issue that was present before AMD fixed switchable graphics on PowerXpress 4.0 cards (such as my HD 6470M coupled with the intel HD Graphics 3000 of my intel Core i5-2430M). The X server has a segmentation fault and the low graphics mode is activated. WORKAROUND: fglrx-installer-13 2:13.101~beta-0ubuntu1~xedgers~quantal1 from: https://launchpad.net/~xorg-edgers/+archive/ppa?field.series_filter=quantal WORKAROUND: Follow carefully the instructions here: https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND As per Nick Andrik, this is a version regression of xserver-xorg- video-intel from 2.20.2 (working and in below mentioned PPA) and 2.20.3. The regression commit is http://cgit.freedesktop.org/xorg/driver/xf86-video- intel/commit/?id=05dcc5f1699ba90fc14c50882e8d4be89bc4a4f9 . Upstream fglrx has published a new version ( 13.1 ) of the driver which seems to solve this issue. No need to revert the commit in the Intel driver any more. ATTENTION: 1. If you choose the integrated GPU (via Catalyst or via amdconfig --px-igpu) and your X server crashes on startup, then your are probably affected by this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220 2. If your system includes an old ATI GPU card (Radeon HD 2x00 3x00 4x00) which is not supported any more by fglrx drivers, then probably you suffer from this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1058040 Subscribe and comment there please. If the X server loads (so you see no low graphics mode window) but you get no menu bars, window decorations, etc, then press Ctrl+Shift+T to open a terminal, write in there: unity --replace and post a comment with the result. The logs from the intial bug report follow: Here is the Xorg log: [20.924] X.Org X Server 1.13.0 Release Date: 2012-09-05 [20.924] X Protocol Version 11, Revision 0 [20.924] Build Operating System: Linux 3.2.0-30-generic x86_64 Ubuntu [20.924] Current Operating System: Linux marco-HP-Pavilion-g6-Notebook-PC 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 [20.924] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=5374f779-2ae8-4842-a390-e21317364c6c ro quiet splash vt.handoff=7 [20.924] Build Date: 08 October 2012 03:34:01PM [20.924] xorg-server 2:1.13.0-0ubuntu6 (For technical support please see http://www.ubuntu.com/support) [20.924] Current version of pixman: 0.26.0 [20.924] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [20.924] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [20.924] (==) Log file: /var/log/Xorg.0.log, Time: Fri Oct 19 02:42:21 2012 [20.924] (==) Using config file: /etc/X11/xorg.conf [20.924] (==) Using system config directory /usr/share/X11/xorg.conf.d [
[Desktop-packages] [Bug 1228548] [NEW] gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage()
*** This bug is a security vulnerability *** Public security bug reported: Had my Nexus attached - running Ubuntu Touch - Unmounted the phone and then app crashed ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sat Sep 21 20:32:20 2013 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2013-03-22 (183 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/9 SegvAnalysis: Segfault happened at: 0x7f823478: (bad) PC (0x7f823478) in non-executable VMA region: 0x7f823400-0x7f823403 rw-p None Stack memory exhausted (SP below stack segment) SegvReason: executing writable VMA None Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 LIBMTP_Get_Storage () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage() UpgradeStatus: Upgraded to saucy on 2013-08-28 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo vboxusers ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1228548 Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage() Status in “gvfs” package in Ubuntu: New Bug description: Had my Nexus attached - running Ubuntu Touch - Unmounted the phone and then app crashed ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sat Sep 21 20:32:20 2013 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2013-03-22 (183 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/9 SegvAnalysis: Segfault happened at: 0x7f823478:(bad) PC (0x7f823478) in non-executable VMA region: 0x7f823400-0x7f823403 rw-p None Stack memory exhausted (SP below stack segment) SegvReason: executing writable VMA None Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 LIBMTP_Get_Storage () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage() UpgradeStatus: Upgraded to saucy on 2013-08-28 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1228548/+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 1228546] Re: software-center crashed with signal 5 in _XReadEvents()
*** This bug is a duplicate of bug 1196625 *** https://bugs.launchpad.net/bugs/1196625 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196625, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1228546/+attachment/3833102/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1228546/+attachment/3833104/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1228546/+attachment/3833105/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1228546/+attachment/3833106/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1228546/+attachment/3833107/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1228546/+attachment/3833108/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1228546/+attachment/3833109/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1196625 software-center crashed with signal 5 in _XReadEvents() ** Tags removed: need-i386-retrace -- 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/1228546 Title: software-center crashed with signal 5 in _XReadEvents() Status in “software-center” package in Ubuntu: New Bug description: tried to install teamviewer by double clicking the *.deb - Software centre creashed once launched ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.09-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.3-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Sat Sep 21 11:25:31 2013 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-07-27 (55 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center /home/username/Downloads/teamviewer_linux.deb ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: software-center StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReadEvents () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: software-center crashed with signal 5 in _XReadEvents() UpgradeStatus: Upgraded to saucy on 2013-08-20 (31 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1228546/+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 1228546] [NEW] software-center crashed with signal 5 in _XReadEvents()
*** This bug is a duplicate of bug 1196625 *** https://bugs.launchpad.net/bugs/1196625 Public bug reported: tried to install teamviewer by double clicking the *.deb - Software centre creashed once launched ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.09-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.3-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Sat Sep 21 11:25:31 2013 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-07-27 (55 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center /home/username/Downloads/teamviewer_linux.deb ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: software-center StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReadEvents () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: software-center crashed with signal 5 in _XReadEvents() UpgradeStatus: Upgraded to saucy on 2013-08-20 (31 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 saucy third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1228546 Title: software-center crashed with signal 5 in _XReadEvents() Status in “software-center” package in Ubuntu: New Bug description: tried to install teamviewer by double clicking the *.deb - Software centre creashed once launched ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.09-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.3-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Sat Sep 21 11:25:31 2013 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-07-27 (55 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center /home/username/Downloads/teamviewer_linux.deb ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: software-center StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReadEvents () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: software-center crashed with signal 5 in _XReadEvents() UpgradeStatus: Upgraded to saucy on 2013-08-20 (31 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1228546/+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 1227173] Re: On every startup Onboard asks for enabling accessibility
I have made another important observation: If I run gsettings set org.gnome.settings-daemon.plugins.a11y-settings active false the dialog asking to activate accessibility goes away, but the login very often fails, I have to enter my password in lightdm 5 or 6 times until succeeding a login. After running gsettings set org.gnome.settings-daemon.plugins.a11y-settings active true the logins succed again. Failed logins give an .xsession-errors like this Script for cjkv started at run_im. Script for default started at run_im. init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped init: gnome-settings-daemon main process (5110) terminated with status 1 init: gnome-session main process (5128) terminated with status 1 init: unity-panel-service main process (5137) terminated with status 1 init: logrotate pre-start process (5055) killed by TERM signal Succeeded logins give the following .xsession-errors: Script for cjkv started at run_im. Script for default started at run_im. init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1227173 Title: On every startup Onboard asks for enabling accessibility Status in “gnome-control-center” package in Ubuntu: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “onboard” package in Ubuntu: Incomplete Bug description: I have a Lenovo Thinkpad Twist convertible ultrabook. The tablet mode (touchscreen-only operation, keyboard folded away) gets continuously working better. I use Onboard as on-screen keyboard to do text input on my convertible in tablet mode (see bug 1210823). This works very well but there is an awkwardness on startup. Every time when Onboard is started (in my case by the laptop/tablet mode switcher script) a dialog pops up which reads: -- Enabling auto-show requires Gnome Accessibility Onboard can turn on accessibility now, however it is recommended that you log out and back in for it to reach its full potential. Enable accessibility now? -- It gives me a No and a Yes button to answer. I click Yes to get the keyboard. Then the keyboard works correctly for the rest of the session (I have set it to show when I am in a text field and to hide otherwise). It does not ask when I switch to laptop mode (which kills Onboard) and back to tablet mode (restarts Onboard), but If I log out and log in again, it asks again. So it seems that it is not saved to be kept over sessions that I have answered Yes to activate accessibility mode. So I am not sure whether really Onboard is the culprit or perhaps gnome-control-center or gnome-settings-daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+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 1210789] Re: icons for mail folders not correct, unread mail does not make folder name bold
Received a new Tbird yesterday, that seems to have solved the issue for me (Thunderbird 1:24.0+build1-0ubuntu0.12.04.1) cheers Tom ** Attachment added: special folder icons correct and inbox bold when unread mails present https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1210789/+attachment/3833144/+files/Screenshot%20from%202013-09-21%2013%3A06%3A39.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1210789 Title: icons for mail folders not correct, unread mail does not make folder name bold Status in “thunderbird” package in Ubuntu: Confirmed Bug description: hi, Running Ubuntu 12.04 amd64. I've just upgraded to T'bird 23.0 from the MozillaTeam PPA in order to have Lightning 2.5b2. I notice several regressions in the GUI: - special maps (drafts, sent, spam, deleted) have lost their special icon, they are just plain brown maps like all others - unread mails do not make the map's name come up *bold* If you have any questions, just ask. cheers Tom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1210789/+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 1228567] [NEW] at-spi2 daemon error messages in .xsession-errors
Public bug reported: Sometimes I get the following messages in .xsession-errors init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped I use a Lenovo Thinkpad Twist convertible with touch screen, using Onboard in tablet mode. Can perhaps have a relation with bug 1227173. ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors Status in “at-spi2-core” package in Ubuntu: New Bug description: Sometimes I get the following messages in .xsession-errors init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped I use a Lenovo Thinkpad Twist convertible with touch screen, using Onboard in tablet mode. Can perhaps have a relation with bug 1227173. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+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 1227173] Re: On every startup Onboard asks for enabling accessibility
For the at-spi2 messages I have also reported bug 1228567. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1227173 Title: On every startup Onboard asks for enabling accessibility Status in “gnome-control-center” package in Ubuntu: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “onboard” package in Ubuntu: Incomplete Bug description: I have a Lenovo Thinkpad Twist convertible ultrabook. The tablet mode (touchscreen-only operation, keyboard folded away) gets continuously working better. I use Onboard as on-screen keyboard to do text input on my convertible in tablet mode (see bug 1210823). This works very well but there is an awkwardness on startup. Every time when Onboard is started (in my case by the laptop/tablet mode switcher script) a dialog pops up which reads: -- Enabling auto-show requires Gnome Accessibility Onboard can turn on accessibility now, however it is recommended that you log out and back in for it to reach its full potential. Enable accessibility now? -- It gives me a No and a Yes button to answer. I click Yes to get the keyboard. Then the keyboard works correctly for the rest of the session (I have set it to show when I am in a text field and to hide otherwise). It does not ask when I switch to laptop mode (which kills Onboard) and back to tablet mode (restarts Onboard), but If I log out and log in again, it asks again. So it seems that it is not saved to be kept over sessions that I have answered Yes to activate accessibility mode. So I am not sure whether really Onboard is the culprit or perhaps gnome-control-center or gnome-settings-daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1227173/+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 1062077] Re: [HP TouchSmart tm2-2010eg] Linux hangs with: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
** Description changed: - Symptom: Linux isn't displaying changes after switching to tty1 and back - to unity - - Steps to reproduce: + Symptom: Linux isn't displaying changes after switching to tty1 and back to Unity. Steps to reproduce: 1. Starting up to Unity 2. Switch to tty1 (Strg + Alt + F1) 3. Switching back to Unity - or: - Resuming the system from suspend leads to the same isssue.This method isn't as reliable as the method stated above + or resuming the system from suspend leads to the same isssue.This method + isn't as reliable as the method stated above. - What happens: - The screen freezes. Magic Keys [Alt + Print + S/U/B] are working thou (so linux-kernel is responding?!) I can't switch to tty1 either. The system becomes responding again after ~2min. Switching VTs is possible afterwards but leads to the same bug again. + What happens: The screen freezes. Magic Keys [Alt + Print + S/U/B] are + working thou (so linux-kernel is responding?!) I can't switch to tty1 + either. The system becomes responding again after ~2min. Switching VTs + is possible afterwards but leads to the same bug again. - What is expected: - Showing up a responding Unity. + What is expected: Showing up a responding Unity. - Interesting Sitenote: - My radeon is switched off using: echoOFF/sys/kernel/debug/vgaswitcheroo/switch - By turning ON the graphiccard the above stated problem doesn't appear. + WORKAROUND: My radeon is switched off using: + echoOFF/sys/kernel/debug/vgaswitcheroo/switch + By turning ON the graphics card the above stated problem doesn't appear. - A short extract of kern.log (full one is attached): - Oct 5 09:06:06 Octavian-Notebook kernel: [ 186.691685] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:06 Octavian-Notebook kernel: [ 186.691700] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, WS 0, PS 0) @ 0xC9AA - Oct 5 09:06:11 Octavian-Notebook kernel: [ 191.692930] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:11 Octavian-Notebook kernel: [ 191.692949] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, WS 0, PS 0) @ 0xC9AA - Oct 5 09:06:11 Octavian-Notebook kernel: [ 191.692960] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C040 (len 861, WS 0, PS 0) @ 0xC09D - Oct 5 09:06:16 Octavian-Notebook kernel: [ 197.021996] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:16 Octavian-Notebook kernel: [ 197.022011] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE0C (len 72, WS 0, PS 0) @ 0xCE3B - Oct 5 09:06:22 Octavian-Notebook kernel: [ 202.223115] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:22 Octavian-Notebook kernel: [ 202.223134] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, WS 0, PS 0) @ 0xC9AA - Oct 5 09:06:27 Octavian-Notebook kernel: [ 207.424244] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:27 Octavian-Notebook kernel: [ 207.424259] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, WS 0, PS 0) @ 0xC9AA - Oct 5 09:06:32 Octavian-Notebook kernel: [ 212.625368] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:32 Octavian-Notebook kernel: [ 212.625387] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, WS 0, PS 0) @ 0xC9AA - Oct 5 09:06:37 Octavian-Notebook kernel: [ 217.826526] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:37 Octavian-Notebook kernel: [ 217.826545] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, WS 0, PS 0) @ 0xC9AA - Oct 5 09:06:42 Octavian-Notebook kernel: [ 223.027631] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:42 Octavian-Notebook kernel: [ 223.027650] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, WS 0, PS 0) @ 0xC9AA - Oct 5 09:06:48 Octavian-Notebook kernel: [ 228.228756] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:48 Octavian-Notebook kernel: [ 228.228772] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C98E (len 62, WS 0, PS 0) @ 0xC9AA - Oct 5 09:06:51 Octavian-Notebook kernel: [ 231.957328] SysRq : This sysrq operation is disabled. - Oct 5 09:06:52 Octavian-Notebook kernel: [ 232.739445] SysRq : This sysrq operation is disabled. - Oct 5 09:06:52 Octavian-Notebook kernel: [ 233.139471] SysRq : This sysrq operation is disabled. - Oct 5 09:06:53 Octavian-Notebook kernel: [ 233.429887] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting - Oct 5 09:06:53 Octavian-Notebook
[Desktop-packages] [Bug 1228572] [NEW] [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a000002 IPEHR: 0x01000000
Public bug reported: After the lockup, the clock in the panel is missing ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Chipset: sandybridge-m-gt1 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 Sep 21 11:45:06 2013 DistUpgraded: 2013-09-14 00:40:14,319 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: No GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:14c7] InstallationDate: Installed on 2013-09-13 (8 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. X55A MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-8-generic root=UUID=a42aba1e-7946-4997-9dfb-2edbd8d2e204 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 UpgradeStatus: Upgraded to saucy on 2013-09-13 (7 days ago) UserGroups: dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55A.413 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55A.413:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnX55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Sep 21 13:08:56 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12874 vendor SEC xserver.version: 2:1.14.2.901-2ubuntu4 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 freeze saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228572 Title: [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: After the lockup, the clock in the panel is missing ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Chipset: sandybridge-m-gt1 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 Sep 21 11:45:06 2013 DistUpgraded: 2013-09-14 00:40:14,319 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: No GpuHangFrequency: Very infrequently GraphicsCard:
[Desktop-packages] [Bug 1228570] Re: Login often fails
I have now tried 5 subsequent logins with XBMC as desktop, they all succeeded, so it is very probable that it is a problem of Unity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228570 Title: Login often fails Status in “lightdm” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: I am using the Lenovo Thinkpad Twist with Saucy and the standard Unity desktop. Often when I log in, after entering the password the screen gets black and within one second I am back in LightDM. I have to enter my password three or four times until getting a successful login. Logging in right after reboot works more often. Logging into the guest account always works. There are no messages in .xsession-errors. /var/log/syslog adds the following lines after pressing Enter after entering the password until LightDM re-appearing: First failed attempt: Sep 21 13:28:05 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:28:05 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:28:05 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:28:05 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:28:05 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.139': no such name Sep 21 13:28:05 till-twist acpid: client 7242[0:0] has disconnected Sep 21 13:28:05 till-twist acpid: client connected from 7493[0:0] Sep 21 13:28:05 till-twist acpid: 1 client rule loaded Sep 21 13:28:05 till-twist dbus[574]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Sep 21 13:28:05 till-twist dbus[574]: [system] Successfully activated service 'org.freedesktop.systemd1' Sep 21 13:28:06 till-twist colord: Device added: xrandr-LVDS1 Sep 21 13:28:06 till-twist colord: Profile added: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:28:06 till-twist colord: Automatic metadata add icc-f5a7781aa544aba4d0654c67690ec8d4 to xrandr-LVDS1 Sep 21 13:28:06 till-twist colord: Profile added: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:28:06 till-twist colord: Profile added: icc-42cf0f25cbd914f2177438317b72f222 Second failed attempt: Sep 21 13:34:42 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:34:42 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:34:42 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:34:42 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:34:42 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.160': no such name Sep 21 13:34:42 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.160': no such name Sep 21 13:34:43 till-twist acpid: client 7493[0:0] has disconnected Sep 21 13:34:43 till-twist acpid: client connected from 7737[0:0] Sep 21 13:34:43 till-twist acpid: 1 client rule loaded Sep 21 13:34:43 till-twist dbus[574]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Sep 21 13:34:43 till-twist dbus[574]: [system] Successfully activated service 'org.freedesktop.systemd1' Sep 21 13:34:43 till-twist colord: Device added: xrandr-LVDS1 Sep 21 13:34:43 till-twist colord: Profile added: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:34:43 till-twist colord: Automatic metadata add icc-f5a7781aa544aba4d0654c67690ec8d4 to xrandr-LVDS1 Sep 21 13:34:43 till-twist colord: Profile added: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:34:43 till-twist colord: Profile added: icc-42cf0f25cbd914f2177438317b72f222 Third failed attempt: Sep 21 13:34:53 till-twist whoopsie[1969]: online Sep 21 13:35:43 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:35:43 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:35:43 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:35:43 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:35:43 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner:
[Desktop-packages] [Bug 1062077] Re: [HP TouchSmart tm2-2010eg] Linux hangs with: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Simon K, would disabling the discrete graphics card in BIOS be an additional available method? As well, given the issue appears to be identified with vgaswitcheroo not quite being free of causing collatoral damage, and you have what appears to be an acceptable alternative to disabling your graphics card, would you like to pursue a fix for this, or would disabling the garphics card via upstart-job be considered a solution? ** Tags removed: regression-potential ** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1062077 Title: [HP TouchSmart tm2-2010eg] Linux hangs with: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: Symptom: Linux isn't displaying changes after switching to tty1 and back to Unity. Steps to reproduce: 1. Starting up to Unity 2. Switch to tty1 (Strg + Alt + F1) 3. Switching back to Unity or resuming the system from suspend leads to the same isssue.This method isn't as reliable as the method stated above. What happens: The screen freezes. Magic Keys [Alt + Print + S/U/B] are working thou (so linux-kernel is responding?!) I can't switch to tty1 either. The system becomes responding again after ~2min. Switching VTs is possible afterwards but leads to the same bug again. What is expected: Showing up a responding Unity. WORKAROUND: My radeon is switched off using: echoOFF/sys/kernel/debug/vgaswitcheroo/switch By turning ON the graphics card the above stated problem doesn't appear. A kern.log: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062077/+attachment/3374796/+files/kern.log ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.26 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: octavian 2405 F pulseaudio Date: Fri Oct 5 09:07:44 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=2e9be59f-1f91-4313-bfac-3babbffc5c00 ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.94 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-09-14 (20 days ago) dmi.bios.date: 07/30/2010 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1486 dmi.board.vendor: Hewlett-Packard dmi.board.version: 83.1A dmi.chassis.asset.tag: CNU0250216 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP TouchSmart tm2 Notebook PC dmi.product.version: 048920252A2000122 dmi.sys.vendor: Hewlett-Packard --- .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DistUpgraded: 2013-02-07 06:43:51,807 DEBUG enabling apt cron job DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.22, 3.5.0-23-generic, x86_64: installed virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1486] Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] [1002:68e0] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-12-04 (64 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC MarkForUpload: True Package: xorg 1:7.7+1ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-4-generic root=UUID=b78f0013-4cb2-4ad2-9c13-9d884b091f3a ro ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6 Tags: raring running-unity
[Desktop-packages] [Bug 1228572] Re: [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a000002 IPEHR: 0x01000000
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228572 Title: [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: After the lockup, the clock in the panel is missing ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Chipset: sandybridge-m-gt1 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 Sep 21 11:45:06 2013 DistUpgraded: 2013-09-14 00:40:14,319 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: No GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:14c7] InstallationDate: Installed on 2013-09-13 (8 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. X55A MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-8-generic root=UUID=a42aba1e-7946-4997-9dfb-2edbd8d2e204 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt1] GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 UpgradeStatus: Upgraded to saucy on 2013-09-13 (7 days ago) UserGroups: dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55A.413 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55A.413:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnX55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Sep 21 13:08:56 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12874 vendor SEC xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1228572/+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 1226618] Re: Thunderbird or ubuntu-bug can't open a browser page
I'm able to open links from Thunderbird 24 (there was a recent update) correctly into Chromium 30. Just out of curiosity, can you run update- alternatives --get-selections | chromium-browser in a Terminal window? It should return gnome-www-browser and x-www-browser, and the paths should be the same. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1226618 Title: Thunderbird or ubuntu-bug can't open a browser page Status in “chromium-browser” package in Ubuntu: New Bug description: This seems to be a recent regression after the update to chromium 29. I can't have thunderbird open links with chromium.. thunderbird=17.0.8+build1-0ubuntu1 chromium-browser=29.0.1547.65-0ubuntu3 (I think that's chad test build still) In System Default Apps, chromium is set as the default browser and appears as New tab with the chromium logo, if that has any importance. Incidentally, while trying to file the bug, ubuntu-bug could just open a window but not have it open on the launchpad bug link. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1226618/+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 1228570] [NEW] Login often fails
Public bug reported: I am using the Lenovo Thinkpad Twist with Saucy and the standard Unity desktop. Often when I log in, after entering the password the screen gets black and within one second I am back in LightDM. I have to enter my password three or four times until getting a successful login. Logging in right after reboot works more often. Logging into the guest account always works. There are no messages in .xsession-errors. /var/log/syslog adds the following lines after pressing Enter after entering the password until LightDM re-appearing: First failed attempt: Sep 21 13:28:05 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:28:05 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:28:05 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:28:05 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:28:05 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.139': no such name Sep 21 13:28:05 till-twist acpid: client 7242[0:0] has disconnected Sep 21 13:28:05 till-twist acpid: client connected from 7493[0:0] Sep 21 13:28:05 till-twist acpid: 1 client rule loaded Sep 21 13:28:05 till-twist dbus[574]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Sep 21 13:28:05 till-twist dbus[574]: [system] Successfully activated service 'org.freedesktop.systemd1' Sep 21 13:28:06 till-twist colord: Device added: xrandr-LVDS1 Sep 21 13:28:06 till-twist colord: Profile added: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:28:06 till-twist colord: Automatic metadata add icc-f5a7781aa544aba4d0654c67690ec8d4 to xrandr-LVDS1 Sep 21 13:28:06 till-twist colord: Profile added: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:28:06 till-twist colord: Profile added: icc-42cf0f25cbd914f2177438317b72f222 Second failed attempt: Sep 21 13:34:42 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:34:42 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:34:42 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:34:42 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:34:42 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.160': no such name Sep 21 13:34:42 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.160': no such name Sep 21 13:34:43 till-twist acpid: client 7493[0:0] has disconnected Sep 21 13:34:43 till-twist acpid: client connected from 7737[0:0] Sep 21 13:34:43 till-twist acpid: 1 client rule loaded Sep 21 13:34:43 till-twist dbus[574]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Sep 21 13:34:43 till-twist dbus[574]: [system] Successfully activated service 'org.freedesktop.systemd1' Sep 21 13:34:43 till-twist colord: Device added: xrandr-LVDS1 Sep 21 13:34:43 till-twist colord: Profile added: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:34:43 till-twist colord: Automatic metadata add icc-f5a7781aa544aba4d0654c67690ec8d4 to xrandr-LVDS1 Sep 21 13:34:43 till-twist colord: Profile added: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:34:43 till-twist colord: Profile added: icc-42cf0f25cbd914f2177438317b72f222 Third failed attempt: Sep 21 13:34:53 till-twist whoopsie[1969]: online Sep 21 13:35:43 till-twist colord: device removed: xrandr-LVDS1 Sep 21 13:35:43 till-twist colord: Profile removed: icc-212ca362d5002958378e8fefb0ad7943 Sep 21 13:35:43 till-twist colord: Profile removed: icc-f5a7781aa544aba4d0654c67690ec8d4 Sep 21 13:35:43 till-twist colord: Profile removed: icc-42cf0f25cbd914f2177438317b72f222 Sep 21 13:35:43 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.175': no such name Sep 21 13:35:43 till-twist NetworkManager[1705]: warn error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.175': no such name Sep 21 13:35:44 till-twist acpid: client 7737[0:0] has disconnected Sep 21 13:35:44 till-twist acpid: client connected from
[Desktop-packages] [Bug 1207757] Re: Scroll momentum is not being damped when a pane reaches its limits
The opposite happens if you fling down. ** Changed in: chromium-browser (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1207757 Title: Scroll momentum is not being damped when a pane reaches its limits Status in “chromium-browser” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: This manifests most in Chrome for me. I fling-scroll a page to the top, it reaches the top, then I press Ctrl and the page will zoom in suddenly. I think the fling momentum is not being damped when the page reaches the top. I would expect the momentum to be damped in the same way as the page is when it reaches the top. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130729-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Aug 2 14:30:35 2013 InstallationDate: Installed on 2013-07-24 (8 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-07-24 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1207757/+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 1207757] Re: Scroll momentum is not being damped when a pane reaches its limits
Just to check, what version of chromium-browser do you have? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1207757 Title: Scroll momentum is not being damped when a pane reaches its limits Status in “chromium-browser” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: This manifests most in Chrome for me. I fling-scroll a page to the top, it reaches the top, then I press Ctrl and the page will zoom in suddenly. I think the fling momentum is not being damped when the page reaches the top. I would expect the momentum to be damped in the same way as the page is when it reaches the top. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130729-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Aug 2 14:30:35 2013 InstallationDate: Installed on 2013-07-24 (8 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-07-24 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1207757/+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 1207757] Re: Scroll momentum is not being damped when a pane reaches its limits
** Bug watch added: code.google.com/p/chromium/issues #296082 http://code.google.com/p/chromium/issues/detail?id=296082 ** Also affects: chromium-browser via http://code.google.com/p/chromium/issues/detail?id=296082 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1207757 Title: Scroll momentum is not being damped when a pane reaches its limits Status in Chromium Browser: Unknown Status in “chromium-browser” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: This manifests most in Chrome for me. I fling-scroll a page to the top, it reaches the top, then I press Ctrl and the page will zoom in suddenly. I think the fling momentum is not being damped when the page reaches the top. I would expect the momentum to be damped in the same way as the page is when it reaches the top. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130729-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Aug 2 14:30:35 2013 InstallationDate: Installed on 2013-07-24 (8 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-07-24 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1207757/+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 1228587] [NEW] When selecting two cell and draggin them X locks up.
Public bug reported: Steps to reproduce : 1. Start libreoffice-calc 2. Select 2 cells 3. Try to draw the cells to another location Actual result: The mouse cursor locks and nothing more happenens. Changing back and forth between tty1 and X a couple of times solves the lockup. Expected result : I would expect the cells to be moved to the new location. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Package changed: apport (Ubuntu) = libreoffice (Ubuntu) -- 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/1228587 Title: When selecting two cell and draggin them X locks up. Status in “libreoffice” package in Ubuntu: New Bug description: Steps to reproduce : 1. Start libreoffice-calc 2. Select 2 cells 3. Try to draw the cells to another location Actual result: The mouse cursor locks and nothing more happenens. Changing back and forth between tty1 and X a couple of times solves the lockup. Expected result : I would expect the cells to be moved to the new location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1228587/+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 1228597] Re: software-center crashed with signal 5 in _XReadEvents()
*** This bug is a duplicate of bug 1196625 *** https://bugs.launchpad.net/bugs/1196625 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196625, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1228597/+attachment/3833372/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1228597/+attachment/3833374/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1228597/+attachment/3833376/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1228597/+attachment/3833377/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1228597/+attachment/3833378/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1228597/+attachment/3833379/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1228597/+attachment/3833380/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1196625 software-center crashed with signal 5 in _XReadEvents() ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- 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/1228597 Title: software-center crashed with signal 5 in _XReadEvents() Status in “software-center” package in Ubuntu: New Bug description: Software Center immediately crashes upon opening. System Information: Intel i7 Sandybridge Ubuntu 13.10 (32-bit) Intel Ivybridge Graphics Unit ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.09-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 ApportVersion: 2.12.4-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Sat Sep 21 11:40:17 2013 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130920) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center Signal: 5 SourcePackage: software-center StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReadEvents () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: software-center crashed with signal 5 in _XReadEvents() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1228597/+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 1020655] Re: dia does not have a panel icon in Unity
Same as #2, but icon context menu works (when the program is running). Of course invisible in Dash search. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dia in Ubuntu. https://bugs.launchpad.net/bugs/1020655 Title: dia does not have a panel icon in Unity Status in “dia” package in Ubuntu: Confirmed Bug description: Dia does not have a panel icon in Unity. It defaults to the ugly ? icon. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dia 0.97.2-5 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 3 17:59:27 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: dia UpgradeStatus: Upgraded to precise on 2012-06-26 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dia/+bug/1020655/+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 1196700] Re: firefox crashed with SIGSEGV in complete_in_idle_cb()
also on saucy...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1196700
Title:
firefox crashed with SIGSEGV in complete_in_idle_cb()
Status in “firefox” package in Ubuntu:
Confirmed
Bug description:
no se como solucionar este problema
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: firefox 23.0~b1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.10.0-1-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
BuildID: 20130626174122
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd640 irq 43'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,1179ff14,0011'
Controls : 25
Simple ctrls : 12
Channel: Unavailable
Date: Mon Jul 1 15:42:26 2013
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-05-30 (31 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
IpRoute:
default via 192.168.1.1 dev wlan1 proto static
192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.8 metric 9
MarkForUpload: True
MostRecentCrashID: bp-689699f2-698e-4e8d-9a66-81a7e2130605
PrefSources: prefs.js
ProcCmdline: /usr/lib/firefox/firefox
https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug/b89eef86-e28e-11e2-8509-002481e7f48a?field.title=nautilus+crashed+with+SIGSEGV+in+gtk_action_get_name%28%29
ProcEnviron:
LANGUAGE=es_CO:es
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=es_CO.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=23.0/20130626174122
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
totem-mozilla 3.8.2-0ubuntu1
rhythmbox-mozilla 2.99.1-0ubuntu1
google-talkplugin 3.19.1.0-1
RunningIncompatibleAddons: False
Signal: 11
SourcePackage: firefox
StacktraceTop:
?? () from /usr/lib/libunity-webapps.so.0
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/firefox/libxul.so
SubmittedCrashIDs: bp-689699f2-698e-4e8d-9a66-81a7e2130605
Title: firefox crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to saucy on 2013-06-03 (28 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 08/31/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.40
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDE:bvr1.40:bd08/31/2010:svnTOSHIBA:pnSatelliteL505:pvrPSLU6U-00G001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite L505
dmi.product.version: PSLU6U-00G001
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1196700/+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 1225849] Re: Keyboard shortcuts do not work
Gnome 3.8 x64. Most annoying behavior. I decided to change to flashback mode because I hate Unity and Gnome3 handles notifications in the worst way ever imaginable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1225849 Title: Keyboard shortcuts do not work Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: Keyboard shortcuts do not work ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session-flashback 1:3.6.2-0ubuntu15 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Mon Sep 16 07:43:31 2013 GsettingsChanges: InstallationDate: Installed on 2013-08-28 (18 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130828) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1225849/+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 1228161] Re: Graphics Adaptor Change fails then works then fails then ...
Daniel, I got this: philmorew@omega:~$ sudo apport-collect 1228161 [sudo] password for philmorew: Traceback (most recent call last): File /usr/share/apport/apport-gtk, line 518, in module app.run_argv() File /usr/lib/python2.7/dist-packages/apport/ui.py, line 556, in run_argv return self.run_update_report() File /usr/lib/python2.7/dist-packages/apport/ui.py, line 406, in run_update_report if not self.crashdb.can_update(self.options.update_report): File /usr/lib/python2.7/dist-packages/apport/crashdb_impl/launchpad.py, line 500, in can_update bug = self.launchpad.bugs[id] File /usr/lib/python2.7/dist-packages/lazr/restfulclient/resource.py, line 950, in __getitem__ raise KeyError(key) KeyError: 1228161 the first time around; presumably because your site was down, so when it came back up I ran it again. Insofar as the /var/log/Xorg.0.log, I'll attach it. Phil ** Attachment added: /var/log/Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1228161/+attachment/3833401/+files/Xorg.0.log -- 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/1228161 Title: Graphics Adaptor Change fails then works then fails then ... Status in “xorg” package in Ubuntu: Incomplete Bug description: Depending on how you look at it, this may or may not be considered a bug. The problem developed immediately after replacing my graphics adaptor because upgrading to Ubuntu 13.04 failed stating there was a problem with my video. What happens is a bit strange because the problem is self correcting but fails after restarting for reasons that are unclear - to me at least. I think perhaps the system recognizes that it is having problems when it first comes up and then cycles through alternative configurations until it finds one that works; and when I say works, it works perfectly. The scenario is as follows: 1. I start the day by booting up the cold system. It comes up with a screen that though largely correct, is rapidly fluttering back and forth, but no so badly that I can't log in. However logging in then brings up a blank gray screen that is also rapidly fluttering. 2. I then toggle my monitor, keyboard and mouse to my MS Windows 8 box and check email, the news, etc., and after awhile switch back to my fluttering Ubuntu box, still with a fluttering blank gray screen. I then do a hardware reset and switch back to my MS Windows Box and browse the news more in depth this time. Finally after awhile, I switch back to my Ubuntu box and find the screen now is no longer fluttering with my login screen. I login and everything continues to work perfectly. 3. The next day, I start at step 1 again because try as I might, I can't find out how to save the working configuration. There is no Xorg.conf file other than older ones with various suffixes: drwxr-xr-x 2 root root 4096 Oct 22 2012 app-defaults drwxr-xr-x 2 root root 4096 Apr 17 09:28 cursors -rw-r--r-- 1 root root18 Feb 18 2013 default-display-manager drwxr-xr-x 6 root root 4096 Oct 27 2009 fonts -rw-r--r-- 1 root root 17394 Jun 22 2009 rgb.txt lrwxrwxrwx 1 root root13 Nov 1 2009 X - /usr/bin/Xorg drwxr-xr-x 3 root root 4096 Aug 24 2012 xinit drwxr-xr-x 2 root root 4096 Feb 10 2011 xkb -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf-backup-100510190140 -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf.dist-upgrade-201005101857 -rw-r--r-- 1 root root 270 May 10 2010 xorg.conf.failsafe -rwxr-xr-x 1 root root 709 Apr 1 2010 Xreset drwxr-xr-x 2 root root 4096 Jan 17 2013 Xreset.d drwxr-xr-x 2 root root 4096 Jan 17 2013 Xresources -rwxr-xr-x 1 root root 3730 Jun 24 2008 Xsession drwxr-xr-x 2 root root 4096 Jul 4 18:40 Xsession.d -rw-r--r-- 1 root root 265 Jun 24 2008 Xsession.options -rw-r--r-- 1 root root13 Aug 24 2009 XvMCConfig -rw--- 1 root root 601 Oct 27 2009 Xwrapper.config The default-display-manager contains: /usr/sbin/lightdm and /usr/bin/Xorg is some sort of ELF file. Most of the fixes I've found are ones that update xorg.conf but since a system wide search has not located a xorg.conf file, presumably something else is being used. My hardware according to the Asus box is: HD 6450 SILENT/DI/1GD3(LP) the Part No.: 90-C1CQ0F-L0AANAYZ and the serial number: D4C0YZ239187 The lspci command nets out to: 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450] Presumably this will net out to some sort of reconfiguration, or more likely a means to save the currently working configuration (I am, by the way, reporting this bug on the failing box after a number of reboots and hardware resets before finally arriving at the now perfectly operational screen). Any thoughts
[Desktop-packages] [Bug 1228161] Re: Graphics Adaptor Change fails then works then fails then ...
apport information ** Tags added: apport-collected ** Description changed: Depending on how you look at it, this may or may not be considered a bug. The problem developed immediately after replacing my graphics adaptor because upgrading to Ubuntu 13.04 failed stating there was a problem with my video. What happens is a bit strange because the problem is self correcting but fails after restarting for reasons that are unclear - to me at least. I think perhaps the system recognizes that it is having problems when it first comes up and then cycles through alternative configurations until it finds one that works; and when I say works, it works perfectly. The scenario is as follows: 1. I start the day by booting up the cold system. It comes up with a screen that though largely correct, is rapidly fluttering back and forth, but no so badly that I can't log in. However logging in then brings up a blank gray screen that is also rapidly fluttering. 2. I then toggle my monitor, keyboard and mouse to my MS Windows 8 box and check email, the news, etc., and after awhile switch back to my fluttering Ubuntu box, still with a fluttering blank gray screen. I then do a hardware reset and switch back to my MS Windows Box and browse the news more in depth this time. Finally after awhile, I switch back to my Ubuntu box and find the screen now is no longer fluttering with my login screen. I login and everything continues to work perfectly. 3. The next day, I start at step 1 again because try as I might, I can't find out how to save the working configuration. There is no Xorg.conf file other than older ones with various suffixes: drwxr-xr-x 2 root root 4096 Oct 22 2012 app-defaults drwxr-xr-x 2 root root 4096 Apr 17 09:28 cursors -rw-r--r-- 1 root root18 Feb 18 2013 default-display-manager drwxr-xr-x 6 root root 4096 Oct 27 2009 fonts -rw-r--r-- 1 root root 17394 Jun 22 2009 rgb.txt lrwxrwxrwx 1 root root13 Nov 1 2009 X - /usr/bin/Xorg drwxr-xr-x 3 root root 4096 Aug 24 2012 xinit drwxr-xr-x 2 root root 4096 Feb 10 2011 xkb -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf-backup-100510190140 -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf.dist-upgrade-201005101857 -rw-r--r-- 1 root root 270 May 10 2010 xorg.conf.failsafe -rwxr-xr-x 1 root root 709 Apr 1 2010 Xreset drwxr-xr-x 2 root root 4096 Jan 17 2013 Xreset.d drwxr-xr-x 2 root root 4096 Jan 17 2013 Xresources -rwxr-xr-x 1 root root 3730 Jun 24 2008 Xsession drwxr-xr-x 2 root root 4096 Jul 4 18:40 Xsession.d -rw-r--r-- 1 root root 265 Jun 24 2008 Xsession.options -rw-r--r-- 1 root root13 Aug 24 2009 XvMCConfig -rw--- 1 root root 601 Oct 27 2009 Xwrapper.config The default-display-manager contains: /usr/sbin/lightdm and /usr/bin/Xorg is some sort of ELF file. Most of the fixes I've found are ones that update xorg.conf but since a system wide search has not located a xorg.conf file, presumably something else is being used. My hardware according to the Asus box is: HD 6450 SILENT/DI/1GD3(LP) the Part No.: 90-C1CQ0F-L0AANAYZ and the serial number: D4C0YZ239187 The lspci command nets out to: 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450] Presumably this will net out to some sort of reconfiguration, or more likely a means to save the currently working configuration (I am, by the way, reporting this bug on the failing box after a number of reboots and hardware resets before finally arriving at the now perfectly operational screen). Any thoughts would be greatly appreciated. If any additional information is needed, let me know and I'll provide it as needed. I've tried to pare down much of the data I've gathered to provide that which I thought to be most meaningful. Thanks Phil ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Fri Sep 20 09:18:20 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to precise on 2013-09-12 (7 days ago) + --- + ApportVersion: 2.0.1-0ubuntu17.4 + Architecture: amd64 + DistroRelease: Ubuntu 12.04 + MarkForUpload: True + Package: xorg 1:7.6+12ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 + Tags: precise + Uname: Linux 3.2.0-53-generic x86_64 + UpgradeStatus: Upgraded
[Desktop-packages] [Bug 1196700] Re: firefox crashed with SIGSEGV in complete_in_idle_cb()
** Package changed: firefox (Ubuntu) = unity-firefox-extension (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-firefox-extension in Ubuntu.
https://bugs.launchpad.net/bugs/1196700
Title:
firefox crashed with SIGSEGV in complete_in_idle_cb()
Status in “unity-firefox-extension” package in Ubuntu:
Confirmed
Bug description:
no se como solucionar este problema
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: firefox 23.0~b1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.10.0-1-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
BuildID: 20130626174122
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd640 irq 43'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,1179ff14,0011'
Controls : 25
Simple ctrls : 12
Channel: Unavailable
Date: Mon Jul 1 15:42:26 2013
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-05-30 (31 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
IpRoute:
default via 192.168.1.1 dev wlan1 proto static
192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.8 metric 9
MarkForUpload: True
MostRecentCrashID: bp-689699f2-698e-4e8d-9a66-81a7e2130605
PrefSources: prefs.js
ProcCmdline: /usr/lib/firefox/firefox
https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug/b89eef86-e28e-11e2-8509-002481e7f48a?field.title=nautilus+crashed+with+SIGSEGV+in+gtk_action_get_name%28%29
ProcEnviron:
LANGUAGE=es_CO:es
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=es_CO.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=23.0/20130626174122
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
totem-mozilla 3.8.2-0ubuntu1
rhythmbox-mozilla 2.99.1-0ubuntu1
google-talkplugin 3.19.1.0-1
RunningIncompatibleAddons: False
Signal: 11
SourcePackage: firefox
StacktraceTop:
?? () from /usr/lib/libunity-webapps.so.0
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/firefox/libxul.so
SubmittedCrashIDs: bp-689699f2-698e-4e8d-9a66-81a7e2130605
Title: firefox crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to saucy on 2013-06-03 (28 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 08/31/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.40
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDE:bvr1.40:bd08/31/2010:svnTOSHIBA:pnSatelliteL505:pvrPSLU6U-00G001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite L505
dmi.product.version: PSLU6U-00G001
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-firefox-extension/+bug/1196700/+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 1097946] Re: software-center crashed with TransactionFailed in _run_transaction(): unprintable TransactionFailed object
** Also affects: software-center (Ubuntu Linaro Evaluation Build) Importance: Undecided Status: 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/1097946 Title: software-center crashed with TransactionFailed in _run_transaction(): unprintable TransactionFailed object Status in Ubuntu Software Center: Confirmed Status in Wine: Invalid Status in “software-center” package in Ubuntu: Confirmed Status in “software-center” source package in Raring: Confirmed Status in “software-center” package in Ubuntu Linaro Evaluation Build: New Bug description: I try to install Skype on ubuntu 13.04 ProblemType: RecoverableProblem DistroRelease: Ubuntu 13.04 Package: software-center 5.5.3 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Wed Jan 9 21:59:07 2013 DuplicateSignature: software-center:trans-failed:error-dep-resolution-failed ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2013-01-04 (5 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130103) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: software-center Title: software-center crashed with TransactionFailed in _run_transaction(): unprintable TransactionFailed object Traceback: Traceback (most recent call last): File /usr/share/software-center/softwarecenter/backend/installbackend_impl/aptd.py, line 990, in _run_transaction yield trans.run(defer=True) TransactionFailed: unprintable TransactionFailed object UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1097946/+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 1228422] [NEW] Severe regressions to typing in Greek, Russian, etc due to IBus
You have been subscribed to a public bug: For the last several versions of Ubuntu, there was an inability to type Greek (or many non-latin scripts) in the Dash. With bug https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1205713 the problem has been fixed, and it got fixed by enabling IBus for Greek, Russian and several other scripts. However, this change revealed several deficiencies in IBus (tested with Greek and Russian): 1. It is no longer possible to use keyboard accelerators when the active keyboard layout is in Greek, Russian, etc. The reason is because the gtk+ IM contains special code so that Ctrl+A while in the Greek keyboard layout would still do a Select All. Currently in Ubuntu 13.10, when you press, for example, Ctrl+A (with Greek layout active), the app receives a Greek Alpha, which is ignored by the app. The same goes with, for example, Alt+F, which no longer opens up the File menu. More background about this at https://bugzilla.mozilla.org/show_bug.cgi?id=69230#c2 (FIXME: need to add link to gtk+ git with code on how they implement the solution) 2. The default keyboard shortcut to switch between keyboard layouts is Super+Space (default for IBus). Pressing the Super key ends up bringing up the HUD most of the times. I have been trying to get myself to press Super+Space more properly, but it's really difficult to get it right. I now get it right only about 30% of the times, and I need to pause when typing in order to check if I am actually writing by accident in the HUD. I would say it is a huge usability issue that, as is, will alienate non- English users of Ubuntu. 3. It is not possible to change the shortcut to switch keyboard layouts to the traditional Alt+Shift (used by most Ubuntu-gr users). In addition, if you manage to change the shortcut to something else, then it's impossible to change back to Super+Space. ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed -- Severe regressions to typing in Greek, Russian, etc due to IBus https://bugs.launchpad.net/bugs/1228422 You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. -- 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 1040873] Re: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working
Just and FYI that this bug also affects the N56DP (AMD version of the N56) and the #1 fix in the first post does fix the problem for me as long as I use surround 4.1 as 5.1 does not work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1040873 Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Hi, this bug is a fork of https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/871808 because #871808 stands for a different hardware with a different solution, so people may get confused. Here is a summary (see post #48 to #54 of #871808): The subwoofer of Asus N56VZ laptop doesn't work out of the box. #sudo hda-jack-sense-test -a : *** Without subwoofer: Pin 0x1e (Black SPDIF Out): present = No *** With subwoofer: Pin 0x1e (Black SPDIF Out): present = Yes http://www.alsa- project.org/db/?f=2778e7f430aa95ae219d0b2bc3cb5e46abd0a33a -- There are two ways of making it work: #1 a. Add to rc.local : echo 0x1e 0x99130112 /sys/class/sound/hwC0D0/user_pin_configs echo 1 /sys/class/sound/hwC0D0/reconfig b. Add options snd-hda-intel model=asus-mode4 in /etc/modprobe.d/alsa-base.conf c. Reboot d. Set the mode to Analog Stereo Output and then to Analog Surround 5.1 output in the sound settings panel. You have to do this each time you reboot!!! #2 a. Add to rc.local : echo 0x16 0x99130111 /sys/class/sound/hwC0D0/user_pin_configs echo 0x1e 0x99130112 /sys/class/sound/hwC0D0/user_pin_configs echo 1 /sys/class/sound/hwC0D0/reconfig b. Reboot c. Set the mode to Analog Stereo Output and then to Analog Surround 5.1 output in the sound settings panel. You have to do this each time you reboot!!! Both give the same results and fix the bug. -- Can you make it work out of the box? There is still two other bugs on this laptop : - crackling audio when playing with sound volume: see https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040867 - When I put the omputer in sleep mode, there is no way to get sound working on resume: should I open a new bug to investigate this? Regards Sam ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam1898 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47' Mixer name : 'Realtek ALC663' Components : 'HDA:10ec0663,10431477,0012' Controls : 23 Simple ctrls : 13 CheckboxSubmission: 54021779511d0213081a2b1707bf951c CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a Date: Thu Aug 23 22:38:00 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: 1898 sam F pulseaudio PID ACCESS COMMAND Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-23T22:27:03.314416 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1040873] Re: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working
Correction to my previous post. I HAVE to switch from 4.1 to 5.1 or 5.1 to 4.1 on reboot to make the change take effect. Either 5.1 or 4.1 work after that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1040873 Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Hi, this bug is a fork of https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/871808 because #871808 stands for a different hardware with a different solution, so people may get confused. Here is a summary (see post #48 to #54 of #871808): The subwoofer of Asus N56VZ laptop doesn't work out of the box. #sudo hda-jack-sense-test -a : *** Without subwoofer: Pin 0x1e (Black SPDIF Out): present = No *** With subwoofer: Pin 0x1e (Black SPDIF Out): present = Yes http://www.alsa- project.org/db/?f=2778e7f430aa95ae219d0b2bc3cb5e46abd0a33a -- There are two ways of making it work: #1 a. Add to rc.local : echo 0x1e 0x99130112 /sys/class/sound/hwC0D0/user_pin_configs echo 1 /sys/class/sound/hwC0D0/reconfig b. Add options snd-hda-intel model=asus-mode4 in /etc/modprobe.d/alsa-base.conf c. Reboot d. Set the mode to Analog Stereo Output and then to Analog Surround 5.1 output in the sound settings panel. You have to do this each time you reboot!!! #2 a. Add to rc.local : echo 0x16 0x99130111 /sys/class/sound/hwC0D0/user_pin_configs echo 0x1e 0x99130112 /sys/class/sound/hwC0D0/user_pin_configs echo 1 /sys/class/sound/hwC0D0/reconfig b. Reboot c. Set the mode to Analog Stereo Output and then to Analog Surround 5.1 output in the sound settings panel. You have to do this each time you reboot!!! Both give the same results and fix the bug. -- Can you make it work out of the box? There is still two other bugs on this laptop : - crackling audio when playing with sound volume: see https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040867 - When I put the omputer in sleep mode, there is no way to get sound working on resume: should I open a new bug to investigate this? Regards Sam ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam1898 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47' Mixer name : 'Realtek ALC663' Components : 'HDA:10ec0663,10431477,0012' Controls : 23 Simple ctrls : 13 CheckboxSubmission: 54021779511d0213081a2b1707bf951c CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a Date: Thu Aug 23 22:38:00 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: 1898 sam F pulseaudio PID ACCESS COMMAND Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-23T22:27:03.314416 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1228633] [NEW] Totem crashes Gnome desktop
Public bug reported: Totem simply does not operate on 12.04 (fully updated) using Gnome 3.4.2 desktop with nVidia 304.88 and dual monitors on a GT-9600 card. a) If run normally to play a video the screen flashes, the second monitor is DISABLED, and the desktop locks-up. b) If run automatically in a Firefox when a page is hit the desktop locks-up. The only solution when this happens us to hard-reset the computer and suffer the long disk checks on reboot. It used to work - but has behaved like this for months. I'm tired of the accidental crashes while in Firefox when I happen to hit a page with Totem-mapped media and have uninstalled it. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- 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/1228633 Title: Totem crashes Gnome desktop Status in “totem” package in Ubuntu: New Bug description: Totem simply does not operate on 12.04 (fully updated) using Gnome 3.4.2 desktop with nVidia 304.88 and dual monitors on a GT-9600 card. a) If run normally to play a video the screen flashes, the second monitor is DISABLED, and the desktop locks-up. b) If run automatically in a Firefox when a page is hit the desktop locks-up. The only solution when this happens us to hard-reset the computer and suffer the long disk checks on reboot. It used to work - but has behaved like this for months. I'm tired of the accidental crashes while in Firefox when I happen to hit a page with Totem-mapped media and have uninstalled it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1228633/+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 1228161] Re: Graphics Adaptor Change fails then works then fails then ...
Sorry, I forgot apport is not so advance with Ubuntu 12.04 (but you shouldn't run it with sudo at any rate) :\ You may want to consider upgrading to the lts-raring graphics stack: sudo apt-get install xserver-xorg-lts-raring linux-generic-lts-raring ** Package changed: xorg (Ubuntu) = xserver-xorg-video-ati (Ubuntu) ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete = Confirmed -- 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/1228161 Title: Graphics Adaptor Change fails then works then fails then ... Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: Depending on how you look at it, this may or may not be considered a bug. The problem developed immediately after replacing my graphics adaptor because upgrading to Ubuntu 13.04 failed stating there was a problem with my video. What happens is a bit strange because the problem is self correcting but fails after restarting for reasons that are unclear - to me at least. I think perhaps the system recognizes that it is having problems when it first comes up and then cycles through alternative configurations until it finds one that works; and when I say works, it works perfectly. The scenario is as follows: 1. I start the day by booting up the cold system. It comes up with a screen that though largely correct, is rapidly fluttering back and forth, but no so badly that I can't log in. However logging in then brings up a blank gray screen that is also rapidly fluttering. 2. I then toggle my monitor, keyboard and mouse to my MS Windows 8 box and check email, the news, etc., and after awhile switch back to my fluttering Ubuntu box, still with a fluttering blank gray screen. I then do a hardware reset and switch back to my MS Windows Box and browse the news more in depth this time. Finally after awhile, I switch back to my Ubuntu box and find the screen now is no longer fluttering with my login screen. I login and everything continues to work perfectly. 3. The next day, I start at step 1 again because try as I might, I can't find out how to save the working configuration. There is no Xorg.conf file other than older ones with various suffixes: drwxr-xr-x 2 root root 4096 Oct 22 2012 app-defaults drwxr-xr-x 2 root root 4096 Apr 17 09:28 cursors -rw-r--r-- 1 root root18 Feb 18 2013 default-display-manager drwxr-xr-x 6 root root 4096 Oct 27 2009 fonts -rw-r--r-- 1 root root 17394 Jun 22 2009 rgb.txt lrwxrwxrwx 1 root root13 Nov 1 2009 X - /usr/bin/Xorg drwxr-xr-x 3 root root 4096 Aug 24 2012 xinit drwxr-xr-x 2 root root 4096 Feb 10 2011 xkb -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf-backup-100510190140 -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf.dist-upgrade-201005101857 -rw-r--r-- 1 root root 270 May 10 2010 xorg.conf.failsafe -rwxr-xr-x 1 root root 709 Apr 1 2010 Xreset drwxr-xr-x 2 root root 4096 Jan 17 2013 Xreset.d drwxr-xr-x 2 root root 4096 Jan 17 2013 Xresources -rwxr-xr-x 1 root root 3730 Jun 24 2008 Xsession drwxr-xr-x 2 root root 4096 Jul 4 18:40 Xsession.d -rw-r--r-- 1 root root 265 Jun 24 2008 Xsession.options -rw-r--r-- 1 root root13 Aug 24 2009 XvMCConfig -rw--- 1 root root 601 Oct 27 2009 Xwrapper.config The default-display-manager contains: /usr/sbin/lightdm and /usr/bin/Xorg is some sort of ELF file. Most of the fixes I've found are ones that update xorg.conf but since a system wide search has not located a xorg.conf file, presumably something else is being used. My hardware according to the Asus box is: HD 6450 SILENT/DI/1GD3(LP) the Part No.: 90-C1CQ0F-L0AANAYZ and the serial number: D4C0YZ239187 The lspci command nets out to: 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450] Presumably this will net out to some sort of reconfiguration, or more likely a means to save the currently working configuration (I am, by the way, reporting this bug on the failing box after a number of reboots and hardware resets before finally arriving at the now perfectly operational screen). Any thoughts would be greatly appreciated. If any additional information is needed, let me know and I'll provide it as needed. I've tried to pare down much of the data I've gathered to provide that which I thought to be most meaningful. Thanks Phil ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Fri Sep 20 09:18:20 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en
[Desktop-packages] [Bug 1228637] Re: wpa_supplicant crashed with SIGSEGV
*** This bug is a duplicate of bug 1210785 *** https://bugs.launchpad.net/bugs/1210785 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1210785, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1228637/+attachment/3833582/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1228637/+attachment/3833584/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1228637/+attachment/3833585/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1228637/+attachment/3833586/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1228637/+attachment/3833587/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1228637/+attachment/3833588/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1228637/+attachment/3833589/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1210785 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1228637 Title: wpa_supplicant crashed with SIGSEGV Status in “wpa” package in Ubuntu: New Bug description: I disconected a USB Wifi Adapter I have when this error appear. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: wpasupplicant 1.0-3ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 ApportVersion: 2.12.4-0ubuntu1 Architecture: i386 Date: Sat Sep 21 09:12:53 2013 ExecutablePath: /sbin/wpa_supplicant InstallationDate: Installed on 2013-09-16 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130914) MarkForUpload: True ProcCmdline: /sbin/wpa_supplicant -B -P /run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant ProcEnviron: SegvAnalysis: Segfault happened at: 0x81028d0: mov0x4(%esi),%edx PC (0x081028d0) ok source 0x4(%esi) (0x0206) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: wpa_supplicant crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1228637/+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 1195867] Re: codeblocks crashed with SIGABRT in g_type_check_instance_cast()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lib32wxgtk2.8 (Ubuntu) Status: New = Confirmed -- 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/1195867 Title: codeblocks crashed with SIGABRT in g_type_check_instance_cast() Status in “codeblocks” package in Ubuntu: Confirmed Status in “gtk+2.0” package in Ubuntu: Confirmed Status in “lib32wxgtk2.8” package in Ubuntu: Confirmed Bug description: Ubuntu Saucy Salamander (development branch) Release: 13.10 Ubuntu GNOME on amd64 codeblocks: Installed: 12.11-3 Candidate: 12.11-3 Version table: *** 12.11-3 0 500 http://ge.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages 100 /var/lib/dpkg/status i'm unable to start codeblocks ide. it crashes afrer choosing compiler ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: codeblocks 12.11-3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Fri Jun 28 23:41:02 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/codeblocks InstallationDate: Installed on 2013-06-25 (3 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130616) MarkForUpload: True ProcCmdline: codeblocks Signal: 6 SourcePackage: codeblocks StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 wxMenu::GtkAppend(wxMenuItem*, int) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 wxMenu::DoAppend(wxMenuItem*) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 ?? () DebuggerManager::RefreshUI() () from /usr/lib/libcodeblocks.so.0 Title: codeblocks crashed with SIGABRT in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/codeblocks/+bug/1195867/+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 1195867] Re: codeblocks crashed with SIGABRT in g_type_check_instance_cast()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+2.0 (Ubuntu) Status: New = Confirmed -- 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/1195867 Title: codeblocks crashed with SIGABRT in g_type_check_instance_cast() Status in “codeblocks” package in Ubuntu: Confirmed Status in “gtk+2.0” package in Ubuntu: Confirmed Status in “lib32wxgtk2.8” package in Ubuntu: Confirmed Bug description: Ubuntu Saucy Salamander (development branch) Release: 13.10 Ubuntu GNOME on amd64 codeblocks: Installed: 12.11-3 Candidate: 12.11-3 Version table: *** 12.11-3 0 500 http://ge.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages 100 /var/lib/dpkg/status i'm unable to start codeblocks ide. it crashes afrer choosing compiler ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: codeblocks 12.11-3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Fri Jun 28 23:41:02 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/codeblocks InstallationDate: Installed on 2013-06-25 (3 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130616) MarkForUpload: True ProcCmdline: codeblocks Signal: 6 SourcePackage: codeblocks StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 wxMenu::GtkAppend(wxMenuItem*, int) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 wxMenu::DoAppend(wxMenuItem*) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 ?? () DebuggerManager::RefreshUI() () from /usr/lib/libcodeblocks.so.0 Title: codeblocks crashed with SIGABRT in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/codeblocks/+bug/1195867/+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 284915] Re: Khelpcenter missing docs list
Launchpad has imported 4 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=128605. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2006-06-04T10:52:47+00:00 carsten wrote: Version: 2.0 Destroyer (using KDE 3.5.3, Kubuntu Package 4:3.5.3-0ubuntu0.1 dapper) Compiler: Target: i486-linux-gnu OS:Linux (i686) release 2.6.15-23-386 Well, this is not a real bugreport, but somehow I feel I want this to be documented... Adept improved a lot in the last year, but the version in Dapper is missing one seriously important thing: Documentation! There is not a single QWhatThis I found ... no QToolTip ... no man-page ... no manual ... the homepage of the author is not giving any information ... http://web.ekhis.org/adept.html is dead I installed Dapper on the computers of two others, both are users and have no clue about things like apt, shell and so on. The didn't understand the concept of Adept at all and finally gave up because they found no documentation whatsoever. This if for me a showstopper-bug, nothing less. There is no usability-section in this bugtracker, this is why I filed it as a wish... Adding tooltips on the 20 most important widgets would help *a lot*. Reply at: https://bugs.launchpad.net/ubuntu/+source/kde- runtime/+bug/284915/comments/0 On 2008-03-09T15:58:10+00:00 mornfall wrote: Yes, well, this is true. However, I have as little time as it gets, so help with documentation would be welcome. I have been working on a 3.0 for some time now, which should address at least some of the usability issues, but there are probably quite some left, and there's still too little documentation. Reply at: https://bugs.launchpad.net/ubuntu/+source/kde- runtime/+bug/284915/comments/9 On 2008-08-12T17:25:57+00:00 mornfall wrote: I believe the situation has much improved with Adept 3. However, this is mostly a perpetual issue -- I'm marking it as needs volunteer, so people are encouraged to step up with help text improvements. Reply at: https://bugs.launchpad.net/ubuntu/+source/kde- runtime/+bug/284915/comments/10 On 2013-09-21T04:44:50+00:00 adaptee wrote: Adept has been in the unmaintained state for a few years. Use muon[1] as replacement . [1] https://launchpad.net/muon Reply at: https://bugs.launchpad.net/ubuntu/+source/kde- runtime/+bug/284915/comments/33 ** Changed in: adeptmgr Status: In Progress = Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to amarok in Ubuntu. https://bugs.launchpad.net/bugs/284915 Title: Khelpcenter missing docs list Status in Adept Manager: Unknown Status in KTorrent: BitTorrent Client for KDE: Unknown Status in “adept” package in Ubuntu: Won't Fix Status in “amarok” package in Ubuntu: Confirmed Status in “cdbs” package in Ubuntu: Fix Released Status in “digikam” package in Ubuntu: Confirmed Status in “k3b” package in Ubuntu: Fix Released Status in “kde-runtime” package in Ubuntu: Confirmed Status in “kde-workspace” package in Ubuntu: Confirmed Status in “kdelibs” package in Ubuntu: Fix Released Status in “kdenetwork” package in Ubuntu: Confirmed Status in “kdepimlibs” package in Ubuntu: Confirmed Status in “konversation” package in Ubuntu: Fix Released Status in “ktorrent” package in Ubuntu: Triaged Bug description: Binary package hint: khelpcenter Missing Doc modules in helpcenter list: Kubuntu Docs: All Present Welcome to KDE: All Present KDE User's Manual: All Present Application Manuals: Find Files/Folders: All Present Graphics: All Present Help: All Present Internet: Akregator = Missing Kmail = Missing Konversation = Appears twice and is Missing Ktorrent = Missing Multimedia: Amarok = Appears Twice and is Missing K3b = Appears Twice and is Missing Office: All Missing System: KsystemLog = Missing Utilities: Knotes = Missing KTimeTracker = Missing Control Center Modules: Fonts = Appears Twice has different info in both Sound = Missing Keyboard Layout = Missing Solid = Missing Mouse = Missing Window Behaviour = Missing Desktop Effects = Missing Window-Specific = Missing KinfoCenter Modules: Processor Information = Missing IEEE 1394 Devices = Missing Kioslaves: ar = Missing audiocd = Missing mbox = Missing scalix = Missing scalixs = Missing zip = Missing Scrollkeeper: Seems to be empty Plasma Manual: All Present Tutorials:
[Desktop-packages] [Bug 1228650] [NEW] nvidia-319-updates 319.49-0ubuntu1: nvidia-319-updates kernel module failed to build
Public bug reported: This one comes evry time i restart my computer. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: nvidia-319-updates 319.49-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.11.0-7-generic Date: Mon Sep 16 21:54:39 2013 InstallationDate: Installed on 2013-09-12 (9 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130912) MarkForUpload: True PackageVersion: 319.49-0ubuntu1 SourcePackage: nvidia-graphics-drivers-319-updates Title: nvidia-319-updates 319.49-0ubuntu1: nvidia-319-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-319-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1228650 Title: nvidia-319-updates 319.49-0ubuntu1: nvidia-319-updates kernel module failed to build Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: New Bug description: This one comes evry time i restart my computer. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: nvidia-319-updates 319.49-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.11.0-7-generic Date: Mon Sep 16 21:54:39 2013 InstallationDate: Installed on 2013-09-12 (9 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130912) MarkForUpload: True PackageVersion: 319.49-0ubuntu1 SourcePackage: nvidia-graphics-drivers-319-updates Title: nvidia-319-updates 319.49-0ubuntu1: nvidia-319-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1228650/+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 1169117] Re: REGRESSION: MBIM kernel suppport should be disabled until userspace support available (breaks Ericsson H5321 etc.)
Having the similar issue with Ericsson H5321gw in Toshiba Z830. SIM registers to network, but than fails to connect most of the tries(like 1success to 30 failures). I tried the solution in 2), after reboot I connected from the first try, but after that I have not be able to get connection. I see the driver used in my case is cdc_acm - cna this be the reason? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1169117 Title: REGRESSION: MBIM kernel suppport should be disabled until userspace support available (breaks Ericsson H5321 etc.) Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Confirmed Status in “modemmanager” package in Ubuntu: Invalid Status in “linux” package in Debian: Fix Committed Bug description: commit bd329e1 (net: cdc_ncm: do not bind to NCM compatible MBIM devices) introduced a new policy, preferring MBIM for dual NCM/MBIM functions if the cdc_mbim driver was enabled. This caused a regression for users wanting to use NCM. This could be solved in different ways: 1) Remove cdc_mbim.ko from packages like linux-image-extra-3.8.0-XX- YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter prefer_mbim to false for cdc_ncm module. This could be done by adding a file /etc/modprobe.d/avoid- mbim.conf with content: options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. 3) Debian has solved it by patching the kernel to reverse the default to be not to use MBIM: http://web.archiveorange.com/archive/v/dbmrrKybrWTJ0XZGsB3B http://lists.debian.org/debian-kernel/2013/03/msg00611.html See also bug #1102343. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1169117/+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 1169117] Re: REGRESSION: MBIM kernel suppport should be disabled until userspace support available (breaks Ericsson H5321 etc.)
Also the modem itself is recognized as Toshiba, not Ericsson: [code] Sep 21 15:31:49 toshiba kernel: [ 7078.450687] usb 1-1.6: new high-speed USB device number 7 using ehci_hcd Sep 21 15:31:49 toshiba kernel: [ 7078.545002] usb 1-1.6: New USB device found, idVendor=0930, idProduct=1319 Sep 21 15:31:49 toshiba kernel: [ 7078.545013] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 21 15:31:49 toshiba kernel: [ 7078.545019] usb 1-1.6: Product: H5321gw Sep 21 15:31:49 toshiba kernel: [ 7078.545024] usb 1-1.6: Manufacturer: TOSHIBA Sep 21 15:31:49 toshiba kernel: [ 7078.545029] usb 1-1.6: SerialNumber: 24359BF58A1F4870 Sep 21 15:31:49 toshiba mtp-probe: checking bus 1, device 7: /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6 Sep 21 15:31:49 toshiba kernel: [ 7078.578410] cdc_acm 1-1.6:1.1: ttyACM0: USB ACM device Sep 21 15:31:49 toshiba kernel: [ 7078.582138] cdc_acm 1-1.6:1.3: ttyACM1: USB ACM device Sep 21 15:31:49 toshiba kernel: [ 7078.590550] cdc_wdm 1-1.6:1.5: cdc-wdm0: USB WDM device Sep 21 15:31:49 toshiba kernel: [ 7078.605591] usb 1-1.6: MAC-Address: 02:15:e0:ec:01:00 Sep 21 15:31:49 toshiba kernel: [ 7078.606071] cdc_ncm 1-1.6:1.6: usb0: register 'cdc_ncm' at usb-:00:1a.0-1.6, CDC NCM, 02:15:e0:ec:01:00 Sep 21 15:31:49 toshiba kernel: [ 7078.607135] cdc_wdm 1-1.6:1.8: cdc-wdm1: USB WDM device Sep 21 15:31:49 toshiba kernel: [ 7078.607728] cdc_acm 1-1.6:1.9: ttyACM2: USB ACM device Sep 21 15:31:49 toshiba mtp-probe: bus: 1, device: 7 was not an MTP device [/code] It is really wird why the modem connects occasionally, but most of the times doesn't. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1169117 Title: REGRESSION: MBIM kernel suppport should be disabled until userspace support available (breaks Ericsson H5321 etc.) Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Confirmed Status in “modemmanager” package in Ubuntu: Invalid Status in “linux” package in Debian: Fix Committed Bug description: commit bd329e1 (net: cdc_ncm: do not bind to NCM compatible MBIM devices) introduced a new policy, preferring MBIM for dual NCM/MBIM functions if the cdc_mbim driver was enabled. This caused a regression for users wanting to use NCM. This could be solved in different ways: 1) Remove cdc_mbim.ko from packages like linux-image-extra-3.8.0-XX- YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter prefer_mbim to false for cdc_ncm module. This could be done by adding a file /etc/modprobe.d/avoid- mbim.conf with content: options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. 3) Debian has solved it by patching the kernel to reverse the default to be not to use MBIM: http://web.archiveorange.com/archive/v/dbmrrKybrWTJ0XZGsB3B http://lists.debian.org/debian-kernel/2013/03/msg00611.html See also bug #1102343. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1169117/+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 774180] Re: Banshee won't quit unless I kill process
For me, the normal 'Quit' option is missing from the menu. I'm running KDE. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/774180 Title: Banshee won't quit unless I kill process Status in “banshee” package in Ubuntu: Incomplete Bug description: Binary package hint: banshee Happened a few times ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: banshee 2.0.0-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Date: Sat Apr 30 09:16:50 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/774180/+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 1228161] Re: Graphics Adaptor Change fails then works then fails then ...
Daniel, Many thanks, I ran your suggested: sudo apt-get install xserver-xorg-lts-raring linux-generic-lts-raring installation; took the system all the way down and then booted up from a cold start and everything now seems to be working normally. MANY THANKS, Phil -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1228161 Title: Graphics Adaptor Change fails then works then fails then ... Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: Depending on how you look at it, this may or may not be considered a bug. The problem developed immediately after replacing my graphics adaptor because upgrading to Ubuntu 13.04 failed stating there was a problem with my video. What happens is a bit strange because the problem is self correcting but fails after restarting for reasons that are unclear - to me at least. I think perhaps the system recognizes that it is having problems when it first comes up and then cycles through alternative configurations until it finds one that works; and when I say works, it works perfectly. The scenario is as follows: 1. I start the day by booting up the cold system. It comes up with a screen that though largely correct, is rapidly fluttering back and forth, but no so badly that I can't log in. However logging in then brings up a blank gray screen that is also rapidly fluttering. 2. I then toggle my monitor, keyboard and mouse to my MS Windows 8 box and check email, the news, etc., and after awhile switch back to my fluttering Ubuntu box, still with a fluttering blank gray screen. I then do a hardware reset and switch back to my MS Windows Box and browse the news more in depth this time. Finally after awhile, I switch back to my Ubuntu box and find the screen now is no longer fluttering with my login screen. I login and everything continues to work perfectly. 3. The next day, I start at step 1 again because try as I might, I can't find out how to save the working configuration. There is no Xorg.conf file other than older ones with various suffixes: drwxr-xr-x 2 root root 4096 Oct 22 2012 app-defaults drwxr-xr-x 2 root root 4096 Apr 17 09:28 cursors -rw-r--r-- 1 root root18 Feb 18 2013 default-display-manager drwxr-xr-x 6 root root 4096 Oct 27 2009 fonts -rw-r--r-- 1 root root 17394 Jun 22 2009 rgb.txt lrwxrwxrwx 1 root root13 Nov 1 2009 X - /usr/bin/Xorg drwxr-xr-x 3 root root 4096 Aug 24 2012 xinit drwxr-xr-x 2 root root 4096 Feb 10 2011 xkb -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf-backup-100510190140 -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf.dist-upgrade-201005101857 -rw-r--r-- 1 root root 270 May 10 2010 xorg.conf.failsafe -rwxr-xr-x 1 root root 709 Apr 1 2010 Xreset drwxr-xr-x 2 root root 4096 Jan 17 2013 Xreset.d drwxr-xr-x 2 root root 4096 Jan 17 2013 Xresources -rwxr-xr-x 1 root root 3730 Jun 24 2008 Xsession drwxr-xr-x 2 root root 4096 Jul 4 18:40 Xsession.d -rw-r--r-- 1 root root 265 Jun 24 2008 Xsession.options -rw-r--r-- 1 root root13 Aug 24 2009 XvMCConfig -rw--- 1 root root 601 Oct 27 2009 Xwrapper.config The default-display-manager contains: /usr/sbin/lightdm and /usr/bin/Xorg is some sort of ELF file. Most of the fixes I've found are ones that update xorg.conf but since a system wide search has not located a xorg.conf file, presumably something else is being used. My hardware according to the Asus box is: HD 6450 SILENT/DI/1GD3(LP) the Part No.: 90-C1CQ0F-L0AANAYZ and the serial number: D4C0YZ239187 The lspci command nets out to: 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450] Presumably this will net out to some sort of reconfiguration, or more likely a means to save the currently working configuration (I am, by the way, reporting this bug on the failing box after a number of reboots and hardware resets before finally arriving at the now perfectly operational screen). Any thoughts would be greatly appreciated. If any additional information is needed, let me know and I'll provide it as needed. I've tried to pare down much of the data I've gathered to provide that which I thought to be most meaningful. Thanks Phil ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Fri Sep 20 09:18:20 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-ati
[Desktop-packages] [Bug 1228418] Re: gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1228418 Title: gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new() Status in “gvfs” package in Ubuntu: Confirmed Bug description: I got this bug when trying to copy file from my PC to Kindle Fire 8.9 HD ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 18:25:17 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130919) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/4 SegvAnalysis: Failure: 'dx' Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 LIBMTP_Get_Storage () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1228418/+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 1228418] Re: gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1228418 Title: gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new() Status in “gvfs” package in Ubuntu: Confirmed Bug description: I got this bug when trying to copy file from my PC to Kindle Fire 8.9 HD ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 18:25:17 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130919) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/4 SegvAnalysis: Failure: 'dx' Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 LIBMTP_Get_Storage () from /usr/lib/x86_64-linux-gnu/libmtp.so.9 Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1228418/+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 1205647] Re: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
This happens to me when trying to unmount an SMB share from Nautilus by clicking on the little triangular icon. However, when right-clicking and choosing unmount, there is *no* crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1205647 Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run() Status in “gvfs” package in Ubuntu: Confirmed Bug description: Unmounting share from nautilus ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Sat Jul 27 15:58:03 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-smb InstallationDate: Installed on 2013-07-20 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=fr_FR LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x7fad3ebbfff1:cmpb $0x0,(%rax) PC (0x7fad3ebbfff1) ok source $0x0 ok destination (%rax) (0x0170) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 ?? () g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run() UpgradeStatus: Upgraded to saucy on 2013-07-20 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1205647/+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 1190602] Re: does not recognize the password
** Changed in: gnome-terminal (Ubuntu) Status: New = Invalid ** No longer affects: xterm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1190602 Title: does not recognize the password Status in “gnome-terminal” package in Ubuntu: Invalid Bug description: Release of Ubuntu:13.10 Package Version: Expected Results: it recognize the password Actual Results: it won't recognize the password Hallo Freshly reinstalled system with reusing the existing separated encrypted home. Gnome-terminal and xterm won't recognize the root password, synaptic update-manager and tty do it, so this is a problem related to the them. Before reinstalling everything was ok. Thanks fabio ProblemType: BugDistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.9.0-5.12-generic 3.9.5 Uname: Linux 3.9.0-5-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Thu Jun 13 15:39:52 2013EcryptfsInUse: YesMarkForUpload: TrueSourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1190602/+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 1228664] [NEW] Trying to unmount a device/share via triangular icon generates a crash
Public bug reported: When trying to unmount a device (external USB stick, Windows partition), or a Samba share from the little triangular icon by simply clicking on it, it generates a crash and the Nautilus window closes. This is not always the case and appears to be intermittent. However, when right-clicking on such a mounted device/share, and selecting Unmount, it always works flawlessly and the Nautilus window stays open. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sat Sep 21 14:50:44 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'958x753+451+138' b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages ** Description changed: When trying to unmount a device (external USB stick, Windows partition), or a Samba share from the little triangular icon by simply clicking on it, it generates a crash and the Nautilus window closes. This is not always the case and appears to be intermittent. However, when right-clicking on such a mounted device/share, and - selecting Unmount, it always works flawlessly and the Nautilys window + selecting Unmount, it always works flawlessly and the Nautilus window stays open. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sat Sep 21 14:50:44 2013 EcryptfsInUse: Yes GsettingsChanges: - b'org.gnome.nautilus.window-state' b'geometry' b'958x753+451+138' - b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' + b'org.gnome.nautilus.window-state' b'geometry' b'958x753+451+138' + b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1228664 Title: Trying to unmount a device/share via triangular icon generates a crash Status in “nautilus” package in Ubuntu: New Bug description: When trying to unmount a device (external USB stick, Windows partition), or a Samba share from the little triangular icon by simply clicking on it, it generates a crash and the Nautilus window closes. This is not always the case and appears to be intermittent. However, when right-clicking on such a mounted device/share, and selecting Unmount, it always works flawlessly and the Nautilus window stays open. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sat Sep 21 14:50:44 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'958x753+451+138' b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1228664/+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 787493] Re: The microphone is muted by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/787493 Title: The microphone is muted by default Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio After I power on my laptop and log in to the (classic) Gnome desktop, my microphone is muted by default. I have to manually unmute it every time upon login. I'm actually not that sure that it's a pulseaudio issue but it's my best bet. laci@nitehawk:~$ lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 laci@nitehawk:~$ apt-cache policy pulseaudio pulseaudio: Installed: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1 Candidate: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1 Version table: *** 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.22+stable-queue-24-g67d18-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/787493/+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 1228222] Re: [sandybridge-m-gt1] GPU lockup IPEHR: 0x79050005 IPEHR: 0x01000000
*** This bug is a duplicate of bug 1140716 *** https://bugs.launchpad.net/bugs/1140716 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228222 Title: [sandybridge-m-gt1] GPU lockup IPEHR: 0x79050005 IPEHR: 0x0100 Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: My GPU in Sandy Bridge based Pentium processor locked up again. I had to reset my laptop, even Magic SysRQ keys didn't worked (I have option in kernel set to support SysRQ keys). ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: i386 Chipset: sandybridge-m-gt1 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 Sep 20 16:22:52 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt1] GPU lockup IPEHR: 0x79050005 IPEHR: 0x0100 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0649] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce GT 620M [1025:064a] InstallationDate: Installed on 2013-09-18 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130917) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Aspire E1-531G MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=f0457e45-8d5b-43a6-adf1-aa45664ab5a7 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt1] GPU lockup IPEHR: 0x79050005 IPEHR: 0x0100 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: XorgConf: Section ServerFlags Option NoTrapSignals true EndSection dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_HR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireE1-531G:pvrV2.07:rvnAcer:rnEA50_HC_HR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire E1-531G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Sep 20 17:29:22 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output XMIR-1 XMIR-2 XMIR-3 xserver.version: 2:1.14.2.901-2ubuntu4 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1228222/+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 1198610] Re: Black screen while trying to disconnect from Bluetooth DUN connection
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1198610 Title: Black screen while trying to disconnect from Bluetooth DUN connection Status in “network-manager” package in Ubuntu: Confirmed Bug description: Hello. The release of Ubuntu I am using: Ubuntu 13.04 The version of the package I am using: 0.9.8.0-0ubuntu6 I am using a Dell Inspiron 5520 laptop. And in order to connect to the Internet, I use my Samsung SGH-L700 phone as a Bluetooth modem. When I try to connect to the Internet via Bluetooth DUN connection using Network Manager applet, there is usually no problem. But when I try to disconnect, What I expect to happen: The connection should be terminated and the system should go on working normally. What happens instead: Suddenly, a black screen with full of text comes up. Sometimes (not always) a panic occurred message with a blinking Caps Lock light can be seen. Additionally, after establishing the connection, the name of the connection isn't viewed on the applet's drop-down menu as it should be. Sometimes there is a strange character, sometimes the text Empty tag, sometimes a text that is not about the connection's name such as org.freedesktop. ... or Connect to a Wi-Fi _network is seen instead of the name. Before reporting this bug, I opened a topic on Ubuntu Turkey Forum. A forum moderator recommended me to file a bug report about network- manager package on Launchpad. So I filed a report here. This is my first bug report. Thanks for possible solutions in advance. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 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.2 Architecture: amd64 Date: Sun Jul 7 08:47:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-25 (72 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.200.1.21 dev ppp0 proto static 169.254.0.0/16 dev ppp0 scope link metric 1000 192.200.1.21 dev ppp0 proto kernel scope link src 176.54.117.54 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Eternet bağlantısı 1 da70e189-6c65-4d1f-b53b-f5fe2792a95b 802-3-ethernet0never yes no /org/freedesktop/NetworkManager/Settings/5 Vodafone Vodafone Internet 1 4e078a89-af38-40da-b417-5c63112ae40e gsm 1372265420 Çrş 26 Haz 2013 19:50:20 EEST nono /org/freedesktop/NetworkManager/Settings/4 Vodafone Vodafone Internet 49a681ee-a7f1-44e1-a73a-1f6a39bce5c9 bluetooth 1373175856 Paz 07 Tem 2013 08:44:16 EEST nono /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH C8:7E:75:0A:BF:14 bluetooth connected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1198610/+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 1198610] Re: Black screen while trying to disconnect from Bluetooth DUN connection
Same apparent problem on a Samsung NP270. The error report is a long list but after the shutdown I do not know where I can find the log. I can easily reproduce the bug, where I can copy the log in order to report here? Thanks Nitto -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1198610 Title: Black screen while trying to disconnect from Bluetooth DUN connection Status in “network-manager” package in Ubuntu: Confirmed Bug description: Hello. The release of Ubuntu I am using: Ubuntu 13.04 The version of the package I am using: 0.9.8.0-0ubuntu6 I am using a Dell Inspiron 5520 laptop. And in order to connect to the Internet, I use my Samsung SGH-L700 phone as a Bluetooth modem. When I try to connect to the Internet via Bluetooth DUN connection using Network Manager applet, there is usually no problem. But when I try to disconnect, What I expect to happen: The connection should be terminated and the system should go on working normally. What happens instead: Suddenly, a black screen with full of text comes up. Sometimes (not always) a panic occurred message with a blinking Caps Lock light can be seen. Additionally, after establishing the connection, the name of the connection isn't viewed on the applet's drop-down menu as it should be. Sometimes there is a strange character, sometimes the text Empty tag, sometimes a text that is not about the connection's name such as org.freedesktop. ... or Connect to a Wi-Fi _network is seen instead of the name. Before reporting this bug, I opened a topic on Ubuntu Turkey Forum. A forum moderator recommended me to file a bug report about network- manager package on Launchpad. So I filed a report here. This is my first bug report. Thanks for possible solutions in advance. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 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.2 Architecture: amd64 Date: Sun Jul 7 08:47:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-25 (72 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.200.1.21 dev ppp0 proto static 169.254.0.0/16 dev ppp0 scope link metric 1000 192.200.1.21 dev ppp0 proto kernel scope link src 176.54.117.54 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Eternet bağlantısı 1 da70e189-6c65-4d1f-b53b-f5fe2792a95b 802-3-ethernet0never yes no /org/freedesktop/NetworkManager/Settings/5 Vodafone Vodafone Internet 1 4e078a89-af38-40da-b417-5c63112ae40e gsm 1372265420 Çrş 26 Haz 2013 19:50:20 EEST nono /org/freedesktop/NetworkManager/Settings/4 Vodafone Vodafone Internet 49a681ee-a7f1-44e1-a73a-1f6a39bce5c9 bluetooth 1373175856 Paz 07 Tem 2013 08:44:16 EEST nono /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH C8:7E:75:0A:BF:14 bluetooth connected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1198610/+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 1227932] Re: Unconfirmed javascript issues in FF 24
Ubuntu 13.04 64 bit. I have the same issue -- 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/1227932 Title: Unconfirmed javascript issues in FF 24 Status in “firefox” package in Ubuntu: Confirmed Bug description: Ubuntu 12.04.2 LTS 32 bit firefox 24.0+build1-0ubuntu0.12.04.1 After automatic-update to FF 24 I can no longer access HULU. When I try to open ANY hulu web page, hulu tells me JavaScript is not enabled. I check FF about:config and the option is set to on FF 23 was working just fine Also 24 had screwed up the AddOn Close All Tabs Reloaded If there any way I can roll back to FF 23 because I can no longer watch any of my TV shows or movies thank to FF 24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1227932/+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 1227932] Re: Unconfirmed javascript issues in FF 24
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New = Confirmed -- 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/1227932 Title: Unconfirmed javascript issues in FF 24 Status in “firefox” package in Ubuntu: Confirmed Bug description: Ubuntu 12.04.2 LTS 32 bit firefox 24.0+build1-0ubuntu0.12.04.1 After automatic-update to FF 24 I can no longer access HULU. When I try to open ANY hulu web page, hulu tells me JavaScript is not enabled. I check FF about:config and the option is set to on FF 23 was working just fine Also 24 had screwed up the AddOn Close All Tabs Reloaded If there any way I can roll back to FF 23 because I can no longer watch any of my TV shows or movies thank to FF 24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1227932/+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 972942] Re: Search field still shows up when switched to another window
** Changed in: nautilus Status: Incomplete = Expired -- 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/972942 Title: Search field still shows up when switched to another window Status in Nautilus: Expired Status in “nautilus” package in Ubuntu: Triaged Bug description: Open any window and then nautilus In nautilus start to type with pops up searchfield in right bottom of nautilus. Switch to other window when searchfiel appears Approowe you see searchfield still in front. Makes to think it is now for other programm. See screenshot ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23 Uname: Linux 2.6.32-40-generic i686 Architecture: i386 Date: Wed Apr 4 01:51:31 2012 InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/972942/+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 1228686] [NEW] X crashes on logout or user switching
Public bug reported: If I try to logout or switch to another user, I am frequently presented with a VT with a blinking cursor. It seems to be about a 50% chance that it will work and do the right thing, and a 50% chance that X dies. I'm on 13.10 saucy daily, 64 bit. dmesg says the following, too, but I haven't found anything else of relevance. [822.442437] HDMI: invalid ELD data byte 68 ** Affects: nvidia-graphics-drivers-319 (Ubuntu) Importance: Undecided Status: New ** Attachment added: Xorg.0.log immediately after the crash https://bugs.launchpad.net/bugs/1228686/+attachment/3833916/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319 in Ubuntu. https://bugs.launchpad.net/bugs/1228686 Title: X crashes on logout or user switching Status in “nvidia-graphics-drivers-319” package in Ubuntu: New Bug description: If I try to logout or switch to another user, I am frequently presented with a VT with a blinking cursor. It seems to be about a 50% chance that it will work and do the right thing, and a 50% chance that X dies. I'm on 13.10 saucy daily, 64 bit. dmesg says the following, too, but I haven't found anything else of relevance. [822.442437] HDMI: invalid ELD data byte 68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1228686/+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 1228689] [NEW] sony vaio pro 13 internal microphone not working
Public bug reported: A number of people are reporting the same issue: http://ubuntuforums.org/showthread.php?t=2172364 I have lived with it for a couple of months silently, but now audio recording is becoming a necessity. I don't have much to add, other than I have gone through the usual troubleshooting and I am willing to provide more info and troubleshoot more if you tell me exactly what you need. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: 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/1228689 Title: sony vaio pro 13 internal microphone not working Status in “pulseaudio” package in Ubuntu: New Bug description: A number of people are reporting the same issue: http://ubuntuforums.org/showthread.php?t=2172364 I have lived with it for a couple of months silently, but now audio recording is becoming a necessity. I don't have much to add, other than I have gone through the usual troubleshooting and I am willing to provide more info and troubleshoot more if you tell me exactly what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+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 1228702] [NEW] Middle Click Doesn't Add to end of Selection
Public bug reported: When you select a block of text and middle click at either the end or the beginning, it doesn't copy the text to the location that was clicked. Instead, it functions as if it were a primary click (left click). Ubuntu 13.04 Gedit 3.6.2-0ubuntu1 ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- 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/1228702 Title: Middle Click Doesn't Add to end of Selection Status in “gedit” package in Ubuntu: New Bug description: When you select a block of text and middle click at either the end or the beginning, it doesn't copy the text to the location that was clicked. Instead, it functions as if it were a primary click (left click). Ubuntu 13.04 Gedit 3.6.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1228702/+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 1040873] Re: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working
echo 1 /sys/class/sound/hwC0D0/reconfig
the side effect of dynamic reconfigure is the driver remove the controls
(1 to 24) except those user space softvol controls (25 to 26), create
the new controls from 27
Alsactl output
!!--
--startcollapse--
state.PCH {
control.25 {
iface MIXER
name 'PCM Playback Volume'
value.0 255
value.1 255
comment {
access 'read write user'
type INTEGER
count 2
range '0 - 255'
tlv '00010008ec140014'
dbmin -5100
dbmax 0
dbvalue.0 0
dbvalue.1 0
}
}
control.26 {
iface MIXER
name 'Digital Capture Volume'
value.0 60
value.1 60
comment {
access 'read write user'
type INTEGER
count 2
range '0 - 120'
tlv '00010008f4480032'
dbmin -3000
dbmax 3000
dbvalue.0 0
dbvalue.1 0
}
}
control.27 {
iface MIXER
name 'Front Playback Volume'
value.0 64
value.1 64
comment {
access 'read write'
type INTEGER
count 2
range '0 - 64'
dbmin -6400
dbmax 0
dbvalue.0 0
dbvalue.1 0
}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1040873
Title:
[N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all:
Subwoofer not working
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
Hi,
this bug is a fork of https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/871808 because #871808 stands for a different hardware
with a different solution, so people may get confused.
Here is a summary (see post #48 to #54 of #871808):
The subwoofer of Asus N56VZ laptop doesn't work out of the box.
#sudo hda-jack-sense-test -a :
*** Without subwoofer:
Pin 0x1e (Black SPDIF Out): present = No
*** With subwoofer:
Pin 0x1e (Black SPDIF Out): present = Yes
http://www.alsa-
project.org/db/?f=2778e7f430aa95ae219d0b2bc3cb5e46abd0a33a
-- There are two ways of making it work:
#1
a. Add to rc.local :
echo 0x1e 0x99130112 /sys/class/sound/hwC0D0/user_pin_configs
echo 1 /sys/class/sound/hwC0D0/reconfig
b. Add options snd-hda-intel model=asus-mode4 in
/etc/modprobe.d/alsa-base.conf
c. Reboot
d. Set the mode to Analog Stereo Output and then to Analog Surround 5.1
output in the sound settings panel. You have to do this each time you reboot!!!
#2
a. Add to rc.local :
echo 0x16 0x99130111 /sys/class/sound/hwC0D0/user_pin_configs
echo 0x1e 0x99130112 /sys/class/sound/hwC0D0/user_pin_configs
echo 1 /sys/class/sound/hwC0D0/reconfig
b. Reboot
c. Set the mode to Analog Stereo Output and then to Analog Surround 5.1
output in the sound settings panel. You have to do this each time you reboot!!!
Both give the same results and fix the bug.
-- Can you make it work out of the box?
There is still two other bugs on this laptop :
- crackling audio when playing with sound volume: see
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040867
- When I put the omputer in sleep mode, there is no way to get sound working
on resume: should I open a new bug to investigate this?
Regards
Sam
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1898 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47'
Mixer name : 'Realtek ALC663'
Components : 'HDA:10ec0663,10431477,0012'
[Desktop-packages] [Bug 1028149] Re: gnome-shell crashed with SIGSEGV in g_cancellable_is_cancelled()
Fixed in raring, leaving it open for quantal. ** Changed in: accountsservice (Ubuntu) Importance: Undecided = Medium ** Changed in: accountsservice (Ubuntu) Status: New = Fix Released ** Also affects: gnome-shell (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Quantal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1028149 Title: gnome-shell crashed with SIGSEGV in g_cancellable_is_cancelled() Status in GNOME Shell: Fix Released Status in “accountsservice” package in Ubuntu: Fix Released Status in “gnome-shell” package in Ubuntu: Confirmed Status in “accountsservice” source package in Quantal: New Status in “gnome-shell” source package in Quantal: New Bug description: I think this happened while unlocking the screen. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-shell 3.5.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 NonfreeKernelModules: openafs nvidia ApportVersion: 2.4-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Mon Jul 23 17:03:03 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1342558406 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/anders SegvAnalysis: Segfault happened at: 0x7f6897144ab9 g_cancellable_is_cancelled+9: movzbl (%rax),%eax PC (0x7f6897144ab9) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_cancellable_is_cancelled (cancellable=0x7f6896ca09a0) at /build/buildd/glib2.0-2.33.6/./gio/gcancellable.c:296 ?? () from /tmp/tmptq8iie/usr/lib/libaccountsservice.so.0 g_simple_async_result_complete (simple=0x48710e0) at /build/buildd/glib2.0-2.33.6/./gio/gsimpleasyncresult.c:775 reply_cb (connection=optimized out, res=0x2e902b0, user_data=user_data@entry=0x48710e0) at /build/buildd/glib2.0-2.33.6/./gio/gdbusproxy.c:2632 g_simple_async_result_complete (simple=0x2e902b0) at /build/buildd/glib2.0-2.33.6/./gio/gsimpleasyncresult.c:775 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1028149/+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 1212337] Re: accounts-daemon crashed with SIGSEGV in dbus_connection_send()
Looks fixed on Raring.
** Changed in: accountsservice (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: accountsservice (Ubuntu)
Importance: Undecided = Medium
** Also affects: accountsservice (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1212337
Title:
accounts-daemon crashed with SIGSEGV in dbus_connection_send()
Status in “accountsservice” package in Ubuntu:
Fix Released
Status in “accountsservice” source package in Precise:
New
Bug description:
Hi. A few weeks ago after log in to the system as a normal user,
'accountservice' (used for querying and manipulating user account
informations) crashed and now it is a regular problem, which happens
all the time -- after every login. I think, that's all what I can
write about this issue, because everything seems to be okay -- no
system freezing etc.
{ additional informations
* ProblemType: Crash
* Architecture: i386
* DistroRelease: Ubuntu 12.04 (Xubuntu 12.04 variant)
* Uname: Linux 3.2.0-51-generic-pae i686
* ApportVersion: 2.0.1-0ubuntu17.4
* NonfreeKernelModules: nvidia
* Package: accountsservice 0.6.15-2ubuntu9.6
* Segfault happened at: 0xb76bb7c3: mov0x10(%eax),%eax
}
Also '/var/log/apport.log' file contain some informations about this
issue. Everything is in a attached log file. I have no ideas, why it
started to happen. Only one thing, which I've done for a few weeks was
'conky-all' install. Nothing more, nothing less - no serious
administrative tasks performed (except e.g. kernel or programs
updates, but it seems to be obvious).
### EDIT: Because this issue still occurs I did some small information
changes about latest Xubuntu update -- from 12.04.2 to 12.04.3
version. Besides next system point update and a new kernel version
informations, I didn't change anything related with this bug when all
of this started to happen. ###
,-[ $ lsb_release -rd ]
| Description:Ubuntu 12.04.3 LTS (with 3.2.0-53.81 Linux kernel)
| Release:12.04
`-
Best regards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1212337/+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 1228724] [NEW] [sandybridge-m-gt1] False GPU lockup IPEHR: 0x79050005
Public bug reported: After a cold start ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Chipset: sandybridge-m-gt1 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 Sep 21 17:08:05 2013 DistUpgraded: 2013-09-14 00:40:14,319 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt1] GPU lockup IPEHR: 0x79050005 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:14c7] InstallationDate: Installed on 2013-09-13 (8 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. X55A MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-8-generic root=UUID=a42aba1e-7946-4997-9dfb-2edbd8d2e204 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt1] False GPU lockup IPEHR: 0x79050005 UpgradeStatus: Upgraded to saucy on 2013-09-13 (8 days ago) UserGroups: dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55A.413 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55A.413:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnX55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Sep 22 00:31:44 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12874 vendor SEC xserver.version: 2:1.14.2.901-2ubuntu4 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 false-gpu-hang freeze saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228724 Title: [sandybridge-m-gt1] False GPU lockup IPEHR: 0x79050005 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: After a cold start ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Chipset: sandybridge-m-gt1 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 Sep 21 17:08:05 2013 DistUpgraded: 2013-09-14 00:40:14,319 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt1] GPU lockup IPEHR: 0x79050005 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc.
[Desktop-packages] [Bug 1228724] Re: [sandybridge-m-gt1] False GPU lockup IPEHR: 0x79050005
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228724 Title: [sandybridge-m-gt1] False GPU lockup IPEHR: 0x79050005 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: After a cold start ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Chipset: sandybridge-m-gt1 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 Sep 21 17:08:05 2013 DistUpgraded: 2013-09-14 00:40:14,319 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt1] GPU lockup IPEHR: 0x79050005 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:14c7] InstallationDate: Installed on 2013-09-13 (8 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. X55A MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-8-generic root=UUID=a42aba1e-7946-4997-9dfb-2edbd8d2e204 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt1] False GPU lockup IPEHR: 0x79050005 UpgradeStatus: Upgraded to saucy on 2013-09-13 (8 days ago) UserGroups: dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55A.413 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55A.413:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnX55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Sep 22 00:31:44 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12874 vendor SEC xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1228724/+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 1228506] Re: Frequent display artifacts, take 2
Which build of Saucy was this issue found in? (beta-1, or one of the daily builds) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228506 Title: Frequent display artifacts, take 2 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Symptoms are the same as in bug https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1221399 For example, see attached photo, replicable 100% just by moving the mouse fast. In bug https://bugs.launchpad.net/xmir/+bug/1218735 I was told to fill a new bug. Note that this Thinkpad has two video cards. I don't know how to tell if Intel or Nvidia is being used. I'm using the default saucy install, no additional drivers. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 21 10:35:28 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f5] NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f5] InstallationDate: Installed on 2013-09-13 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130909) MachineType: LENOVO 2449A22 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=d9f16f85-5511-470f-972f-687054e80e8f ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 2449A22 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET90WW(2.50):bd12/21/2012:svnLENOVO:pn2449A22:pvrThinkPadW530:rvnLENOVO:rn2449A22:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2449A22 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Sep 20 13:38:20 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1228506/+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 1228161] Re: Graphics Adaptor Change fails then works then fails then ...
You're welcome. Marking 'Invalid' since it was more of a support request. If you have problems with the new kernel/X, please file a new bug. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1228161 Title: Graphics Adaptor Change fails then works then fails then ... Status in “xserver-xorg-video-ati” package in Ubuntu: Invalid Bug description: Depending on how you look at it, this may or may not be considered a bug. The problem developed immediately after replacing my graphics adaptor because upgrading to Ubuntu 13.04 failed stating there was a problem with my video. What happens is a bit strange because the problem is self correcting but fails after restarting for reasons that are unclear - to me at least. I think perhaps the system recognizes that it is having problems when it first comes up and then cycles through alternative configurations until it finds one that works; and when I say works, it works perfectly. The scenario is as follows: 1. I start the day by booting up the cold system. It comes up with a screen that though largely correct, is rapidly fluttering back and forth, but no so badly that I can't log in. However logging in then brings up a blank gray screen that is also rapidly fluttering. 2. I then toggle my monitor, keyboard and mouse to my MS Windows 8 box and check email, the news, etc., and after awhile switch back to my fluttering Ubuntu box, still with a fluttering blank gray screen. I then do a hardware reset and switch back to my MS Windows Box and browse the news more in depth this time. Finally after awhile, I switch back to my Ubuntu box and find the screen now is no longer fluttering with my login screen. I login and everything continues to work perfectly. 3. The next day, I start at step 1 again because try as I might, I can't find out how to save the working configuration. There is no Xorg.conf file other than older ones with various suffixes: drwxr-xr-x 2 root root 4096 Oct 22 2012 app-defaults drwxr-xr-x 2 root root 4096 Apr 17 09:28 cursors -rw-r--r-- 1 root root18 Feb 18 2013 default-display-manager drwxr-xr-x 6 root root 4096 Oct 27 2009 fonts -rw-r--r-- 1 root root 17394 Jun 22 2009 rgb.txt lrwxrwxrwx 1 root root13 Nov 1 2009 X - /usr/bin/Xorg drwxr-xr-x 3 root root 4096 Aug 24 2012 xinit drwxr-xr-x 2 root root 4096 Feb 10 2011 xkb -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf-backup-100510190140 -rw-r--r-- 1 root root 269 May 10 2010 xorg.conf.dist-upgrade-201005101857 -rw-r--r-- 1 root root 270 May 10 2010 xorg.conf.failsafe -rwxr-xr-x 1 root root 709 Apr 1 2010 Xreset drwxr-xr-x 2 root root 4096 Jan 17 2013 Xreset.d drwxr-xr-x 2 root root 4096 Jan 17 2013 Xresources -rwxr-xr-x 1 root root 3730 Jun 24 2008 Xsession drwxr-xr-x 2 root root 4096 Jul 4 18:40 Xsession.d -rw-r--r-- 1 root root 265 Jun 24 2008 Xsession.options -rw-r--r-- 1 root root13 Aug 24 2009 XvMCConfig -rw--- 1 root root 601 Oct 27 2009 Xwrapper.config The default-display-manager contains: /usr/sbin/lightdm and /usr/bin/Xorg is some sort of ELF file. Most of the fixes I've found are ones that update xorg.conf but since a system wide search has not located a xorg.conf file, presumably something else is being used. My hardware according to the Asus box is: HD 6450 SILENT/DI/1GD3(LP) the Part No.: 90-C1CQ0F-L0AANAYZ and the serial number: D4C0YZ239187 The lspci command nets out to: 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450] Presumably this will net out to some sort of reconfiguration, or more likely a means to save the currently working configuration (I am, by the way, reporting this bug on the failing box after a number of reboots and hardware resets before finally arriving at the now perfectly operational screen). Any thoughts would be greatly appreciated. If any additional information is needed, let me know and I'll provide it as needed. I've tried to pare down much of the data I've gathered to provide that which I thought to be most meaningful. Thanks Phil ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Fri Sep 20 09:18:20 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to precise on 2013-09-12 (7 days
[Desktop-packages] [Bug 1225793] Re: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem
https://wiki.ubuntu.com/PulseAudio/Log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1225793 Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: New Bug description: No sound from main speakers. Panasonic cf 74. STAC9200 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: helmut01462 F pulseaudio helmut01467 F xfce4-volumed Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe864 irq 46' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,10f7,00102201 HDA:14f12bfa,10f7,0009' Controls : 19 Simple ctrls : 8 Date: Sun Sep 15 17:57:14 2013 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.00L10 dmi.board.name: CF74-2 dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.board.version: 001 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.chassis.version: 001 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L10:bd08/24/2006:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-74ECBAXBM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF74-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001: dmi.product.name: CF-74ECBAXBM dmi.product.version: 002 dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225793/+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 1227791] Re: Saucy_Salamander_Abstract wallpaper conflicts with brand guidelines
** Changed in: ubuntu-wallpapers (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-wallpapers (Ubuntu) Assignee: (unassigned) = Canonical User Experience and Design team (canonical-ux) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1227791 Title: Saucy_Salamander_Abstract wallpaper conflicts with brand guidelines Status in “ubuntu-wallpapers” package in Ubuntu: Confirmed Bug description: In the Saucy Salamander wallpapers set, the image Saucy_Salamander_Abstract_by_José_Vera_alcivar.jpg contains an abstract illustration of a salamander and a slightly tweaked rendering of the Ubuntu logo. The image contains a deep purple, textured background and it is stored as a low quality jpg image. The Ubuntu logo section of the brand guide (http://design.ubuntu.com/brand/ubuntu-logo) lists several specific rules, and we are clearly going against some of those: The circle of friends in this wallpaper is not quite a circle. The logo is not being placed against a brand colour. The logo is not using one of the six available colourways. There is not sufficient empty space between the logo and other elements. In addition, as a result of the compression (and the nature of scaling rendered text in a bitmap, as will always be happening in a background picture), the logo appears fuzzy. There is nothing in particular that says this is off brand, but I'm sure we can agree it is: Ubuntu's logo is sharp and precise, and it should stay that way. Suggested remedies: Get this image as a PNG, relocate the logo with the correct shape and colours, or remove the logo from the image altogether. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1227791/+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 1220277] Re: unity-webapps-amazon overwriting file from unity-webapps-common
Ok, I've removed amazon from the webapps stack. ** Changed in: unity-webapps-amazon (Ubuntu) Status: New = Fix Released ** Changed in: webapps-applications (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webapps-applications in Ubuntu. https://bugs.launchpad.net/bugs/1220277 Title: unity-webapps-amazon overwriting file from unity-webapps-common Status in “unity-webapps-amazon” package in Ubuntu: Fix Released Status in “webapps-applications” package in Ubuntu: Fix Released Bug description: When installing both unity-webapps-common and unity-webapps-amazon, we get the following error in the daily-release check job: /var/log/upstart/otto-setup.log: Selecting previously unselected package unity-webapps-amazon. /var/log/upstart/otto-setup.log: Unpacking unity-webapps-amazon (from .../unity-webapps-amazon_2.4.16daily13.06.20-0ubuntu1_all.deb) ... /var/log/upstart/otto-setup.log: dpkg: error processing /var/cache/apt/archives/unity-webapps-amazon_2.4.16daily13.06.20-0ubuntu1_all.deb (--unpack): /var/log/upstart/otto-setup.log: trying to overwrite '/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json', which is also in package unity-webapps-common 2.4.16+13.10.20130829.2-0ubuntu2 This is blocking the release. More info: https://jenkins.qa.ubuntu.com/job/autopilot-saucy- daily_release/1516/label=autopilot-intel/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-webapps-amazon/+bug/1220277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1225793] Re: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem
no such file From: Raymond 1225...@bugs.launchpad.net To: helm...@yahoo.com Sent: Saturday, September 21, 2013 8:39 PM Subject: [Bug 1225793] Re: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem https://wiki.ubuntu.com/PulseAudio/Log -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1225793 Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225793/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1225793 Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: New Bug description: No sound from main speakers. Panasonic cf 74. STAC9200 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: helmut01462 F pulseaudio helmut01467 F xfce4-volumed Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe864 irq 46' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,10f7,00102201 HDA:14f12bfa,10f7,0009' Controls : 19 Simple ctrls : 8 Date: Sun Sep 15 17:57:14 2013 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.00L10 dmi.board.name: CF74-2 dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.board.version: 001 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.chassis.version: 001 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L10:bd08/24/2006:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-74ECBAXBM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF74-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001: dmi.product.name: CF-74ECBAXBM dmi.product.version: 002 dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1225793] Re: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem
I tried to alter this file with no luck at all...Ugh From: Raymond 1225...@bugs.launchpad.net To: helm...@yahoo.com Sent: Friday, September 20, 2013 11:20 PM Subject: [Bug 1225793] Re: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem the pulseaudio verbose show you how PA make up Ports: analog-output: Analog Output (priority: 9900) Active Port: analog-output change the volume control from the selected the output.conf http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/alsa/mixer/paths /sys/class/sound/hwC0D0/init_pin_configs: 0x08 0x70c00170 [N/A] SPDIF In at Oth N/A 0x09 0x70400180 [N/A] SPDIF Out at Oth N/A 0x10 0x30210020 [Jack] HP Out at Oth N/A Conn = 1/8, Color = Unknown DefAssociation = 0x2, Sequence = 0x0, Misc = 0x00 0x0e 0x90170110 [Fixed] Speaker at Int N/A Conn = Analog, Color = Unknown DefAssociation = 0x1, Sequence = 0x0, Misc = NO_PRESENCE 0x0f 0x70800130 [N/A] Line In at Oth N/A 0x10 0x30a10040 [Jack] Mic at Oth N/A Conn = 1/8, Color = Unknown DefAssociation = 0x4, Sequence = 0x0, Misc = 0x0 0x11 0x70100160 [N/A] Speaker at Oth N/A 0x12 0x70300150 [N/A] CD at Oth N/A -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1225793 Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225793/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1225793 Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: New Bug description: No sound from main speakers. Panasonic cf 74. STAC9200 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: helmut01462 F pulseaudio helmut01467 F xfce4-volumed Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe864 irq 46' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,10f7,00102201 HDA:14f12bfa,10f7,0009' Controls : 19 Simple ctrls : 8 Date: Sun Sep 15 17:57:14 2013 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.00L10 dmi.board.name: CF74-2 dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.board.version: 001 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.chassis.version: 001 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L10:bd08/24/2006:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-74ECBAXBM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF74-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001: dmi.product.name: CF-74ECBAXBM dmi.product.version: 002 dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1225793] Re: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem
I just loaded the new audio driver and still so speaker option in pulse audio mixer. From: Raymond 1225...@bugs.launchpad.net To: helm...@yahoo.com Sent: Saturday, September 21, 2013 8:39 PM Subject: [Bug 1225793] Re: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem https://wiki.ubuntu.com/PulseAudio/Log -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1225793 Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225793/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1225793 Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: New Bug description: No sound from main speakers. Panasonic cf 74. STAC9200 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: helmut01462 F pulseaudio helmut01467 F xfce4-volumed Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe864 irq 46' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,10f7,00102201 HDA:14f12bfa,10f7,0009' Controls : 19 Simple ctrls : 8 Date: Sun Sep 15 17:57:14 2013 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [CF-74ECBAXBM, SigmaTel STAC9200, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.00L10 dmi.board.name: CF74-2 dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.board.version: 001 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.chassis.version: 001 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L10:bd08/24/2006:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-74ECBAXBM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF74-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001: dmi.product.name: CF-74ECBAXBM dmi.product.version: 002 dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225793/+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 1228689] Re: sony vaio pro 13 internal microphone not working
https://wiki.ubuntu.com/Audio/AlsaInfo https://wiki.ubuntu.com/PulseAudio/Log pactl list ** Changed in: pulseaudio (Ubuntu) Status: New = Incomplete -- 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/1228689 Title: sony vaio pro 13 internal microphone not working Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: A number of people are reporting the same issue: http://ubuntuforums.org/showthread.php?t=2172364 I have lived with it for a couple of months silently, but now audio recording is becoming a necessity. I don't have much to add, other than I have gone through the usual troubleshooting and I am willing to provide more info and troubleshoot more if you tell me exactly what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+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 787493] Re: The microphone is muted by default
https://wiki.ubuntu.com/Audio/AlsaInfo https://wiki.ubuntu.com/PulseAudio/Log pactl list ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = Incomplete -- 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/787493 Title: The microphone is muted by default Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: Binary package hint: pulseaudio After I power on my laptop and log in to the (classic) Gnome desktop, my microphone is muted by default. I have to manually unmute it every time upon login. I'm actually not that sure that it's a pulseaudio issue but it's my best bet. laci@nitehawk:~$ lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 laci@nitehawk:~$ apt-cache policy pulseaudio pulseaudio: Installed: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1 Candidate: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1 Version table: *** 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.22+stable-queue-24-g67d18-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/787493/+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 1227795] Re: [P5Q DELUXE, Analog Devices AD1989B, Other SPDIF Out, Rear] No sound at all
http://www.intel.com/support/motherboards/desktop/sb/CS-032871.htm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1227795 Title: [P5Q DELUXE, Analog Devices AD1989B, Other SPDIF Out, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: i'm new with linux. i've got a nvidia gtx 260 and a dvi adaptar to connect with hdmi to my amplifier. this works perfectly on windows but not with linux. also i tried an coax cable to connect the desktop with the amplifier but also no sound. i tried a few solutions like changing to 5.1 multichannel but nothing worked. what confuses me ist that the device is always analog and not digital. it should be digital i guess but i have no idea how to change it help is very much apprechiated ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johannes 2098 F pulseaudio /dev/snd/pcmC0D0p: johannes 2098 F...m pulseaudio Date: Thu Sep 19 18:37:11 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johannes 2098 F pulseaudio /dev/snd/pcmC0D0p: johannes 2098 F...m pulseaudio Symptom_Jack: Other SPDIF Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [P5Q DELUXE, Analog Devices AD1989B, Other SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to raring on 2013-09-19 (0 days ago) dmi.bios.date: 12/11/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1702:bd12/11/2008:svnSystemmanufacturer:pnP5QDELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q DELUXE dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1227795/+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 1228689] Re: sony vaio pro 13 internal microphone not working
Thank you for the quick reply. Attached is the output of pactl list however the two URLs that you pointed me to say This page does not exist yet. You can create a new empty page, or use one of the page templates. ** Attachment added: output of pactl list as requested https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+attachment/3834166/+files/pactl_list.txt ** Changed in: pulseaudio (Ubuntu) Status: Incomplete = 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/1228689 Title: sony vaio pro 13 internal microphone not working Status in “pulseaudio” package in Ubuntu: New Bug description: A number of people are reporting the same issue: http://ubuntuforums.org/showthread.php?t=2172364 I have lived with it for a couple of months silently, but now audio recording is becoming a necessity. I don't have much to add, other than I have gone through the usual troubleshooting and I am willing to provide more info and troubleshoot more if you tell me exactly what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+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 1228689] Re: sony vaio pro 13 internal microphone not working
Correction: the two URLs had a %E2%80%8E at the end when clicked. Once removed, I got to the inteded destinations and followed the instructions. http://www.alsa- project.org/db/?f=cfb15d2374ed789c7543388ae242666a06488c51 log coming next. -- 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/1228689 Title: sony vaio pro 13 internal microphone not working Status in “pulseaudio” package in Ubuntu: New Bug description: A number of people are reporting the same issue: http://ubuntuforums.org/showthread.php?t=2172364 I have lived with it for a couple of months silently, but now audio recording is becoming a necessity. I don't have much to add, other than I have gone through the usual troubleshooting and I am willing to provide more info and troubleshoot more if you tell me exactly what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+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 1163107] Re: Wacom calibration results are off (wrong area)
Josh's workaround through dconf will work for me, but once I restart my computer the calibration will return to being completely off. I have a Lenovo X230 tablet. This means that everytime I want to use the stylus I have to manually reset via the terminal. -- 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/1163107 Title: Wacom calibration results are off (wrong area) Status in GNOME Control Center: New Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: When I try to calibrate the touchscreen on my laptop (HP EliteBook 2760p, Wacom Serial Tablet WACf004) the result gets worse and worse with every calibration. The area on which the touchscreen is effective becomes smaller every time to the point where it is completely unusable. This can be verified with xsetwacom --get 15 area, right now this gives me -9978 -6651 6336 -4878. I can reset this by manually setting a new area, e.g. xsetwacom --set 15 area 0 0 25000 16000 However, xsetwacom only works for the current session, after a reboot all information is lost and the calibration is off again. What should happen: the area for the touchscreen is improved with calibrating What happens instead: the area gets smaller for every calibration I'd be happy to contribute a bit in fixing this bug, but my knowledge is limited. Meanwhile, I'd appreciate a workaround: how can I reset the area used for the touchscreen to the default? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 14:19:57 2013 InstallationDate: Installed on 2013-03-20 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True 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-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.04.01-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1163107/+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 1228689] Re: sony vaio pro 13 internal microphone not working
I was following the instructions in https://wiki.ubuntu.com/PulseAudio/Log at the killall command, the computer prompted that an error occured and asked me to report it. It also promted that /etc/xdg/autostart/pulseaudio.desktop has been modified I am using Lubuntu 13.10 -- 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/1228689 Title: sony vaio pro 13 internal microphone not working Status in “pulseaudio” package in Ubuntu: New Bug description: A number of people are reporting the same issue: http://ubuntuforums.org/showthread.php?t=2172364 I have lived with it for a couple of months silently, but now audio recording is becoming a necessity. I don't have much to add, other than I have gone through the usual troubleshooting and I am willing to provide more info and troubleshoot more if you tell me exactly what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+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 1223181] Re: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+2.0 (Ubuntu) Status: New = Confirmed -- 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/1223181 Title: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: to reproduce, I open the Variables view in eclipse and step through the application. the eclipse jvm crashes with: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912 # # JRE version: 7.0_21-b11 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-x11-2.0.so.0+0x2202aa] gtk_tree_view_get_background_area+0x8a # # Core dump written. Default location: /home/juergen/core or core.11567 # # An error report file with more information is saved as: # /home/juergen/hs_err_pid11567.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # This did not happen in ubuntu 13.04. using KDE as a desktop (installed ubuntu, installed kde packages) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk2.0-0 2.24.20-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Tue Sep 10 07:25:17 2013 InstallationDate: Installed on 2010-11-24 (1020 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/+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 1228689] Re: sony vaio pro 13 internal microphone not working
the information about the killall prompted error is in bug 1228759 -- 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/1228689 Title: sony vaio pro 13 internal microphone not working Status in “pulseaudio” package in Ubuntu: New Bug description: A number of people are reporting the same issue: http://ubuntuforums.org/showthread.php?t=2172364 I have lived with it for a couple of months silently, but now audio recording is becoming a necessity. I don't have much to add, other than I have gone through the usual troubleshooting and I am willing to provide more info and troubleshoot more if you tell me exactly what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+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 1228689] Re: sony vaio pro 13 internal microphone not working
Here is the log. Got the SIGABRT error again when pressing CTRL+C to terminate the logging. ** Attachment added: pulseverbose.log https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+attachment/3834212/+files/pulseverbose.log -- 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/1228689 Title: sony vaio pro 13 internal microphone not working Status in “pulseaudio” package in Ubuntu: New Bug description: A number of people are reporting the same issue: http://ubuntuforums.org/showthread.php?t=2172364 I have lived with it for a couple of months silently, but now audio recording is becoming a necessity. I don't have much to add, other than I have gone through the usual troubleshooting and I am willing to provide more info and troubleshoot more if you tell me exactly what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+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 1228765] [NEW] Need to implement DisplayConfig dbus interface within Unity
Public bug reported: For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such it seems the cleanest solution would be to copy the display config interface from Mutter into Unity. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. ** Affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1228765 Title: Need to implement DisplayConfig dbus interface within Unity Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such it seems the cleanest solution would be to copy the display config interface from Mutter into Unity. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1228765/+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 1027202] Re: Does not connect (to wired network) after suspend
I'm also seeing this on saucy on a gigabyte ga-965p-dq6 motherboard with a marvell 88e8056 gige controller. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1027202 Title: Does not connect (to wired network) after suspend Status in “network-manager” package in Ubuntu: Triaged Bug description: I work with Xubuntu 12.04 on a MacBook Air 4,1. I can easily connect to the internet (wired network / auto ethernet), but after I put the laptop to sleep/suspend, nm-applet is gray and I can't connect to the internet anymore. Rebooting solves the problem. This seemed to be related up to the fact that it was a wireless connection (which always worked fine for me): https://bugs.launchpad.net/ubuntu/+source /network-manager-applet/+bug/704756 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Fri Jul 20 20:33:05 2012 EcryptfsInUse: Yes InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 178.83.94.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 178.83.94.0/23 dev eth1 proto kernel scope link src 178.83.94.48 metric 1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 eth2 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled disabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1027202/+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
