[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work

[Tudor Holton]

I experienced this same issue today after upgrading to Ubuntu 21.04 also
on a Dell 7140 with the same trackpad.

I followed the above advice:
1. install xserver-xorg-input-synaptics package -> sudo apt install 
xserver-xorg-input-synaptics -y
2. Masking the service fwupd using systemctl mask fwupd.service command

...and my trackpad is now working again.

Kernel 5.4.0-42 isn't packaged for Ubuntu 21.04 so I couldn't do the
last steps, but it seems I didn't need them.

So, from this, it seems that fwupd is trying to do some firmware update
in relation to the trackpad which is giving the trackpad into a hissy
fit.  Disable fwupd, no update.  No update, no problems. :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655

Title:
  [Dell Venue 11 Pro 7140] Trackpad does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1856032] Re: Removable media icon stays on the dock after eject.

[Tudor Holton]

I can confirm that this still occurs on 20.10.  Is there a workaround to
remove the icon from the dash after ejecting?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856032

Title:
  Removable media icon stays on the dock after eject.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1856032/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

Hi Christopher,

1) I tried removing iwlwifi and iwlmvm and then suspending.  In both
kernel 4.20.3 and 5.0.0-rc2 the result was the same.

I tried just leaving the system to run *without suspending*, and I found
that the system would lock up after a few minutes anyway.  The memory
steadily increased (but nowhere near full) and the system load hit 5
(out of 4 CPUs).  In both cases jbd2 was consuming 100% CPU at the time
it locked up.  I would normally think this was a disk issue in this case
but I can't replicate it on Ubuntu kernel 4.18 (and I use this machine
all day every day) so I don't think the issue is faulty hardware.

2) On a short suspend/resume cycle (before the system locked up) I
resumed and reenabled the module.  This time Network Manager appeared to
connect, however the system locked up very shortly after that.

I think there is a deeper issue here.  Perhaps with jbd2 or kworker.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 4.20.3 showing dmesg error kernel write locking 
up. Page 1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230630/+files/IMG_20190120_171547.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 4.20.3 showing dmesg error kernel write locking 
up. Page 2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230631/+files/IMG_20190120_171558.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write 
locking up. Page 3"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230627/+files/IMG_20190120_171227.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 5.0.0-rc2 showing dmesg and sync locking up."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230624/+files/IMG_20190120_170833.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write 
locking up. Page 1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230625/+files/IMG_20190120_171139.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write 
locking up. Page 2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230626/+files/IMG_20190120_171209.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write 
locking up. Page 4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230628/+files/IMG_20190120_171242.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 4.20.3 showing dmesg error kernel write locking 
up. Page 3"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230632/+files/IMG_20190120_171610.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write 
locking up. Page 5"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230629/+files/IMG_20190120_171250.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

For @penalvch:

1) $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A17
09/10/2018

2) I tried with kernel 4.20.3 and got a similar result to above (with
the "Not Tainted" Network Manager), however after suspending and
resuming, the machine consistently locks up as soon as the disk is
written to, meaning that I couldn't even get a copy of the report!

In 5.0.0-rc2, there is no complaint from the kernel, however, the WiFi
adapter still doesn't work and the machine also locks up consistently
after the resume so I couldn't get a report from that either!  :-(

(I can probably grab a photo with my phone if you really need it.)

If it had just been a case of the WiFi adapter not working, I'd say this
was fixed, but I think the locking up in mainline kernels may indicate a
deeper problem from the suspend.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

Ok.  I've had some partial success with the addition of:

[Sleep]
SuspendState=freeze

in /etc/systemd/sleep.conf

However, I also lose the wifi in the process.  The kernel reports:

[   69.744693] [ cut here ]
[   69.744695] Timeout waiting for hardware access (CSR_GP_CNTRL 0x)
[   69.744730] WARNING: CPU: 2 PID: 1323 at 
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2008 
iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi]
[   69.744731] Modules linked in: usbhid rfcomm pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac ipmi_devintf ipmi_msghandler 
bnep binfmt_misc nls_iso8859_1 snd_soc_sst_broadwell dell_wmi wmi_bmof 
snd_soc_sst_haswell_pcm snd_soc_sst_firmware snd_soc_sst_ipc snd_soc_sst_dsp 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel dell_laptop pcbc 
dell_smbios dell_wmi_descriptor dcdbas aesni_intel aes_x86_64 crypto_simd 
cryptd glue_helper intel_cstate intel_rapl_perf joydev snd_hda_codec_hdmi 
cdc_mbim serio_raw cdc_acm btusb cdc_wdm uvcvideo btrtl arc4 cdc_ncm 
snd_soc_rt298 btbcm input_leds btintel videobuf2_vmalloc usbnet 
videobuf2_memops mii bluetooth videobuf2_v4l2 videobuf2_common snd_hda_intel 
videodev
[   69.744760]  ecdh_generic media snd_hda_codec iwlmvm snd_hda_core mac80211 
hid_sensor_incl_3d snd_soc_rt286 snd_hwdep hid_sensor_rotation i915 
snd_soc_rl6347a snd_seq_midi snd_soc_core iwlwifi snd_compress 
snd_seq_midi_event ac97_bus snd_rawmidi snd_pcm_dmaengine snd_pcm 
hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_als hid_sensor_accel_3d 
hid_sensor_trigger industrialio_triggered_buffer kfifo_buf snd_seq 
drm_kms_helper hid_sensor_iio_common hid_multitouch drm cfg80211 industrialio 
snd_seq_device snd_timer mac_hid wmi i2c_algo_bit fb_sys_fops mei_me snd 
dw_dmac syscopyarea intel_vbtn sysfillrect sysimgblt dw_dmac_core 
snd_soc_sst_acpi processor_thermal_device snd_soc_acpi soc_button_array 
int3400_thermal soundcore video int3403_thermal mei snd_soc_acpi_intel_match 
sparse_keymap acpi_thermal_rel
[   69.744786]  int340x_thermal_zone intel_soc_dts_iosf acpi_pad sch_fq_codel 
parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 mmc_block 
hid_sensor_custom hid_sensor_hub hid_generic sdhci_pci cqhci sdhci ahci 
i2c_i801 libahci lpc_ich i2c_hid hid [last unloaded: usbhid]
[   69.744801] CPU: 2 PID: 1323 Comm: NetworkManager Tainted: G   OE
 4.18.0-13-generic #14-Ubuntu
[   69.744801] Hardware name: Dell Inc. Venue 11 Pro 7140/0XMVMH, BIOS A17 
09/10/2018
[   69.744807] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi]
[   69.744807] Code: 2f f9 49 8d 56 08 bf 00 20 00 00 e8 d2 15 d2 f7 e9 31 ff 
ff ff 89 c6 48 c7 c7 50 b4 5a c0 c6 05 6f 6c 02 00 01 e8 ca 3c d0 f7 <0f> 0b e9 
ec fe ff ff 48 8b 7b 30 48 c7 c1 b8 b4 5a c0 31 d2 31 f6 
[   69.744830] RSP: 0018:ba2501ecb190 EFLAGS: 00010086
[   69.744831] RAX:  RBX: 965a4f7f0018 RCX: 0006
[   69.744832] RDX: 0007 RSI: 0086 RDI: 965a5e5164b0
[   69.744833] RBP: ba2501ecb1b0 R08: 0001 R09: 03a9
[   69.744834] R10: 0004 R11:  R12: 965a4f7f8f50
[   69.744834] R13: ba2501ecb1c0 R14:  R15: 965a4f7f0220
[   69.744836] FS:  7f8e1b5e5bc0() GS:965a5e50() 
knlGS:
[   69.744837] CS:  0010 DS:  ES:  CR0: 80050033
[   69.744837] CR2: 55f0beff4010 CR3: 0001fd4e2001 CR4: 003606e0
[   69.744838] DR0:  DR1:  DR2: 
[   69.744839] DR3:  DR6: fffe0ff0 DR7: 0400
[   69.744840] Call Trace:
[   69.744846]  iwl_write_prph+0x3d/0x90 [iwlwifi]
[   69.744852]  iwl_pcie_apm_init+0x1db/0x240 [iwlwifi]
[   69.744858]  iwl_trans_pcie_start_hw+0x52/0x1d0 [iwlwifi]
[   69.744864]  iwl_mvm_up+0x3c/0x9c0 [iwlmvm]
[   69.744867]  ? skb_dequeue+0x59/0x70
[   69.744869]  ? wireless_nlevent_flush+0x78/0x80
[   69.744874]  __iwl_mvm_mac_start+0x29b/0x300 [iwlmvm]
[   69.744880]  iwl_mvm_mac_start+0x4c/0x130 [iwlmvm]
[   69.744882]  ? inetdev_event+0x77/0x500
[   69.744896]  drv_start+0x48/0x100 [mac80211]
[   69.744909]  ieee80211_do_open+0x436/0x840 [mac80211]
[   69.744922]  ieee80211_open+0x52/0x60 [mac80211]
[   69.744924]  __dev_open+0xd5/0x170
[   69.744925]  __dev_change_flags+0x184/0x1f0
[   69.744926]  dev_change_flags+0x27/0x60
[   69.744928]  do_setlink+0x307/0xe10
[   69.744933]  ? iwl_pcie_txq_inc_wr_ptr+0x97/0x110 [iwlwifi]
[   69.744936]  ? nla_parse+0xbf/0xe0
[   69.744938]  ? inet6_validate_link_af+0x4f/0x70
[   69.744939]  ? nla_parse+0x35/0xe0
[   69.744941]  rtnl_newlink+0x511/0x8c0
[   69.744943]  ? __snmp6_fill_stats64.isra.57+0xf6/0x120
[   69.744945]  ? __nla_reserve+0x41/0x50
[   69.744946]  ? __nla_put+0x20/0x30
[   69.744949]  ? _raw_read_unlock_bh+0x20/0x30
[   69.744950] 

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

Well I just upgraded to 18.04 and I'm afraid it doesn't work for me.
Suspend instead ends up in a state where the only option is to force a
power reset.

This is why you should give the OP time to check.

** Changed in: linux (Ubuntu)
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

I mean I upgraded to 18.10 from 18.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

...especially since the bug has been open for over 3 years and we have
seen 6 releases in that time. Less than 2 days from release it a little
unfair, don't you think?

Unless you have the same hardware and are able to verify the bug as
described??

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

I stand corrected.  Even still, it would be nice to give the OP (that
being me) at least a couple of days to install the new version and test
it before declaring it fixed. :-|

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

Except that Ubuntu 18.10 ships with Linux 4.15.  So unless the fix has
been backported it won't be fixed released yet.

** Changed in: linux (Ubuntu)
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753263] Re: GNOME Power Statistics shows nothing on Ubuntu 18.04

[Tudor Holton]

/proc/timer_stats was enabled when the kernel was compiled with
CONFIG_TIMER_STATS=y

However, this was removed from the kernel in February 2017,  see this commit 
log:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.19-rc6=20dcfe1b7df4072a3c13bdb7506f7138125d0099

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753263

Title:
  GNOME Power Statistics shows nothing on Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1753263/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: [Dell Venue 11 Pro 7140] Power button not working

[Tudor Holton]

Ubuntu 17.10 now triggers the power dialog when the power button is
pressed.

** Changed in: linux (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  [Dell Venue 11 Pro 7140] Power button not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: [Dell Venue 11 Pro 7140] Power button not working

[Tudor Holton]

Yes.  When I press the power button now I get the power dialog.  Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  [Dell Venue 11 Pro 7140] Power button not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728465] [NEW] Mouse pointer disappears on client in 17.10

[Tudor Holton]

Public bug reported:

When using synergy as a client on Ubuntu 17.10, the mouse disappears
whenever it enters the screen.

This bug has been reported in public Symless forums, also here:
https://symless.com/forums/topic/4393-no-mouse-and-keyboard-input-on-
ubuntu-1710-client/

If the display manager is changed to "Ubuntu" then the mouse pointer does not 
show.
If the display manager is changed to "Ubuntu on xorg" then the mouse pointer is 
displayed.

In both cases, the mouse actually works, it just isn't shown in the
default setting.

There are other bugs in "Ubuntu on xorg" that make this not an ideal
solution.

** Affects: synergy (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728465

Title:
  Mouse pointer disappears on client in 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/synergy/+bug/1728465/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720511] Re: Failed to create the apt-file cache /usr/share/apt-file/do-apt-file-update (no such file or directory)

[Tudor Holton]

do-apt-file-update was in zesty:
https://packages.ubuntu.com/search?suite=zesty=any=exactfilename=contents=do-apt-file-update

but is not in artful:
https://packages.ubuntu.com/search?suite=artful=any=exactfilename=contents=do-apt-file-update

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720511

Title:
  Failed to create the apt-file cache /usr/share/apt-file/do-apt-file-
  update (no such file or directory)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-file/+bug/1720511/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1588131] Re: package keystone 2:9.0.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Tudor Holton]

Isn't this something apt is supposed to handle?  I thought if you
specify that the upgrade path has to go through a previous version, then
it gets that version and follows the trail back.  No?  If I'm correct
then it's a config fault.  How do the packages do it that have multiple
DB structure changes?  They can't have every possible upgrade path in
there, surely?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588131

Title:
  package keystone 2:9.0.0-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1588131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1588131] Re: package keystone 2:9.0.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Tudor Holton]

Hi Corey,
All the versioning information is at the bottom of the first post.
Cheers,
Tudor

** Changed in: keystone (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/1588131

Title:
  package keystone 2:9.0.0-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1588131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632506] [NEW] Onscreen Keyboard is too far away and not obvious

[Tudor Holton]

Public bug reported:

Placing the onscreen keyboard in a menu puts it too far away from the
user (2-clicks) and non-obvious.

Most modern UIs have a single button to trigger the onscreen keyboard,
and this is usually indicated quite clearly by a keyboard-looking icon.

Unity, however, puts this in a non-descript menu with an icon consisting
of only 4 squares.  The user has to know what this means, at first.  If
the user does manage to work out that this is where the keyboard can be
triggered, again the option is unclear.  Instead of "Onscreen keyboard"
we have "Show onboard".  No mention of a keyboard at all!

I understand that this design decision was probably made when
touchscreens were rare and mainly used for accessibility.  The people
who did use it probably didn't switch it on and off regularly.  However,
with the advent of tablets without keyboards it's normal user behaviour
to switch the keyboard on and off regularly as needed.  Thus the current
behaviour seems non-intuitive and frustrating in this context. 2-clicks
is 1-click too many.

I also understand that this is technically an applet.  However, the
indicator is triggered by the Unity setting "On Screen Keyboard" so I
see this as a Unity issue.  Maybe we need to choose/build a better
indicator?  Is there something we can use from a newer Unity UI?

In summary:
- "Show onboard" should be moved out of a menu and into an icon that clearly 
depicts a keyboard.
- We should invert or colour the icon when it is in use.
- All other options currently in that menu ("Preferences", "Help") can be moved 
to Settings

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: touch

** Attachment added: "The accessibility indicator dropdown menu showing "Show 
Onboard" which activates the onscreen keyboard."
   
https://bugs.launchpad.net/bugs/1632506/+attachment/4759636/+files/slice_0_1.gif

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632506

Title:
  Onscreen Keyboard is too far away and not obvious

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1632506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1588131] [NEW] package keystone 2:9.0.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Tudor Holton]

Public bug reported:

Setting up keystone (2:9.0.0-0ubuntu1) ...
2016-06-02 12:42:43.180 17865 CRITICAL keystone [-] KeyError: 
2016-06-02 12:42:43.180 17865 ERROR keystone Traceback (most recent call last):
2016-06-02 12:42:43.180 17865 ERROR keystone   File "/usr/bin/keystone-manage", 
line 10, in 
2016-06-02 12:42:43.180 17865 ERROR keystone sys.exit(main())
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/keystone/cmd/manage.py", line 47, in main
2016-06-02 12:42:43.180 17865 ERROR keystone cli.main(argv=sys.argv, 
config_files=config_files)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py", line 992, in main
2016-06-02 12:42:43.180 17865 ERROR keystone CONF.command.cmd_class.main()
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py", line 371, in main
2016-06-02 12:42:43.180 17865 ERROR keystone 
migration_helpers.sync_database_to_version(extension, version)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/keystone/common/sql/migration_helpers.py", 
line 210, in sync_database_to_version
2016-06-02 12:42:43.180 17865 ERROR keystone _sync_common_repo(version)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/keystone/common/sql/migration_helpers.py", 
line 136, in _sync_common_repo
2016-06-02 12:42:43.180 17865 ERROR keystone init_version=init_version, 
sanity_check=False)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration.py", line 79, in 
db_sync
2016-06-02 12:42:43.180 17865 ERROR keystone migration = 
versioning_api.upgrade(engine, repository, version)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186, in 
upgrade
2016-06-02 12:42:43.180 17865 ERROR keystone return _migrate(url, 
repository, version, upgrade=True, err=err, **opts)
2016-06-02 12:42:43.180 17865 ERROR keystone   File "", line 
2, in _migrate
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py", line 
160, in with_engine
2016-06-02 12:42:43.180 17865 ERROR keystone return f(*a, **kw)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 345, in 
_migrate
2016-06-02 12:42:43.180 17865 ERROR keystone changeset = 
schema.changeset(version)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 82, in 
changeset
2016-06-02 12:42:43.180 17865 ERROR keystone changeset = 
self.repository.changeset(database, start_ver, version)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/migrate/versioning/repository.py", line 225, 
in changeset
2016-06-02 12:42:43.180 17865 ERROR keystone changes = 
[self.version(v).script(database, op) for v in versions]
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/migrate/versioning/repository.py", line 189, 
in version
2016-06-02 12:42:43.180 17865 ERROR keystone return 
self.versions.version(*p, **k)
2016-06-02 12:42:43.180 17865 ERROR keystone   File 
"/usr/lib/python2.7/dist-packages/migrate/versioning/version.py", line 163, in 
version
2016-06-02 12:42:43.180 17865 ERROR keystone return 
self.versions[VerNum(vernum)]
2016-06-02 12:42:43.180 17865 ERROR keystone KeyError: 
2016-06-02 12:42:43.180 17865 ERROR keystone

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keystone 2:9.0.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
Uname: Linux 3.13.0-87-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Thu Jun  2 12:35:22 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-12-05 (910 days ago)
InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: keystone
Title: package keystone 2:9.0.0-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-06-02 (0 days ago)

** Affects: keystone (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588131

Title:
  package keystone 2:9.0.0-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications 

[Bug 43363] Re: network: should list NFS shares too

[Tudor Holton]

*** This bug is a duplicate of bug 24430 ***
https://bugs.launchpad.net/bugs/24430

I've also written about the fact that nfs:// as a prefix doesn't work in
Nuatilus->Connect to Server  on 15.10 either.
http://askubuntu.com/questions/748397/how-do-i-mount-nfs-through-
nautilus

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/43363

Title:
  network: should list NFS shares too

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/43363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1541649] [NEW] Plymouth needs a safe method to unlock the device on boot without a physical keyboard.

[Tudor Holton]

Public bug reported:

My tablet is encrypted, and I'm presented with the plymouth decryption
screen during every boot.  However, there is no onscreen keyboard,
causing me to have to dig out a keyboard just to start the machine.

I'd imagine as this goes along we're going to get more and more
keyboardless devices.  Windows has already solved this.

I disagree with the comments in bug
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1239004 which is
closely related to this.

The simplest way is to implement an onscreen keyboard.  Obviously, it
would have to support everything that could be in a physical keyboard,
tho, or people could lock it with a physical keyboard and then find they
can't unlock it with an onscreen one due to a missing symbol.

Another idea would be not to use a keyboard at all.  We could instead use:
(a) a USB key (which has the (dis)advantage of being crackable programmatically)
(b) a sequence of vectors, like phones do (but there's a security risk since on 
some screens you can see the mark where it's been done repeatedly)
(c) a voice print (fakeable)
(d) a voice password (security risk due to being heard)
(e) a camera image (also fakeable)
(f) randomised visual word ordering with decoys and fail2ban scenarios.

I believe that the safest and most reliable way is simply to use an
onscreen keyboard, however, creating an encryption hook into plymouth
could allow other methods to be used.  (f) could also work, tho and may
be considerably easier to implement.

** Affects: plymouth (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541649

Title:
  Plymouth needs a safe method to unlock the device on boot without a
  physical keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1541649/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477859] Re: Onboard Audio not working on Dell Venue 11 Pro 7140

[Tudor Holton]

Also, SPK Mux needs to be set to Front to have the audio come out of
the device speakers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477859

Title:
  Onboard Audio not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477859] Re: Onboard Audio not working on Dell Venue 11 Pro 7140

[Tudor Holton]

It works!   In mainline kernel 4.2.0-rc5, if you go into alsamixer and
unmute the SPO channel, then suddenly there's playback! :-D

** Tags removed: kernel-bug-exists-upstream-4.2-rc5
** Tags added: kernel-bug-fixed-upstream-4.2-rc5

** Tags added: latest-bios-a07

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477859

Title:
  Onboard Audio not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1464757] Re: Audio broken on Dell Venue 11 Pro 7140

[Tudor Holton]

It's not quite that simple.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464757 points out
that you still have to unmute the SPO channel in alsamixer to actually
get sound.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464757

Title:
  Audio broken on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477859] Re: Onboard Audio not working on Dell Venue 11 Pro 7140

[Tudor Holton]

Getting closer!  Mainline kernel 4.2.0-rc5 shows the rt286 audio just
like 4.1.3 did, and the touchscreen is back!  However, there's still no
sound. :-(  It behaves like it's playing, tho.  I've checked and
pavucontrol shows everything is there and the sound is showing on the
audiometer.  Nothing appears to be muted.  I've muted and unmuted things
a few times but no go.

I also tried with and without acpi_osi=Windows 2013.  No effect.  I
understand, tho, that from 4.2.0 onwards, this flag is no longer
required?

** Tags added: kernel-bug-exists-upstream-4.2-rc5

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477859

Title:
  Onboard Audio not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477859] Re: Onboard Audio not working on Dell Venue 11 Pro 7140

[Tudor Holton]

FYI, currently I'm testing on BIOS revision A07.  This is the latest on
the Dell website as of today.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477859

Title:
  Onboard Audio not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477859] Re: Onboard Audio not working on Dell Venue 11 Pro 7140

[Tudor Holton]

Mainline kernel 4.1.3-040103 sees the rt286 device appear.  However,
there is no actual sound. :-(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477859

Title:
  Onboard Audio not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: [Dell Venue 11 Pro 7140] Power button not working

[Tudor Holton]

http://www.spinics.net/lists/linux-input/msg40163.html

** Tags removed: kernel-bug-exists-upstream-4.2-rc3
** Tags added: kernel-bug-exists-upstream-4.2-rc4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  [Dell Venue 11 Pro 7140] Power button not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477859] Re: Onboard Audio not working on Dell Venue 11 Pro 7140

[Tudor Holton]

No go on 4.2-rc4-unstable

** Tags added: kernel-bug-exists-upstream-4.2-rc3 kernel-bug-exists-
upstream-4.2-rc4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477859

Title:
  Onboard Audio not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: resume-trace
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/4435117/+files/dmesg.txt

** Tags added: kernel-bug-exists-upstream-4.2-rc4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

I'm attaching the wakeup and resume-trace scripts.  Am I reading it
right that it has something to do with
/home/kernel/COD/linux/drivers/base/power/main.c:1065 ?

** Attachment added: wakeup
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/4435116/+files/wakeup

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477859] [NEW] Onboard Audio not working on Dell Venue 11 Pro 7140

[Tudor Holton]

Public bug reported:

No input or output devices appear in Sound Settings unless HDMI is
plugged in.  So the audio card is working but not detecting the onboard
audio inputs or outputs for some reason.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic 3.19.0.23.22
ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
Uname: Linux 3.19.0-23-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tudor  1774 F pulseaudio
Date: Fri Jul 24 17:27:39 2015
HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e
InstallationDate: Installed on 2015-07-06 (17 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
MachineType: Dell Inc. Venue 11 Pro 7140
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-23-generic 
root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash 
i915.i915_enable_rc6=1 acpi_osi=!Windows 2013 vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-23-generic N/A
 linux-backports-modules-3.19.0-23-generic  N/A
 linux-firmware 1.143.2
SourcePackage: linux
SystemImageInfo:
 current build number: 0
 device name: 
 channel: daily
 last update: Unknown
UpgradeStatus: Upgraded to vivid on 2015-07-07 (17 days ago)
dmi.bios.date: 06/30/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Venue 11 Pro 7140
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477859

Title:
  Onboard Audio not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1477859] Re: Onboard Audio not working on Dell Venue 11 Pro 7140

[Tudor Holton]

No go on 4.2-rc3-unstable.

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477859

Title:
  Onboard Audio not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: Power button not working on Dell Venue 11 Pro 7140

[Tudor Holton]

** Tags added: kernel-bug-exists-upstream

** Tags added: kernel-bug-exists-upstream-4.2-rc3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  Power button not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: Power button not working on Dell Venue 11 Pro 7140

[Tudor Holton]

** Tags added: kernel-bug-exists-upstream-4.2-rc2

** 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/1472478

Title:
  Power button not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

** Tags added: kernel-bug-exists-upstream-4.2-rc2

** 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/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: Power button not working on Dell Venue 11 Pro 7140

[Tudor Holton]

Sorry.  No go on latest mainline kernel.  (It gets worse.  Touchscreen
doesn't work at all!)  Anyhoo, here's the output:

$ uname -a
Linux kneetm 4.2.0-040200rc2-generic #201507121935 SMP Sun Jul 12 23:36:39 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
$ sudo evtest /dev/input/event1
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x1 version 0x0
Input device name: Power Button
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 116 (KEY_POWER)
Properties:
Testing ... (interrupt to exit)
^C

[No output from pressing button]

$ cat /sys/firmware/acpi/interrupts/ff_pwr_btn 
   0   invalid

$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  Power button not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

Sorry.  No go.

$ uname -a
Linux kneetm 4.2.0-040200rc2-generic #201507121935 SMP Sun Jul 12 23:36:39 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
$ sudo pm-suspend

[Screen goes blank, power light goes off, but can't restart it from the
power button]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1311568] Re: [desktoptouch] Cannot scroll content through touch

[Tudor Holton]

Still not working in 15.04 vivid.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311568

Title:
  [desktoptouch] Cannot scroll content through touch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1311568/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472832] [NEW] Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

Public bug reported:

Instead of suspending the machine into a state where it can be started
quickly, it appears that suspend causes the system to end up in a state
which requires a forced start.  The power light is off, and the only way
to start the machine again is to hold down the power button for more
than 5 seconds. A quick check of uptime shows that it did, indeed, start
again.

I'm attaching a suspend log.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic (not installed)
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tudor  1785 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul  9 10:57:38 2015
HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e
InstallationDate: Installed on 2015-07-06 (2 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. 
 Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Venue 11 Pro 7140
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash 
i915.i915_enable_rc6=1 acpi_osi=!Windows 2013 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-22-generic N/A
 linux-backports-modules-3.19.0-22-generic  N/A
 linux-firmware 1.143.1
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago)
dmi.bios.date: 06/30/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Venue 11 Pro 7140
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

** Attachment added: pm-suspend.log
   
https://bugs.launchpad.net/bugs/1472832/+attachment/4426622/+files/pm-suspend.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472832

Title:
  Suspend issue with Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: Power button not working on Dell Venue 11 Pro 7140

[Tudor Holton]

I upgraded to linux-image-3.19.0-22 but this issue still occurs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  Power button not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] [NEW] Power button not working on Dell Venue 11 Pro 7140

[Tudor Holton]

Public bug reported:

When pressing the power button on the Dell Venue 11 Pro 7140 there is no
reaction. dmesg and showkey are not detecting any key event when
pressing the power button.

This is identical to the RedHat bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1194632

Here are my details:
$sudo evtest /dev/input/event1
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x1 version 0x0
Input device name: Power Button
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 116 (KEY_POWER)
Properties:
Testing ... (interrupt to exit)

[Pressing button gives no output]

$cat /sys/firmware/acpi/interrupts/ff_pwr_btn
   0   invalid

I've attached the acpidata.dat file as well as the minimum requirements.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic (not installed)
ProcVersionSignature: Ubuntu 3.16.0-43.58-generic 3.16.7-ckt13
Uname: Linux 3.16.0-43-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tudor  1763 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jul  8 14:19:01 2015
HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e
InstallationDate: Installed on 2015-07-06 (1 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 004: ID 114d:1002 Alpha Imaging Technology Corp. 
 Bus 001 Device 003: ID 0bda:5757 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Venue 11 Pro 7140
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-43-generic 
root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash 
i915.i915_enable_rc6=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-43-generic N/A
 linux-backports-modules-3.16.0-43-generic  N/A
 linux-firmware 1.143.1
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-07-07 (0 days ago)
dmi.bios.date: 06/30/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Venue 11 Pro 7140
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

** Attachment added: ACPI Data File
   
https://bugs.launchpad.net/bugs/1472478/+attachment/4426100/+files/acpidata.dat

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  Power button not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: Power button not working on Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: lspci-vnvn.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+attachment/4426117/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  Power button not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: Power button not working on Dell Venue 11 Pro 7140

[Tudor Holton]

** Attachment added: version.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+attachment/4426116/+files/version.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  Power button not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472478] Re: Power button not working on Dell Venue 11 Pro 7140

[Tudor Holton]

This device was originally on BIOS version A04.   I have also upgraded
it to BIOS version A07 but the problem still exists.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472478

Title:
  Power button not working on Dell Venue 11 Pro 7140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1354972] Re: 14.04.1 released but do-release-upgrade reports No new release found

[Tudor Holton]

It's possible that this bug is deliberate, and the cause may be concern
over bug #1252843.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354972

Title:
  14.04.1 released but do-release-upgrade reports No new release found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1354972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1354972] [NEW] 14.04.1 released but do-release-upgrade reports No new release found

[Tudor Holton]

Public bug reported:

I am currently receiving this warning every time I log in:

Your current Hardware Enablement Stack (HWE) is no longer supported
---snip for brevity---

* Upgrade from Ubuntu 12.04 LTS to Ubuntu 14.04 LTS by running:
sudo do-release-upgrade 

---snip for brevity---

However, when I do sudo do-release-upgrade this reports:

Checking for a new Ubuntu release
No new release found

I understand that the policy is that LTS servers should not be upgraded
until .1, however .1 was released over a week ago.

I believe this is an administrative bug.  Since
UpdateManager.Core.MetaRelease references the URL
http://changelogs.ubuntu.com/meta-release-lts which does not yet contain
14.04.

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354972

Title:
  14.04.1 released but do-release-upgrade reports No new release found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1354972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349650] [NEW] Deadline warnings should use international date format.

[Tudor Holton]

Public bug reported:

I just had this message appear on my server:

Your current Hardware Enablement Stack (HWE) is going out of support
on 07/08/14.  After this date security updates for critical parts (kernel
and graphics stack) of your system will no longer be available.

Being as I'm in a country that uses MM/DD/YY, I read this as July 8 (in
the past) and was about to submit a bug report regarding the upgrade
from 12.04 to 14.04 being unavailable (because do-release-upgrade
(without -d) is still unaware of stable 14.04 at this time).  Then I
read the associated wiki, and realised that this deadline is actually in
the future.

Can we please always list deadline warnings in the unambiguous -MM-
DD format, please?  Or break out the month into letters so it's clearer.

Thanks.

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349650

Title:
  Deadline warnings should use international date format.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1349650/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1167890] Re: Only supports adding VLAN up to 100

[Tudor Holton]

Has there been movement on this?  On the surface it looks like a
qualifier for 1000 cuts, particularly since most cloud VLANs start at
100 by default, in my experience.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167890

Title:
  Only supports adding VLAN up to 100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1167890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1167890] Re: Only supports adding VLAN up to 100

[Tudor Holton]

If you're looking for a quick solution to this:

1) Create a VLAN connection using the GUI

2) Edit the file /etc/NetworkManager/system-connections/[VLAN
Connection]

3) Under [vlan] change the id to your proper id

4a) Reboot, or

4b) i)Delete the link on the command line:  ip link del [vlan]

ii) Restart NetworkManager: service network-manager restart

Now your vlan should be working.

*Warning: The GUI will still show the VLAN ID as 100.  If you don't edit
it, it won't edit the file.*

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167890

Title:
  Only supports adding VLAN up to 100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1167890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157643] Re: procps fail to start

[Tudor Holton]

Yes, in my case it was /etc/sysctl.d/30-iscsitarget.conf that was
causing the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157643

Title:
  procps fail to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157643] Re: procps fail to start

[Tudor Holton]

Danny Lawson's fix didn't work for me either.  :-(  And I have a
slightly different result for that command:

# cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sudo sysctl -p -
kernel.printk = 4 4 1 7
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.tcp_syncookies = 1
kernel.yama.ptrace_scope = 1
vm.mmap_min_addr = 65536
net.core.wmem_max = 1048576
net.core.rmem_max = 1048576
net.core.wmem_default = 1048576
net.core.rmem_default = 1048576
error: Invalid argument setting key net.ipv4.tcp_mem
net.ipv4.tcp_rmem = 1048576
net.ipv4.tcp_wmem = 1048576
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.ip_forward = 1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157643

Title:
  procps fail to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 631830] Re: `xdg-open` handles IRC URIs incorrectly

[Tudor Holton]

This appears to have worsened.  xdg-open irc://irc.gnome.org/banshee now
calls gvfs-open, too!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/631830

Title:
  `xdg-open` handles IRC URIs incorrectly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/631830/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 917269] [NEW] Progress bar could be more friendly by telling user to make tea for long operations.

[Tudor Holton]

Public bug reported:

It would be nice if the plymouth progress bar could make a rough time
estimate and then provide some text advising the user.  Currently it
progresses in percentages, and the user has to estimate time relative to
the percentage.

For example, on a machine with 1TB of disk space, a file system check at
boot can take several minutes.In such long periods it would be nice
to tell the user it will be a few minutes or even go so far as to say
to Enough time to make a cup of your favourite hot beverage or some
such.

** Affects: plymouth (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: fsck progressbar time

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917269

Title:
  Progress bar could be more friendly by telling user to make tea for
  long operations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/917269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 917269] Re: Progress bar could be more friendly by telling user to make tea for long operations.

[Tudor Holton]

If the texts for these time advisory notices were in a text file
somewhere then it could be part of a theme so that different sentences
could be used for different languages or environments.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917269

Title:
  Progress bar could be more friendly by telling user to make tea for
  long operations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/917269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 917269] Re: Progress bar could be more friendly by telling user to make tea for long operations.

