Printer configuration problems

Hi. I have noticed i was getting no response from my printer so i went into Yast to check if it had dis-configured itself. I keep getting this message. not sure what is going on but i get the same response for any hardware.

Error
Can’t locate strict.pm in @INC (@INC contains: /y2update/modules /root/.yast2/modules /usr/share/YaST2/modules /usr/lib/perl5/5.10.0/i586-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl/5.10.0/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl/5.10.0/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl .) at /usr/share/YaST2/modules/URLRecode.pm line 15.
BEGIN failed–compilation aborted at /usr/share/YaST2/modules/URLRecode.pm line 15.
Compilation failed in require.
BEGIN failed–compilation aborted.

Anyone please able to recognise a problem and how to reconfigure my hardware?

thank you.

On 2011-03-02 01:36, Linuxinlennox wrote:
> Can’t locate strict.pm in @INC (@INC contains: /y2update/modules

You need perl-base installed.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Thanks.
Actually, anything I click on from the YaST control center sends the same message. I am unable to access YaST.
I assume it is an update that is necessary? Is there anyway to install it otherwise?

You could launch the ncurses (text-mode) yast interface via console (as root) with ‘yast’ command, or use zypper

zypper in perl-base

Thanks deano, Tried both options.
The ncurses (text-mode) yast interface was not responsive.

This was the output from zypper in perl-base

hcppc2:/home/dave # zypper in perl-base
Retrieving repository '11.2' metadata [done]
Building repository '11.2' cache [done]
Retrieving repository 'Packman Repository' metadata [done]
Building repository 'Packman Repository' cache [done]
Retrieving repository 'http://packman.iu-bremen.de/suse/11.2' metadata [done]
Building repository 'http://packman.iu-bremen.de/suse/11.2' cache [done]
Loading repository data...
Reading installed packages...
'perl-base' is already installed.
No update candidate for 'perl-base-5.12.1-2.3.1.i586'. The highest available version is already installed.
Resolving package dependencies...

Nothing to do.

yast still giving the same error message.

On 2011-03-02 09:36, Linuxinlennox wrote:
>
> Thanks deano, Tried both options.
> The ncurses (text-mode) yast interface was not responsive.

Yep.

> This was the output from zypper in perl-base

> Reading installed packages…
> ‘perl-base’ is already installed.

Reinstall it, force the issue.

zypper in --help


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

What would be the terminal command to force install? I tried a few option combinationss from zypper in --help. No luck!

dave@dhcppc2:~> zypper in --help
install (in) [options] <capability|rpm_file_uri> ...

Install packages with specified capabilities or RPM files with specified
location. A capability is NAME.ARCH][OP<VERSION>], where OP is one
of <, <=, =, >=, >.

  Command options:
    --from <alias|#|URI>    Select packages from the specified repository.
-r, --repo <alias|#|URI>    Load only the specified repository.
-t, --type <type>           Type of package (package, patch, pattern, product, srcpackage).
                            Default: package.
-n, --name                  Select packages by plain name, not by capability.
-C, --capability            Select packages by capability.
-f, --force                 Reinstall the package if the exact version is
                            available in repositories.
-l, --auto-agree-with-licenses
                            Automatically say 'yes' to third party license
                            confirmation prompt.
                            See 'man zypper' for more details.
    --debug-solver          Create solver test case for debugging.
    --no-recommends         Do not install recommended packages, only required.
    --recommends            Install also recommended packages in addition
                            to the required.
-R, --no-force-resolution   Do not force the solver to find solution,
                            let it ask.
    --force-resolution      Force the solver to find a solution (even
                            an aggressive one).
-D, --dry-run               Test the installation, do not actually install.
    --download              Set the download-install mode. Available modes:
                            only, in-advance, in-heaps, as-needed
-d, --download-only         Only download the packages, do not install.

On 2011-03-03 00:06, Linuxinlennox wrote:
>
> What would be the terminal command to force install? I tried a few
> option combinationss from zypper in --help. No luck!

Sigh…

>
> Code:
> --------------------
> dave@dhcppc2:~> zypper in --help


> -f, --force Reinstall the package if the exact version is
> available in repositories.

Did I say force? No, I did not. I said force, perhaps? Mmm… :stuck_out_tongue:


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

No idea what to do now. Anyone please have any advice how i can access yast and other applications again that have been shut down by this problem?

