https://bugzilla.novell.com/show_bug.cgi?id=235059
Summary: /etc/resmgr.conf.d/99-avrdude_parport.conf is out of
date
Product: openSUSE 10.3
Version: unspecified
Platform: i686
OS/Version: SuSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
AssignedTo: sndirsch(a)novell.com
ReportedBy: rschiele(a)gmail.com
QAContact: qa(a)suse.de
/etc/resmgr.conf.d/99-avrdude_parport.conf is out of date and only produces log
messages like:
Jan 14 20:28:55 sighup resmgr[13786]:
/etc/resmgr.conf.d/99-avrdude_parport.conf:1: command 'add' no longer supported
Jan 14 20:28:55 sighup resmgr[13786]:
/etc/resmgr.conf.d/99-avrdude_parport.conf:2: command 'add' no longer supported
Jan 14 20:28:55 sighup resmgr[13786]:
/etc/resmgr.conf.d/99-avrdude_parport.conf:3: command 'add' no longer supported
Jan 14 20:28:55 sighup resmgr[13786]:
/etc/resmgr.conf.d/99-avrdude_parport.conf:4: command 'add' no longer supported
Jan 14 20:28:55 sighup resmgr[13786]:
/etc/resmgr.conf.d/99-avrdude_parport.conf:5: command 'add' no longer supported
Jan 14 20:28:55 sighup resmgr[13786]:
/etc/resmgr.conf.d/99-avrdude_parport.conf:6: command 'add' no longer supported
Jan 14 20:28:55 sighup resmgr[13786]:
/etc/resmgr.conf.d/99-avrdude_parport.conf:7: command 'add' no longer supported
Jan 14 20:28:55 sighup resmgr[13786]:
/etc/resmgr.conf.d/99-avrdude_parport.conf:8: command 'add' no longer supported
--
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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=234531
Summary: gigaset-frontend package not included
Product: openSUSE 10.2
Version: Final
Platform: All
OS/Version: SuSE Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: tilman(a)imap.cc
QAContact: qa(a)suse.de
Kernel 2.6.18 includes ISDN drivers for Siemens Gigaset SX255 family devices
connected via USB.
A package containing useful utilities for use with these devices is available
from
http://sourceforge.net/projects/gigaset307x/.
I would like to suggest including this package in future openSUSE releases.
--
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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230217
Summary: kbabel does not allow skim to input Chinese chars
Product: openSUSE 10.2
Version: Final
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: gubotruth(a)gmail.com
QAContact: qa(a)suse.de
CC: zsu(a)novell.com
openSUSE 10.2 x86_64, KDE environment, all packages from the DVD.
With scim/skim ok in all other K apps, Kbabel does not allow skim to input
Chinese chars in its msgstr field. With Eng keyboard on, everything's good.
However, with a Chinese IM on, it seems that every time I press a key, an IMEnd
signal is sent. For instance, with pinyin on, I press "wo" in order to form a
char query, it strangely runs into this way(from shell):
sending IMStart with 0 chars to 0x9fdce0
sending IMCompose to 0x9fdce0 with 1 chars, cpos=0, sellen=1, text=我
sending IMCompose to 0x9fdce0 with 1 chars, cpos=1, sellen=0, text=我
sending IMEnd with 0 chars to 0x9fdce0, text=
sending IMStart with 0 chars to 0x9fdce0
sending IMCompose to 0x9fdce0 with 1 chars, cpos=0, sellen=1, text=哦
sending IMCompose to 0x9fdce0 with 1 chars, cpos=1, sellen=0, text=哦
sending IMEnd with 0 chars to 0x9fdce0, text=
And there will be no char to be display in Kbabel.
This bug has been there since SUSE 10.1, also existing in SLE 10 series.
--
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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206464
Summary: openal cannot load ogg files
Product: SUSE Linux 10.1
Version: Final
Platform: Other
OS/Version: SuSE Linux 10.1
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Sound
AssignedTo: tiwai(a)novell.com
ReportedBy: opensuse(a)arvin.schnell-web.net
QAContact: qa(a)suse.de
The OpenAL library is missing the extension to load ogg files.
Reproduce by running the testprogram /usr/lib/openal/testvorbis.
tcsh: /usr/lib/openal/testvorbis
Could not GetProc alutLoadVorbis_LOKI
Worked in SUSE Linux 9.2.
--
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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=211235
Summary: Bad postscript creation from kprinter concludes in ugly
pdf
Product: SUSE Linux 10.1
Version: Final
Platform: i686
OS/Version: SuSE Linux 10.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: geroxp(a)web.de
QAContact: kde-maintainers(a)suse.de
Steps to reproduce:
1. Open Konqueror
2. Go to http://www.cnn.com
3. Print the page with kde's pdf printer (which is nothing else but ps2pdf, I
think)
4. Watch the pdf either with kpdf (which is default viewer) or with acroread
and you will see the jumping letters
The problem only occurs, when using kprinter to print the pdf OR generate a
postscript-file which will be used to create a pdf. It could have something to
do with kprinter itself or with GNU enscript (which is used by kprinter).
When using Mozilla-Firefox to print to a cups-pdf printer
(http://www.novell.com/coolsolutions/feature/17636.html) this problem does not
occur (while firefox uses its own postscript generator). When printing from a
kde application or using kprinter we have again the mysterious jumping letters.
See also bug #210256
--
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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213934
Summary: Konqueror does not auto refresh folder/drive content
Product: openSUSE 10.2
Version: Alpha 5 plus
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: romain.pelissier(a)sqliaison.com
QAContact: qa(a)suse.de
When I open My computer and select the DVD/CD drive in the Disk information
section I can have access to the content of the DVD. But if I change the DVD,
Konqueror does not refresh the folder and file list automatically and I have to
do that manually
--
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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223800
Summary: kmix does not set MasterMixerDevice automatically -
global hotkeys not working
Product: openSUSE 10.2
Version: RC 1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: robin.knapp(a)fujitsu-siemens.com
QAContact: qa(a)suse.de
kmix does not select the master channel automatically.
Global hotkeys for master channel won't work until the master channel is set up
manually by right clicking on the icon and selecting "Hauptkanal auswählen"
("select master channel" I think)
In this dialogue, the master channel is already selected so just pressing ok
does the job and global hotkeys for the master channel work.
<snip>
robin@linux:~/.kde/share/config> diff kmixrc.bad kmixrc.good
4a5
> MasterMixerDevice=0
</snip>
(kmixrc.bad = before selecting master channel manually, kmixrc.good = after)
However, somewhere I read that XF86RaiseVolume and XF86LowerVolume should be
automatically bound to volume up/down in 10.2, but I still have to set global
hotkeys for this. I'm not sure if this is intended.
--
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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=237565
Summary: kwrite (kate) stops opening
Product: openSUSE 10.2
Version: Final
Platform: i586
OS/Version: SuSE Linux 10.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X.Org
AssignedTo: sndirsch(a)novell.com
ReportedBy: mvdv(a)spamcop.net
QAContact: sndirsch(a)novell.com
Hi,
Following refers to openSUSE 10.2, std pacakges, updated.
Opening plain text files using kwrite from within konqueror works for a while,
then starts to complain (Sorry - Konqueror):
KDEinit could not launch 'kwrite'.
This can be fixed by a reboot, but then reoccurs. I've seen this behavior with
both kate and kwrite.
running (as root) from a bash shell:
# kwrite /path/to/text.file &
Does work for a few days longer. Then kwrite fails to launch from the command
shell. I haven't persisted long enough with kate to see if it also fails from
the bash shell.
The shell error is:
kwrite: cannot connect to X server :0
HTH
--
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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=212053
Summary: Set promote_secondaries=1 by default
Product: openSUSE 10.2
Version: Alpha 5
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: kernel01(a)hailfinger.org
QAContact: qa(a)suse.de
/proc/sys/net/ipv4/conf/*/promote_secondaries is currently set to 0 by default.
Changing that to 1 would be a user-visible change for users with multiple ip
addresses on one interface, but the changed behaviour is IMO less surprising
than the current one.
Description for promote_secondaries:
Deleting the primary IP address of an interface forces deletion all secondary
IP addresses unless promote_secondaries is set.
This side effect of killing all secondary addresses without warning (and
without documentation about this behaviour) has caused me and lots of others
quite some grief.
Scenario: You are logged into a remote box on one of its secondary IP addresses
(to be able to change the primary IP address without disrupting your work),
delete the primary IP address to later add the new primary IP address and
suddenly find out that the secondary IP address you were using for
administration has vanished. No way to connect to the box (it has no IP address
anymore), so you have to ask someone to flip the power switch and hope it works
with the old config after reboot.
If promote_secondaries had been set, the disaster would not have happened.
--
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, or are watching someone who is.