November 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 840159] New: Should there be a entry in Yast | Services Manager for msql/mariadb.
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=840159 https://bugzilla.novell.com/show_bug.cgi?id=840159#c0 Summary: Should there be a entry in Yast | Services Manager for msql/mariadb. Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: doiggl(a)velocitynet.com.au QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=557641) --> (http://bugzilla.novell.com/attachment.cgi?id=557641) listed services in Yast | Services Manager User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20 Hello, Should there be a entry in Yast | Services Manager for msql/mariadb. So you can start|stop & enable|disable this service. Part of lamp service. Thanks Glenn Reproducible: Always Steps to Reproduce: 1. missing service entry for msql/mariadb Expected Results: service entry for msql/mariadb -- 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 11

[Bug 846321] New: MySQL (MariaDB) not showing in Services so it can be enabled/disabled
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=846321 https://bugzilla.novell.com/show_bug.cgi?id=846321#c0 Summary: MySQL (MariaDB) not showing in Services so it can be enabled/disabled Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jorgeh(a)fsbcomputers.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=563792) --> (http://bugzilla.novell.com/attachment.cgi?id=563792) Services Manager Window User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 MySQL (MariaDB) is not showing in the Services Manager, it is installed and it can be started using "systemctl start mysql", but it doesn't show in the list given by the Services Manager of YaST Reproducible: Always Steps to Reproduce: 1. Open YaST 2. Open Serivices Manager 3. look for MySQL Actual Results: Not in list Expected Results: To be in the list so it can be enabled at boot time. -- 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 675870] New: Cannot enable mysql service because it needs $network in run level 2
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=675870 https://bugzilla.novell.com/show_bug.cgi?id=675870#c0 Summary: Cannot enable mysql service because it needs $network in run level 2 Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: silviu_marin-caea(a)otpbank.ro QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 chkconfig --add mysql insserv: FATAL: service network is missed in the runlevels 2 to use service mysql insserv: exiting now! /sbin/insserv failed, exit code 1 mysql 0:off 1:off 2:off 3:off 4:off 5:off 6:off Reproducible: Always Steps to Reproduce: 1. chkconfig --add mysql 2. error 3. edit /etc/init.d/mysql 4. remove run level 2 from "Default-Start:" 5. chkconfig --add mysql 6. ok Actual Results: In default configuration, mysql cannot be enabled as a service to start at boot Expected Results: Should be able to enable mysql service -- 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 21

[Bug 837513] New: request-tracker package in devel:languages:perl has an issue (rt-mailgate)
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=837513 https://bugzilla.novell.com/show_bug.cgi?id=837513#c0 Summary: request-tracker package in devel:languages:perl has an issue (rt-mailgate) Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: lrupp(a)suse.com ReportedBy: ncutler(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Field Engineer Blocker: --- rt-mailgate is a critical component of Request Tracker (package 'request-tracker' in project 'devel:languages:perl') As it currently stands, in openSUSE or SLE11-SP2 I can get rt-mailgate to communicate with the server using SSL encryption (https) *only* if I explicitly provide the --ca-file option to rt-mailgate. Even this is a bug; rt-mailgate should be able to find the Trust Root certificate itself. Still, at least it worked. Today I upgraded our RT server to SLE11-SP3, and rt-mailgate stopped working over SSL completely. The MTA passes the email to rt-mailgate, but rt-mailgate does nothing and eventually times out. I can reproduce the bug (on SLE11-SP3) by issuing the following command: # echo "hello" | /usr/bin/rt-mailgate --debug --queue General --action correspond --ca-file /etc/ssl/certs/Trust-Root.crt.pem --url https://our.rt.instance This generates the following output: /usr/bin/rt-mailgate: temp file is '/tmp/OOT6t4Rcoi/TsM08ZYrQV' /usr/bin/rt-mailgate: connecting to https://our.rt.instance/REST/1.0/NoAuth/mail-gateway Nothing further happens. I have worked around the issue by having rt-mailgate communicate without SSL (http). This works fine: # echo "hello" |/usr/bin/rt-mailgate --debug --queue rt_internal --action comment --url http://our.rt.instance /usr/bin/rt-mailgate: temp file is '/tmp/cdJXHiPXWr/IgReSdTbFr' /usr/bin/rt-mailgate: connecting to http://our.rt.instance/REST/1.0/NoAuth/mail-gateway not ok - Could not load a valid user # Or, if I provide a valid email: # cat testmail |/usr/bin/rt-mailgate --debug --queue rt_internal --action comment --url http://our.rt.instance /usr/bin/rt-mailgate: temp file is '/tmp/JxvCRVKXAJ/x3uMMQP32D' /usr/bin/rt-mailgate: connecting to http://our.rt.instance/REST/1.0/NoAuth/mail-gateway okTicket: 35348Queue: GeneralOwner: NobodyStatus: newSubject: testRequestor: me(a)some.domain # and of course the ticket is created as expected and I can see it in the RT web UI. -- 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 9

[Bug 849084] New: yast2 sw_single: confusing dialog when canceling
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=849084 https://bugzilla.novell.com/show_bug.cgi?id=849084#c0 Summary: yast2 sw_single: confusing dialog when canceling Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: lslezak(a)suse.com ReportedBy: suse-beta(a)cboltz.de QAContact: jsrain(a)suse.com Found By: Beta-Customer Blocker: --- yast2 sw_single displays a confusing dialog when clicking the "cancel" button: Abandon all changes? [Abandon] [Cancel] Keep in mind that you clicked "cancel" before, you want to cancel sw_single, and now of course have to click [Cancel]. NOT. This is confusing. A better dialog would be Abandom all changes? [Yes] [No] For bonus points, use a full sentence/question: Do you want to abandom all changes? [Yes] [No] -- 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 679128] New: opensuse 11.4 virtualbox ose 4.0.4.-1.2.3 extremely slow, IO & processing
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=679128 https://bugzilla.novell.com/show_bug.cgi?id=679128#c0 Summary: opensuse 11.4 virtualbox ose 4.0.4.-1.2.3 extremely slow, IO & processing Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rens.groenewegen(a)xs4all.nl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b11) Gecko/20110203 Firefox/4.0b11 windows 7 64 and windows xp 32 and fedora are extremely slow in booting, sluggish performance; It looks like any IO is so slow that GUI performance is ok but halted whenever a few kbytes are needed. when loading OS, IO does not exceed 1 mbyte per second...... Reproducible: Always Steps to Reproduce: 1.install and see for yourself. 2. 3. Actual Results: load any OS in virtualbox and experience the slow performance Expected Results: should have worked as always, good performance and responsive interaction. workaround: install Oracle VM virtualbox 4.0.0 r69151 for suse x86_64 11.3 on opensuse 11.4 and all your problems are gone...... the client virtualbox software inside the OS is still on 4.0.4, so that is apparently not the issue. cheers RG -- 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 23

