Results 1 to 10 of 10

Thread: KpackageKit Crashes

Hybrid View

  1. #1
    Join Date
    Sep 2009
    Location
    Columbus, Ohio, USA
    Posts
    178

    Question KpackageKit Crashes

    Using a fresh install of 11.4 KDE, when I download an app from a website (for example google talk plugin) KpackageKit opens it by default and promptly crashes.

    Then after KpackageKit crashes, everything else crashes. Since the menu and konsole crash, I have to do a hard reboot to get out. Then, after that, neither 11.4 nor the OSes will boot. (I fix grub, though, with directions I got from
    caf4926 last year).

    For the time being, until I find out what to do, I've uninstalled KpackageKit. I then selected Yast as the application to install google talk plugin but got no response.

    Any help would be deeply appreciated.

    Randall
    AMD Athlon II X2 220, 2.8 GHz, 6 GB, PNY GeForce 210; 1 TB: Windows 7HP, Ubuntu 13.10, DBLab/Linux Mint 16 Remix, Suse 12.1 KDE.

  2. #2
    Join Date
    Sep 2009
    Location
    Columbus, Ohio, USA
    Posts
    178

    Default Re: KpackageKit Crashes

    BUMP

    Perhaps I should rephrase the question. What other app can I install and use instead of KpackageKit? I reinstalled it and it worked just slightly better; i.e. everything else didn't crash after it crashed. Yast didn't crash, but it didn't work either -- I had to reboot before I could get rid of KpackageKit again.

    Or is there some way I can make Yast do by default what KpackageKit is supposed to do by default?

    Any help will be much appreciated. Thank you.
    AMD Athlon II X2 220, 2.8 GHz, 6 GB, PNY GeForce 210; 1 TB: Windows 7HP, Ubuntu 13.10, DBLab/Linux Mint 16 Remix, Suse 12.1 KDE.

  3. #3
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: KpackageKit Crashes

    On 04/23/2011 01:06 PM, Randymanme wrote:
    >
    > BUMP
    >


    lots of folks use zypper instead of either YaST or kpackagekit..

    --
    CAVEAT: http://is.gd/bpoMD
    [openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8 via NNTP]
    A Penguin Being Tickled - http://www.youtube.com/watch?v=0GILA0rrR6w

  4. #4
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: KpackageKit Crashes

    Randymanme wrote:

    >
    > BUMP
    >
    > Perhaps I should rephrase the question. What other app can I install
    > and use instead of KpackageKit? I reinstalled it and it worked just
    > slightly better; i.e. everything else didn't crash after it crashed.
    > Yast didn't crash, but it didn't work either -- I had to reboot before I
    > could get rid of KpackageKit again.
    >
    > Or is there some way I can make Yast do by default what KpackageKit is
    > supposed to do by default?
    >
    > Any help will be much appreciated. Thank you.
    >

    It is not completely clear to me which of kpackagekit's functionality you
    refer to here to be substituted.
    Is the main intention to have the automatic updates and notifications or
    something else (you mention installing applications)?
    Can you describe it a bit more.

    I second DenverD's suggestion to use zypper for the moment until you solved
    the gui issues.

    Beside that I see you have a real problem it is for sure not normal that the
    application crashes and esp. that afterwards everything else crashes - your
    kde seems to be in a bad state or you have some fundamental configuration or
    hardware related problem.

    I think we should try to find out and solve that first.
    You mention a fresh 11.4 install so I guess you run also the default KDE
    version.
    To give us a clue can you add the following information to get an idea.

    Did you add additional repositories and which
    Code:
    zypper lr -u
    post the output.
    Ensure in your system that dependencies are satisfied with
    Code:
    su -
    zypper verify
    Maybe you can get usefull information about the crash by simply starting
    kpackegekit in a terminal and watching the output when it crashes.

    What graphics card are you using and what driver, KDE crashes can sometimes
    be triggered by that (more often freezes but who knows).

    A further method to see if it has something to do with your personal KDE
    settings is to create a new dummy user. Log out and login again as that new
    user and try the program there. If it works something is wrong with your
    individual settings.

    I could speculate much more but we need info to nail down where your problem
    really comes from.

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.1 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.0 | nVidia
    ION | 3GB Ram

  5. #5
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: KpackageKit Crashes

    martin_helm wrote:

    > zypper lr -u

    Sorry I meant
    Code:
    zypper lr -d
    which shows more details not -u which only shows the URI.

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.1 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.0 | nVidia
    ION | 3GB Ram

  6. #6
    Join Date
    Sep 2009
    Location
    Columbus, Ohio, USA
    Posts
    178

    Default Re: KpackageKit Crashes

    Thank you very much for the thoughtful requests for more data. Me thinks I should post it piecemeal because it's rather lengthy.
    From: martin_helm's Avatar
    martin_helm
    "It is not completely clear to me which of kpackagekit's functionality you
    refer to here to be substituted.
    Is the main intention to have the automatic updates and notifications or
    something else (you mention installing applications)?
    Can you describe it a bit more."

    Well that's a good question for newbie-me.  I'm not clear on what all KpackageKit is supposed to do.  All I've seen of it is when I downloaded Google Talk plugin and some other app that I don't remember what it was, now.  

    In a nutshell, I just want it to do whatever it's supposed to do without crashing.  (Seems like I recall, by the way,  sometime in 2009, when I was trying to make SuSE look like Kubuntu, Yast wouldn't install KpackageKit –  long story)

    (none):~ # zypper lr -u
    #  | Alias                             | Name                                        | Enabled | Refresh | URI                                                                       
    ---+-----------------------------------+---------------------------------------------+---------+---------+----------------------------------------------------------------------------
     1 | download.nvidia.com-opensuse      | nVidia Graphics Drivers                     | No      | Yes     | ftp://download.nvidia.com/opensuse/11.4/
     
                                      
     2 | download.opensuse.org-Extra       | openSUSE BuildService - KDE:Extra           | No      | Yes     | Index of /repositories/KDE:/Extra/openSUSE_11.4
     
           
     3 | download.opensuse.org-UpdatedApps | openSUSE BuildService - KDE:UpdatedApps     | No      | Yes     | http://download.opensuse.org/reposit.../openS(none):~
     
    # su -
    Directory: /root
    Sat Apr 23 09:08:08 EDT 2011
    (none):~ # zypper verify
    Loading repository data...
    Reading installed packages...

    Dependencies of all installed packages are satisfied.
    (none):~ # USE_11.4/ 
     4 | download.opensuse.org-standard    | Main Repository (Contrib)                   | No      | Yes     | Index of /repositories/openSUSE:/11.4:/Contrib/standard
     

     5 | download.opensuse.org-webcam      | openSUSE BuildService - Drivers for webcams | No      | Yes     | Index of /repositories/drivers:/webcam/openSUSE_11.4
    6 | opensuse-guide.org-repo           | libdvdcss repository                        | No      | Yes     | http://opensuse-guide.org/repo/11.4/
     
                                          
     7 | packman.inode.at-suse             | Packman Repository                          | Yes     | Yes     | Index of /suse/openSUSE_11.4/
     
                                   
     8 | repo-debug                        | openSUSE-11.4-Debug                         | No      | Yes     | Index of /debug/distribution/11.4/repo/oss
     
                
     9 | repo-debug-update                 | openSUSE-11.4-Update-Debug                  | No      | Yes     | Index of /debug/update/11.4
     
                               
    10 | repo-non-oss                      | openSUSE-11.4-Non-Oss                       | Yes     | Yes     | Index of /distribution/11.4/repo/non-oss
     
                  
    11 | repo-oss                          | openSUSE-11.4-Oss                           | Yes     | Yes     | Index of /distribution/11.4/repo/oss
     
                      
    12 | repo-source                       | openSUSE-11.4-Source                        | Yes     | Yes     | Index of /source/distribution/11.4/repo/oss
     
               
    13 | repo-update                       | openSUSE-11.4-Update                        | Yes     | Yes     | Index of /update/11.4
     
                                     
    (none):~ #
    (none):~ # su -
    Directory: /root
    Sat Apr 23 09:08:08 EDT 2011
    (none):~ # zypper verify
    Loading repository data...
    Reading installed packages...
    (none):~ # su -
    Directory: /root
    Sat Apr 23 09:08:08 EDT 2011
    (none):~ # zypper verify
    Loading repository data...
    Reading installed packages...

    Dependencies of all installed packages are satisfied.
    (none):~ #
    Dependencies of all installed packages are satisfied.
    (none):~ #

    I'm using a nVidia GeForce FX 5500 graphics card; Sysinfo says 2d driver: nvidia, 3d driver: 173.14.28
    AMD Athlon II X2 220, 2.8 GHz, 6 GB, PNY GeForce 210; 1 TB: Windows 7HP, Ubuntu 13.10, DBLab/Linux Mint 16 Remix, Suse 12.1 KDE.

  7. #7
    Join Date
    Sep 2009
    Location
    Columbus, Ohio, USA
    Posts
    178

    Default Re: KpackageKit Crashes

    (none):~ # zypper lr -d
    # | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
    ---+-----------------------------------+---------------------------------------------+---------+---------+----------+--------+-----------------------------------------------------------------------------+--------
    1 | download.nvidia.com-opensuse | nVidia Graphics Drivers | No | Yes | 99 | rpm-md | ftp://download.nvidia.com/opensuse/11.4/ |
    2 | download.opensuse.org-Extra | openSUSE BuildService - KDE:Extra | No | Yes | 99 | rpm-md | Index of /repositories/KDE:/Extra/openSUSE_11.4 |
    3 | download.opensuse.org-UpdatedApps | openSUSE BuildService - KDE:UpdatedApps | No | Yes | 99 | rpm-md | Index of /repositories/KDE:/UpdatedApps/openSUSE_11.4 |
    4 | download.opensuse.org-standard | Main Repository (Contrib) | No | Yes | 99 | rpm-md | Index of /repositories/openSUSE:/11.4:/Contrib/standard |
    5 | download.opensuse.org-webcam | openSUSE BuildService - Drivers for webcams | No | Yes | 99 | rpm-md | Index of /repositories/drivers:/webcam/openSUSE_11.4 |
    6 | libdvdcss repository | libdvdcss repository | Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/11.4/ |
    7 | opensuse-guide.org-repo | libdvdcss repository | No | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/11.4/ |
    8 | packman.inode.at-suse | Packman Repository | Yes | Yes | 99 | rpm-md | Index of /suse/openSUSE_11.4/ |
    9 | repo-debug | openSUSE-11.4-Debug | No | Yes | 99 | NONE | Index of /debug/distribution/11.4/repo/oss |
    10 | repo-debug-update | openSUSE-11.4-Update-Debug | No | Yes | 99 | NONE | Index of /debug/update/11.4 |
    11 | repo-non-oss | openSUSE-11.4-Non-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.4/repo/non-oss |
    12 | repo-oss | openSUSE-11.4-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.4/repo/oss |
    13 | repo-source | openSUSE-11.4-Source | Yes | Yes | 99 | yast2 | Index of /source/distribution/11.4/repo/oss |
    14 | repo-update | openSUSE-11.4-Update | Yes | Yes | 99 | rpm-md | Index of /update/11.4 |
    (none):~ #
    AMD Athlon II X2 220, 2.8 GHz, 6 GB, PNY GeForce 210; 1 TB: Windows 7HP, Ubuntu 13.10, DBLab/Linux Mint 16 Remix, Suse 12.1 KDE.

  8. #8
    Join Date
    Sep 2009
    Location
    Columbus, Ohio, USA
    Posts
    178

    Default Re: KpackageKit Crashes

    As far as running KpackageKit in the terminal, I didn't precisely know what that meant, but I did give it a shot. Here goes. Just to give you a preview, the following four and a half pages are all about “zypper in google-talk-plugin” and “zypper in kmplayer.”

    (none):~ # kpackagekit
    (none):~ # su
    (none):~ # zypper in google-talk-plugin
    Retrieving repository 'Packman Repository' metadataRetrieving repository 'Packman Repository' metadataRetrieving repository 'Packman Repository' metadataRetrieving repository 'Packman Repository' metadataRetrieving repository 'Packman Repository' metadata [done]
    Building repository 'Packman Repository' cache [100Building repository 'Packman Repository' cache [100Building repository 'Packman Repository' cache [done]
    Loading repository data...
    Reading installed packages...
    'google-talk-plugin' not found in package names. Trying capabilities.
    No provider of 'google-talk-plugin' found.
    Resolving package dependencies...

    Nothing to do.
    (none):~ # zypper in kmplayer
    Loading repository data...
    Reading installed packages...
    'kmplayer' not found in package names. Trying capabilities.
    No provider of 'kmplayer' found.
    Resolving package dependencies...
    Nothing to do.
    (none):~ # (none):~ # kpackagekit
    bash: syntax error near unexpected token `:~'
    (none):~ # (none):~ # su
    bash: syntax error near unexpected token `:~'
    (none):~ # (none):~ # zypper in google-talk-pluginbash: syntax error near unexpected token `:~'
    (none):~ # Retrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadat [done]
    If 'Retrieving' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Retrieving
    (none):~ # Building repository 'Packman Repository' cache [10Building repository 'Packman Repository' cache [10Building repository 'Packman Repository' cache [doe]
    If 'Building' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Building
    (none):~ # Loading repository data...
    If 'Loading' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Loading
    (none):~ # Reading installed packages...
    If 'Reading' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Reading
    (none):~ # 'google-talk-plugin' not found in package names. Tying capabilities.
    If 'google-talk-plugin' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf google-talk-plugin
    (none):~ # No provider of 'google-talk-plugin' found.
    If 'No' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf No
    (none):~ # Resolving package dependencies...
    If 'Resolving' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Resolving
    (none):~ #
    (none):~ # Nothing to do.
    If 'Nothing' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Nothing
    (none):~ # (none):~ #
    bash: syntax error near unexpected token `:~'
    (none):~ # (none):~ # kpackagekit
    bash: syntax error near unexpected token `:~'
    (none):~ # (none):~ # su
    bash: syntax error near unexpected token `:~'
    (none):~ # (none):~ # zypper in google-talk-pluginbash: syntax error near unexpected token `:~'
    (none):~ # Retrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadat [done]
    If 'Retrieving' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Retrieving
    (none):~ # Building repository 'Packman Repository' cache [10Building repository 'Packman Repository' cache [10Building repository 'Packman Repository' cache [doe]
    If 'Building' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Building
    (none):~ # Loading repository data...
    If 'Loading' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Loading
    (none):~ # Reading installed packages...
    If 'Reading' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Reading
    (none):~ # 'google-talk-plugin' not found in package names. Tying capabilities.
    If 'google-talk-plugin' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf google-talk-plugin
    (none):~ # No provider of 'google-talk-plugin' found.
    If 'No' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf No
    (none):~ # Resolving package dependencies...
    If 'Resolving' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Resolving
    (none):~ #
    (none):~ # Nothing to do.
    If 'Nothing' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Nothing
    (none):~ # (none):~ #
    bash: syntax error near unexpected token `:~'
    (none):~ # (none):~ # zypper in kmplayer
    bash: syntax error near unexpected token `:~'
    (none):~ # Loading repository data...
    If 'Loading' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Loading
    (none):~ # Reading installed packages...
    If 'Reading' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Reading
    (none):~ # 'kmplayer' not found in package names. Trying capabilities.
    If 'kmplayer' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf kmplayer
    (none):~ # No provider of 'kmplayer' found.
    If 'No' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf No
    (none):~ # Resolving package dependencies...
    If 'Resolving' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Resolving
    (none):~ #
    (none):~ # Nothing to do.
    If 'Nothing' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf Nothing
    (none):~ # (none):~ # (none):~ # kpackagekit
    bash: syntax error near unexpected token `:~'
    (none):~ # bash: syntax error near unexpected token `:~'
    > (none):~ # (none):~ # su
    > bash: syntax error near unexpected token `:~'
    > (none):~ # (none):~ # zypper in google-talk-pluginbash: syntax error near unexpected token `:~'
    bash: command substitution: line 1: unexpected EOF while looking for matching `''
    bash: command substitution: line 4: syntax error: unexpected end of file
    If 'bash:' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf bash:
    (none):~ # (none):~ # Retrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadatRetrieving repository 'Packman Repository' metadat [done]
    bash: syntax error near unexpected token `:~'
    (none):~ # If 'Retrieving' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    If 'If' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf If
    (none):~ #     cnf Retrieving
    Retrieving: command not found                          
    (none):~ # (none):~ # Building repository 'Packman Repository' cache [10Building repository 'Packman Repository' cache [10Building repository 'Packman Repository' cache [doe]
    bash: syntax error near unexpected token `:~'
    (none):~ # If 'Building' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    If 'If' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf If
    (none):~ #     cnf Building
    Building: command not found                        
    (none):~ # (none):~ # Loading repository data...
    bash: syntax error near unexpected token `:~'
    (none):~ # If 'Loading' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    If 'If' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf If
    (none):~ #     cnf Loading
    Loading: command not found                       
    (none):~ # (none):~ # Reading installed packages...
    bash: syntax error near unexpected token `:~'
    (none):~ # If 'Reading' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    If 'If' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf If
    (none):~ #     cnf Reading
    Reading: command not found                       
    (none):~ # (none):~ # 'google-talk-plugin' not found in package names. Tying capabilities.
    bash: syntax error near unexpected token `:~'
    (none):~ # If 'google-talk-plugin' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    If 'If' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf If
    (none):~ #     cnf google-talk-plugin
    google-talk-plugin: command not found                                  
    (none):~ # (none):~ # No provider of 'google-talk-plugin' found.
    bash: syntax error near unexpected token `:~'
    (none):~ # If 'No' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    If 'If' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf If
    (none):~ #     cnf No
    No: command not found                  
    (none):~ # (none):~ # Resolving package dependencies...
    bash: syntax error near unexpected token `:~'
    (none):~ # If 'Resolving' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    If 'If' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf If
    (none):~ #     cnf Resolving
    Resolving: command not found                         
    (none):~ # (none):~ #
    bash: syntax error near unexpected token `:~'
    (none):~ # (none):~ # Nothing to do.
    bash: syntax error near unexpected token `:~'
    (none):~ # If 'Nothing' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    If 'If' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf If
    (none):~ #     cnf Nothing
    Nothing: command not found                       
    (none):~ # (none):~ # (none):~ #
    bash: syntax error near unexpected token `:~'
    (none):~ # bash: syntax error near unexpected token `:~'
    > (none):~ #
    AMD Athlon II X2 220, 2.8 GHz, 6 GB, PNY GeForce 210; 1 TB: Windows 7HP, Ubuntu 13.10, DBLab/Linux Mint 16 Remix, Suse 12.1 KDE.

  9. #9
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: KpackageKit Crashes

    Now it is completely unclear waht you really did here that looks as if you
    took the output of the programs and copy and pasted it back to the
    console????

    Ok, if your original problem is to install google-talk-plugin (I do not use
    it) just do the following:
    Visit this page
    http://www.google.com/chat/video/download.html
    Select the rpm for your system 32 or 64 bit.
    And click now the button "Install Video and Voice Chat"
    The browser should ask you to download or install the package depending on
    your browser settings.

    Download the package and save it to place where you can find it again.
    Let us for the moment asume you saved the file to the folder Downloads in
    your home and that you chose the 64 bit rpm.

    Open a terminal and type
    Code:
    cd ~/Downloads
    sudo zypper in google-talkplugin_current_x86_64.rpm
    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.2 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.0 | nVidia
    ION | 3GB Ram

  10. #10
    Join Date
    Mar 2010
    Location
    Europe
    Posts
    657

    Default Re: KpackageKit Crashes

    Quote Originally Posted by Randymanme View Post
    Using a fresh install of 11.4 KDE, when I download an app from a website (for example google talk plugin) KpackageKit opens it by default and promptly crashes.

    Then after KpackageKit crashes, everything else crashes. Since the menu and konsole crash, I have to do a hard reboot to get out. Then, after that, neither 11.4 nor the OSes will boot. (I fix grub, though, with directions I got from
    caf4926 last year).

    For the time being, until I find out what to do, I've uninstalled KpackageKit. I then selected Yast as the application to install google talk plugin but got no response.

    Any help would be deeply appreciated.

    Randall
    I am not entirely sure what you are trying to do. As far as I can see you are trying to install a 'loose' .rpm, right? If so, I would suggest that you create a folder somewhere on your HD, put all those loose .rpm into it and then configure this folder as a repository with YaST's 'Software Repositories'.


    OTOH, if you wish to make it so that if you (double-)click an .rpm, YaST is used to install it, then you could for instance use Dolphin or Konqueror to get the 'Properties' of any .rpm, and then change the Application Preference Order:

    Hint: "Install/Remove Software" is YaST. It would need to be moved up.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •