June 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 881364] New: Yast Configuration of Mailserver fails when reading/modifying mail transport from openLDAP
by bugzilla_noreply＠novell.com 05 Jun '14

05 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881364 https://bugzilla.novell.com/show_bug.cgi?id=881364#c0 Summary: Yast Configuration of Mailserver fails when reading/modifying mail transport from openLDAP Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: michael.hieb(a)celoso.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=593339) --> (http://bugzilla.novell.com/attachment.cgi?id=593339) yast.log and openldap debugging recorded in system.log User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31 Using yast2 on openSuSe 13.1 to configure mailserver (postfix+cyrus+openLDAP) - as I have many times in the past witut problems on older distributions, I am encountering the following problems (similar to bug reported in 874083). 1. OpenLDAP server and client are set up listening on 389 and 636 (SSL). Schemas for dnszone and suse-mailserver are loaded. 2. Tested with ldapsearch and testsasl. All works fine. 3. When using yast to configure mailserver (advanced) I get the following four errors: Cannot read mail server transports Cannot read mail server preventions Cannot read mail server relay settings Cannot read mail serve local delivery settings 4. As well, changes to configuration of mail transport, etc.. do not stick. Next time we run yast they are missing again. As well menus for local transport, e.g. cyrus, are missing. I turned on logging for the ldap server and examined the yast logs (see below). As the first error is generated "Cannot read mail server transports" there is the following error in yast log: 2014-06-02 21:22:36 <3> pacaya(26981) [agent-ldap] LdapAgent.cc(debug_exception):505 ldap error while modifying cn=userTemplate,dc=celoso,dc=net (32): No such object 2014-06-02 21:22:36 <3> pacaya(26981) [-e] SCR_INIT_FAILED[2655:/usr/share/YaST2/modules/YaPI/MailServer.pm] LDAP modify failed 2014-06-02 21:22:36 <3> pacaya(26981) [-e] Description: 32 : No such object 2014-06-02 21:22:36 <3> pacaya(26981) [Ruby] modules/MailServer.rb:412 Cannot read mail server transports. In syslog from ldap server I see: 2014-06-02T21:24:46.862906+01:00 pacaya slapd[26799]: conn=2181 op=3 SRCH base="dc=celoso,dc=net" scope=2 deref=0 filter="(objectClass=suseUserTemplate)" 2014-06-02T21:24:46.863068+01:00 pacaya slapd[26799]: => bdb_filter_candidates 2014-06-02T21:24:46.863237+01:00 pacaya slapd[26799]: #011AND 2014-06-02T21:24:46.863444+01:00 pacaya slapd[26799]: => bdb_list_candidates 0xa0 2014-06-02T21:24:46.863626+01:00 pacaya slapd[26799]: => bdb_filter_candidates 2014-06-02T21:24:46.863814+01:00 pacaya slapd[26799]: #011OR 2014-06-02T21:24:46.864009+01:00 pacaya slapd[26799]: => bdb_list_candidates 0xa1 2014-06-02T21:24:46.864206+01:00 pacaya slapd[26799]: => bdb_filter_candidates 2014-06-02T21:24:46.864572+01:00 pacaya slapd[26799]: #011EQUALITY 2014-06-02T21:24:46.864776+01:00 pacaya slapd[26799]: <= bdb_filter_candidates: id=0 first=0 last=0 2014-06-02T21:24:46.864973+01:00 pacaya slapd[26799]: => bdb_filter_candidates 2014-06-02T21:24:46.865173+01:00 pacaya slapd[26799]: #011EQUALITY 2014-06-02T21:24:46.865539+01:00 pacaya slapd[26799]: <= bdb_filter_candidates: id=1 first=6 last=6 2014-06-02T21:24:46.865738+01:00 pacaya slapd[26799]: <= bdb_list_candidates: id=1 first=6 last=6 2014-06-02T21:24:46.865965+01:00 pacaya slapd[26799]: <= bdb_filter_candidates: id=1 first=6 last=6 2014-06-02T21:24:46.866165+01:00 pacaya slapd[26799]: <= bdb_list_candidates: id=1 first=6 last=6 2014-06-02T21:24:46.867305+01:00 pacaya slapd[26799]: <= bdb_filter_candidates: id=1 first=6 last=6 2014-06-02T21:24:46.867500+01:00 pacaya slapd[26799]: => test_filter 2014-06-02T21:24:46.867639+01:00 pacaya slapd[26799]: EQUALITY 2014-06-02T21:24:46.867769+01:00 pacaya slapd[26799]: <= test_filter 6 2014-06-02T21:24:46.867894+01:00 pacaya slapd[26799]: conn=2181 op=3 SEARCH RESULT tag=101 err=0 nentries=1 text= 2014-06-02T21:24:46.868022+01:00 pacaya slapd[26799]: conn=2181 op=4 BIND anonymous mech=implicit ssf=0 2014-06-02T21:24:46.868162+01:00 pacaya slapd[26799]: conn=2181 op=4 BIND dn="cn=Administrator,dc=celoso,dc=net" method=128 2014-06-02T21:24:46.868301+01:00 pacaya slapd[26799]: conn=2181 op=4 BIND dn="cn=Administrator,dc=celoso,dc=net" mech=SIMPLE ssf=0 2014-06-02T21:24:46.868481+01:00 pacaya slapd[26799]: conn=2181 op=4 RESULT tag=97 err=0 text= 2014-06-02T21:24:46.868684+01:00 pacaya slapd[26799]: connection_input: conn=2181 deferring operation: binding 2014-06-02T21:24:46.868813+01:00 pacaya slapd[26799]: conn=2181 op=5 MOD dn="cn=userTemplate,dc=celoso,dc=net" Testing with ldapsearch I see the following: pacaya:~ # ldapsearch -H ldaps://pacaya.celoso.net -D "cn=Administrator,dc=celoso,dc=net" -W -v "cn=userTemplate,dc=celoso,dc=net" ldap_initialize( ldaps://pacaya.celoso.net:636/??base ) Enter LDAP Password: filter: cn=userTemplate,dc=celoso,dc=net requesting: All userApplication attributes # extended LDIF # # LDAPv3 # base <dc=celoso,dc=net> (default) with scope subtree # filter: cn=userTemplate,dc=celoso,dc=net # requesting: ALL # # search result search: 2 result: 0 Success # numResponses: 1 pacaya:~ # ldapsearch -H ldaps://pacaya.celoso.net -D "cn=Administrator,dc=celoso,dc=net" -W -v "cn=userTemplate" ldap_initialize( ldaps://pacaya.celoso.net:636/??base ) Enter LDAP Password: filter: cn=userTemplate requesting: All userApplication attributes # extended LDIF # # LDAPv3 # base <dc=celoso,dc=net> (default) with scope subtree # filter: cn=userTemplate # requesting: ALL # # usertemplate, ldapconfig, celoso.net dn: cn=usertemplate,ou=ldapconfig,dc=celoso,dc=net cn: usertemplate objectClass: top objectClass: suseObjectTemplate objectClass: suseUserTemplate suseDefaultValue: homeDirectory=/home/%uid suseDefaultValue: loginShell=/bin/bash suseNamingAttribute: uid susePlugin: UsersPluginLDAPAll # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 pacaya:~ # Reproducible: Always Steps to Reproduce: 1. configure openldap server and client in Network Services to run on localhost 2. load dnszone and suse-mailserver schemas into ldap server 3. run Network Services -> Mailserver Actual Results: 1. Obtain following four errors: Cannot read mail server transports Cannot read mail server preventions Cannot read mail server relay settings Cannot read mail serve local delivery settings 2. When I try to set Local Delivery (cyrus), Mail Transport, or Mailserver Domains, etc... the definition is missing when I leave and re-enter Yast2, i.e. information is not saved. Expected Results: Expect configuration to not generate errors, allow Local Delivery (cyrus), Mail Transport, or Mailserver Domains, etc... to be set. The bug looks similar to the bug reported in 874083, though the bug I am experiencing affects more than just the mailserver domains. The reporter of that bug states that he resolved his problem by "manually loading" the suse-mailserver.schema into ldap. If that is the solution, or you'd like me to test if it is a solution, I'll need an explanation of how to perform the manual load. -- Configure bugmail: https://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 881106] New: gcc: internal compiler error while compiling a 3.12.21 vanilla kernel
by bugzilla_noreply＠novell.com 05 Jun '14