[Bug 809789] New: ACPI problems (CPU Fan, AC events) on Toshiba Tecra R840-14X after 12.3 update from 12.2
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=809789 https://bugzilla.novell.com/show_bug.cgi?id=809789#c0 Summary: ACPI problems (CPU Fan, AC events) on Toshiba Tecra R840-14X after 12.3 update from 12.2 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: hcderaad(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=530043) --> (http://bugzilla.novell.com/attachment.cgi?id=530043) hwinfo output User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.32 (KHTML, like Gecko) Chrome/27.0.1425.0 Safari/537.32 SUSE/27.0.1425.0 On an updated install (from 12.2) the CPU Fan keeps running at full speed and also ac actions are not noticed (ac plugged in/out, battery levels are incorrect). ACPI messages show the following: i [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.7.10-7-desktop root=UUID=ee6616ed-bf20-4008-8ad4-2fc09091c959 resume=/dev/disk/by-id/ata-Hitachi_HTS725050A9A360_110507PCJ400GLHKL9BJ-part5 splash=silent quiet showopts acpi_osi=Linux [ 0.000000] BIOS-e820: [mem 0x00000000aa5d0000-0x00000000aa5d01ff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000aa5d3000-0x00000000aa6cffff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000aa6d0000-0x00000000aa6effff] ACPI data [ 0.000000] ACPI: RSDP 00000000000f0030 00014 (v00 TOSHIB) [ 0.000000] ACPI: RSDT 00000000aa6ef038 00058 (v01 TOSHIB A007D 00000004 01000013) [ 0.000000] ACPI: FACP 00000000aa6ee000 00081 (v02 TOSHIB A007D 00000004 LOHR 0000005F) [ 0.000000] ACPI: DSDT 00000000aa6dd000 08A46 (v02 TOSHIB A007D 20111220 INTL 20061109) [ 0.000000] ACPI: FACS 00000000aa6ad000 00040 [ 0.000000] ACPI: HPET 00000000aa6ed000 00038 (v01 TOSHIB A007D 00000001 LOHR 0000005F) [ 0.000000] ACPI: APIC 00000000aa6ec000 000BC (v01 TOSHIB A007D 00000001 LOHR 0000005F) [ 0.000000] ACPI: MCFG 00000000aa6eb000 0003C (v01 TOSHIB A007D 00000001 LOHR 0000005F) [ 0.000000] ACPI: ASF! 00000000aa6ea000 000A0 (v32 TOSHIB A007D 00000001 LOHR 0000005F) [ 0.000000] ACPI: TCPA 00000000aa6e9000 00032 (v02 TOSHIB A007D 00000000 LOHR 0000005F) [ 0.000000] ACPI: BOOT 00000000aa6e8000 00028 (v01 TOSHIB A007D 00000000 LOHR 0000005F) [ 0.000000] ACPI: SLIC 00000000aa6e7000 00176 (v01 TOSHIB A007D 00000000 LOHR 0000005F) [ 0.000000] ACPI: SSDT 00000000aa6dc000 00395 (v01 TOSHIB SataAhci 00001000 INTL 20061109) [ 0.000000] ACPI: SSDT 00000000aa6d9000 00720 (v01 TOSHIB PtidDevc 00001000 INTL 20061109) [ 0.000000] ACPI: SSDT 00000000aa6d7000 007E5 (v01 PmRef Cpu0Ist 00003000 INTL 20061109) [ 0.000000] ACPI: SSDT 00000000aa6d6000 00996 (v01 PmRef CpuPm 00003000 INTL 20061109) [ 0.000000] ACPI: DMAR 00000000aa6d5000 00110 (v01 INTEL SNB 00000001 INTL 00000001) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x00] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x00] disabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ2 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.7.10-7-desktop root=UUID=ee6616ed-bf20-4008-8ad4-2fc09091c959 resume=/dev/disk/by-id/ata-Hitachi_HTS725050A9A360_110507PCJ400GLHKL9BJ-part5 splash=silent quiet showopts acpi_osi=Linux [ 0.004081] ACPI: Core revision 20120913 [ 0.178902] PM: Registering ACPI NVS region [mem 0xaa5d0000-0xaa5d01ff] (512 bytes) [ 0.178904] PM: Registering ACPI NVS region [mem 0xaa5d3000-0xaa6cffff] (1036288 bytes) [ 0.179189] ACPI: bus type pci registered [ 0.185976] ACPI: Added _OSI(Module Device) [ 0.185978] ACPI: Added _OSI(Processor Device) [ 0.185979] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.185980] ACPI: Added _OSI(Processor Aggregator Device) [ 0.185981] ACPI: Added _OSI(Linux) [ 0.187392] ACPI: EC: Look up EC in DSDT [ 0.192829] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query honored via cmdline [ 0.194030] ACPI: SSDT 00000000aafd6798 0071E (v01 PmRef Cpu0Cst 00003001 INTL 20061109) [ 0.194398] ACPI: Dynamic OEM Table Load: [ 0.194400] ACPI: SSDT (null) 0071E (v01 PmRef Cpu0Cst 00003001 INTL 20061109) [ 0.194823] ACPI: SSDT 00000000aafd7a98 00303 (v01 PmRef ApIst 00003000 INTL 20061109) [ 0.195234] ACPI: Dynamic OEM Table Load: [ 0.195236] ACPI: SSDT (null) 00303 (v01 PmRef ApIst 00003000 INTL 20061109) [ 0.200886] ACPI: SSDT 00000000aafd5d98 00119 (v01 PmRef ApCst 00003000 INTL 20061109) [ 0.201249] ACPI: Dynamic OEM Table Load: [ 0.201250] ACPI: SSDT (null) 00119 (v01 PmRef ApCst 00003000 INTL 20061109) [ 0.201877] ACPI: Interpreter enabled [ 0.201880] ACPI: (supports S0 S3 S4 S5) [ 0.201899] ACPI: Using IOAPIC for interrupt routing [ 0.206873] ACPI: ACPI Dock Station Driver: 1 docks/bays found [ 0.206877] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.207120] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f]) [ 0.216916] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 0.217092] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT] [ 0.217133] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT] [ 0.217171] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT] [ 0.217211] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT] [ 0.217254] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT] [ 0.217294] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP07._PRT] [ 0.217352] pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM [ 0.221285] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11 [ 0.221333] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 11 12 14 15) [ 0.221377] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11 [ 0.221421] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 *3 4 5 6 7 11 12 14 15) [ 0.221467] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 *10 12 14 15) [ 0.221511] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled. [ 0.221555] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 *6 7 10 12 14 15) [ 0.221598] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15) [ 0.221750] ACPI: bus type scsi registered [ 0.221797] ACPI: bus type usb registered [ 0.221886] PCI: Using ACPI for IRQ routing [ 0.227790] pnp: PnP ACPI init [ 0.227800] ACPI: bus type pnp registered [ 0.228130] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active) [ 0.228310] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.228572] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active) [ 0.228631] pnp 00:03: Plug and Play ACPI device, IDs IFX0102 PNP0c31 (active) [ 0.228730] system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active) [ 0.228769] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active) [ 0.228831] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.228873] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.228904] pnp 00:08: Plug and Play ACPI device, IDs PNP0b00 (active) [ 0.228938] pnp 00:09: Plug and Play ACPI device, IDs PNP0303 (active) [ 0.228965] pnp 00:0a: Plug and Play ACPI device, IDs PNP0f13 (active) [ 0.229036] system 00:0b: Plug and Play ACPI device, IDs PNP0c01 (active) [ 0.229157] pnp: PnP ACPI: found 12 devices [ 0.229158] ACPI: ACPI bus type pnp unregistered [ 1.051240] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 1.051248] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff880243491678), AE_NOT_FOUND (20120913/psparse-536) [ 1.051312] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 1.051315] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff880243491650), AE_NOT_FOUND (20120913/psparse-536) [ 1.052886] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 1.052891] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff880243491678), AE_NOT_FOUND (20120913/psparse-536) [ 1.052948] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359) [ 1.052951] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff880243491650), AE_NOT_FOUND (20120913/psparse-536) [ 1.053904] ACPI: Invalid Power Resource to register! [ 1.382363] ACPI: Invalid Power Resource to register!<6>[ 1.389260] usb 2-1: New USB device found, idVendor=8087, idProduct=0024 [ 1.855408] acpi LNXSYBUS:01: hash matches [ 1.855411] acpi TOS6208:00: hash matches [ 1.899515] ACPI: Requesting acpi_cpufreq [ 1.902310] ACPI: Power Button [PWRB] [ 1.902656] ACPI: Thermal Zone [TZ01] (16 C) [ 1.902718] ACPI: Lid Switch [LID] [ 1.903851] ACPI: Power Button [PWRF] [ 3.402480] acpi device:04: registered as cooling_device4 [ 3.402646] ACPI: Video Device [GFX0] (multi-head: yes rom: yes post: no) [ 11.296334] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared [ 11.296388] ACPI: AC Adapter [ADP1] (on-line) [ 11.297490] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared [ 11.297495] ACPI: Battery Slot [BAT1] (battery present) [ 11.649429] toshiba_bluetooth: Detected Toshiba ACPI Bluetooth device - installing RFKill handler [ 12.397823] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19 [ 12.717314] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20120913/utaddress-251) [ 12.717321] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.717325] ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251) [ 12.717330] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.717332] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251) [ 12.717336] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.717338] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251) [ 12.717342] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver These look similar to bug 808876, 807996, 804197 Reproducible: Always Steps to Reproduce: 1. Boot the laptop 2. Wait for the login screen, wait for ~ 10 seconds 3. Fan starts running at full speed 4. Login, disconnect power, battery indicator (KDE 4) still shows plugged in AC Expected Results: The fan should resume normal operation (dynamic), AC events should be registered. -- 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 13

