August 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 629236] New: vlock cannot authenticate user - missing PAM configuration
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=629236 http://bugzilla.novell.com/show_bug.cgi?id=629236#c0 Summary: vlock cannot authenticate user - missing PAM configuration Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mike(a)mk-sys.cz QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9pre) Gecko/20100730 The vlock package is missing PAM configuration file /etc/pam.d/vlock so that vlock cannot authenticate users (default /etc/pam.d/other denies everyone). In default installation, even with suitable /etc/pam.d/vlock, vlock still cannot authenticate users (unless run by root) as vlock-main does not have SGID bit and cannot read /etc/shadow. But this seems intentional according to /etc/permissions.* However, these files should set permissions of /usr/sbin/vlock-main rather than /usr/bin/vlock as the latter is a shell script now. Reproducible: Always Steps to Reproduce: 1. lock a terminal using vlock 2. press enter Actual Results: vlock doesn't ask for password and shows "authentication failure" Expected Results: ask for password and check it -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 629160] New: YaST2 printer module should offer 2 page test print
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=629160 http://bugzilla.novell.com/show_bug.cgi?id=629160#c0 Summary: YaST2 printer module should offer 2 page test print Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alanprescott(a)yahoo.co.uk QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.95 (like Gecko) SUSE Whilst the option to run a test print whilst configuring a printer is extremely useful it would be very useful if the test print was more than a single side when configuring printers with Duplex units. ATM the only way to be sure that duplex has been configured correctly is to leave the printer module and print a known 2-sided document and then go back into to module to make any corrections. If a 2 page test print was available from within the printer module this wouldn't be necessary. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 629096] New: polkit-default-privs: add support for org.gnome.settingsdaemon.datetimemechanism.*
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=629096 http://bugzilla.novell.com/show_bug.cgi?id=629096#c0 Summary: polkit-default-privs: add support for org.gnome.settingsdaemon.datetimemechanism.* Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: lnussel(a)novell.com ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- The polkit helper to set date/time information is moving from gnome-panel to gnome-settings-daemon in GNOME 2.31/2.32. This is the exact same code, with the same methods/policies, but it moved so it can be used by more people. Replacing org.gnome.clockapplet.mechanism with org.gnome.settingsdaemon.datetimemechanism would be enough to update polkit-default-privs. Note that the changes will be in G:F soon and will hit Factory only in a few days, I guess. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 628698] New: [cups-drivers-splix] problems with CLP-315 printer
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=628698 http://bugzilla.novell.com/show_bug.cgi?id=628698#c0 Summary: [cups-drivers-splix] problems with CLP-315 printer Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: af1n(a)o2.pl QAContact: jsmeix(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 There are 2 problems: 1. Please enable J-BIG compression in Splix "SpliX J-BIG compression algorithm has been disabled during the compilation. Please recompile SpliX and enable the J-BIG compression algorithm." 2. Cups is looking for cms profile in: /usr/share/cups/model/samsung/cms/CLP-300cms but the current path in opensuse for this file is: /usr/share/cups/model/Samsung/cms/CLP-300cms If i don't link: ln -s /usr/share/cups/model/Samsung /usr/share/cups/model/samsung i get the following error: "SpliX Cannot open CMS file /usr/share/cups/model/samsung/cms/CLP-300cms (2)" There is actually a third problem... Neither cups nor Yast doesn't detect this printer. I had to go around this problem using URL based discovery parallel:/dev/usb/lp0. There is also a problem with udev, it keeps the permissions of /dev/usb/lp0 as crw-rw---- 1 root users 180, 0 2010-08-05 14:48 /dev/usb/lp0 and cups cannot access it, i get the following error from cups: "Unable to open device file "/dev/usb/lp0": Permission denied" When i change the rights using: chmod a+rwx /dev/usb/lp0 Then cups starts to display the J-BIG error and cms errors :) Reproducible: Always Steps to Reproduce: 1. zypper install cups-drivers-splix 2. plug in the printer 3. do: chmod a+rwx /dev/usb/lp0 4. do: ln -s /usr/share/cups/model/Samsung /usr/share/cups/model/samsung 5. add the printer to cups using parallel:/dev/usb/lp0 6. print a test page Actual Results: A nice set of cups errors, like: - "SpliX J-BIG compression algorithm has been disabled during the compilation" - "SpliX Cannot open CMS file /usr/share/cups/model/samsung/cms/CLP-300cms (2)" - "Unable to open device file "/dev/usb/lp0": Permission denied" Expected Results: A nice colorful test painted by the printer. I get the following errors in dmesg after connecting the printer: [860262.191049] usb 1-3: new high speed USB device using ehci_hcd and address 55 [860262.246967] hub 1-0:1.0: unable to enumerate USB device on port 3 [860262.456106] usb 1-3: new high speed USB device using ehci_hcd and address 56 [860262.511347] hub 1-0:1.0: unable to enumerate USB device on port 3 [860262.721068] usb 1-3: new high speed USB device using ehci_hcd and address 57 [860262.776353] hub 1-0:1.0: unable to enumerate USB device on port 3 [860262.986397] usb 1-3: new high speed USB device using ehci_hcd and address 58 [860263.041601] hub 1-0:1.0: unable to enumerate USB device on port 3 [860263.251342] usb 1-3: new high speed USB device using ehci_hcd and address 59 [860263.306627] hub 1-0:1.0: unable to enumerate USB device on port 3 [860263.516283] usb 1-3: new high speed USB device using ehci_hcd and address 60 [860263.571606] hub 1-0:1.0: unable to enumerate USB device on port 3 [860263.781360] usb 1-3: new high speed USB device using ehci_hcd and address 61 [860263.836594] hub 1-0:1.0: unable to enumerate USB device on port 3 [860264.046309] usb 1-3: new high speed USB device using ehci_hcd and address 62 [860264.102591] hub 1-0:1.0: unable to enumerate USB device on port 3 [860264.313138] usb 1-3: new high speed USB device using ehci_hcd and address 63 [860264.827040] usb 1-3: device not accepting address 63, error -71 [860264.929093] usb 1-3: new high speed USB device using ehci_hcd and address 64 [860264.984419] hub 1-0:1.0: unable to enumerate USB device on port 3 [860265.194049] usb 1-3: new high speed USB device using ehci_hcd and address 65 [860265.321862] usb 1-3: device descriptor read/all, error -71 [860265.424077] usb 1-3: new high speed USB device using ehci_hcd and address 66 [860265.940064] usb 1-3: device not accepting address 66, error -71 [860266.042074] usb 1-3: new high speed USB device using ehci_hcd and address 67 [860266.068997] usb 1-3: device descriptor read/8, error -71 [860266.195364] usb 1-3: device descriptor read/8, error -71 [860266.399067] usb 1-3: new high speed USB device using ehci_hcd and address 68 [860266.425496] usb 1-3: device descriptor read/all, error -71 [860266.426344] hub 1-0:1.0: unable to enumerate USB device on port 3 [860266.667089] usb 4-1: new full speed USB device using uhci_hcd and address 33 [860266.801115] usb 4-1: not running at top speed; connect to a high speed hub [860266.834120] usb 4-1: New USB device found, idVendor=04e8, idProduct=328e [860266.834129] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [860266.834135] usb 4-1: Product: CLP-310 Series [860266.834140] usb 4-1: Manufacturer: Samsung Electronics Co., Ltd. [860266.834144] usb 4-1: SerialNumber: 1434BAGQ700024P [860266.842212] usblp0: USB Bidirectional printer dev 33 if 0 alt 0 proto 2 vid 0x04E8 pid 0x328E Output from lsusb: 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 can't get debug descriptor: Connection timed out cannot read device status, Connection timed out (110) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 24

