December 2012 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] CUPS Printing for HP PSC 1510 Series : Tumbleweed
by Ken Schneider - Factory 12 Dec '12

12 Dec '12

On 12/12/2012 10:21 AM, "Stefan Brüns" pecked at the keyboard and wrote: > > > Am 11.12.12, schrieb Ken Schneider - openSUSE <suse-list3(a)bout-tyme.net>: > >> Thanks for the links, they provided me with a better understanding of the print system and the problem with duplex printing. >> >> Since it appears that a newer version of poppler fixes the duplex printing regression problem will an update be forthcoming so that users with duplex printers can actually start to print in duplex mode? > > The fix is actually in cups, which has to call popplers pstopdf with the right parameters. > > See https://build.opensuse.org/project/show?project=openSUSE%3AMaintenance%3A11… > > Regards, > > Stefan > > Wouldn't it be calling pdftops not pstopdf? -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] CUPS Printing for HP PSC 1510 Series : Tumbleweed
by "Stefan Brüns" 12 Dec '12

12 Dec '12

Am 11.12.12, schrieb Ken Schneider - openSUSE <suse-list3(a)bout-tyme.net>: > Thanks for the links, they provided me with a better understanding of the print system and the problem with duplex printing. > > Since it appears that a newer version of poppler fixes the duplex printing regression problem will an update be forthcoming so that users with duplex printers can actually start to print in duplex mode? The fix is actually in cups, which has to call popplers pstopdf with the right parameters. See https://build.opensuse.org/project/show?project=openSUSE%3AMaintenance%3A11… Regards, Stefan PS: Sorry Ken for the private mail, got hit by this stupid webmailer again ... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] LibreOffice : Tumbleweed
by ellanios82 12 Dec '12

12 Dec '12

Hello List LibreOffice : Tumbleweed : refuses to start _________ - get message : /usr/lib/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib/libpangocairo-1.0.so.0: undefined symbol: g_object_replace_qdata ........... what to do please ?? thanks Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] custom openSUSE-NET-x86_64.iso with different install= URL
by Olaf Hering 12 Dec '12

12 Dec '12

The openSUSE-Net.iso images at http://download.opensuse.org/factory/iso/ do unfortunately point to a non-existant installation source, instead to http://download.opensuse.org/factory/repo/oss/ To make things easier for me I want to roll my own with just the REPO_URL changed. How can I link/branch this "thing", with just the REPO_URL changed? It seems that the "Branch package" link in the web UI in https://build.opensuse.org/package/show?package=_product%3AopenSUSE-cd-mini… does not work. Appearently its not an ordinary package. Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] noshow for fans and voltages in 12.3
by Constant Brouerius van Nidek 12 Dec '12

12 Dec '12

In Gkrellm I monitor the teperatures and fan speeds on a regular base, due to the high daily temperatures. Up to 12.2 I was able to have the system and CPU temperature and all three temps from the harddisks. Two fan speeds were also shown. Due to an acpi driver problem I have to add "acpi_enforce_resources=lax" in the bootsequence. Worked like a charm. In 12.3 though the CPU, system temp and fans are not shown any more. And when I remove "acpi_enforce_resources=lax" from the boot sequence also my harddisk temperatures vanish. According to the sensors-detect my temp chip is a Winbond A83697HF/F/HG on the ISA bus at 0x290. What has changed since 12.2 that causes the noshow and is there a solution? Is my problem Suse specific or should I ask de Gkrellm people? Sensors shows everything. # sensors acpitz-virtual-0 Adapter: Virtual device temp1: +18.5°C (crit = +75.0°C) w83697hf-isa-0290 Adapter: ISA adapter in0: +1.47 V (min = +3.97 V, max = +0.22 V) ALARM in2: +3.30 V (min = +0.91 V, max = +1.47 V) ALARM in3: +2.96 V (min = +0.11 V, max = +1.12 V) ALARM in4: +3.15 V (min = +1.15 V, max = +2.72 V) ALARM in5: +0.61 V (min = +3.84 V, max = +2.38 V) ALARM in6: +3.57 V (min = +3.46 V, max = +0.35 V) ALARM in7: +3.23 V (min = +0.13 V, max = +3.01 V) ALARM in8: +3.12 V (min = +1.57 V, max = +1.79 V) ALARM fan1: 2450 RPM (min = 45000 RPM, div = 2) ALARM fan2: 3214 RPM (min = 27000 RPM, div = 2) ALARM temp1: +36.0°C (high = -95.0°C, hyst = +47.0°C) sensor = thermistor temp2: +18.5°C (high = +70.0°C, hyst = +65.0°C) sensor = CPU diode beep_enable: enabled -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.3 Milestone 1 (i586) Kernel: 3.6.3-1-default KDE Development Platform: 4.9.80) 14:36pm up 0:08, 3 users, load average: 1.96, 4.79, 2.76 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] BUG -- programs requiring specific library versions -- not 'minimum versions'...
by Linda Walsh 12 Dec '12

