Re: [opensuse-factory] Can not access taskbak after new installation
On Thu, 2006-07-20 at 06:43 +0200, Andreas Jaeger wrote: > The Nice Spider <[EMAIL PROTECTED]> writes: > > > 1. after fresh install 10.2 aplha 2 and come to gnome, > > i can not access the > > taskbar. > > 2. so, i am logout (ctrl-alt-del) and login again but > > this error message > > appear: ... panel already running...exit (something > > like this message). > > 3. after click the message box and login again my > > computer hang. > > 4. then i reset my pc... and this message appear > > (continously): > > - Trans replayed: mount 11, transid 129.. > > above text appear about 500 lines! > > 5. now, gnome work fine. > > Please file this as a CRITICAL bugreport in bugzilla against GNOME, Considering that this is the same code we are shipping in SLE and we have no relevant bug reports, I think this is at most MAJOR. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] There are 2 desktop on Gnome!
On Wed, 2006-07-19 at 19:41 -0700, The Nice Spider wrote: > 1. look at the task bar, after Places there is > "Desktop" but in right-bottom > corner there "Desktop Icon" too. I think the "Desktop" > (with some app there, > such as Control Center, yast, lock screen and logout) > is usefull and make > confuse, better put only "Lock Screen and Logout" in > the Application. > > 2. Application task bar name is TOTALLY wrong! Because > there is System and > Yast there. I think better used another name such as > .. i don't know. > Look at: > a. WinXP, they named it "Start" > b. Redhat (for those who anti-windows, I give u this > sample), they only put > the RH Logo > > After user click "the suse icon" then the taskbar will > show all app in their > category, this is more make sense > > 3. Please by default put the Desktop icon on left > side, opensuse not put it > on right side. please provide click and drag of the > desktop. you can do that > by modifying the gnome, i only told you the way even i > can not do it my self > :) easy to speak cause i don't know how to modify > gnome. The menu bar in 10.2 will be replaced by the main menu of SLE shortly. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Nautilus Issues with EEL
On Fri, 2006-08-04 at 16:58 -0700, Ryan Lewon wrote: > I have nautilus-2.12.2-76 installed... Of coures it will not launch, it says > "nautilus: symbol lookup error: /opt/gnome/lib/libnautilus-private.so.2: > undefined symbol: eel_uri_get_scheme. I suppose since the EEL package was > updated this would be causing the underlying issues. Any fixes going to be > released for this? (SUSE_Factory repository). Yes. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Symbolic link /media/cdrom
On Mon, 2006-08-21 at 18:33 +0200, Marcel Hilzinger wrote: > Am Montag, 21. August 2006 18:27 schrieb Tobias Burnus: > > Hello, > > > > Marcel Hilzinger schrieb: > > > set a symbolic link each time a CD/DVD is inserted with /media/cdrom. The > > > link should always point to the last inserted CD/DVD. > > > /media/SUSE_LINUX_10.1 > > > is cool, but its hard to work with CDs on command line and writing > > > documentation for Suse is also very hard. So please let's become > > > cd /media/cdrom > > > true for Suse Linux 10.2. Konqueror,etc should/can still show the label > > > of the disk. > > > > I always though this was the case since 10.0: It is mounted to > > /media/device (device could be "dvdram", "cdrom", "cdwriter" etc.) > > and there is a symbolic link from /media/ to /media/. > That's true for 10.0, but not for 10.1. That's why I suggest to always keep > the simple > > /media/cdrom > > The intermezzo with /media/cdrwriter, /media/dvdram, /media/dvdwriter was not > very successful I guess. > > Coolo: Please ask also the documentation team. It's really hard to write docu > for Suse Linux if you cannot tell users, where CDs/DVDs will be mounted! In SLE at least, and presumably in 10.2, there are udev rules which should handle this (works on SLE), see /etc/udev/rules.d/65-cdrom.rules -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.automake
On Fri, 2006-08-18 at 13:35 +0200, Christoph Thiel wrote: > Hi everyone, > > we are in the process of going through all SuSEconfig scripts to assess > their value/impact and to analyze different ways of solving the problems > those SuSEconfig scripts address. In many case SuSEconfig.* scripts turn > out to just be a "cheap solution". > > Let's try to reduce the number of SuSEconfig scripts to the absolute > minimum! And try to find superior solutions! > > > The first case that I'd like to fix is SuSEconfig.automake, which reads: > > --- > #!/bin/sh > cat /usr/share/aclocal/dirlist.d/* >/etc/aclocal_dirlist > --- > > There are only two packages that place files in > /usr/share/aclocal/dirlist.d/ -- gnome-filesystem and automake itself. > > To achieve the same, while getting rid of SuSEconfig.automake, I'd like to > propose to move the above-named script to %postinstall / %postuninstall of > gnome-filesystem and automake. I suspect the gnome-filesystem one isn't really required anymore since /etc/profile.d/ is used by gnome to set ACLOCAL_FLAGS which is respected by gnome-autogen. Stanislav could comment more accurately though. -JP -- > > JP Rosevear <[EMAIL PROTECTED]> > Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.automake
On Mon, 2006-08-21 at 20:42 +0200, Andreas Hanke wrote: > Hi, > > JP Rosevear schrieb: > > I suspect the gnome-filesystem one isn't really required anymore > > since /etc/profile.d/ is used by gnome to set ACLOCAL_FLAGS which is > > respected by gnome-autogen. Stanislav could comment more accurately > > though. > > Doesn't suffice for me. Running "autoreconf -fi" on inkscape with just > ACLOCAL_FLAGS set does not work for me. The dirlist entry is really > needed there. gnome-autogen runs aclocal with the ACLOCAL_FLAGS included, so you are probably right and this won't work in the autoreconf case. Moving gnome to /usr should suffice though. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Error while starting the GNOME settings daemon
On Wed, 2006-08-30 at 21:19 +0200, Christoph Thiel wrote: > On Wed, 30 Aug 2006, Émeric Maschino wrote: > > > I just finished a fresh network installation of openSUSE 10.2 Alpha 3 on > > my hp workstation zx6000 (Itanium IA-64 architecture). When I log in a > > GNOME session, I'm getting a dialog stating that there was an error > > starting the GNOME settings daemon. This dialog has no window decoration > > at all. During the same time, the window manager icon is displayed for > > several minutes in the GNOME splash screen before the starting process > > and the remaining icons are displayed. I eventually access to a GNOME > > desktop, but there's no window decoration at all and windows can't thus > > be moved, resized, etc. > > > > I've only found one similar report here www.tuxmachines.org/node/8898 > > > > There's nothing similar in bugzilla for the openSUSE 10.2 and > > OpenSUSE.org products. > > Please file a bug then! Its already filed, its probably just an artifact of the latest control center package not being in stable. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] RED ALERT: do not lock session with Factory
On Tue, 2006-09-12 at 16:48 +0200, Azerion wrote: > I filled a bugreport for this one, I guess, but cannot find it anymore. Any > comments on that? > > If you lock qou're KDE-session you won't be able to return. It will allways > return "Incorrect password". It first happened tonight while I was updating > to factory. There is a bug filed on this for gnome-screensaver as well, so perhaps its a generally pam failure? -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Mozilla Firefox 2.0
On Mon, 2006-10-16 at 12:57 +0200, Dominique Leuenberger wrote: > Hi everybody, > > On the openSUSE Wiki, it's written that with openSUSE 10.2, Mozilla > Firefox 2.0 should be delivered (Mozilla is due to be released in > October). > But up to now, even in the current factory tree, there are no traces > of Firefox 2.0. Only 1.5.0.7 is available. > > Is this to be changed or will we deliver and 'old' Firefox with > openSUSE 10.2? We are packaging 2.0 for 10.2. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Compositing manager in Metacity
On Fri, 2006-10-13 at 16:20 +0100, James Ogley wrote: > Ref: http://rubberturnip.org.uk/index.cgi/2006/10/13 > > A while ago[1] there was some discussion here around the compositing > manager in Metacity. I've built metacity packages and libcm which is > required for the CM in my BS repo[2]. I don't have a Factory install at > the moment so I'd appreciate if some intrepid tester could, well, test > them for me. > > If they work, I'd like to propose the changes for Factory/10.2. > > [1] http://lists.opensuse.org/opensuse-factory/2006-09/msg00204.html > [2] http://software.opensuse.org/download/home:/Riggwelter/ I disagree, the compositing stuff in metacity is not well maintained. RedHat, the primary authors of that work, have decided to use compiz instead. There are technical challenges doing compositing inside of metacity. See some recent mails on gnome's desktop-devel-list (especially where Owen Taylor describes the issues in detail). -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Icon Set for YaST
On Wed, 2006-10-18 at 13:54 +0200, Andreas Jaeger wrote: > Hi, > > reading the discussions on this mailing list about the switch of the > YaST2 icon theme and gathering some more information that I was not > aware at when I made the decision, I'm suggesting the following plan: > > * Go back for 10.2 to the crystal icon set for YaST (the crystal icons > were used in 10.1 and earlier) > > * For openSUSE 10.3: > > - figure out which icons are needed > > - take care that we have a complete set of tango icons for yast2 > (there are still some missing which I didn't know before making > the decision) I'm surprised by this one since Jakub covered everything for SLE, maybe there are just a couple of holes for new module? > - use consistent names for icons so that we can easily switch > between themes. > > - find volunteers to take care of new crystal icons for yast2 > > - consolidate all YaST icons in one central place (currently *most* > are in the theme package but not all) so that we can switch > between icon sets > > - discuss and decide which icon set to use for YaST for the > following situations: > * during installation > * with GNOME as default desktop > * with KDE as default desktop > > - discuss and decide whether to change the icon set for KDE (and to > which icon set) > > Would this plan be ok? -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Remove zen-installer from gnome-main-menu
On Sun, 2006-11-05 at 15:34 +, James Ogley wrote: > > There is a way to change this. In gconf : > > /desktop/gnome/applications/main-menu/system-area/package_manager_item > > I think here's an important point and it affects the Favourite > Applications section too. Bizarrely, it never occurred to me that that > might be GConf controlled (turns out to be > under /desktop/gnome/applications/main-menu/file-area) and I'm an > uber-1337 GNOME-master (ahem). It looked like these were Novell's > favourite apps. > > If gnome-main-menu is going to be seriously usable (especially if it's > accepted into upstream), there needs to be an obvious way (perhaps a > 'Choose Favourite Applications' button next to the 'More Applications' > one) of editing this list. We were concerned about this, however in our user testing right click and drag and drop were found and used. > The 'More Applications' list is another important thing to look at. At > the moment, it launches the application browser which, frankly, is > rubbish. It would make a lot more sense if pressing this button simply > opened the Applications menu, as a menu. User testing did not show this to be rubbish actually. The speed at which it opens is an issue. User testing did show that hierarchical menus are awful for most users since they don't know where to look. There is an enhancement idea to make More Applications do more of a traditional menu as an *option* for users who do know what they are doing with a hierarchical menu however. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Remove zen-installer from gnome-main-menu
On Sun, 2006-11-05 at 00:29 +0100, Andreas Jaeger wrote: > "Claes Bäckström" <[EMAIL PROTECTED]> writes: > > > Hi > > > > I would like that when I choose "install software" in gnome-main-menu > > it will start yast2 sw_single instead of zen-installer. > > > > Should I file a enhancement bug in bugzilla? > > This might be possible already today with some gconf action. JP, do > you know what needs to be done? If this is the case, let's document > it on the wiki, As noted in another thread, you simply have to alter the following gconf keys: /desktop/gnome/applications/main-menu/system-area/package_manager_item (the system section item) /desktop/gnome/applications/main-menu/uninstall_package_command /desktop/gnome/applications/main-menu/upgrade_package_command (the right click options) We are working on a way to make the system area more easily configurable since that has been a frequent request, but that won't be in 10.2. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] y2controlcenter-gnome
On Sun, 2006-11-05 at 19:21 +0100, Claes Bäckström wrote: > Hi > > Been using y2controlcenter-gnome from the yast2-control-center-gnome > rpm and I really love it. Have one small question only. Why isn't the > yast modules sorted the same way as in yast2 control-center? Right now its alphabetical but Scott has a fix that makes it follow the order hints in the YaST-gnome.menu file. > And is "Graphics Setup" really a "Common Task". I configure my > resolution and graphic cards once after that I don't touch it. For me > this is no "Common Task" Could go either way, sometimes people change their resolution (ie for a projector) this way instead of, say, resapplet. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] y2controlcenter-gnome
On Tue, 2006-11-07 at 01:53 +, Ricardo Cruz wrote: > JP Rosevear wrote (@ Terça, 7 de Novembro de 2006 00:55): > > On Sun, 2006-11-05 at 19:21 +0100, Claes Bäckström wrote: > > > Hi > > > > > > Been using y2controlcenter-gnome from the yast2-control-center-gnome > > > rpm and I really love it. Have one small question only. Why isn't the > > > yast modules sorted the same way as in yast2 control-center? > > > > Right now its alphabetical but Scott has a fix that makes it follow the > > order hints in the YaST-gnome.menu file. > > > > > And is "Graphics Setup" really a "Common Task". I configure my > > > resolution and graphic cards once after that I don't touch it. For me > > > this is no "Common Task" > > > > Could go either way, sometimes people change their resolution (ie for a > > projector) this way instead of, say, resapplet. > > > This yast2-control-center-gnome sounds cool. Just wondering, why didn't you > use the Yast .desktop entries (from /usr/share/applications/YaST2) and used > Gnome specifics? To integrate better with Gnome other setup tools? It uses the Yast .desktop entries. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Software test plans
On Mon, 2006-11-13 at 23:58 +1100, Peter Flodin wrote: > One thing that I think we are currently missing is test plans for the > community volunteers when doing beta testing. Sure there is a benefit > having large numbers of people doing random things as well, as you > want to test things that nobody thought of. But especially for new > testers I think having some actual tests to run through would ensure > that openSUSE testing is done consistently and I think would attract > people who just need that little hand to get started with Beta > testing. > > I have started http://en.opensuse.org/testing which is in a > rudimentary state at this point. > > Before I go further, I have some questions about http://betatestdb.suse.de > If I understand correct, it contains SUSE's own internal Beta test > plans. Correct? Can these be made public? Or can interested parties be > given access? Is the contents suitable to be used to create community > test plans? > > I would like to see a range of test plans for different hardware and > components on the wiki, categorised with expected time to complete. > You have a spare 30 minutes, you pull up a suitable length test plan > and complete it. bugzilla.novell.com now has testopia 1.1 as well and there is some testing going on with that, could be a route forward. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Q: Nautilus and removable device icons
On Thu, 2006-11-30 at 07:02 +0100, Juergen Orschiedt wrote: > Is it possible to show different icons for mounted/unmounted removable > (USB) devices? > It's a bit annoying always to right click to see the mount status... They should look different, do you have gnome-mount installed? The umounted one should look like a floppy drive almost. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Cannot mount volumes on desktop (HAL permission problem)
On Wed, 2006-11-29 at 21:09 +0100, Émeric Maschino wrote: > Hi Hugo, > > It doesn't seem to be related since the volumes on my desktop are > definitely not mounted (as can be checked with a right-click to access > the properties or the output of the mount command). I think you actually encountered: https://bugzilla.novell.com/show_bug.cgi?id=221337 -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Cannot mount volumes on desktop (HAL permission problem)
On Mon, 2006-12-04 at 21:35 +0100, Émeric Maschino wrote: > You're absolutely right. However, what's the definite status of this > bug? It's marked as RESOLVED but the last comments don't seem to > confirm this, except for the last one. > > Since I'm not running a PowerPC-based system, it could be a general > SCSI problem as stated in comment #7. Should I report the outputs of > shal and the other tools provided in the bug report? Its unlikely. Check to make sure you have hal with the appropriate fix. rpm -q --changelog hal. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Samba and SuSEfirewall
On Thu, 2007-02-08 at 22:35 +0100, Marcus Meissner wrote: > On Thu, Feb 08, 2007 at 10:25:23PM +0100, Alberto Passalacqua wrote: > > Thinking to possible improvements for 10.3, I thought it would be nice > > to have this bug solved. > > > > https://bugzilla.novell.com/show_bug.cgi?id=243809 > > > > It worked in 9.3 (if I remember right), and it's actually an obstacle > > for new users who try to configure samba, do that properly in Yast, but > > can't browse the local network even after selecting "Open firewall > > ports" in the Samba server yast tool. > > Just put the respective network interface into the Internal Zone, > it has all ports opened by default. This isn't very intuitive for most users. Better would be to finish the packages-can-open-ports bug and the samba-needs-a-narrower-range-of-ports bug. Might also be an idea to trigger the firewall changes for nautilus and konqueror. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Gnome 2.18
On Mon, 2007-02-19 at 16:48 +0100, [EMAIL PROTECTED] wrote: > Hi, > > > > Are there any plans to bring the latest gnome (at this moment it should > > > be around 2.18 beta2. > > > > 2.17.91 started going into Factory late last week, expect it to be > > hitting the servers real soon. > > OK, nice, but I assumed you wanted to get rid of /opt/gnome before doing > version upgrades? I think we're far enough along we can keep going, but we should keep going on the /opt/gnome removal. > Right now at least the following packages are still using it: > > NetworkManager-openvpn-gnome > seamonkey > jpilot-Backup > NetworkManager-vpnc-gnome > seamonkey-mail > OpenOffice_org This one is already filed: https://bugzilla.novell.com/show_bug.cgi?id=246588 > apparmor-admin_eng > > Not all of them are GNOME packages, but some of them are, they should be > fixed. Definitely. One thing that discovered a few bugs for me was strings/grepping everything in /usr for "opt/gnome" not everything needs updating since somethings are just comments or extra paths, but it would be great if someone could churn through that output looking for problems. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] meeting minutes of last dist meeting
On Mon, 2007-02-19 at 19:35 +0100, Andreas Jaeger wrote: > Our last meeting was moved by a week and I forgot to inform you. > Sorry about that. Here're the minutes, > Usecases: > * Reduced image size especially of thin clients and Live images > * Reduced image size for distributions > * Updating of single translation should be easier A key part this last item would be the ability to take translations from the community as well, similar to Ubuntu's Rosetta. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] meeting minutes of last dist meeting
On Tue, 2007-02-20 at 13:40 +0100, Alberto Passalacqua wrote: > > > I understand the issue/status of GNOME packages (and of the several > > > apparently > > > ignored critical bugs) was going to be addressed. Any update on this? > > > > Those are not on-topic for the dist meeting. > > > > I got a list of 4 bugs and I though we see progress there. Don't we? > > > > Andreas > > Just for knowledge, the original list was: > > * Bug 229190 - main-menu Hangs This is not easy to replicate. A trace of it while hanging would be good. > * Bug 228129 - gnome-main-menu leaks ~2mb per recent entry/opened > file Think we have a fix for this one, we'll put it out soon. > * Bug 216129 - gnome-panel crash Only happening in factory (still needs a fix eventually) > * Bug 224409 - gnome-panel burns my CPU (10 gettimeofday calls > in 10 seconds) Not really 10.2 specific, happens if desktop-data-SuSE is updated, so should mostly affect factory (but needs to be fixed). > * Bug 215301 - Banshee doesn't recognise my ipod anymore There is a work around in the bug, but we should release a patch. > * Bug 230676 - It's impossible to configure a printer if not root. > (The gnome configuration tool doesn't remember per-user settings > like two-side printing or printing quality) Yes, this is a problem, configuration as non-root (even for setting up a printer) is something that was discussed at the last dist meeting, we want to have a general solution for 10.3. > * Bug 229254 - Gnome CD/DVD burning dialog widget disappear This seems to be an issue with multiple drives, its easy to work around be right-clicking the iso file instead. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Printing in openSUSE 10.3
A couple weeks ago at the dist meeting we discussed improving how printers are configured on openSUSE. Specifically we discussed the following use cases as something we would want to achieve for 10.3, and we'd like to open up the discussion on implementation: 1) Detecting a local USB printer when plugged into the machine and prompting the user to configure it or automatically selecting a driver and configuring the printer We have a lot of the detection code, both usb and hal cups backends can detect the usb printer. Hal being a general hardware detection layer actually sends a message when its plugged in and GNOME uses this to pop up a dialog to configure the printer via a hal backend for cups. However the hal backend is not a standard upstream cups backend and its very difficult to convert a cups hal:// uri to a usb:// one - but not entirely impossible, there is some code in /usr/bin/add-unknown-printer (part of the gnome-volume-manager) to do some of this. Yast also does not support the hal backend currently. The usb cups backend is the standard upstream cups backend but it does no polling so we'd need to poll somehow (gnome-volume-manager and kmediamanager are possiblities). For true zero config printer, we'd need to build up a database of printer ids and driver mappings and include that in the distro. We also need to make this configurable so that you have the possibility of not doing zeroconfig printing on servers. 2) Not needing root to configure a printer Couple of thoughts here, for a hal based solution we might be able to leverage PolicyKit and unify our hardware access permissions system with an upstream default. We could also alter resmgr for this or use sudo. We need to make sure this is configurable though, because it needs to be turned off for servres. 3) Detecting when a printer is connected/disconnected and offering visual feedback via a notification area icon, or some other ui feedback An easy thing to do here would be to patch cups to send out dbus signals and both GNOME and KDE could put up tray icons or whatever. HAL could also be used to detect disconnects reconnects 4) Ability to remove printers from cups (even shared printers) when they're unplugged to prevent jobs from accumulating in the queue or being default If we can get to zeroconfig printing we could optionally just remove a printer from cups when its unplugged. A little more unclear how useful it would be. If someone wants to throw up some info as an openSUSE project http://en.opensuse.org/Projects that would be great. I suspect items 1) and 2) are really the keys, if they work then 3) or 4) should be pretty straightforward. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Network profiles in NetworkManager
On Wed, 2007-02-28 at 21:19 +0100, Alberto Passalacqua wrote: > An interesting enhancement, which seems to be already present in Fedora, > was suggested by a user (psp250) in IRC. Do you know how Fedora is doing it? > NetworkManager at the moment is able to connect to manage only a single > static IP, and if static DNS are specified, it's unable to update them > when it connects to a dynamic network. > > The suggestion is to: > > * Make NM able to manage more configurations for the same network > card (for example, if the wireless card is used to connect to > different AP's, some with fixed configurations, some with > dynamic ones). > * Make NM able to manage static and dynamic DNS without having to > change the settings in Yast. So both of these are planned, better than that we have an idea on how to automatically detect location so NM does the right thing automatically. Robert or Tambet can explain that better than I. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Thu, 2007-03-01 at 10:04 +0100, Ludwig Nussel wrote: > JP Rosevear wrote: > > 1) Detecting a local USB printer when plugged into the machine and > > prompting the user to configure it or automatically selecting a driver > > and configuring the printer > > [...] > > 2) Not needing root to configure a printer > > Why do printers need a special case? It's just some piece of > hardware that can be plugged in at run time. Ideally there is a > (default) driver so it's possible to configure the hardware > automatically in the background and the user won't notice. If you > need any interactive input (ie YaST) to configure a device you need > to authenticate[1] as root. That barrier does not only avoid > accidential privilege escalation, it also prevents users from > thoughtlessly doing something that can harm the system. You need to > authenticate only if you plug in the hardware the first time > anyways. One likely does not plug in a different printer, scanner, > tv card etc every day. They don't need to be a special case, I suggested a couple of ways we could generalize this for hardware. One good use case we've seen with customers is that they don't want to give out the root password because that would enable users to do anything they want like update packages. > > 3) Detecting when a printer is connected/disconnected and offering > > visual feedback via a notification area icon, or some other ui feedback > > There should be no special case for printers. You want that for any > hardware. Like e.g. a well known popuplar OS tells you "the XYZ > device is ready to use now" (or whatever the exact wording is). In > case of a printers I'd expect tools like kprinter to already > visually indicate if a queue is disabled which is unrelated to > whether the hardware is actually available. I'm talking of specialized device info, not simple existence. Yes, you can poll for the status, but a straight forward message on the bus allows a number of applications to receive pushes rather than pull the info. > > 4) Ability to remove printers from cups (even shared printers) when > > they're unplugged to prevent jobs from accumulating in the queue or being > > default > > I think it's a valid use case to queue a printjob and have it > printed when the printer is connected again. Its a valid use case not to want to do this either, which is why it should be configurable. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Thu, 2007-03-01 at 11:29 +0100, Ludwig Nussel wrote: > JP Rosevear wrote: > > One good use case we've seen with customers is that they don't want to > > give out the root password because that would enable users to do > > anything they want like update packages. > > What specific part of printer configuration should a user be able to > do without authentication? Demanding that users must be able to > "configure printers" without knowing the root password is too coarse > grained. AFAICS the YaST2 printer module for example offers to > reconfigure the firewall and to install additional packages when > needed also as part of printer configuration. Adding printers. You can get large setups with dozens or hundreds of printers. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Thu, 2007-03-01 at 12:33 +0100, Klaus Singvogel wrote: > JP Rosevear wrote: > [...] > > > > 1) Detecting a local USB printer when plugged into the machine and > > prompting the user to configure it or automatically selecting a driver > > and configuring the printer > > > > We have a lot of the detection code, both usb and hal cups backends can > > detect the usb printer. > > Please keep in mind: this discussion should not be restricted to usb > and hal backend, also the vendor specific backends should be > supported: hp:, hpfax: (both from the full OpenSource project hplip), > epson:, and many more to get the best printing results from a printer. Very good point. Can these detect USB devices like the usb backend? Or to they have a better canonical naming scheme for the printers? > > Hal being a general hardware detection layer > > actually sends a message when its plugged in and GNOME uses this to pop > > up a dialog to configure the printer via a hal backend for cups. > > However the hal backend is not a standard upstream cups backend and its > > very difficult to convert a cups hal:// uri to a usb:// one - but not > > entirely impossible, there is some code in /usr/bin/add-unknown-printer > > (part of the gnome-volume-manager) to do some of this. > > We need to mention that the current hal backend needs to be extended > to satisfy the new requirements, which actual CUPS system expects > from backends. But it seems that upstream developers didn't work on > this opportunity till today. Well, it works enough to be used extensively in Fedora and Ubuntu, but yes it could be missing some pieces that we would need to add. > > Yast also does not support the hal backend currently. The usb cups > > backend is the standard upstream cups backend but it does no polling > > so we'd need to poll somehow (gnome-volume-manager and kmediamanager > > are possiblities). > > Hmm. I had a quick look at the current hal/dbus architecture. I didn't > see any pollin by any device so far. Instead an administration process > called by the hal/dbus system is executed. I'm speeking about the > hal-cups-utils/hal_lpadmin tools. > Maybe I'm wrong... I meant if we want to base the detection on the usb backend we'll need polling. > But if not, then we might replace the hal backend by _any_ backend, > and no need to use no longer developed tools (hal backend) is needed. > Instead we can use our own mechanism here, even YaST, as soon as YaST > supports installation of printers without any need of user feedback > (full automatism). > > I want to point out, that there should be no goal to remove the usb > backend from the system. The reasons are the manuals, and the CUPS > book, which only speaks about this. Also the good help at the cups > mailing lists should be mentioned, which is no longer usuable for > the customers, if we cut the usb backend off the system. Agreed. > > For true zero config printer, we'd need to build up a database of > > printer ids and driver mappings and include that in the distro. We also > > need to make this configurable so that you have the possibility of not > > doing zeroconfig printing on servers. > > True. This is the first step. > > I'm still asking myself how a correct paper size (Letter or DinA4) > is configured by zero conf. Locale data might be one way to guess (pretty much anyone outside North America is probably A4 :-)). > If we want to extend this later, then we should think about a way to > preserve an existend, and possibly modified configuration of a specific > printer. The idea is here to get the old system configuration back, > as soon as a printer gets replugged into the system. Agreed. > > 2) Not needing root to configure a printer > [...] > > No comments from me to this topic so far. > > > 3) Detecting when a printer is connected/disconnected and offering > > visual feedback via a notification area icon, or some other ui feedback > > > > An easy thing to do here would be to patch cups to send out dbus signals > > and both GNOME and KDE could put up tray icons or whatever. HAL could > > also be used to detect disconnects reconnects > > We need also handle the situation if a printer gets connected/ > disconnected from the system when the system was switched off. We > should not restrict our thinking about getting signals, boot time > needs also to be handled properly. > > About the tray icons: as this automatic configuration should also > work on machines without KDE nor GNOME, this is only an optional > extension in my point of view. DBus signals would handle this, if there is no listener they would j
Re: [opensuse-factory] OpenSUSE, bugs and some considerations
On Fri, 2007-03-02 at 22:52 +0100, Alberto Passalacqua wrote: > After quite a long time, I decided to do some considerations on the > status of OpenSUSE as a community and as a distribution, starting from > everyday experience. > > I'll start from some bug reports, which affects me directly and which > have been waiting for a solution for a long time since the release of > 10.2 final. They're only examples, you can find many others on bugzilla. > > * main-menu Hangs > https://bugzilla.novell.com/show_bug.cgi?id=240727 > > * Banshee doesn't recognize ipod > https://bugzilla.novell.com/show_bug.cgi?id=215301 > > * yast is still unable to list printers > https://bugzilla.novell.com/show_bug.cgi?id=240727 > > * Gimp can't print: > https://bugzilla.novell.com/show_bug.cgi?id=230887 which sends > to bug #226710, which is not accessible. > > > The main menu bug is a blocker and it's really strange no-one in the > development team noticed it during the development stage. A patch was > recently released on bugzilla, but it only partially solves the problem > for some user and does nothing for others, which indicates the issue is > quite serious. We suspect it might be related to the size or entries in ~/.recently-used and are continuing to look at it. > A final comment, to conclude this already long e-mail, is about the > GNOME-KDE question (seriously, for once). > > Gnome users (not only me, there are a few, but there are) are quite > bored to see GNOME considered the de-facto second choice of the > distribution because it is less tested than KDE and less maintained. > > Now, I understand many developers at SUSE love KDE and that SUSE was a > KDE based distribution. But in the past at least it was coherent: KDE > was the default and SUSE was really optimised for KDE. It was so evident > that GNOME appeared out of place, and it was OK. A user who chose SUSE > knew it was a KDE distribution. > > Today SUSE has no defaults, so a user thinks he can choose what he likes > more, but it's not that way. > > In openSUSE 10.2 it is so evident a lot of the efforts were put in > creating a KDE which is better than GNOME. Examples are many: from the > new kickoff menu, which was developed faster than the gnome main-menu > and has none of the issues of the gnome one, to the opensuse-updater, > which has no equivalent in GNOME (I know one is coming for 10.3). > > Both DE should be considered as alternatives, not as rivals. I do myself > this mistake, I know. But it's really annoying to read "Use KDE" or "Use > a KDE app" when a user asks for help about GNOME. > > Moreover GNOME is the default on SLED, and having a low quality GNOME on > openSUSE doesn't help to give a good image to potential customers. > > If things are going to stay as they are at the moment, I would really > prefer a strong but clear decision to make openSUSE again a KDE based > distribution instead of having a two-DE distribution only in appearance. So, to be frank about this, the development group that includes GNOME work has not been very focused on openSUSE in the past, however we've been making a concerted effort to change this for 10.3. In the next couple of days I'll post info more widely that you already know Alberto about the opensuse GNOME mailing list and irc channel. That being said the same development group that manage GNOME has driven other general desktop technologies that have improved openSUSE substantially, such as Xgl/Compiz, NetworkManager, Beagle, so a lot of work has benefited openSUSE both for GNOME and KDE. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Fri, 2007-03-02 at 11:56 +0100, Ludwig Nussel wrote: > JP Rosevear wrote: > > On Thu, 2007-03-01 at 11:29 +0100, Ludwig Nussel wrote: > > > JP Rosevear wrote: > > > > One good use case we've seen with customers is that they don't want to > > > > give out the root password because that would enable users to do > > > > anything they want like update packages. > > > > > > What specific part of printer configuration should a user be able to > > > do without authentication? Demanding that users must be able to > > > "configure printers" without knowing the root password is too coarse > > > grained. AFAICS the YaST2 printer module for example offers to > > > reconfigure the firewall and to install additional packages when > > > needed also as part of printer configuration. > > > > Adding printers. You can get large setups with dozens or hundreds of > > printers. > > Are you talking about setups where you plug in your shiny new USB > printer and want it to just work or are you talking about network > printers? I was assuming you were talking about the former but I > somehow doubt that "hundreds of printers" need to be configured in > that scenario ;-) Network printers, I should have actually listed that explicitly in use case 2) as well. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Mon, 2007-03-05 at 15:30 +0100, Johannes Meixner wrote: > Hello, > > On Mar 2 18:44 JP Rosevear wrote (shortened): > > On Fri, 2007-03-02 at 11:56 +0100, Ludwig Nussel wrote: > > > JP Rosevear wrote: > > > > On Thu, 2007-03-01 at 11:29 +0100, Ludwig Nussel wrote: > > > > > > > > > > What specific part of printer configuration should a user > > > > > be able to do without authentication? > > > > Network printers > > Network printers??? > > What about > http://en.opensuse.org/SDB:CUPS_in_a_Nutshell > "Intrinsic design of CUPS for printing in the network" > > What is the original end-user requirement behind? The original requirement is two fold 1) Ease of use for end users It works perfectly fine on Windows XP and OS X to browse network printers and print to one without requiring admin privileges. 2) Restricting root access for admins Admins want to allow straightforward operations like changing the wireless network or adding a printer without giving out the full root password (which allows things like installing new packages) Item 1) is primary here, its just easier. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Tue, 2007-03-06 at 10:58 +0100, Johannes Meixner wrote: > Hello, > > On Mar 5 13:09 JP Rosevear wrote (shortened): > > On Mon, 2007-03-05 at 15:30 +0100, Johannes Meixner wrote: > > > > > > What about > > > http://en.opensuse.org/SDB:CUPS_in_a_Nutshell > > > "Intrinsic design of CUPS for printing in the network" > > > > > > What is the original end-user requirement behind? > > > > The original requirement is two fold > > > > 1) Ease of use for end users > > > > It works perfectly fine on Windows XP and OS X to browse network > > printers and print to one without requiring admin privileges. > > Your info is too terse for me. > I still do not understand the end-user's situation. > Please do not misunderstand me - I don't want to do nitpicking. > But I need to understand the whole picture from the end-user's point > of view - otherwise whatever nice-looking implementation may not > solve the actual end-user problem. The situtation is the end user doesn't want to type in a password to do simple operations. > What do you mean with "browse network printers" here? > Browse the raw printers or browse associated SMB shares > (or whatever kind of associated print queues)? Adding an SMB shared printer is the specific case I had in mind, but other types of network printers too if applicable > Did you read > http://en.opensuse.org/SDB:CUPS_in_a_Nutshell > "Intrinsic design of CUPS for printing in the network"? > When there is a CUPS server, there is _nothing_ to be set up > at all on the client systems, see > http://en.opensuse.org/SDB:CUPS_in_a_Nutshell > "Configuration of the clients" > > Start cupsd. > ... > Under normal circumstances, you should not configure > anything else, especially > * no local queues on clients and > * no changes in the default settings for cupsd on clients. > > > Why do you want to implement Windows-stlye printing > when we use CUPS on Linux? Because its what most users expect and want, even many linux ones. > Or is there a special end-user environment why we need > to do Windows-stlye printing even with CUPS on Linux? > > Perhaps you are talking about a user with a Linux laptop > or Linux workstation in a Windows-only environment? Not just in these specific cases, I'm thinking home users in general. > > 2) Restricting root access for admins > > > > Admins want to allow straightforward operations like changing the > > wireless network or adding a printer without giving out the full root > > password (which allows things like installing new packages) > > Why cannot the admin set up appropriate stuff in cupsd.conf > so that whatever users on whatever hosts are allowed to do > whatever he likes? > > Why should we implement something anew when from my point of view > everything is (and was) already implemented in CUPS? > > Since CUPS 1.2 there are even fine-grained policies, see > http://www.cups.org/documentation.php/ref-cupsd-conf.html > "Policy" and "Limit (Policy)" Ah, this is nice, I wasn't aware there was a policy system in 1.2, thanks for pointing this out. > From my point of view all we may need is a nice GUI to set up > those policies in cupsd.conf - e.g. an enhancement of the CUPS > web-interface, see on a CUPS 1.2 system > http://localhost:631/admin > "Server" Yes, quite possibly with the policy system above. I might rather see a single yast module that is a starting point for various configurations of this type of options, ie something like: [ ] Primary user can mount removable media [ ] All users can mount removable media [ ] Primary user can add and remove printers [ ] All users can add and remove printers [ ] Primary user can install, update and remove software [ ] All users can install, update and remove software Where the primary user is the first user you create. Ideally we'd be able to keep this hidden and have a 'Home User' vs 'Traditional Unix Permissions' option or something. (I'm also not sure this is actually a Yast module, but it will do for now as an example). This would lead into a nice system for things like basic parental controls. Robert, you had some ideas around this right? -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Wed, 2007-03-07 at 16:39 +0100, Johannes Meixner wrote: > Hello, > > On Mar 7 10:30 JP Rosevear wrote (shortened): > > On Tue, 2007-03-06 at 10:58 +0100, Johannes Meixner wrote: > > > Your info is too terse for me. > > > I still do not understand the end-user's situation. > > > Please do not misunderstand me - I don't want to do nitpicking. > > > But I need to understand the whole picture from the end-user's point > > > of view - otherwise whatever nice-looking implementation may not > > > solve the actual end-user problem. > > > > The situtation is the end user doesn't want to type in a password > > to do simple operations. > > Frommy point of viwe it seems from mail to mail > you change the issue (it started with USB printers, > became network printers, now it is about typing passwords) > and it seems you still don't tell the whole story. No, the user should not need root to include any printers, I just didn't explicitly call out network printers to begin with and I should have. > > > > Why do you want to implement Windows-stlye printing > > > when we use CUPS on Linux? > > > > Because its what most users expect and want, even many linux ones. > > I am afraid but it seems now we are at a dead end. Why exactly are we at a dead end? We agreed in the dist meeting not needing root to configure a printer was a valid use case. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Thu, 2007-03-08 at 10:04 +0100, Johannes Meixner wrote: > Hello, > > On Mar 7 10:46 JP Rosevear wrote (shortened): > > On Wed, 2007-03-07 at 16:39 +0100, Johannes Meixner wrote: > > > On Mar 7 10:30 JP Rosevear wrote (shortened): > > > > On Tue, 2007-03-06 at 10:58 +0100, Johannes Meixner wrote: > > > > > Your info is too terse for me. > > > > > I still do not understand the end-user's situation. > > > > > Please do not misunderstand me - I don't want to do nitpicking. > > > > > But I need to understand the whole picture from the end-user's point > > > > > of view - otherwise whatever nice-looking implementation may not > > > > > solve the actual end-user problem. > > > > > > > > The situtation is the end user doesn't want to type in a password > > > > to do simple operations. > > > > > > Frommy point of viwe it seems from mail to mail > > > you change the issue (it started with USB printers, > > > became network printers, now it is about typing passwords) > > > and it seems you still don't tell the whole story. > > > > No, the user should not need root to include any printers, I just didn't > > explicitly call out network printers to begin with and I should have. > > You mix up many different things is your requests > that I don't know what you actually want. > > I asked you several times to provide more info about the > original problem and the user situation but all I get > are terse snippets which are useless at least for me. I will put this as plainly as I can, the original problems are: 1) It sucks for home users to have to enter a password to setup a printer. 2) Large corporate environments don't want to give out a root password, but do want people to be able to configure a printer still. You pointed out the policy piece in cups 1.2 which is great, that gives us the underlying tools to solve this. We just need to figure out how to set this up nicely for people instead of using vim to edit a file on disk. Klaus's role bast yast email sounds promising for this. > You talk about USB printers and home users and about printing > in big networks with hundreds of printers (obviously now a > business environment) where dedicated admins exist and full > automated setup of printers (in the network?) and not being > root to set up printing (in the network?) and whatever else > may come into mind when talking about "the printing stuff". See above, two cases to be solved by the same mechanism. > > > > > > Why do you want to implement Windows-stlye printing > > > > > when we use CUPS on Linux? > > > > > > > > Because its what most users expect and want, even many linux ones. > > > > > > I am afraid but it seems now we are at a dead end. > > > > Why exactly are we at a dead end? We agreed in the dist meeting not > > needing root to configure a printer was a valid use case. > > We are at a dead end when you want to pervert how printing > is done under Unix/Linux operating sytems (for CUPS and even > for the old-stlye Unix/Linux printing systems like LPR and LPRng) > into how printing is done under Windows (and iPrint). I personally don't think setting up cups policies that mimic "Windows or OS X printing permission requirements is "perverting the Unix/Linux way"? There are millions of people who expect this kind of behavior. I want them all to be happy SUSE users. I think even existing users will by and large like this change, and if not it needs to be optional anyhow. > Because you wrote "most users expect and want" this, > it means you want to do Windows-stlye printing by default. > > This is the dead end. Nope, its a challenge. We need to present the average end/home user with what they want and expect. You've talked a lot about how cups differs. The windows-style part I'm looking for is the end user experience, its not to fundamentally change how cups works. > Again: > Please be exact with your wording! > > "do Windows-stlye printing" is different to "no need to be root > to do something" (which is different to "not type in a password"). Not having a password is the key. Maybe I jumped a head on the implementation, but a simple way to do this is to not require being root for this operation. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Printing in openSUSE 10.3
On Thu, 2007-03-08 at 10:57 +0100, Johannes Meixner wrote: > Hello, > > On Mar 7 10:52 Robert Love wrote (shortened): > > The use case is that a standard use should (optionally) be able to > > manage his printers without requiring the administrator. > > The "optionally" is the crucial word here! > The system admin (i.e. the person who set up the system) > can of course delegate his permissions and set up appropriate > stuff in cupsd.conf so that whatever users on whatever hosts > are allowed to do whatever the system admin likes, > see my mail dated 6 Mar 2007. > > The crucial point is that it is under the system admin's control > who is allowed to do what and that the system admin is aware of > the consequences, for example http://www.cups.org/str.php?L790 > --- > the CUPS admin user can copy this way any printout to any place > he likes (e.g. send it via mail to any external address ... > --- > If any user could change any print queue, any user could copy > any printout. Note the "copy" which means that it is also > correctly printed on the printer so that an innocent other user > would not notice that his printout was copied. > I assume this is not what we want to have by default to make our > customers happy in big networks with hundreds of printers ;-) The solution though is in a comment in the upstream bug: "If you would like to contribute a patch which adds a "RestrictFilters" option (or a list of allowed paths, or something like that), we will consider it for inclusion in CUPS 1.2." We could be proactive here and send a patch upstream! -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Minutes from 2007-03-23 dist meeting
On Fri, 2007-03-23 at 14:44 +0100, Ludwig Nussel wrote: > Andreas Jaeger wrote: > > Let's look what can be done for ntp - and later look at other > > services. Note the ntp service is also usefull for machines without > > network (serial DCF77 clock). Right now the dispatcher script sends a > > signal to ntp if the IP address changes but during boot ntp starts > > even if network is not running. > > > > Suggestion: ntp start script should figure out if NetworkManager is > > running and if it is only start if network is up - otherwise the > > dispatcher script will start it. > > At home my ntpd starts up with no servers defined and the ip-up > script adds time servers via ntpdc IIRC. Requires that the local > clock is sufficiently exact though. I'm not sure if there is a way > to remove time servers from a running ntpd again though. > > > Dial-in support for NetworkManager to support ISDN, Modem, UMTS, 3G > > cards is beeing worked on and should be ready for openSUSE 10.3. > > Whatever that means. Does it use existing config files as created by > yast? Potentially, just as we can use yast info for wireless and wired configs now, however the upstream implementation will not do this by default of course, it will have its own PPP config UI. How much knowledge we can extract from yast to implement the upstream config is an open question. Longer term however, I think the approach is almost definitely to use NM everywhere (of course it needs a lot of work to get there for things like static routes, multiple interfaces at the same time etc, but when discussed with the Mobile and Server teams several months ago there was general agreement on this direction). -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Re: Meeting minutes dist meeting 2007-03-23
On Mon, 2007-03-26 at 14:41 +0200, Klaus Singvogel wrote: > Andreas Jaeger wrote: > [...] > > * Status on print configuration > > > > - Discussion on opensuse-factory has been started. > > - Cups 1.2 has policies - and there's also discussion about role > > based YaST. We should avoid too many different solutions. > > - Red Hat seems to use hal backend. > > - Looking at Fedora solutions, they have some database for automatic > > setup. > > - not sure what can be done in time for 10.3 > > > > I'm wondering how this _result_ came up. > > The discussion on opensuse-factory seemed to have stopped, whereas in > the dist meeting were now some results presented, which seem not to > honor some important facts, and seem not to be common positions. I noted the discussion had stalled on factory, we became way bogged down on the issue of root vs non-root, questioning the fundamental use case after it was agreed on in previous dist meetings rather than focusing on solutions for the cases, so Chris Rivera has been doing more research that should be reported this week. > So I cannot agree with the later listed results, i.e. the > RedHat/Fedora related ones. > > Why we should _not_ use Hal backend: > - We cannot use hal backend, if we have need to support printing > ability of multifunction printers (scanner/printer/fax). The lock > of the usb device when supporting the scanning functionality is > the main reason. > - To have a full support of printers, we need to support vendor > specific backends (!= hal backend), like those from HP or Epson. > - The hal backend lacks still of implementation of new features of the > cups-1.2.x system. The upstream maintainer (RedHat/Fedora) doesn't > show any activity regarding this since release of cups-1.2x (9 > months). ==> outdated. > - It's not necessary to use the hal backend just to have the hal > functionality of plugin/remove of printers use. > Writing a hal policy file (.fdi file) with call of an Novell/SuSE > specific tool should be enough/better. I said in the dist meeting I was not convinced we should use the hal backend, I was noting RedHat uses it and has no intention of stopping. We may still need to solve the hal uri -> cups usb URI mapping problem though if we want to trigger intelligent behavior when a usb printer is plugged in. > We should not use the automatic setup solution from Fedora: > - The origin of the database seems not to be public. We cannot react > if we want to handle all of our supported printers just before a > product realase. We are always one release cycle behind > RedHat/Fedora if we want to use their solution. No improvements > at our side. I noted it could be a starting point, nothing more. How do we generate our database? No one in the previous dist meetings indicating we had a good mapping of printers to print drivers and noted that previous efforts to collect this data had failed. > - The automatic setup didn't show any further development at > Fedora/RedHat since quiet some time (it's outdated!). This was the > main reason, why even Ubuntu/Debian went away and uses now > printerdrake. > - We already have a in-house solution, named YaST!!! Why cant we use > that? YaST already does automatic printer installation, when doing a > new system installation. It should be no major effort, to enhance > YaST in such a way that we get an command-line interface to do this. Fine with me to examine, but no one had proposed this at all, as noted above the discussion got completely side tracked on the root/non-root issue. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-gnome] Re: [opensuse-factory] GNOME?
On Mon, 2007-04-23 at 16:20 +0100, James Ogley wrote: > > Third, beagle integration and SLAB are very bad. Again the beagle What in particular is wrong with beagle in GNOME? Or do you mean > > integration in KDE is terrific and kickoff works wonderfully but > > beagle in GNOME and SLAB are just horrendous. Why is SLAB such a hog? Well, in 10.2 the best version didn't go in and it simply had a lot of leaks. We've been getting a maintenance update ready for that. > The new version of slab, in Factory, seems to be less of a hog but it > still doesn't have the Beagle integration of KickOff. If you're referring to having the search results show up in the menu itself, we considered that, but felt it was overloading the menu too much. This was a conscious decision and like all UI decisions you can't please everyone (I think even kickoff has its detractors). The way to change peoples minds is to compare use cases and demonstrate the clear benefits. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] gnomebaker
On Thu, 2007-04-26 at 17:31 -0400, James Tremblay wrote: > Dear Gnome and Nautilus Team leaders, > would it be all that difficult to change the default gnome installation to > carry GnomeBaker with it? it's insultive to the end user not to have simple > md5sum checking or even have the ability to tell it to write at best possible > speed then verify. Which is completely possible under KDE with K3b which is a > default package. > I use KDE on My Laptop, but my office is all Novell SLED and I am trying not > to have to convert Novell networking and other documentation from Gnome to > KDE so I use the Gnome there, If Novell is going to support both desktop's > why are they not feature to feature equal ? I'm not suggesting that you adopt > an aditude of "is the Kitchen sink in Der, Eh " but when someone writes a > nice tool like GnomeBaker use it! I could really vent here but I won't out > of respect but... Sounds pretty reasonable, file a bug and send us the number! We should upgrade to 0.6.1 while we're at it. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] gnomebaker
On Thu, 2007-04-26 at 21:15 -0400, James Tremblay wrote: > On Thursday 26 April 2007 19:31, you wrote: > > On Thu, 2007-04-26 at 17:31 -0400, James Tremblay wrote: > > > Dear Gnome and Nautilus Team leaders, > > > would it be all that difficult to change the default gnome installation > > > to carry GnomeBaker with it? it's insultive to the end user not to have > > > simple md5sum checking or even have the ability to tell it to write at > > > best possible speed then verify. Which is completely possible under KDE > > > with K3b which is a default package. > > > I use KDE on My Laptop, but my office is all Novell SLED and I am trying > > > not to have to convert Novell networking and other documentation from > > > Gnome to KDE so I use the Gnome there, If Novell is going to support both > > > desktop's why are they not feature to feature equal ? I'm not suggesting > > > that you adopt an aditude of "is the Kitchen sink in Der, Eh " but when > > > someone writes a nice tool like GnomeBaker use it! I could really vent > > > here but I won't out of respect > > > but... > > > > Sounds pretty reasonable, file a bug and send us the number! > > > > We should upgrade to 0.6.1 while we're at it. > > > > -JP > now filed as bug #269051 And pushed to the right people for 10.3... -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Anyone interested in revamping the gnome-main-menu?
On Tue, 2007-05-08 at 13:37 +0200, Dominique Leuenberger wrote: > >>> On 08-05-2007 at 13:49, Jochen Hayek > <[EMAIL PROTECTED]> > wrote: > >>>>>> "CJ" == Christian Jäger writes: > > > > CJ> 1. Removing unneccessary space-stealers > > > > CJ> - Lock screen (who needs this?) > > > > I need it. > > > > For locking my screen I type Alt-F1 and then I select the "Lock > Screen" entry > > using cursor keys. > > > > Are you not locking your screen? > > > > How else do you lock your screen? > > I have my desktop arranged with a second panel on top with some nifty > things I need: left corner: terminal, then the mini commander and on the > right I have lock screen, logout and shutdown, together with the system > monitor. > > So basically I don't need the lock screen down there in the menu... but > I agree: it should be about a free choice, not forcing the user. Well, you in particular can right click on the item and remove it :-). (PS there is an #opensuse-gnome irc and mailing list too). -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Topics dist meeting 2007-05-10
On Thu, 2007-05-10 at 09:16 +1200, Volker Kuhlmann wrote: > On Thu 10 May 2007 05:23:24 NZST +1200, Andreas Jaeger wrote: > > > We'd like to discuss the following topics tomorrow. Please send your > > comments and suggestions as usual so that I can represent them. > > > * Smaller systems - what can be done? > > > > Goal: A system with 128 MB of space. > > > > Challenges are especially: > > * Languages and localization > > * documentation - > some packages have documentation split up already > > * theming -> some packages will be split up so that only one theme is > > in a package. > > Are you talking about 128MB of *disk* space or *RAM* space? Please make > and keep this distinction clear! Disk space. > What is the intended/envisaged use of such an installation / system? > > Do you think a small system which has only 128MB of software storage > space (hard disk, flash card, ...) has >=256MB of RAM to run SUSE > version-any on? Sure, thin clients do. This requirement is not being pulled out of thin air. Also linux on a usb stick type installations. > Are you thinking people might install on a big computer, then transplant > 128MB of storage space into something small? Do gnome, KDE, or languages > in this situation have any relevance whatsoever? No, not thinking this. > Why put effort into saving (say) 200MB of disk space when the smallest > disk on the market is 40-80GB? See above. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] compiz-fusion and 10.3
On Sun, 2007-07-22 at 00:12 +0200, Martin Schlander wrote: > As feature freeze is drawing closer and compiz-fusion have yet to release I'm > wondering what will be done here. > > Will compiz-fusion(-git) move into factory before feature freeze? Yes, this is the plan. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
on how kde discovers help files and our older patches broke big time. We should look at the for 10.4 Thats good and all , but it doesn't go all the way of course - Gary Ekker has been getting some better bug criteria created for understanding when we should upstream, wontfix, invalid, etc. Its for both SLED and openSUSE, we did a test run last week and it worked reasonably well. I think Gary would like to publish these soon for GNOME at least, just a bit of hesitation to push them out at this point in the release cycle. Maybe AJ/Coolo/Christoph could take a quick look first and they can form a basis for discussion across the project (although maybe upstreaming differs between kernel and GNOME). Finally, there has been a move to standardize severity definitions internally at Novell, we should probably see about publicizing those or consciously have different (more standard open source definitions) for those. I have some definition thats Gary, Thorsten K, Mihnea and I did a few months a go that could be a good start once they are un-SLEDified if anyone is interested. (I suppose these last two things should migrate to an opensuse-project thread.) -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
On Tue, 2007-09-04 at 15:37 -0300, Druid wrote: > > > > 3) We (as the GNOME maintainers who work for Novell) have traditionally > > not focused on openSUSE much, rather spending most of our time on SLED. > > This improved for 10.3 and well continue to improve, but we lagged a > > little more than we thought due to SP1 of SLED 10. > > > > Seems one of those very traditional traditions that goes through > centuries and more centuries, and generations and more generations. > > As far as I know, KDE is included in SLED too. How come KDE doesnt > have those problems of too much focus in SLED? What can we expect of > that? That the gnome in opensuse is barely maintained? Or does that > mean that the KDE guys doesnt put much effort in SLED? I think its fair to say that in the past its been paid less attention than the GNOME in SLED, although I would rate it as higher than "barely maintained". But things like features, polish, maintenance updates, etc have been targeted at SLED not openSUSE for development cycles. All I can say is: if you're a KDE user on openSUSE doesn't affect you much :-). If you're a GNOME use drop by our list or irc channel and help keep us on track just like Alberto did by sending the original mail :-). -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] About dropped packages -- xmms
On Wed, 2007-09-05 at 12:13 +0200, Stephan Binner wrote: > On Wednesday, 5. September 2007 11:07:54 Andras Barna wrote: > > > 3. uses gtk 1. so? gtk1 is in Factory > > But the rather sooner than later plan is to get rid of gtk1 I think. Thats probably a long way off, there are still little dark corners that use gtk1 for custom in house apps, proprietary apps etc. (As opposed to GNOME 1.x we've dropped like a hot potato). -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Bug 305195
On Wed, 2007-09-05 at 11:34 +0200, Frank-Michael Fischer wrote: > Bernhard Walle wrote: > > * Frank-Michael Fischer <[EMAIL PROTECTED]> [2007-08-30 12:44]: > > > >> Is there someone who does not experience this bug with Beta2? If not, I > >> should raise it to "Blocker". > >> > > > > Please don't. As Christoph pointed out in the last status mail, GNOME > > will be updated anyway before openSUSE 10.3 gets released. So, maybe > > > Could, please, someone help me understand, what this comment is supposed > to mean: > > --- /Comment #7 From Mark Gordon <mailto:[EMAIL PROTECTED]> > 2007-09-04 15:42:16 MST / [reply > <https://bugzilla.novell.com/show_bug.cgi?id=305195#add_comment>] --- > > There are many ways to create files in Gnome. This one method is currently > broken. > > Yes, there are many applications by which one is able to create files > despite this bug. But isn't Nautilus supposed to server as THE file > manager in Gnome. Or are there other file managers in Gnome I could use > for creating files? Or is "touch" a Gnome application since one may use > it in the Gnome terminal? This actually touches on a mail written in another thread, we have no uniform severity definitions. In this particular case, there is some weird behavior of create new file when using the context menu in a nautilus menu to create a new file (we were trying to replicate it yesterday, and its not consistent). The rationale for not being critical or blocker, is you can easily create files in general still and even the regular menus work. Its hard to justify raising this above major with such a narrow use case. (BTW, if you have a consistent way to reproduce this, please stick it in the bug). -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: What changed between Build1005 and Build1010 in x86_64?
On Wed, 2007-09-12 at 10:53 +0200, Andreas Jaeger wrote: > To check what has changed, you can check the opensuse-commit list: > http://lists.opensuse.org/opensuse-commit/2007-09/date.html > > It will show you all changes by date. The compiler has not been changed > past Beta3, The other thing is that there was a rev change (from 3 to 4) with no source change. Did we intentionally bump everything before RC1? -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: What changed between Build1005 and Build1010 in x86_64?
On Wed, 2007-09-12 at 15:08 +0200, Andreas Jaeger wrote: > JP Rosevear <[EMAIL PROTECTED]> writes: > > > On Wed, 2007-09-12 at 10:53 +0200, Andreas Jaeger wrote: > >> To check what has changed, you can check the opensuse-commit list: > >> http://lists.opensuse.org/opensuse-commit/2007-09/date.html > >> > >> It will show you all changes by date. The compiler has not been changed > >> past Beta3, > > > > The other thing is that there was a rev change (from 3 to 4) with no > > source change. Did we intentionally bump everything before RC1? > > You mean a change of the build number? We increase it always when we > rebuild and one of the packages it depends on has been changed. > > JP, you were once complaining that after a rebuild the number was not > increased even if it contained different dependencies - now it is really > increased ;-) Yes, I'm glad. I just didn't realize it was now working that way. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] codecs in 10.3?
On Thu, 2007-09-20 at 14:51 +0200, Peter Czanik wrote: > Hello, > Just finished installing RC1 on PPC. I remembered to see something like > 'opensuse-codecs-installer' in changelog, so tried to check, if it means > proper mp3 support in 10.3. > First experience: I installed GNOME for a test. First tried banshee, did > not start. Then totem, but the same. Starting them from the command line > shows an ugly loud crash for both applications. Both start perfectly fine here. We have no bug reports about them crashing on start up. Please file with a trace if you can replicate them. > Second: installed KDE, as I usually do. Opened the mp3 file with > kaffeine. First I got a dialog box, if I want to install a suitable > codec. When answering 'yes', I got two pages opened, one for mp3 and a > second one for xvid. Both of them explained that I wanted to open an > unsupported media file, but nothing more. > Question: what is the status of codec support? Do I see useless pages, > because no content is yet there, or because PPC is not supported? (I > have yet to install on x86) I believe its because the content is not finished there yet. This is what you would go to as part of both GNOME and KDE via gstreamer. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] couldn't launch gnome-settings-daemon after update to RC1
On Sat, 2007-09-22 at 14:08 -0300, Gabriel . wrote: > I managed to update from 10.2 to 10.3 RC1, now, every time I log in a > get an error that the gnome-settings-daemon cannot start. > I attached an screenshot. > > By the way, I noticed that some kde packages was installed, even > though I had installed just gnome (I think there are packages from > kde3base, ksysguard, kconsole, etc) Try running /usr/lib/control-center-2.0/gnome-settings-daemon manually and see what it spits out to the console. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] problem loading OAFIID:GNOME_MixerApplet RC1
On Sat, 2007-09-22 at 19:39 -0300, Gabriel . wrote: > After upgrading to RC1 I got this message 'The panel encountered a > problem while loading "OAFIID:GNOME_MixerApplet".' > > Manually adding the volume control applet to the panel results in the > same error message. Remove the mixer applet from the panel and run "/usr/lib/gnome-panel/mixer_applet2" on the command line. See if there are any errors, if not add the applet to the panel and see if there are any errors there. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] [status report] openSUSE distribution, week 39
On Tue, 2007-09-25 at 12:16 +0200, Stephan Kulow wrote: > * We're down to 0 blockers (two were just FIXED this morning) and 68 critical. > The criticals may result in online updates available at time for the GA. GNOME team has this critical: https://bugzilla.novell.com/show_bug.cgi?id=307290 A fix is submitted in the gnome-utils package, not sure if it should be a blocker or not because it might throw errors on install or upgrade and those can't be fixed after an update (gnome-utils is also a leaf). -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Some 10.3 Bug Statistics
On Sun, 2007-09-30 at 20:58 +0200, Christian Boltz wrote: > 2) I have no real idea why the Gnome bug count increased that much. My >guess (as a KDE user) is a) the move to /usr/bin and b) the major >version upgrade caused some problems. I'd say both of these as well. I'd probably add that I think overall involvement has gone in GNOME for openSUSE 10.3. There are probably at least a half a dozen more big contributors external to Novell (vs 10.2) which I think indicates an overall rise. What would be interesting would be to see how bug counts compare vs counts in Fedora and Ubuntu/Kubuntu. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] poppler 0.6
Hi, I'd like to push poppler 0.6 to factory/STABLE now that 10.3 has branched. Its been in BETA for a while and I can't see any breaks even though ABI built (although BETA seems to have a lot of non-building packages currently). Any objections? -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Evolution attachment icons missing
On Tue, 2007-10-02 at 14:12 -0400, Doctor Who wrote: > The attachment icons are missing for Evolution (openSUSE 10.3 RC1), at > least for IMAP accounts. I've not tested this with POP or other > accounts. https://bugzilla.novell.com/show_bug.cgi?id=308959 -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] kernel CONFIG_PROFILING
My sysprof builds in autobuild started failing with: /usr/src/packages/BUILD/sysprof-1.0.8/obj/debug/sysprof-module.c:45:6: warning: "CONFIG_PROFILING" is not defined /usr/src/packages/BUILD/sysprof-1.0.8/obj/debug/sysprof-module.c:46:3: error: #error Sysprof needs a kernel with profiling support compiled in. I couldn't find anything in the kernel changelog, was this change intentional? -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Re: [opensuse-gnome] Some comment on openSUSE 10.3 and GNOME after a month from release
On Mon, 2007-10-29 at 02:12 +0100, Alberto Passalacqua wrote: > * Using GNOME after the first login/logout is annoying or > impossible because: > > * The launchers in main-menu are slow or not responding at > all (The standard menu is working). > * YaST has similar issues to main-menu. Modules do not > start or start after a long delay since when clicked. > * Logout/shutdown functionalities are not working anymore > and suspend/standby buttons are grayed out. Being worked on in: https://bugzilla.novell.com/show_bug.cgi?id=331577 > * There are lacking dependencies for applets, like the deskbar > (Bug 328912, reported before release) or others, for which a > patch still has to come (python dependency lacks), while the > bug, reported in beta 2, is marked as fixed in bugzilla. The deskbar applet was a mistake made in communicating with the maintenance team. We've been preparing to resubmit the fix so the patch is issued. > * Anjuta is obsolete (Provided version 1.2.4a - Available version > 2.2.2), and the provided version starts up with 3 error > messages. The bug was reported in beta 2 and was fixed in > GNOME:STABLE, upgrading to 2.2.2, but a patch still has to come. Unfortunately a patch will not come as this upgrade involves new packages. > * Evolution crashes when doing common operations like selecting > contacts category (Bug 335546), has issues with Exchange (Bug > 328149, found before release), and lacks of some of the most > published features of GNOME 2.20, as the backup feature (Bug > 331752). I know the evolution team was preparing a set of fixes, they may be able to give a status. > * Gedit is compiled without python support (Bug 299546), while it > has python support on other distributions (read Fedora, to cite > one). Unfortunate side effect of the upgrade to gtksourceview without using the shared library policy: https://bugzilla.novell.com/show_bug.cgi?id=337396 > * Bug-buddy is dumbed down, without the possibility of reporting > bugs (Bug 307860, reported in beta 2). This was fixed in GNOME 2.20.1 upstream, we have begun backporting this for release. > I think bug reporters and testers did their job during the development > stage, the bug slashing weekend and the community contribution to 10.3 > were probably the biggest since the birth of the project. > > As a consequence, I think some more effort to fix at least the most > annoying bugs, some more care in trying patches even with the > cooperation of the community, and a somewhat less restrictive approach > to patch releases (we are at "only security stuff" now) should be really > considered. I agree, but you will need to convince coolo or the board when that starts functioning to change this policy. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Xgl/Compiz 11.0 Notes (DRAFT)
Last week Jigish (cyberorg), Matthias (mhopf), David (davidr) and I
(jpr) all met to discuss next steps for compiz, compiz-fusion and xgl in
openSUSE 11.0. Notes from the meeting follow (AI == action item),
please respond with any questions or comments and especially any
volunteering for some action items:
* xgl/aiglx/nvidia configuration
-aiglx
-already in 10.3
-X team believes aiglx not ready as universal default
-no easy way to turn it on
-closer to 11.0 maybe be better for intel
-don't make it default for now
-AI: add easy way to turn on
-AI: check as we get closer to 11.0 for intel
-nvidia
-AI: use native video support where possible
-xgl
-AI: default for hardware unless otherwise stated
* video/gaming patches
-xine to take advantage of video playback? no.
-AI: document how to do full screen opengl games
-possibly provide script
* multihead
-need xrandr 1.2 in Xgl
-AI: David needs to hack this up soon
* compiz version
-compiz 0.7/0.8 ("compiz 2.0") should be usable by end of year
-compiz-fusion devs already looking at git head changes
-settings tools may need some significant work
-could just port ccsm plugin initially
-AI: ship icompiz 0.8 for 11.0
* making compiz the default
-comparable gui in yast during install to turning 3D acceleration on/off
-AI: make sure "compiz" should launches everything necessary
-AI: talk to KDE team about KDE 4 and kwin compositing
* configuration
-upstream vs. distro simplified
-AI: ship power configuration tool from upstream
-AI: have simple config tool (or tools) for GNOME and KDE if nothing
available upstream
-JP
--
JP Rosevear <[EMAIL PROTECTED]>
Novell, Inc.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Problems with yast2
On Wed, 2007-12-12 at 12:34 +0100, Lukas Ocilka wrote: > Markus Koßmann wrote: > > After updating my factory installation yesterday evening " yast2 > > sw_single" > > fails with: > > 635 Error while creating client module sw_single > > > > y2log shows > > [...] > > 2007-12-11 19:38:23 <1> linux-n04x(5049) [wfm] > > Y2WFMComponent.cc(import):698 > > Y2WFMComponent::import (SlideShow) > > 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] > > clients/sw_single.ycp:21 Loading module 'Language' failed > > 2007-12-11 19:38:23 <3> linux-n04x(5049) [libycp] Import.cc(import):97 No > > matching component found > > 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] > > clients/sw_single.ycp:21 Import 'Language' failed... > > 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] > > clients/sw_single.ycp:21 Could not create its namespace > > 2007-12-11 19:38:23 <3> linux-n04x(5049) [libycp] > > Bytecode.cc(readFile):1161 > > Caught invalid bytecode in '/usr/share/YaST2/modul > > es/SlideShow.ybc' I *think* this is a problem with yast-gtk only atm because of the mod-ui rewrite. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] new live cd 2.5
On Wed, 2007-12-19 at 09:27 +0100, Stephan Kulow wrote: > Am Mittwoch 19 Dezember 2007 schrieb Ted Bullock: > > Ted Bullock wrote: > > > Testing now, I'll post back here in a few minutes. > > > > > > -Ted > > > > Ok, so I tested the latest livecd with my Dell 700m laptop. The system > > booted ok, however it spent ages doing the X11 configuration stuff. > > When GNOME finally started up, the screen had a resolution of 1280x800 > > (screen default) but GNOME only used 1024x768. > > This looks very funny :) > > If you find out, what it is, let me know. It's one more reason though > to not push the live cd out as we only change the problems. Originally > we wanted to have a new round of live cd to fix known problems and now > we get tons of new problems. This is bug https://bugzilla.novell.com/show_bug.cgi?id=310208 It currently seems to only affect intel 945GM. There are test packages in the bug. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Pango Issue In Factory
There is a rather bad pango issue in factory: https://bugzilla.novell.com/show_bug.cgi?id=349940 Please avoid that package or get a working pango package from GNOME:UNSTABLE until factory syncs again. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] 21/12/07, Many unsatisfied deps, when zypper dup.
On Fri, 2007-12-21 at 18:41 +0100, Robert Kaiser wrote: > Markus Koßmann wrote: > > The current dependency problem seems to be that there is a update to > > openldap-2.4 but there are still many packages , which have dependencies on > > libldap-2.3/liblber-2.3 > > Even more fun is that here suddenly the default fonts in all GTK/GNOME > apps stopped working (KDE stuff still works fine). This means that also > all Mozilla-based apps, xchat and others only display sqauers instead of > characters to me. Whatever font this is I have for writing and > displaying mail messages does only show up those squares for spaces and > not for normal characters, so I can write thise message at least. > > I think this is the first time ever since summer or so when I started > using FACTORY that it's completely unusable for my daily operations - > and I so badly would need my computer working today :( See my mail about pango to this list or bug https://bugzilla.novell.com/show_bug.cgi?id=349940 -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Factory-Upgrade impossible due to gnomekeyring.
On Thu, 2008-01-03 at 14:01 +0100, Dirk Mueller wrote: > On Sunday 30 December 2007, M9. wrote: > > > Many pkgs depend on this. > > The most annoying is that not installing totem would be the right > > solution, but it is impossible to apply that proposel... > > Please post error messages, do not interpret them. I was able to do a factory > update just fine. libtasn1 is a new requirement and has not been synced to the external factory tree yet. You can get libtasn1* from GNOME:UNSTABLE as a work around for now. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] a checkin timeout before an Alpha release?
On Tue, 2008-01-15 at 13:50 +0100, Stephan Kulow wrote: > Am Dienstag 15 Januar 2008 schrieb Toni Harbaugh-Blackford: > > Would it be possible to have a 'new version' checkin timeout before > > an alpha release of the Factory? It seams that there are too many new > > checkins that break Factory lately. It would be nice if there were a > > short > > window before an alpha release where only bug fixes were checked in. > > > > I realize that the point of Factory is to keep current with the latest > > software, but a short period of stabilization before a release does not > > sound unreasonable to me > > > There is a short period. Friday is the deadline, the alpha is released > thursday the week after. More of a freeze is unacceptable during alpha > phase. Except that we've had limited testing of factory because of the disk outage. It would be nice to have that back for a day or two before we burn the iso. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] a checkin timeout before an Alpha release?
On Tue, 2008-01-15 at 14:31 +0100, Dirk Mueller wrote: > On Tuesday 15 January 2008, JP Rosevear wrote: > > > > There is a short period. Friday is the deadline, the alpha is released > > > thursday the week after. More of a freeze is unacceptable during alpha > > > phase. > > Except that we've had limited testing of factory because of the disk > > outage. > > Factory was synced out before that. Except its not accessible for update on the opensuse servers, the raid server died in the middle of my update yesterday. > > It would be nice to have that back for a day or two before we > > burn the iso. > > failed_packages gnome-maintainers | wc -l > 43 Thats all packages on all distros, there are many less on factory (17 I think, and not all are distributable either). > I don't think that factory testing is the issue. I don't follow your point, even with packages failing factory helps you test and determine ahead of time how good an alpha would be. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beagle
On Thu, 2008-01-17 at 12:14 +0100, Joachim Reichelt wrote: > Hi, > > can anyone tell me any reson for installing beagle? > All I see is garbage on ~/.beage and endless/uncounted beagled-helper > (we are using nfs) > Just now a system run out of memory only by these uncountable number of > beagled-helper jobs There seem to be some issues with nfs in 10.3 at least, please file a bug. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beagle
On Thu, 2008-01-17 at 12:48 +0100, Igor Jagec wrote: > On Thu, 2008-01-17 at 12:31 +0100, Andreas Vetter wrote: > > > On Thu, 17 Jan 2008, Dominique Leuenberger wrote: > > > I for myself always uninstall it after the setup... bu I learnt to > ... > > I also uninstall it on every machine > > Me too. I use Google Desktop Search because it is more mature tool and > consumes less CPU power. Its also indexes far less last time I checked. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beagle
On Thu, 2008-01-17 at 22:57 +0100, Christian Jäger wrote: > Am Donnerstag, den 17.01.2008, 21:11 + schrieb peter nikolic: > > On Thursday 17 January 2008, Christian Jäger wrote: > > > It is perfectly normal that an indexing tool is especially active when > > > building an initial index. Whoever doesn't have the patience to wait > > Beagle should be an OPTION not a preset thing . > > > > I would think very few people using Opensuse on the desktop either at work > > or > > at home do not need Beagle and prefere a faster more responsive machine to > > one that is faffing around building an unwanted index of some form > > . > Again, I strongly doubt that; few people are properly organized (I'm > not), otherwise Google Desktop wouldn't be the success it is. Before this goes on and on like the opensuse@ thread, I propose that I (being someone interested in the beagle decision and somewhat responsible for its packaging) put together a summary of the issues real/perceived, known bugs and a list of the options. I should be able to do this sometime next week. One note is that there really hasn't been a precedent for discussing distro changes like this in public, its generally been up to "the powers that be" - either the team leads or developers at Novell for various components or coolo/aj to make this decision so this is kind of a change. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beagle
On Thu, 2008-01-17 at 19:26 -0600, Hans Petter Jansson wrote: > On Fri, 2008-01-18 at 01:53 +0100, Igor Jagec wrote: > > On Thu, 2008-01-17 at 14:59 -0500, JP Rosevear wrote: > > > > On Thu, 2008-01-17 at 12:48 +0100, Igor Jagec wrote: > > > > Me too. I use Google Desktop Search because it is more mature tool and > > > > consumes less CPU power. > > > > Its also indexes far less last time I checked. > > > That's nice to hear, thanks! I'll test it on Factory over the weekend. > > I suspect that what JP is saying, is that it indexes far fewer file > formats, not that its indexer runs faster. At least, that's how I read > it. It looks like you read it differently, since your reply is so > positive :) Yes, fewer file formats is what I meant. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] beagle
On Sat, 2008-01-19 at 00:34 +0100, Igor Jagec wrote: > On Fri, 2008-01-18 at 14:43 -0600, Hans Petter Jansson wrote: > > > > BTW I've noticed that it indexes fewer file formats than GDS (which is > > > one of the reasons why I use GDS), but I'll test it on Factory anyway. > > > On my openSUSE 10.3 I'll keep using GDS for now. > > Ok, but I think he meant that GDS indexes fewer file formats than > > Beagle :) > > Whoops... :o) > > I see it's been a very long time since I've played with Beagle last, and > now is right time to test it on my Factory installation :) FYI, 0.3.2 will be available in Factory next week probably. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] libbeagle 0.3.2 is missing in the Factory repo
On Mon, 2008-01-28 at 13:54 +0100, Igor Jagec wrote: > Hi there! > > I've just updated Factory on my test partition and I saw that > libbeagle-0.3.0 is missing, which is probably the reason why I can't > install libbeagle-python-0.3.0-2.i586.rpm. I hope you'll fix that soon > so we can play with the new Beagle! libbeagle follows the shlib policy now, so libbeagle1 replaces plain libbeagle. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] libbeagle 0.3.2 is missing in the Factory repo
On Mon, 2008-01-28 at 17:44 +0100, Igor Jagec wrote: > On Mon, 2008-01-28 at 09:34 -0500, JP Rosevear wrote: > > > > I've just updated Factory on my test partition and I saw that > > > libbeagle-0.3.0 is missing, which is probably the reason why I can't > > > install libbeagle-python-0.3.0-2.i586.rpm. I hope you'll fix that soon > > > so we can play with the new Beagle! > > libbeagle follows the shlib policy now, so libbeagle1 replaces plain > > libbeagle. > > > Ah so... ok, I've just installed it. But it seems that Beagle is not > working on Factory. Here's what I got: > > Every 5.0s: beagle-info --status > > Debug: Done reading conf > from /home/igor/.beagle/config/Daemon.xml > Debug: Done reading conf > from /etc/beagle/config-files/Daemon.xml > Could not connect to the daemon. One of the upstream maintainers poked me yesterday and provided me with a patch that I've submitted to Factory. The patch will be in the 0.3.3 release. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
