Increasing importance due to possible denial-of-service during a resize
of large 'complex' file-systems. In this case both reports using DM RAID
6.
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided => High
** Changed in: e2fsprogs (Ubuntu)
Status: Confirmed => Triaged
--
You
, but no keyscript is
set. Please ensure there is also a typed pass-phrase set.
** Affects: cryptsetup (Ubuntu)
Importance: Undecided
Assignee: TJ (tj)
Status: In Progress
** Patch added: "Proposed fix"
https://bugs.launchpad.net/bugs/1494851/+attachment/4461428/+files
** Changed in: cryptsetup (Ubuntu)
Status: New => Triaged
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => High
** Changed in: cryptsetup (Ubuntu)
Assignee: (unassigned) => TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bu
Public bug reported:
"man resize2fs" states "Optionally, the size parameter may be suffixed
by one of the following the units designators: 's', 'K', 'M', or 'G',
for 512 byte sectors, kilobytes, megabytes, or gigabytes, respectively."
In practice the suffix appears to be ignored.
$ sudo
Public bug reported:
'man resize2fs' claims "If no units are specified, the units of the size
parameter shall be the filesystem blocksize of the filesystem" but
makes no mention of the units used in the minimum size report. The tool
itself makes no mention of units.
Many users would assume the
** Description changed:
When crypttab specifies a key-file for the container of the root file-
system but there is no keyscript= option no cryptsetup support is
installed in the initrd.img.
Currently the cryptroot initramfs hook script knows its a problem and
will report:
The actual problem is -ETIMEDOUT.
I'm doing git-bisect to find the offending commit(s).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491988
Title:
15.10: BT Command List not created:
Another log, this time capturing the module, function, line-number and
message.
Sep 10 00:52:44 hephaestion kernel: [23623.022036] bluetooth:hci_cmd_work:4358:
hci1 cmd_cnt 1 cmd queued 4
Sep 10 00:52:44 hephaestion kernel: [23623.022044]
bluetooth:hci_send_frame:3494: hci1 type 1 len 3
Sep 10
I believe I've identified the root-cause:
$ hciconfig hci1 features
hci1: Type: BR/EDR Bus: USB
BD Address: 00:10:7A:4D:15:33 ACL MTU: 672:8 SCO MTU: 255:255
Features: 0xff 0xfb 0x01 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets>
Extract from the kern.log:
Sep 10 00:17:36 hephaestion kernel: [21515.251265] hci1 end: err -110
-110 == -ETIMEDOUT
There are 2 functions that print the message "end: err %d":
net/bluetooth/hci_core.c::__hci_cmd_sync_ev()
net/bluetooth/hci_core.c::__hci_req_sync()
--
You received this bug
Tested the keyboards successfully with Lubuntu 12.04 Precise and Ubuntu
13.04 Raring which confirms this is a regression.
linux 3.2.0-30-generic-pae, bluez 4.98-2ubuntu7
linux 3.8.0-35-generic, bluez 4.101-0ubuntu8b1
** Changed in: bluez (Ubuntu)
Status: New => Triaged
** Changed in:
I've now tested the device on two other systems with older releases; the
results seem to point to a regression somewhere between v3.2 and v3.8:
FAILS: linux 3.8.0-35-generic, bluez 4.101-0ubuntu8b1 (same
failure mode as Linux v4.2)
WORKS: linux 3.2.0-30-generic-pae, bluez
** Summary changed:
- 15.10: Multiple Bluetooth controllers not found
+ 15.10: BT Command List not created: bluetooth:__hci_req_sync:298: hci1 end:
err -ETIMEDOUT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been working on this some more. I noticed that even when both
adapters are connected before bluetoothd starts, it does not find the
2nd adapter.
The problem appears to be in the read_index_list_complete() call-back,
which sees only 1 controller despite the RFkill events reporting 3
devices,
ntu)
Status: Triaged => In Progress
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
** Changed in: bluez (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491988
Title:
15.10: Multiple Bluetooth controllers not found
To manage
** Bug watch added: GNU Savannah Bug Tracker #45889
http://savannah.gnu.org/bugs/?45889
** Also affects: grub via
http://savannah.gnu.org/bugs/?45889
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hit this again today; Was working fine until about 05:40 when I locked
the session and left. Returned around 12:20, touched the mousepad to
wake the monitors, backlights come on but no display. SSH from another
host shows a 2nd X server attempts to start on :1 at the time I
returned, fails, tries
Public bug reported:
Helping a user on IRC where ubuntu-drivers failed to detect
0a:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX
850M] [10de:1391] (rev a2)
Looking at the source-code I noticed that
/usr/lib/python3/dist-
Public bug reported:
Upstream bug: https://savannah.gnu.org/bugs/index.php?45889
Boot disk with 3 LUKS/dm-crypt GPT partitions
(hd0,gpt3) (hd0,gpt4) (hd0,gpt5)
grub is in (hd0,gpt3). The others have a LVM VG each.
Using GRUB_ENABLE_CRYPTODISK=y
I deliberately fail the first pass-phrase
** Description changed:
+ Upstream bug: https://savannah.gnu.org/bugs/index.php?45889
+
Boot disk with 3 LUKS/dm-crypt GPT partitions
(hd0,gpt3) (hd0,gpt4) (hd0,gpt5)
grub is in (hd0,gpt3). The others have a LVM VG each.
Using GRUB_ENABLE_CRYPTODISK=y
I deliberately fail
Public bug reported:
Wasn't aware of this; apport found it after a reboot
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-7.7-lowlatency 4.2.0
Uname: Linux 4.2.0-7-lowlatency x86_64
NonfreeKernelModules: nvidia
ApportVersion:
Hit this again today with lightdm spamming the logs.
I'd left the PC for about 45 minutes; came back to a backlit but black
display and no response to input.
I connected via SSH and found lightdm had TWO instances of X running,
one on tty7 and the other on tty8
I could find no clues in any of
** Changed in: xorg-server (Ubuntu)
Status: Expired => Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Low => Medium
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
- The mouse cursor is gone when Oneiric starts. The mouse itself is
+ The mouse cursor is gone when the GUI starts. The mouse itself is
responding, but the pointer is invisible. Very annoying. I do have a
workaround. One must simply restart the lightdm interface with
$ cat /etc/systemd/system/bluetooth.service
.include /lib/systemd/service/bluetooth.service
[Service]
ExecStart=/usr/lib/bluetooth/bluetoothd -d
$ journalctl -fu bluetooth | tee /tmp/bluetooth-multiple-adapters.log
...
Stop/Start bluetooth service
...
Insert 2nd USB adapter
Sep 04
The latest discussion about this on the systemd mailing-list:
http://lists.freedesktop.org/archives/systemd-
devel/2014-August/022014.html
"Also note that we really should redesign the entire scheme around the
kernel keyring as only transport for the keys (and the bus for
signalling). I am a bit
Colormap: 0x20 (installed)
Bit Gravity State: NorthWestGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsViewable
Override Redirect State: no
Corners: +1920+0 -0+0 -0-0 +1920-0
-geometry 1200x1920-0+0
S tj265
Public bug reported:
$ hcitool dev
Devices:
hci100:10:7A:4D:15:33
hci000:1F:3A:E0:0A:AF
$ hcitool -i hci1 scan
Scanning ...
00:0A:95:4B:BD:C2 Apple Wireless Keyboard
$ sudo systemctl restart bluetooth
$ journalctl -u bluetooth | grep adapter_service_add
Public bug reported:
15.10 Wily, amd64:
$ sudo kvm -drive file=/dev/sda,if=scsi -vga std
(process:3535): GLib-WARNING **:
/build/glib2.0-3tdlHy/glib2.0-2.45.6/./glib/gmem.c:482: custom memory
allocation vtable not supported
$ apt-cache policy qemu-kvm
qemu-kvm:
Installed:
Public bug reported:
15.10 Wily, amd64:
$ sudo kvm -drive file=/dev/sda,if=scsi -vga std
(process:3535): GLib-WARNING **:
/build/glib2.0-3tdlHy/glib2.0-2.45.6/./glib/gmem.c:482: custom memory
allocation vtable not supported
$ apt-cache policy qemu-kvm
qemu-kvm:
Installed:
What does this report?
$ sudo lsblk /dev/sdb1
Also, is there an entry referring to it already, possibly with noauto
option?
$ cat /etc/fstab
I'm wondering if you are effected by the mirror side of the issue I was
researching.
In my case systemd is insisting on trying to mount non-existent
So it seems since reconfiguring the Access Point to use mode 'auto' and
channel 'auto' the poor performace has been cured?
The disconnect you report looks to be isolated:
Aug 31 18:00:00 Saria-Lin kernel: [ 7467.759694] wlan0: deauthenticating
from 00:25:9c:9d:47:37 by local choice (Reason:
Currently testing with the v4.2 from wily-proposed with additional
patches for:
PCI: check pref compatible bit for mem64 resource of pcie device
PCI: get new realloc size for bridge that does not have children
workqueue: Make flush_workqueue() available again to non GPL modules
--
You received
Public bug reported:
Is there a way to prevent systemd from creating generator targets for
hot-plug disks?
Currently it is causing very long delays at boot-time - which are not
interruptible by the sys-admin - but I'm not sure at what point systemd
decided those hot-plug devices should be added
Came across this bug looking for another issue. Some observations:
There is no information in this report of the file-system type. It is
file-systems not partitions or devices that are mounted, so any problem
with an unclean file-system could prevent it being auto-mounted.
The partition looks to
Also happening in 15.10 Wily, with lightdm 1.15.3-0ubuntu3
Repeated 3 times per second constantly for about 15 minutes and then
system froze - not sure if this was the cause of the freeze but it was
the only logged info immediately before the freeze.
Sep 1 19:23:43 hephaestion lightdm[951]:
Public bug reported:
With a LUKS > LVM > EXT4 rootfs the update-initramfs hooks scripts do
not include the "allow-discards" option in the generated
/conf/conf.d/cryptroot
This prevents all file-systems contained in the LVM VG LVs from using
the mount option 'discard'.
$ journalctl | grep -B3
Unfortunately, no, due to the GPL symbol change for flush_workqueue,
which prevents DKMS from building the nvidia driver. Looks like mainline
won't get that fix until 4.3:
http://lkml.iu.edu/hypermail/linux/kernel/1508.0/02260.html
WARNING: could not find
My fault, I copied the cryptsetup command-line option "--allow-discards"
into crypttab, instead of using the "discard" option as per "man
crypttab".
Interesting that despite the faulty option discard support was
automatically enabled, despite the strong security warning about using
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
Title:
Wily: hidinput_disconnect BUG: unable to handle kernel NULL pointer
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: linux (Ubuntu)
Status: Expired => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437988
Your IRC conversation indicates the PC also experiences intermittent
issues with the Ps/2 connected Synaptic Touchpad. Hopefully that issue
can be solved with some i8042.XXX kernel parameter.
If not, and combined with this issue, I would suggest a boot-time RAM
test using memtest86+ (available
Public bug reported:
15.10 amd64, kernel BUG when a Bluetooth mouse disconnected due to
battery failure - in other words, an uncommanded disconnect.
$ uname -a
Linux hephaestion.lan.iam.tj 4.1.0-3-lowlatency #3-Ubuntu SMP PREEMPT Tue Jul
28 13:11:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Log
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455110/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
Title:
PREEMPT Tue Jul
28 13:11:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Log attached:
$ journalctl -n 48 | awk '{$1="";$2="";$4="";print $0}'
+ ---
+ ApportVersion: 2.18-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+ USER PID ACCESS COMMAND
+ /dev/snd
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455107/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455109/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455114/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455119/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455111/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455116/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455117/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455108/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455115/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455113/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455118/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1490551/+attachment/4455112/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490551
Public bug reported:
Bluez 5.3 does not have support for pairing with devices (such as
keyboards) that use a PIN code for pairing.
A mouse pairs correctly.
From my research it seems as if the ChromeOS project developed patches
to fix this and they are supposed to have been included in Bluez 5.4
Public bug reported:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1=;$2=;$4=;print $0}'
23:31:53 systemd[1]: Starting Bluetooth
This also occurs from a fresh boot:
Aug 30 23:42:21 hephaestion.lan.iam.tj systemd[1]: Starting Bluetooth service...
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Bluetooth daemon 5.33
Aug 30 23:42:21 hephaestion.lan.iam.tj bluetoothd[793]: Starting SDP server
Aug 30 23:42:21
This may be caused by bug #1490349 15:10: bluetoothd reports Not
enough handles to register service at start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490347
Title:
[Regresision] 15:10 -
This really needs to be solved. Unlocking secure systems that use some
external key device that requires a specific helper script to access is
a significant use case.
According to the Debian bug report discussion it seems that upstream
systemd aren't prepared to finish their replacement
Another attempt, this time with
$ sudo /usr/sbin/bluetoothd -nd
and the log-file is attached.
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
Still affects 15.10 Wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278114
Title:
value of GRUB_ENABLE_CRYPTODISK: util/grub-install.c instructs '1' but
util/config.c expects 'y'
To manage
** Changed in: lvm2 (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490088
Title:
15.10: pvs/pvscan/pvdisplay not recognising PV metadata when lvmetad
is
Public bug reported:
Working on a 14.04 amd64 host with a 15.10 chroot I found that several
PV tools cannot recognise PVs created on 14.04.
As a test on 14.04 I created 2 test loop device files and used pvcreate
on them (loop0 has zero metadata copies).
## In 14.04:
$ sudo losetup -vf
Workaround is:
service lvm2-lvmetad stop
Problem is that lvmetad is designed to cache device metadata on
discovery, which (should) come from specialised udevd rules. In the
chroot there is no init/udevd running so even re-attaching the loop
devices doesn't cause the PVs to be scanned.
There is
** Summary changed:
- 15.10: pvs/pvscan/pvdisplay not recognising PV metadata created by 14.04
+ 15.10: pvs/pvscan/pvdisplay not recognising PV metadata when lvmetad is
running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On Trusty 14.04 LTS, and possibly later releases too (yet to be be
tested) QEMU/KVM USB Host Device pass-through fails when the host has
multiple identical USB devices attached.
When using the GUI to choose a USB Host device those devices are listed
to the user by their USB
Public bug reported:
With Trusty 14.04 LTS documentation suggests that when attaching a Host
USB device that
virsh nodedev-list --tree
can be used to gather the values required for the XML address element
such as:
hostdev mode='subsystem' type='usb' managed='yes'
source
I had to use virsh edit domain to manually add an address
specifier thus:
$ virsh dumpxml Kubuntu14.04
--- 8- snip ---
hostdev mode='subsystem' type='usb' managed='yes'
source
vendor id='0x8564'/
product id='0x1000'/
address bus='2' device='7'/
/source
be required for other PCI devices.
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Useful investigation and follow-up comments from Matthew Garrett's at
his site:
http://mjg59.dreamwidth.org/11750.html
Several users confirm opening the case and disconnecting the battery for
a short time (a couple of minutes) and reconnecting appears to
permanently resolve the issue.
--
You
Returning status to Triaged since there are multiple reports that this
issue is not fixed, and commit dbf0e4c7257f8d6 referred to in comment
#34 is a USB suspend/resume issue, not a power-profile when on battery
issue.
** Changed in: linux (Ubuntu)
Status: Fix Released = Triaged
--
You
There are several reports that the model works fine as far back as 12.04
However, there are several confirmed reports that disconnecting the
internal battery and/or re-insulating its leads, solves the issue. That
suggests a power starvation issue, or that some component remains
powered when the
On 24/08/15 18:11, Ralf Mardorf wrote:
I've followed the issue with interest. Glad you finally identified the cause.
I wonder if smartd ought to be taught to check the power/sleep state of a
device and only query it if it is currently awake/active?
--
Ubuntu-devel-discuss mailing list
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482608
Title:
ssh-add fails to add ed25519 keys
To manage notifications about this
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1482608
Title:
ssh-add fails to add ed25519 keys
To manage
** Description changed:
- drops into busybox (initramfs) on initial boot.
+ Summary:
+
+ Boot drops into busybox (initramfs) on initial boot.
+
+ Cause:
+
+ initrd.img/conf/conf.d/cryptroot gets an entry for a subsidary swap LV
+ added as well as the rootfs when using full disk encryption +
** Description changed:
My Huawei E173 modem is not recognized as a modem anymore after
installing Ubuntu 15.04 and Mainline kernel 4.0 RC6. It worked out of
the box with Ubuntu 14.10.
I tried various guides (editing /etc/modules and
/lib/udev/rules.d/40-usb_modeswitch.rules) but
** Changed in: cryptsetup (Ubuntu)
Status: New = Triaged
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided = High
** Changed in: cryptsetup (Ubuntu)
Assignee: (unassigned) = TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Please report what happens with the stock kernel installed by Ubuntu.
** Changed in: acpid (Ubuntu)
Status: New = Incomplete
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Incomplete
** Changed in: acpid
This may be caused by upstream changes to the Huawei device handling:
Version 2.2.0, 2014/05/29
Introduction of parameter HuaweiNewMode, wrapping the standard bulk
message for all newer Huawei devices; support for generic fall-back
config files, combined with OS switch (per vendor
** Information type changed from Private to Public
** Changed in: xorg-server (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479009
Title:
Xorg crashed
Attached is IRC log of report and diagnosis
** Attachment added: IRC log of report and diagnosis
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477587/+attachment/4433051/+files/irc.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
+
+ -
+
+ (From TJ):
+
+ $ xrandr -q
+ Screen 0: minimum 320 x 200, current 3600 x 1080, maximum 16384 x 16384
+ HDMI-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y
axis) 477mm x 268mm
+1920x1080 60.0
Public bug reported:
The explicit copyright text in each source file is Proprietary all
rights reserved, not open source.
The package copyright file /usr/share/doc/nvidia-340/copyright is less
than ideal and only purports to repeat extracts from an email exchange,
it is not a copyright license.
A note to clarify expectations on an UEFI system.
If the installer boots in UEFI mode the installer detects this through
the presence of the EFI variables node in the sysfs at
/sys/firmware/efi/vars. In this case the grub-efi package and its
dependencies is selected, installed, and configured.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-14.04.3
--
You received this bug
I made configuration changes when the issue originally occurred and
despite reverting the ones I can identify cannot now reproduce the issue
- although I suspect that is because I've forgotten one or more changes
I made.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ SRU request.
+
+ [Impact]
+
There are typos in the postinst script that cause garbage to be written
to /etc/default/miniupnpd resulting in the service failing to start.
- I found these when a user reported they couldn't start the daemon.
+ [Test Case]
- It
This bug was fixed in Debian some time ago and the working package is
carried in 14.10, 15.04 and 15.10.
Can it be backported to 14.04?
** Description changed:
There are typos in the postinst script that cause garbage to be written
to /etc/default/miniupnpd resulting in the service failing
** Description changed:
- SRU request.
+ Security Update and/or SRU request for 14.04.
+
+ There are security fixes to this package in Debian (1.8.20140523-4, in
+ 15.04+) that fix several CVEs and postinst failures (1.8.20130730-3, in
+ 14.10+) . Unfortunately it is not clear precisely which
Public bug reported:
There are typos in the postinst script that cause garbage to be written
to to /etc/default/miniupnod resulting in the service failing to
start.
I found these when a user reported they couldn't start the daemon.
** Affects: miniupnpd (Ubuntu)
Importance: High
** Description changed:
There are typos in the postinst script that cause garbage to be written
- to to /etc/default/miniupnod resulting in the service failing to
- start.
+ to /etc/default/miniupnod resulting in the service failing to start.
I found these when a user reported they
** Description changed:
There are typos in the postinst script that cause garbage to be written
- to /etc/default/miniupnod resulting in the service failing to start.
+ to /etc/default/miniupnpd resulting in the service failing to start.
I found these when a user reported they couldn't
I've published a possibly fixed package for Trusty to my PPA at:
https://launchpad.net/~tj/+archive/ubuntu/nvidia
Please test and report back if that fixes the issue. If it does I can
attach the fixed branch to bug #1431753 where the other release fixes
are being tracked.
** Changed in: nvidia
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) = (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358491
Title
801 - 900 of 2979 matches
Mail list logo
