openSUSE Users July 2012

users@lists.opensuse.org

142 participants
141 discussions

[opensuse] Printing with Canon IP1600 - cups thinks success, but nothing comes out

by Myrosia Dzikovska

I am trying to get a Canon IP1600 to print in OpenSuse 12.1. There are ubuntu instructions on the web, that I am trying to adapt http://askubuntu.com/questions/41615/how-to-install-canon-pixma-ip1600 I downloaded the drivers, tracked down older libraries (gtk1), and installed the rpms. The ppd file needed minor corrections, to say resolution 600x600 instead of 600/600, but with that passed the cupstestppd. Yast print setup happily detects the printer, reads in the ppd file, and lets me choose the ip2200 driver (which according to the docs should support ip1600 as well) . But when I print a test page, nothing comes out of the printer. The cups error log is attached. It contains no errors - cups clearly thinks that all is well. I tried using the command it logs from the command line, with a ps file, but that just got a bunch of stuff printed on the console instead of going to the printer. What could be going wrong here? (logged command) /usr/bin/gs -r600 -g4958x7016 -q -dNOPROMPT -dSAFER -sDEVICE=ppmraw -sOutputFile=- -| /usr/local/bin/cifip2200 --imageres 600 --papersize a4 --media plain --quality 3 --bbox 9,14,585,834 Thanks Myrosia

9 years, 10 months

[opensuse] How to submit bug reports that actually get to a package maintainer

by Karl Ove Hufthammer

Dear list members, I have read http://en.opensuse.org/openSUSE:Submitting_bug_reports on submitting bug reports. And about a year ago I submitted a bug report on a packaging bug in the ‘neverball’ package (official OSS repository), using the above guidelines: https://bugzilla.novell.com/show_bug.cgi?id=699124 This never got a reply, and it looks like the assignee (which was automatically selected by Bugzilla) is a person that haven’t worked on openSUSE for *many* years, and probably will never look at the bug report (since he’s now at Canonical). Since the official way of reporting bugs in packages (like this one) doesn’t work, who should I contact, or where should I submit packaging bug reports so that they get to people that actually are able to do anything about them? I’d be grateful for any advice. -- Karl Ove Hufthammer http://huftis.org/ Jabber: karl(a)huftis.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 10 months

[opensuse] Still wanting to upgrade to 12.1 ..............

by Duaine Hechler

with the following conditions fixed. I would like to here from persons that have had these problems fixed. - Can't get my MB sound card to work (Intel ICH7) consistent. - alsasound will not stay "yes" in the system service levels. - rcalsasound or alsactl reports (alsa) "inactive" - and - can't get it active. - Can't get my display to stay at 1024x768 - Can't get rid of the "Nepomuk Indexing Disabled) popups TIA, Duaine -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler(a)att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 10 months

[opensuse] GNOME:Stable:3.4 on openSUSE 12.2

by Roger Oberholtzer

For a while the evolution app in openSUSE 12.1 has been failing. I have used other readers while waiting for a fix. I decided that perhaps a better solution was to add GNOME:/STABLE:/3.4/ and see what that evolution does. Perhaps not one of my better solutions. Aside from evolution still not starting (for apparently different reasons), things like ConsoleKit are now failing. I get a popup message when logging in to KDE about this. So, networking and other things are now broken. I see that a common complaint is that there are undefined symbols. For example, one of the libraries that was updated is: /usr/lib/libpolkit-gobject-1.so.0 and it complains that g_mutex_lock is not defined. This file comes from libpolkit0, which was built July 2. So I would think some other person would have experienced any obvious problem. Other libs make other complaints. But the common thing is that the undefined functions all start with 'g_'. So I am guessing some GNOME library did not get updated. There were no errors when I did the update. So whatever was installed was considered consistent by zypper. Perhaps there is a missing dependency. I also have GNOME:Apps enabled. My KDE is from KDE:Release:48. Perhaps there is some dependency interaction? I do not have any Factory repos. Anyone else been there done that? Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 And remember: It is RSofT and there is always something under construction. It is like talking about large city with all constructions finished. Not impossible, but very unlikely. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 10 months

[opensuse] smbd does not start in oS 12.1

by Istvan Gabor

Hello: In my openSUSE 12.1 system smbd does not start at boot. I use systemd. ~> smbclient -L localhost WARNING: The security=share option is deprecated WARNING: no network interfaces found Enter user's password: Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED) ~> ps -e|grep -i nmb ~> ~> ps -e|grep -i smb 4344 ? 00:00:00 smbd 4359 ? 00:00:00 smbd ~> Related line in /var/log/messages: Jul 12 12:20:11 linux nmb[3937]: Starting Samba NMB daemon ..failed Jul 12 12:20:11 linux systemd[1]: nmb.service: control process exited, code=exited status=7 Jul 12 12:20:11 linux systemd[1]: Unit nmb.service entered failed state. Jul 12 12:20:11 linux smbd[4334]: [2012/07/12 12:20:11.474016, 0] lib/interface.c:543(load_interfaces) Jul 12 12:20:11 linux smbd[4334]: WARNING: no network interfaces found Jul 12 12:20:11 linux smb[4287]: Starting Samba SMB daemon ..done I found this: http://lists.opensuse.org/opensuse-bugs/2012-01/msg00755.html https://bugzilla.novell.com/show_bug.cgi?id=739360 but I think my problem can be differewnt since I have up to date samba packages: samba-client-32bit-3.6.3-34.12.1.x86_64 samba-3.6.3-34.12.1.x86_64 If I restart nmbd and smbd manually, they work. What should I check? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 10 months

[opensuse] Laptop recommendation

by Lívio Cipriano

Hi, I want to buy a laptop, preference with 17" screen. Any recommendations(s)? Regards Lívio Cipriano -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 10 months