[Tudor Holton]

I'm pretty sure this is a wishlist item, but for some reason launchpad
won't let me mark it as such.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917269

Title:
  Progress bar could be more friendly by telling user to make tea for
  long operations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/917269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 121967] Re: Fingerprint reader as scroll wheel

[Tudor Holton]

@Brad  Sorry, why would I need to provide logs?   This is a wishlist
item about a proposed feature relating to using a fingerprint scanner as
a scrollwheel in non-security-related situations.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121967

Title:
  Fingerprint reader as scroll wheel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/121967/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 579854] Re: Partner packages should reflect proper license info

[Tudor Holton]

Question 142628 relates to this bug.  https://answers.launchpad.net
/software-center/+question/142628

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/579854

Title:
  Partner packages should reflect proper license info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/579854/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 849076] [NEW] Add diaspora to the list of broadcast account types.

[Tudor Holton]

Public bug reported:

Diaspora is an open source, free, modifiable social networking software
in the same vein as facebook.  We should support it as a protocol
alongside the existing twitter, identi.ca, and facebook.

** Affects: indicator-me
 Importance: Undecided
 Status: New

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: disapora

** Tags added: disapora

** Also affects: ubuntu
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849076

Title:
  Add diaspora to the list of broadcast account types.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-me/+bug/849076/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 849076] Re: Add diaspora to the list of broadcast account types.

[Tudor Holton]

For more info on disapora see https://joindiaspora.com/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849076

Title:
  Add diaspora to the list of broadcast account types.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-me/+bug/849076/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 849076] Re: Add diaspora to the list of broadcast account types.

[Tudor Holton]

Can someone make this a wishlist item, please?  I don't seem to have
enough privileges to change the status.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849076

Title:
  Add diaspora to the list of broadcast account types.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-me/+bug/849076/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 435183] Re: Doesn't display information about exact software license

[Tudor Holton]

Has there been any movement on this bug?   I have an open question that
directly relates to it at https://answers.launchpad.net/software-
center/+question/142628 , particularly in relation to skovprodukter's
question in this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/435183

Title:
  Doesn't display information about exact software license

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/435183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 759338] [NEW] snd-hda-intel locks sound resource on ALC269

[Tudor Holton]

Interestingly, calling padsp jmstudio works.

I don't know where that leaves us.  Why would it work without padsp on
one chip, but require it on another in using the same kernel module?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/759338

Title:
  snd-hda-intel locks sound resource on ALC269

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 759338] [NEW] snd-hda-intel locks sound resource on ALC269

[Tudor Holton]

Public bug reported:

I've been using the Java Media Framework on Ubuntu for awhile.  It works
really well across OSs.

However, on my Acer AS 1810TZ, any Java Virtual Machine that uses JMF locks up 
the sound so no other application (not even other JMF VMs) can play audio.  If 
any application attempts to play audio, the following message it logged to 
syslog:
pulseaudio[5303]: alsa-sink.c: Error opening PCM device front:0: Device or 
resource busy

This message is logged every time another piece of audio is played until
the Virtual Machine exits.

There is no other warning relating to this happening.  Sound will
pretend to play in flashplayer and other JMF VMS, for example.
Rhythmbox pretends to play but does not move the slider.

When the application causing the lock exits, a loud noise is emitted
from the speaker that sounds like the entire audio has been buffered and
then played in a split second.

The details of my soundcard are here:
http://www.alsa-project.org/db/?f=f7656fbd90e6b1e08c1faeb774f07ec434982d9b

Interestingly, I have another laptop with the same version of Ubuntu,
and also with snd-hda-intel module used which doesn't exhibit this
problem.  However, it's a STAC9228, so probably a significantly
different section of the code.  But I thought this might narrow down the
issue.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: framework java jmf media snd-hda-intel

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/759338

Title:
  snd-hda-intel locks sound resource on ALC269

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 104511] Re: [needs-packaging] jmf - Java Media Framework

[Tudor Holton]

Sorry.  I'm not using JMF as part of OpenOffice.  I'm using it as part
of Bentokit Flywire - a GPL3 radio broadcasting playout system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/104511

Title:
  [needs-packaging] jmf - Java Media Framework

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 104511] Re: [needs-packaging] jmf - Java Media Framework

[Tudor Holton]

I stumbled across this bug report while I was building a JMF Installer
for Debian and Ubuntu GNU/Linux.   Thought you might like to know about
it.   It's at https://launchpad.net/jmf-installer or
http://www.bentokit.org/project/jmf-installer.  It's in our own nightly-
build debian repository for testing.  Please report bugs/suggestions to
https://bugs.launchpad.net/jmf-installer.

** Changed in: ubuntu
 Assignee: (unassigned) = Bentokit Developers (bentokitdevs)

** Changed in: ubuntu
   Status: Confirmed = Fix Committed

** Changed in: ubuntu
   Status: Fix Committed = In Progress

** Also affects: flywire
   Importance: Undecided
   Status: New

** Changed in: flywire
 Assignee: (unassigned) = Bentokit Developers (bentokitdevs)

** Changed in: flywire
   Importance: Undecided = Wishlist

** Changed in: flywire
   Status: New = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/104511

Title:
  [needs-packaging] jmf - Java Media Framework

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 548814] Re: Indicator applet shows 'setup broadcast accounts', even when accounts are setup and running

[Tudor Holton]

This bug appears to have resurfaced.  Although I've manually installed
python-indicate but I'm still getting the Gwibber Broadcast Accounts
dialog pop up every 10-15 mins.   It's getting pretty annoying.   Since
python-indicate is installed, does that make it a separate bug?

-- 
Indicator applet shows 'setup broadcast accounts', even when accounts are setup 
and running
https://bugs.launchpad.net/bugs/548814
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.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 586660] Re: Increase volume after mute defaults to previous volume

[Tudor Holton]

I am *not* arguing that zero volume and mute should be the same.

I am arguing that, when the speaker is mute, and the user requests to 
*increase* the volume, that that increase should be assumed to mean from 
zero volume, because, at that point, there is no sound, and the term 
increase is relative.

If, instead, the user *unmuted*, then the volume should be the previous 
volume before it was muted.

The question here is: The user wants an increase relative to what?  To 
which we have three possible answers:
1) Relative to the previous sound before unmuting - PA's current approach
2) Relative to the current sound (i.e. zero volume) - My proposal
3) Unrelated because mute is the restrictive binary for the prescriptive 
vector volume. - Alsamixer's approach

As a counterargument, if both volume and mute worked independently as 
Dana is describing, then I should be able to increase and decrease the 
volume without unmuting.  That is not currently the case.  If I mute 
either through keys or by clicking mute then the volume control 
becomes disabled.

As another example of consistency, alsamixer does allow you to modify 
the volume when muted.  Mute and volume are therefore independent.

In my humble opinion, both zero volume and alsamixer's approach are 
consistent when talking about increasing.   In the case of alsamixer, 
the user is able to decrease the volume prior to unmuting because mute 
and volume work independently, thereby avoiding the situation where the 
user is incapable of reducing the sound *before* unmuting.