[Bug 849024] New: Dark desktop theme but light grey KDE windows.
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=849024 https://bugzilla.novell.com/show_bug.cgi?id=849024#c0 Summary: Dark desktop theme but light grey KDE windows. Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: Other OS/Version: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: fricker(a)bk.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Grey windows looks like aliens in the pretty dark with green theme. Also if use custom dark theme Yast will keep grey colour. Any chance fix that ? Reproducible: Always Steps to Reproduce: 1. Just have a look on default windows 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 843718] kiwi: missing patch: use kpartx sync mode to make sure devices are created
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=843718 https://bugzilla.novell.com/show_bug.cgi?id=843718#c13 --- Comment #13 from Adrian Schröter <adrian(a)suse.com> 2013-11-05 17:24:09 UTC --- One thing, what you could test is to build within KVM using osc on a current openSUSE to rule out that the kernel is guilty. But in the end you will need to create a test case for this, I think. maybe just dump out the failing command with strace and list the device directory before and after the "udevadm settle" call, which seems to work. -- 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 0

[Bug 803505] New: named seems to be started before eth0 is up
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=803505 https://bugzilla.novell.com/show_bug.cgi?id=803505#c0 Summary: named seems to be started before eth0 is up Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bha(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.11) Gecko/20121123 Firefox/10.0.11 Iceape/2.7.11 chkconfig named is on. After reboot, named is not listening externally. Feb 13 08:33:27 PortableWS-06 named[1388]: using default UDP/IPv4 port range: [1024, 65535] Feb 13 08:33:27 PortableWS-06 named[1388]: using default UDP/IPv6 port range: [1024, 65535] Feb 13 08:33:27 PortableWS-06 named[1388]: listening on IPv6 interfaces, port 53 Feb 13 08:33:27 PortableWS-06 named[1388]: listening on IPv4 interface lo, 127.0.0.1#53 Feb 13 08:33:27 PortableWS-06 named[1388]: generating session key for dynamic DNS When I do 'rcnamed restart' later, named works better and is also reachable from outside. Feb 13 09:21:41 PortableWS-06 named[2688]: using default UDP/IPv4 port range: [1024, 65535] Feb 13 09:21:41 PortableWS-06 named[2688]: using default UDP/IPv6 port range: [1024, 65535] Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv6 interfaces, port 53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface lo, 127.0.0.1#53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface eth0, 10.128.100.6#53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface eth0:bha, 10.200.48.66#53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface eth0:ntp1, 10.128.89.101#53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface eth0:ntp2, 10.128.89.102#53 Feb 13 09:21:41 PortableWS-06 named[2688]: generating session key for dynamic DNS Reproducible: Always Steps to Reproduce: 1a. Build a small openSuse 12.2 Appliance containing package bind and static IP-config using susestudio.com or Kiwi 1b. or Install Package bind on openSuse 12.2 with static IP-address 2. do chkconfig named on 3. reboot 4. check /var/log/messages 5. do rcnamed restart 6. check /var/log/messages Actual Results: named is not listening on external IPv4 interfaces. Feb 13 08:33:27 PortableWS-06 named[1388]: listening on IPv6 interfaces, port 53 Feb 13 08:33:27 PortableWS-06 named[1388]: listening on IPv4 interface lo, 127.0.0.1#53 Feb 13 08:33:27 PortableWS-06 named[1388]: generating session key for dynamic DNS Expected Results: Listen also on eth0 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv6 interfaces, port 53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface lo, 127.0.0.1#53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface eth0, 10.128.100.6#53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface eth0:bha, 10.200.48.66#53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface eth0:ntp1, 10.128.89.101#53 Feb 13 09:21:41 PortableWS-06 named[2688]: listening on IPv4 interface eth0:ntp2, 10.128.89.102#53 Feb 13 09:21:41 PortableWS-06 named[2688]: generating session key for dynamic DNS My System is a small suse Studio Appliance Preload ISO Image installed with statich IP configuration on a HP Notebook. With autostart- apache2, atftpd, names and a manual-start dhcpd -- 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 7