[opensuse] Re: Why bin & no bin64? => lets fix lib64=>lib, bin(32),lib(32)=>/usr32/{bin,lib}

by Linda Walsh

Nelson Marques wrote: > Ever heard of FHS? It's stands for Filesystem Hierarchy Standard. > > Enjoy the reading :) ---- It is based on really screwed up reasoning. Why was it accepted? Regardless, Suse doesn't follow it now, so why not move ahead with a more soundly reasoned solution. Seems a smart solution would be to use a separate file-system namespace with everything but the bin & lib directories being the same between 32&64 bit. Would provid transparency. Their rational .. that lib(X) is architecture dependent, also applies to /bin, yet they don't apply the same reasoning. ... more specifically under specific options, they also say: lib<qual> Alternate format essential shared libraries (optional) "Lib<qual>" is for an alternate format. Alternate to what? I would assert alternate format doesn't mean native format. And that on a X64 machine running an X64 kernel where x32 compatibility is *optional*, that it is 32-bit dirs that are optional. So the document is internally inconsistent besides being. ========= I think having a smart loader that virtualizes the arch-dependent dirs. To make it arch, blind, create a /usr64/{bin,lib}, then on any given machine, /usr/{bin,lib} can be mounts/links to the native binaries (/usr64 or /usr32...)... Rational -- their rational was based on 8 year old data when x86-32 packages out numbered x86-64 packages. Clearly that doesn't apply on a modern x86-64 bit system -- where it's better than 3:1 64-bit (linux certainly has taken the lead on this). Existing 32 bit binaries would almost never work on a 64 bit system -- you would need to have the same libraries installed.. Does suse support taking 32bit binaries from 2004 and installing them on a 2012-suse12.1 system? If not, the justification for this is negated. What they don't mention is that existing programs are rebuilt, often from sources, and will build with the defaults for that platform. That being the case, it would require modification of those programs to work if their lib path wasn't "/usr/lib". Supporting non-recompiled binaries from 8 or more years prior, I don't think has ever been supported. What were they thinking? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 11 months

[opensuse] Buggy thunderbird 13?

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 With this "versionitis" of thunderbird, the program is in fact worse than ever. For example, twice I had the mouse pointer converted to a miniature page that I assume I have to drop at some folder for the operation to complete. But I can not drop the page anywhere! ESC does not work, and I retain that useless mouse pointer even if I go to an xterm. Clicking anywhere in the desktop does not work, not even outside Th. I have to alt-tab to an xterm, get the PID and kill thunderbird, using the keyboard, the mouse is dead till I kill Th. Another problem. Eventually, when syncing for off-network usage, it says that some operation did not complete because some folder is busy doing something else. I have to click ok and continue. This message is new. What on earth do I care the problems it finds? I want it to shut up and do its job as it always did. It doesn't even say what folder is busy and doing what and ordered by whom, so that I have a chance of killing that operation. Anybody else has seen this? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAlALCnAACgkQtTMYHG2NR9UHSQCghX8dU1/tmfnHIxKlWnkiD60+ TNUAn0ke2x8IZwA8wA3VGa50xtfiE1Al =ysai -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 11 months

Re: [opensuse] How to submit bug reports that actually get to a package maintainer

by Wilfred van Velzen

On Tue, Jul 31, 2012 at 2:18 PM, Andreas Jaeger <aj(a)suse.com> wrote: > When entering a bug, you only set SEverity - not Priority. > > Clicking on Severity gives: > https://bugzilla.novell.com/page.cgi?id=fields.html#bug_severity > > and below severity is priority: > "This field is utilized by the programmers/engineers to prioritize their > work to be done. " > > If you go from bugs.opensuse.org, you can find also this page: > http://en.opensuse.org/openSUSE:Bug_definitions#Bug_Priorities > > Regarding importance, the importance links to a text field that explains > this as well. > > Yes, it's not well known but it's documented and some engineers work as > I explained. Ok, thanks for the explanation. Maybe only the 'Assignee' should be able to change the priority? (If that's practically possible) -- Met vriendelijke groet / Best regards, Wilfred van Velzen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 11 months

Re: [opensuse] How to submit bug reports that actually get to a package maintainer

by Wilfred van Velzen

> >>On 2012-07-31 at 09:44, Marcus Meissner <meissner(a)suse.de> wrote: > On Tue, Jul 31, 2012 at 09:10:47AM +0200, Karl Ove Hufthammer wrote: > > Dear list members, > > > > I have read http://en.opensuse.org/openSUSE:Submitting_bug_reports > > on submitting bug reports. And about a year ago I submitted a bug report > > on a packaging bug in the ‘neverball’ package (official OSS repository), > > using the above guidelines: > > https://bugzilla.novell.com/show_bug.cgi?id=699124 > > > > This never got a reply, and it looks like the assignee (which was > > automatically selected by Bugzilla) is a person that haven’t worked > > on openSUSE for *many* years, and probably will never look at the bug > > report (since he’s now at Canonical). > > > > Since the official way of reporting bugs in packages (like this one) > > doesn’t work, who should I contact, or where should I submit packaging > > bug reports so that they get to people that actually are able to do > > anything about them? I’d be grateful for any advice. > > I assigned it someone else. > > You could look through the maintainers in the "games" repository where > neverball lives and mail them. > > Or this list. > > Or you can fix this yourself via OBs collaboration and do a submitrequest:) > > Ciao, Marcus I've reported a bug that got absolutely zero responses or activity. Didn't even get triaged yet in 2 months time... https://bugzilla.novell.com/show_bug.cgi?id=764739 -- Met vriendelijke groet / Best regards, Wilfred van Velzen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 years, 11 months

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users July 2012