Same just happened to me on Ubuntu 18.10 after console-setup-linux was
updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787879
Title:
kbd_mode resets on console-setup-linux package upgrade
T
I think this bug report demonstrates a significant problem in the
current boot system: the reported user-visible symptom can be caused by
a wide variety of underlying issues during the boot process. Further,
it's hard to diagnose which underlying issue affects each system .
I propose this bug numb
Re #5 how to reproduce with a normal Ubuntu installation:
1. apt-get install gdm
2. Choose gdm as the default display manager when prompted.
3. apt-get remove gdm
4. cat /etc/X11/default-display-manager
This should just say "lightdm" and following boots should fail until the
file content is change
** Attachment added: "version"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/864195/+attachment/2518627/+files/version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864195
Title:
Oneir
/var/log/installer/ contains only these two files, attached.
** Attachment added: "debug"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/864195/+attachment/2518636/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/865056
Title:
system thinks battery is critically low and goes to hibernation
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Public bug reported:
I suspended and resumed the system with fully charged battery. Right
after resume, the system decided to hibernate. When I resumed again, I
could see the dialog "Power - Laptop battery critically low - The
battery is below the critical level and this computer is about to
hiber
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864195
Title:
Oneiric beta2 install fails on SATA RAID/fakeraid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
Public bug reported:
I installed Oneiric beta2 on a laptop that has SATA RAID/fakeraid. The
installation process failed to install GRUB, and choosing to install
GRUB on another partition didn't work either.
However, I was able to install GRUB manually in the target chroot to
/dev/mapper/isw_eahge
Public bug reported:
I've installed Oneiric beta2 on a laptop that has SATA RAID/fakeraid.
During system boot, I see the following message:
udevd[105]: inotify_add_watch(6, /dev/dm-1, 10) failed: No such file or
directory.
However, I haven't noticed a problem caused by this. I do note that on
so
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864185
Title:
warning during boot about udev trying to watch /dev/dm-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864174
Title:
boot hangs waiting for lightdm after purging gdm
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/l
Public bug reported:
I've installed Oneiric beta2 and at some point installed and purged gdm.
After that, boot will hang waiting for lightdm to start, which never
happens. This is because /etc/X11/default-display-manager ends up saying
"lightdm" whereas /etc/init/lightdm.conf accepts "/usr/bin/lig
I hit the bug mentioned in comments #4 and #5 -- filed as bug #864174.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828576
Title:
Light-DM not used after upgrade 11.04→11.10
To manage notification
I had the same symptoms as the original reporter but the problem was
wrong contents of /etc/X11/default-display-manager: #864174
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/856810
Title:
Boot hang
Adam, wrt bug #312756 "support graphics card hot switch":
Here in bug #435906, I'm not asking for hot switch -- what we urgently
need is just that the extra GPU be turned off. I consider this a
significant bug as these laptops are certainly not designed to power two
GPUs at a time. Further, this i
** Description changed:
- Some new laptops such as this Acer Travelmate 8371G (Timeline) have two
+ Some laptops such as this Acer Travelmate 8371G (Timeline) have two
graphics adapters (Intel 4500MHD and ATI HD 4330). There are two BIOS
settings: "Switchable graphics" and "Discrete graphics".
Now in Maverick, vga_switcheroo is enabled, but the extra GPU is still
powered on by default.
As a workaround, I've added the following line to /etc/rc.local:
echo "OFF" > /sys/kernel/debug/vgaswitcheroo/switch
--
need to turn off extra "Switchable graphics" GPU
https://bugs.launchpad.net/bug
** This bug is no longer a duplicate of bug 312756
support graphics card hot switch
--
need to turn off extra "Switchable graphics" GPU
https://bugs.launchpad.net/bugs/435906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/41479902/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/41479903/AplayDevices.txt
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/41479904/BootDmesg.gz
** Attac
Public bug reported:
X freeze on i915
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Su
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/35327204/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35327205/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/35327206/Disassembly.txt
** Attachm
This seems to be fixed now. Thanks!
--
[MASTER] chrome error when viewing untrusted https site using firefox with
fi-FI on karmic
https://bugs.launchpad.net/bugs/429835
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Sorry, I don't have any .crash files for X, gdm, gnome-session etc. just
for gnome-keyring-daemon and indicator-messages-service as well as
polkitd, console-kit-daemon and NetworkManager. Apport won't submit
these as some unrelated library packages have been updated meanwhile.
Anyway, I don't thin
Attaching the end of .xsession-errors. Unfortunately a lot of it is in LANG,
but translating, there are messages like this:
"Resource temporarily unavailable", "Remote closed connection", "Connection to
the settings daemon failed", "Window manager warning: Critical IO error 111
(Connection refus
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/33581847/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/33581848/AplayDevices.txt
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/33581849/BootDmesg.gz
** Attac
Public bug reported:
Last time during resume, X appeared but then immediately crashed, and
gdm wouldn't restart anymore. dmesg had lines like this for each process
using gobject:
[21720.091101] gnome-session[2342]: segfault at 1 ip 0028ab18 sp
bfcf4d20 error 6 in libgobject-2.0.so.0.2200.2[27e000
Mat, as I wrote above, I tested this and the menu won't be affected. Any
other places to check? If none, then gnome-settings-daemon can be
removed from this bug and we can start waiting for the new icon design -
right?
--
display properties notification area icon still fully coloured
https://bugs
*** This bug is a duplicate of bug 42 ***
https://bugs.launchpad.net/bugs/42
I did some more testing, and the error is not quite 100% reproducible: I
was able to get Firefox to open some reports for apport and emacs as
well (4 passes for 11 failures), and I was able to get some errors
As mentioned in bug #442527 (marked as duplicate of this as the steps
and the error are the same), the error is (100%) reproducible for
specific package names (such as apport and in my case, emacs) whereas
some other package names work fine (such as linux).
** Summary changed:
- Can't report a b
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33223665/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/33223666/XsessionErrors.txt
--
emacs default font is huge
https://bugs.launchpad.net/bugs/445402
You received this bug no
Public bug reported:
Binary package hint: emacs23
Since the latest emacs upgrade in Karmic, the default font is now huge.
The Set Default Font dialog claims the font is DejaVu Sans Mono Book 12,
and in the preview, capital letters indeed are 12 pixels high. However,
in the editor, capital letters
*** This bug is a duplicate of bug 441804 ***
https://bugs.launchpad.net/bugs/441804
** This bug has been marked a duplicate of bug 441804
Can't report a bug with ubuntu-bug
--
problem with xserver when reporting bug
https://bugs.launchpad.net/bugs/442527
You received this bug notificatio
Tested current status (humanity-icon-theme 0.4.1-0ubuntu1, gnome-
settings-daemon 2.28.0-0ubuntu2).
$ dpkg -S gsd-xrandr.svg
humanity-icon-theme: /usr/share/icons/Humanity/apps/24/gsd-xrandr.svg
gnome-settings-daemon: /usr/share/icons/hicolor/scalable/apps/gsd-xrandr.svg
humanity-icon-theme: /usr/
As others have commented earlier, this bug appears to be somewhat random
(a race condition?) and so a few successful boots don't mean the bug is
fixed. If #32 doesn't do essentially more than #2, it fails every now
and then at least here and as such I'm not surprised of comments #12,
#31, #37.
I'm
This seems to have been fixed upstream and released in apport
1.9.2-0ubuntu1.
--
ubuntu-bug crashes with LANG=fi_FI.UTF-8
https://bugs.launchpad.net/bugs/432954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Tags added: ubuntu-boot-experience
--
"BAR 6" warnings during boot
https://bugs.launchpad.net/bugs/435885
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.c
I suppose whether it's the same bug for different BAR numbers depends on how
you look at it. The suggested kernel patch disables this for BAR 6 only, reason
being: "since
this is BAR 6, is we have a ROM which has been mapped high, and then
not unmapped. -- We shouldn't warn about not being able t
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32594478/AlsaDevices.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Attachment added: "WifiSyslog.gz"
http://launchpadlibrarian.net/32594498/WifiSyslog.gz
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/32594497/UdevLog.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/32594496/UdevDb.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: "RfKill.txt"
http://launchpadlibrarian.net/32594495/RfKill.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/32594494/ProcModules.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/32594493/ProcInterrupts.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/32594492/ProcCpuinfo.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Attachment added: "PciMultimedia.txt"
http://launchpadlibrarian.net/32594491/PciMultimedia.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
** Attachment added: "Lsusb.txt"
http://launchpadlibrarian.net/32594489/Lsusb.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/32594488/Lspci.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Attachment added: "IwConfig.txt"
http://launchpadlibrarian.net/32594484/IwConfig.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/32594483/CurrentDmesg.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/32594479/AplayDevices.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/32594481/Card0.Amixer.values.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Attachment added: "Card0.Codecs.codec.0.txt"
http://launchpadlibrarian.net/32594482/Card0.Codecs.codec.0.txt
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/32594480/BootDmesg.gz
--
Seeing drm:intel_dp_i2c_init errors on boot
https://bugs.launchpad.net/bugs/409361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tuukka 1962 F pulseaud
This bug affects me too when running "apport-cli -f" when
LANG=fi_FI.UTF-8. The issue is in Apport using apport.unicode_gettext
and then sys.stdout.writing the result, which doesn't convert the
unicode strings to the locale charset before output. The simple patch to
fix this is the following:
---
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32371624/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/32371625/AplayDevices.txt
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/32371626/BootDmesg.gz
** Attac
Public bug reported:
Some new laptops such as this Acer Travelmate 8371G (Timeline) have two
graphics adapters (Intel 4500MHD and ATI HD 4330). There are two BIOS
settings: "Switchable graphics" and "Discrete graphics". With the latter
option, only the ATI GPU is in use, but with the former option
Public bug reported:
In the beginning of a silent boot on this machine, I get these two warning
lines:
pci :01:00.0: BAR 6: no parent found for of device [0xfffe-0x]
pci :03:00.0: BAR 6: no parent found for of device [0xfffe-0x]
for which lspci says:
01:00.0
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32370645/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/32370646/AplayDevices.txt
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/32370647/BootDmesg.gz
** Attac
As far as I know, nobody's able to resume Acer Timeline machines from
suspend. I've just upgraded Karmic and the resume still fails with
kernel linux-image-2.6.31-10-generic 2.6.31-10.35. More specifically,
the machine enters suspend fine and the power led starts to blink
orange. A press of the spa
The euro and dollar key issue is discussed at bug #30562 here:
https://bugs.launchpad.net/debian-goodies/+bug/30562
--
[ jaunty ] Acer aspire 9800 keycode not all mapped
https://bugs.launchpad.net/bugs/328022
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Same machine here. It's interesting to note that of the six scsi_hosts,
0, 4, 5 remain in max_performance whereas 1,2,3 can be set to min_power.
--
Unable to activate ALPM
https://bugs.launchpad.net/bugs/431822
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Same here, and I didn't have to do more than log in and wait a sec. I
don't even have any synergy client machines turned on.
--
synergys assert failure: synergys: CArchMultithreadPosix.cpp:286: virtual void
CArchMultithreadPosix::closeMutex(CArchMutexImpl*): Assertion `status == 0'
failed.
http
Same symptoms started to appear here at the same time (yesterday), but
the hardware is different (Intel/Intel/laptop vs. ATI/nVidia/desktop)
and I run X the normal way (via gdm). I see the bug sometimes when I use
the "switch user" feature (no keyboard or mouse at gdm login screen).
I had a look a
66 matches
Mail list logo
