For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs. I've experimented with having both, but it is just making bugs
hard to find now. Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are
For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs. I've experimented with having both, but it is just making bugs
hard to find now. Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are
For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs. I've experimented with having both, but it is just making bugs
hard to find now. Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are
For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs. I've experimented with having both, but it is just making bugs
hard to find now. Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are
For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs. I've experimented with having both, but it is just making bugs
hard to find now. Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are
For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs. I've experimented with having both, but it is just making bugs
hard to find now. Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are
For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs. I've experimented with having both, but it is just making bugs
hard to find now. Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are
Moved this to be an Upstream bug.
I think that the most probably implementation will be that you declare
chroots in /etc/init.conf that you wish the init daemon to manage. init
will then also look in CHROOT/etc/init for jobs, and record these as
belonging to that chroot. All actions on these
** Summary changed:
- init.d script points to a program named force-reload, which does not exist
+ upstart-job: refers to force-reload(8) instead of reload(8)
--
upstart-job: refers to force-reload(8) instead of reload(8)
https://bugs.launchpad.net/bugs/532862
You received this bug notification
The --verbose parameter doesn't change anything other than potentially
making the boot slightly slower - this sounds more like a nouveau issue
** Package changed: upstart (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
Booting with the '--verbose'
Please also attach your /var/log/udev
--
Booting with the '--verbose' parameter results in a black screen
https://bugs.launchpad.net/bugs/542992
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The flashing caps lock light means you have experienced a kernel panic
** Summary changed:
- Upstart update causes boot to hang - Karmic/ Lucid
+ Kernel panic on boot
** Package changed: upstart (Ubuntu) = linux (Ubuntu)
--
Kernel panic on boot
https://bugs.launchpad.net/bugs/542407
You
*** This bug is a duplicate of bug 497299 ***
https://bugs.launchpad.net/bugs/497299
** This bug has been marked a duplicate of bug 497299
upstart not starting init-scripts (event net-device-up IFACE=lo missing)
--
In Ubuntu Karmic 9.10 the upstart package version 0.6.3-11, don't
Unfortunately there just isn't enough information here to begin to
diagnose your problem. Please read
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
In particular, please give full details about what you changed, and what
you see on screen.
Either way, this is unlikely to be an Upstart
I think the problem here is simply that killprocs (on entering runlevel
1) kills all Upstart-managed jobs, including Plymouth - so plymouth is
not cleanly shutdown, restoring the console
If you press Alt+F1, or Alt+F7, do you find the sulogin shell?
** Summary changed:
- [Lucid Beta] telinit
This is definitely not an Upstart problem, however there is insufficient
information in this report to determine what the problem is. Please
read http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
** Package changed: upstart (Ubuntu) = ubuntu
** Changed in: ubuntu
Status: New =
Thanks for the report.
At your debug shell, could you run the initctl list command for me,
and provide the output.
Also when booting, add --verbose to the kernel command line, and capture
the output from that.
Thanks very much
** Changed in: upstart (Ubuntu)
Status: New = Incomplete
**
The suggested change to udev.conf in that bug report is completely
wrong, incorrect, broken and busted - it will almost always result in
your system not booting
** Changed in: upstart (Ubuntu)
Status: New = Invalid
--
upstart fails to boot with NVidia proprietary driver and several
** Description changed:
Nouveau blacklisting fails when /usr is on seperate partition.
cat /etc/modprobe.d/nvidia-graphics-drivers.conf
blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-173
blacklist nvidia-96
alias nvidia nvidia-current
File exists as above and
Agreed, it should be made available in those processes that run
alongside. It probably makes sense to include it in the event as well,
so you could do:
on started apache
script
.. $APACHE_PID ...
end script
** Summary changed:
- Upstart should include pid as an environment variable
The funny thing is that I have this one written down in my notes, but
never filed a bug for it. Thanks
** Summary changed:
- 'expect fork'+'respawn'+script+ENOENT = start/running w/o PID
+ init: failed exec() and expect cause hang or missing pid
** Changed in: upstart (Ubuntu)
Status:
Actually, the mode change is caused by the framebuffer driver loading on
boot - this isn't changeable.
In the next version we're looking at moving this up so that the
bootloader sets the mode, and the kernel inherits that for its
framebuffer - this will prevent the screen clearing
** Package
On Wed, 2010-04-07 at 16:27 +, paul fox wrote:
where can i find the upstream bug?
This is the upstream bug ;-)
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
--
init: add non-destructive means to disable a job
Moved to Ubuntu bug tracker
** Changed in: ureadahead
Status: Incomplete = Invalid
--
after deleting pack file, first boot is fast, subsequent boots are slow
https://bugs.launchpad.net/bugs/491956
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New = Triaged
** Changed in: ureadahead (Ubuntu)
Importance: Undecided = High
** Changed in: ureadahead
Status: Triaged =
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New = Invalid
** Changed in: ureadahead
Status: New = Invalid
** Changed in: ureadahead (Ubuntu)
Status: Invalid = New
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New = Invalid
** Changed in: ureadahead (Ubuntu)
Status: Invalid = New
** Changed in: ureadahead
Status: New = Invalid
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New = Invalid
** Changed in: ureadahead (Ubuntu)
Status: Invalid = New
** Changed in: ureadahead
Status: New = Invalid
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New = Invalid
** Changed in: ureadahead (Ubuntu)
Status: Invalid = New
** Changed in: ureadahead
Status: New = Invalid
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New = Incomplete
** Changed in: ureadahead
Status: Incomplete = Invalid
** Changed in: ureadahead (Ubuntu)
Importance:
Moved to Ubuntu bug tracker
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ureadahead (Ubuntu)
Status: New = Confirmed
** Changed in: ureadahead (Ubuntu)
Importance: Undecided = High
** Changed in: ureadahead
Status: Confirmed =
Thanks, please do!
** Changed in: upstart (Ubuntu)
Status: Incomplete = Invalid
--
Upstart not starting jobs on boot
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
appreciate that.
It's quite possible that you each have a different problem at this
point.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Wed, 2010-04-07 at 18:47 +, Lars Düsing wrote:
Has anybody forwarded this problem to upstream?
Ubuntu are upstream for Upstart (I wrote it!)
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
init: job stuck with expect fork/daemon when parent reaps child
https://bugs.launchpad.net
package and upload to Ubuntu as I make it ;-)
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
init: add non-destructive means to disable a job
https://bugs.launchpad.net/bugs/94065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
The following assertion is wrong:
- Headless systems won't ever see what plymouth is doing (graphical
boot animation)
the graphical parts of plymouth are contained in the plymouth-theme-*
packages which are Recommends only, without them Plymouth merely
regulates access to the system console in
--
Scott James Remnant
sc...@ubuntu.com
--
Please remove the plymouth dependency from mountall / cryptsetup
https://bugs.launchpad.net/bugs/556372
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Package changed: e2fsprogs (Ubuntu) = dpkg (Ubuntu)
--
package libss2 1.41.11-1ubuntu1 failed to install/upgrade: error writing to
'standard output': Siker
https://bugs.launchpad.net/bugs/556327
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I don't think this is a Plymouth bug or a util-linux bug - it sounds
like getty simply isn't running at the point that the user VT switches.
Which VTs did you try and switch to? When you switch back to X's VT,
you see the X server again?
Could you provide the output of initctl list for me
**
interpretation
of the debugging.
Scott
--
Scott James Remnant
sc...@ubuntu.com
** Changed in: mountall (Ubuntu)
Status: Incomplete = Fix Released
--
ply_event_loop_process_pending_events can block, causing mountall to deadlock
https://bugs.launchpad.net/bugs/518937
You received this bug
It looks like the getty processes are running.
If you press ENTER after Alt+F1, do you see the login: screen?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
VT switch not work with GT240
https://bugs.launchpad.net/bugs/554818
You received this bug notification because you are a member
On Tue, 2010-04-06 at 18:00 +, RussianNeuroMancer wrote:
Yes.
And this works for all VT 1 thru 6?
Sounds like something has just cleared the screens, no idea what?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
VT switch not work with GT240
https://bugs.launchpad.net/bugs/554818
You
Confirmed as still being an issue
** Changed in: plymouth (Ubuntu)
Status: Fix Committed = In Progress
--
no fsck messages shown in details mode (no splash on cmdline)
https://bugs.launchpad.net/bugs/540645
You received this bug notification because you are a member of Ubuntu
Bugs, which
patches in
xorg-edgers that break it again :p)
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubuntu
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided = Low
** Changed in: e2fsprogs (Ubuntu)
Status: New = Incomplete
--
e2fsprogs reports wrong fragmentation
https://bugs.launchpad.net/bugs/548512
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Project changed: upstart = null
** Changed in: null
Status: New = Invalid
** Also affects: ubuntu
Importance: Undecided
Status: New
--
network connection gone 10.04beta1
https://bugs.launchpad.net/bugs/555703
You received this bug notification because you are a member of
** Project changed: upstart = null
--
SD-card having mount point in fstab are not unmounted at halt/reboot time
https://bugs.launchpad.net/bugs/393189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Project changed: upstart = null
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: initramfs-tools (Ubuntu)
Status: New = Fix Released
--
Cannot boot after alternate install using mdadm + lvm: Gave up waiting for
root device
https://bugs.launchpad.net/bugs/550557
You received this bug notification because you are a member of Ubuntu
Bugs, which is
attach the first and last ~1MB of this drive - and let me know
how large it is - this should allow me to trace through blkid to see why
it's not working as intended.
status incomplete
Scott
--
Scott James Remnant
sc...@ubuntu.com
** Changed in: cryptsetup (Ubuntu)
Status: New
On Sat, 2010-04-03 at 08:35 +, orgoj wrote:
My boot.log
** Attachment added: boot.log
http://launchpadlibrarian.net/42957861/boot.log
Thanks, could you try again replacing --verbose with --debug
Also attach your /var/log/udev file
Scott
--
Scott James Remnant
sc...@ubuntu.com
Yes it should.
** Changed in: plymouth (Ubuntu)
Status: Triaged = Invalid
--
plymouth depends on hardware-specific stuff
https://bugs.launchpad.net/bugs/554017
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The lucid util-linux code looks right to me; it should report RAID over
LUKS since RAID is higher in the probe list, and the first successful
probe is returned.
If you can reproduce this problem on lucid, please re-open this bug
** Changed in: util-linux (Ubuntu)
Status: Confirmed = Fix
On Fri, 2010-04-02 at 20:33 +, vmc wrote:
Both installs have the same mountall and esfsck version numbers.
What are the version numbers of mountall and plymouth?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs
** Package changed: udev (Ubuntu) = consolekit (Ubuntu)
--
HP F-4580: Problems with scanner support
https://bugs.launchpad.net/bugs/549073
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
partition. It waited forever for it (it never showed up I assume), and
you were able to skip it.
Could you try appending --debug to the mountall exec line
in /etc/init/mountall.conf and attach /var/log/boot.log after waiting a
short time then skipping.
Scott
--
Scott James Remnant
sc
** Changed in: mountall (Ubuntu)
Status: Incomplete = Fix Released
--
[Lucid] fsck flips rapidly between two messages
https://bugs.launchpad.net/bugs/538433
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Package changed: sysvinit (Ubuntu) = gdm (Ubuntu)
--
log off instead of shutdown or restart
https://bugs.launchpad.net/bugs/554158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 551013 ***
https://bugs.launchpad.net/bugs/551013
** This bug has been marked a duplicate of bug 551013
ubuntu-logo on VGA fb (as with nvidia binary drivers) does not display
crisply
--
plymouth: after installing proprietary nvidia driver, splash
** Changed in: plymouth (Ubuntu)
Status: New = Invalid
** Changed in: plymouth (Ubuntu)
Status: Invalid = Triaged
** Changed in: plymouth (Ubuntu)
Importance: Undecided = Medium
** Summary changed:
- Mount error message is overlayed with the SM message
+ ubuntu-logo theme:
*** This bug is a duplicate of bug 551013 ***
https://bugs.launchpad.net/bugs/551013
** This bug has been marked a duplicate of bug 551013
ubuntu-logo on VGA fb (as with nvidia binary drivers) does not display
crisply
--
[Lucid Beta1] ubuntu-logo does not display crisply using fglrx
progress messages, prompting for passowrds, questions, etc. during boot.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
ubuntu-logo on VGA fb (as with nvidia binary drivers) does not display crisply
https://bugs.launchpad.net/bugs/551013
You received this bug notification because you are a member
file a new bug.
status invalid
Scott
--
Scott James Remnant
sc...@ubuntu.com
** Changed in: udev (Ubuntu)
Status: New = Invalid
--
[Lucid] cdrom drive not recognized automatically
https://bugs.launchpad.net/bugs/539731
You received this bug notification because you are a member of Ubuntu
) Press S (to skip mounting that one)
(c) Press M (for manual recovery)
Could you try each one in turn, and let us know what changes/what you
see.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug
** Package changed: plymouth (Ubuntu) = mountall (Ubuntu)
--
Text message when hard drive as an UNEXPECTED INCONSISTENCY flashes
https://bugs.launchpad.net/bugs/553721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
important medium
Scott
--
Scott James Remnant
sc...@ubuntu.com
** Package changed: plymouth (Ubuntu) = mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
--
Pressing F to fix hard drive when it has: UNEXPECTED INCONSISTENCY; doesn't
work
https://bugs.launchpad.net
This should be fixed with mountall 2.10, please update and test
** Changed in: mountall (Ubuntu)
Status: New = Fix Released
--
/boot partition not mounted at startup
https://bugs.launchpad.net/bugs/549148
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Fix Released
--
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
https://bugs.launchpad.net/bugs/543484
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: udev (Ubuntu)
Status: New = Confirmed
** Changed in: udev (Ubuntu)
Importance: Low = Medium
** Changed in: udev (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
With evolution, F9 don't synchronise, but screen become less bright
On Thu, 2010-04-01 at 22:59 +, ceg wrote:
Yeah, it was a production karmic machine where this got in with update
to 2.16-1ubuntu5.
So you *haven't* tried this with lucid?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
breaking raid: root raid_member opened as luks
https
Could you edit /etc/init/mountall.conf and append --verbose to the
command-line for the mountall binary, then try booting.
Capture the output at the point of looping - the precise detail is
important here, including the error that leads it to skip the mount
** Changed in: mountall (Ubuntu)
Part of the bug here is that even after skipping a filesystem, mountall
will try and mount it again whenever it can - that's why you see the
loop - that was right at the time - but now it's just wrong - a skipped
filesystem should be ignored entirely.
But that still doesn't explain why it stops
(changing to Won't Fix - the report is valid - it's just not something
we're ever going to change)
** Changed in: plymouth (Ubuntu)
Status: Invalid = Won't Fix
--
Package dependencies are too strong
https://bugs.launchpad.net/bugs/553285
You received this bug notification because you are
*** This bug is a duplicate of bug 551013 ***
https://bugs.launchpad.net/bugs/551013
According to the report, you're using the NVIDIA binary driver - so it's
normal for a black screen to appear before X. This comes under the
general banner of #551013
** This bug has been marked a duplicate
The ubuntu-logo and ubuntu-text themes are very different; if ubuntu-
text works, and ubuntu-logo does not, that implies a fault with the
renderer.
Could you try one of the other graphical themes (e.g. plymouth-theme-
spinfinity) and see whether it works or fails with that
** Changed in:
My understanding of this problem:
blkid currently, deliberately, returns only the first detected RAID or
LUKS container for a filesystem - with the checking order being raid
first.
This means if a partition has both a RAID and LUKS signature, it will
always be returned as RAID.
You request that
** Changed in: udev (Ubuntu)
Status: New = Confirmed
** Changed in: udev (Ubuntu)
Importance: Undecided = Medium
** Changed in: udev (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
brightness hotkeys don't work as expected, asus ul30a
Can you confirm that Plymouth disappears completely when you see this
busybox shell?
Press Alt+F1 thru Alt+F7 - what do you see on each of the consoles?
Which one is the busybox shell on (if Alt+F1 does nothing, then probably
F1, and Alt+F1 should get you back)
** Changed in: plymouth (Ubuntu)
There is certainly visual notification of fsck
** Changed in: mountall (Ubuntu)
Status: New = Invalid
--
Boot stuck somewhere before starting X server
https://bugs.launchpad.net/bugs/553374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
From the sounds of your second comment, I don't think you had an fsck at
all, but your machine is simply failing to boot
If you press Escape - what messages do you see on screen at this point?
If nothing, try booting without splash and quiet on the kernel
command-line, and with --verbose instead
the ureadahead message mentioned in that bug, atlhough I believe that
it's innocuous; nevertheless, does that give you a clue where in the
boot is has gotten stuck?
Nope, no idea, sorry. Does it still stick?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Loops on mount failure when Plymouth
** Changed in: pybootchartgui (Ubuntu)
Status: New = Confirmed
** Changed in: pybootchartgui (Ubuntu)
Importance: Undecided = Medium
** Changed in: pybootchartgui (Ubuntu)
Status: Confirmed = Incomplete
--
pybootchartgui crashed with TypeError in render()
Given the crash, it can only be one of our themes ;-)
** Changed in: plymouth (Ubuntu)
Status: New = Confirmed
** Changed in: plymouth (Ubuntu)
Importance: Undecided = Medium
--
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
https://bugs.launchpad.net/bugs/553072
You
** Summary changed:
- [Lucid Beta1] ubuntu-logo on VGA fb (as with nvidia binary drivers) does not
display crisply
+ ubuntu-logo on VGA fb (as with nvidia binary drivers) does not display crisply
--
ubuntu-logo on VGA fb (as with nvidia binary drivers) does not display crisply
so that INIT_VERBOSE=yes on the
kernel command line works, the way it appears to be intended to
It's going to be the former.
I suddenly realised that changing the default this late in the cycle,
and so it's different from upstream Upstart, was a plan made entirely of
crazy.
Scott
--
Scott James
Public bug reported:
Binary package hint: ubuntustudio-look
The plymouth theme package name should be named plymouth-theme-$THEME,
where $THEME is the name of the .plymouth file (e.g. ubuntustudio-
logo)
The package also needs to depend on plymouth-label
** Affects: ubuntustudio-look (Ubuntu)
** Changed in: udev (Ubuntu)
Status: New = Confirmed
** Changed in: udev (Ubuntu)
Importance: Undecided = Medium
** Changed in: udev (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
Special keys (hot keys) on ASUS 1005 series
https://bugs.launchpad.net/bugs/542709
You
for developing) a new way
that works just fine. I'd've commented out the fallback long ago, but
for the fact we have reports of issues with the nouveau drm driver.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Rendering reverts to framebuffer with kernel 2.6.32-16 or later
https
** Changed in: udev (Ubuntu)
Status: New = Confirmed
** Changed in: udev (Ubuntu)
Importance: Undecided = Wishlist
--
no by-path and by-id symlinks for PCI input devices
https://bugs.launchpad.net/bugs/546128
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- Lack of exit codes
+ initctl: lacks proper exit codes
** Changed in: upstart (Ubuntu)
Status: New = Triaged
** Changed in: upstart (Ubuntu)
Importance: Undecided = Medium
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in:
Public bug reported:
Binary package hint: xubuntu-artwork
The plymouth theme package name should be plymouth-theme-$THEME where
theme is the name of the .plymouth file (e.g. plymouth-theme-xubuntu-
logo?)
And the package should depend on plymouth-label
** Affects: xubuntu-artwork (Ubuntu)
** Package changed: sysvinit (Ubuntu) = gdm (Ubuntu)
--
Sessions missing on sign in screen
https://bugs.launchpad.net/bugs/552137
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
*** This bug is a duplicate of bug 551013 ***
https://bugs.launchpad.net/bugs/551013
** This bug has been marked a duplicate of bug 551013
ubuntu-logo on VGA fb (as with nvidia binary drivers) does not display
crisply
--
Boot splash has low resolution and color depth when using nvidia
*** This bug is a duplicate of bug 527666 ***
https://bugs.launchpad.net/bugs/527666
There were a bunch of confirmed bugs that should all be fixed with
Plymouth 0.8.1-3
(and hi, CaE!)
** This bug has been marked a duplicate of bug 527666
Waiting for /some/partition [SM]
--
Boot hangs
*** This bug is a duplicate of bug 527666 ***
https://bugs.launchpad.net/bugs/527666
err, I actually mean fixed with mountall 2.10 - it's been a long week
--
Boot hangs with Waiting for /some/mount [SM] forever.
https://bugs.launchpad.net/bugs/544223
You received this bug notification
*** This bug is a duplicate of bug 527666 ***
https://bugs.launchpad.net/bugs/527666
** This bug has been marked a duplicate of bug 527666
Waiting for /some/partition [SM]
--
old line in /etc/fstab stalls boot process
https://bugs.launchpad.net/bugs/551191
You received this bug
The screens and prompting have been reworked a little to make it more
obvious
--
plymouth crashes the filesystem
https://bugs.launchpad.net/bugs/537926
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 548954 ***
https://bugs.launchpad.net/bugs/548954
** This bug has been marked a duplicate of bug 548954
Ubuntu servers should display information during boot by default
--
No verbose output on ubuntu-server
https://bugs.launchpad.net/bugs/542666
You
Or, to put simply, your card pretends to have more than one output at
all times ;-)
This proves, to me, that this bug is the *cause* of bug #533135
--
nouveau hard lockup in nouveau_gem_ioctl_cpu_fini
https://bugs.launchpad.net/bugs/539655
You received this bug notification because you are a
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Triaged
--
System fails to boot with plymouth installed (nouveau driver with 1 display)
https://bugs.launchpad.net/bugs/533135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
601 - 700 of 6846 matches
Mail list logo
