August 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 586555] New: lxde dumps messages to console
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586555 http://bugzilla.novell.com/show_bug.cgi?id=586555#c0 Summary: lxde dumps messages to console Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXDE AssignedTo: andrea(a)opensuse.org ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- the error messages from the X session are dumped to the console (/dev/tty1) when lxdm is used. lxdm should detach from the console and session messages should go to ~/.xsession-errors. looks like /etc/X11/xdm/Xsession is not executed -- 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 13

[Bug 586486] New: Multiple Issues with Yast Configuration of Postfix MTA for Relaying over SMTP
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586486 http://bugzilla.novell.com/show_bug.cgi?id=586486#c0 Summary: Multiple Issues with Yast Configuration of Postfix MTA for Relaying over SMTP Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andrew(a)acooke.org QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 The Yast configuration of Postfix as MTA, using the standard (not advanced) mode, for delivering mail over SMTP to a relay, has a number of issues. 1 - When using TLS authentication (SASL) the host address is not surrounded with [] as recommended here - http://www.postfix.org/SASL_README.html (see section titled "Enabling SASL authentication in the Postfix SMTP/LMTP client"). This is necessary because often the same name (mail.example.com or smtp.example.com) is used both as a relay and to handle incoming mail. Only the relay needs authentication, and so is given one physical machine, while other physical machines handle the main mail volume. In such a case, MX records point to the "other" machines, and [] is necessary to use the "real" machine (which is the only one with autentication). For a concrete example of the pain this causes please see http://forum.webfaction.com/viewtopic.php?pid=15066 2 - When the config is changed in Yast (eg the SMT server name changed), the changes appear in /etc/systconfig/postfix and sasl_passwd, but not in main.cnf. 3 - When the config is changed in Yast (eg the SMT auth details changed), the sasl_passwd.db file is not regenerated with "postmap sasl_passwd". Reproducible: Always Steps to Reproduce: 1. Use Yast to configure SMTP 2. See it fail to work in the case described above, where MX names are used instead of the exact, given host. 3. Change details 4. See how the updated details are not used in subsequent connections. -- 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 16

