Setting up firmware-b43-installer (1:017-2) ...
[SNIP]
No chroot environment found. Starting normal installation
--2013-10-19 16:16:04--
http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
Resolving www.lwfinger.com (www.lwfinger.com)... failed: Name or service not
known.
wget:
Assignee: Jean-Baptiste Lallement (jibel)
Status: Triaged
** Tags: amd64 apport-bug qa-manual-testing trusty
** Changed in: alsa-lib (Ubuntu)
Assignee: (unassigned) = Jean-Baptiste Lallement (jibel)
** Changed in: alsa-lib (Ubuntu)
Status: New = In Progress
** Changed
proposition of patch.
** Patch added: alsa-lib_1.0.27.2-1ubuntu7.debdiff
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1246392/+attachment/3895822/+files/alsa-lib_1.0.27.2-1ubuntu7.debdiff
** Changed in: alsa-lib (Ubuntu)
Status: In Progress = Triaged
--
You received this
more verbose strace during a start/stop of dialer-app
** Attachment added: strace_-fFvtt_-s.init_--user_--debug.strace.gz
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864305/+files/strace_-fFvtt_-s.init_--user_--debug.strace.gz
--
You received this bug
/var/log/udev
** Attachment added: _var_log_udev
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864307/+files/_var_log_udev
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
output of get_state.sh after dialer-app has been stopped.
** Attachment added: get_state.out
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864306/+files/get_state.out
--
You received this bug notification because you are a member of Kernel
Packages, which is
output of ls -al /proc/1467/fd/
** Attachment added: ls_-al__proc_PID_fd_.out
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864308/+files/ls_-al__proc_PID_fd_.out
** Changed in: upstart (Ubuntu Saucy)
Status: Incomplete = Confirmed
** Changed in: linux
output of get_state.sh as user phablet
** Attachment added: get_state.out
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864343/+files/get_state.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
output of initctl list as user phablet.
** Attachment added: initctl_list.out
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864504/+files/initctl_list.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: lightdm
Status: Confirmed = Invalid
** Changed in: lightdm (Ubuntu)
Status: Triaged = Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags added: beta qa-daily-testing rtm14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1352778
Title:
bluetooth does not stay off (aka setting does not persist across
reboot)
*** This bug is a duplicate of bug 1376063 ***
https://bugs.launchpad.net/bugs/1376063
** This bug is no longer a duplicate of bug 1296114
[desktop] Bluetooth is always enabled after reboot even if it was disabled
** This bug has been marked a duplicate of bug 1376063
[touch] Bluetooth
It works fine on Utopic Desktop Beta 2 (20140923)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1383851
Title:
Cannot enter LVM encryption password in qemu with -vga std
Status in
I installed Beta2 and upgraded the kernel from 3.16.0-17.23 to 3.16.0.22.23 and
can reproduce the issue.
Upgrading plymouth alone from 0.9.0-0ubuntu5 to 0.9.0-0ubuntu6 doesn't
reproduce it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: bluez (Ubuntu)
Status: New = Incomplete
** Changed in: bluez (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
I couldn't reproduce this crash on recent builds and there was no syslog
on the image I tested due to a bug with the ownership of /var/log.
I'm closing this report because of the lack of information and will re-
open if it reproduces.
** Changed in: linux (Ubuntu)
Status: Triaged =
I cannot run that command on a phone
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
current build number: 122
device name: krillin
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-02-25 15:06:29
version version: 122
version ubuntu: 20150225
version device: 20150210-95b6a9f
version custom: 20150225
It happened up to
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479453
Title:
IN CAR: Bluetooth is connected
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479449
Title:
IN CAR: Bluetooth connected but
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479445
Title:
IN CAR: Signal Strength not
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479438
Title:
IN CAR: Battery levels not
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479442
Title:
IN CAR: Previous Calls log is
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1495441
Title:
Oom killer can trigger a crash
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016
--
You received this bug notification because
Thanks for your report. Which version (OTA) of the phone are you using?
To find the version, open system-settings, scroll down and tap on 'About this
phone', then the version is the field named 'OS'.
Thank you.
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
**
We are closing this bug report because it lacks the information we need to
investigate the problem, as described in the previous comments. Please reopen
it if you can give us the missing information, and don't hesitate to submit bug
reports in the future.
To reopen the bug report you can
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1525320
Title:
Aquaris E4.5 can't connect with car
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue for you?
Thanks in advance.
--
You received this bug notification because you
** Changed in: canonical-devices-system-image
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1390532
Title:
[Bluetooth] Attempt to pair using default
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016
--
You received this bug notification because you
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1499789
Title:
BLUEZ5: Connecting a keyboard
** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => John McAleely (john.mcaleely)
** Changed in: canonical-devices-system-image
Importance: Undecided => Medium
--
You received this bug
** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1390532
Title:
[Bluetooth] Attempt to pair using default
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1539158
Title:
Unable to pair with in-car
@Pat, according to your last comment you couldn't reproduce the issue
with the new bluetooth stack, do you confirm that it is fixed with
latest rc-proposed build?
** Changed in: canonical-devices-system-image
Status: In Progress => Incomplete
--
You received this bug notification because
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1533716
Title:
Delay of approx. 60 seconds when an
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1533716
Title:
Delay of approx. 60 seconds when
I can reproduce the problem with a Garmin Nüvi and latest krillin rc-
proposed. It seems that the call is not initiated when the device is
suspended. As soon as the device wakes up, the call starts.
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
** Changed in:
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww08-2016
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycling Emerson EM229 headset
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww08-2016
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-mako in Ubuntu.
https://bugs.launchpad.net/bugs/1518418
Title:
devices need governor tuning for
** Changed in: canonical-devices-system-image
Status: Confirmed => Triaged
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww08-2016
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww08-2016
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1525320
Title:
Aquaris E4.5 can't connect with car
It's clearly a recent regression . I tried 6 times with krillin rc-
proposed 220 (20160104) and couldn't reproduce the issue. Then upgraded
to latest build (230) and reproduced the issue immediately.
** Tags added: regression-proposed
--
You received this bug notification because you are a
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww04-2016
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1488170
Title:
Bluetooth initiated after quitting
Here is a syslog from krillin rc-proposed 230 when the problem is reproduced.
@20:18:20 the call is initiated from the BT device, the device wakes up and
there is an ATD command to setup the call but immediately the device suspends
again.
Jan 14 20:18:20 ubuntu-phablet kernel: [
** Tags added: regression-proposed
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => John McAleely (john.mcaleely)
** Changed in: canonical-devices-system-image
Milestone: None =>
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1535829
Title:
[bluetooth] "Forget this device"
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1535822
Title:
[bluetooth] Connect automatically
These kernel have been on flo and mako for a while, marking as
verification done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-mako in Ubuntu.
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1535660
Title:
Certain Bluetooth mice do not
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
** Changed in: canonical-pocket-desktop
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: canonical-pocket-desktop
Status: In Progress => Fix Committed
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1418040
Title:
Calling from car using bluetooth,
** Summary changed:
- Cannot use BT speaker after resume from suspend
+ Cannot use BT speaker - sink is suspended
** Description changed:
- After resuming from suspend it is possible to connect to a BT speaker but not
possible to play anything.
+ After a fresh boot or resuming from suspend it
Public bug reported:
After resuming from suspend it is possible to connect to a BT speaker but not
possible to play anything.
Furthermore, if I play a video from youtube, the stream plays fine if the
output is the internal speaker, but as soon as I select the BT speaker the
stream hangs. It
After some experiments on a up to date yakkety, I cannot make audio BT work
after a resume from suspend. The following procedure works around the problem:
1. With a BT speaker already paired, power off the BT speaker
2. Reboot the laptop
3. Go to the BT indicator, and with the BT speaker still
** Attachment added: "pacmd_list-cards.out"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1608820/+attachment/4746073/+files/pacmd_list-cards.out
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1608820
Title:
Cannot use BT speaker - sink is suspended
Status
Thanks Luke, it works much better with pulse from your PPA.
I tried several resume/suspend cycles, powering the speaker off/on or
not and it works much better. The initial pairing with the device is
also improved. I'll keep your ppa for a while to see how it behaves but
overall this is really an
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908620/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908623/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908622/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908615/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908621/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908617/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1700557
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908619/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908614/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1700557
apport information
** Tags added: apport-collected artful
** Description changed:
Automated tests of preseeded installation are failing in UTAH. The VMs
does not reboot unless a key is pressed. It started failing on
2017-06-20.
Only preseeded installation of desktop images are
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908618/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1700557/+attachment/4908616/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
- Automated tests of preseeded installation are failing in UTAH. The VMs
- does not reboot unless a key is pressed. It started failing on
- 2017-06-20.
+ Test Case:
+ 1. Boot an artful desktop ISO in a VM
+ 2. Wait until it boots to the live session
+
+ Expected result
+
** Description changed:
Automated tests of preseeded installation are failing in UTAH. The VMs
does not reboot unless a key is pressed. It started failing on
- 2017-06-20 which matches with the release of the gnome session by
- default.
+ 2017-06-20.
Only preseeded installation of
And the same happens in the lab. After installation the VM hangs until
it receives an input event. Same gap in the logs
[1.776465] clocksource: tsc: mask: 0x max_cycles:
0x256f21accd7, max_idle_ns: 440795301583 ns
[ 59.357199] random: fast init done
--
You received this
** Summary changed:
- VM doesn't reboot after installation unless a key is pressed
+ VM doesn't reboot after installation until an input event is received
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: utah
** Changed in: linux (Ubuntu)
@koza, not in the release pocket. As Seb said it is blocked in proposed
because python3-dbusmock tests fail with bluez 5.45 (cf bug 1696480)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#bluez
http://autopkgtest.ubuntu.com/packages/p/python-dbusmock/artful/amd64
With bluez 5.45 python3-dbusmock tests fail with:
It happens even if you start a VM directly with qemu from the command
line with the qxl driver (option -vga qxl) independently of virt-
manager.
For example, the following command will hang on boot:
/usr/bin/qemu-system-x86_64 -m 2G -smp 2 -localtime -no-reboot -cpu core2duo
-enable-kvm -drive
@bdmurray, I'd like you to reconsider the notfixing tag, it's a real
issue for QA because qxl is the only driver that works with wayland. The
system falls back to X with the standard vga driver and does not boot
after installation with cirrus.
--
You received this bug notification because you
Trace with 4.13
kernel BUG at
/build/linux-jlxc7t/linux-4.13.0/drivers/gpu/drm/ttm/ttm_bo_util.c:589!
invalid opcode: [#1] SMP
Modules linked in: overlay nls_utf8 isofs dm_mirror dm_region_hash dm_log qxl
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse
** Tags added: rls-aa-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1718679
Title:
Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
Status in linux
** Description changed:
Test Case
1. Boot artful desktop 20170817 under qemu with qxl
2. Wait until ubiquity-dm is displayed
Expected result
It boots
Actual result
It hangs on the splash screen and the dots below the Ubuntu logo are not
blinking. If the option 'splash' is
** Tags added: wayland
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1718679
Title:
Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
Status in linux package in
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1721400
Title:
Screen dim during encryption unlock prompt
Status in linux package in Ubuntu:
Confirmed
This bug is also reproducible with the end user stage of an OEM
installation which runs ubiquity-dm like a boot from an ISO.
I think 4.14 (from Canonical kernel team's ppa) fixes the issue. I
installed this kernel during the OEM prepare stage, then the image boots
fine during the end user setup.
4.14.0-0.1
from
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+sourcepub/8271798/+listing-archive-extra
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1711358
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1330785
Title:
Weston on Nouveau displays black screen on Nouveau
Public bug reported:
Ubuntu Desktop Bionic up to date
System doesn't boot with an external monitor attached.
There is this message in the journal (full journal attached for this
boot)
fbcon: inteldrmfb (fb0) is primary device
[drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A
For reference, the lp report tracking the fontconfig issue is bug
1749546
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1754836
Title:
Xubuntu: ERROR:dbus.proxies:Introspect error on
4.13.0-32.35: Boot
4.15.0-10.11: Does not boot
4.16.0-041600rc3.201802261351: Does not boot
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
ubuntu cosmic desktop 20180925
After installation gdm fails to start and there is only a black screen
with a blinking cursor on the top left of the screen.
- gdm3 can be started manually from a tty
+ gdm3 can be started manually from a tty.
+ Switching to
Thanks for your report.
Could you please attach the journal from the boot that failed?
You can get a list of the boots with the command: journalctl --list-boots
Then the journal of a given boot with: journalctl -b [id]
Where id is correspond to the id of the boot returned by list-boots
This is fixed with x-x-v-ati 1:18.1.0-1
Thanks!
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Importance: Low => High
** Tags added: rls-bb-incoming rls-cc-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775526
Title:
package
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Eoan)
Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/b
** Description changed:
On Ubuntu desktop, without a network connection, the user can select to
install 3rd party drivers (which states that it'll install graphics
driver) but even if he selects this option, nVidia proprietary drivers
won't be installed because they are not on the pool of
** Description changed:
On Ubuntu desktop, without a network connection, the user can select to
install 3rd party drivers (which states that it'll install graphics
driver) but even if he selects this option, nVidia proprietary drivers
won't be installed because they are not on the pool of
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Triaged
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Eoan)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
On Ubuntu desktop, without a network connection, the user can select to
install 3rd party drivers (which states that it'll install graphics
driver) but even if he selects this option, nVidia proprietary drivers
won't be installed because they are not on the pool of the ISO.
1 - 100 of 199 matches
Mail list logo