05 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881106 https://bugzilla.novell.com/show_bug.cgi?id=881106#c0 Summary: gcc: internal compiler error while compiling a 3.12.21 vanilla kernel Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: schaefer.frank(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 [make all -j2] ... CC [M] fs/quota/quota_v2.o CC [M] drivers/gpu/drm/nouveau/core/engine/copy/nva3.o CC [M] fs/quota/quota_tree.o CC [M] drivers/gpu/drm/nouveau/core/engine/copy/nvc0.o LD fs/quota/built-in.o CC [M] drivers/gpu/drm/nouveau/core/engine/copy/nve0.o CC fs/ramfs/inode.o In file included from include/linux/fs.h:8:0, from fs/ramfs/inode.c:26: include/linux/dcache.h:161:1: internal compiler error: Speicherzugriffsfehler } ____cacheline_aligned; ^ In file included from include/linux/mmzone.h:797:0, from include/linux/gfp.h:4, from include/linux/slab.h:14, from drivers/gpu/drm/nouveau/core/os.h:5, from drivers/gpu/drm/nouveau/core/engine/copy/nve0.c:25: include/linux/memory_hotplug.h: In function ‘remove_memory’: include/linux/memory_hotplug.h:254:1: internal compiler error: Speicherzugriffsfehler static inline void remove_memory(int nid, u64 start, u64 size) {} ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://bugs.opensuse.org/> for instructions. Please submit a full bug report, with preprocessed source if appropriate. See <http://bugs.opensuse.org/> for instructions. make[2]: *** [fs/ramfs/inode.o] Fehler 1 make[1]: *** [fs/ramfs] Fehler 2 make[4]: *** [drivers/gpu/drm/nouveau/core/engine/copy/nve0.o] Fehler 1 make: *** [fs] Fehler 2 make: *** Warte auf noch nicht beendete Prozesse... make[3]: *** [drivers/gpu/drm/nouveau] Fehler 2 make[3]: *** Warte auf noch nicht beendete Prozesse... CC drivers/hid/hid-lg.o CC [M] drivers/gpu/drm/radeon/radeon_drv.o CC [M] drivers/gpu/drm/radeon/radeon_device.o CC drivers/hid/hid-lgff.o CC drivers/hid/hid-lg2ff.o CC drivers/hid/hid-lg3ff.o CC drivers/hid/hid-lg4ff.o CC [M] drivers/gpu/drm/radeon/radeon_asic.o CC drivers/hid/hid-debug.o CC [M] drivers/gpu/drm/radeon/radeon_kms.o [hangs] Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 881023] New: Impossible to access phone sd memory
by bugzilla_noreply＠novell.com 05 Jun '14