Perhaps another way to argue this would be to say that disabling the 
volume control when muted is a bad idea because this creates a situation 
where the user is unable to avoid creating a loud noise (other than 
shutting down or pausing all applications that emit audio, which can be 
very difficult).  Unnecessary noise, particularly loud noise, can be 
extremely inappropriate in some situations.

This is what caused me to raise this bug, and why I am exceptionally 
passionate about it.  I was placed in an embarrassing enough situation 
to avoid using PA altogether and instead use alsamixer...but that's 
because I knew it was there and how to use it.   I'm more concerned that 
small things like this affect new users perspective of the whole 
graphical operating environment.

-- 
Increase volume after mute defaults to previous volume
https://bugs.launchpad.net/bugs/586660
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.com/mailman/listinfo/ubuntu-bugs

[Bug 586660] [NEW] Increase volume after mute defaults to previous volume

[Tudor Holton]

Public bug reported:

Binary package hint: pulseaudio

Steps to reproduce:
1) Unmute audio and set volume to something loud. (e.g. Maximum volume)
2) Mute audio
3) Increase volume (by using a key combination)

Symptom:
Audio unmuted and volume reverts to previous volume before mute.

Expected outcome:
Audio unmuted and volume should be set to lowest value possible + 1 step for 
the requested increase.

If I simply wanted to unmute the audio (thereby returning the velume to
its previous setting) then I would have pressed the unmute key
combination and not volume increase.  To me (and I'm guessing a few
others), pressing volume increase suggests that one wants to increase
from its current position (0 when muted).

I understand that there may be an underlying technical difference
between 0 volume and mute.  For example, if you set volume to zero and
mute or unmute, the volume doesn't change.  However, as a user I feel
that mute and zero volume are the same thing in this context.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Increase volume after mute defaults to previous volume
https://bugs.launchpad.net/bugs/586660
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.com/mailman/listinfo/ubuntu-bugs

[Bug 586660] Re: Increase volume after mute defaults to previous volume

[Tudor Holton]

Sorry,  this is current Lucid 10.04 as up-to-date as at today's date
(2010-05-28).

-- 
Increase volume after mute defaults to previous volume
https://bugs.launchpad.net/bugs/586660
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.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 586660] Re: Increase volume after mute defaults to previous volume

[Tudor Holton]

I disagree.  Just because something is consistent, that doesn't mean it 
is sensible or intuitive.

On 28/05/10 14:54, David Henningsson wrote:
 Even if the argument might make sense, the current behavior is
 consistent with every volume controller I know, e g the one on my TV, so
 I guess this is a won't fix.



-- 
Increase volume after mute defaults to previous volume
https://bugs.launchpad.net/bugs/586660
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.com/mailman/listinfo/ubuntu-bugs

[Bug 551507] Re: Gedit indent (CTRL+T) plugin missing

[Tudor Holton]

@Jake Guthmiller : Eh?   Chris Coulson very clearly pointed out that the
functionality is still there.   In order to indent, you highlight a
block of text and press TAB  (instead of CTRL-T).

-- 
Gedit indent (CTRL+T) plugin missing
https://bugs.launchpad.net/bugs/551507
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.com/mailman/listinfo/ubuntu-bugs

[Bug 297183] Re: gtkrsync shows no progress bars

[Tudor Holton]

What if I don't want to delete after?

-- 
gtkrsync shows no progress bars
https://bugs.launchpad.net/bugs/297183
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.com/mailman/listinfo/ubuntu-bugs

[Bug 502071] Re: FH_DATE_PAST_20XX scores on all mails dated 2010 or later

[Tudor Holton]

@Peter   Thanks for mentioning that you had a linode.  I'd been
scratching my head for weeks as to why I supposedly had everything
updated but still this problem.  I added in the extra karmic-updates
lines and that fixed it for me, too.

-- 
FH_DATE_PAST_20XX scores on all mails dated 2010 or later
https://bugs.launchpad.net/bugs/502071
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 502071] Re: FH_DATE_PAST_20XX scores on all mails dated 2010 or later

[Tudor Holton]

@Peter   Thanks for mentioning that you had a linode.  I'd been
scratching my head for weeks as to why I supposedly had everything
updated but still this problem.  I added in the extra karmic-updates
lines and that fixed it for me, too.

-- 
FH_DATE_PAST_20XX scores on all mails dated 2010 or later
https://bugs.launchpad.net/bugs/502071
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.com/mailman/listinfo/ubuntu-bugs

[Bug 295525] Re: cueconvert can't convert toc file(generated by cdrdao) to cue file

[Tudor Holton]

I notice that this bug is now 16 months old.  I have just hit the same
problem.  Did you manage to find a solution?

I looked at the debian bug tracking system, but noone appears to have
reported it there either.  Some of the bug reports are as old as 2006.

So, either the solution is obvious (perhaps I'm using the wrong switch
from cdrdao?) or this package has been abandoned.

Anyone know anything more?

-- 
cueconvert can't convert toc file(generated by cdrdao) to cue file
https://bugs.launchpad.net/bugs/295525
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.com/mailman/listinfo/ubuntu-bugs

[Bug 179383] Re: cueconvert creates invalid cue from toc

[Tudor Holton]

Could this be related to Debian bug http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=399517 ?

** Bug watch added: Debian Bug tracker #399517
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399517

-- 
cueconvert creates invalid cue from toc
https://bugs.launchpad.net/bugs/179383
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.com/mailman/listinfo/ubuntu-bugs

[Bug 121967] Re: Fingerprint reader as scroll wheel

[Tudor Holton]

Needs migrating forward to current kernel development.

** Changed in: linux (Ubuntu)
   Status: Incomplete = New

-- 
Fingerprint reader as scroll wheel
https://bugs.launchpad.net/bugs/121967
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.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 503186] Re: Cannot open SCSI driver!

[Tudor Holton]

@Schily:

That wouldn't be an upgrade since it's not in the Ubuntu repository.

If I want to complain about *your* version, then I'll do so on *your*
package, thank you very much.  It was *you* that changed your license to 
CDDL, and that's what I consider a fork just as much as cdrkit.

Until you want contribute your fixes as GPL (the basis for Debian),
please quit trolling on other packages bug reports.

Schily wrote:
 And this is again a problem that disappears if you
 upgrade to recent original software from:

 ftp://ftp.berlios.de/pub/cdrecord/alpha/ 
  
 http://cdrecord.berlios.de/ 

 instead of using an unmaintaned fork.



-- 
Cannot open SCSI driver!
https://bugs.launchpad.net/bugs/503186
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.com/mailman/listinfo/ubuntu-bugs

[Bug 503186] [NEW] Cannot open SCSI driver!

[Tudor Holton]

Public bug reported:

wodim and icedax complain Cannot open SCSI driver! when scanning for
devices even though nautilus detects and reads the CDs perfectly.

Below is a transcript of what I tried:

tu...@kneet:~$ wodim -scanbus
wodim: No such file or directory. 
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.

tu...@kneet:~$ sudo wodim --devices
wodim: No such file or directory. 
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.

