https://bugzilla.novell.com/show_bug.cgi?id=440889
Summary: Adding a field to change timezone in Bugzilla
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: bugzilla
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: noelamac(a)gmail.com
QAContact: novbugzilla-bugs(a)forge.provo.novell.com
Found By: ---
Hello,
In Bugzilla, I cannot find under "Preferences" any field to change the timezone
of the reports (defaults to MDT).
I think it would be nice to have that option so the user can adjust it to fit
his needs.
Thanks!
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=440321
Summary: "something is blocking the memory sub-system"
Product: openSUSE 11.1
Version: Factory
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: sven.burmeister(a)gmx.net
QAContact: jsrain(a)novell.com
Found By: ---
On a MSI Wind I boot via the card-reader and point the yast ncurses installer
to the oss repo for 11.1. During the installtion I get lots of notifications
that some process is using some memory sub-system.
Not sure what it means or how to solve it.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=440856
Summary: Kernel update to 2.6.25.18-0.2-pae brakes suspend to ram
Product: openSUSE 11.0
Version: Final
Platform: x86
OS/Version: openSUSE 11.0
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: meik.piepmeyer(a)web.de
QAContact: qa(a)suse.de
Found By: ---
This is OS 11.0 on a Thinkpad T61. Suspend to ram worked like a charm until the
latest kernel update. I did install every kernel update just in time, so the
previous version should be known by the developers. Now with 2.6.25.18-0.2-pae,
the laptop wakes up, but there is only a blank display, no chance to get to a
console with CTRL+ALT+F2 etc..
Any logs to give you?
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=439663
Summary: Your default new configuration of hibernating when idle
can be dangerous.
Product: openSUSE 11.1
Version: Beta 3
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
AssignedTo: bnc-team-gnome(a)forge.provo.novell.com
ReportedBy: robin.listas(a)telefonica.net
QAContact: qa(a)suse.de
Found By: ---
openSUSE 11.1 Beta 3
Note: It has taken me almost five hours to test and write up this report,
so please give it due consideration.
My point is that having a default configuration of hibernating openSUSE
machines (not SLES/SLED, thus not certified bundles) can be dangerous and cause
loss of data. If the machine is not certified and the user instructed, it must
be left to the administrator the decision of what will be the default
configuration: hibernate or not.
Notice that this default configuration can not be modified by us (Bug 439075).
Notice that users have no easy access to change their own configuration, as the
power manager applet doesn't start (Bug 439647).
Finally notice that I know that the test I did is dangerous for data. The
problem is that the danger is caused by the automated decision of the system to
hibernate, not by the user deciding to hibernate or knowingly place his system
on a dangerous situation.
I connected an external disk via USB with 4 reiserfs partitions, two normal,
two encrypted (created with yast in 11.0). Of each partition type one is
manually mounted, the other automatically. I also connected a usb keychain
flash disk, vfat, automounted.
I then created with OOwriter a file on each.
I also left a thunderbird session connected to two remote imap servers, open.
Then I left the machine alone, allowing it to automatically hibernate. Notice
that it auto-hibernated with open files on external media!
1) usb keychain disk, automatically mounted, vfat: survives. OOo can save the
file.
2..5) External HD, which was /dev/sda, now is /dev/sdc
2) Encrypted reiser partition, LUKS, mounted via your script
/etc/init.d/boot.crypto and proper /etc/crypttab configuration file.
Partition survives, nautilus can navigate it, CLI ok. However, oowriter can not
write to it:
# ls /mnt//usb/Erelas/cer/
~lock.4_erelas.odt# 4_erelas.odt
Error saving the document 4_erelas:
Object not accesible
The object cannot be accessed due to insuficient user rights.
3) Encrypted reiserfs partition, LUKS, automatically mounted via Gnome desktop.
Does not survive, partition does not appear. The device is there:
minas-morgul:/other/main/etc # dmsetup ls
luks_crypto_042a7ba2-8908-4255-be33-a9cb51580de4 (253, 0)
mcr_mm_erelas (253, 1)
but it is not mounted. The mountpoint /media/disk where it was, has
dissapeared. An attempt to manually mount it fails:
mount: /dev/mapper/luks_crypto_042a7ba2-8908-4255-be33-a9cb51580de4 already
mounted or /mnt/usb/Nardol busy
And it is not possible for dmsetup to remove it:
minas-morgul:/other/main/etc # dmsetup remove
luks_crypto_042a7ba2-8908-4255-be33-a9cb51580de4
device-mapper: remove ioctl failed: Device or resource busy
Command failed
oowriter fails when saving the file, obviously, the mount point has
disappeared. Even "save as" gives an error: because the current dir has
disappeared under its feet.
I must congratulate the team that wrote the /etc/init.d/boot.crypto script,
because their system survived hibernation - although oowriter did not
(lockfile?). However, the automatically mounted encrypted partition is
not that robust.
4) Manually mounted partition: survives partially. It can be read, but gives
errors:
minas-morgul:/etc # l /mnt/Amon_Din/
ls: /mnt/Amon_Din/: Input/output error
ls: /mnt/Amon_Din/.: Input/output error
ls: /mnt/Amon_Din/cer: Input/output error
ls: cannot access /mnt/Amon_Din/casa: Permission denied
ls: /mnt/Amon_Din/Part_1-Amon_Din: Input/output error
total 0
drwxr-xr-x 6 root root 160 Oct 28 16:49 ./
drwxr-xr-x 4 root root 96 Oct 28 16:42 ../
-rw-r--r-- 1 root root 0 Oct 28 16:43 Part_1-Amon_Din
?????????? ? ? ? ? ? casa
drwxr-xr-x 2 cer root 120 Oct 28 16:59 cer/
minas-morgul:/etc #
oowriter can not save:
Error saving the document 1_amon_din:
General Error
General input/output error.
The reason is that the device is still mounted on /dev/sda1, which does not
exist, it is now /dev/sdc1:
minas-morgul:/etc # mount | grep Amon
/dev/sda1 on /mnt/Amon_Din type reiserfs
(rw,noexec,nosuid,nodev,noatime,acl,user_xattr)
Even umounting and mounting gives problems to oowriter, there is a lockfile.
minas-morgul:/etc # ls /mnt/Amon_Din/cer/
~lock.1_amon_din.odt# 1_amon_din.odt
5) Automatically mounted reiserfs partition survives. oowriter succeeds saving.
I propose that, on openSUSE you:
a) change the default to never hibernate automatically
b) pop up a dialog when the user activates autohibernation warning him of the
dangers and the precautions he must have with things like external media,
opened sessions to/from other machines, etc.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=437718
Summary: gdm broken: after some idle time, I cannot login
Product: openSUSE 11.1
Version: Beta 3
Platform: Other
OS/Version: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: GNOME
AssignedTo: bnc-team-gnome(a)forge.provo.novell.com
ReportedBy: aj(a)novell.com
QAContact: qa(a)suse.de
CC: mhopf(a)novell.com
Found By: ---
After a reboot I can login without problems *directly* but if I let gdm run for
around 1h (not sure about exact time), I can only move the mouse but no button
down events appear to happen. Therefore it is impossible to log into the
system with gdm.
This occured for me on a VMware installation and also on an installation with a
IBM Thinkpad.
Talking with the X guys (CC'ed Matthias), it looks like a gdm bug and not a
generic X issue.
--
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.