05 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881023 https://bugzilla.novell.com/show_bug.cgi?id=881023#c0 Summary: Impossible to access phone sd memory Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andrea.turrini(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 This bug report comes from https://forums.opensuse.org/showthread.php/498482-oS-13-1-problems-to-acces… I essentially just copy the original post since it should contain all needed info. Not sure whether I have chosen the right component: it seems to be a problem related to ModemManager since it behaves differently in oS 13.1 and oS 12.3 I have a galaxy ace S5830i but I can not access its sd memory from my oS 13.1 (kernel 3.11.10-11-desktop, x86_64) . When I connect the usb cable, /var/log/messages shows: 2014-06-02T14:28:02.423340+08:00 caradhras kernel: [ 4263.059574] usb 3-2: new high-speed USB device number 25 using xhci_hcd 2014-06-02T14:28:05.385289+08:00 caradhras kernel: [ 4266.025268] usb 3-2: Device not responding to set address. 2014-06-02T14:28:05.586328+08:00 caradhras kernel: [ 4266.226061] usb 3-2: Device not responding to set address. 2014-06-02T14:28:05.787297+08:00 caradhras kernel: [ 4266.427205] usb 3-2: device not accepting address 25, error -71 2014-06-02T14:28:06.146249+08:00 caradhras kernel: [ 4266.786555] usb 3-2: new high-speed USB device number 27 using xhci_hcd 2014-06-02T14:28:06.158290+08:00 caradhras kernel: [ 4266.799512] usb 3-2: New USB device found, idVendor=04e8, idProduct=685e 2014-06-02T14:28:06.158327+08:00 caradhras kernel: [ 4266.799555] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2014-06-02T14:28:06.158333+08:00 caradhras kernel: [ 4266.799566] usb 3-2: Product: BCM21553-Thunderbird 2014-06-02T14:28:06.158337+08:00 caradhras kernel: [ 4266.799575] usb 3-2: Manufacturer: Broadcom 2014-06-02T14:28:06.158350+08:00 caradhras kernel: [ 4266.799598] usb 3-2: SerialNumber: 0123456789ABCDEF 2014-06-02T14:28:06.163267+08:00 caradhras kernel: [ 4266.803997] usb-storage 3-2:1.0: USB Mass Storage device detected 2014-06-02T14:28:06.163307+08:00 caradhras kernel: [ 4266.804193] scsi14 : usb-storage 3-2:1.0 2014-06-02T14:28:06.164249+08:00 caradhras kernel: [ 4266.804721] cdc_acm 3-2:1.1: This device cannot do calls on its own. It is not a modem. 2014-06-02T14:28:06.164276+08:00 caradhras kernel: [ 4266.804836] cdc_acm 3-2:1.1: ttyACM0: USB ACM device 2014-06-02T14:28:06.168499+08:00 caradhras mtp-probe: checking bus 3, device 27: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2" 2014-06-02T14:28:06.169387+08:00 caradhras mtp-probe: bus: 3, device: 27 was not an MTP device 2014-06-02T14:28:08.897407+08:00 caradhras ModemManager[4278]: <info> Creating modem with plugin 'Generic' and '1' ports 2014-06-02T14:28:08.898001+08:00 caradhras ModemManager[4278]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2' successfully created 2014-06-02T14:28:08.997069+08:00 caradhras ModemManager[4278]: <warn> Modem couldn't be initialized: couldn't load current capabilities: Failed to determine modem capabilities. and nothing else, even if I choose to enable the USB storage on the phone. No notification appears on my DE (lxde) and no sd device is created. However, if I connect the same phone on my oS 12.3 (different laptop, still lxde), it works as expected and /var/log/messages shows: 2014-06-02T13:07:51.497338+08:00 orodruin kernel: [ 124.107126] usb 1-1: new high-speed USB device number 2 using ehci_hcd 2014-06-02T13:07:51.613311+08:00 orodruin kernel: [ 124.223102] usb 1-1: New USB device found, idVendor=04e8, idProduct=685e 2014-06-02T13:07:51.613339+08:00 orodruin kernel: [ 124.223109] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2014-06-02T13:07:51.613346+08:00 orodruin kernel: [ 124.223114] usb 1-1: Product: BCM21553-Thunderbird 2014-06-02T13:07:51.613350+08:00 orodruin kernel: [ 124.223118] usb 1-1: Manufacturer: Broadcom 2014-06-02T13:07:51.613354+08:00 orodruin kernel: [ 124.223122] usb 1-1: SerialNumber: 0123456789ABCDEF 2014-06-02T13:07:51.622306+08:00 orodruin mtp-probe: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1" 2014-06-02T13:07:51.623302+08:00 orodruin mtp-probe: bus: 1, device: 2 was not an MTP device 2014-06-02T13:07:51.689301+08:00 orodruin kernel: [ 124.299462] cdc_acm 1-1:1.1: This device cannot do calls on its own. It is not a modem. 2014-06-02T13:07:51.689352+08:00 orodruin kernel: [ 124.299607] cdc_acm 1-1:1.1: ttyACM0: USB ACM device 2014-06-02T13:07:51.690362+08:00 orodruin kernel: [ 124.300664] usbcore: registered new interface driver cdc_acm 2014-06-02T13:07:51.690387+08:00 orodruin kernel: [ 124.300667] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters 2014-06-02T13:07:51.714417+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info> (ttyACM0) opening serial port... 2014-06-02T13:07:51.715171+08:00 orodruin modem-manager[590]: <info> (ttyACM0) opening serial port... 2014-06-02T13:07:51.732304+08:00 orodruin kernel: [ 124.342049] Initializing USB Mass Storage driver... 2014-06-02T13:07:51.732338+08:00 orodruin kernel: [ 124.342244] scsi6 : usb-storage 1-1:1.0 2014-06-02T13:07:51.732343+08:00 orodruin kernel: [ 124.342382] usbcore: registered new interface driver usb-storage 2014-06-02T13:07:51.732347+08:00 orodruin kernel: [ 124.342386] USB Mass Storage support registered. 2014-06-02T13:07:52.734288+08:00 orodruin kernel: [ 125.344747] scsi 6:0:0:0: Direct-Access SAMSUNG S5830i Card 0000 PQ: 0 ANSI: 2 2014-06-02T13:07:52.735557+08:00 orodruin kernel: [ 125.345600] sd 6:0:0:0: Attached scsi generic sg1 type 0 2014-06-02T13:07:52.737353+08:00 orodruin kernel: [ 125.347755] sd 6:0:0:0: [sdb] Attached SCSI removable disk 2014-06-02T13:07:55.749450+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <warn> Couldn't probe for capabilities, probably not a GSM or CDMA modem 2014-06-02T13:07:55.750156+08:00 orodruin modem-manager[590]: <warn> Couldn't probe for capabilities, probably not a GSM or CDMA modem 2014-06-02T13:07:55.750770+08:00 orodruin modem-manager[590]: <info> (ttyACM0) closing serial port... 2014-06-02T13:07:55.751355+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info> (ttyACM0) closing serial port... 2014-06-02T13:07:55.754077+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info> (ttyACM0) serial port closed 2014-06-02T13:07:55.754742+08:00 orodruin modem-manager[590]: <info> (ttyACM0) serial port closed 2014-06-02T13:07:55.756790+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info> (ttyACM0) opening serial port... 2014-06-02T13:07:55.756820+08:00 orodruin modem-manager[590]: <info> (ttyACM0) opening serial port... 2014-06-02T13:07:59.776554+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <warn> Couldn't probe for capabilities, probably not a GSM or CDMA modem 2014-06-02T13:07:59.777899+08:00 orodruin modem-manager[590]: <warn> Couldn't probe for capabilities, probably not a GSM or CDMA modem 2014-06-02T13:07:59.778689+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info> (ttyACM0) closing serial port... 2014-06-02T13:07:59.779393+08:00 orodruin modem-manager[590]: <info> (ttyACM0) closing serial port... 2014-06-02T13:07:59.786316+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info> (ttyACM0) serial port closed 2014-06-02T13:07:59.787126+08:00 orodruin modem-manager[590]: <info> (ttyACM0) serial port closed 2014-06-02T13:08:04.106917+08:00 orodruin su: (to root) ori on /dev/pts/0 2014-06-02T13:08:04.108152+08:00 orodruin su: pam_unix(su:session): session opened for user root by ori(uid=1000) 2014-06-02T13:08:56.291323+08:00 orodruin kernel: [ 188.901114] sd 6:0:0:0: [sdb] 15519744 512-byte logical blocks: (7.94 GB/7.40 GiB) 2014-06-02T13:08:56.292293+08:00 orodruin kernel: [ 188.902251] sd 6:0:0:0: [sdb] No Caching mode page present 2014-06-02T13:08:56.292312+08:00 orodruin kernel: [ 188.902258] sd 6:0:0:0: [sdb] Assuming drive cache: write through 2014-06-02T13:08:56.294749+08:00 orodruin kernel: [ 188.904233] sd 6:0:0:0: [sdb] No Caching mode page present 2014-06-02T13:08:56.294779+08:00 orodruin kernel: [ 188.904240] sd 6:0:0:0: [sdb] Assuming drive cache: write through 2014-06-02T13:08:56.296288+08:00 orodruin kernel: [ 188.906650] sdb: sdb1 2014-06-02T13:08:56.978559+08:00 orodruin udisksd[1575]: Mounted /dev/sdb1 at /run/media/ori/9016-4EF8 on behalf of uid 1000 solid-hardware returns only: # solid-hardware listen Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Listening to add/remove events: Device Added: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2' Device Added: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0' Device Added: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1' Device Added: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2' Device Added: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/tty/ttyACM0' Device Removed: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0' Device Removed: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/tty/ttyACM0' Device Removed: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2' Device Removed: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1' Device Removed: udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2' and fdisk shows only my hard-disk. Following a suggestion in the forum, I tried to set DisableSwitching=1 in /etc/usb_modeswitch.conf but nothing changed, also because it seems that the device 04e8:685e is not in one of the usb_modeswitch related files. According to the technical specs of the laptop with oS 13.1, the USB port I used is a USB-2; if I use the USB-3 port, I obtain the same result. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 879906] New: mcelog lack support for recent CPUs
by bugzilla_noreply＠novell.com 05 Jun '14