[Bug 586376] New: network settings: "activate device" event -- add option for exclusive activation
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586376 http://bugzilla.novell.com/show_bug.cgi?id=586376#c0 Summary: network settings: "activate device" event -- add option for exclusive activation Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Yast -> network devices -> network settings -> interface -> activate device Currently there are several options, like on boot, on cable connection, manual, etc. Let's focus on cable connection -- when cable is connected that device is activated. That is what this option says. But what this option _does not_ say is this activation is exclusive, i.e. it will shutdown all other active interfaces. I am not discussing if such implicit, additional action is useful or not (for me not), but anyway, if there is an _extra_ action, there should be an _extra_ option. Namely: [ ] exclusive activation that way user could set/control if she/he really wants exclusive connection over only one interface. This way also it would be finally possible to use "on cable connection" settings with multiple interfaces/connections (currently it is not possible and user has to set it up manually with ifup). -- 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 586172] New: sysfs: cannot create duplicate filename '/bus/ieee1394/drivers/sbp2...
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586172 http://bugzilla.novell.com/show_bug.cgi?id=586172#c0 Summary: sysfs: cannot create duplicate filename '/bus/ieee1394/drivers/sbp2... Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jpschewe(a)mtu.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I have a Western Digital MyBook attached via Firewire to my desktop. With the latest 11.2 kernel I'm receiving this error on every boot. The drive works fine, but the warning is concerning. <6>[ 13.564098] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:10.1/input/input5 <7>[ 13.761068] ieee1394: Node added: ID:BUS[0-00:1023] GUID[0090a976213be423] <7>[ 13.761150] ieee1394: Host added: ID:BUS[0-01:1023] GUID[0010dc0000cf92b6] <6>[ 13.930522] scsi6 : SBP-2 IEEE-1394 <6>[ 18.409456] ieee1394: sbp2: Logged into SBP-2 device <6>[ 18.439171] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [1024] <5>[ 18.569852] scsi 6:0:0:0: Direct-Access WD My Book 1025 PQ: 0 ANSI: 4 <5>[ 18.586911] sd 6:0:0:0: Attached scsi generic sg2 type 0 <6>[ 18.605107] scsi7 : SBP-2 IEEE-1394 <5>[ 18.643641] sd 6:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB) <5>[ 18.691159] sd 6:0:0:0: [sdb] Write Protect is off <7>[ 18.707856] sd 6:0:0:0: [sdb] Mode Sense: 10 00 00 00 <5>[ 18.723828] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 18.740441] sd 6:0:0:0: [sdb] Assuming drive cache: write through <5>[ 18.841637] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 18.858351] sd 6:0:0:0: [sdb] Assuming drive cache: write through <6>[ 18.875218] sdb: sdb1 <5>[ 19.509210] sd 6:0:0:0: [sdb] Cache data unavailable <3>[ 19.526010] sd 6:0:0:0: [sdb] Assuming drive cache: write through <5>[ 19.542626] sd 6:0:0:0: [sdb] Attached SCSI disk <6>[ 22.908499] ieee1394: sbp2: Logged into SBP-2 device <6>[ 22.938881] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [1024] <5>[ 23.074794] scsi 7:0:1:0: Enclosure WD My Book Device PQ: 0 ANSI: 4 <5>[ 23.091848] scsi 7:0:1:0: Attached scsi generic sg3 type 13 <5>[ 23.108446] ses 7:0:1:0: Attached Enclosure device <4>[ 23.126186] ------------[ cut here ]------------ <4>[ 23.142608] WARNING: at /usr/src/packages/BUILD/kernel-default-2.6.31.12/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xde/0x150() <4>[ 23.159767] Hardware name: MS-7207PV <4>[ 23.176784] sysfs: cannot create duplicate filename '/bus/ieee1394/drivers/sbp2/0090a976213be423-1' <4>[ 23.194258] Modules linked in: ses enclosure sbp2 snd_hda_codec_realtek ppdev pcspkr ohci1394 floppy ieee1394 parport_pc parport sr_mod sg cdrom snd_hda_intel snd_hda_codec snd_hwdep snd_pcm button snd_timer amd64_edac_mod forcedeth edac_core k8temp snd snd_page_alloc nvidia(P) i2c_nforce2 preloadtrace linear raid456 raid6_pq async_xor async_memcpy async_tx xor raid0 dm_snapshot dm_mirror dm_region_hash dm_log reiserfs aic7xxx scsi_transport_spi edd dm_mod raid1 fan ide_pci_generic amd74xx ide_core ata_generic sata_nv pata_amd thermal processor thermal_sys <4>[ 23.268356] Pid: 624, comm: knodemgrd_0 Tainted: P 2.6.31.12-0.1-default #1 <4>[ 23.287049] Call Trace: <4>[ 23.305454] [<ffffffff81011749>] try_stack_unwind+0x189/0x1b0 <4>[ 23.324009] [<ffffffff8101013d>] dump_trace+0x9d/0x330 <4>[ 23.342316] [<ffffffff81011254>] show_trace_log_lvl+0x64/0x90 <4>[ 23.360635] [<ffffffff810112a3>] show_trace+0x23/0x40 <4>[ 23.378712] [<ffffffff81555268>] dump_stack+0x81/0x9e <4>[ 23.378719] [<ffffffff8106db80>] warn_slowpath_common+0x80/0xd0 <4>[ 23.378724] [<ffffffff8106dc5b>] warn_slowpath_fmt+0x4b/0x70 <4>[ 23.378730] [<ffffffff811d6f3e>] sysfs_add_one+0xde/0x150 <4>[ 23.378735] [<ffffffff811d756b>] sysfs_do_create_link+0x14b/0x1a0 <4>[ 23.378740] [<ffffffff811d7621>] sysfs_create_link+0x21/0x40 <4>[ 23.378746] [<ffffffff8135fac8>] driver_sysfs_add+0x38/0xa0 <4>[ 23.378751] [<ffffffff81360050>] device_bind_driver+0x20/0x50 <4>[ 23.378756] [<ffffffff813600cb>] device_attach+0x4b/0xc0 <4>[ 23.378761] [<ffffffff8135e1c1>] bus_rescan_devices_helper+0x61/0x90 <4>[ 23.378766] [<ffffffff8135ed68>] bus_for_each_dev+0x78/0xc0 <4>[ 23.378771] [<ffffffff8135edd7>] bus_rescan_devices+0x27/0x50 <4>[ 23.378787] [<ffffffffa0c575a2>] nodemgr_host_thread+0x272/0x330 [ieee1394] <4>[ 23.378808] [<ffffffff8108ea66>] kthread+0xb6/0xc0 <4>[ 23.378814] [<ffffffff8100d70a>] child_rip+0xa/0x20 <4>[ 23.378819] ---[ end trace 02b373f7d663109a ]--- 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 30

[Bug 586083] New: obs://build.opensuse.org/multimedia/rosegarden4-10.02-29.3.x86_64 sigsegv in Rosegarden::HeadersGroup::slotSetCurrentSegment
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586083 http://bugzilla.novell.com/show_bug.cgi?id=586083#c0 Summary: obs://build.opensuse.org/multimedia/rosegarden4-10.02- 29.3.x86_64 sigsegv in Rosegarden::HeadersGroup::slotSetCurrentSegment Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: davejplater(a)gmail.com ReportedBy: m.munnix(a)redcross.be QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=346966) --> (http://bugzilla.novell.com/attachment.cgi?id=346966) stdout + bt full I had done a lot of editing in notation editor, clicked on save. Back to main window without closing notation editor, select the split track tool, then clicked on a track at the desired split point. Got the segfault Attaching output + full backtrace -- 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 16

