[Bug 1618001] Re: My computer reboots instead of shutting down
Further testing reveals that: 3.2.0-1.3 is the last version that is GOOD. 3.2.0-2.4 is the most recent version that went from GOOD to BAD. In other words, the regression happened between 3.2.0-1.3 and 3.2.0-2.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
Hmmm.. I'm getting inconsistent results. Here's what I have tested so far: 3.0.0-12.20: OK. [3.0.0-13.21 through 3.0.0-32.50: 29 entries not tested] 3.0.0-32.51: NOK. 3.1.0-1.1: OK. 3.1.0-2.2: OK. 3.1.0-2.3: OK. 3.2.0-1.1: OK. [3.2.0-1.2 through 3.2.0-22.35: 34 entries not tested] 3.2.0-23.36: NOK. So, it went from GOOD to BAD, then back to GOOD and back to BAD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
I installed the 3.0.0-12 kernel under Ubuntu 12.04 ("precise"), as per
the KernelBisection instructions.
(I did, however, run into a dependency problem, in that the 'linux-
headers-3.0.0-12-generic' package depended on 'linux-headers-3.0.0-12',
which wasn't listed on the
'https://launchpad.net/ubuntu/oneiric/+source/linux' page to which the
bisection page referred me. I therefore went looking for the missing
package in the old oneiric repository, and found it at 'http://old-
releases.ubuntu.com/ubuntu/pool/main/l/linux/linux-
headers-3.0.0-12_3.0.0-12.20_all.deb'.)
When I subsequently booted Ubuntu 12.04 with this kernel, my computer
successfully shut down, even with a USB medium attached. (In other
words, same behaviour as Ubuntu 11.10 with this kernel version.
So:
o The 3.0.0-12 kernel is OK;
o The 3.2.0-23 kernel is NOT OK.
Guess it's time to start bisecting the kernel versions now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618001
Title:
My computer reboots instead of shutting down
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
I will review the kernel bisection later on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
One further observation: I'm noticing that some USB sticks will not properly 'Eject' on those releases that present the problem; whether I select the 'Eject' or 'Unmount' option on the menu of such a device, does not make a difference, in that the device does get unmounted, but the icon will remain visible (in the 'unmounted' state). On those releases that do properly shut down, 'Eject' on such a device will not only unmount the device, but will also remove its icon from display. One device that shows such errant behaviour, is my 'Alcor Micro Corp. Flash Drive', of which I attach the 'lsusb' details (file 'lsusb_flash.txt'). ** Attachment added: "lsusb_flash.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+attachment/4731163/+files/lsusb_flash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
A few other quick tests: - When booting from the 11.10 ISO, 'ubuntu-11.10-desktop-amd64.iso', shutdown works correctly. - When booting from the 12.04 ISO, 'ubuntu-12.04-desktop-amd64.iso', shutdown works only if no USB media are attached (not really surprising, since that's the same behaviour as when running 12.04 after installation). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
I have just tested 12.04, installed from the 'ubuntu-12.04-desktop- amd64.iso' image, without updates. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04 LTS Release:12.04 Codename: precise $ uname -a Linux wkst1 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux It behaves exactly like 14.04: With no USB media attached, shutdown works. If there's a USB medium connected, then the computer reboots instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
Don't know about any releases between 10.04 and 14.04, since I have never run any of these. I have just downloaded the 'ubuntu-12.04-desktop-amd64.iso' image, to test it. I have also downloaded the original 14.04 image, since I don't know if the issue was present in the initial 14.04 release (I immediately installed updates after install, and I seem to remember that a new kernel got installed at that point, so I have never run the initial 14.04 kernel). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
I installed updates to my 14.04 system about once a week, including any
new kernel versions that came along (I always did "apt-get dist-
upgrade"). In other words, there wasn't really one specific kernel
version that I was using.
My dad's computer, which has pretty much the same hardware as mine (same
model motherboard and CPU, I even bought the hardware for both computers
at the same time), is still running 14.04 ("Ubuntu 14.04.5 LTS",
according to the 'lsb_release' command). The kernel version that it
currently reports (with 'uname -a') is:
Linux wkst0 3.13.0-93-generic #140-Ubuntu SMP Mon Jul 18 21:21:05 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
As far as I can remember, his computer has been having the issue ever
since I first installed 14.04 on it: if there are no USB media present
upon shutdown, then the computer will successfully power off, but if any
USB medium is still connected, then it will reboot.
I refrained from upgrading his computer to 16.04 because under that
release, the computer will reboot, instead of powering off, even without
any USB media present. Now that I have at least a workaround for this
issue, I was considering upgrading his computer after all, but I hadn't
gotten around to it just yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618001
Title:
My computer reboots instead of shutting down
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
Just tested with v4.8-rc3: $ uname -a Linux wkst1 4.8.0-040800rc3-generic #201608212032 SMP Mon Aug 22 00:34:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux The problem persists. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] Re: My computer reboots instead of shutting down
The problem started happening as soon as I did the (fresh) Ubuntu 16.04 install. Previously, the computer had been running 14.04, and the computer would properly shut down as long as no USB medium (stick or disk) was connected when I initiated the shutdown. I got into the habit of disconnecting all USB media before shutting down, and never paid further attention to the issue. I saw this very same behaviour under a Debian release (could be 7 or 8) that was installed on the computer for a short while. Before 14.04, the computer had 10.04, and I don't remember having seen the problem in those days. I have already tested with v4.8-rc2 mainline build, and the problem persisted. Will try '-rc3' when I find the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618001 Title: My computer reboots instead of shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618001] [NEW] My computer reboots instead of shutting down
Public bug reported:
See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579542
When I try to shutdown my computer, it seems as though it is trying to
power off, but it immediately reboots instead.
I can circumvent the problem by unbinding the EHCI drivers right before
power off. I created a systemd service to do this automatically. First,
I created a script, '/usr/local/sbin/unbind-ehci-drivers' that the
service will execute:
--
#!/bin/sh
DRIVER_DIRECTORY='/sys/bus/pci/drivers/ehci-pci'
cd "${DRIVER_DIRECTORY}"
find -mindepth 1 -maxdepth 1 -name '*:*:*.*' -type l -printf '%f\0' | xargs -I
'{}' --null echo '{}' > unbind
--
Next, the '/etc/systemd/system/unbind-ehci-drivers.service' systemd
service file:
--
[Unit]
Description=Unbind EHCI drivers upon system shutdown
DefaultDependencies=no
Before=halt.target
[Service]
Type=oneshot
ExecStart=/usr/local/sbin/unbind-ehci-drivers
[Install]
WantedBy=shutdown.target
--
With these files in place, the following command will enable the service:
root@localhost# systemctl enable unbind-ehci-drivers
Shutdown works now.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-34-generic 4.4.0-34.53
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: luvr 2872 F pulseaudio
/dev/snd/controlC1: luvr 2872 F pulseaudio
CurrentDesktop: XFCE
Date: Mon Aug 29 14:04:15 2016
HibernationDevice: RESUME=UUID=d7daa6c6-cf48-4498-8abf-144837e1a26b
InstallationDate: Installed on 2016-08-09 (19 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
enp2s0no wireless extensions.
lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA78G-DS3H
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic
root=UUID=4b189e9a-d377-49c2-a527-2fc432a51f4f ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-34-generic N/A
linux-backports-modules-4.4.0-34-generic N/A
linux-firmware1.157.3
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/03/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-MA78G-DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/03/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78G-DS3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78G-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA78G-DS3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618001
Title:
My computer reboots instead of shutting down
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618001/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579542] Re: My computer reboots instead of shutdown
Update: In file '/etc/systemd/system/unbind-ehci-drivers.service', only the 'halt.target' appears to be required on the 'Before' line: -- Before=halt.target -- Also, on the 'WantedBy' line, just 'shutdown.target' is sufficient: -- WantedBy=shutdown.target -- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579542 Title: My computer reboots instead of shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579542] Re: My computer reboots instead of shutdown
To make the shutdown work, I created a systemd service that will run
whenever the halt.target or the shutdown.target is to be reached. Since
I need to unbind the EHCI drivers, I named the service, naturally,
'unbind-ehci-drivers'.
First, I created the '/usr/local/sbin/unbind-ehci-drivers' script, which
the service must execute:
--
#!/bin/sh
DRIVER_DIRECTORY='/sys/bus/pci/drivers/ehci-pci'
cd "${DRIVER_DIRECTORY}"
find -mindepth 1 -maxdepth 1 -name '*:*:*.*' -type l -printf '%f\0' | xargs -I
'{}' --null echo '{}' > unbind
--
Next, the '/etc/systemd/system/unbind-ehci-drivers.service' systemd
service file:
--
[Unit]
Description=Unbind EHCI drivers upon system shutdown
DefaultDependencies=no
Before=shutdown.target halt.target
[Service]
Type=oneshot
ExecStart=/usr/local/sbin/unbind-ehci-drivers
[Install]
WantedBy=halt.target shutdown.target
--
With these files in place, the following command will enable the
service:
root@localhost# systemctl enable unbind-ehci-drivers
Optionally, verify if the service is now enabled:
root@localhost# systemctl is-enabled unbind-ehci-drivers
Two other commands that will show more details about the service:
root@localhost# systemctl --all list-units unbind-ehci-drivers.service
root@localhost# systemctl list-unit-files unbind-ehci-drivers.service
Shutdown works now.
Ref.:
'http://askubuntu.com/questions/416299/execute-command-before-shutdown-reboot',
entry "How to Do it with Systemd (it's easier)".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579542
Title:
My computer reboots instead of shutdown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579542/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579542] Re: My computer reboots instead of shutdown
Running Ubuntu 16.04. Just tested with v4.8-rc2 mainline build, and the problem remains. In my case, there are no devices in /sys/bus/pci/drivers/xhci_hcd, so there's nothing to unbind there. Instead, unbinding the ehci-pci devices made the shutdown work: echo ':00:12.2 :00:13.2' > /sys/bus/pci/drivers/ehci-pci/unbind I'll try and create a system halt script to do this automatically upon each shutdown/ halt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579542 Title: My computer reboots instead of shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'
dino99, I won't argue about dependency issues; that may well be the case. In fact, the "libgdk-pixbuf2-dev" package wasn't installed on my Xubuntu system either. I will add that the problem is not specific to Xubuntu, though. I found reports about it under Debian and ArchLinux as well. Also, it must have been known for quite a long time to the Slackware team, since they have the following code fragment in their "/etc/rc.d/rc.M" script, which is executed upon each boot: - if [ -x /usr/bin/update-gdk-pixbuf-loaders ]; then /usr/bin/update-gdk-pixbuf-loaders --verbose fi - When this is executed, the following output is produced: - Updating gdk-pixbuf.loaders for x86_64-slackware-linux: /usr/bin/gdk-pixbuf-query-loaders-64 --update-cache - That is, obviously, one way to circumvent the problem: rerun the command upon each boot... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/619003 Title: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib /gdk-pixbuf-2.0/2.10.0/loaders.cache' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'
dino99,
I have just got this error on a Xubuntu 14.04 system when I did an "apt-get
dist-upgrade" on it.
I'm very careful to make sure that old settings files are purged when packages
are removed, so I'm pretty sure that there were no residual configuration files
remaining when I installed the updates. I even ran an "aptitude purge
'?config-files'" first, just to be sure.
Also, I had double-checked that there were no 'automatically installed
packages that are no longer needed' present on the system ("apt-get
--purge autoremove" did nothing), so I was safe there, too.
The first visual clue that indicated that the problem was real, was the
Mousepad file selection dialog, which didn't work; there was no file
list and no buttons on the dialog windows, but just a grey background
instead. After a reboot, the desktop background, the icons, and all
kinds of visual elements were messed up.
I then did what the error message suggested, i.e.:
gdk-pixbuf-query-loaders >
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
That told me that "gdk-pixbuf-query-loaders" was not installed, and wanted me
to run the following:
apt-get install libgdk-pixbuf2.0-dev
I then reran the "gdk-pixbuf-query-loaders" command, and rebooted. After
that, all was well again.
I then did an "apt-get dist-upgrade" on another Xubuntu 14.04 system,
and that didn't run into any problems.
The two systems had initially been freshly installed (no update from an
earlier release). The one that presented the problem had not been
updated for quite a while (one and a half to two months, I believe),
while the other one, with no problems, gets updated at least once a
week. Also, the problematic system does not have the xubuntu-restricted-
extras installed, while the second one does (though I doubt it that this
will be the cause of the issue). The problem system was installed more
recently, from the 14.04.2 release, while the other one was installed
from the initial 14.04 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619003
Title:
GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib
/gdk-pixbuf-2.0/2.10.0/loaders.cache'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: [Grubenv] error: malformed file, press any key to continue
You're right: I hadn't noticed, but my 'grubenv' file contains a "recordfail=1" line. Also, as you state, there is no time-out on the GRUB menu. As a further experiment, I removed the "recordfail" lines on the menu entries that included them, since I assumed that these were the commands that were responsible for updating the 'grubenv' file. And, indeed, the "recordfail=1" line no longer shows up after reboot. Furthermore, the countdown on the GRUB menu remains. Perhaps I should try and develop my own GRUB install scripts; as it stands, the GRUB configuration file is far more complicated than what I need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311247 Title: [Grubenv] error: malformed file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: [Grubenv] error: malformed file, press any key to continue
Since it looks like the '/boot/grub/grubenv' file is rewritten upon each boot, and (as #53 indicates) the '/etc/init.d/grub-common' script appears to be responsible for this action, I decided to turn off the 'executable' flag on this script--i.e. as root: chmod -x /etc/init.d/grub-common As a result, the grubenv file is being left alone now, and the error no longer reappears. I must say, though, that the error had occurred at boot time when I cleared the executable flag on the script. Consequently, the error kept on happening from that point on, until I reconfigured GRUB--i.e.: grub-install --force /dev/sdb3 grub-install --force --recheck /dev/sdb3 update-grub Makes me wonder what is the actual use of the grub-common script? As far as I can tell, the system works just as well without it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311247 Title: [Grubenv] error: malformed file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: error: malformed file, press any key to continue
Looks like the error message does still appear every now and then. Must have something to do with the '/boot/grub/grubenv' file, which gets recreated upon each boot. The code snippet posted by "AcCEsS" above (cf. comment #7) must be responsible for the error, though I have no idea what it is trying to test for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311247 Title: error: malformed file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311247] Re: error: malformed file, press any key to continue
I also got this error, but now it's gone. I have Ubuntu 14.04 installed on my /dev/sdb3 partition, and the GRUB2 boot loader is installed on the boot sector of the partition (not on the Master Boot Record). The problem disappeared after I did the following (though I'm unsure if that's what made it disappear; for all I know, it could be sheer coincidence): Booted Ubuntu 14.04. Got the error, but the boot completed OK. Ran the following three commands (as root, i.e., after I issued the "sudo su -" command): grub-install --force /dev/sdb3 grub-install --force --recheck /dev/sdb3 update-grub Rebooted Ubuntu 14.04. Still got the error, but, again, the boot completed OK. Repeated the very same three commands. Rebooted Ubuntu 14.04 one more time. The error was gone. So far, the issue hasn't returned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311247 Title: error: malformed file, press any key to continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1311247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556118] Re: CCSM cube deformation stuck on cylinder
I can confirm this bug. On a newly installed system, after I install the CompizConfig Settings Manager and activate Cube Reflection and Deformation, the deformation is stuck at Cylinder. I'm not sure what I did that made it work; I experimented with various CompizConfig settings, but the deformation stubbornly kept behaving as Cylinder. The next day, when I restarted the machine, Deformation suddenly worked correctly. At first, I thought that it had something to do with the graphics hardware (nVidia) in the machine, but I have also seen it happen in an AMD/ATI system. I'll try to pay a little more attention to the sequence of events that lead to a solution if I ever run into the problem again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556118 Title: CCSM cube deformation stuck on cylinder -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556118] Re: CCSM cube deformation stuck on cylinder
I can confirm this bug. On -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556118 Title: CCSM cube deformation stuck on cylinder -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 674153] Re: debmirror cannot download Canonical repository, but reports "Duplicate dist" error instead
** Patch added: "Support multiple dists in the "Canonical" repository, in addition to the "Ubuntu" repository" https://bugs.launchpad.net/bugs/674153/+attachment/1730282/+files/debmirror_origin_patch -- debmirror cannot download Canonical repository, but reports "Duplicate dist" error instead https://bugs.launchpad.net/bugs/674153 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 674153] [NEW] debmirror cannot download Canonical repository, but reports "Duplicate dist" error instead
Public bug reported: Binary package hint: debmirror Running Ubuntu 10.04, using debmirror 1:2.4.4ubuntu2. Trying to download the "Canonical" repository into a "PartnerRepos" directory, as follows: -- mkdir PartnerRepos debmirror --method=http --host=archive.canonical.com --root=ubuntu \ --dist=lucid,lucid-backports,lucid-proposed,lucid-security,lucid-updates \ --section=partner --arch=amd64,i386 --progress PartnerRepos -- This terminates with an error: "Duplicate dist" -- Get Release files. [0%] Getting: dists/lucid/Release... ok [0%] Getting: dists/lucid/Release.gpg... ok [0%] Getting: dists/lucid-backports/Release... ok [0%] Getting: dists/lucid-backports/Release.gpg... ok Duplicate dist lucid. -- Apparently, the lucid version of "debmirror" assumes that a repository has only one dist by default, and explicitly handles the "Ubuntu" repository in a special way, to support its multiple dists. The same problem occurs under maverick (which uses the same debmirror version as lucid), as well as under the current natty pre-release. I documented this issue in greater detail at http://ubuntuforums.org/showthread.php?p=10103252#post10103252 ** Affects: debmirror (Ubuntu) Importance: Undecided Status: New -- debmirror cannot download Canonical repository, but reports "Duplicate dist" error instead https://bugs.launchpad.net/bugs/674153 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 218202] Re: numlockx does not turn num lock keyboard light on.
Ubuntu Lucid (and Karmic, too, if I remember correctly) didn't have this problem here, but some earlier release did. The bug has returned in Maverick. I want NumLock ON when the system prompts me for the username and the password, so I install the numlockx package and add the following lines to the "/etc/gdm/Init/Default" file (just above the "exit 0" line): if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on fi Under Maverick, NumLock will be turned on, but the NumLock LED will not. Strange thing is, GNOME (i.e., the session that gets started for me when I log in) does appear to understand how to turn BOTH the NumLock state AND the NumLock LED on. The first time I logged in to GNOME, I pressed the NumLock key to activate the NumLock state (as well as the LED), and I left it that way. Ever since, whenever I log in, GNOME will restore the NumLock state AND turn on the LED for me. Thus: GNOME KNOWS how to make sure that BOTH the NumLock state AND the NumLock LED are turned ON. Is there anyone here who could tell me what exactly GNOME does to turn on the LED, in addition to the NumLock state? Would it be doable to modify the numlockx utility to do the same? I wouldn't mind to try and do this myself, if only I knew where to start. -- numlockx does not turn num lock keyboard light on. https://bugs.launchpad.net/bugs/218202 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 563862] Re: When logging on power manager fails
I agree with owen, above. When the login screen appears, the boot sequence may still be going on in the background. The end of the boot sequence is signalled audibly with the drum sound (provided, of course that you have sounds on), so the system knows perfectly well when it is done booting. Perhaps the "Login" button on the login screen should simply be kept disabled until the boot sequence is completed? There's no harm in letting the user type in the username and password while the boot process is still running (I do that all the time); it's just that the user should not hit the "Login" button until the computer is fully booted up (I have gotten into the habit of waiting until I hear the drum sound, and only then hitting "Login"; I haven't had any problems since). -- When logging on power manager fails https://bugs.launchpad.net/bugs/563862 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 563862] Re: When logging on power manager fails
I'm noticing that the message window doesn't show up if I wait long enough before I log in--"long enough" being until I hear the Ubuntu startup sound. Apart from this little glitch, the system appears to be working fine, so, at least for the time being, I can live with it. -- When logging on power manager fails https://bugs.launchpad.net/bugs/563862 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 563862] Re: When logging on power manager fails
For me, blacklisting gspca_vc032x doesn't change a thing: Booting still takes a long time, then on logon, I get the "Power Manager not responding" window. More annoying is that sometimes the "Shutdown" item on my panel gets disabled: It changes from red to gray, and it no longer responds. There's no longer any way to shutdown or restart the computer from the desktop environment. I can switch to a character-mode console, stop gdm, and then run a reboot or halt command. However, the computer then often appears to hang before it completely shuts down the operating system; -- still works at that point, though. -- When logging on power manager fails https://bugs.launchpad.net/bugs/563862 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 480350] Re: [Intrepid, Jaunty] Boot process switches from graphical to character mode midstream
I have just done a fresh Jaunty reinstall on one of the two systems, and installed all updates. The issue is gone now. I do wonder how it might get triggered, though. Once a system develops this issue, is appears to be irreparable (at least to the best of my knowledge), short of a fresh reinstall. -- [Intrepid, Jaunty] Boot process switches from graphical to character mode midstream https://bugs.launchpad.net/bugs/480350 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 480350] Re: [Intrepid, Jaunty] Boot process switches from graphical to character mode midstream
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/35501612/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/35501613/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35501614/Dependencies.txt ** Attachment added: "HalComputerInfo.txt" http://launchpadlibrarian.net/35501615/HalComputerInfo.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/35501616/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/35501617/Lsusb.txt ** Attachment added: "MenuLst.txt" http://launchpadlibrarian.net/35501618/MenuLst.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/35501619/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/35501620/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/35501622/ProcModules.txt -- [Intrepid, Jaunty] Boot process switches from graphical to character mode midstream https://bugs.launchpad.net/bugs/480350 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 480350] [NEW] [Intrepid, Jaunty] Boot process switches from graphical to character mode midstream
Public bug reported: Binary package hint: usplash [-- The issue that I'm reporting here occurs on two computers with the same AMD-64 motherboard model, the same CPU model, and both using the on-board ATI graphics adapter. They are running the 32-bit releases of Intrepid and/or Jaunty. On my Dell Studio 17 laptop, which runs 32-bit Jaunty, this issue does not occur (so far). --] Until recently, my AMD-64 computers could boot up their Intrepid and Jaunty (32-bit) systems in graphical mode just fine. A few weeks ago this began to change--first with Intrepid (shortly before the final Karmic release), then with Jaunty (shortly after the final Karmic release). Nowadays, they begin their boot process in graphical mode, showing the Ubuntu logo, with the "gauge" thing moving back and forth, but then, in the middle of the process, they switch to character mode. The first few lines that I see on the character-mode screen are the following: * Reading files needed to boot... * Setting preliminary keymap... * Preparing restricted drivers... (...etc...) The systems can complete their boot processes without error; it's just that they will switch to character mode midstream. I have no idea why they would suddenly begin to behave like this; in an attempt to get the completely graphical boot back, I have tried the following--but to no avail: * Recreate the initial RAM disk; * Specify various different xres and yres values in "/etc/usplash.conf," and rebuild the initial RAM disk each time; * Purge the usplash package, reboot, and reinstall the usplash package; * Install the startupmanager package, and play with its settings. I have run out of inspiration now. (This isn't a gentle way to try and get me to upgrade to Karmic, is it? ;-) ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 MachineType: Gigabyte Technology Co., Ltd. GA-MA78G-DS3H Package: usplash 0.5.31 ProcCmdLine: root=UUID=5aaeb11e-30d2-4f41-a1e6-cd1fadce6f82 ro quiet splash vga=794 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-16.55-generic SourcePackage: usplash UsplashConf: # Usplash configuration file xres=1280 yres=1024 ** Affects: usplash (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- [Intrepid, Jaunty] Boot process switches from graphical to character mode midstream https://bugs.launchpad.net/bugs/480350 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 357134] Re: jockey-kde hungs on 'Activate'
Further observations: I *can* install the fglrx driver with a command like: -- sudo apt-get install fglrx-amdcccle -- (which installs the Catalyst Control Center, in addition to the actual driver). I can then activate it with: -- sudo aticonfig --initial -- When I subsequently reboot, the fglrx driver becomes active--but with *HORRIBLE* performance. While I'm dragging a window, for example, a trail gets left behind, until I drop the window in its final position. Also, none of the compositing features built in to KDE4 can be activated. With these issues, I wouldn't even *dare* try compiz-fusion! I'll stick with Ubuntu (GDM/GNOME) for now, and forget about Kubuntu until next year (i.e., the 10.04 or 10.10 release). -- jockey-kde hungs on 'Activate' https://bugs.launchpad.net/bugs/357134 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 357134] Re: jockey-kde hungs on 'Activate'
Happening to me in Kubuntu 9.10 (final) with ATI Radeon HD 3200 Graphics. -- jockey-kde hungs on 'Activate' https://bugs.launchpad.net/bugs/357134 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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
Aha! Got the new generic kernel working! Here's the output of the "uname -a" command: -- Linux wkst1 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux -- To get the kernel working, I recreated its initial ram disk image, by executing the following command (while running under one of the other working kernels on my karmic system partition): -- sudo update-initramfs -c -v -k 2.6.31-14-generic -- So, it seems like the initial ram disk image did not get properly created when the new generic kernel was installed. -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
I'm having the very same problem. When I attempt to boot from the newly installed kernel, "vmlinuz-2.6.31-14-generic," I get dropped into a character-mode console, which apparently runs from the initial ram disk --the prompt is "(initramfs)". The previously installed kernel, "vmlinuz-2.6.31-13-generic," continues to work fine. Together with the generic kernel, the real-time kernel (which is also installed on this karmic system partition) got updated as well--from "vmlinuz-2.6.31-7-rt" to "vmlinuz-2.6.31-9-rt". In contrast to the updated generic kernel, the new real-time kernel boots up fine; in fact, I'm running it as I type this comment. I'm attaching the text that I see when I try to boot the "vmlinuz-2.6.31-14-generic" kernel. (I typed the text over manually, so I hope I didn't introduce any typos in the text.) The output from the "sudo blkid -p /dev/sdc2" is as follows (I executed the command while running the newly installed--working--real-time kernel): /dev/sdc2: UUID="4034c660-0e15-48f5-8b9a-128b5b0861ed" VERSION="1.0" TYPE="ext3" USAGE="filesystem" ** Attachment added: "Kernel 2.6.31-14-generic Boot Failure.txt" http://launchpadlibrarian.net/33912010/Kernel%202.6.31-14-generic%20Boot%20Failure.txt -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 407660] Re: Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace
I have just installed the real-time kernel on my Ubuntu 9.10 beta system, and I'm running with it right now; "uname -a" gives the following output: Linux wkst1 2.6.31-7-rt #9-Ubuntu SMP PREEMPT RT Wed Oct 7 22:08:13 UTC 2009 i686 GNU/Linux The bug certainly seems to be resolved. This is great news! -- Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace https://bugs.launchpad.net/bugs/407660 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 407660] Re: Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace
> with the nolapic option does the system still lock up with the same tick_handle_periodic() trace? Nope... No trace. The only output that appears on screen, is the following two lines: [0.212982] BIOS bug, local APIC #0 not detected!... [0.213018] ... forcing use of dummy APIC emulation.(tell your hw vendor) And at that point, nothing more happens. -- Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace https://bugs.launchpad.net/bugs/407660 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 407660] Re: Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace
> with the nolapic option does the system still lock up with the same tick_handle_periodic() trace? Nope... No trace. The only output that appears on screen, is the following two lines: [0.212982] BIOS bug, local APIC #0 not detected!... [0.213018] ... forcing use of dummy APIC emulation.(tell your hw vendor) And at that point, nothing more happens. -- Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace https://bugs.launchpad.net/bugs/407660 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 407660] Re: Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace
> I can actually get it to fully boot if I pass the nolapic option and disable the lan in the bios. Hmmm... That doesn't work for me. I simply get a message stating that the local APIC cannot be found, after which my system still locks up. Enabling or disabling the LAN in BIOS doesn't change a thing. There must be more to it than just the LAN option--different CPU models, different disk configurations, or whatnot? -- Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace https://bugs.launchpad.net/bugs/407660 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 407660] Re: Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace
I'm attaching the output from the "cpuid" command. (The command was run under Ubuntu 8.10 on one of the machines on which I attempted to run UbuntuStudio 9.04). ** Attachment added: "cpuid.txt" http://launchpadlibrarian.net/29772755/cpuid.txt -- Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace https://bugs.launchpad.net/bugs/407660 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 407660] Re: Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace
I'm also attaching the output of the "lshw" command (run on the same computer). The motherboard is a Gigabyte GA-MA78G-DS3H. ** Attachment added: "lshw.txt" http://launchpadlibrarian.net/29772777/lshw.txt -- Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace https://bugs.launchpad.net/bugs/407660 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 407660] Re: Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace
** Attachment added: "calltrace.txt" http://launchpadlibrarian.net/29772738/calltrace.txt -- Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace https://bugs.launchpad.net/bugs/407660 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 407660] [NEW] Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace
Public bug reported: I installed UbuntuStudio 9.04 from the "ubuntustudio-9.04-alternate- amd64.iso" DVD. The installation went OK, but as soon as I boot up the computer, it displays a Call Trace and locks up. The only way out is a hard reset. I subsequently installed the real-time kernel 2.6.28-3-rt (which come with UbuntuStudio 9.04) on top of a plain Ubuntu install, with the same results. Since the system locks up firmly whenever I attempt to boot it, there's not much more that I can do in terms of diagnostics; the Call Trace doesn't seem to get saved onto disk, I had to manually type it over in order to obtain a copy of it (see the "calltrace.txt" attachment). ** Affects: linux-rt (Ubuntu) Importance: Undecided Status: New -- Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace https://bugs.launchpad.net/bugs/407660 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 339313] Re: Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
When I run Kubuntu Jaunty from the LiveCD, I just cannot connect to my wireless network (which uses a WEP key)--not even if I start the KDE Wallet first. After installation, I *can* connect, but it doesn't work as flawlessly as it should: It will ask for my (hex) WEP key twice--but, since that's just a one-time event, I can live with it. During the connection procedure, the KDE Wallet will pop up, and (as apo noted in comment #41, above), if I leave the KDE Wallet password empty, automatic connection works fine ever since. I must add that I find Ubuntu KDE in its present form a rather unpleasant experience; I certainly hope that future releases will show significant improvements. For a far more enjoyable KDE experience, I would prefer openSUSE 11.1--if only I liked SUSE better... -- Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key https://bugs.launchpad.net/bugs/339313 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 298797] Re: I/O errors on USB device - device is not cleanly unmounted
Update: Currently (running Ubuntu 8.10, fully updated as per 2009-02-14), I can no longer reproduce the problem. USB works perfectly now. I guess this solves the problem for me. Note: Under 8.04, USB still won't work (cfr. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/254589), but since the problem is now gone under 8.10, I'll simply stop using the older release. (And here I was thinking that 8.04 was supposed to be a "Long- Term Support"--a.k.a. "Stable" release...) -- I/O errors on USB device - device is not cleanly unmounted https://bugs.launchpad.net/bugs/298797 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 179042] Re: Videos tear and "blink" when enabling compiz [AMD Feature #7647] [EPR#257833]
> change your preferences in your video player to output via "x11". An earlier comment here explained how to do that in various video players: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/179042/comments/25 This is really just a work-around, not a real fix, though. Basically, this is an AMD/ATI problem, because AMD/ATI doesn't properly support the development of full-featured open-source drivers for their video adapters--even though they once appeared to promise that they would: see http://www.linux.com/feature/119049 We're, in effect, being held hostage by AMD/ATI; only they can resolve this mess. NVIDIA isn't any better, by the way; I decided to dump them because of the annoying bugs in their binary-only drivers, and because of the apparent promise from AMD/ATI. In fact, the only vendor that seems to properly support open-source drivers for its graphics hardware, is Intel. My only computer that doesn't need a proprietary driver for its video adapter, is a Dell Studio 17 laptop--which has an Intel graphics chip built in. Unfortunately, there aren't any separate Intel graphics adapter cards available; if and when good Intel graphics cards (with full-featured open-source Linux drivers) ever became available, I'd rush out and buy one--No wait, I'd buy at least five! -- Videos tear and "blink" when enabling compiz [AMD Feature #7647] [EPR#257833] https://bugs.launchpad.net/bugs/179042 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 298797] Re: I/O errors on USB device - device is not cleanly unmounted
I have been testing Fedora 10 (the KDE version) for a few days now, and I cannot reproduce this problem there. So, it's a problem with either Ubuntu 8.10, or GNOME. To know for sure, I would have to test it under Kubuntu 8.10 as well; if I can get around to doing so, I'll report my findings here. -- I/O errors on USB device - device is not cleanly unmounted https://bugs.launchpad.net/bugs/298797 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 254589] Re: ubuntu doesn't recognise usb drives
For reference: This attachment ("lshw_silverstone_hd.txt") is the
complete output from the "lshw" command, after I booted Ubuntu 8.04
(fully updated) from harddisk, and connected a USB stick to the
Silverstone hub.
I didn't have to run the "lsusb" command, since the Silverstone hub
functions normally.
If I connect a USB device to either of the other two hubs (i.e., either
the external STLab or the front-panel Sitecom), then that will not get
registered until I run the "lsusb" command.
** Attachment added: "lshw_silverstone_hd.txt"
http://launchpadlibrarian.net/19943973/lshw_silverstone_hd.txt
--
ubuntu doesn't recognise usb drives
https://bugs.launchpad.net/bugs/254589
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 254589] Re: ubuntu doesn't recognise usb drives
For reference: This attachment ("lshw_silverstone_cd.txt") is the
complete output from the "lshw" command, after I booted from the Ubuntu
8.04 Live CD, and connected a USB stick to the Silverstone hub.
** Attachment added: "lshw_silverstone_cd.txt"
http://launchpadlibrarian.net/19943844/lshw_silverstone_cd.txt
--
ubuntu doesn't recognise usb drives
https://bugs.launchpad.net/bugs/254589
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 254589] Re: ubuntu doesn't recognise usb drives
I'm having this very same problem, on two computers with nearly identical hardware: Same brand and type of motherboard, same (AMD64) CPU, same types and capacities of harddisks, same brand and type of DVD drive. They both have three USB hubs connected to them: - A four-port external STLab USB 2.0 hub, connected to a USB plug at the back of the computer; - A front-panel Sitecom FW-006 Combo hub, with four USB 2.0 ports and two Firewire ports, connected to the motherboard headers; - A front-panel Silverstone Combo hub, with four USB ports, one Firewire port, and audio, also connected to the motherboard headers. (Cfr. attachment "lshw.txt" which is the output from the "sudo lshw" command.) When I boot up the Ubuntu 8.04 Live CD, USB works fine: Any device that I connect, will get registered and auto-mounted, as expected. However, when I'm running Ubuntu 8.04 from harddisk, USB devices will NOT get registered (there won't even be any messages in "dmesg"), until I run the "lsusb" command--that will cause the devices to get registered and auto-mounted, and messages to that effect will appear in the "dmesg" log. From then on, any further USB devices that I connect, will function normally, ... until I disconnect all USB devices again. At that point, I need to reissue the "lsusb" command after I connect another USB device. There's one exception: A USB device that I connect to the Silverstone hub, WILL get registered and auto-mounted without further ado. This one hub, thus, is properly handled. Under Ubuntu 8.10 (Intrepid Ibex--installed and fully updated), I cannot reproduce the issue, so it seems to be gone with the newer kernel releases. However, there are other problems in Intrepid Ibex (playing media files in the movie player, or in vlc, or in any other media player that I tried, suffers from bad, insupportable flickering), which, until resolved, keep me from upgrading. ** Attachment added: "lshw.txt" http://launchpadlibrarian.net/19943716/lshw.txt -- ubuntu doesn't recognise usb drives https://bugs.launchpad.net/bugs/254589 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 298797] Re: I/O errors on USB device - device is not cleanly unmounted
** Attachment added: "Input/Output errors as reported by unison." http://launchpadlibrarian.net/19700243/unison-errors -- I/O errors on USB device - device is not cleanly unmounted https://bugs.launchpad.net/bugs/298797 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 298797] Re: I/O errors on USB device - device is not cleanly unmounted
** Attachment added: "fsck" http://launchpadlibrarian.net/19700208/fsck -- I/O errors on USB device - device is not cleanly unmounted https://bugs.launchpad.net/bugs/298797 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 298797] Re: I/O errors on USB device - device is not cleanly unmounted
After I ran into the problem, I booted into Slackware, connected the USB disk, and ran "fsck" on it. The output from "fsck" reported that the device "was not cleanly unmounted, check forced." (Cfr. the "fsck" file attached.) (Note that Slackware identifies the disk as "/dev/sdd," while Ubuntu calls it "/dev/sde.") ** Attachment added: "fsck" http://launchpadlibrarian.net/19700200/fsck -- I/O errors on USB device - device is not cleanly unmounted https://bugs.launchpad.net/bugs/298797 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 298797] Re: I/O errors on USB device - device is not cleanly unmounted
** Attachment added: "dmesg" http://launchpadlibrarian.net/19700118/dmesg -- I/O errors on USB device - device is not cleanly unmounted https://bugs.launchpad.net/bugs/298797 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 298797] [NEW] I/O errors on USB device - device is not cleanly unmounted
Public bug reported: Binary package hint: udev Ubuntu Release: Ubuntu 8.10 (Intrepid Ibex), fully updated as per 2008-11-16. When the system performs many I/O operations on a USB disk in quick succession, I/O errors tend to get reported, and the device will get "not cleanly unmounted." The "sudo fdisk -l" command will then no longer list the USB disk, even though the desktop still displays its icon. An attempt to open the disk through the icon, will open a nautilus file viewer window, but no contents will be displayed. This problem is particularly easy to reproduce using the "unison" file synchronisation utility; just let it try and scan a fairly large directory on the harddisk and a copy of that directory on the USB disk, and wait until the scan finishes. The "unison" window will then display a number of I/O errors. Doing the exact same "unison" scan under Slackware 12.1 will NOT exhibit the problem--it will successfully complete the scan, and it will not report any I/O errors. Errors are being reported in "dmesg," starting at [254.032039] in the attached "dmesg" file: "hub 1-4:1.0: cannot reset port 1 (err = -110)." After a few of these errors, the question "Maybe the USB cable is bad?" is asked--however, it's highly unlikely that the cable would be bad, since it works flawlessly under Slackware. At [1096.32], there's an error saying "sd 6:0:0:0: rejecting I/O to offline device" (followed by some further errors); these occurred when I attempted to open the disk from the desktop icon that was still being displayed. Further observations: The USB disk is a 2.5" device, without a separate power supply; it draws its power from the USB bus. It comes with an additional cable, which I can optionally connect to another USB port, in order to draw power from there. If I do that, then the I/O Errors disappear, and the device works flawlessly. Could it be that Ubuntu (as opposed to Slackware) does not supply sufficient power to the USB port?!? ** Affects: udev (Ubuntu) Importance: Undecided Status: New -- I/O errors on USB device - device is not cleanly unmounted https://bugs.launchpad.net/bugs/298797 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 260001] Re: ubiquity crashed with InstallStepError in configure_bootloader()
In my case, it cannot be a question of "the existing grub multiboot
partition being back-level," because I install GRUB into the root
partition that I'm creating. I even install the GRUB boot loader
("stage1") into the Boot Block of the root partition (NOT in the Master
Boot Block--I use a custom-compiled GRUB as my Master Boot Loader, and
let it chainload to whichever partition that I want to boot.
In my case, the problem is that I'm trying to set up "/home" as a
separate partition--that won't work either.
It seems to me that intrepid will fail unless you install EVERYTHING
into one partition--including "/boot", "/home", and whichever locations
for you might wish to use a separate partition.
Anyway, I have circumvented the problem by initially setting up a
single, self-contained root partition, and afterwards moving "/home"
into its own partition.
--
ubiquity crashed with InstallStepError in configure_bootloader()
https://bugs.launchpad.net/bugs/260001
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 256283] Re: Cannot change option "Use 24 Hour Clock" for login screen
Still present in Ubuntu 8.10 with gdm package version 2.20.8-0ubuntu3 as well. The workaround, as described by Nils-Anders Nøttseter above, still works. -- Cannot change option "Use 24 Hour Clock" for login screen https://bugs.launchpad.net/bugs/256283 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 260001] Re: ubiquity crashed with InstallStepError in configure_bootloader()
My suspicion that GRUB won't install onto the Boot Block of a partition,
doesn't turn out to hold water.
I did a reinstall with GRUB on the Boot Block of the root partition, and this
time it worked fine.
The difference: This time I installed everything into one single partition; I
did not configure "/home" to go onto a separate partition.
So, the first scenario that I tried, did not work: Setting up a root
partition with a separate "/home" partition, and installing GRUB onto
the Boot Block of the root partition.
Two other scenarios did work:
(1) Install everything into one single partition (no separate "/home"), and
installing GRUB onto the Master Boot Record of (what Ubuntu 8.10 sees as) my
first harddisk.
(2) Install everything into one single partition (no separate "/home"), and
installing GRUB onto the Boot Block of the root partition.
***A LITTLE BACKGROUND INFORMATION ON MY HARDDISK CONFIGURATION***
There are four harddisks in this computer: One IDE, and three S-ATA
drives.
The IDE drive is in the "slave" position on the IDE cable (the "master" is my
DVD-RW).
Both the BIOS and Ubuntu 8.04 consider it to be the FIRST harddisk.
Ubuntu 8.04 calls it "/dev/hdb". Ubuntu 8.10, on the other hand, considers it
to be the FOURTH (last) harddisk, and calls it "/dev/sdd".
Since the BIOS considers this to be the FIRST harddisk, the system will boot
from the Master Boot Record of this disk by default.
My Ubuntu root partition sits on the first S-ATA drive.
Both the BIOS and Ubuntu 8.04 consider this to be the SECOND harddisk.
Ubuntu 8.10 considers it to be the FIRST harddisk.
Both Ubuntu releases will call it "/dev/sda".
Since Ubuntu 8.10 considers it to be the FIRST harddisk, it will set up GRUB on
the Master Boot Record of this disk by default. In this scenario, I will have
to select this disk as my boot disk (from the BIOS boot screen) whenever I want
to run Ubuntu 8.10.
My Ubuntu "/home" partition (which I am currently not using) sits on the second
S-ATA drive.
Ubuntu 8.04 considers this to be the THIRD harddisk.
Ubuntu 8.10 considers this to be the SECOND harddisk.
Both Ubuntu releases will call it "/dev/sdb".
(I believe, that BIOS considers it to be the FOURTH drive, but I would have to
verify to be sure.)
The "/home" partition is actually the second partition on this disk; the first
one is a 2-GB Linux swap partition. There's also empty space following the
partitions.
The third S-ATA drive ("/dev/sdc" for both Ubuntu releases) currently
only has a 2-GB Linux swap partition; the rest of the space is empty.
--
ubiquity crashed with InstallStepError in configure_bootloader()
https://bugs.launchpad.net/bugs/260001
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 260001] Re: ubiquity crashed with InstallStepError in configure_bootloader()
Looks to me like GRUB doesn't want to be installed onto the Boot Block of a partition; it wants to be installed onto the Master Boot Block of a disk. Now, when you manually install GRUB onto the Boot Block of a partition (using the GRUB "setup" command), it displays a warning about being unable to write some stuff out (I believe it's a message about stage 1.5, for which there is no room when you install it onto a Boot Block), but it clearly states that this failure is not fatal. Perhaps the installer picks up this warning and "promotes" it into an error? Anyway, I have now been able to install Intrepid Ibex, with GRUB going to the Master Boot Record of what this Ubuntu release calls "(hd0)" in GRUB terms. My BIOS, however, sees it as the second (NOT the first) harddisk. This disagreement has the fortunate side-effect that my EXISTING Master Boot Record wasn't touched; UNfortunately, though, booting the 8.10 system is now somewhat clumsy, since I have to select the second harddisk as the boot disk whenever I want to run Ubuntu 8.10. Having said that, I would now like to install GRUB onto the Boot Block of the 8.10 root partition, so I can continue to make my main GRUB (installed onto the Master Boot Block of my first harddisk) link to it via chainloading. -- ubiquity crashed with InstallStepError in configure_bootloader() https://bugs.launchpad.net/bugs/260001 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 226833] Re: MASTER - nvidia drivers + OO.o trigger plasma drawing artifacts
I agree with Jonathan Thomas that this must be an nVIDIA driver problem. It doesn't happen on a (newly assembled) AMD64 system with an ATI graphics adapter. -- MASTER - nvidia drivers + OO.o trigger plasma drawing artifacts https://bugs.launchpad.net/bugs/226833 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 249553] Re: flashplugin-nonfree Version 10 beta won't properly play ".swf" contents
Forget about this bug... I have just upgraded my PC hardware to an AMD64 CPU with an onboard ATI video chip, and the problem is gone: After I ran my pulse-audio-fixes script, the http://www.metacafe.com site works flawlessly. I'm not sure what could have caused the problems in the first place--the NVIDIA binary driver (which I used with my old hardware)? Some upgrade to Ubuntu that happened to solve it? No idea, but it's gone now. -- flashplugin-nonfree Version 10 beta won't properly play ".swf" contents https://bugs.launchpad.net/bugs/249553 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 249553] Re: flashplugin-nonfree Version 10 beta won't properly play ".swf" contents
** Attachment added: "pulse-audio-fixes" http://launchpadlibrarian.net/16133117/pulse-audio-fixes -- flashplugin-nonfree Version 10 beta won't properly play ".swf" contents https://bugs.launchpad.net/bugs/249553 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 249553] [NEW] flashplugin-nonfree Version 10 beta won't properly play ".swf" contents
Public bug reported: In an attempt to solve the stability issues with Firefox and the Flash plugin, and to allow simultaneous access to the sound hardware by multiple applications, I followed parts A and B of the Ubuntu Forum post at http://ubuntuforums.org/showthread.php?p=4928900. Actually, I ran the “pulse-audio-fixes” script (which I wrote in order to easily repeat the procedure on other computers). Furthermore, I added my user account to the “pulse-audio” and “pulse-rt” groups, as suggested by the forum post. As the most important results of this procedure, the “flashplugin- nonfree” plugin was upgraded to the Version 10 Beta release “10.0.1.218+10.0.0.525ubuntu1,” and the “libflashsupport” package got uninstalled. While both of the original problems were solved, the Flash plugin apparently has great trouble playing “.swf” content on web pages. As an example, videos from “http://www.metacafe.com” won't properly play with this beta version of the plugin: Sometimes they simply won't play at all, sometimes they will take ages to start, only to play for a few seconds and then stop, sometimes the content that does play only shows a part of the image, etc. I tested the Flash 9 plugin on a second computer, which played the contents from the Metacafe site fine. When I subsequently upgraded the plugin to the Version 10 beta, it ran into the exact same problems as the first machine. ** Affects: flashplugin-nonfree (Ubuntu) Importance: Undecided Status: New -- flashplugin-nonfree Version 10 beta won't properly play ".swf" contents https://bugs.launchpad.net/bugs/249553 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 226833] Re: Open Office breaks Plasma
** Changed in: openoffice.org (Ubuntu) Status: New => Invalid -- Open Office breaks Plasma https://bugs.launchpad.net/bugs/226833 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 227924] Re: Systembar and menu get corrupted if OpenOffice.org is the foreground application
** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/14347139/Screenshot.png -- Systembar and menu get corrupted if OpenOffice.org is the foreground application https://bugs.launchpad.net/bugs/227924 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 227924] [NEW] Systembar and menu get corrupted if OpenOffice.org is the foreground application
Public bug reported: Running Kubuntu-kde4 8.04, with OpenOffice.org 2.4.0 (everything is installed from the repositories). When OpenOffice.org is open and is the foreground application, the systembar and menu get corrupted (cfr. attached screenshot, where the menu is terribly mangled). Display returns to normal when I minimise OpenOffice.org, and select another application, although sometimes I need to switch to another desktop. Once the display of the systembar and menu is restored, no more visual problems will occur until I return to work with OpenOffice.org. I haven't seen the problem happen with any other application so far. In case it matters: I'm using an NVIDIA GeForce FX 5700LE graphics adapter, and the nvidia-glx-new restricted driver. ** Affects: meta-kde4 (Ubuntu) Importance: Undecided Status: New -- Systembar and menu get corrupted if OpenOffice.org is the foreground application https://bugs.launchpad.net/bugs/227924 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 218202] Re: [hardy] numlockx does not turn num lock keyboard light on.
Note: The same issue happens under Kubuntu (the KDE3 generation; haven't tested with Kubuntu Remix yet). Thus: - Under Ubuntu (GNOME), numlockx handles the keyboard LED just fine; - Under Xubuntu (xfce), numlockx will not control the LED; however, you can run "numlockx on" from the "/etc/gdm/Init/Default" script, and the LED will be turned on allright; - Under Kubuntu (KDE), numlockx will not control the LED either; I don't remember where the KDE Display Manager looks for its startup script, but I'm fairly confident that "numlockx on" can be run from that script, and the LED will be turned on right. -- [hardy] numlockx does not turn num lock keyboard light on. https://bugs.launchpad.net/bugs/218202 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 218202] Re: [hardy] numlockx does not turn num lock keyboard light on.
Martin-Éric Racine wrote: > Hence why I am veering towards blaming XFCE for skipping the X startup script. I don't think that XFCE is skipping the startup script: After I installed numlockx on Xubuntu, the numeric keypad did become functional upon login--but the keyboard LED did not get lit. It seems to me that the startup script "/etc/X11/Xsession.d/55numlockx" is the one that will execute numlockx upon login (there doesn't seem to be any other place where it might be done), so it must get run. The issue is that XCFE will not turn the keyboard LED on. You can easily verify this by running the command "numlockx on" manually from a shell window: it *will* turn on NumLock mode, but it will not light the LED. Conversely, "numlockx off" will turn NumLock mode off again, but it will not dim the LED (if it was lit, e.g., after you pressed the NumLock key). -- [hardy] numlockx does not turn num lock keyboard light on. https://bugs.launchpad.net/bugs/218202 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 218202] Re: [hardy] numlockx does not turn num lock keyboard light on.
The suggestion made by Cipher_no1 above, does work: Turning on NumLock from "/etc/gdm/Init/Default" *will* turn on the keyboard LED. Once the xfce environment is loaded, however, the "numlockx" utility will no longer touch the LED. For me, this is an acceptable work-around for this issue--NumLock is now automatically turned on when I boot the system, *AND* the LED correctly reflects this fact. Since the NumLock key still functions correctly (i.e., it toggles both the NumLock status and the LED), I can live with it. -- [hardy] numlockx does not turn num lock keyboard light on. https://bugs.launchpad.net/bugs/218202 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 218202] Re: [hardy] numlockx does not turn num lock keyboard light on.
For me, numlockx *does* correctly handle the keyboard led, at least under Ubuntu. Under *Xubuntu* however, the led will NOT get lit. This has the rather strange effect that: - If I use numlockx to turn NumLock on, then the numeric keypad will become functional, but the led will remain off; - If I subsequently press the NumLock key, then the numeric keypad will be deactivated, but the led will become lit! Rather confusing... -- [hardy] numlockx does not turn num lock keyboard light on. https://bugs.launchpad.net/bugs/218202 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