05 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=879906 https://bugzilla.novell.com/show_bug.cgi?id=879906#c0 Summary: mcelog lack support for recent CPUs Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mjr19(a)cam.ac.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 The mcelog package is based on quite old source, and lacks full support for more recent Intel processors. The rpm changelog states that the sources were last updated on 17th Aug 2011, so support for many recent CPUs is absent. Suggest updating to a more recent upstream source tree, for upstream does have better support. Reproducible: Always Steps to Reproduce: (Assuming mcelog not currently running) 1. /usr/sbin/mcelog --daemon --foreground 2. Read message 3. Press ctrl C to exit mcelog Actual Results: mcelog: Unsupported new Family 6 Model 3c CPU: only decoding architectural errors or mcelog: Unsupported new Family 6 Model 3e CPU: only decoding architectural errors or mcelog: Unsupported new Family 6 Model 3a CPU: only decoding architectural errors Expected Results: No output at all (as is the case on older processors). One of those CPUs was a Xeon E3-1220 v3, launched June 2013, one a Xeon E5-1650 v2, launched Sept 2013, one a Xeon E3-1230 v2 launched May 2012. Suse 13.1 was released November 2013, so might be expected to support all of these. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 881259] New: If IPv6 is enabled/disabled - suggestion is to reboot. Not needed so it seems
by bugzilla_noreply＠novell.com 05 Jun '14