tu...@kneet:~$ sudo adduser tudor cdrom
The user `tudor' is already a member of `cdrom'.
tu...@kneet:~$ sudo wodim --devices
wodim: No such file or directory. 
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.

tu...@kneet:~$ sudo wodim -scanbus
wodim: No such file or directory. 
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.

tu...@kneet:~$ sudo wodim -scanbus --verbose
TOC Type: 1 = CD-ROM
wodim: No such file or directory. 
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.

tu...@kneet:~$ sudo wodim --devices --verbose
TOC Type: 1 = CD-ROM
wodim: No such file or directory. 
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.

tu...@kneet:~$ sudo icedax --devices
icedax: No such file or directory. Cannot open '-1'. Cannot open SCSI driver.
icedax: For possible targets try 'wodim -scanbus'.
Use the script scan_scsi.linux to find out more.
Probably you did not define your SCSI device.
Set the CDDA_DEVICE environment variable or use the -D option.
You can also define the default device in the Makefile.
For possible transport specifiers try 'wodim dev=help'.

** Affects: cdrkit (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Cannot open SCSI driver!
https://bugs.launchpad.net/bugs/503186
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.com/mailman/listinfo/ubuntu-bugs

[Bug 503186] Re: Cannot open SCSI driver!

[Tudor Holton]

Description:Ubuntu 9.10
Release:9.10

-- 
Cannot open SCSI driver!
https://bugs.launchpad.net/bugs/503186
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.com/mailman/listinfo/ubuntu-bugs

[Bug 474929] [NEW] Empathy does not import any Pidgin accounts

[Tudor Holton]

Public bug reported:

Binary package hint: empathy

Empathy does not import any Pidgin accounts on my machine.  Every time
Empathy starts, it offers to import from Pidgin, it lists my accounts,
and I select to import all.  However, none are imported.  I end up with
a blank Empathy window.

This could be related to bug #388906 since I have IRC accounts in my
Pidgin config.

** Affects: empathy (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Empathy does not import any Pidgin accounts
https://bugs.launchpad.net/bugs/474929
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.com/mailman/listinfo/ubuntu-bugs

[Bug 474929] Re: Empathy does not import any Pidgin accounts

[Tudor Holton]

If I deselect my IRC accounts from the import window, it imports all the
others.  This must mean that bug #388906 is stopping the import of other
protocols.

-- 
Empathy does not import any Pidgin accounts
https://bugs.launchpad.net/bugs/474929
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.com/mailman/listinfo/ubuntu-bugs

[Bug 388906] Re: empathy does not import irc from pidgin

[Tudor Holton]

If I deselect my IRC accounts from the import window, it imports all the
others. This must mean that importing IRC accounts is stopping the
import of other protocols.

This means that this bug is having a direct effect on bug #474929.

-- 
empathy does not import irc from pidgin
https://bugs.launchpad.net/bugs/388906
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.com/mailman/listinfo/ubuntu-bugs

[Bug 346700] Re: [jaunty] Usb-creator creates incorrect free, persistent space; to /cdrom not /

[Tudor Holton]

Both D Gilder and jruss are correct.  Correcting line 134 of install.py
results in a 4GB casper-rw file on my 16GB USB key when I requested an
8GB casper-rw file.  Previously, no casper-rw file was created at all,
so 4GB is better than nothing for now.  Obviously, we would prefer to be
able to provide a file for then entire size of the user's USB key, or at
least that the installer should warn or not allow this situation to
occur.  Many users now have usb keys greater than 4GB.

-- 
[jaunty] Usb-creator creates incorrect free, persistent space; to /cdrom not /
https://bugs.launchpad.net/bugs/346700
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.com/mailman/listinfo/ubuntu-bugs

[Bug 369031] [NEW] Update Manager won't tick Distribution Upgrades Checkbox, particularly brasero.

[Tudor Holton]

Public bug reported:

Binary package hint: update-manager

Update Manager shows updates that can't be selected.  They have a
checkbox displayed, but the checkbox can't be ticked.

The untickable items are displayed in the Distribution Updates
section, and in my case I have brasero as untickable.

If I select the item, the upgrade information is displayed as normal.

If I right-click the package, Check all is available, but selecting it
won't tick the untickable item.

If the package is the only one available, Install updates is greyed
out.

What does this mean?

Screenshot attached.

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Update Manager won't tick Distribution Upgrades Checkbox, particularly brasero.
https://bugs.launchpad.net/bugs/369031
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.com/mailman/listinfo/ubuntu-bugs

[Bug 369031] Re: Update Manager won't tick Distribution Upgrades Checkbox, particularly brasero.

[Tudor Holton]

** Attachment added: Screenshot.png
   http://launchpadlibrarian.net/26112711/Screenshot.png

-- 
Update Manager won't tick Distribution Upgrades Checkbox, particularly brasero.
https://bugs.launchpad.net/bugs/369031
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.com/mailman/listinfo/ubuntu-bugs

[Bug 369031] Re: Update Manager won't tick Distribution Upgrades Checkbox, particularly brasero.

[Tudor Holton]

After all other upgrades complete.

** Attachment added: Screenshot-Update Manager.png
   http://launchpadlibrarian.net/26112853/Screenshot-Update%20Manager.png

-- 
Update Manager won't tick Distribution Upgrades Checkbox, particularly brasero.
https://bugs.launchpad.net/bugs/369031
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.com/mailman/listinfo/ubuntu-bugs

[Bug 174032] Re: lvresize fails attempting to call fsadm with --resizefs parameter

[Tudor Holton]

Any news on this bug?  I notice that I'm still getting the error massage
listed here, and this is the first bug to turn up in google for ubuntu
lvm lvresize 'execlp failed'.

-- 
lvresize fails attempting to call fsadm with --resizefs parameter
https://bugs.launchpad.net/bugs/174032
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.com/mailman/listinfo/ubuntu-bugs

[Bug 326339] [NEW] gnome-cups-manager doesn't notify user of cups-pdf failure

[Tudor Holton]

Public bug reported:

Binary package hint: gnome-cups-manager

If cups-pdf fails to print, the user isn't notified.

Steps to reproduce:
1) With cups-pdf installed, cause cups-pdf to fail
2) Try to print using the PDf printer
3) Notice that the printer applet pops up and then goes away quickly.
3b) Also notice that there's no print job remaining in the queue.

What should happen:
3) Printer applet should stay up.  Popup notification should appear and say 
'PDF printer failed to print'. Print job should remain in queue.

My first assumption was that the print job had completed, so I went
looking for the file.  It was only after not finding the file and then
going into System-Administration-Printing, that I noticed that the
state for the printer was 'Idle - /usr/lib/cups/backend/cups-pdf
failed'.

** Affects: gnome-cups-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cups-pdf

** Summary changed:

- cups-pdf doesn't notify user of failure
+ gnome-cups-manager doesn't notify user of cups-pdf failure

** Tags added: cups-pdf

-- 
gnome-cups-manager doesn't notify user of cups-pdf failure
https://bugs.launchpad.net/bugs/326339
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.com/mailman/listinfo/ubuntu-bugs