… this bug appears to me to be the same as what was observed on openSUSE-11.0 (ie it has not been fixed for KDE-3.5.9 on 11.1 alpha2). The same work around observed to work on openSUSE-11.0 also works on 11.1 alpha2. NTFS - openSUSE - External_HD_hotplug_bug_in_openSUSE_11.0
One has to watch carefully on the first boot, as the default in grub is erroneously set to failsafe, … but one can later go into YaST and change that default to the properly menu selection. There is a bug already noted about this (as one of the more irritating bugs - albeit easy to fix).
I also raised a bug report on the openSUSE installer in a rather minor obscure area, that is likely only to impact more experienced users (and the work arounds are easy). https://bugzilla.novell.com/show_bug.cgi?id=419889
I just finished a 1,500 package update, including linux-unvm 2.6.27-rc4-4-default #1 SMP update and I’m pleased to report that all went very well on my x86-64 KDE4.1 install:)
I obtained a very nice response to my bug report on 11.1 alpha2’s network printing. The response included a nice brief reference on printing and a note as to the 11.1 yast plans for network printing:
The YaST printer module in openSUSE 11.1 is a complete rewrite from scratch. Many thanks for testing it!
What you write about is just not yet implemented so that your report is valid but on the other hand I like to close it as “Fixed in Milestone: Beta3” because in openSUSE 11.1 Beta3 all mandatory functionality would be implemented.
Please be patient and reopen it, if it is not fixed in openSUSE 11.1 Beta3.
In the meantime use e.g. the CUPS web interface http://localhost:631/ to set up a queue for a printer in the network (go to “Administration” and log in as “root”).
What there is currently implemented is only a very basic “placeholder” to have some dialog at all for the workflow.
By the way: To print from a CUPS client system to a queue on a CUPS server, usually you don’t need a queue on the CUPS client system. Use “CUPS Browsing” or set up a “client-only” config, see SDB:CUPS in a Nutshell - openSUSE "Configuring CUPS in the Network "
Re: 11.1 Alpha2, KDE4 install with factory updates.
I have been doing a daily update and yesterday I ran into some problems.
I haven’t filed a bug report as I’m not sure exactly what the problem is – yet.
Starting Yast2 or Smart from the Kmenu will give me the root gui but then they die (no gui).
which could be a “gtk” issue -
I can start them from a terminal & can refresh and download, but, some rpms at install throw a “UI Syntax error” and they freeze.
I can’t open File Manager super user mode to look at my Yast2 logs as it dies too.
When I have time to dig through the command line with an editor, I’ll get back or wait until 11.1Beta1
or
try a factory network install & see what happens (I’ll need a couple of free hours as it’s been my experience that one needs to hang around the computer).
Jim
Edit, back in 11.1alpha2
starting smart in a terminal
“linux-tgfl:/home/jim # smart --gui
(smart:5087): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”
try to install a RPM using smart
“Output from pm-profiler-0.1-6@noarch:
insserv: Script avahi-daemon is broken: incomplete LSB comment.
insserv: missing Required-Stop:' entry: please add even if empty. insserv: Script avahi-dnsconfd is broken: incomplete LSB comment. insserv: missing Required-Stop:’ entry: please add even if empty.
etc, for a page or two”
I see they marked as “resolved” the bug report you raised:
*The kernel makes up those device names and they are not persistent.
That’s why openSUSE uses persistent udev names to identify hard-disks
e.g. in /etc/fstab and boot config. The installer also displays these
persistent udev names.*
Yesterday afternoon, I tried another factory network install from scratch and it again failed; but, this time it was not the UI syntax error stuff – just failed to complete the install
I then went to my 11.1 alpha2 install & 1st updated all Yast2 & kernel packages – went fine, except at reboot I had lost all icons in Yast & do not seem to have the DB shown anymore – that works fine in Smart though.
I bite the bullet and press ahead and update it all – seems to be working fine (although I haven’t tested everything, at least it reboots & the package managers are working)
BTW, the repro servers were “flying” yesterday which made it easy to mess around. There will probably be another couple thousand updates again today – later;)
Wow. Update all. … much much more adventurous than I.
In my case I installed alpha2, … played with it for a few days, and have not rebooted since. I’m waiting now for beta1 (or possibly beta2). I am leaving the country 4 times (with international travel) in the next month, followed by a change of apartments (with all the hastle and home-building setup that surrounds that) - so Linux will be taking a back seat to other activities.