[Bug 628487] New: Courier config files come with TLS_CERTFILE=/usr/share/courier-imap/pop3d.pem
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=628487 http://bugzilla.novell.com/show_bug.cgi?id=628487#c0 Summary: Courier config files come with TLS_CERTFILE=/usr/share/courier-imap/pop3d.pem Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: chris(a)computersalat.de ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- /etc/courier/pop3d-ssl and /etc/courier/imapd-ssl come with this default: TLS_CERTFILE=/usr/share/courier-imap/pop3d.pem This feels like having a deja-vu, see bug 241937 and bug 341267 :-/ Please fix it again;-) It looks like /usr/share/courier-imap/mkimapdcert (which is called from the courier-*-ssl initscripts when $TLS_CERTFILE doesn't exist) will generate the certificate in /usr/share/courier-imap/. The certificate should be somewhere in /etc/ - /etc/ssl/private would probably be the best place. Please fix the location in the config files and the mkimapdcert script. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 628256] New: sysvinit: Id "x0" respawning too fast
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=628256 http://bugzilla.novell.com/show_bug.cgi?id=628256#c0 Summary: sysvinit: Id "x0" respawning too fast Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- On tty1 of the domU I constantly get INIT: Id "x0" respawning too fast: disabled for 5 minutes This is because the xen console is attached by default (as installed by "vm-install") to tty1 and not xvc0, i.e. there is no /dev/xvc*. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 628243] New: corosync: dies after start
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=628243 http://bugzilla.novell.com/show_bug.cgi?id=628243#c0 Summary: corosync: dies after start Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: tserong(a)novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- After starting corosync (using fixed rpms, bug #623427), most of its children instantly die. 4178 ? Ssl 0:00 /usr/sbin/corosync 4188 ? S 0:00 \_ /usr/lib64/heartbeat/crmd 4204 ? Z 0:00 \_ [cib] <defunct> 4205 ? Z 0:00 \_ [attrd] <defunct> 4206 ? Z 0:00 \_ [pengine] <defunct> 4207 ? Z 0:00 \_ [stonithd] <defunct> -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 15

