[Solved] "cannot open display" after suspend/resume, possibly broadcom

Hey peoples,
[EDIT: I think my initial assumptions are incorrect, this issue seems to be occurring independently of whatever wifi driver I have loaded]
I'm finding that after suspend/resume my machine will not open any new windows. The windows that were already open continue to function. If I've left a terminal open, and attempt to open a new window I get the message:
[framps@localhost ~]$ firefox
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0.0
I've found that removing the broadcom-wl driver from my system seems to fix the issue. I can't see anything particularly obvious in my dmesg. I think I need the broadcom-wl driver as I have not been able to get b43 or bcma to work for my machine.
[  948.814261] cfg80211: World regulatory domain updated:
[  948.814266] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  948.814269] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  948.814272] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  948.814275] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  948.814277] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  948.814280] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  949.404722] r8169 0000:0c:00.0 eth0: link down
[  949.404741] r8169 0000:0c:00.0 eth0: link down
[  949.404773] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  949.355635] PM: Syncing filesystems ... done.
[  949.717960] PM: Preparing system for mem sleep
[  949.851316] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  949.862059] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[  949.875377] PM: Entering mem sleep
[  949.875472] Suspending console(s) (use no_console_suspend to debug)
[  950.064255] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 1 ep 0 with no TDs queued?
[  950.064507] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  950.075138] sd 0:0:0:0: [sda] Stopping disk
[  950.165918] ERROR @wl_notify_scan_status : Scan complete while device not scanning
[  950.477845] i915 0000:00:02.0: power state changed by ACPI to D3hot
[  950.551140] PM: suspend of devices complete after 676.056 msecs
[  950.551485] PM: late suspend of devices complete after 0.342 msecs
[  950.567669] r8169 0000:0c:00.0: wake-up capability enabled by ACPI
[  950.581418] ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
[  950.594384] ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
[  950.620974] xhci_hcd 0000:00:14.0: wake-up capability enabled by ACPI
[  950.634321] PM: noirq suspend of devices complete after 82.939 msecs
[  950.634762] ACPI: Preparing to enter system sleep state S3
[  950.730816] PM: Saving platform NVS memory
[  950.736910] Disabling non-boot CPUs ...
[  950.738461] smpboot: CPU 1 is now offline
[  950.840631] smpboot: CPU 2 is now offline
[  950.943831] smpboot: CPU 3 is now offline
[  950.944231] Extended CMOS year: 2000
[  950.945389] ACPI: Low-level resume complete
[  950.945427] PM: Restoring platform NVS memory
[  950.945811] Extended CMOS year: 2000
[  950.945864] Enabling non-boot CPUs ...
[  950.949268] smpboot: Booting Node 0 Processor 1 APIC 0x1
[  950.963117] CPU1 is up
[  950.966520] smpboot: Booting Node 0 Processor 2 APIC 0x2
[  950.980330] CPU2 is up
[  950.980386] smpboot: Booting Node 0 Processor 3 APIC 0x3
[  950.994238] CPU3 is up
[  950.997398] ACPI: Waking up from system sleep state S3
[  951.471580] i915 0000:00:02.0: power state changed by ACPI to D0
[  951.498111] xhci_hcd 0000:00:14.0: wake-up capability disabled by ACPI
[  951.524753] ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
[  951.551380] ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
[  951.564744] nvidia 0000:01:00.0: power state changed by ACPI to D0
[  951.591567] PM: noirq resume of devices complete after 120.295 msecs
[  951.591837] PM: early resume of devices complete after 0.236 msecs
[  951.591891] i915 0000:00:02.0: setting latency timer to 64
[  951.591894] xhci_hcd 0000:00:14.0: setting latency timer to 64
[  951.591968] mei 0000:00:16.0: irq 43 for MSI/MSI-X
[  951.591983] ehci_hcd 0000:00:1a.0: setting latency timer to 64
[  951.592037] ehci_hcd 0000:00:1d.0: setting latency timer to 64
[  951.592108] ahci 0000:00:1f.2: setting latency timer to 64
[  951.592119] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
[  951.594182] r8169 0000:0c:00.0: wake-up capability disabled by ACPI
[  951.634511] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
[  951.636110] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[  951.796066] r8169 0000:0c:00.0 eth0: link down
[  951.824070] Extended CMOS year: 2000
[  951.831119] usb 3-1.3: reset full-speed USB device number 3 using ehci_hcd
[  951.910921] ata5: SATA link down (SStatus 0 SControl 300)
[  951.916168] btusb 3-1.3:1.0: no reset_resume for driver btusb?
[  951.916171] btusb 3-1.3:1.1: no reset_resume for driver btusb?
[  951.924226] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  951.926030] ata2.00: configured for UDMA/100
[  951.981369] usb 4-1.6: reset high-speed USB device number 3 using ehci_hcd
[  952.876326] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  952.877743] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[  952.877747] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[  952.877750] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  952.880489] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[  952.880493] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[  952.880496] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  952.881600] ata1.00: configured for UDMA/100
[  952.893105] sd 0:0:0:0: [sda] Starting disk
[  952.911681] PM: resume of devices complete after 1321.544 msecs
[  952.912745] PM: Finishing wakeup.
[  952.912748] Restarting tasks ... done.
[  953.018321] video LNXVIDEO:00: Restoring backlight state
[  953.018862] video LNXVIDEO:01: Restoring backlight state
[  953.376503] r8169 0000:0c:00.0 eth0: link up
[  953.376515] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Any help would be greatly appreciated. Thanks.
Last edited by frampy (2013-03-16 01:20:57)