No idea what to do now. Anyone please have any advice how i can access yast and other applications again that have been rehabilitated by this problem?

Carlos was trying to advise this form of command:

zypper in --force <name-of-package>

Edit: More info.

You may find other perl or yast2 packages (eg perl-bindings, yast2-core) may need to be reinstalled here (based on what quick searches on this error have thrown up for me)

On 2011-03-03 03:36, deano ferrari wrote:
>
>> No idea what to do now. Anyone please have any advice how i can access
>> yast and other applications again that have been rehabilitated by this
>> problem?
>
> Carlos was trying to advise this form of command:
>
>
> Code:
> --------------------
> zypper in --force <name-of-package>
> --------------------

Right. I was hopping that reading a manual with hints would be enough. I
believe in study and investigation being better that being told directly
what to do is better for the soul.

O:-)

Ok, off to bed for me, or I may do/say some thing even more daft.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Right. I was hopping that reading a manual with hints would be enough. I
believe in study and investigation being better that being told directly
what to do is better for the soul.

I get it Carlos. I am very interested in the study and i am learning heaps here.I just have to get this printer operational for work.

Thanks to deano. Those items installed. Now i have a new error message in Yast. Something about a language plugin. Only it is not in my language.:embarrassed:

Error loading language plugin /usr/lib/YaST2/plugin/libpy2lang_perl.so: libperl.so: cannot open shared object file: No such file or directory
Error while creating client module webpin_package_search

I have no idea of the command to load this in terminal! Totally lost.

I just have to get this printer operational for work.

  1. You may be able to get the printer configured via your browser. CUPS has a web interface:

http://localhost:631

Administration > Add Printer > …

  1. Now, I don’t know how you got in this sticky situation with YaST (as I’ve never experienced this), but searching online, I found a similar error reported in this thread.

So, I’m wondering if this may have occurred because of conflicting repositories enabled with your system (unintentional and otherwise). Did you attempt any ‘1-click’ installs for example?

Anyway, please post the output of

zypper lr -d
  1. Did you reinstall yast2-perl-bindings?

Lets also have a look at your installed yast2 packages

rpm -qa |grep yast2

Once we’ve checked that your repo list is ok, it may be possible to run

zypper ve

to discover/rectify any package conflicts etc (if you’re lucky :))

Don’t try this last command before submitting the repo list and receiving advice on this though.

So, I’m wondering if this may have occurred because of conflicting repositories enabled with your system (unintentional and otherwise). Did you attempt any ‘1-click’ installs for example?

I have done plenty of mucking around with repositories recently trying to get flash updated, and had to clear many out as advised in another thread.



dave@dhcppc2:~> zypper lr -d
#  | Alias                                                        | Name                                                         | Enabled | Refresh | Priority | Type   | URI                                                          | Service
---+--------------------------------------------------------------+--------------------------------------------------------------+---------+---------+----------+--------+--------------------------------------------------------------+--------
1  | 11.2                                                         | 11.2                                                         | Yes     | Yes     |   99     | rpm-md | http://packman.iu-bremen.de/suse/11.2/                       |
2  | NON-OSS                                                      | NON-OSS                                                      | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.3/repo/non-oss/ |
3  | OSS                                                          | OSS                                                          | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.3/repo/oss/     |
4  | Packman Repository                                           | Packman Repository                                           | Yes     | Yes     |   99     | rpm-md | http://packman.mirrors.skynet.be/pub/packman/suse/11.2       |
5  | UPDATE                                                       | UPDATE                                                       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/11.3/                    |
6  | http://download.opensuse.org/distribution/11.2/repo/oss/suse | http://download.opensuse.org/distribution/11.2/repo/oss/suse | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/11.2/repo/oss/suse |
7  | http://download.opensuse.org/update/11.2/                    | http://download.opensuse.org/update/11.2/                    | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/11.2/                    |
8  | http://packman.iu-bremen.de/suse/11.2                        | http://packman.iu-bremen.de/suse/11.2                        | Yes     | Yes     |   99     | rpm-md | http://packman.iu-bremen.de/suse/11.2                        |
9  | openSUSE 11.2-0                                              | openSUSE 11.2-0                                              | Yes     | No      |   99     | yast2  | cd:///                                                       |
10 | openSUSE:11.2:NonFree                                        | openSUSE:11.2:NonFree                                        | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.2/repo/non-oss/ |
dave@dhcppc2:~> zypper in --force perl-base

  1. Did you reinstall yast2-perl-bindings?