05 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881259 https://bugzilla.novell.com/show_bug.cgi?id=881259#c0 Summary: If IPv6 is enabled/disabled - suggestion is to reboot. Not needed so it seems Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: roeland(a)linux-it.nl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 while I was troubleshooting native IPv6 I had to enable/disable IPv6 a few times. yast2 network suggests that to pick up the enable/disable IPv6 a reboot is required. However, if I look at the ifconfig of the affected interface it is being applied and also works -- e.g. if I enable, IPv6 will work, and if disable it (obviously) does not work. It seems that the info box "reboot required" is not true anymore. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://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 881387] New: libdmtx - wrong handling of DmtxPropRowPadBytes
by bugzilla_noreply＠novell.com 05 Jun '14

05 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881387 https://bugzilla.novell.com/show_bug.cgi?id=881387#c0 Summary: libdmtx - wrong handling of DmtxPropRowPadBytes Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ch.ehrlicher(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=593361) --> (http://bugzilla.novell.com/attachment.cgi?id=593361) Patch to fix the issue User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 Setting DmtxPropRowPadBytes to something != 0 (in my case 4 to fulfill the QImage 32Bit alignment) results in a crash because the row padding is not handled correctly: img->rowSizeBytes = img->width * (img->bitsPerPixel/8) + img->rowPadBytes; the correct calculation is: img->rowSizeBytes = img->width * (img->bitsPerPixel/8); /* Align to next multiple of img->rowPadBytes */ if(img->rowPadBytes > 0) img->rowSizeBytes = (((img->rowSizeBytes + img->rowPadBytes - 1) / img->rowPadBytes ) * img->rowPadBytes); Due to the wrong caluclation a out-of-bounds access later on result in a crash. The attached patch fixes this issue. Since libdmtx is unmaintained I'm posting the patch here to get it at least into the openSUSE rpms Reproducible: Always Steps to Reproduce: 1. Create a dmtx Context with dmtxEncodeCreate 2. Set DmtxPropRowPadBytes to 4 with dmtxEncodeSetProp 3. Create a Datamatrix Image with dmtxEncodeDataMatrix -> Crash 4. Create a QImage from the resulting raw barcode image Actual Results: Crash / Corrupted Image Expected Results: No Crash -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 869366] New: virt-manager causes libvirtd to emit endless messages
by bugzilla_noreply＠novell.com 04 Jun '14