It seems that the only option for my  wifi card, BCM43228 is the proprietary broadcom-wl.
Can anyone suggest how I might be able to get any debugging information for this module? Maybe this driver is conflicting with something else on my system, as I can't find anyone else that is seeing this same issue.
Very frustrating, my machine is a Thinkpad Edge E530. Because I ordered from New Zealand there was no option to include the alternative Intel card and I was stuck with the broadcom. Apparently there's a whitelist on the BIOS aswell which will prevent me from installing another card.

Similar Messages

  • [SOLVED] Cannot open display: . Problem from Terminal

    Hi,
    I have a small problem with X I guess. I hope you can help me, as extensive googleling did not help.
    I'm just configuring my arch install (newbie). Everything I have configured so far works great, the documentation is really good. I can start my xfce sessions an everything. However, I just wanted to look something up, when
    $ xfce4-about
    printed the following error:
    xfce4-about: Cannot open display: .
    This happened from terminal, not within a xfce-session.
    Does anyone have an idea how I should proceed to eliminate this minor problem?
    Thanks for your help in advance.
    Last edited by jared (2012-02-22 04:38:21)

    Seems you can't run xfce4-about from the non-X terminal, just like you can't run firefox.

  • [Solved] Cannot open display :0.0

    Yup, the xhost thing fixed it (although I had to use localhost rather than local).  Thanks!
    I sometimes use secondary accounts by way of profile control, that is if I want to try programs with different settings I'll su to a different shell account.  Up until this week when I upgraded to the latest everything, I could open an xterm, su to my secondary login, and start firefox or whatever just fine.
    Now suddenly I can't do that; I get two lines of
    No protocol specified
    and then
    Error: Cannot open display:  :0.0
    And one more
    No protocol specified
    I'm sure it's a permissions issue, and probably fixes a security hole from previous versions; root can still do this but not my non-root accounts.  Any idea which device files I need to modify to allow account B to open a window on account A's desktop?
    Last edited by WyoPBS (2011-12-29 04:15:59)

    try
    xhost +local:
    in your primary account.
    Also check these topics:
    https://bbs.archlinux.org/viewtopic.php?id=45941
    https://bbs.archlinux.org/viewtopic.php?id=122848

  • [SOLVED] Vaio power usage after suspend/resume cycle

    Hi,
    I came to the conclusion my laptop (Sony Vaio VPCSB36FG/B) suffers from one particular issue:
    After a suspend/resume cycle, the discrete card in the laptop (Radeon HD6470M) is powered on again, although /sys/kernel/debug/vgaswitcheroo/switch still reports the contrary.
    This explains why the laptop is using ~5W more after a suspend/resume cycle. I can blacklist the radeon module on boot, but then the discrete card is powered on when the laptop is started. And since the module is blacklisted, there is no way to disable the card using vgaswitcheroo.
    Unfortunately, blacklisting the module (on boot) and manually loading the module after boot, then switching the card off (using vgaswitcheroo) and removing the module results in either a display driver crash or the message: "radeon module is in use".
    For the record, I'm using the open source driver for both cards (i915 & radeon).
    My guess is, the only way to prevent the card from being powered on after a suspend/resume cycle is to make sure the radeon module is not enabled at all before suspending the laptop, but I'm wondering how to achieve this.
    Any suggestions please?
    Last edited by LordChaos73 (2013-01-16 20:48:21)

    Okay, this workaround seems to work, at least manually:
    1. Before suspending, the discrete card should be powered on (suspending seems to be a little slower now):
    echo ON > /sys/kernel/debug/vgaswitcheroo/switch
    2. After resume, one is able to turn off the discrete again:
    echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
    Now I just need to figure out how to automate this in a nicely fashion.
    Last edited by LordChaos73 (2013-01-16 20:49:06)

  • Gtk-WARNING **: cannot open display [Solved]

    Hello,
    I've just installed openbox and experimenting with it. But I'am unable to run any panel. Ive already install lxpanel, fbpanel, plank, but each time I try to launch them from the terminal I get the same error massages. Firefox, leafpad, terminal, all launch properly, only the panels I can't make them run. Any idea how to solve this?
    [mak@myhost ~]$ fbpanel
    (fbpanel:688): Gtk-WARNING **: cannot open display:
    [mak@myhost ~]$
    [mak@myhost ~]$ plank
    [INFO 19:09:21.484514] [AbstractMain:170] Plank version: 0.7.1
    [INFO 19:09:21.484627] [AbstractMain:171] Kernel version: 3.17.6-1-ARCH
    [INFO 19:09:21.484704] [AbstractMain:172] GLib version: 2.42.1
    [INFO 19:09:21.484784] [AbstractMain:173] GTK+ version: 3.14.6
    [INFO 19:09:21.484850] [AbstractMain:175] + HiDPI support enabled
    [INFO 19:09:21.484915] [AbstractMain:177] Wnck version: 3.4.9
    [INFO 19:09:21.485001] [AbstractMain:178] Cairo version: 1.14.0
    [INFO 19:09:21.485081] [AbstractMain:179] Pango version: 1.36.8
    Unable to init server: Could not connect: Connection refused
    [WARN 19:09:21.493039] [Gtk] cannot open display:
    [mak@myhost ~]$
    Last edited by jmak (2014-12-19 00:25:02)

    karol wrote:
    The display should be set on its own. It's
    $ echo $DISPLAY
    :0
    for my first X server and
    $ echo $DISPLAY
    :1
    for the other one I'm running.
    How exactly do you start X?
    I start manually,
    startx

  • [Solved]no sound after suspend/resume after kernel 3.9.2 upgrade

    I don't know  what to provide to help solve this problem. Leave me messages.Thank you!
    Last edited by chu887 (2013-06-06 08:54:16)

    johni wrote:
    I got mine working!
    First I commented out the module parameter from my /etc/modprobe.d//intel-hda-audio.conf:
    #options snd-hda-intel model=dell-eq
    Since it works without that now, I will probably remove the file.
    Next, I went into alsamixer, and noticed a couple items not there before, turned down low:
    "Speaker", and two "HeadPhone" mixers, both turned down almost off.  I turned up the volume on the speaker, and was able to get sound from the speakers.   The same worked for the headphone entries (I have two headphone jacks).
    After I did this, it works better than before because I used to only have one working headphone jack.
    Also, I confirmed sound is still working after suspend/resume for me.
    Hopefully this will help one of you.
    Thanks,the problem has been resolved by downgrade.
    Sound is absolutely normal before I suspend/resume my system,  volume is normal, not too large,not too little. But there's no sound at all after resume it .  I guess it's probably to have something to do with our audio card - HDA intel,  my computer is also a dell laptop( dell 1420 , 2007/2008, really old ).
    My advice is : don't upgrade to kernel 3.9.2 ,it's an odd version( odd version is not stable).

  • [SOLVED] Chromuim: Gtk-WARNING **: cannot open display:

    I've just tried to install chromium, but the program doesn't start.
    From terminal I recieve this:
    [7183:7183:4023157347:FATAL:chrome/browser/browser_main.cc(537)] Check failed: profile. Cannot get default profile.
    Abortito
    trying as root:
    [federico@giunta-desktop ~]$ su
    Password:
    [root@giunta-desktop federico]# chromium
    No protocol specified
    (chromium:7209): Gtk-WARNING **: cannot open display: :0
    How can I fix this problem?
    Last edited by FeDiX 91 (2010-09-02 16:47:46)

    FeDiX 91 wrote:
    i found a sort of fix to this problem, but I have to repeat it ever time i launch the app...
    This is the link: [lnk]http://ubuntuforums.org/archive/index.php/t-166863.html[/lnk]
    another question which han nothing to do whith this... are there some shortcuts in this site for html codes? thanks
    Using xhost+ creates automatically a security problem for Xorg, do NOT do that.

  • [XFCE]Keyboard layout config sometimes gets reset after suspend/resume

    After I got suspend/resume working thanks to the help here, I have still another little problem with it: After suspend/resume the keyboard layout configuration in the corresponding xfce-panel plugin is sometimes reset to US. The keyboard layout should be Russian/German with switching the layouts with LCtrl+LShift. In the xorg.conf everything is fine, but it seems to be disregarded:
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "de,ru"
    Option "XkbVariant" ",winkeys"
    Option "XkbOptions" "grp:ctrl_shift_toggle"
    EndSection
    The settings that I make in the panel-applet via its configuration dialogue work though, but they sometimes get reset after a suspend/resume.
    The XFCE session is started via following command in ~/.xinitrc:
    exec ck-launch-session dbus-launch xfce4-session
    Thanks for any hint,
    PhotonX

    I see. Then you should maybe add debug output to check whether the script is run at all and if yes, where it fails. Like
    button/lid)
    echo "lid action caught" >> /home/lid.log
    case "$3" in
    close)
    logger 'LID closed'
    # Suspend and lock the screen
    /usr/sbin/pm-suspend &
    DISPLAY=:0.0 su -c - miki /usr/bin/slimlock
    echo "lid closed" >> /home/lid.log
    open)
    logger 'LID opened'
    # Set the keyboard layout again on IT
    setxkbmap it
    echo "lid opened" >> /home/lid.log
    logger "ACPI action undefined: $3"
    echo "something wrong happened" >> /home/lid.log
    esac
    and then check /home/lid.log after lid close&open.

  • X or GDM dies after suspend/resume (Nvidia card)

    For a while now (about a month, I think), X seems to crash after suspend/resume and I end up back on the GDM login screen.
    The problem is intermittent, but I'd say it happens about 50% of the time. As can be seen in the log below, after a while a new gdm-x-session replaces the one that was running before suspend.
    Any ideas? I'm stuck.
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:77
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:78
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 226:0
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:68
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:64
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:79
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:67
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:65
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got pause for 13:66
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) config/udev: removing device X10 WTI RF receiver mouse
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) evdev: X10 WTI RF receiver mouse: Close
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) UnloadModule: "evdev"
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: releasing fd for 13:78
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (EE) systemd-logind: failed to release device: Did not receive a reply. Possible causes include: the remote application did not send a reply, the messag
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:77
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: Failed to close file descriptor: Could not close fd 23
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 226:0
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0"
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): configuration option may not be set correctly. When the
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(0): Config Options in the README.
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(GPU-0): Display (Medion MD30422PV (DFP-0)) does not support NVIDIA 3D
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) NVIDIA(GPU-0): Vision stereo.
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:68
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:64
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:79
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:67
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:65
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) systemd-logind: got resume for 13:66
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) config/udev: removing device X10 WTI RF receiver
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[7021]: (II) evdev: X10 WTI RF receiver: Close
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) config/udev: removing device X10 WTI RF receiver mouse
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) evdev: X10 WTI RF receiver mouse: Close
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) UnloadModule: "evdev"
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) config/udev: removing device X10 WTI RF receiver
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) evdev: X10 WTI RF receiver: Close
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) UnloadModule: "evdev"
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) config/udev: Adding input device X10 WTI RF receiver mouse (/dev/input/mouse2)
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) No input driver specified, ignoring this device.
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) This device may have been added with another device file.
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) config/udev: Adding input device X10 WTI RF receiver mouse (/dev/input/event14)
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (**) X10 WTI RF receiver mouse: Applying InputClass "evdev pointer catchall"
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) systemd-logind: returning pre-existing fd for /dev/input/event14 13:78
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) Using input driver 'evdev' for 'X10 WTI RF receiver mouse'
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (**) X10 WTI RF receiver mouse: always reports core events
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (**) evdev: X10 WTI RF receiver mouse: Device: "/dev/input/event14"
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (--) evdev: X10 WTI RF receiver mouse: Vendor 0xbc7 Product 0x6
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (--) evdev: X10 WTI RF receiver mouse: Found 9 mouse buttons
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (--) evdev: X10 WTI RF receiver mouse: Found relative axes
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (--) evdev: X10 WTI RF receiver mouse: Found x and y relative axes
    May 06 09:54:00 myhost /usr/lib/gdm/gdm-x-session[20001]: (II) evdev: X10 WTI RF receiver mouse: Configuring as mouse

    I waited a couple of days, tried suspending again and now things work as they should, or at least they appear to.
    I have no idea what has changed.

  • Cannot open mail after upgrading to leopard

    I cannot open mail after I upgraded to leopard. I keep getting this message that "mail has unexpectadly quit. I have sent reports to apple. Does anyone have any suggestions?

    5.1.4 will solve the compatibility issue, however, it is no longer available from Apple -you would have to find a copy on Ebay or similar. The current version is FCP 6 -part of Final Cut Studio 2.
    Going back to Tiger will also solve it and will not cost anything, apart from the time spent reinstalling.
    Unless there is some feature in Mac OS X 10.5 that you really need, this would be the easiest way to get FCP running again.

  • Cannot open display error MATE

    I installed MATE alongside XFCE but when I try to open MATE after I login at boot it just comes up with the error Cannot open display and it then exits?
    I used the command:
    exec mate-session
    to try and start MATE.
    Thanks
    Al.
    PS I've you need any more details about my system just ask.

    Thats what I added to ~/.xinitrc as per the wiki.
    #!/bin/sh
    # ~/.xinitrc
    #Executed by startx (run your window manager from here)
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    exec ck-launch-session mate-session
    # exec gnome-session
    # exec startkde
    # exec startxfce4
    # ...or the Window Manager of your choice

  • Loosing X ... 'Error: cannot open display: localhost:11.0'

    Hello, I hope some may be able to help me finding a solution to this X related problem.
    Before Lion everything worked as expected.
    From a terminal I
    ssh -X user@linuxbox
    and it work as expected... all the X application come back to my Mac.
    but after a while (generaly not long ... about 5 to 10 min)
    I cannot launch any X application anymore.
    within my Terminal I get "Error: cannot open display: localhost:11.0"
    and  on the linuxbox side I get " sshd[xxxx]: channel 4: open failed: administratively prohibited: open failed"
    Running 10.7.1. fully updated (from my 10.6.8 Mac I do not have this problem
    ... and never had)
    Thanks in advance for your help
    PhS

    'arch' is set as the alias for localhost.  I never entered 'arch' anyway, that's just what the error said.
    e:  I tried ssh-ing into a X session on another laptop running an Ubuntu live CD.  I can ssh into it normally, but when I run 'xinit -e ssh -XCT [email protected] gnome-session -- :1' it just starts a new X session on ctrl+alt+F8 using my startx file, rather than the one on the other computer.
    Last edited by Yes (2008-07-11 19:17:28)

  • OS X - Fix for wifi disconnect after suspend/resume

    OS X - Fix for wifi disconnect after suspend/resume
    I've purchased a Mac recently and since upgrading to Maverick have been having some problem with wifi after suspend/resume. Looking into the issue, I've found this thread: https://discussions.apple.com/thread/5495375 and some people have reported that turning off bluetooth did fix the issue.
    For my case, this was not possible, so I've tried to make a little fix, that disable bluetooth on suspend and enable it on wake, but with a 10 seconds delay, in order to let the wifi connect successfully.
    Here is my github repo for anyone to look at the code: https://github.com/Setsuna666/osx-wifibtfix
    Here is the latest version of the fix, which include an uninstall script: https://github.com/Setsuna666/osx-wifibtfix/archive/v1.0.2.zip
    If you have any questions or issues, please post it here so it can be easier for me to keep track of.

    Installed properly this time:
    It appears to work, when I resume from sleep the Bluetooth icon is off (gray) and wifi connects, after 10s Bluetooth icon comes on again. 
    Here is the correct output:
    Antzcrashing-MacBook-Air:osx-wifibtfix-1.0.3 Antzcrashing$ sudo bash install.sh
    Password:
    Installing Wifi/BT fix by Setsuna666...
    Downloading SleepWatcher...
    Downloading file from http://www.bernhard-baehr.de/sleepwatcher_2.2.tgz...
    % Total    % Received % Xferd  Average Speed   Time Time     Time  Current
                                     Dload  Upload Total   Spent    Left Speed
    100 43385  100 43385 0     0  28567 0  0:00:01  0:00:01 --:--:-- 28580
    Extracting SleepWatcher...
    x ./sleepwatcher_2.2/
    x ./sleepwatcher_2.2/config/
    x ./sleepwatcher_2.2/ReadMe.rtf
    x ./sleepwatcher_2.2/sleepwatcher
    x ./sleepwatcher_2.2/._sleepwatcher.8
    x ./sleepwatcher_2.2/sleepwatcher.8
    x ./sleepwatcher_2.2/sources/
    x ./sleepwatcher_2.2/sources/Makefile
    x ./sleepwatcher_2.2/sources/._sleepwatcher.c
    x ./sleepwatcher_2.2/sources/sleepwatcher.c
    x ./sleepwatcher_2.2/sources/sleepwatcher.xcodeproj/
    x ./sleepwatcher_2.2/sources/sleepwatcher.xcodeproj/bb.pbxuser
    x ./sleepwatcher_2.2/sources/sleepwatcher.xcodeproj/bb.perspectivev3
    x ./sleepwatcher_2.2/sources/sleepwatcher.xcodeproj/project.pbxproj
    x ./sleepwatcher_2.2/config/de.bernhard-baehr.sleepwatcher-20compatibility-localu ser.plist
    x ./sleepwatcher_2.2/config/de.bernhard-baehr.sleepwatcher-20compatibility.plist
    x ./sleepwatcher_2.2/config/rc.sleep
    x ./sleepwatcher_2.2/config/rc.wakeup
    Creating dependencies for SleepWatcher...
    Installing SleepWatcher...
    Copying SleepWatcher configuration...
    cp: /Users/Jeffrey/Documents/OS: No such file or directory
    cp: Stuff/MAC/osx-wifibtfix-1.0.3/extra//rc.sleep: No such file or directory
    cp: /Users/Jeffrey/Documents/OS: No such file or directory
    cp: Stuff/MAC/osx-wifibtfix-1.0.3/extra//rc.wakeup: No such file or directory
    Starting SleepWatcher...
    Downloading blueutil...
    Downloading file from http://www.frederikseiffert.de/blueutil/download/blueutil.dmg...
    % Total    % Received % Xferd  Average Speed   Time Time     Time  Current
                                     Dload  Upload Total   Spent    Left Speed
    100 33343  100 33343 0     0  11945 0  0:00:02  0:00:02 --:--:-- 11942
    Mounting blueutil disk image...
    Checksumming Driver Descriptor Map (DDM : 0)…
    Driver Descriptor Map (DDM : 0): verified   CRC32 $0275F970
    Checksumming Apple (Apple_partition_map : 1)…
    Apple (Apple_partition_map : 1): verified   CRC32 $1779B6BD
    Checksumming disk image (Apple_HFS : 2)…
              disk image (Apple_HFS : 2): verified   CRC32 $920D4FD8
    Checksumming  (Apple_Free : 3)…
                        (Apple_Free : 3): verified   CRC32 $00000000
    verified   CRC32 $AFAB3FAE
    /dev/disk2              Apple_partition_scheme          
    /dev/disk2s1            Apple_partition_map             
    /dev/disk2s2            Apple_HFS                        /Volumes/blueutil
    Installing blueutil...
    Finished installing Wifi/BT fix
    Now try to suspend and resume your Mac, your wifi should connect without issue

  • XOrg - Error: cannot open display: 0

    I was recently using 'play on linux' to play 'League Of Legends' when the game crashed. On reboot and starting my GUI using 'startx' my GUI worked for about 40 seconds, after that I lost the ability to exit/restart my Window Manager(i3) or start any new programs. If I try to start a program from a previously existing terminal window I get something along the lines of 'Error: Cannot Open Display :0'.
    I can still switch workspaces and seemingly operate already existing terminal windows.
    This happens on every boot. My only known method of exiting the GUI is to restart the Machine. The 'echo $DISPLAY' command returns ':0'. I dont seem to have /var/log/Xorg.0.log' or '/var/log/Xorg.log'. Im posting from my phone.
    I have already uninstalled Play on Linux, and reinstalled xorg-server.

    VexatioN wrote:If I try to start a program from a previously existing terminal window I get something along the lines of 'Error: Cannot Open Display :0'
    https://bbs.archlinux.org/viewtopic.php?id=57855
    VexatioN wrote:I dont seem to have /var/log/Xorg.0.log' or '/var/log/Xorg.log'
    Look in ~/.local/share/xorg/Xorg.0.log
    Anything in the journal?

  • (gnome-session:4336): Gtk-WARNING **: cannot open display.

    I'm having troble getting gnome running on my system.
    When I'm running gnome-session Im getting (gnome-session:4336): Gtk-WARNING **: cannot open display.
    The exact same setup will allow me to run xfce4 without any problem.
    I did manage to start gnome once with gdm, but then nothing but rightclick on the mouse and the desktop icons would work, and after that one time both gdm and gnome wont work.
    I just did a base install of arch 0.7, xorg, gnome, nvidia and sound drivers.
    Also, if I put exec gnome-session in my .xinitrc file I get a Fatal server error: Requested entity already in use.

    the .xinitrc it is executed by the X window system after the X Server is started
    if you run gnome-session from a console shell and there is no X server started, it cannot open the display...
    the X server is normally started during "startx" or "xinit"
    Last edited by danielsoft (2008-04-03 10:18:40)

Maybe you are looking for

  • My iphone 4 wont open the messaging app

    I recently got a text message, but I try to open the messaging app and it will try to open then it will kick me out

  • Using Epson RX580 Media Card Reader

    When inserting compact flash card, epson shuts off. I have tried different cards (CF and SD) with same result. Epson support confirms TWAIN driver version and compatibility with 10.5. Any suggestions or just wait for and Apple and Epson to update?

  • When I try to open a script, it won't launch

    I can't open scripts. I just get blank, gray page. help

  • Event handling across master/detail regions.

    Hi, I have a table displaying a few targets in the master region and the details of the selected target are shown in an other region. The selected target is passed as an input parameter to the dependent region. Both these regions are displayed in one

  • JSSE only with 1.4.2?

    hey, to make JSSE we recently updated our JRE to 1.4.2 through installation of the j2sdk142_12 and later of j2re142_03 TO OUR SURPRISE the changes did not affect the whole system, when I run C:\java -version it still gives me the old JRE. only when I