12 Dec '12

Nelson Marques wrote: >> Example -- make gvim dependent on 'perl', then it runs no matter >> what the version. > > I think that what you missed was one very important thing: > > * libperl.so does not include any interface version number - since it > provides embedded perl functionality you need some versioning. --- Who is 'you'? Vim doesn't need it. Vim only uses libperl to provide optional perl functionality to be used by the user at run time. Even in perl, if you do a: "use 5.14.0;" That only give you an assurance that you are running, at least, under 5.14.0 OR higher. It's not limited to 5.14.0. Even perl does not restrict programs to a fixed version. But Suse added exact version requirements to vim and and other programs making it impossible to upgrade piecemeal. It's one thing to say you must have *at least* this version, but requiring *exact* versions is Bad software practice. It is as bad or worse than hard-coding absolute pathnames. Many programs under the 12.X series now have exact dependencies on GLIB x.14, x.15, x.16... etc... (12.1/12.2/factory), which means binaries from one version are BOTH forwards and backwards incompatible. That's a violation of basic software design and support that is unthinkable. It would be like all software vendors 'failing' to load if MS updates any library. That is a worse case of DLL hell that what MS had. MS's DLL hell happened because they only allowed 1 version of a shared library **in memory** at the same time. If an old piece of software loaded an old version of some library, then a newer piece of software wouldn't load because it needed a newer version of the library that couldn't be loaded. They fixed this in Vista, about 8-9 years ago. In the suse version of DLL hell, they only allow 1 version of a library to be loaded onto a machine at all (as rpm will uninstall old versions). AND -- software doesn't have requirements for a "MINIMUM" version, but an exact version -- meaning that newer versions of the library can't be used to support old versions. Generally speaking libraries are **usually** backwards compatible and this type of requirement is unnecessary. When there is a large interface change, you end up with a major re-release of the library -- like libreadline5 + libreadline6 -- both of which can be used and required at the same time. This is what I meant earlier by suse creating damage much faster than I can even documented it, let alone fix. That's even assuming I wasn't argued to death about why standard software practices were no longer reasonable or desirable... which isn't the case with many developers who feel bad SW design should be justified rather than fixed. More than one person has said, we don't care what you want -- this what we are doing and this is what is going to be, deal with it. That type of attitude indicates they don't care about users or anyone other than themselves. This is the suse "community"?? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Tumbleweed: unresolveable GLIBC
by Marcel "Ammler" Gmür 11 Dec '12

11 Dec '12

got the following issue on every package for repository Tumbleweed: unresolvable: nothing provides libc.so.6(GLIBC_2.15)(64bit) needed by libglib-2_0-0, nothing provides libpcre.so.1()(64bit) needed by libglib-2_0-0 https://build.opensuse.org/project/monitor?project=home%3Aopenttdcoop&succe… It might need some rebuild on the repo, right? Greets & Thanks Ammler -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] Tumbleweed - After running zypper dup Mozilla products including Chromium do not start up
by Roman Bysh 11 Dec '12

11 Dec '12

Hello List mates, I ran zypper dup over the last 2 - 3 days. And, I found Firefox Chromium and Thunderbird NOT starting up. firefox /usr/lib64/firefox/firefox: symbol lookup error: /usr/lib64/libpangocairo-1.0.so.0: undefined symbol: g_object_replace_qdata mantrid@opensuse~] $ thunderbird /usr/lib64/thunderbird/thunderbird-bin: symbol lookup error: /usr/lib64/libpangocairo-1.0.so.0: undefined symbol: g_object_replace_qdata The mouse was very sluggish. Cheers! Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 15

[opensuse-factory] Tumbleweed - kvm 1.3.0-5.1 error with usb2 controller
by ConteZero 11 Dec '12

11 Dec '12

After kvm update to 1.3.0-5.1 virt-manager gives the following error: Error starting domain: unsupported configuration: ich9-usb-ehci1 not supported in this QEMU binary Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 117, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1098, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 682, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: unsupported configuration: ich9-usb-ehci1 not supported in this QEMU binary The problem is the USB controller settings in the virtual machine, with model "USB 2" I've the error, if I change to model "default" it works. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 11 Dec '12

11 Dec '12

Ken Schneider - openSUSE wrote: > On 11/28/2012 07:07 PM, Linda Walsh pecked at the keyboard and wrote: > > Linda, > > You have been ask several times to stop cross posting, so once again > please stop. ---- Um which list does one post questions about current and future development and current releases on? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 6