[Bug 628233] New: CUPS default "RIPCache 8m" causes various kind of printout failures
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=628233 http://bugzilla.novell.com/show_bug.cgi?id=628233#c0 Summary: CUPS default "RIPCache 8m" causes various kind of printout failures Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEEDINFO Severity: Major Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: jsmeix(a)novell.com QAContact: jsmeix(a)novell.com CC: roger.larsson(a)e-gatan.se, manchette(a)free.fr InfoProvider: coolo(a)novell.com Found By: Development Blocker: --- By default CUPS has only 8 MB RIPCache, see "RIPCache" at http://www.cups.org/documentation.php/doc-1.4/ref-cupsd-conf.html -------------------------------------------------------------------- The RIPCache directive sets the size of the memory cache used by Raster Image Processor ("RIP") filters such as imagetoraster and pstoraster ... The default cache size is "8m", or 8 megabytes. -------------------------------------------------------------------- This default exits since a long time and did not cause any issue. But since a few month more and more weird issues regarding printout failures happen because of this low default. When RIPs need much more memory, they may simply fail so that there is no printout at all, see bug #625611 or https://answers.launchpad.net/hplip/+question/104395 When RIPs need a bit more memory, they may not fail but produce broken output which is even worse because it wastes paper and toner/ink for nonsense printouts, see attachment #380232 from https://bugzilla.novell.com/show_bug.cgi?id=603131#c25 CUPS upstream agrees to increase the default RIPCache, see http://www.cups.org/str.php?L3535 There is also a discussion whether or not to have a fixed RIPCache size by default at all, see the thread about "Sense and nonsense of RIPCache" in the cups.general newsgroup/forum on http://www.cups.org/newsgroups.php?gcups.general+Q"Sense+and+nonsense+of+RIPCache" For the current openSUSE 11.3 I would like to provide a CUPS packages update where the one line RIPCache 128m is added to /etc/cups/cupsd.conf (by default there is no "RIPCache" line in /etc/cups/cupsd.conf which means CUPS' built-in default cache size is used). I think to make sure those line gets added in any case to the user's /etc/cups/cupsd.conf it is best to add it via "sed" magic via RPM post-install script if there is not yet a "RIPCache" line in the user's /etc/cups/cupsd.conf (e.g. when a server admin had already specified his specific RIPCache value). 128 MB is half of the minimum required RAM (256 MB) and a quater of the recommended RAM (512 MB) for a system where openSUSE is to be installed (according to what I found on a openSUSE 11.2 box) so that "RIPCache 128m" should be a safe default which can be set on any user's system. Coolo, do you agree that I do such a CUPS packages update? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 65

[Bug 628138] New: Non-dialup interfaces do not appear in smpppd front-ends
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=628138 http://bugzilla.novell.com/show_bug.cgi?id=628138#c0 Summary: Non-dialup interfaces do not appear in smpppd front-ends Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: xgpub(a)tellas.gr QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.1 Firefox/3.6.8 This looks very much like Bug 547978. # grep USERCONTROL /etc/sysconfig/network/ifcfg-* /etc/sysconfig/network/ifcfg-dsl0:USERCONTROL='yes' /etc/sysconfig/network/ifcfg-eth0:USERCONTROL='no' /etc/sysconfig/network/ifcfg-eth1:USERCONTROL='yes' /etc/sysconfig/network/ifcfg-eth2:USERCONTROL='no' /etc/sysconfig/network/ifcfg-lo:USERCONTROL=no /etc/sysconfig/network/ifcfg-tun0:USERCONTROL='yes' # cinternet -I --verbose trying to connect local smpppd 01 a dsl0 Everything worked great in 11.2. Reproducible: Always Steps to Reproduce: 1. install smpppd 2. switch to "Traditional Method with ifup" and configure your network interface ethX or tunX with enabled user control 3. try to contrl them via cinternet or k/qinternet (which don't show any controllable non-dialup interfaces) Actual Results: There is no way to control non-dialup interfaces via smpppd front-ends like cinternet/qinternet/kinternet. Expected Results: Non-dialup user controllable interfaces should appear in smpppd front-ends. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 21

[Bug 627969] New: Install with NFS mounts not available result in negative disk space cost calc
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=627969 http://bugzilla.novell.com/show_bug.cgi?id=627969#c0 Summary: Install with NFS mounts not available result in negative disk space cost calc Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: darryl.miles(a)darrylmiles.org QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.7) Gecko/20100713 Firefox/3.6.7 When installing and specifying NFS mounts. If these mount points are not able to be mounted during installation time they result in a negative amount of space requirements for storage calcualtion. This results in being unable to progress the install. In my case the mount points were not even to any location that the installation may have written to, they were places like /nfs/foobar/dir and /nfs/foobar. Also the reason they would not mount was due to the use of a short label for the hostname (which has yet to be setup in /etc/hosts) to that the 'df' output looks pretty. So the issue here is that the system could ignore mount points that are not required by the installation process (since they are not part of the normal file system paths). It shouldn't mark the storage requirements with a negative figure, this is non-intuative as to the real problem. Which is that it the installation has been unable to mount/verify the NFS server. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5