04 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=869366 https://bugzilla.novell.com/show_bug.cgi?id=869366#c0 Summary: virt-manager causes libvirtd to emit endless messages Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: carnold(a)suse.com ReportedBy: schwab(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- As soon as I start virt-manager, libvirtd spams syslog with endless messages. 2014-03-20T11:23:53.570596+01:00 hawking libvirtd[961]: Cannot create route - destination and gw are both 0/0 2014-03-20T11:23:53.570870+01:00 hawking libvirtd[961]: Cannot create route from netlink message: No such file or directory This happens several times per second. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 876346] New: Wake on LAN not working with 13.1 (but working with 12.1 on same machine)
by bugzilla_noreply＠novell.com 04 Jun '14

04 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=876346 https://bugzilla.novell.com/show_bug.cgi?id=876346#c0 Summary: Wake on LAN not working with 13.1 (but working with 12.1 on same machine) Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joschibrauchle(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 On a machine where Wake-on-LAN is enabled in BIOS, the machine a) does NOT wake up from standby or poweroff in openSUSE 13.1, BUT b) does wake up from standy with openSUSE 12.1 LiveCD. Poweroff was not tested. Diagnose for openSUSE 13.1: -------------------------------------------------------- Before standby: -------------------------------------------------------- # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes # ethtool -s eth0 wol g Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes # cat /proc/acpi/wakeup Device S-state Status Sysfs node PEXA S4 *disabled PEXX S4 *disabled PEXB S4 *disabled pci:0000:00:1c.0 PEXC S4 *disabled pci:0000:00:1c.4 PEXD S4 *disabled USB1 S3 *enabled pci:0000:00:1d.0 USB2 S3 *enabled pci:0000:00:1d.1 USB3 S3 *enabled pci:0000:00:1d.2 USB4 S3 *enabled pci:0000:00:1a.0 USB5 S3 *enabled pci:0000:00:1a.1 USB6 S3 *enabled pci:0000:00:1a.2 USB7 S3 *disabled USB8 S3 *enabled pci:0000:00:1d.7 USB9 S3 *enabled pci:0000:00:1a.7 LAN S4 *enabled pci:0000:00:19.0 PCIH S4 *disabled pci:0000:00:1e.0 KEYB S1 *enabled pnp:00:08 PS2M S1 *disabled pnp:00:09 # pm-suspend -------------------------------------------------------- Going to standby... WOL WAS NOT WORKING, machine did not powerup from standby. Resuming by pressing power button. After resume: -------------------------------------------------------- # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes # cat /proc/acpi/wakeup Device S-state Status Sysfs node PEXA S4 *disabled PEXX S4 *disabled PEXB S4 *disabled pci:0000:00:1c.0 PEXC S4 *disabled pci:0000:00:1c.4 PEXD S4 *disabled USB1 S3 *enabled pci:0000:00:1d.0 USB2 S3 *enabled pci:0000:00:1d.1 USB3 S3 *enabled pci:0000:00:1d.2 USB4 S3 *enabled pci:0000:00:1a.0 USB5 S3 *enabled pci:0000:00:1a.1 USB6 S3 *enabled pci:0000:00:1a.2 USB7 S3 *disabled USB8 S3 *enabled pci:0000:00:1d.7 USB9 S3 *enabled pci:0000:00:1a.7 LAN S4 *disabled pci:0000:00:19.0 PCIH S4 *disabled pci:0000:00:1e.0 KEYB S1 *enabled pnp:00:08 PS2M S1 *disabled pnp:00:09 -------------------------------------------------------- More details: # hwinfo --netcard 16: PCI 19.0: 0200 Ethernet controller [Created at pci.319] Unique ID: rBUF.hO2O_T8oBY8 SysFS ID: /devices/pci0000:00/0000:00:19.0 SysFS BusID: 0000:00:19.0 Hardware Class: network Model: "Intel 82566DM-2 Gigabit Network Connection" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x10bd "82566DM-2 Gigabit Network Connection" SubVendor: pci 0x1734 "Fujitsu Technology Solutions" SubDevice: pci 0x10fd Revision: 0x02 Driver: "e1000e" Driver Modules: "e1000e" Device File: eth0 Memory Range: 0xd0020000-0xd003ffff (rw,non-prefetchable) Memory Range: 0xd0007000-0xd0007fff (rw,non-prefetchable) I/O Ports: 0x1820-0x183f (rw) IRQ: 44 (2111 events) HW Address: 00:19:99:3b:07:5b Link detected: yes Module Alias: "pci:v00008086d000010BDsv00001734sd000010FDbc02sc00i00" Driver Info #0: Driver Status: e1000e is active Driver Activation Cmd: "modprobe e1000e" Config Status: cfg=no, avail=yes, need=no, active=unknown -------------------------------------------------------- One can see, the ethtool output AFTER resume shows that wake on lan is DISABLED on eth0. The machine does NOT wake up from a magic paket during standby in openSUSE 13.1 (but DOES wake up when using 12.1 live CD). Hence, at some point in time during going to standby, it looks like WOL is being disabled! Reproducible: Always Steps to Reproduce: 1. enable WOL using ethtool 2. go to standby 3. try to wake up machine with magic packet Actual Results: Machine does not wake up with 13.1, but does so in 12.1 Expected Results: Machine should wake up in 13.1 as in 12.1 -- Configure bugmail: https://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 881240] New: yast2 sw_single crashes randomly
by bugzilla_noreply＠novell.com 04 Jun '14