Yes, just did that.

dave@dhcppc2:~> rpm -qa |grep yast2
yast2-theme-openSUSE-2.18.10-1.1.1.noarch
yast2-mouse-2.18.2-2.1.i586              
yast2-x11-2.18.0-2.1.noarch              
patterns-openSUSE-yast2_basis-11.3-1.1.1.i586
yast2-country-data-2.18.21-0.3.1.i586        
yast2-core-2.19.3-1.1.1.i586                 
yast2-xml-2.16.1-56.1.i586                   
yast2-dbus-client-2.18.0-2.1.i586            
yast2-security-2.18.3-2.2.noarch             
yast2-sudo-2.18.2-2.2.noarch                 
yast2-qt-graph-2.18.4-4.1.i586               
yast2-slp-2.16.0-83.1.i586                   
yast2-apparmor-2.18.4-1.1.1.noarch           
yast2-tv-2.18.4-2.8.noarch                   
yast2-nfs-common-2.18.1-2.2.noarch           
yast2-online-update-frontend-2.18.5-2.2.noarch
yast2-installation-2.18.33-1.1.2.noarch       
yast2-metapackage-handler-0.8.10-0.1.1.noarch 
yast2-ycp-ui-bindings-2.18.5-2.1.i586         
yast2-transfer-2.18.0-3.1.i586                
yast2-ldap-2.17.3-9.1.i586                    
yast2-add-on-2.18.3-2.1.noarch                
yast2-qt-pkg-2.19.3-0.1.3.i586                
yast2-inetd-2.17.3-3.3.noarch                 
yast2-trans-en_GB-2.18.1-16.19.1.noarch       
yast2-registration-branding-openSUSE-2.18.0-2.4.noarch
yast2-pam-2.18.1-0.1.1.noarch                         
yast2-nfs-client-2.18.0-2.2.noarch                    
yast2-firewall-2.18.1-1.1.2.noarch                    
yast2-iscsi-client-2.18.6-2.2.noarch                  
yast2-ncurses-pkg-2.19.4-1.1.1.i586                   
yast2-branding-openSUSE-2.18.0-2.1.noarch             
yast2-perl-bindings-2.18.0-2.1.i586                   
yast2-backup-2.18.5-0.1.1.noarch                      
yast2-hardware-detection-2.17.1-2.3.i586              
yast2-2.18.25-2.5.i586
yast2-printer-2.18.19-2.2.i586
yast2-nis-client-2.18.2-2.2.i586
yast2-online-update-2.18.5-2.2.noarch
yast2-tune-2.18.1-2.2.i586
autoyast2-installation-2.18.14-1.1.3.noarch
yast2-samba-server-2.18.2-2.1.noarch
yast2-irda-2.18.2-0.1.1.noarch
yast2-network-2.18.53-1.1.1.i586
patterns-openSUSE-yast2_install_wf-11.3-1.1.1.i586
yast2-control-center-qt-2.18.12-1.1.1.i586
yast2-theme-openSUSE-Oxygen-2.18.10-1.1.1.noarch
yast2-packager-2.18.13-1.1.3.i586
yast2-ldap-client-2.18.5-2.6.noarch
yast2-update-2.18.6-2.3.i586
yast2-storage-2.18.19-2.3.i586
yast2-ntp-client-2.18.0-3.2.noarch
yast2-control-center-gnome-2.13.4-2.3.i586
yast2-bootloader-2.18.17-2.5.i586
yast2-samba-client-2.18.3-2.2.noarch
yast2-qt-2.18.7-2.1.i586
yast2-trans-ja-2.18.1-16.19.1.noarch
yast2-country-2.18.21-0.3.1.i586
yast2-packager-webpin-2.18.13-1.1.3.i586
yast2-sound-2.18.4-1.1.2.1.i586
yast2-runlevel-2.17.4-2.2.noarch
yast2-registration-2.18.0-2.4.noarch
yast2-restore-2.18.1-3.1.noarch
yast2-users-2.18.13-2.1.i586
yast2-pkg-bindings-2.19.1-1.11.i586
yast2-trans-stats-2.15.0-122.2.noarch
yast2-scanner-2.18.0-2.2.i586
yast2-repair-2.18.3-2.4.noarch
yast2-sysconfig-2.17.0-56.2.noarch
yast2-control-center-2.18.12-1.1.1.i586
yast2-mail-2.18.2-2.2.noarch
yast2-profile-manager-2.18.2-2.2.i586
yast2-libyui-2.18.8-2.1.i586
yast2-vm-2.16.10-3.1.i586
yast2-kerberos-client-2.18.3-2.2.noarch
yast2-ncurses-2.19.5-1.6.i586
yast2-gtk-2.21.70-2.2.1.i586
dave@dhcppc2:~>


