Announcement

Collapse
No announcement yet.

Cannot access Desktop Activities

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Cannot access Desktop Activities

    [SOLVED] Apologies if there's a post on this; I haven't been able to find it.
    I went to change my desktop wallpaper the other day, but when I right-clicked on the desktop, the only window that came up had only two lines: "Activities" and "Desktop Activity," the latter being greyed out. I can't figure out what happened to the context window that normally opens. My copy of Lynx is up to date. I even tried (gasp!) rebooting (sorry; a relic from my Windows days).
    I tried going into Desktop Effects and got a message saying "Check your X configuration." And I would, too, if I knew how. I've looked in /etc/X11 for an xorg.conf file, but there isn't one. (Not that I would know what to do with it if I had it.)
    Thanks to all. Enjoy the holidays.

    Don

    #2
    Re: Cannot access Desktop Activities

    Sorry to hear about your issue, however, you've provided us with no information that would be useful, namely your graphics card or GPU you are using. Also, what version of KDE are you running?
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      Re: Cannot access Desktop Activities

      I am well rebuked; I should know better by now. It's KDE 4.42, and the graphics card is BFG GeForce 9600 GT OC 512Mb. There have been no (intentional) changes to either hardware or software since I last changed the wallpaper on September 21. The only thing I've done is to run update periodically.

      Comment


        #4
        Re: Cannot access Desktop Activities

        Nvidia graphics card. What version of the driver are you using? KDE 4.4.2 is 'old' for Maverick, but that is likely not contributing to your issue. The Nvidia driver is the more likely culprit. That said, you can verify that all updates you have run were completed fully. Open a console and type:
        Code:
        sudo apt-get update && sudo apt-get install -f
        The second command: Fix; attempt to correct a system with broken dependencies in place.

        Are you using any third-party repositories?
        Windows no longer obstructs my view.
        Using Kubuntu Linux since March 23, 2007.
        "It is a capital mistake to theorize before one has data." - Sherlock Holmes

        Comment


          #5
          Re: Cannot access Desktop Activities

          Snowhog,
          I don't think I'm using any third party repositories. I ran the command; here's the return I got on it:

          Hit http://security.ubuntu.com lucid-security Release.gpg
          Ign http://security.ubuntu.com/ubuntu/ lucid-security/restricted Translation-en_US
          Hit http://archive.canonical.com lucid Release.gpg
          Ign http://archive.canonical.com/ubuntu/ lucid/partner Translation-en_US
          Hit http://us.archive.ubuntu.com lucid Release.gpg
          Ign http://us.archive.ubuntu.com/ubuntu/ lucid/restricted Translation-en_US
          Ign http://security.ubuntu.com/ubuntu/ lucid-security/main Translation-en_US
          Ign http://security.ubuntu.com/ubuntu/ lucid-security/universe Translation-en_US
          Ign http://security.ubuntu.com/ubuntu/ lucid-security/multiverse Translation-en_US
          Hit http://archive.canonical.com lucid Release.gpg
          Ign http://archive.canonical.com/ lucid/partner Translation-en_US
          Hit http://security.ubuntu.com lucid-security Release
          Hit http://archive.canonical.com lucid Release
          Ign http://us.archive.ubuntu.com/ubuntu/ lucid/main Translation-en_US
          Ign http://us.archive.ubuntu.com/ubuntu/ lucid/universe Translation-en_US
          Ign http://us.archive.ubuntu.com/ubuntu/ lucid/multiverse Translation-en_US
          Hit http://us.archive.ubuntu.com lucid-updates Release.gpg
          Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/restricted Translation-en_US
          Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Translation-en_US
          Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/universe Translation-en_US
          Ign http://us.archive.ubuntu.com/ubuntu/ lucid-updates/multiverse Translation-en_US
          Hit http://archive.canonical.com lucid Release
          Hit http://us.archive.ubuntu.com lucid Release
          Hit http://security.ubuntu.com lucid-security/restricted Packages
          Hit http://us.archive.ubuntu.com lucid-updates Release
          Hit http://archive.canonical.com lucid/partner Packages
          Hit http://archive.canonical.com lucid/partner Sources
          Hit http://security.ubuntu.com lucid-security/main Packages
          Hit http://security.ubuntu.com lucid-security/restricted Sources
          Hit http://security.ubuntu.com lucid-security/universe Packages
          Hit http://security.ubuntu.com lucid-security/universe Sources
          Hit http://us.archive.ubuntu.com lucid/restricted Packages
          Hit http://us.archive.ubuntu.com lucid/main Packages
          Hit http://us.archive.ubuntu.com lucid/restricted Sources
          Hit http://us.archive.ubuntu.com lucid/universe Packages
          Hit http://archive.canonical.com lucid/partner Packages
          Hit http://security.ubuntu.com lucid-security/multiverse Packages
          Hit http://security.ubuntu.com lucid-security/multiverse Sources
          Hit http://us.archive.ubuntu.com lucid/universe Sources
          Hit http://us.archive.ubuntu.com lucid/multiverse Packages
          Hit http://us.archive.ubuntu.com lucid/multiverse Sources
          Hit http://us.archive.ubuntu.com lucid-updates/restricted Packages
          Hit http://us.archive.ubuntu.com lucid-updates/main Packages
          Hit http://us.archive.ubuntu.com lucid-updates/restricted Sources
          Hit http://us.archive.ubuntu.com lucid-updates/universe Packages
          Hit http://us.archive.ubuntu.com lucid-updates/universe Sources
          Hit http://us.archive.ubuntu.com lucid-updates/multiverse Packages
          Hit http://us.archive.ubuntu.com lucid-updates/multiverse Sources
          Reading package lists... Done
          Reading package lists... Done
          Building dependency tree
          Reading state information... Done
          The following packages were automatically installed and are no longer required:
          linux-headers-2.6.32-26-generic linux-headers-2.6.32-21-generic
          fairymax linux-headers-2.6.32-24-generic linux-headers-2.6.32-21
          linux-headers-2.6.32-22 linux-headers-2.6.32-23
          linux-headers-2.6.32-24 linux-headers-2.6.32-25
          linux-headers-2.6.32-26 libreadline5
          linux-headers-2.6.32-22-generic linux-headers-2.6.32-25-generic
          xaw3dg linux-headers-2.6.32-23-generic
          Use 'apt-get autoremove' to remove them.
          0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

          BTW, I'm not using Maverick; I'm on Lucid l0.04.1.

          Thanks.
          Don

          Comment


            #6
            Re: Cannot access Desktop Activities

            Thread moved to Lucid.

            You're booting in to the 2.6.32-26 kernel? Do you still have the other kernels in your Grub menu? If you do, do you experience this issue if you boot in to one of the prior kernels?
            Windows no longer obstructs my view.
            Using Kubuntu Linux since March 23, 2007.
            "It is a capital mistake to theorize before one has data." - Sherlock Holmes

            Comment


              #7
              Re: Cannot access Desktop Activities

              You've just gone well beyond my meager experience with Linux. It boots automatically into this kernel. I don't know how to boot into a prior kernel, but I'm going to do some research now to find out and to find out whether there are prior kernels. (This is my awkward way of saying that I don't know how to pull up the Grub menu, but I will in a few minutes.)

              Comment


                #8
                Re: Cannot access Desktop Activities

                Here's the output of the grub.cfg file. Is this what you (I?) needed to see? I'm not sure what it's telling me.

                #
                # DO NOT EDIT THIS FILE
                #
                # It is automatically generated by /usr/sbin/grub-mkconfig using templates
                # from /etc/grub.d and settings from /etc/default/grub
                #

                ### BEGIN /etc/grub.d/00_header ###
                if [ -s $prefix/grubenv ]; then
                load_env
                fi
                set default="0"
                if [ ${prev_saved_entry} ]; then
                set saved_entry=${prev_saved_entry}
                save_env saved_entry
                set prev_saved_entry=
                save_env prev_saved_entry
                set boot_once=true
                fi

                function savedefault {
                if [ -z ${boot_once} ]; then
                saved_entry=${chosen}
                save_env saved_entry
                fi
                }

                function recordfail {
                set recordfail=1
                if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
                }
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                if loadfont /usr/share/grub/unicode.pf2 ; then
                set gfxmode=640x480
                insmod gfxterm
                insmod vbe
                if terminal_output gfxterm ; then true ; else
                # For backward compatibility with versions of terminal.mod that don't
                # understand terminal_output
                terminal gfxterm
                fi
                fi
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                set locale_dir=($root)/boot/grub/locale
                set lang=en
                insmod gettext
                if [ ${recordfail} = 1 ]; then
                set timeout=-1
                else
                set timeout=10
                fi
                ### END /etc/grub.d/00_header ###

                ### BEGIN /etc/grub.d/05_debian_theme ###
                set menu_color_normal=white/black
                set menu_color_highlight=black/light-gray
                ### END /etc/grub.d/05_debian_theme ###

                ### BEGIN /etc/grub.d/10_linux ###
                menuentry 'Ubuntu, with Linux 2.6.32-27-generic' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux /boot/vmlinuz-2.6.32-27-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro quiet splash
                initrd /boot/initrd.img-2.6.32-27-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-27-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                echo 'Loading Linux 2.6.32-27-generic ...'
                linux /boot/vmlinuz-2.6.32-27-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro single
                echo 'Loading initial ramdisk ...'
                initrd /boot/initrd.img-2.6.32-27-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux /boot/vmlinuz-2.6.32-26-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro quiet splash
                initrd /boot/initrd.img-2.6.32-26-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                echo 'Loading Linux 2.6.32-26-generic ...'
                linux /boot/vmlinuz-2.6.32-26-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro single
                echo 'Loading initial ramdisk ...'
                initrd /boot/initrd.img-2.6.32-26-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-25-generic' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux /boot/vmlinuz-2.6.32-25-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro quiet splash
                initrd /boot/initrd.img-2.6.32-25-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-25-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                echo 'Loading Linux 2.6.32-25-generic ...'
                linux /boot/vmlinuz-2.6.32-25-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro single
                echo 'Loading initial ramdisk ...'
                initrd /boot/initrd.img-2.6.32-25-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux /boot/vmlinuz-2.6.32-24-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro quiet splash
                initrd /boot/initrd.img-2.6.32-24-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                echo 'Loading Linux 2.6.32-24-generic ...'
                linux /boot/vmlinuz-2.6.32-24-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro single
                echo 'Loading initial ramdisk ...'
                initrd /boot/initrd.img-2.6.32-24-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux /boot/vmlinuz-2.6.32-23-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro quiet splash
                initrd /boot/initrd.img-2.6.32-23-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                echo 'Loading Linux 2.6.32-23-generic ...'
                linux /boot/vmlinuz-2.6.32-23-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro single
                echo 'Loading initial ramdisk ...'
                initrd /boot/initrd.img-2.6.32-23-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux /boot/vmlinuz-2.6.32-22-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro quiet splash
                initrd /boot/initrd.img-2.6.32-22-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                echo 'Loading Linux 2.6.32-22-generic ...'
                linux /boot/vmlinuz-2.6.32-22-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro single
                echo 'Loading initial ramdisk ...'
                initrd /boot/initrd.img-2.6.32-22-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux /boot/vmlinuz-2.6.32-21-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro quiet splash
                initrd /boot/initrd.img-2.6.32-21-generic
                }
                menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
                recordfail
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                echo 'Loading Linux 2.6.32-21-generic ...'
                linux /boot/vmlinuz-2.6.32-21-generic root=UUID=5da6aa85-e95d-4ece-99c3-b8fffda68da5 ro single
                echo 'Loading initial ramdisk ...'
                initrd /boot/initrd.img-2.6.32-21-generic
                }
                ### END /etc/grub.d/10_linux ###

                ### BEGIN /etc/grub.d/20_memtest86+ ###
                menuentry "Memory test (memtest86+)" {
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux16 /boot/memtest86+.bin
                }
                menuentry "Memory test (memtest86+, serial console 115200)" {
                insmod ext2
                set root='(hd1,1)'
                search --no-floppy --fs-uuid --set 5da6aa85-e95d-4ece-99c3-b8fffda68da5
                linux16 /boot/memtest86+.bin console=ttyS0,115200n8
                }
                ### END /etc/grub.d/20_memtest86+ ###

                ### BEGIN /etc/grub.d/30_os-prober ###
                if [ ${timeout} != -1 ]; then
                if keystatus; then
                if keystatus --shift; then
                set timeout=-1
                else
                set timeout=0
                fi
                else
                if sleep --interruptible 3 ; then
                set timeout=0
                fi
                fi
                fi
                ### END /etc/grub.d/30_os-prober ###

                ### BEGIN /etc/grub.d/40_custom ###
                # This file provides an easy way to add custom menu entries. Simply type the
                # menu entries you want to add after this comment. Be careful not to change
                # the 'exec tail' line above.
                ### END /etc/grub.d/40_custom ###

                Comment


                  #9
                  Re: Cannot access Desktop Activities

                  According to your file, you have seven different kernels intalled - .21 to .27 (.27 being the most recent, and the one you are booting into). When you boot your PC, the Grub menu is presented to you for 10-seconds (based on what I read in the file). So from the menu, select an earlier kernel, say, the .26 kernel, and see if you have the functionality from the desktop that you expect and should have.
                  Windows no longer obstructs my view.
                  Using Kubuntu Linux since March 23, 2007.
                  "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                  Comment


                    #10
                    Re: Cannot access Desktop Activities

                    Well, this is embarrassing, to say the least. The machine won't even get to the Grub boot screen; it just hangs up on the initial screen. My inclination at this point is to shut it down and reset the CMOS by pulling the battery. (I know this will be hard to believe, but I built this machine, and it's been running just fine.)
                    Does that procedure make any sense?

                    Comment


                      #11
                      Re: Cannot access Desktop Activities

                      What are the specs on the HD that Linux (root) is installed on? With that many installed kernels, unless you established a very generous root partition, you may have reached the space limit.
                      Windows no longer obstructs my view.
                      Using Kubuntu Linux since March 23, 2007.
                      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                      Comment


                        #12
                        Re: Cannot access Desktop Activities

                        I don't remember the exact specs, because I can't get it to boot even to a Kubuntu CD. The drive is .5T, and the root sector is at least 200G.

                        Comment


                          #13
                          Re: Cannot access Desktop Activities

                          A half-terrabyte drive, with 200Gb for root, well space issues are not the issue. That you can't boot from a CD is more telling. As to that, access your bios when starting up the PC and check the boot order options. Put the CD Drive first, followed by the HDD. If that is already set that way, then you might just want to remove the battery for a bit, and reinstall it and fire up the PC.
                          Windows no longer obstructs my view.
                          Using Kubuntu Linux since March 23, 2007.
                          "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                          Comment


                            #14
                            Re: Cannot access Desktop Activities

                            Let me say first how much I appreciate all the time you're spending with me. It really is very generous of you.
                            I tried pulling the battery and got a screen that asked me what boot I wanted to try. I picked "last known good" and ended up at the same place I'd been. Still no boot to the CD. I'll try it again and try one of the other options on the menu.

                            Comment


                              #15
                              Re: Cannot access Desktop Activities

                              Well, I'm doing what might be called making progress in a negative direction. Now nothing comes up on the screen at all. At least it used to tell me to go to hell. Is it possible that my video card has simply gone bad? (It shouldn't; it was new in May, but such things have been known to happen.)
                              If it has, I'm obviously not going to get a replacement tomorrow, but do you have one you'd recommend?
                              (Dibl will be ashamed of me; he's been helping me switch to Linux since earlier this year. I wish I had a clue about what's happening.)

                              Don

                              Comment

                              Working...
                              X