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,
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:
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
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:
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
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
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
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
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
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
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
: 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/
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
--
--
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,
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' >
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
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
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
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
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
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
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
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
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:
---cut---
mkdir PartnerRepos
debmirror --method=http --host=archive.canonical.com --root=ubuntu \
** 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
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
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.
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
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
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
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
** 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
**
Further observations: I *can* install the fglrx driver with a command
like:
---cut---
sudo apt-get install fglrx-amdcccle
---tuc---
(which installs the Catalyst Control Center, in addition to the actual
driver). I can then activate it with:
---cut---
sudo aticonfig --initial
---tuc---
When I
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
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,
Aha! Got the new generic kernel working! Here's the output of the uname -a
command:
---cut---
Linux wkst1 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686
GNU/Linux
---tuc---
To get the kernel working, I recreated its initial ram disk image, by
executing the following command
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
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
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
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
** 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,
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
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
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
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
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
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,
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'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
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
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.
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
** 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.
--
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
** 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.
--
** 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
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
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
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
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
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
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
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
** 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
** 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
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).
** 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,
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
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
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
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
71 matches
Mail list logo