Ok, I see problems here with your repos. You have a mixture of 11.2 and 11.3 repos enabled. I’m surprised it is only yast that is giving you problems here! This points to a bad upgrade attempt on your part.

Repo’s 1,4,6,7,8,9 and 10 should be removed like this

zypper rr 1

Repeat for the other 11.2 repos.

Then run

zypper dup

On 2011-03-03 10:36, Linuxinlennox wrote:
>
>> So, I’m wondering if this may have occurred because of conflicting
>> repositories enabled with your system (unintentional and otherwise). Did
>> you attempt any ‘1-click’ installs for example?
> I have done plenty of mucking around with repositories recently trying
> to get flash updated, and had to clear many out as advised in another
> thread.

And you did it badly.

> Code:
> --------------------
>
>
> dave@dhcppc2:~> zypper lr -d
> # | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
> —±-------------------------------------------------------------±-------------------------------------------------------------±--------±--------±---------±-------±-------------------------------------------------------------±-------
> 1 | 11.2 | 11.2 | Yes | Yes | 99 | rpm-md | http://packman.iu-bremen.de/suse/11.2/ |

This one is repeated with number 4, remove.

> 2 | NON-OSS | NON-OSS | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.3/repo/non-oss/ |

Wow. This one is for 11.3, and the previous one is for 11.2 -> BIG PROBLEM!

> 3 | OSS | OSS | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.3/repo/oss/ |

Wow. This one is for 11.3, and the previous one is for 11.2 -> BIG PROBLEM!

> 4 | Packman Repository | Packman Repository | Yes | Yes | 99 | rpm-md | http://packman.mirrors.skynet.be/pub/packman/suse/11.2 |

Change to 11.3

> 5 | UPDATE | UPDATE | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/11.3/ |
> 6 | http://download.opensuse.org/distribution/11.2/repo/oss/suse | http://download.opensuse.org/distribution/11.2/repo/oss/suse | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/11.2/repo/oss/suse |

Remove

> 7 | http://download.opensuse.org/update/11.2/ | http://download.opensuse.org/update/11.2/ | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/11.2/ |

Remove! 11.2

> 8 | http://packman.iu-bremen.de/suse/11.2 | http://packman.iu-bremen.de/suse/11.2 | Yes | Yes | 99 | rpm-md | http://packman.iu-bremen.de/suse/11.2 |

Remove! 11.2

> 9 | openSUSE 11.2-0 | openSUSE 11.2-0 | Yes | No | 99 | yast2 | cd:/// |

Remove! 11.2

> 10 | openSUSE:11.2:NonFree | openSUSE:11.2:NonFree | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.2/repo/non-oss/ |

Remove! 11.2

Certainly, you have a muck up of repos for 11.2 and 11.3. I don’t know what
version you have.

Repair the list of repos, leave only those for 11.3, then do a rpm verify
all. You will probably need a zypper dup. Later.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-03-03 11:06, deano ferrari wrote:

> Code:
> --------------------
> zypper rr 1
> --------------------

Remember that you have to do a zypper lr after each remove by number: they
change.

> Repeat for the other 11.2 repos.
>
> Then run
>
>
> Code:
> --------------------
> zypper dup
> --------------------

To do that, make sure that only the main repos are enabled:

  1. 11.3 DVD (not in the list).
  2. 11.3 oss
  3. 11.3 non-oss
  4. 11.3 updates

Certainly packman must be disabled. Then run the dup, and after rebooting,
activate packman essentials and re-install multimedia stuff.

The above advice is assuming that the system is 11.3. I don’t know if you
have mostly 11.2 or 11.3 at this point…


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I am actually running Suse 11.2. To have the upgrades i need the repos for suse 11.3? that is where i have become confused.
So Suse 11.3 repos are suitable for a system running 11.2 (well, until I upgrade my system anyway). And i need to delete 11.2 repos?