[Bug 586070] New: Missing period in sentence.
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=586070 http://bugzilla.novell.com/show_bug.cgi?id=586070#c0 Summary: Missing period in sentence. Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: isis.binder(a)gmail.com QAContact: ke(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.9.2) Gecko/20100115 Firefox/3.6 File: apparmor-parser.po Line: 90 #: ../parser_interface.c:81 msgid "Couldn't copy profile Bad memory address\n" 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 3

[Bug 585802] New: wpa_supplicant needs nl80211 driver for country=DE (WIRELESS_REGULATORY_DOMAIN)
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=585802 http://bugzilla.novell.com/show_bug.cgi?id=585802#c0 Summary: wpa_supplicant needs nl80211 driver for country=DE (WIRELESS_REGULATORY_DOMAIN) Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: mt(a)novell.com ReportedBy: mt(a)novell.com QAContact: qa(a)suse.de CC: radmanic(a)novell.com, coolo(a)novell.com, ro(a)novell.com, mzugec(a)novell.com, jmatejek(a)novell.com Depends on: 555850 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #537708 +++ Until openSUSE:11.2, we were using the "wext" wpa driver by default. For openSUSE:11.3 it would be required to switch as many drivers as possible to the new "nl80211" driver to not to restricts any devices to "world" (ie. most restrictive) regulatory domain. As already proposed in bug 537708 comment 6, it makes sense to use the new driver as default, except in cases where it does not work. The intention of this bug is to track these non-working cases. See also bug 535750 comment 7: "[...] If the wpa_supplicant is running with the -Dnl80211 then it does not authenticate. -Dwext works fine.[...]" See also bug 555850, crda -- Database signature verification failed. -- 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 20

[Bug 585679] New: "Package Manager" -> "Software Manager"
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=585679 http://bugzilla.novell.com/show_bug.cgi?id=585679#c0 Summary: "Package Manager" -> "Software Manager" Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rpmcruz(a)alunos.dcc.fc.up.pt QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-PT; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 It was decided a while back to use the term "Software Manager" rather than "Package Manager" (or "Package Selector"). Please change the two "Initialize Package Manager" strings over webpin_package_search.ycp Reproducible: Always -- 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 6

[Bug 585433] New: NetworkManager 0.8 no longer connects after machine crashed during suspend
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=585433 http://bugzilla.novell.com/show_bug.cgi?id=585433#c0 Summary: NetworkManager 0.8 no longer connects after machine crashed during suspend Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: tambet(a)novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa(a)suse.de CC: hmacht(a)novell.com, vbotka(a)novell.com, rjw(a)novell.com Found By: Community User Blocker: --- If a machine crashes during a suspend to disk/ram, after next boot NetworkManager 0.8 will no longer connect to any network (wired or wireless), the applet will always show "networking system disabled". I tracked it down to the fact, that NM since 0.8 apparently remembers the "suspended" setting over a restart / reboot. During suspend, pm-utils calls dbus-send --system \ --print-reply --reply-timeout=200 \ --dest=org.freedesktop.NetworkManager \ /org/freedesktop/NetworkManager \ org.freedesktop.NetworkManager.sleep During resume, it wakes up NM by calling dbus_send --system \ --dest=org.freedesktop.NetworkManager \ --print-reply --reply-timeout=200 \ /org/freedesktop/NetworkManager \ org.freedesktop.NetworkManager.wake If the machine crashes during suspend, the .wake is not called and NM remains suspended forever. No matter if it those pm-utils calls are stupid or not, IMHO NetworkManager should not remember this setting via a restart or even a reboot of the machine. (adding people to CC who will probably have to deal with fallout from this bug, because it might get attributed to suspend or wireless). -- 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 63

[Bug 585432] New: Milestone 3 Gnome does not boot after Install
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=585432 http://bugzilla.novell.com/show_bug.cgi?id=585432#c0 Summary: Milestone 3 Gnome does not boot after Install Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: usrox(a)hotmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 5.1; U; de) Presto/2.5.22 Version/10.50 I boot the LiveCD and start openSuse. After successful installation from the Live Installer I reboot the System. After chosing "OpenSuse" it wants to boot up the operating System but eventually hangs up on a black screen. The last message I see when booting up is: "Starting HAL Deamon..." then the display changes and goes black. After that nothing works anymore. No Mouse and Keyboard Input react. I can only switch off and on the Computer. "Failsafe" Mode does not work either. This issue is the same as in Milestone 2. Reproducible: Always Steps to Reproduce: 1.Boot up into openSuse Live 2.Install from LiveCD Installer 3.Reboot Computer Actual Results: Black Screen Expected Results: Boot into installed version of openSuse. Hardware: Notebook Samsung R522 with Core 2 Duo T6400 4 GB Ram Ati Mobility 4650 -- 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 20