January 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 224886] reimplement zmart features in zypper
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=224886 User jkupec(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=224886#c10 Ján Kupec <jkupec(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Status Whiteboard|in-svn | --- Comment #10 from Ján Kupec <jkupec(a)novell.com> 2008-01-14 08:27:39 MST --- submitted -- 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 353515] New: opensuseupdater-kde crashes when selecting upgrade while refreshing
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=353515 Summary: opensuseupdater-kde crashes when selecting upgrade while refreshing Product: openSUSE 11.0 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: felix(a)derklecks.de QAContact: qa(a)suse.de Found By: --- The opensuse-updater-kde crashes every time when one clicks on the list of upgrades while the applet is refreshing the repo. STEPS TO REPRODUCE: 1. configure the applet to show upgrades 2. click on the icon in the taskbar to open the main window of the updater 3. right click on the icon to check for updates 4. if there are several upgrades and one clicks on one of them, the updater crashes. I will attach the backtrace. -- 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 163626] kernel-xen: suspend-to-disk or RAM does not work
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=163626 User jbeulich(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=163626#c9 --- Comment #9 from Jan Beulich <jbeulich(a)novell.com> 2008-01-14 07:04:06 MST --- Suspend (to RAM) ought to work in 3.2 (but needs to be tested), hibernate will continue to not work there. -- 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 348092] New: chasen broken on 64-bit
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=348092 Summary: chasen broken on 64-bit Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: uli(a)novell.com ReportedBy: uli(a)novell.com QAContact: qa(a)suse.de Found By: Development The x86-64 build of chasen does not produce any sensible output. Installing the i586 build makes the problem go away. -- 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 353610] New: KIWI: Looging into files leaves filedescriptors open
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=353610 Summary: KIWI: Looging into files leaves filedescriptors open Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms(a)novell.com ReportedBy: jcborn(a)novell.com QAContact: adrian(a)novell.com Found By: Development I used KIWILog to log different kinds of messages in different locations. I created a new instance of KIWILog as follows: $this->{m_logger} = new KIWILog("tiny"); $this->{m_logger}->setLogHumanReadable(); $this->{m_logger}->setLogFile("$this->{m_basedir}/packages.log"); When I stop execution at some point and issue the command "lsof | grep packages.log" I see the file opened many times. After each call of KIWILog::warning() or KIWILog::info() there are two more than before. The problem seems to be in KIWILog::setOutputChannel() and KIWILog::resetOutputChannel() where some file descriptors are concatenated. Marcus: I'll switch back to stdout/stderr logging and capture the output in the meantime; but for the final product I'd like to write to several logfiles, so this would be extremely nice to have :) -- 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 350566] New: lilo hanging at christmas screen
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=350566 Summary: lilo hanging at christmas screen Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: snwint(a)novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: --- A friend of me just informed me that lilo shows the christmas screen on his computer - and hangs at this stage :-( Interestingly, it works if he first enters bios setup, saves the settings and then boots. I'll ask him to disable the message=... line in lilo.conf (not tested yet) and expect this fixes the problem. Question: Are you interested in debugging this problem? If yes, please point me to some instruction. -- 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 348980] New: [patch] ogmmerge crashes on x86-64 because of typo
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=348980 Summary: [patch] ogmmerge crashes on x86-64 because of typo Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tony(a)daylessday.org QAContact: qa(a)suse.de Found By: --- ogmmerge (from ogmtools package) crashes when trying to merge two files on openSUSE 10.3 64bit. The backtrace looked like this: #0 vorbis_comment_dup (vc=0x631b40) at vorbis_header_utils.c:163 #1 0x0000000000410636 in video_packetizer_c::produce_header_packets (this=0x631c50) at p_video.cpp:129 #2 0x0000000000410026 in video_packetizer_c::process (this=0x631c50, buf=0x6715b0 "", size=3286, num_frames=1, key=1, last_frame=0) at p_video.cpp:174 #3 0x0000000000405d8d in avi_reader_c::read (this=0x6312e0) at r_avi.cpp:401 #4 0x0000000000405029 in main (argc=5, argv=0x7fff55714448) at ogmmerge.cpp:956 vorbis_header_utils.c, line 163: memcpy(new_vc->comment_lengths, vc->comment_lengths, (vc->comments + 1) * sizeof(char *)); Apparently, lengths are not (char *), they are ints, so the line should look like this: memcpy(new_vc->comment_lengths, vc->comment_lengths, (vc->comments + 1) * sizeof(int)); This change fixed the crash. See the patch attached. The bug's been reported to the original author. -- 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 351760] New: yast partitioner shows wrong mount points
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351760 Summary: yast partitioner shows wrong mount points Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: psikodad(a)gmx.de QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=189404) --> (https://bugzilla.novell.com/attachment.cgi?id=189404) yast logs the yast partitioner shows wrong mount points for two entries. see yast logs at time 2008-01-04 20:46 the mount points of /dev/md0 on /srv/ftp/mp3 /dev/md1 on /srv/ftp/video are wrong. correct is: /dev/md0 on /home /dev/md1 on /home/dom/video The reason could be that I'm executing two --bind mount commands at start up: mount -r --bind /home/dom/video/Nina /srv/ftp/video mount -r --bind /home/dom/MP3 /srv/ftp/mp3 the output of mount shows ----------- dom@alone:~> mount /dev/hda3 on / type reiserfs (rw,noatime,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/hdc5 on /windows/160GB type reiserfs (rw,noatime,acl,user_xattr) usbfs on /proc/bus/usb type usbfs (rw,default) /dev/md0 on /home type reiserfs (rw,noatime) /dev/md1 on /home/dom/video type reiserfs (rw,noatime) /home/dom/video/Nina on /srv/ftp/video type none (ro,bind) nfsd on /proc/fs/nfsd type nfsd (rw) /home/dom/MP3 on /srv/ftp/mp3 type none (ro,bind) -------------- after umounting /srv/ftp/mp3 and /srv/ftp/video everything is OK. YaST shows now the correct mount points for /dev/md0 and /dev/md1. (see yast logs at 2008-01-04 21:31) I guess the --bind confuses YaST, isn't it? regards Dominik PS: the yast logs are 2MB big and I removed already some old log files. The original save_y2logs file is 10MB big. If you need the full file, just ask for them... -- 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 271720] New: Yast LVM confuses mount points
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=271720 Summary: Yast LVM confuses mount points Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martin(a)oneiros.de QAContact: jsrain(a)novell.com Having additional mount points under an LVM mount point (e.g. with bind) confuses the LVM module of Yast: It shows the last mount point in fstab as mount point for the volume. E.g. with the attached fstab Yast thinks that /dev/system/space is mounted at /space/home/ms/Documents -- 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.

1 11

[Bug 274817] New: revamping the GNOME main menu layout to something simpler
by bugzilla_noreply＠novell.com 14 Jan '08

14 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=274817 Summary: revamping the GNOME main menu layout to something simpler Product: openSUSE 10.3 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: christian.jaeger(a)rub.de QAContact: qa(a)suse.de When we look at the layout of the 0.9x-series of the gnome-main-menu, we see a lot of empty space (see attached picture #1); this dead space can be regarded as wasted screen-real-estate. Is it a good idea to go the big-board-way and eventually fill the whole screen? IMHO the right thing to do is not to fill the empty spaces with yet more buttons but to shrink the main-menu. A smaller menu makes for shorter ways for the mouse-cursor and quicker access. This brings me to a second problem - too many buttons. IMHO the menu in its current form already constitutes an information-overload for many users: apart from the actual application-buttons we have no less than 11(!) click-able tiles in the menu; not including the search function. My suggestion is to bring this number down to 6. See attached picture #2. Here is how I arrived at this design in more detail: Thought #1: We don't need _two_ bars attached to the actual menu. Tought #2: We don't need the search-field to extend across the entire length of the menu. Thought #3: So let's put the buttons from the right-side bar into the top bar and get rid of the right-side bar. I would especially like the logout-button to be prominent (because my Dad couldn't locate it in the original menu...). For this we still need to drop some buttons; candidate number one is 'lock screen'. At default settings, Gnome locks the screen automatically after some minute of inactivity; plus a screen-lock could just be added as another option to the 'logout'-menu (http://www.tuxmachines.org/gallery/d/357-2/byebye.jpg) Candidate #2 is the 'install software'-button. Some users install or remove software regularly, a bigger portion of users does so very rarely. My suggestion is to simply put the 'install software' or a 'software management'-button among the other applications because an application it is and next to other applications is where people will look when they look for applications. Finally, the info-tiles. Do we really need to know whether the machine is connected to the Net every time we open the menu? And also, how much space there is on the HD? I think not. Also, this replicates data we should be shown in the gnome-panel (network-manager, D-Bus low-space warning). In the end, if want more in-depth information about what the state of our computers is, we would look for system-information somewhere where we can do other system-maintenance, also, i.e. somewhere in the control center. So, my suggestion is a new tab which merges some system information display with an integrated version of the control center. Let us call it 'System'. But I'm gonna file this suggestions as another bug. Apart from the main tab of the main-menu there is more waste of screen-real-estate. The 'Documents'-tab displays does use an entire tab to display no more than 6 recently-used documents at the defaults. The 'Places'-tab uses this space to display 8 places that we also find in Nautilus' sidebar. And it even looks more messy than Nautilus' places-sidebar. Why do we need a whole tab to do something that fits into a sidebar? This is not efficient IMHO. As 'Documents' and 'Places' share a very similar semantic value (spatial), I think we could easily merge these two tabs and call it 'Documents', 'Files' or whatever. See attached picture #3. I have some more suggestions, namely integrating a rudimentary filebrowser, but I'm going to file another bug for that. This would also give us a beautiful trinity of function in the main menu, now: 'Applications' (=actions), 'Documents' (=data) and 'System' (=settings). Easier software installation is a big point of discussion ATM and I think that the main-menu could be useful in this respect, too. I'm gonna file another bug for that. One more word about the 'search'-function. As many other people I feel it should be intuitive if the search button would display results inside the main menu, as long as the user doesn't hit the return-key. --------- We should also have some guidelines about the design of the menu. I have some suggestions to make: • The mouse should have to move short ways --> no dead space wanted. • The complexity of the layout should be minimal (no extra bars). • The menu should stay small. • The hierarchy of buttons is top-down and left-right • There should be as few clickable objects as possible. • There should be as few screens as possible to navigate before finding a desired function • There is three types of click-able objects in the menu: links(those aren't tiles and don't have symbols), actions and 'super' objects (those aren't tiles, either) • 'Super' objects are those which trigger actions that supersede the usual menu-actions: logout and help • Links represent collections of activities • Clicking on links changes the layout of the main frame, like in an internet-browser-window • Links appear only within the main-window, which they change, in order to make their being connected obvious • Activities are represented by tiles. --> installing software is only an activity, too! • Links should change the main frame • Information should not be clickable! (because it confuses) -->'harddrive' and 'network' are reduced to text-status and aren't tiles, anymore • There should not be more bars than necessary in order not to distract the eye from the main part of the menu. What do you think so far? Is this a meaningful collection of ideas? Thanks for your time; keep up the great work! Chris The initial discussion about this design-proposal started here: http://lists.opensuse.org/archive/opensuse-gnome/2007-05/msg00013.html -- 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.

1 20