[Bug 390012] [NEW] [Kubuntu 9.04] Cannot extract audio from CD as ordinary user
Public bug reported: Fresh install of Kubuntu 9.04 with the default user 'emgaron'. "groups" for that user reports: emgaron adm dialout cdrom plugdev lpadmin admin sambashare The machine is a HP Kayak XM600 which has and Adaptec 29160 U160 SCSI controller. Attached to that controller are two U160 HDs and (on the narrow channel) a Plextor PX-40TS SCSI CDROM and a Plextor PX-W1210S CD- RW. When I put an audio CD into the PX-W1210S, I can extract audio files from an audio CD as a normal user without problems. If I do the same using the PX-40TS, K3B just hangs at the first file. A cancel only works if I force the ejection of the CD with "eject /dev/sr1". If I start K3B as root (sudo k3b --cddarip /dev/sr1), the extraction *does* work. Both dev files for the CDROMs seem to have identical permissions: ~$ ls -l /dev/cdrom* lrwxrwxrwx 1 root root 3 2009-06-20 21:40 /dev/cdrom -> sr0 lrwxrwxrwx 1 root root 3 2009-06-20 21:40 /dev/cdrom1 -> sr1 ~$ ls -l /dev/sr[01] brw-rw+ 1 root cdrom 11, 0 2009-06-20 21:40 /dev/sr0 brw-rw+ 1 root cdrom 11, 1 2009-06-20 21:40 /dev/sr1 To be sure, I also installed grip and tried the same thing with grip - with identical results. Extracting audio from sr0 (PX-W1210S) works as ordinary user, whereas the same from sr1 (PX-40TS) only works as root. As the same setup has worked fine earlier under SuSE 9.3 before I installed Kubuntu on it, I think there must be some subtle bug somewhere. Given that it affects both k3b and grip, it does not seem to be related to the app. Hence, I'm not sure which package to assign this to. ** Affects: ubuntu Importance: Undecided Status: New -- [Kubuntu 9.04] Cannot extract audio from CD as ordinary user https://bugs.launchpad.net/bugs/390012 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378706] Re: Jaunty PPC alternate CD fails to create user account
I have seen this happening once on my iMac DV (400MHz G3 slot-loader). The user account was not created, but I was able to create it manually when booting from the "alternate" CD in "rescue" mode. I could then get a shell while using the installed system as / and subsequently use "adduser" to create a user. I also had to use rescue mode to make sure that account was added to the sudoers file. The same install showed the problem with the root account as described above. I found that this was due to the entry for "root" missing completely from /etc/passwd. Adding it manually resolved this. Also, I only ran into this when I installed the machine before I had replaced the PRAM battery (i.e. it was forgetting its date, time and settings each time I booted). After I had replaced the battery, reset the NVRAM and reset the hardware clock (actually using hwclock --systohc), a second fresh install of 9.04 from the alternate CD correctly created both user account and "root" entry. -- Jaunty PPC alternate CD fails to create user account https://bugs.launchpad.net/bugs/378706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] [NEW] 9.04 PPC: X only partially functional
Public bug reported: Binary package hint: xserver-xorg-video-r128 Fresh install on an Apple iMac DV (400MHz slot-loader). Before installing, I have replaced the PRAM battery, reset the NVRAM and made sure that the hardware clock was set correctly and kept correctly across power downs. I then proceeded to install 9.04 from the alternate CD for PPC. The install went fine and after the first boot, gdm came up with the login screen. On closer inspection, however, X was started in PseudoColor 8bit mode - which is very annoying and almost unusable in some cases. Hence, I tried to manually configure X to display 24bit TrueColor or at least 16bit (after having installed all updates). I came across the following issues: 1) The "out-of-the-box" xorg.conf file is empty. I have no experience with 9.04 yet, so I don't know whether it's supposed to be that way. 2) After adding the information from one of the many xorg.conf files that can be found for Ubuntu on PPC (which includes the r128 driver), X failed with "no device found" (see attached Xorg.0.log-r128-no_device). This despite all evidence pointing to this iMac having an ATI Rage 128 (see lspci.txt) 3) I then removed the "Driver" instruction to let X choose the driver itself. This resulted in another failure to run X, this time with an error about "modified mode" (see Xorg.0.log-no_driver-modified_mode). In fact, I got this error for all colour depth settings except for 8bit - which is just what I want to get rid of. I will now proceed and install 8.04 from alternate to see whether the machine will then show different behaviour. The original MacOS 9 installation on that box *did* run in TrueColor mode, so I assume that the hardware is fine. ** Affects: xserver-xorg-video-r128 (Ubuntu) Importance: Undecided Status: New -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "Xorg.0.log-r128-no_device" http://launchpadlibrarian.net/28913893/Xorg.0.log-r128-no_device -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "Xorg.0.log-no_driver-modified_mode" http://launchpadlibrarian.net/28913901/Xorg.0.log-no_driver-modified_mode -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "lspci.txt" http://launchpadlibrarian.net/28913899/lspci.txt -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "xorg.conf-r128" http://launchpadlibrarian.net/28913902/xorg.conf-r128 -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "xorg.conf-no_driver" http://launchpadlibrarian.net/28913910/xorg.conf-no_driver -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
Just finished installing 8.04. As described in http://forums.macrumors.com/archive/index.php/t-662667.html the initial X configuration does not produce a working X, however, with the xorg.conf given on that page X works just fine at 1024x768 with 24bit. So, the hardware is fine - just the xserver/driver in 9.04 seems to have problems. -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Tags added: apple ati imac rage xorg -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22976] Re: Live CD boots to a black screen on Blueberry G3 iMac
I wonder whether in Intrepid this is related to the bug report I filed a few days ago (I could not find this one then): https://bugs.launchpad.net/bugs/398204 . As far as I remember, I have already tried playing with "DefaultFbBpp" to no avail, but I'll re- check, just to be sure. -- Live CD boots to a black screen on Blueberry G3 iMac https://bugs.launchpad.net/bugs/22976 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22976] Re: Live CD boots to a black screen on Blueberry G3 iMac
Ok, I've re-installed 9.04PPC on my iMac and tried this again. "DefaultFbBpp" does *not* work. If I add this statement to the screen section, X fails with this error: (II) FBDEV(0): using default device (II) Running in FRAMEBUFFER Mode (--) FBDEV(0): Depth 24, (**) framebuffer bpp 32 (==) FBDEV(0): RGB weight 888 (==) FBDEV(0): Default visual is TrueColor (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) (II) FBDEV(0): hardware: OFfb ATY,Rage12 (video memory: 600kB) (II) FBDEV(0): checking modes against framebuffer device... (II) FBDEV(0): mode "1024x768" test failed (II) FBDEV(0): mode "800x600" test failed (II) FBDEV(0): mode "640x480" test failed (II) FBDEV(0): checking modes against monitor... (--) FBDEV(0): Virtual size is 800x600 (pitch 800) (**) FBDEV(0): Built-in mode "current": 100.0 MHz, 119.0 kHz, 186.0 Hz (II) FBDEV(0): Modeline "current"x0.0 100.00 800 816 824 840 600 616 624 640 -hsy nc -vsync -csync (119.0 kHz) (==) FBDEV(0): DPI set to (96, 96) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.4 (**) FBDEV(0): using shadow framebuffer (II) Loading sub module "shadow" (II) LoadModule: "shadow" (II) Loading /usr/lib/xorg/modules//libshadow.so (II) Module shadow: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.1.0 ABI class: X.Org ANSI C Emulation, version 0.4 (==) Depth 24 pixmap format is 32 bpp (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode (EE) FBDEV(0): mode initialization failed -- Live CD boots to a black screen on Blueberry G3 iMac https://bugs.launchpad.net/bugs/22976 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Result of running strace against startx ** Attachment added: "X.strace" http://launchpadlibrarian.net/29203121/X.strace -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] [NEW] 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Public bug reported: Binary package hint: xserver-xorg-video-r128 Ubuntu 9.04PPC "out-of-the-box" fresh install on an iMac DV 400MHz (G3, slot-loader): As the default installation results in 8bit only display (256 colours, PseudoColor mode), I have tried to force the usage of the r128 driver using a minimal xorg.conf (see attachments). This fails, as the r128 driver fails to detect the card (see attached Xorg.0.log). I could not see any difference between including the "disable 'dri'" statement and leaving it out - in the log, it looks like this statement is actually ignored/overridden by the X server. If I run strace against "startx" (strace -fo xserver.trace startx), I can see that the driver accesses the AGP bus and both PCI busses (see also attached output of "lspci -vvnn"). Under 8.04, the same driver works fine on the same hardware. Note: This bugreport supersedes https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-r128/+bug/398204 ! ** Affects: xserver-xorg-video-r128 (Ubuntu) Importance: Undecided Status: New ** Tags: apple ati imac ppc rage xorg -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/29203060/xorg.conf -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Logfile when trying to start X with r128 driver ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/29203097/Xorg.0.log -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Output of lspci -vvnn ** Attachment added: "lspci_vvnn.txt" http://launchpadlibrarian.net/29203133/lspci_vvnn.txt -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] Re: 9.04 PPC: fbdev wrongly configured in X
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/29203657/xorg.conf -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] Re: 9.04 PPC: fbdev wrongly configured in X
Logfile with error message ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/29203660/Xorg.0.log -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] Re: 9.04 PPC: fbdev wrongly configured in X
fbset output ** Attachment added: "fbset_iv.txt" http://launchpadlibrarian.net/29203666/fbset_iv.txt -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] [NEW] 9.04 PPC: fbdev wrongly configured in X
Public bug reported: Binary package hint: xserver-xorg-video-fbdev Ubuntu 9.04PPC "out-of-the-box" fresh install on an iMac DV 400MHz (G3, slot-loader): After the install, xorg.conf stays empty. Hence, X tries to figure out the correct settings and driver automatically. On my iMac, X fails to detect the built-in ATI Rage 128 card (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-r128/+bug/400864 ) and subsequently tries to use the fbdev driver. When doing so, X does start, however, only 256 colours are used (8bit PseudoColor mode). I tried to investigate the cause for this and tried several things: 1) Create a minimal xorg.conf (the attached version contains some commented out lines from experimenting) with "DefaultDepth 24" in the Screen section. This results in an error message "FBIOPUT_VSCREENINFO succeeded but modified mode" (see attached Xorg.0.log). 2) I tried the same thing using "DefaultFbBpp 32" instead of "DefaultDepth 24". The result was the same. 3) I noticed in the log file that apparently the modes are checked against the fbdev set-up. The default frame-buffer set-up as listed by "fbset -i -v" is attached as well. It can be seen from this output and Xorg.0.log that the frame buffer seems to have 8bit only and only some 600KB of video memory. Hence, I tried modifying these settings with fbset - to no avail. I also tried adding a "VideoRam" statement to xorg.conf - also to no avail. I was not able to change any settings. In the end, I am still not able to run anything but 8bit graphics using the fbdev driver. My impression is that this is due to the frame buffer being in the wrong mode itself, but this seemingly cannot be changed easily. The same hardware works fine with 24bit under 8.04, using the r128 driver. ** Affects: xserver-xorg-video-fbdev (Ubuntu) Importance: Undecided Status: New ** Tags: apple ati fbdev imac ppc rage xorg -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
On closer inspection, I noticed that this bug report touches separate, most likely independent issues (X with fbdev vs. X with r128 driver). Hence, I decided to replace this bug report with separate ones to make it easier to focus on one single issue: 1) r128 does not detect ATI Rage 128 on G3 iMac: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/400864 2) fbdev wrongly configured in X : https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/400875 This bug report is therefore obsolete. I shall try to close it myself - if that fails, please close it for me. -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
This bug report has been superseeded by https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/400864 and https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/400875 ** Changed in: xserver-xorg-video-r128 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-r128 (Ubuntu) Assignee: (unassigned) => Thomas Ribbrock (emgaron+ubuntu) -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] Re: 9.04 PPC: fbdev wrongly configured in X
For completeness: dmesg ** Attachment added: "dmesg" http://launchpadlibrarian.net/29204401/dmesg -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
For completeness: dmesg ** Attachment added: "dmesg" http://launchpadlibrarian.net/29204400/dmesg -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Partial SOLUTION: xorg.conf must contain the line BusID "PCI:0:16:0" in the "Device" section - this will detect the ATI Rage. I had not tried this as I assumed that the lspci (hex-)value should be correct, but apparently, xorg expects decimal. Hence, the installer needs to somehow come up with this. Unfortunately, the r128 driver now crashes. I will open a new bug for *that* problem. -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 289422] Re: 8.10: Application to override monitor selection missing
*** This bug is a duplicate of bug 211364 *** https://bugs.launchpad.net/bugs/211364 This bug is not a duplicate of #211364 - that report is specifically written with regard to Kubuntu/KDE, whereas this report is true for both Kubuntu *and* Ubuntu, Gnome and KDE. -- 8.10: Application to override monitor selection missing https://bugs.launchpad.net/bugs/289422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 289422] Re: 8.10: Application to override monitor selection missing
>From my original bug report (see above): "In Kubuntu 8.04, it was possible to hard-set/override the monitor selection via System Settings -> Display. Under Kubuntu 8.10RC, this setting is no longer present (same goes for Ubuntu 8.10RC, by the way). Apparently, there is no way to set what monitor you are using." I *am* talking about "System settings" -> "General" -> "Display" (as far as Kubuntu is concerned - as I said, Ubuntu 8.10 has the same problem). In Kubuntu 8.04, this same utility was still called "Monitor & Display" and had a "Hardware" tab in which you could manually select the monitor you have. In 8.10 and 9.04, this option has been removed and as far as I can see nothing has been provided to replace it. This means that in these versions, the user does not have the option to override the *definition* of the monitor. If the system recognises my monitor as "800x600" (or does not recognise it at all), "800x600" is all I get - contrary to 8.04, I cannot override this and tell the system "but my monitor REALLY *can* do 1600x1200!" The only way to do so is to manually edit xorg.conf, which is something I did not have to do in *years* with any distribution - and also something which cannot be expected of a novice user who happens to have an older monitor or is using a KVM-switch that fails to propagate the DDC signals properly. The latter is precisely what I have at home and at work: With some KVM, autodetection works, with others, it does not - and if it does not, neither Kubuntu (8.10 and 9.04) nor Ubuntu 8.10 (have not tested 9.04 yet) offer me the option to manually define my monitor using a proper GUI. Other systems (tested: Opensuse 11, Kubuntu 8.04 and Ubuntu 8.04) do. In my eyes, this is a usability regression in comparison with 8.04 and therefore a bug. ** Summary changed: - 8.10: Application to override monitor selection missing + 8.10/9.04: Application to override monitor selection missing -- 8.10/9.04: Application to override monitor selection missing https://bugs.launchpad.net/bugs/289422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384967] [NEW] Kubuntu 9.04: Sound only partially working on HP Kayak XM600
Public bug reported:
On my HP Kayak XM600, sound is only working partially after having
installed Kubuntu 9.04. So far, I have seen two scenarios:
Upgrade from Kubuntu 8.10 (where sound - I think - was working. Not 100% sure)
to 9.04:
- No system sounds (i.e. no sound for Login/Logout, error messages, beep,
etc.). When going to System Settings -> Notifications -> KDE System
Notifications and tried to play any of the sounds there, nothing happened.
- No sound in amarok
- Something like "ogg123 FILE.ogg" did work (so the hardware is ok)
- The mixer in KMix was correctly shown, no odd settings there
- System Settings -> Multimedia showed "Sound Fusion CS46xx (CS46xx)" at the
top of the list. Clicking on "Test" did result in a sound being played. The
other two entries ("Sound Fusion CS46xx (CS46xx - Rear)" and "PulseAudio" did
not do anything).
- I tried installing the phonon-gstreamer backend and use that instead of the
xine-backend, but that did not change anything.
As I could not get sound to work, I decided to wipe that machine
completely and perform a fresh install of Kubuntu 9.04 (including fresh
user account). After that, sound still was not working - no system
sounds, no sound in amarok, but the mixer was still ok and "ogg123 ..."
still worked. Basically the same as after the upgrade.
Based on some comments in the forums, I installed the "pulseaudio"
package (which did not get installed automatically). I then went to
System Settings -> Multimedia and put the "PulseAudio" entry to the top.
To be sure, I logged out and even rebooted. After I log in, I still do
not get any system sounds, however, amarok seems to be able to play now.
The sounds in System Settings -> Notifications -> KDE System
Notifications behave very oddly: If I press the play button, nothing
happens. If I press it again, the sound is played once. If I continue,
every second button press will result in the sound being played. If I
press the button in rapid succession, the sounds get played several
times simultaneously. The latter does not surprise me that much, but the
fact that I have to click twice to get any reaction seems odd. In normal
use, the system sounds/notification still don't work.
ProblemType: Bug
Architecture: i386
ArecordDevices:
E: core-util.c: Home directory /home/emgaron not ours.
List of CAPTURE Hardware Devices
card 0: CS46xx [Sound Fusion CS46xx], device 0: CS46xx [CS46xx]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: emgaron3111 F knotify4
emgaron3201 F pulseaudio
emgaron3207 F kmix
Card0.Amixer.info:
Card hw:0 'CS46xx'/'Sound Fusion CS46xx at 0xe920/0xe900, irq 17'
Mixer name : 'Cirrus Logic CS4297A rev 4'
Components : 'AC97a:43525914'
Controls : 45
Simple ctrls : 26
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: alsa-base 1.0.18.dfsg-1ubuntu8
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Uname: Linux 2.6.28-11-generic i686
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
Kubuntu 9.04: Sound only partially working on HP Kayak XM600
https://bugs.launchpad.net/bugs/384967
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384967] Re: Kubuntu 9.04: Sound only partially working on HP Kayak XM600
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/27664941/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/27664944/AplayDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/27664945/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/27664947/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/27664949/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/27664951/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/27664953/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27664954/Dependencies.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/27664956/PciMultimedia.txt -- Kubuntu 9.04: Sound only partially working on HP Kayak XM600 https://bugs.launchpad.net/bugs/384967 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46516] Re: NFSv4 mounts often missing after boot
I just wanted to add that I have this exact same problem with NFSv3 mounts on Feisty. *None* of the mounts listed in /etc/fstab get mounted during boot - I had to add additional mount commands to /etc/rc.local to get them mounted. Example line from /etc/fstab: 192.168.1.1:/export/src /usr/local/src nfs nouser,wsize=8192,rsize=8192,atime,auto,rw,nodev,noexec,suid 0 0 This share will not get mounted during boot. It will, however, get mounted by the following command in rc.local: mount /usr/local/src which means that the fstab entry *as such* works. The client is Kubuntu 7.04 'Feisty' AMD64 (nfs-common is installed and all updates are applied) and the server runs OpenBSD 3.8 on Sparc64. I've been using the same server set-up (OpenBSD on Sparc) for years now with varying Linux clients (Red Hat, Fedora, Mandrake, SuSE, Aurora) and never had any issues, so I tend to assume that the server is ok... :-) -- NFSv4 mounts often missing after boot https://bugs.launchpad.net/bugs/46516 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 245417] [NEW] Make subject of status mail configurable
Public bug reported: unattended-upgrades has a nice feature which sends a status report via mail to a configurable address. That's great if you have several workstations running Ubuntu and want to keep track of things. However, the subject of these mails is fixed, making it difficult to determine which workstation has sent the mail. Hence my suggestion: If you get a chance, please make the subject configurable - that way, each workstation can use a unique subject (e.g. with the hostname in it), making it a lot easier to scan through a list of status messages. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- Make subject of status mail configurable https://bugs.launchpad.net/bugs/245417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 245422] [NEW] Make log/status mail contain info about "kept back" packages
Public bug reported: Binary package hint: unattended-upgrades In some cases, unattended-upgrades will not execute all available upgrades (e.g. if apt holds back a package due to some other package needing to be installed additionally). Unfortunately, neither the *.log files nor the status mail of unattended-upgrades contains any information about this - you have to log in on the workstation in question and run "apt-get upgrade" manually to get this information. It would be great if unattended-upgrades could supply this information itself (especially in the mail) - that way keeping an eye on what's going on is a lot easier for an admin with several of these workstations. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- Make log/status mail contain info about "kept back" packages https://bugs.launchpad.net/bugs/245422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252319] [NEW] gcompris installation only partially functional on Kubuntu
Public bug reported: Binary package hint: gcompris Fresh install of Kubuntu 8.04 with all updates applied: I have installed gcompris-8.4.4-1.1ubuntu1 which pulled in the corresponding gcompris-data package. As I wanted to have the sound as well, I've installed gcompris-sound-de, gcompris-sound-en and gcompris- sound-nl as well. The first thing I noticed was that gcompris would insist on using English written text, even when switched to Dutch or German. I then proceeded to install language-support-de, -nl and -en (8.04+20080214), which did not resolve this problem. After some investigation, I found that the corresponding "gcompris.mo" files are not part of the gcompris package, nor are they part of the language packages I installed - they are actually part of the "language-pack- gnome-XX" packages - but these do not get installed automatically on a Kubuntu system. I think this should be fixed, as not having the gcompris.mo files installed severely hampers the usability on a non- English (or multilinugal) system. Secondly, even after installing all that I found that (at least) one of the reading games still does not work: "Reading Activities" -> "Click on a letter" - no sound is produced for the letters the user is supposed to click on, making this game unusable (tried in German and Dutch so far). ** Affects: gcompris (Ubuntu) Importance: Undecided Status: New -- gcompris installation only partially functional on Kubuntu https://bugs.launchpad.net/bugs/252319 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252319] Re: gcompris installation only partially functional on Kubuntu
Additional info:
"Click on a letter" does not work for English (UK), either. I ran strace on
gcompris while trying this and found that gcompris does indeed find the correct
ogg vorbis file for the welcome message of the game
("/usr/share/gcompris/boards/voices/en/misc/click_on_letter.ogg") and the first
letter (in this case it was
"/usr/share/gcompris/boards/voices/en/alphabet/U0061.ogg"), but for some odd
reasons, the sound is not played.
Playing those files with ogg123 from the command line does work fine.
I also just discovered that while the background music and the initial
"Welcome" do work, none of the other sound effects seem to work. For
example, "Discovery activities" -> "Sound activities" -> "Melody" and
"Discovery activities" -> "Memory activities" -> "Railway" do not work,
either. However, "Discovery activities" -> "Memory activities" -> "Audio
memory game" works.
--
gcompris installation only partially functional on Kubuntu
https://bugs.launchpad.net/bugs/252319
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252319] gcompris problems with locale and sound on Kubuntu
SOLUTION: Some googling gave me the idea that some gstreamer plugins might be needed. I discovered that "gstreamer0.10-plugins-good" is sufficient - all games described above are now working. Hence, the whole issue comes down to dependency/packaging problems: - Under Kubuntu, either gcompris needs to pull in the necessary "language-pack-gnome-XX" or the "gcompris.mo" files need to be packaged differently. Otherwise, the locales do not work in gcompris. - Either gcompris or the "gcompris-sound-XX" packages need to pull in "gstreamer0.10-plugins-good". Otherwise, sound will not work for all games in gcompris. I will change the subject to make this more easily findable. -- gcompris installation only partially functional on Kubuntu https://bugs.launchpad.net/bugs/252319 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Case (1) seems to chime with what I mentioned in comment #53 ( https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/138691/comments/53 ) about having the dbus shutdown script (K20dbus) in rc0.d as well. However, I did not verify at the time whether that has any ill side effects. Case (2) is apparently what we experienced here. We do not have any VPN involved, but we do have NFS. The one thing I noticed: At home, I have an OpenBSD NFS server and currently (among others...) one Kubuntu 8.04 and one Kubuntu 7.10 workstation hanging off it, with several directories mounted statically (i.e. via fstab) from the NFS server. Neither of those shows the problems we observed at work. My guess is that it is not simply NFS, but in some way also the NIS+automounter set-up we have here. Also, umountnfs did not time out in our set-up - at least not within 24h (I tried...) -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232160] Re: OpenOffice.org automatic detection of file lock requirement does not work - WITH SOLUTION
I tested the new package yesterday with FILE_LOCKING set to "auto" in /etc/openoffice/soffice.sh - and now it is indeed working as expected on our NFS directories. Thank you! -- OpenOffice.org automatic detection of file lock requirement does not work - WITH SOLUTION https://bugs.launchpad.net/bugs/232160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
"reboot=b" didn't make any change on "Machine 3" (Asus M2A-VM). I did, however, find a few more things on both desktop machines (as the laptop is still on 7.10, I'll focus on the two 8.04 machines): - Adding some extra wait time in /etc/init.d/kdm after stopping kdm and before calling usplash_down did not make any change - If I use "shutdown -P now" remotely (i.e. via a ssh session as root (root account *is* enabled)), the machines seems to shut down properly all the time - If I use "sudo shutdown -P now" from a Konsole, the machine hangs on shutdown as described - If I do an "su -" first in Konsole to become 'root', a subsequent "shutdown -P now" will successfully shut down the machine - When the machine hangs, I can actually use "Ctrl-Alt-Del" to get the shutdown process to continue. The first message I see then is "Main rc0 process killed". Also, I get a message about "shutting down kdm... ...kdm is not running". However, in this case, the machine will not shut down all the way, instead, I end up with a black screen with a white blinking cursor in the top left corner. For completeness, as X seems to play some kind of role: - "Machine 2" (Asus P5L-1394) has an nVidia 7300LE VGA card - "Machine 3" (Asus M2A-VM) has an ATI Radeon RS690/Radeon X1200 Series VGA card (onboard) -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Another piece for the puzzle: Apparently, if I shut down all network related services (NIS, NTP, NFS/automounter) prior to initiating shutdown from within KDE, the machines are much more likely to successfully shut down. No idea why. -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
A long row of boot/shut-down cycles with varying parameters got me a bit closer to the solution: All the machines we use have static NFS mounts for some additional directories in /usr/local plus automounted home directories (also via NFS). I haven't experimented with the home directories yet (all tests were run using a local user), but I discovered this: If I manually unmount the static NFS mounts prior to shutting down, the shutdown will succeed. Further investigation showed that the shutdown actually hangs in umountnfs.sh (/etc/rc0.d/S31umountnfs.sh) right at the "umount" command. Hence, something has happened previously during the shutdown process that prevents the "umount" from succeeding. I went even further and added a custom script to /etc/rc0.d to investigate at which point "umount" would fail to work. Unmounting of the static NFS shares worked fine until after sendsignals (/etc/rc0.d/S20sendsignals) has been run, i.e. I can add a script at S19 or any of the K... levels that unmounts the NFS shares and it will succeed. If I add it as S21... or higher, it will hang at "umount", just like the umountnfs.sh script does. It looks like "sendsignals" kills something that is vital to unmounting the NFS shares (NetworkManager?!). However, this does not explain why there is a difference between initiating shutdown from within KDE/kdm and running "shutdown -P now" from the console. For that, I have no idea whatsoever... Now that I can design a workaround for this, I will have a look at the automounted directories... -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown - WORKING "WORKAROUND"
SOLVED! Finally, I got the whole thing working. In the end, the solution was simple: Disable/remove NetworkManager! Boot times actually seem shorter and shutdown works. NIS now comes right up (as opposed to with a delay with NetworkManager operating). To disable NetworkManager without removing it, do the following: 1) Make CERTAIN that your standard network interface is configured properly in /etc/network/interfaces. "systemsettings" was no help in doing so - I had to edit the file manually. In my case, there already was an entry for "eth0" - I just needed to add/uncomment the actual configuration. The complete entry looks like this: # The primary network interface auto eth0 iface eth0 inet dhcp Once this is done, the interface will be enabled during boot-up, despite NetworkManager being disabled. 2) Disable NetworkManager Create two files in /etc/default: echo "exit" > /etc/default/NetworkManager echo "exit" > /etc/default/NetworkManagerDispatcher 3) Reboot If everything went well, you should now have a working, NetworkManager- free network interface. DOWNSIDES: There are probably some potential downsides to disabling NetworkManager, especially if you want your machine to automatically switch between e.g. ethernet and wireless - as far as I understand that's precisely what NetworkManager was invented for. Hence, this situation does need "real" fixing at some point. However, if you have a workstation with a static network interface (in our case, even the laptops are used that way), there's no need for such functionality - just getting the interface up at boot time is sufficient. Another downside is that the knetworkmanager icon does no longer work to indicate the status of the network connection. "knetstats" seems to do the job nicely, however. As we don't need NetworkManager's functionality, there might be potential downsides that I have missed - YMMV, as always. To the developers: If you need some additional input to try and debug the underlying NetworkManager problem, please let me know and I'll rig up a box that uses NetworkManager to test. -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Well, one thing I found very valuable when debugging my version of this problem (apparently, there are several causes resulting in the same or at least very similar behaviour) is this: In /etc/default/rcS, make sure that "VERBOSE" is set to "yes" (default is no). That way, some of the scripts in /etc/init.d will be, well. more verbose - only after making this change did I doscover that the shutdown did *not* hang at "Sending...KILL... processes" (which comes from /etc/init.d/sendsignals), but rather later in /etc/init.d/unmountnfs.sh. Unfortunately, there are several scripts running after 'sendsignals' that do not print any output to the screen, unless VERBOSE is yes. In the end, I even added 'echo' statements to some scripts in /etc/init.d just to find out where *exactly* the shutdown hung. I would like to suggest that everybody who experiences this kind of problem tries to look into this - the more precise we can pinpoint the exact location where the shutdown process hangs, the greater the chance that the developers can actually solve this. To the developers: I forgot to mention that - just before removing NetworkManger - I also found a way to get rid of its error messages at shutdown without removing it.I copied "K20dbus" from /etc/rc1.d to /etc/rc0.d, figuring that if dbus needed shutdown for single user, it would also need shutdown for shutdown... After that modification, NetworkManager did no longer spew that bunch of warnings and error messages that the original poster described. It did, however, not solve the problem with the hang. Of course, I'm used to a fully blown Sys V compatible runlevel mechanism (as used e.g. by Red Hat, SuSE, Mandrake) rather than what (K)ubuntu does, so I might well have overlooked something here. -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220504] Re: Firefox doesn't know what apps to use to open any type of downloaded files
I can confirm that installing firefox-gnome-support did fill firefox' application list here as well. I find this very odd as I run Kubuntu 8.04 and hence to not quite expect to have to install something wiht "gnome" in its title just to make another progam work. However, while the application list is now populated, it has no effect whatsoever - firefox still does not let me see PDF files and - even worse - will crash if I try several times. -- Firefox doesn't know what apps to use to open any type of downloaded files https://bugs.launchpad.net/bugs/220504 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232160] [NEW] OpenOffice.org automatic detection of file lock requirement does not work - WITH SOLUTION
Public bug reported: Binary package hint: openoffice.org When switching from SuSE 10.0/OpenOffice 2.0 to Kubuntu 8.04/OpenOffice 2.4 I noticed that file locking no longer worked - two users were able to open the same document at the same time and save changes, with the last save winning. As this is a very undesirable situation I went to investigate. I found that (K)Ubuntu uses custom scripts to start OpenOffice and that these scripts contain some code to automatically determine whether $HOME or the edited file is located on a NFS (or Samba) share depending on the setting of FILE_LOCKING in /etc/openoffice/soffice.sh. FILE_LOCKING defaults to "auto' so the auto detection code is used. Unfortunately, this code does not work - file locking is never enabled, despite the fact that we use NFS-mounted home directories. Having a closer look at /usr/lib/openoffice/program/soffice revealed the problematic part: [...current version of the script...] if [ -z "$SAL_ENABLE_FILE_LOCKING" ]; then case "$FILE_LOCKING" in auto) if ! file_or_home_on_nfs "$@"; then # file locking now enabled by default SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING fi [...] The second if statement is never evaluated successfully, no matter what "file_or_home_on_nfs" returns. Hence, SAL_ENABLE_FILE_LOCKING is never set and thus file locking never enabled. I've modified the code as follows: [...WORKING version...] if [ -z "$SAL_ENABLE_FILE_LOCKING" ]; then case "$FILE_LOCKING" in auto) file_or_home_on_nfs "$@" if [ $? -eq 0 ]; then # file locking now enabled by default SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING fi [...] This version works and correctly sets SAL_ENABLE_FILE_LOCKING to "1". This is most likely not the most elegant variant, but at least it works. I have noticed that there are more if statements like this in the same file (e.g. "if ! working_opengl_support; then" a bit further on) and I have not checked the other scripts in that directory, so there might be similar bugs waiting... WORKAROUND: For those who need file locking to be working before the developers have released a fix: Set FILE_LOCKING to "yes" in /etc/openoffice/soffice.sh to force file locking on all the time (on all types of file systems). Version Information: > lsb_release -rd Description:Ubuntu 8.04 Release:8.04 > apt-cache policy openoffice.org openoffice.org: Installed: 1:2.4.0-3ubuntu6 Candidate: 1:2.4.0-3ubuntu6 Version table: *** 1:2.4.0-3ubuntu6 0 ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New -- OpenOffice.org automatic detection of file lock requirement does not work - WITH SOLUTION https://bugs.launchpad.net/bugs/232160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
We currently have three machines at work that show this behaviour: On shutdown, the system will hang with output resembling what the original poster described in his bug report (Netmanager lines etc.). Every now and then, this output is followed by "Sending all processes the KILL signal", but none of the machines will shut down any further. This is the single-biggest showstopper that prevents us from rolling out (K)ubuntu at the moment. What I have been able to gather so far is this: Machine 1: An Acer TM8104WLMib Laptop with Kubuntu 7.10 i386 installed from the alternate disk, with all updates. I tried adding "acpi=off" to the boot options, but that results in the network interfaces not being recognised and didn't seem to help anyway. This machine *will* shut down if I choose "console login" (hence shutting down X first) and the issue "shutdown -h now" from the command line. Machine 2: Desktop with Asus P5L-1394 motherboard and an Intel PD925. Kubuntu 8.04 i386 without any updates, installed automatically via preseeded network-install, using the alternate CD as starting point, but with a complete mirror (via apt-mirror) of "dists" and "pool". Originally, this machine had Kubuntu 7.10 and needed to be installed using a second NIC, as the onboard NIC (Attansic L1) was not recognised by the install kernel. In that case, the shutdown problem vanished when I removed the second NIC. It returned, however, when I installed 8.04 using the onboard NIC only (fortunately, 8.04's install kernel *does* support the chipset). Machine 3: Desktop with Asus M2A-VM motherboard and an AMD Athlon X2. Kubuntu 8.04 i386 installed automatically via preseeded network-install, using the alternate CD as starting point, but with a complete mirror (via apt-mirror) of "dists" and "pool" (like machine 2). All updates including the latest "proposed" ones are installed (to check what was said by Adolfo above). Still having the shutdown problem. I tried adding "irqpoll apci=off" to the boot options, but that did not change anything. Again, if I choose "console login" and press Ctrl-Alt-Delete, the machine will shut down properly, though not power off. Using "normal" shutdown it hangs in the manner described above. I have also tried to boot this machine with the Kubuntu 8.04 i386 Desktop Live CD and in that case, the machine *will* shut down properly (after having displayed the "Remove CD" message) -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
I have done some more experimenting with "Machine 3" from my previous message. Results: - If I boot the machine, the press Ctrl-Alt-Del at the login screen (i.e. without logging in) and choose shutdown, the machine *will* shut down properly - If I boot the machine and log in, then choose "Turn off" via the KDE Menu, the machine will hang as described - If I remove "quiet splash" from the boot options, the machine *will* shut down properly, even if I do log in. I can still see the Networkmanager/dbus error messages described above during the shutdown process, though. Given these results, my guess is that X does also play a part in this - rather annoying - bug... -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Looks like I spoke too soon - apparently, removing "quest splash" does not always help. The machine just hung again, despite this change. Maybe some race condition? -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 289422] [NEW] 8.10: Application to override monitor selection missing
Public bug reported: In Kubuntu 8.04, it was possible to hard-set/override the monitor selection via System Settings -> Display. Under Kubuntu 8.10RC, this setting is no longer present (same goes for Ubuntu 8.10RC, by the way). Apparently, there is no way to set what monitor you are using. Given that this severely hampers the usability of (K)Ubuntu, I regard this as a bug. There are many situations where the autodetection does not work - older monitors, for example, or - more often - the use of KVMs. At work, all our machines hang off KVMs and for many machines we were forced to hard- set the monitor selection (Kubuntu 8.04), as autodetection fails when the KVM is switched to "the other PC". At home, I face the same problem: I just installed Ubuntu 8.10RC - and was not able to get anything but 800x600, as I cannot tell Ubuntu what monitor I'm using... Again, the machine is connected via a KVM. In these cases, you *have* to be able to configure the monitor yourself. I am aware that I could change xorg.conf directly, but having to do so is *very* disappointing for a distribution like (K)Ubuntu and will pose a problem for less experienced users. ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - 8,10: Application to override monitor selection missing + 8.10: Application to override monitor selection missing -- 8.10: Application to override monitor selection missing https://bugs.launchpad.net/bugs/289422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270838] [NEW] KDE System Settings: Several config windows too big to be usable
Public bug reported: Binary package hint: kde-systemsettings Several of the configuration dialogues that can be accessed via "System Settings" are far too big and do not scale when the window is resized. One of the worst offenders is "Regional & Language" - this screen is so big, that it does not even display fullscreen on 1280x1024 without having to use scrollbars, which makes using this configuration screen very cumbersome. Most of the other configuration screens require fullscreen on 1280x1024 just to avoid scrollbars. None of the screens seem to scale properly when resizing the window. Strangely enough, as far as I can see, the *same* screens scale perfectly when used with the original "kcontrol" (KDE Control Centre) command. "Regional & Accessibility" for example works just fine in a *much* smaller window - no scrollbars necessary. Unfortunately, kcontrol does not seem to be part of the default menu. lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 apt-cache policy kde-systemsettings kde-systemsettings: Installed: 0.0svn20070312-0ubuntu5 ** Affects: kde-systemsettings (Ubuntu) Importance: Undecided Status: New -- KDE System Settings: Several config windows too big to be usable https://bugs.launchpad.net/bugs/270838 You received this bug notification because you are a member of Almost Kubuntu Bugs, which is subscribed to kde-systemsettings in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 54454] Re: ubuntu/gnome printing system is not able to print on more than 1 page in some cases
I can confirm this bug for Kubuntu 8.04.1 and firefox-3.0 (3.0.1+build1 +nobinonly-0ubuntu0.8.04.3). In all cases, the print preview only shows one page and no matter whether I print to file or to an actual printer, I only get one page. >From what I can see so far, this problem is most likely to occur if the webpage in question uses frames. Two examples: http://www.marktplaats.nl/ http://www.hyperelliptic.org/tanja/conf/ECC08/ Pages without frames seem to work a lot better for printing. You *can* work around it sometimes by selecting "Each frame on separate pages" in the Options tab of the print dialogue, but it's still very annoying. -- ubuntu/gnome printing system is not able to print on more than 1 page in some cases https://bugs.launchpad.net/bugs/54454 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384967] [NEW] Kubuntu 9.04: Sound only partially working on HP Kayak XM600
Public bug reported:
On my HP Kayak XM600, sound is only working partially after having
installed Kubuntu 9.04. So far, I have seen two scenarios:
Upgrade from Kubuntu 8.10 (where sound - I think - was working. Not 100% sure)
to 9.04:
- No system sounds (i.e. no sound for Login/Logout, error messages, beep,
etc.). When going to System Settings -> Notifications -> KDE System
Notifications and tried to play any of the sounds there, nothing happened.
- No sound in amarok
- Something like "ogg123 FILE.ogg" did work (so the hardware is ok)
- The mixer in KMix was correctly shown, no odd settings there
- System Settings -> Multimedia showed "Sound Fusion CS46xx (CS46xx)" at the
top of the list. Clicking on "Test" did result in a sound being played. The
other two entries ("Sound Fusion CS46xx (CS46xx - Rear)" and "PulseAudio" did
not do anything).
- I tried installing the phonon-gstreamer backend and use that instead of the
xine-backend, but that did not change anything.
As I could not get sound to work, I decided to wipe that machine
completely and perform a fresh install of Kubuntu 9.04 (including fresh
user account). After that, sound still was not working - no system
sounds, no sound in amarok, but the mixer was still ok and "ogg123 ..."
still worked. Basically the same as after the upgrade.
Based on some comments in the forums, I installed the "pulseaudio"
package (which did not get installed automatically). I then went to
System Settings -> Multimedia and put the "PulseAudio" entry to the top.
To be sure, I logged out and even rebooted. After I log in, I still do
not get any system sounds, however, amarok seems to be able to play now.
The sounds in System Settings -> Notifications -> KDE System
Notifications behave very oddly: If I press the play button, nothing
happens. If I press it again, the sound is played once. If I continue,
every second button press will result in the sound being played. If I
press the button in rapid succession, the sounds get played several
times simultaneously. The latter does not surprise me that much, but the
fact that I have to click twice to get any reaction seems odd. In normal
use, the system sounds/notification still don't work.
ProblemType: Bug
Architecture: i386
ArecordDevices:
E: core-util.c: Home directory /home/emgaron not ours.
List of CAPTURE Hardware Devices
card 0: CS46xx [Sound Fusion CS46xx], device 0: CS46xx [CS46xx]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: emgaron3111 F knotify4
emgaron3201 F pulseaudio
emgaron3207 F kmix
Card0.Amixer.info:
Card hw:0 'CS46xx'/'Sound Fusion CS46xx at 0xe920/0xe900, irq 17'
Mixer name : 'Cirrus Logic CS4297A rev 4'
Components : 'AC97a:43525914'
Controls : 45
Simple ctrls : 26
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: alsa-base 1.0.18.dfsg-1ubuntu8
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Uname: Linux 2.6.28-11-generic i686
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
Kubuntu 9.04: Sound only partially working on HP Kayak XM600
https://bugs.launchpad.net/bugs/384967
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384967] Re: Kubuntu 9.04: Sound only partially working on HP Kayak XM600
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/27664941/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/27664944/AplayDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/27664945/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/27664947/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/27664949/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/27664951/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/27664953/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27664954/Dependencies.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/27664956/PciMultimedia.txt -- Kubuntu 9.04: Sound only partially working on HP Kayak XM600 https://bugs.launchpad.net/bugs/384967 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Case (1) seems to chime with what I mentioned in comment #53 ( https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/138691/comments/53 ) about having the dbus shutdown script (K20dbus) in rc0.d as well. However, I did not verify at the time whether that has any ill side effects. Case (2) is apparently what we experienced here. We do not have any VPN involved, but we do have NFS. The one thing I noticed: At home, I have an OpenBSD NFS server and currently (among others...) one Kubuntu 8.04 and one Kubuntu 7.10 workstation hanging off it, with several directories mounted statically (i.e. via fstab) from the NFS server. Neither of those shows the problems we observed at work. My guess is that it is not simply NFS, but in some way also the NIS+automounter set-up we have here. Also, umountnfs did not time out in our set-up - at least not within 24h (I tried...) -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252319] [NEW] gcompris installation only partially functional on Kubuntu
Public bug reported: Binary package hint: gcompris Fresh install of Kubuntu 8.04 with all updates applied: I have installed gcompris-8.4.4-1.1ubuntu1 which pulled in the corresponding gcompris-data package. As I wanted to have the sound as well, I've installed gcompris-sound-de, gcompris-sound-en and gcompris- sound-nl as well. The first thing I noticed was that gcompris would insist on using English written text, even when switched to Dutch or German. I then proceeded to install language-support-de, -nl and -en (8.04+20080214), which did not resolve this problem. After some investigation, I found that the corresponding "gcompris.mo" files are not part of the gcompris package, nor are they part of the language packages I installed - they are actually part of the "language-pack- gnome-XX" packages - but these do not get installed automatically on a Kubuntu system. I think this should be fixed, as not having the gcompris.mo files installed severely hampers the usability on a non- English (or multilinugal) system. Secondly, even after installing all that I found that (at least) one of the reading games still does not work: "Reading Activities" -> "Click on a letter" - no sound is produced for the letters the user is supposed to click on, making this game unusable (tried in German and Dutch so far). ** Affects: gcompris (Ubuntu) Importance: Undecided Status: New -- gcompris installation only partially functional on Kubuntu https://bugs.launchpad.net/bugs/252319 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252319] Re: gcompris installation only partially functional on Kubuntu
Additional info:
"Click on a letter" does not work for English (UK), either. I ran strace on
gcompris while trying this and found that gcompris does indeed find the correct
ogg vorbis file for the welcome message of the game
("/usr/share/gcompris/boards/voices/en/misc/click_on_letter.ogg") and the first
letter (in this case it was
"/usr/share/gcompris/boards/voices/en/alphabet/U0061.ogg"), but for some odd
reasons, the sound is not played.
Playing those files with ogg123 from the command line does work fine.
I also just discovered that while the background music and the initial
"Welcome" do work, none of the other sound effects seem to work. For
example, "Discovery activities" -> "Sound activities" -> "Melody" and
"Discovery activities" -> "Memory activities" -> "Railway" do not work,
either. However, "Discovery activities" -> "Memory activities" -> "Audio
memory game" works.
--
gcompris installation only partially functional on Kubuntu
https://bugs.launchpad.net/bugs/252319
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252319] gcompris problems with locale and sound on Kubuntu
SOLUTION: Some googling gave me the idea that some gstreamer plugins might be needed. I discovered that "gstreamer0.10-plugins-good" is sufficient - all games described above are now working. Hence, the whole issue comes down to dependency/packaging problems: - Under Kubuntu, either gcompris needs to pull in the necessary "language-pack-gnome-XX" or the "gcompris.mo" files need to be packaged differently. Otherwise, the locales do not work in gcompris. - Either gcompris or the "gcompris-sound-XX" packages need to pull in "gstreamer0.10-plugins-good". Otherwise, sound will not work for all games in gcompris. I will change the subject to make this more easily findable. -- gcompris installation only partially functional on Kubuntu https://bugs.launchpad.net/bugs/252319 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 245417] [NEW] Make subject of status mail configurable
Public bug reported: unattended-upgrades has a nice feature which sends a status report via mail to a configurable address. That's great if you have several workstations running Ubuntu and want to keep track of things. However, the subject of these mails is fixed, making it difficult to determine which workstation has sent the mail. Hence my suggestion: If you get a chance, please make the subject configurable - that way, each workstation can use a unique subject (e.g. with the hostname in it), making it a lot easier to scan through a list of status messages. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- Make subject of status mail configurable https://bugs.launchpad.net/bugs/245417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 245422] [NEW] Make log/status mail contain info about "kept back" packages
Public bug reported: Binary package hint: unattended-upgrades In some cases, unattended-upgrades will not execute all available upgrades (e.g. if apt holds back a package due to some other package needing to be installed additionally). Unfortunately, neither the *.log files nor the status mail of unattended-upgrades contains any information about this - you have to log in on the workstation in question and run "apt-get upgrade" manually to get this information. It would be great if unattended-upgrades could supply this information itself (especially in the mail) - that way keeping an eye on what's going on is a lot easier for an admin with several of these workstations. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- Make log/status mail contain info about "kept back" packages https://bugs.launchpad.net/bugs/245422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270838] [NEW] KDE System Settings: Several config windows too big to be usable
Public bug reported: Binary package hint: kde-systemsettings Several of the configuration dialogues that can be accessed via "System Settings" are far too big and do not scale when the window is resized. One of the worst offenders is "Regional & Language" - this screen is so big, that it does not even display fullscreen on 1280x1024 without having to use scrollbars, which makes using this configuration screen very cumbersome. Most of the other configuration screens require fullscreen on 1280x1024 just to avoid scrollbars. None of the screens seem to scale properly when resizing the window. Strangely enough, as far as I can see, the *same* screens scale perfectly when used with the original "kcontrol" (KDE Control Centre) command. "Regional & Accessibility" for example works just fine in a *much* smaller window - no scrollbars necessary. Unfortunately, kcontrol does not seem to be part of the default menu. lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 apt-cache policy kde-systemsettings kde-systemsettings: Installed: 0.0svn20070312-0ubuntu5 ** Affects: kde-systemsettings (Ubuntu) Importance: Undecided Status: New -- KDE System Settings: Several config windows too big to be usable https://bugs.launchpad.net/bugs/270838 You received this bug notification because you are a member of Almost Kubuntu Bugs, which is subscribed to kde-systemsettings in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 54454] Re: ubuntu/gnome printing system is not able to print on more than 1 page in some cases
I can confirm this bug for Kubuntu 8.04.1 and firefox-3.0 (3.0.1+build1 +nobinonly-0ubuntu0.8.04.3). In all cases, the print preview only shows one page and no matter whether I print to file or to an actual printer, I only get one page. >From what I can see so far, this problem is most likely to occur if the webpage in question uses frames. Two examples: http://www.marktplaats.nl/ http://www.hyperelliptic.org/tanja/conf/ECC08/ Pages without frames seem to work a lot better for printing. You *can* work around it sometimes by selecting "Each frame on separate pages" in the Options tab of the print dialogue, but it's still very annoying. -- ubuntu/gnome printing system is not able to print on more than 1 page in some cases https://bugs.launchpad.net/bugs/54454 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 289422] [NEW] 8.10: Application to override monitor selection missing
Public bug reported: In Kubuntu 8.04, it was possible to hard-set/override the monitor selection via System Settings -> Display. Under Kubuntu 8.10RC, this setting is no longer present (same goes for Ubuntu 8.10RC, by the way). Apparently, there is no way to set what monitor you are using. Given that this severely hampers the usability of (K)Ubuntu, I regard this as a bug. There are many situations where the autodetection does not work - older monitors, for example, or - more often - the use of KVMs. At work, all our machines hang off KVMs and for many machines we were forced to hard- set the monitor selection (Kubuntu 8.04), as autodetection fails when the KVM is switched to "the other PC". At home, I face the same problem: I just installed Ubuntu 8.10RC - and was not able to get anything but 800x600, as I cannot tell Ubuntu what monitor I'm using... Again, the machine is connected via a KVM. In these cases, you *have* to be able to configure the monitor yourself. I am aware that I could change xorg.conf directly, but having to do so is *very* disappointing for a distribution like (K)Ubuntu and will pose a problem for less experienced users. ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - 8,10: Application to override monitor selection missing + 8.10: Application to override monitor selection missing -- 8.10: Application to override monitor selection missing https://bugs.launchpad.net/bugs/289422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46516] Re: NFSv4 mounts often missing after boot
I just wanted to add that I have this exact same problem with NFSv3 mounts on Feisty. *None* of the mounts listed in /etc/fstab get mounted during boot - I had to add additional mount commands to /etc/rc.local to get them mounted. Example line from /etc/fstab: 192.168.1.1:/export/src /usr/local/src nfs nouser,wsize=8192,rsize=8192,atime,auto,rw,nodev,noexec,suid 0 0 This share will not get mounted during boot. It will, however, get mounted by the following command in rc.local: mount /usr/local/src which means that the fstab entry *as such* works. The client is Kubuntu 7.04 'Feisty' AMD64 (nfs-common is installed and all updates are applied) and the server runs OpenBSD 3.8 on Sparc64. I've been using the same server set-up (OpenBSD on Sparc) for years now with varying Linux clients (Red Hat, Fedora, Mandrake, SuSE, Aurora) and never had any issues, so I tend to assume that the server is ok... :-) -- NFSv4 mounts often missing after boot https://bugs.launchpad.net/bugs/46516 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Well, one thing I found very valuable when debugging my version of this problem (apparently, there are several causes resulting in the same or at least very similar behaviour) is this: In /etc/default/rcS, make sure that "VERBOSE" is set to "yes" (default is no). That way, some of the scripts in /etc/init.d will be, well. more verbose - only after making this change did I doscover that the shutdown did *not* hang at "Sending...KILL... processes" (which comes from /etc/init.d/sendsignals), but rather later in /etc/init.d/unmountnfs.sh. Unfortunately, there are several scripts running after 'sendsignals' that do not print any output to the screen, unless VERBOSE is yes. In the end, I even added 'echo' statements to some scripts in /etc/init.d just to find out where *exactly* the shutdown hung. I would like to suggest that everybody who experiences this kind of problem tries to look into this - the more precise we can pinpoint the exact location where the shutdown process hangs, the greater the chance that the developers can actually solve this. To the developers: I forgot to mention that - just before removing NetworkManger - I also found a way to get rid of its error messages at shutdown without removing it.I copied "K20dbus" from /etc/rc1.d to /etc/rc0.d, figuring that if dbus needed shutdown for single user, it would also need shutdown for shutdown... After that modification, NetworkManager did no longer spew that bunch of warnings and error messages that the original poster described. It did, however, not solve the problem with the hang. Of course, I'm used to a fully blown Sys V compatible runlevel mechanism (as used e.g. by Red Hat, SuSE, Mandrake) rather than what (K)ubuntu does, so I might well have overlooked something here. -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220504] Re: Firefox doesn't know what apps to use to open any type of downloaded files
I can confirm that installing firefox-gnome-support did fill firefox' application list here as well. I find this very odd as I run Kubuntu 8.04 and hence to not quite expect to have to install something wiht "gnome" in its title just to make another progam work. However, while the application list is now populated, it has no effect whatsoever - firefox still does not let me see PDF files and - even worse - will crash if I try several times. -- Firefox doesn't know what apps to use to open any type of downloaded files https://bugs.launchpad.net/bugs/220504 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232160] [NEW] OpenOffice.org automatic detection of file lock requirement does not work - WITH SOLUTION
Public bug reported: Binary package hint: openoffice.org When switching from SuSE 10.0/OpenOffice 2.0 to Kubuntu 8.04/OpenOffice 2.4 I noticed that file locking no longer worked - two users were able to open the same document at the same time and save changes, with the last save winning. As this is a very undesirable situation I went to investigate. I found that (K)Ubuntu uses custom scripts to start OpenOffice and that these scripts contain some code to automatically determine whether $HOME or the edited file is located on a NFS (or Samba) share depending on the setting of FILE_LOCKING in /etc/openoffice/soffice.sh. FILE_LOCKING defaults to "auto' so the auto detection code is used. Unfortunately, this code does not work - file locking is never enabled, despite the fact that we use NFS-mounted home directories. Having a closer look at /usr/lib/openoffice/program/soffice revealed the problematic part: [...current version of the script...] if [ -z "$SAL_ENABLE_FILE_LOCKING" ]; then case "$FILE_LOCKING" in auto) if ! file_or_home_on_nfs "$@"; then # file locking now enabled by default SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING fi [...] The second if statement is never evaluated successfully, no matter what "file_or_home_on_nfs" returns. Hence, SAL_ENABLE_FILE_LOCKING is never set and thus file locking never enabled. I've modified the code as follows: [...WORKING version...] if [ -z "$SAL_ENABLE_FILE_LOCKING" ]; then case "$FILE_LOCKING" in auto) file_or_home_on_nfs "$@" if [ $? -eq 0 ]; then # file locking now enabled by default SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING fi [...] This version works and correctly sets SAL_ENABLE_FILE_LOCKING to "1". This is most likely not the most elegant variant, but at least it works. I have noticed that there are more if statements like this in the same file (e.g. "if ! working_opengl_support; then" a bit further on) and I have not checked the other scripts in that directory, so there might be similar bugs waiting... WORKAROUND: For those who need file locking to be working before the developers have released a fix: Set FILE_LOCKING to "yes" in /etc/openoffice/soffice.sh to force file locking on all the time (on all types of file systems). Version Information: > lsb_release -rd Description:Ubuntu 8.04 Release:8.04 > apt-cache policy openoffice.org openoffice.org: Installed: 1:2.4.0-3ubuntu6 Candidate: 1:2.4.0-3ubuntu6 Version table: *** 1:2.4.0-3ubuntu6 0 ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New -- OpenOffice.org automatic detection of file lock requirement does not work - WITH SOLUTION https://bugs.launchpad.net/bugs/232160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
We currently have three machines at work that show this behaviour: On shutdown, the system will hang with output resembling what the original poster described in his bug report (Netmanager lines etc.). Every now and then, this output is followed by "Sending all processes the KILL signal", but none of the machines will shut down any further. This is the single-biggest showstopper that prevents us from rolling out (K)ubuntu at the moment. What I have been able to gather so far is this: Machine 1: An Acer TM8104WLMib Laptop with Kubuntu 7.10 i386 installed from the alternate disk, with all updates. I tried adding "acpi=off" to the boot options, but that results in the network interfaces not being recognised and didn't seem to help anyway. This machine *will* shut down if I choose "console login" (hence shutting down X first) and the issue "shutdown -h now" from the command line. Machine 2: Desktop with Asus P5L-1394 motherboard and an Intel PD925. Kubuntu 8.04 i386 without any updates, installed automatically via preseeded network-install, using the alternate CD as starting point, but with a complete mirror (via apt-mirror) of "dists" and "pool". Originally, this machine had Kubuntu 7.10 and needed to be installed using a second NIC, as the onboard NIC (Attansic L1) was not recognised by the install kernel. In that case, the shutdown problem vanished when I removed the second NIC. It returned, however, when I installed 8.04 using the onboard NIC only (fortunately, 8.04's install kernel *does* support the chipset). Machine 3: Desktop with Asus M2A-VM motherboard and an AMD Athlon X2. Kubuntu 8.04 i386 installed automatically via preseeded network-install, using the alternate CD as starting point, but with a complete mirror (via apt-mirror) of "dists" and "pool" (like machine 2). All updates including the latest "proposed" ones are installed (to check what was said by Adolfo above). Still having the shutdown problem. I tried adding "irqpoll apci=off" to the boot options, but that did not change anything. Again, if I choose "console login" and press Ctrl-Alt-Delete, the machine will shut down properly, though not power off. Using "normal" shutdown it hangs in the manner described above. I have also tried to boot this machine with the Kubuntu 8.04 i386 Desktop Live CD and in that case, the machine *will* shut down properly (after having displayed the "Remove CD" message) -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
I have done some more experimenting with "Machine 3" from my previous message. Results: - If I boot the machine, the press Ctrl-Alt-Del at the login screen (i.e. without logging in) and choose shutdown, the machine *will* shut down properly - If I boot the machine and log in, then choose "Turn off" via the KDE Menu, the machine will hang as described - If I remove "quiet splash" from the boot options, the machine *will* shut down properly, even if I do log in. I can still see the Networkmanager/dbus error messages described above during the shutdown process, though. Given these results, my guess is that X does also play a part in this - rather annoying - bug... -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Looks like I spoke too soon - apparently, removing "quest splash" does not always help. The machine just hung again, despite this change. Maybe some race condition? -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232160] Re: OpenOffice.org automatic detection of file lock requirement does not work - WITH SOLUTION
I tested the new package yesterday with FILE_LOCKING set to "auto" in /etc/openoffice/soffice.sh - and now it is indeed working as expected on our NFS directories. Thank you! -- OpenOffice.org automatic detection of file lock requirement does not work - WITH SOLUTION https://bugs.launchpad.net/bugs/232160 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
"reboot=b" didn't make any change on "Machine 3" (Asus M2A-VM). I did, however, find a few more things on both desktop machines (as the laptop is still on 7.10, I'll focus on the two 8.04 machines): - Adding some extra wait time in /etc/init.d/kdm after stopping kdm and before calling usplash_down did not make any change - If I use "shutdown -P now" remotely (i.e. via a ssh session as root (root account *is* enabled)), the machines seems to shut down properly all the time - If I use "sudo shutdown -P now" from a Konsole, the machine hangs on shutdown as described - If I do an "su -" first in Konsole to become 'root', a subsequent "shutdown -P now" will successfully shut down the machine - When the machine hangs, I can actually use "Ctrl-Alt-Del" to get the shutdown process to continue. The first message I see then is "Main rc0 process killed". Also, I get a message about "shutting down kdm... ...kdm is not running". However, in this case, the machine will not shut down all the way, instead, I end up with a black screen with a white blinking cursor in the top left corner. For completeness, as X seems to play some kind of role: - "Machine 2" (Asus P5L-1394) has an nVidia 7300LE VGA card - "Machine 3" (Asus M2A-VM) has an ATI Radeon RS690/Radeon X1200 Series VGA card (onboard) -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Another piece for the puzzle: Apparently, if I shut down all network related services (NIS, NTP, NFS/automounter) prior to initiating shutdown from within KDE, the machines are much more likely to successfully shut down. No idea why. -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
A long row of boot/shut-down cycles with varying parameters got me a bit closer to the solution: All the machines we use have static NFS mounts for some additional directories in /usr/local plus automounted home directories (also via NFS). I haven't experimented with the home directories yet (all tests were run using a local user), but I discovered this: If I manually unmount the static NFS mounts prior to shutting down, the shutdown will succeed. Further investigation showed that the shutdown actually hangs in umountnfs.sh (/etc/rc0.d/S31umountnfs.sh) right at the "umount" command. Hence, something has happened previously during the shutdown process that prevents the "umount" from succeeding. I went even further and added a custom script to /etc/rc0.d to investigate at which point "umount" would fail to work. Unmounting of the static NFS shares worked fine until after sendsignals (/etc/rc0.d/S20sendsignals) has been run, i.e. I can add a script at S19 or any of the K... levels that unmounts the NFS shares and it will succeed. If I add it as S21... or higher, it will hang at "umount", just like the umountnfs.sh script does. It looks like "sendsignals" kills something that is vital to unmounting the NFS shares (NetworkManager?!). However, this does not explain why there is a difference between initiating shutdown from within KDE/kdm and running "shutdown -P now" from the console. For that, I have no idea whatsoever... Now that I can design a workaround for this, I will have a look at the automounted directories... -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown - WORKING "WORKAROUND"
SOLVED! Finally, I got the whole thing working. In the end, the solution was simple: Disable/remove NetworkManager! Boot times actually seem shorter and shutdown works. NIS now comes right up (as opposed to with a delay with NetworkManager operating). To disable NetworkManager without removing it, do the following: 1) Make CERTAIN that your standard network interface is configured properly in /etc/network/interfaces. "systemsettings" was no help in doing so - I had to edit the file manually. In my case, there already was an entry for "eth0" - I just needed to add/uncomment the actual configuration. The complete entry looks like this: # The primary network interface auto eth0 iface eth0 inet dhcp Once this is done, the interface will be enabled during boot-up, despite NetworkManager being disabled. 2) Disable NetworkManager Create two files in /etc/default: echo "exit" > /etc/default/NetworkManager echo "exit" > /etc/default/NetworkManagerDispatcher 3) Reboot If everything went well, you should now have a working, NetworkManager- free network interface. DOWNSIDES: There are probably some potential downsides to disabling NetworkManager, especially if you want your machine to automatically switch between e.g. ethernet and wireless - as far as I understand that's precisely what NetworkManager was invented for. Hence, this situation does need "real" fixing at some point. However, if you have a workstation with a static network interface (in our case, even the laptops are used that way), there's no need for such functionality - just getting the interface up at boot time is sufficient. Another downside is that the knetworkmanager icon does no longer work to indicate the status of the network connection. "knetstats" seems to do the job nicely, however. As we don't need NetworkManager's functionality, there might be potential downsides that I have missed - YMMV, as always. To the developers: If you need some additional input to try and debug the underlying NetworkManager problem, please let me know and I'll rig up a box that uses NetworkManager to test. -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384967] [NEW] Kubuntu 9.04: Sound only partially working on HP Kayak XM600
Public bug reported:
On my HP Kayak XM600, sound is only working partially after having
installed Kubuntu 9.04. So far, I have seen two scenarios:
Upgrade from Kubuntu 8.10 (where sound - I think - was working. Not 100% sure)
to 9.04:
- No system sounds (i.e. no sound for Login/Logout, error messages, beep,
etc.). When going to System Settings -> Notifications -> KDE System
Notifications and tried to play any of the sounds there, nothing happened.
- No sound in amarok
- Something like "ogg123 FILE.ogg" did work (so the hardware is ok)
- The mixer in KMix was correctly shown, no odd settings there
- System Settings -> Multimedia showed "Sound Fusion CS46xx (CS46xx)" at the
top of the list. Clicking on "Test" did result in a sound being played. The
other two entries ("Sound Fusion CS46xx (CS46xx - Rear)" and "PulseAudio" did
not do anything).
- I tried installing the phonon-gstreamer backend and use that instead of the
xine-backend, but that did not change anything.
As I could not get sound to work, I decided to wipe that machine
completely and perform a fresh install of Kubuntu 9.04 (including fresh
user account). After that, sound still was not working - no system
sounds, no sound in amarok, but the mixer was still ok and "ogg123 ..."
still worked. Basically the same as after the upgrade.
Based on some comments in the forums, I installed the "pulseaudio"
package (which did not get installed automatically). I then went to
System Settings -> Multimedia and put the "PulseAudio" entry to the top.
To be sure, I logged out and even rebooted. After I log in, I still do
not get any system sounds, however, amarok seems to be able to play now.
The sounds in System Settings -> Notifications -> KDE System
Notifications behave very oddly: If I press the play button, nothing
happens. If I press it again, the sound is played once. If I continue,
every second button press will result in the sound being played. If I
press the button in rapid succession, the sounds get played several
times simultaneously. The latter does not surprise me that much, but the
fact that I have to click twice to get any reaction seems odd. In normal
use, the system sounds/notification still don't work.
ProblemType: Bug
Architecture: i386
ArecordDevices:
E: core-util.c: Home directory /home/emgaron not ours.
List of CAPTURE Hardware Devices
card 0: CS46xx [Sound Fusion CS46xx], device 0: CS46xx [CS46xx]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: emgaron3111 F knotify4
emgaron3201 F pulseaudio
emgaron3207 F kmix
Card0.Amixer.info:
Card hw:0 'CS46xx'/'Sound Fusion CS46xx at 0xe920/0xe900, irq 17'
Mixer name : 'Cirrus Logic CS4297A rev 4'
Components : 'AC97a:43525914'
Controls : 45
Simple ctrls : 26
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: alsa-base 1.0.18.dfsg-1ubuntu8
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Uname: Linux 2.6.28-11-generic i686
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
Kubuntu 9.04: Sound only partially working on HP Kayak XM600
https://bugs.launchpad.net/bugs/384967
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384967] Re: Kubuntu 9.04: Sound only partially working on HP Kayak XM600
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/27664941/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/27664944/AplayDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/27664945/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/27664947/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/27664949/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/27664951/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/27664953/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27664954/Dependencies.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/27664956/PciMultimedia.txt -- Kubuntu 9.04: Sound only partially working on HP Kayak XM600 https://bugs.launchpad.net/bugs/384967 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378706] Re: Jaunty PPC alternate CD fails to create user account
I have seen this happening once on my iMac DV (400MHz G3 slot-loader). The user account was not created, but I was able to create it manually when booting from the "alternate" CD in "rescue" mode. I could then get a shell while using the installed system as / and subsequently use "adduser" to create a user. I also had to use rescue mode to make sure that account was added to the sudoers file. The same install showed the problem with the root account as described above. I found that this was due to the entry for "root" missing completely from /etc/passwd. Adding it manually resolved this. Also, I only ran into this when I installed the machine before I had replaced the PRAM battery (i.e. it was forgetting its date, time and settings each time I booted). After I had replaced the battery, reset the NVRAM and reset the hardware clock (actually using hwclock --systohc), a second fresh install of 9.04 from the alternate CD correctly created both user account and "root" entry. -- Jaunty PPC alternate CD fails to create user account https://bugs.launchpad.net/bugs/378706 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] [NEW] 9.04 PPC: X only partially functional
Public bug reported: Binary package hint: xserver-xorg-video-r128 Fresh install on an Apple iMac DV (400MHz slot-loader). Before installing, I have replaced the PRAM battery, reset the NVRAM and made sure that the hardware clock was set correctly and kept correctly across power downs. I then proceeded to install 9.04 from the alternate CD for PPC. The install went fine and after the first boot, gdm came up with the login screen. On closer inspection, however, X was started in PseudoColor 8bit mode - which is very annoying and almost unusable in some cases. Hence, I tried to manually configure X to display 24bit TrueColor or at least 16bit (after having installed all updates). I came across the following issues: 1) The "out-of-the-box" xorg.conf file is empty. I have no experience with 9.04 yet, so I don't know whether it's supposed to be that way. 2) After adding the information from one of the many xorg.conf files that can be found for Ubuntu on PPC (which includes the r128 driver), X failed with "no device found" (see attached Xorg.0.log-r128-no_device). This despite all evidence pointing to this iMac having an ATI Rage 128 (see lspci.txt) 3) I then removed the "Driver" instruction to let X choose the driver itself. This resulted in another failure to run X, this time with an error about "modified mode" (see Xorg.0.log-no_driver-modified_mode). In fact, I got this error for all colour depth settings except for 8bit - which is just what I want to get rid of. I will now proceed and install 8.04 from alternate to see whether the machine will then show different behaviour. The original MacOS 9 installation on that box *did* run in TrueColor mode, so I assume that the hardware is fine. ** Affects: xserver-xorg-video-r128 (Ubuntu) Importance: Undecided Status: New -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "Xorg.0.log-r128-no_device" http://launchpadlibrarian.net/28913893/Xorg.0.log-r128-no_device -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "Xorg.0.log-no_driver-modified_mode" http://launchpadlibrarian.net/28913901/Xorg.0.log-no_driver-modified_mode -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "lspci.txt" http://launchpadlibrarian.net/28913899/lspci.txt -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "xorg.conf-r128" http://launchpadlibrarian.net/28913902/xorg.conf-r128 -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Attachment added: "xorg.conf-no_driver" http://launchpadlibrarian.net/28913910/xorg.conf-no_driver -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
Just finished installing 8.04. As described in http://forums.macrumors.com/archive/index.php/t-662667.html the initial X configuration does not produce a working X, however, with the xorg.conf given on that page X works just fine at 1024x768 with 24bit. So, the hardware is fine - just the xserver/driver in 9.04 seems to have problems. -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
** Tags added: apple ati imac rage xorg -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22976] Re: Live CD boots to a black screen on Blueberry G3 iMac
I wonder whether in Intrepid this is related to the bug report I filed a few days ago (I could not find this one then): https://bugs.launchpad.net/bugs/398204 . As far as I remember, I have already tried playing with "DefaultFbBpp" to no avail, but I'll re- check, just to be sure. -- Live CD boots to a black screen on Blueberry G3 iMac https://bugs.launchpad.net/bugs/22976 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22976] Re: Live CD boots to a black screen on Blueberry G3 iMac
Ok, I've re-installed 9.04PPC on my iMac and tried this again. "DefaultFbBpp" does *not* work. If I add this statement to the screen section, X fails with this error: (II) FBDEV(0): using default device (II) Running in FRAMEBUFFER Mode (--) FBDEV(0): Depth 24, (**) framebuffer bpp 32 (==) FBDEV(0): RGB weight 888 (==) FBDEV(0): Default visual is TrueColor (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) (II) FBDEV(0): hardware: OFfb ATY,Rage12 (video memory: 600kB) (II) FBDEV(0): checking modes against framebuffer device... (II) FBDEV(0): mode "1024x768" test failed (II) FBDEV(0): mode "800x600" test failed (II) FBDEV(0): mode "640x480" test failed (II) FBDEV(0): checking modes against monitor... (--) FBDEV(0): Virtual size is 800x600 (pitch 800) (**) FBDEV(0): Built-in mode "current": 100.0 MHz, 119.0 kHz, 186.0 Hz (II) FBDEV(0): Modeline "current"x0.0 100.00 800 816 824 840 600 616 624 640 -hsy nc -vsync -csync (119.0 kHz) (==) FBDEV(0): DPI set to (96, 96) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.4 (**) FBDEV(0): using shadow framebuffer (II) Loading sub module "shadow" (II) LoadModule: "shadow" (II) Loading /usr/lib/xorg/modules//libshadow.so (II) Module shadow: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.1.0 ABI class: X.Org ANSI C Emulation, version 0.4 (==) Depth 24 pixmap format is 32 bpp (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode (EE) FBDEV(0): mode initialization failed -- Live CD boots to a black screen on Blueberry G3 iMac https://bugs.launchpad.net/bugs/22976 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Result of running strace against startx ** Attachment added: "X.strace" http://launchpadlibrarian.net/29203121/X.strace -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] [NEW] 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Public bug reported: Binary package hint: xserver-xorg-video-r128 Ubuntu 9.04PPC "out-of-the-box" fresh install on an iMac DV 400MHz (G3, slot-loader): As the default installation results in 8bit only display (256 colours, PseudoColor mode), I have tried to force the usage of the r128 driver using a minimal xorg.conf (see attachments). This fails, as the r128 driver fails to detect the card (see attached Xorg.0.log). I could not see any difference between including the "disable 'dri'" statement and leaving it out - in the log, it looks like this statement is actually ignored/overridden by the X server. If I run strace against "startx" (strace -fo xserver.trace startx), I can see that the driver accesses the AGP bus and both PCI busses (see also attached output of "lspci -vvnn"). Under 8.04, the same driver works fine on the same hardware. Note: This bugreport supersedes https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-r128/+bug/398204 ! ** Affects: xserver-xorg-video-r128 (Ubuntu) Importance: Undecided Status: New ** Tags: apple ati imac ppc rage xorg -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/29203060/xorg.conf -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Logfile when trying to start X with r128 driver ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/29203097/Xorg.0.log -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
Output of lspci -vvnn ** Attachment added: "lspci_vvnn.txt" http://launchpadlibrarian.net/29203133/lspci_vvnn.txt -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] Re: 9.04 PPC: fbdev wrongly configured in X
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/29203657/xorg.conf -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] Re: 9.04 PPC: fbdev wrongly configured in X
Logfile with error message ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/29203660/Xorg.0.log -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] Re: 9.04 PPC: fbdev wrongly configured in X
fbset output ** Attachment added: "fbset_iv.txt" http://launchpadlibrarian.net/29203666/fbset_iv.txt -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] [NEW] 9.04 PPC: fbdev wrongly configured in X
Public bug reported: Binary package hint: xserver-xorg-video-fbdev Ubuntu 9.04PPC "out-of-the-box" fresh install on an iMac DV 400MHz (G3, slot-loader): After the install, xorg.conf stays empty. Hence, X tries to figure out the correct settings and driver automatically. On my iMac, X fails to detect the built-in ATI Rage 128 card (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-r128/+bug/400864 ) and subsequently tries to use the fbdev driver. When doing so, X does start, however, only 256 colours are used (8bit PseudoColor mode). I tried to investigate the cause for this and tried several things: 1) Create a minimal xorg.conf (the attached version contains some commented out lines from experimenting) with "DefaultDepth 24" in the Screen section. This results in an error message "FBIOPUT_VSCREENINFO succeeded but modified mode" (see attached Xorg.0.log). 2) I tried the same thing using "DefaultFbBpp 32" instead of "DefaultDepth 24". The result was the same. 3) I noticed in the log file that apparently the modes are checked against the fbdev set-up. The default frame-buffer set-up as listed by "fbset -i -v" is attached as well. It can be seen from this output and Xorg.0.log that the frame buffer seems to have 8bit only and only some 600KB of video memory. Hence, I tried modifying these settings with fbset - to no avail. I also tried adding a "VideoRam" statement to xorg.conf - also to no avail. I was not able to change any settings. In the end, I am still not able to run anything but 8bit graphics using the fbdev driver. My impression is that this is due to the frame buffer being in the wrong mode itself, but this seemingly cannot be changed easily. The same hardware works fine with 24bit under 8.04, using the r128 driver. ** Affects: xserver-xorg-video-fbdev (Ubuntu) Importance: Undecided Status: New ** Tags: apple ati fbdev imac ppc rage xorg -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
On closer inspection, I noticed that this bug report touches separate, most likely independent issues (X with fbdev vs. X with r128 driver). Hence, I decided to replace this bug report with separate ones to make it easier to focus on one single issue: 1) r128 does not detect ATI Rage 128 on G3 iMac: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/400864 2) fbdev wrongly configured in X : https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/400875 This bug report is therefore obsolete. I shall try to close it myself - if that fails, please close it for me. -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398204] Re: 9.04 PPC: X only partially functional
This bug report has been superseeded by https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/400864 and https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/400875 ** Changed in: xserver-xorg-video-r128 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-r128 (Ubuntu) Assignee: (unassigned) => Thomas Ribbrock (emgaron+ubuntu) -- 9.04 PPC: X only partially functional https://bugs.launchpad.net/bugs/398204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400875] Re: 9.04 PPC: fbdev wrongly configured in X
For completeness: dmesg ** Attachment added: "dmesg" http://launchpadlibrarian.net/29204401/dmesg -- 9.04 PPC: fbdev wrongly configured in X https://bugs.launchpad.net/bugs/400875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400864] Re: 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac
For completeness: dmesg ** Attachment added: "dmesg" http://launchpadlibrarian.net/29204400/dmesg -- 9.04 PPC: r128 does not detect ATI Rage 128 on G3 iMac https://bugs.launchpad.net/bugs/400864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