04 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881240 https://bugzilla.novell.com/show_bug.cgi?id=881240#c0 Summary: yast2 sw_single crashes randomly Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: vpelcak(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=593240) --> (http://bugzilla.novell.com/attachment.cgi?id=593240) y2 logs When trying to manage packages with yast (to remove obsolete packages for example), yast repeatedly and randomly crashes. y2logs in attachment. -- Configure bugmail: https://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 881182] New: Error while creating users. Installer said I should report as bug.
by bugzilla_noreply＠novell.com 04 Jun '14

04 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881182 https://bugzilla.novell.com/show_bug.cgi?id=881182#c0 Summary: Error while creating users. Installer said I should report as bug. Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: nrickert(a)ameritech.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 I was attempting to install using: openSUSE-FTT-DVD-x86_64-Snapshot20140602-Media.iso (downloaded from the openQA site). I had completed the partition section, and was in the section for defining users. I had clicked "Change", and checked the button to import users from prior installation. On the next screen, I had checked the box to import all three users. The next screen was an error popup. I hand-wrote the message: ----- Internal error. Please report a bug report with logs Details: Current textdomain (nil) was not added, use FastGettext.add_text_domain ! Caller: /usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.8.1/lib/fast_gettext/storage.rb:93:in `current repository ----- After I dismissed that message, the next screen showed (among other things): ----- Calling Yast module `inst_user_first has failed ----- Note that the unclose quote in the last line was part of what I saw. I will attach Yast logs. Note that I repeated this. The same error occurred both times. The Yast logs are from the second time. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2