[Bug 1249097] Re: gearadmin crashes on launch
This can't be reproduced on any supported version of Ubuntu. ** Changed in: gearmand (Ubuntu) Status: Confirmed => 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/1249097 Title: gearadmin crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gearmand/+bug/1249097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357523] Re: Verbose option not recognized
Confirmed, this is a documentation bug. Fixing upstream. ** Changed in: gearmand (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357523 Title: Verbose option not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gearmand/+bug/1357523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1260830] Re: gearman upstart job does not use /etc/default/gearman-job-server
upstart job is long gone I'm afraid. systemd unit from Debian seems to work fine. ** Changed in: gearmand (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1260830 Title: gearman upstart job does not use /etc/default/gearman-job-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gearmand/+bug/1260830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357523] Re: Verbose option not recognized
https://github.com/gearman/gearmand/pull/234 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357523 Title: Verbose option not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gearmand/+bug/1357523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070900] Re: gearmand infinite loop invokes oom-killer
Neither of these work on 1.1.18 in Ubuntu 18.04. This was likely fixed upstream and released long ago. ** Changed in: gearmand (Ubuntu) Status: New => 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/1070900 Title: gearmand infinite loop invokes oom-killer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gearmand/+bug/1070900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 815796] Re: 0.24 make fails on 32-bit installs
This does not affect current Ubuntu versions, which do have 32-bit binaries. ** Changed in: gearmand (Ubuntu) Status: Confirmed => 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/815796 Title: 0.24 make fails on 32-bit installs To manage notifications about this bug go to: https://bugs.launchpad.net/gearmand/+bug/815796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015081] Re: memcached backend no longer supported
This was fixed some time since 11.10, and memcached support works fine as of 18.04. ** Changed in: gearmand (Ubuntu) Status: New => 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/1015081 Title: memcached backend no longer supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gearmand/+bug/1015081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901370] Re: 0.26 build error: 'drizzle_column_skip_all' was not declared in this scope
gearmand in recent versions of Ubuntu does not support libdrizzle. ** Changed in: gearmand (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901370 Title: 0.26 build error: 'drizzle_column_skip_all' was not declared in this scope To manage notifications about this bug go to: https://bugs.launchpad.net/gearmand/+bug/901370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 805329] Re: /usr/lib/libdrizzle.so.0: no version information available
gearmand doesn't support libdrizzle in recent package versions. ** Changed in: gearmand (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/805329 Title: /usr/lib/libdrizzle.so.0: no version information available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gearmand/+bug/805329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 800734] Re: gearmand 0.22 no longer recognises --libdrizzle-mysql or --libdrizzle_user arguments
In current versions, libdrizzle is not included, but libmysqlclient functionality is. As such, I think this might be irrelevant. ** Changed in: gearmand (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/800734 Title: gearmand 0.22 no longer recognises --libdrizzle-mysql or --libdrizzle_user arguments To manage notifications about this bug go to: https://bugs.launchpad.net/gearmand/+bug/800734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711724] Re: Segfaults with dict
Uploaded to python3.6 for zesty too. ** Changed in: python3.6 (Ubuntu Zesty) Status: New => In Progress ** Changed in: python3.6 (Ubuntu Zesty) Importance: Undecided => High ** Changed in: python3.6 (Ubuntu Zesty) Assignee: (unassigned) => Clint Byrum (clint-fewbar) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711724 Title: Segfaults with dict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711724] Re: Segfaults with dict
Uploaded for zesty as well. ** Changed in: python3.5 (Ubuntu Zesty) Importance: Undecided => High ** Changed in: python3.5 (Ubuntu Zesty) Status: New => In Progress ** Changed in: python3.5 (Ubuntu Zesty) Assignee: (unassigned) => Clint Byrum (clint-fewbar) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711724 Title: Segfaults with dict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711724] Re: Segfaults with dict
I've uploaded just this fix to xenial and zesty, without the other bug which isn't SRU-ready yet. Thanks for your review raof! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711724 Title: Segfaults with dict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711724] Re: Segfaults with dict
** Changed in: python3.5 (Ubuntu Xenial) Status: New => In Progress ** Changed in: python3.5 (Ubuntu Xenial) Assignee: (unassigned) => Clint Byrum (clint-fewbar) ** Changed in: python3.5 (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711724 Title: Segfaults with dict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711724] Re: Segfaults with dict
The attached patch is also included in Python 3.6.2 upstream, which is released in artful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711724 Title: Segfaults with dict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711724] Re: Segfaults with dict
This python script reproduces the segfault when run via python3.5 ** Attachment added: "bpo-27945.py" https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+attachment/4934875/+files/bpo-27945.py ** Description changed: In certain situations python3.5 will segfault. This bug is confirmed and fixed upstream in Python 3.5.4 http://bugs.python.org/issue27945 + + [Test Case] + 1. download attached bpo-27945.py + 2. run: python3.5 bpo-27945.py + + If it does not segfault, the bug is fixed. + + [Regression Potential] + The fix has been shown to introduce a minor performance hit for dictionaries in general. ** Also affects: python3.5 (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: python3.5 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711724 Title: Segfaults with dict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711724] Re: Segfaults with dict
Python3.5 has been removed from artful, and thus does not need to be fixed. ** Also affects: python3.6 (Ubuntu) Importance: Undecided Status: New ** Changed in: python3.6 (Ubuntu) Status: New => Fix Released ** Changed in: python3.6 (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711724 Title: Segfaults with dict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711724] [NEW] Segfaults with dict
Public bug reported: In certain situations python3.5 will segfault. This bug is confirmed and fixed upstream in Python 3.5.4 http://bugs.python.org/issue27945 [Test Case] 1. download attached bpo-27945.py 2. run: python3.5 bpo-27945.py If it does not segfault, the bug is fixed. [Regression Potential] The fix has been shown to introduce a minor performance hit for dictionaries in general. ** Affects: python3.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: python3.5 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: python3.5 (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: python3.5 (Ubuntu Xenial) 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/1711724 Title: Segfaults with dict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1711724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 820679] Re: nmbd and smbd will not be started again on transition from runlevel 1 to 2
Always nice to see a 6 year old bug fixed! Excerpts from Andreas Hasenack's message of 2017-06-08 23:19:08 UTC: > ** Changed in: samba (Ubuntu) >Status: Triaged => Invalid > > ** Changed in: samba (Ubuntu Trusty) >Status: New => Won't Fix > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/820679 > > Title: > nmbd and smbd will not be started again on transition from runlevel 1 > to 2 > > Status in samba package in Ubuntu: > Invalid > Status in samba source package in Trusty: > Won't Fix > > Bug description: > The stop on conditions for these jobs is > > stop on runlevel [!2345] > > which will cause them to stop when the administrator switches runlevel > to 1. But the on switch to 2, there is no corresponding start on > condition to cause them to start again. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/samba/+bug/820679/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820679 Title: nmbd and smbd will not be started again on transition from runlevel 1 to 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/820679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1646253] Re: I am getting frequent DRM hangs while playing Cities: Skylines from Steam
I'll try and do that some time this week. Thanks Joseph. Excerpts from Joseph Salisbury's message of 2016-12-13 20:01:45 UTC: > This issue appears to be an upstream bug, since you tested the latest > upstream kernel. Would it be possible for you to open an upstream bug > report[0]? That will allow the upstream Developers to examine the issue, > and may provide a quicker resolution to the bug. > > Please follow the instructions on the wiki page[0]. The first step is to > email the appropriate mailing list. If no response is received, then a > bug may be opened on bugzilla.kernel.org. > > Once this bug is reported upstream, please add the tag: 'kernel-bug- > reported-upstream'. > > [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel > > ** Changed in: linux (Ubuntu Xenial) >Status: Confirmed => Triaged > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Triaged > > ** Also affects: linux (Ubuntu Zesty) >Importance: Medium >Status: Triaged > > ** Also affects: linux (Ubuntu Yakkety) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu Yakkety) >Status: New => Triaged > > ** Changed in: linux (Ubuntu Yakkety) >Importance: Undecided => Medium > > ** Tags added: yakkety zesty > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1646253 > > Title: > I am getting frequent DRM hangs while playing Cities: Skylines from > Steam > > Status in linux package in Ubuntu: > Triaged > Status in linux source package in Xenial: > Triaged > Status in linux source package in Yakkety: > Triaged > Status in linux source package in Zesty: > Triaged > > Bug description: > It happens during normal gameplay. Have tried reducing settings. Seems > like a legitimate driver bug. The program crashes, but X does not. > > [16868.151225] [drm] stuck on render ring > [16868.155458] [drm] GPU HANG: ecode 8:0:0x84dffefc, in Cities.x64 [21076], > reason: Ring hung, action: reset > [16868.155472] [ cut here ] > [16868.155503] WARNING: CPU: 1 PID: 13959 at > /build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 > intel_mmio_flip_work_func+0x38e/0x3d0 [i915]() > [16868.155505] WARN_ON(__i915_wait_request(mmio_flip->req, > mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips)) > [16868.155506] Modules linked in: > [16868.155508] tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio > usbhid hid snd_usbmidi_lib usb_serial_simple usbserial ctr ccm pci_stub > vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM > iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ipt_REJECT > nf_reject_ipv4 xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 > nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter bridge > stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter > ip_tables x_tables rfcomm aufs bnep arc4 iwlmvm uvcvideo mac80211 > videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 intel_rapl videobuf2_core > x86_pkg_temp_thermal v4l2_common intel_powerclamp cdc_mbim snd_hda_codec_hdmi > coretemp cdc_wdm snd_hda_codec_realtek snd_hda_codec_generic cdc_ncm videodev > joydev iwlwifi > [16868.155545] input_leds cdc_acm btusb usbnet serio_raw media btrtl > snd_hda_intel mii btbcm rtsx_pci_ms thinkpad_acpi snd_hda_codec btintel > memstick snd_hda_core cfg80211 bluetooth snd_hwdep snd_seq_midi > snd_seq_midi_event intel_pch_thermal nvram snd_rawmidi lpc_ich snd_pcm mei_me > mei shpchp snd_seq snd_seq_device snd_timer snd soundcore kvm_intel mac_hid > kvm irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng > algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul > ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper > ablk_helper cryptd i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect > sysimgblt rtsx_pci fb_sys_fops ahci psmouse ptp drm libahci pps_core wmi fjes > video > [16868.155589] CPU: 1 PID: 13959 Comm: kworker/1:0 Tainted: GW OE > 4.4.0-51-generic #72-Ubuntu > [16868.155591] Hardware name: LENOVO 20CLS5N900/20CLS5N900, BIOS N10ET36W > (1.15 ) 06/19/2015 > [16868.155617] Workqueue: events intel_mmio_flip_work_func [i915] > [16868.155619] 0286 dd043c13 880382bbbd20 > 813f5fc3 > [16868.155622] 880382bbbd68 c03a7ab8 880382bbbd58 > 810812b2 > [16868.155624] 8802970af040 88042dc56500 88042dc5ae00 > 0040 > [16868.155626] Call Trace: > [16868.155632] [] dump_stack+0x63/0x90 > [16868.155637] [] warn_slowpath_common+0x82/0xc0 > [16868.155639] [] warn_slowpath_fmt+0x5c/0x80 > [16868.155643] [] ? __switch_to+0x437/0x5c0 > [16868.155667] [] intel_mmio_flip_work_func+0x38e/0x3d0 > [i915] > [16868.155672] [] process_one_work+0x165/0x480 >
[Bug 1646253] Re: I am getting frequent DRM hangs while playing Cities: Skylines from Steam
I was able to play about 12 hours of the game without a crash. So things definitely improved. But eventually it happened again. [160126.986645] [drm] GPU HANG: ecode 8:0:0x85db, in Cities.x64 [23989], reason: Hang on render ring, action: reset [160126.986646] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [160126.986647] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [160126.986647] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [160126.986648] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [160126.986648] [drm] GPU crash dump saved to /sys/class/drm/card0/error [160126.986686] drm/i915: Resetting chip after gpu hang [160137.977308] drm/i915: Resetting chip after gpu hang Linux clint-ThinkPad-X250 4.9.0-040900rc8-generic #201612051443 SMP Mon Dec 5 19:45:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646253 Title: I am getting frequent DRM hangs while playing Cities: Skylines from Steam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1646253] Re: I am getting frequent DRM hangs while playing Cities: Skylines from Steam
Excerpts from Joseph Salisbury's message of 2016-12-06 16:36:24 UTC: > Can you also give the latest DRM nightly kernel a test? It is available from: > http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2016-12-06/ > I'm installing it now. The crash is less frequent with 4.9 (have gone 2 hours now without it), so it may take me a few days to confirm it doesn't happen anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646253 Title: I am getting frequent DRM hangs while playing Cities: Skylines from Steam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646253] Re: I am getting frequent DRM hangs while playing Cities: Skylines from Steam
Launchpad must have changed since I last did this. It says the bug won't be visible by you even though I subscribed you. Let me know if that error file will help and I'll send it somewhere, but I'm concerned it may have sensitive information from system RAM in it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646253 Title: I am getting frequent DRM hangs while playing Cities: Skylines from Steam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646253] Re: I am getting frequent DRM hangs while playing Cities: Skylines from Steam
Hello! This game never worked properly. I installed it and it had these hangs starting immediately. It got better after I turned graphics detail _way_ down, but it still happens every 20 - 45 minutes of game play. I installed the mainline build from today, and it did not help: [ 103.860280] perf: interrupt took too long (2603 > 2500), lowering kernel.perf_event_max_sample_rate to 76750 [ 133.523728] perf: interrupt took too long (3432 > 3253), lowering kernel.perf_event_max_sample_rate to 58250 [ 198.406328] perf: interrupt took too long (4312 > 4290), lowering kernel.perf_event_max_sample_rate to 46250 [ 260.543970] perf: interrupt took too long (5546 > 5390), lowering kernel.perf_event_max_sample_rate to 36000 [ 346.007069] perf: interrupt took too long (6985 > 6932), lowering kernel.perf_event_max_sample_rate to 28500 [ 538.451884] perf: interrupt took too long (8771 > 8731), lowering kernel.perf_event_max_sample_rate to 22750 [ 824.436053] perf: interrupt took too long (11067 > 10963), lowering kernel.perf_event_max_sample_rate to 18000 [ 1355.146416] perf: interrupt took too long (13847 > 13833), lowering kernel.perf_event_max_sample_rate to 14250 [ 1802.222924] iwlwifi :03:00.0: Too many chunks: 20 [ 2727.702727] [drm] GPU HANG: ecode 8:0:0x85db, in Cities.x64 [5594], reason: Hang on render ring, action: reset [ 2727.702728] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 2727.702729] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 2727.702729] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 2727.702729] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 2727.702730] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 2727.718889] drm/i915: Resetting chip after gpu hang [ 2738.742501] drm/i915: Resetting chip after gpu hang I will attach the error file mentioned and mark the bug private (in case the memory references has sensitive information). ** 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/1646253 Title: I am getting frequent DRM hangs while playing Cities: Skylines from Steam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646253] [NEW] I am getting frequent DRM hangs while playing Cities: Skylines from Steam
Public bug reported: It happens during normal gameplay. Have tried reducing settings. Seems like a legitimate driver bug. The program crashes, but X does not. [16868.151225] [drm] stuck on render ring [16868.155458] [drm] GPU HANG: ecode 8:0:0x84dffefc, in Cities.x64 [21076], reason: Ring hung, action: reset [16868.155472] [ cut here ] [16868.155503] WARNING: CPU: 1 PID: 13959 at /build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]() [16868.155505] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips)) [16868.155506] Modules linked in: [16868.155508] tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio usbhid hid snd_usbmidi_lib usb_serial_simple usbserial ctr ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm aufs bnep arc4 iwlmvm uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 intel_rapl videobuf2_core x86_pkg_temp_thermal v4l2_common intel_powerclamp cdc_mbim snd_hda_codec_hdmi coretemp cdc_wdm snd_hda_codec_realtek snd_hda_codec_generic cdc_ncm videodev joydev iwlwifi [16868.155545] input_leds cdc_acm btusb usbnet serio_raw media btrtl snd_hda_intel mii btbcm rtsx_pci_ms thinkpad_acpi snd_hda_codec btintel memstick snd_hda_core cfg80211 bluetooth snd_hwdep snd_seq_midi snd_seq_midi_event intel_pch_thermal nvram snd_rawmidi lpc_ich snd_pcm mei_me mei shpchp snd_seq snd_seq_device snd_timer snd soundcore kvm_intel mac_hid kvm irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt rtsx_pci fb_sys_fops ahci psmouse ptp drm libahci pps_core wmi fjes video [16868.155589] CPU: 1 PID: 13959 Comm: kworker/1:0 Tainted: GW OE 4.4.0-51-generic #72-Ubuntu [16868.155591] Hardware name: LENOVO 20CLS5N900/20CLS5N900, BIOS N10ET36W (1.15 ) 06/19/2015 [16868.155617] Workqueue: events intel_mmio_flip_work_func [i915] [16868.155619] 0286 dd043c13 880382bbbd20 813f5fc3 [16868.155622] 880382bbbd68 c03a7ab8 880382bbbd58 810812b2 [16868.155624] 8802970af040 88042dc56500 88042dc5ae00 0040 [16868.155626] Call Trace: [16868.155632] [] dump_stack+0x63/0x90 [16868.155637] [] warn_slowpath_common+0x82/0xc0 [16868.155639] [] warn_slowpath_fmt+0x5c/0x80 [16868.155643] [] ? __switch_to+0x437/0x5c0 [16868.155667] [] intel_mmio_flip_work_func+0x38e/0x3d0 [i915] [16868.155672] [] process_one_work+0x165/0x480 [16868.155674] [] worker_thread+0x4b/0x4c0 [16868.155677] [] ? process_one_work+0x480/0x480 [16868.155679] [] kthread+0xd8/0xf0 [16868.155681] [] ? kthread_create_on_node+0x1e0/0x1e0 [16868.155685] [] ret_from_fork+0x3f/0x70 [16868.155687] [] ? kthread_create_on_node+0x1e0/0x1e0 [16868.155689] ---[ end trace 1339c06922e659f4 ]--- [16868.157772] drm/i915: Resetting chip after gpu hang [16874.163802] [drm] stuck on render ring [16874.168161] [drm] GPU HANG: ecode 8:0:0x86dd, in Cities.x64 [21076], reason: Ring hung, action: reset [16874.168182] [ cut here ] [16874.168215] WARNING: CPU: 1 PID: 13959 at /build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]() [16874.168216] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips)) [16874.168217] Modules linked in: [16874.168221] tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio usbhid hid snd_usbmidi_lib usb_serial_simple usbserial ctr ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm aufs bnep arc4 iwlmvm uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 intel_rapl videobuf2_core x86_pkg_temp_thermal v4l2_common intel_powerclamp cdc_mbim snd_hda_codec_hdmi coretemp cdc_wdm snd_hda_codec_realtek snd_hda_codec_generic cdc_ncm videodev joydev iwlwifi [16874.168250] input_leds cdc_acm btusb usbnet serio_raw media btrtl snd_hda_intel mii btbcm rtsx_pci_ms thinkpad_acpi
[Bug 1632482] Re: OpenStack os_image is_public flag does not make image public in Glance V1 API
Thanks Frank. I'm a shade developer. I'll get this fixed upstream and a new release should be out within a few weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632482 Title: OpenStack os_image is_public flag does not make image public in Glance V1 API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-shade/+bug/1632482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632482] Re: OpenStack os_image is_public flag does not make image public in Glance V1 API
** Changed in: python-shade (Ubuntu) Status: New => Triaged ** Changed in: python-shade (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632482 Title: OpenStack os_image is_public flag does not make image public in Glance V1 API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-shade/+bug/1632482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341046] Re: OpenAFS needs patches for kernel 3.16 [openafs-modules-dkms 1.6.9-1: openafs kernel module failed to build]
AFS users cannot use the backported kernel on trusty. ** Also affects: openafs (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: openafs (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341046 Title: OpenAFS needs patches for kernel 3.16 [openafs-modules-dkms 1.6.9-1: openafs kernel module failed to build] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1341046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576930] Re: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04
Ubuntu 16.04 does not have MySQL 5.5, it has 5.7. The most likely explanation for the memory usage going up is that default buffer sizes have been increased significantly for mysqld over the last few releases. You may need to edit config files to reduce the buffers. ** Package changed: mysql-5.5 (Ubuntu) => mysql-5.7 (Ubuntu) ** Changed in: mysql-5.7 (Ubuntu) Importance: Undecided => High ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.7 in Ubuntu. Matching subscriptions: main https://bugs.launchpad.net/bugs/1576930 Title: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1576930/+subscriptions -- 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 1576930] Re: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04
Ubuntu 16.04 does not have MySQL 5.5, it has 5.7. The most likely explanation for the memory usage going up is that default buffer sizes have been increased significantly for mysqld over the last few releases. You may need to edit config files to reduce the buffers. ** Package changed: mysql-5.5 (Ubuntu) => mysql-5.7 (Ubuntu) ** Changed in: mysql-5.7 (Ubuntu) Importance: Undecided => High ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576930 Title: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1576930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544216] [NEW] libiscsi support is disabled
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/libiscsi/+bug/1271653 has been filed and is under review by the security team. Hopefully libiscsi will be promoted to main before feature freeze of 16.04. Meanwhile, we should be optimistic and prepare a build of qemu with libiscsi support turned on and test it, potentially morphing this into a feature freeze exception request if the MIR makes it a bit tight to get the upload in. Having libiscsi support in 16.04 will allow users to run OpenStack Nova with stock qemu 16.04 in containers on _any_ host OS in an unprivileged container. ** Affects: qemu (Ubuntu) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544216 Title: libiscsi support is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1544216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544216] [NEW] libiscsi support is disabled
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/libiscsi/+bug/1271653 has been filed and is under review by the security team. Hopefully libiscsi will be promoted to main before feature freeze of 16.04. Meanwhile, we should be optimistic and prepare a build of qemu with libiscsi support turned on and test it, potentially morphing this into a feature freeze exception request if the MIR makes it a bit tight to get the upload in. Having libiscsi support in 16.04 will allow users to run OpenStack Nova with stock qemu 16.04 in containers on _any_ host OS in an unprivileged container. ** Affects: qemu (Ubuntu) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1544216 Title: libiscsi support is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1544216/+subscriptions -- 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 1533738] Re: Remove juju-jitsu package from Xenial
http://gifsec.com/wp-content/uploads/GIF/2015/01/Dr.-Evil-For-My-Homies- Homies-One-For-Me-Pour-GIF.gif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533738 Title: Remove juju-jitsu package from Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-jitsu/+bug/1533738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530072] Re: update to mysql 5.6
I orphaned handlersocket some time ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731877 I'd suggest just dropping handlersocket from ubuntu. ** Bug watch added: Debian Bug tracker #731877 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731877 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530072 Title: update to mysql 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/handlersocket/+bug/1530072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512200] Re: reportbug: crashes on BTS query returning "HTTPError 500 Internal Server Error"
I've sponsored the upload to trusty-proposed and built test packages with it that resolve the bug for me. Vivid test build is going now and I will upload that as well. Thanks for the patches Shih-Yuan! ** Also affects: python-debianbts (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: python-debianbts (Ubuntu Vivid) Status: New => In Progress ** Changed in: python-debianbts (Ubuntu Vivid) Importance: Undecided => Critical ** Changed in: python-debianbts (Ubuntu Vivid) Assignee: (unassigned) => Clint Byrum (clint-fewbar) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512200 Title: reportbug: crashes on BTS query returning "HTTPError 500 Internal Server Error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debianbts/+bug/1512200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512200] Re: reportbug: crashes on BTS query returning "HTTPError 500 Internal Server Error"
** Changed in: python-debianbts (Ubuntu) Status: New => Fix Released ** Also affects: python-debianbts (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: python-debianbts (Ubuntu Trusty) Status: New => In Progress ** Changed in: python-debianbts (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: python-debianbts (Ubuntu Trusty) Assignee: (unassigned) => Clint Byrum (clint-fewbar) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512200 Title: reportbug: crashes on BTS query returning "HTTPError 500 Internal Server Error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debianbts/+bug/1512200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481158] Re: sfdisk gets cylinder calculation wrong when using sectors
I've hit this as well. 2.26 is available in Wily, so any fixes here would be to trusty. It seems like a major rewrite wouldn't be backported in the SRU process though. So this might have to remain unfixed in the LTS unless somebody wants to ferret out the problem and make a smaller patch just for 2.20. ** Changed in: util-linux (Ubuntu) Status: New = Confirmed ** Changed in: util-linux (Ubuntu) Importance: Undecided = High ** Changed in: util-linux (Ubuntu) Status: Confirmed = Fix Released ** Also affects: util-linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: util-linux (Ubuntu Trusty) Status: New = Triaged ** Changed in: util-linux (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481158 Title: sfdisk gets cylinder calculation wrong when using sectors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1481158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059387] Re: package gearman-job-server 0.14-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Also Ubuntu 11.04 is long EOL, so I'm marking this incomplete. If somebody still sees something like this on a current release of Ubuntu please do feel free to reopen it as New. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059387 Title: package gearman-job-server 0.14-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/gearmand/+bug/1059387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059387] Re: package gearman-job-server 0.14-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This looks like a packaging bug only, so I've removed the upstream link. ** No longer affects: gearmand ** Changed in: gearmand (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059387 Title: package gearman-job-server 0.14-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/gearmand/+bug/1059387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
I tested this on a trusty box with UCA packages (which are the same code as the vivid packages) + the vivid-proposed python-ironicclient, and it passes the test case. I don't have the time to rebuild the whole thing on a vivid host. I think given that this is python and the code is identical in UCA and on vivid, we can consider this verification-done. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ironicclient in Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+subscriptions -- 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 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
I tested this on a trusty box with UCA packages (which are the same code as the vivid packages) + the vivid-proposed python-ironicclient, and it passes the test case. I don't have the time to rebuild the whole thing on a vivid host. I think given that this is python and the code is identical in UCA and on vivid, we can consider this verification-done. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
I will test with the packages from proposed today and report here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
I will test with the packages from proposed today and report here. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ironicclient in Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+subscriptions -- 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 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
Note that I've submitted a fix to kilo/stable requirements: https://review.openstack.org/#/c/198072/ ** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ironicclient in Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+subscriptions -- 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 1470950] Re: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
Note that I've submitted a fix to kilo/stable requirements: https://review.openstack.org/#/c/198072/ ** Also affects: nova 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/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470950] [NEW] Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
Public bug reported: The nova ironic driver in Kilo was updated to use a new parameter in ironicclient, configdrive, which was added in v0.4.0 of python- ironicclient Test case #. Install kilo nova and kilo ironic #. Configure nova to use ironic virt #. nova boot instance #. Observe failure in nova-compute log showing incorrect configdrive parameter being used. #. update ironicclient to =0.4.1 #. restart nova-compute #. nova boot again #. instance should boot ** Affects: nova Importance: Undecided Status: New ** Affects: python-ironicclient (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-ironicclient (Ubuntu Vivid) Importance: High Status: Triaged ** Also affects: python-ironicclient (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: python-ironicclient (Ubuntu) Status: New = Fix Released ** Changed in: python-ironicclient (Ubuntu Vivid) Status: New = Triaged ** Changed in: python-ironicclient (Ubuntu Vivid) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470950] [NEW] Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver
Public bug reported: The nova ironic driver in Kilo was updated to use a new parameter in ironicclient, configdrive, which was added in v0.4.0 of python- ironicclient Test case #. Install kilo nova and kilo ironic #. Configure nova to use ironic virt #. nova boot instance #. Observe failure in nova-compute log showing incorrect configdrive parameter being used. #. update ironicclient to =0.4.1 #. restart nova-compute #. nova boot again #. instance should boot ** Affects: nova Importance: Undecided Status: New ** Affects: python-ironicclient (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-ironicclient (Ubuntu Vivid) Importance: High Status: Triaged ** Also affects: python-ironicclient (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: python-ironicclient (Ubuntu) Status: New = Fix Released ** Changed in: python-ironicclient (Ubuntu Vivid) Status: New = Triaged ** Changed in: python-ironicclient (Ubuntu Vivid) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ironicclient in Ubuntu. https://bugs.launchpad.net/bugs/1470950 Title: Version of ironicclient in vivid/UCA not sufficient to interact properly with Nova ironic virt driver To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470950/+subscriptions -- 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 1450803] Re: mysqlhotcopy: error in SQL syntax
Regardless of its status in 5.6/5.7, we shipped 5.5 to users in Ubuntu 14.04, when it was still undeprecated, so I think it is worth fixing in 14.04. Note that in Ubuntu 15.04 and later, 5.6 is shipped, and mysqlhotcopy is in fact shown as deprecated: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/vivid/mysql-5.6/vivid/view/head:/scripts/mysqlhotcopy.sh#L161 Now, my personal feeling is that users should stop using it _immediately_ because it really is a terrible thing to rely on. But, we take bugs that might affect data integrity, including backups, pretty seriously. ** Also affects: mysql-5.5 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: mysql-5.5 (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: mysql-5.5 (Ubuntu Trusty) Status: New = Triaged ** Changed in: mysql-5.5 (Ubuntu Utopic) Status: New = Triaged ** Changed in: mysql-5.5 (Ubuntu Trusty) Importance: Undecided = High ** Changed in: mysql-5.5 (Ubuntu Utopic) Importance: Undecided = High ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid ** Changed in: mysql-5.5 (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1450803 Title: mysqlhotcopy: error in SQL syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1450803/+subscriptions -- 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 1450803] Re: mysqlhotcopy: error in SQL syntax
Regardless of its status in 5.6/5.7, we shipped 5.5 to users in Ubuntu 14.04, when it was still undeprecated, so I think it is worth fixing in 14.04. Note that in Ubuntu 15.04 and later, 5.6 is shipped, and mysqlhotcopy is in fact shown as deprecated: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/vivid/mysql-5.6/vivid/view/head:/scripts/mysqlhotcopy.sh#L161 Now, my personal feeling is that users should stop using it _immediately_ because it really is a terrible thing to rely on. But, we take bugs that might affect data integrity, including backups, pretty seriously. ** Also affects: mysql-5.5 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: mysql-5.5 (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: mysql-5.5 (Ubuntu Trusty) Status: New = Triaged ** Changed in: mysql-5.5 (Ubuntu Utopic) Status: New = Triaged ** Changed in: mysql-5.5 (Ubuntu Trusty) Importance: Undecided = High ** Changed in: mysql-5.5 (Ubuntu Utopic) Importance: Undecided = High ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid ** Changed in: mysql-5.5 (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450803 Title: mysqlhotcopy: error in SQL syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1450803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450803] Re: mysqlhotcopy: error in SQL syntax
leonick, can you please provide a clear step by step test case for us to follow so we can be sure the patch works? Also, if you could re-make the patch in unified format with 'diff -u' that would help make it easier to apply, though we can manually apply it if you're unable to provide a unified diff. ** Changed in: mysql-5.5 (Ubuntu) Status: Invalid = Incomplete ** Changed in: mysql-5.5 (Ubuntu) Assignee: (unassigned) = leonick (leonick) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450803 Title: mysqlhotcopy: error in SQL syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1450803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450803] Re: mysqlhotcopy: error in SQL syntax
leonick, can you please provide a clear step by step test case for us to follow so we can be sure the patch works? Also, if you could re-make the patch in unified format with 'diff -u' that would help make it easier to apply, though we can manually apply it if you're unable to provide a unified diff. ** Changed in: mysql-5.5 (Ubuntu) Status: Invalid = Incomplete ** Changed in: mysql-5.5 (Ubuntu) Assignee: (unassigned) = leonick (leonick) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1450803 Title: mysqlhotcopy: error in SQL syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1450803/+subscriptions -- 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 1240049] Re: multipath udev rules problem
This bug is not Incomplete, as we don't need more information from users. This bug was fixed, and is a Medium status because the problem reported was the erroneous warnings. We don't fix Medium bugs in SRU. So I've marked the Trusty portion as Won't Fix. The lack of 0.5 and its udev listening features in trusty is also likely not going to be fixable as an SRU, unless an exception is made to allow this new feature. 0.5 should be merged into vivid+1 and backports used to bring the new udev functionality to trusty users. However, multipath being a non-leaf package, that may also be difficult as extensive testing would be necessary. ** Changed in: multipath-tools (Ubuntu) Status: Incomplete = Fix Released ** Changed in: multipath-tools (Ubuntu Trusty) Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1240049 Title: multipath udev rules problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1240049/+subscriptions -- 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 1240049] Re: multipath udev rules problem
This bug is not Incomplete, as we don't need more information from users. This bug was fixed, and is a Medium status because the problem reported was the erroneous warnings. We don't fix Medium bugs in SRU. So I've marked the Trusty portion as Won't Fix. The lack of 0.5 and its udev listening features in trusty is also likely not going to be fixable as an SRU, unless an exception is made to allow this new feature. 0.5 should be merged into vivid+1 and backports used to bring the new udev functionality to trusty users. However, multipath being a non-leaf package, that may also be difficult as extensive testing would be necessary. ** Changed in: multipath-tools (Ubuntu) Status: Incomplete = Fix Released ** Changed in: multipath-tools (Ubuntu Trusty) Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240049 Title: multipath udev rules problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1240049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200288] Re: yum urlgrabber error in lxc-create -t fedora
This has been verified for almost 2 weeks. Any reason it isn't released to trusty-updates yet? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to urlgrabber in Ubuntu. https://bugs.launchpad.net/bugs/1200288 Title: yum urlgrabber error in lxc-create -t fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urlgrabber/+bug/1200288/+subscriptions -- 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 1200288] Re: yum urlgrabber error in lxc-create -t fedora
This has been verified for almost 2 weeks. Any reason it isn't released to trusty-updates yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1200288 Title: yum urlgrabber error in lxc-create -t fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urlgrabber/+bug/1200288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200288] Re: yum urlgrabber error in lxc-create -t fedora
Tested on 14.04 from trusty-proposed, works! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to urlgrabber in Ubuntu. https://bugs.launchpad.net/bugs/1200288 Title: yum urlgrabber error in lxc-create -t fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urlgrabber/+bug/1200288/+subscriptions -- 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 1200288] Re: yum urlgrabber error in lxc-create -t fedora
Tested on 14.04 from trusty-proposed, works! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1200288 Title: yum urlgrabber error in lxc-create -t fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urlgrabber/+bug/1200288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200288] Re: yum error in lxc-create -t fedora
** Also affects: urlgrabber (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: urlgrabber (Ubuntu Trusty) Status: New = In Progress ** Changed in: urlgrabber (Ubuntu Trusty) Importance: Undecided = High ** Changed in: urlgrabber (Ubuntu Trusty) Assignee: (unassigned) = Clint Byrum (clint-fewbar) ** Summary changed: - yum error in lxc-create -t fedora + yum urlgrabber error in lxc-create -t fedora -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1200288 Title: yum urlgrabber error in lxc-create -t fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urlgrabber/+bug/1200288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200288] Re: yum error in lxc-create -t fedora
** Also affects: urlgrabber (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: urlgrabber (Ubuntu Trusty) Status: New = In Progress ** Changed in: urlgrabber (Ubuntu Trusty) Importance: Undecided = High ** Changed in: urlgrabber (Ubuntu Trusty) Assignee: (unassigned) = Clint Byrum (clint-fewbar) ** Summary changed: - yum error in lxc-create -t fedora + yum urlgrabber error in lxc-create -t fedora -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to urlgrabber in Ubuntu. https://bugs.launchpad.net/bugs/1200288 Title: yum urlgrabber error in lxc-create -t fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urlgrabber/+bug/1200288/+subscriptions -- 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 1200288] Re: yum error in lxc-create -t fedora
This is pretty badly broken, and fixed already in Debian and everywhere else. ** Changed in: urlgrabber (Ubuntu) Status: Confirmed = Triaged ** Changed in: urlgrabber (Ubuntu) Importance: Undecided = Critical ** Changed in: urlgrabber (Ubuntu) Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to urlgrabber in Ubuntu. https://bugs.launchpad.net/bugs/1200288 Title: yum error in lxc-create -t fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urlgrabber/+bug/1200288/+subscriptions -- 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 1200288] Re: yum error in lxc-create -t fedora
This is pretty badly broken, and fixed already in Debian and everywhere else. ** Changed in: urlgrabber (Ubuntu) Status: Confirmed = Triaged ** Changed in: urlgrabber (Ubuntu) Importance: Undecided = Critical ** Changed in: urlgrabber (Ubuntu) Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1200288 Title: yum error in lxc-create -t fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urlgrabber/+bug/1200288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200288] Re: yum urlgrabber error in lxc-create -t fedora
** Description changed: + [Impact] + + * Users wishing to use Yum on Ubuntu to build Fedora packages will be + met with a backtrace due to curl changing its' API. This makes + urlgrabber basically unusable without forcing turning off SSL + certification verification, which is not acceptible. + + [Test Case] + + * Install yum-utils + * Ensure sslverify in section main is not set, or is 1 in /etc/yum/yum.conf + * Create a working directory for testing, reference as WORKING + * mkdir $WORKING/yum.repos.d + * Add attached fedora.repo to $WORKING/yum.repos.d + * mkdir $WORKING/var/lib/rpm + * rpm --rootdir=$WORKING initdb + * yumdownloader --releasever=21 --setopt-reposdir=$WORKING/yum.repos.d --destdir=$WORKING + + The yumdownloader step will fail with a traceback ending in + pycurl.error: (43, 'CURLOPT_SSL_VERIFYHOST no longer supports 1 as + value!') + + [Regression Potential] + + * Since the library is mostly inoperable when running without SSL + verification, regressions seem unlikely. + + * The additional fix for keepalives which was included upstream is low + risk also as it simply makes the code resilient to a known failure by + not allowing incompatible options to be used together. + + [Other Info] + N/A + + Original Report + On ubuntu 13.04 with yum: 3.4.3-1ubuntu1 lxc: 0.9.0-0ubuntu3.3 lxc-templates: 0.9.0-0ubuntu3.3 - When attempting to create a fedora Linux Container, I see $ sudo lxc-create -n fed1 -t fedora lxc-create: No config file specified, using the default config /etc/lxc/default.conf This is not a fedora host and release missing, defaulting to 14. use -R|--release to specify release - Checking cache download in /var/cache/lxc/fedora/x86_64/14/rootfs ... + Checking cache download in /var/cache/lxc/fedora/x86_64/14/rootfs ... Downloading fedora minimal ... Fetching from http://kdeforge.unl.edu/mirrors/fedora-archive/fedora/linux/releases/14/Everything/x86_64/os//Packages/fedora-release-14-1.noarch.rpm - % Total% Received % Xferd Average Speed TimeTime Time Current - Dload Upload Total SpentLeft Speed + % Total% Received % Xferd Average Speed TimeTime Time Current + Dload Upload Total SpentLeft Speed 100 24404 100 244040 0 41435 0 --:--:-- --:--:-- --:--:-- 43192 rpm: RPM should not be used directly install RPM packages, use Alien instead! rpm: However assuming you know what you are doing... warning: /var/cache/lxc/fedora/x86_64/14/partial/fedora-release-14.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY Preparing... # [100%] - package fedora-release-14-1.noarch is already installed + package fedora-release-14-1.noarch is already installed Traceback (most recent call last): - File /usr/bin/yum, line 29, in module - yummain.user_main(sys.argv[1:], exit_code=True) - File /usr/share/yum-cli/yummain.py, line 288, in user_main - errcode = main(args) - File /usr/share/yum-cli/yummain.py, line 140, in main - result, resultmsgs = base.doCommands() - File /usr/share/yum-cli/cli.py, line 436, in doCommands - self._getTs(needTsRemove) - File /usr/lib/python2.7/dist-packages/yum/depsolve.py, line 101, in _getTs - self._getTsInfo(remove_only) - File /usr/lib/python2.7/dist-packages/yum/depsolve.py, line 112, in _getTsInfo - pkgSack = self.pkgSack - File /usr/lib/python2.7/dist-packages/yum/__init__.py, line 892, in lambda - pkgSack = property(fget=lambda self: self._getSacks(), - File /usr/lib/python2.7/dist-packages/yum/__init__.py, line 673, in _getSacks - self.repos.populateSack(which=repos) - File /usr/lib/python2.7/dist-packages/yum/repos.py, line 294, in populateSack - sack.populate(repo, mdtype, callback, cacheonly) - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 168, in populate - if self._check_db_version(repo, mydbtype): - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 226, in _check_db_version - return repo._check_db_version(mdtype) - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1268, in _check_db_version - repoXML = self.repoXML - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1467, in lambda - repoXML = property(fget=lambda self: self._getRepoXML(), - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1459, in _getRepoXML - self._loadRepoXML(text=self) - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1449, in _loadRepoXML - return self._groupLoadRepoXML(text, self._mdpolicy2mdtypes()) - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1424, in _groupLoadRepoXML - if self._commonLoadRepoXML(text): - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1242, in _commonLoadRepoXML - result =
[Bug 1200288] Re: yum urlgrabber error in lxc-create -t fedora
** Description changed: + [Impact] + + * Users wishing to use Yum on Ubuntu to build Fedora packages will be + met with a backtrace due to curl changing its' API. This makes + urlgrabber basically unusable without forcing turning off SSL + certification verification, which is not acceptible. + + [Test Case] + + * Install yum-utils + * Ensure sslverify in section main is not set, or is 1 in /etc/yum/yum.conf + * Create a working directory for testing, reference as WORKING + * mkdir $WORKING/yum.repos.d + * Add attached fedora.repo to $WORKING/yum.repos.d + * mkdir $WORKING/var/lib/rpm + * rpm --rootdir=$WORKING initdb + * yumdownloader --releasever=21 --setopt-reposdir=$WORKING/yum.repos.d --destdir=$WORKING + + The yumdownloader step will fail with a traceback ending in + pycurl.error: (43, 'CURLOPT_SSL_VERIFYHOST no longer supports 1 as + value!') + + [Regression Potential] + + * Since the library is mostly inoperable when running without SSL + verification, regressions seem unlikely. + + * The additional fix for keepalives which was included upstream is low + risk also as it simply makes the code resilient to a known failure by + not allowing incompatible options to be used together. + + [Other Info] + N/A + + Original Report + On ubuntu 13.04 with yum: 3.4.3-1ubuntu1 lxc: 0.9.0-0ubuntu3.3 lxc-templates: 0.9.0-0ubuntu3.3 - When attempting to create a fedora Linux Container, I see $ sudo lxc-create -n fed1 -t fedora lxc-create: No config file specified, using the default config /etc/lxc/default.conf This is not a fedora host and release missing, defaulting to 14. use -R|--release to specify release - Checking cache download in /var/cache/lxc/fedora/x86_64/14/rootfs ... + Checking cache download in /var/cache/lxc/fedora/x86_64/14/rootfs ... Downloading fedora minimal ... Fetching from http://kdeforge.unl.edu/mirrors/fedora-archive/fedora/linux/releases/14/Everything/x86_64/os//Packages/fedora-release-14-1.noarch.rpm - % Total% Received % Xferd Average Speed TimeTime Time Current - Dload Upload Total SpentLeft Speed + % Total% Received % Xferd Average Speed TimeTime Time Current + Dload Upload Total SpentLeft Speed 100 24404 100 244040 0 41435 0 --:--:-- --:--:-- --:--:-- 43192 rpm: RPM should not be used directly install RPM packages, use Alien instead! rpm: However assuming you know what you are doing... warning: /var/cache/lxc/fedora/x86_64/14/partial/fedora-release-14.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY Preparing... # [100%] - package fedora-release-14-1.noarch is already installed + package fedora-release-14-1.noarch is already installed Traceback (most recent call last): - File /usr/bin/yum, line 29, in module - yummain.user_main(sys.argv[1:], exit_code=True) - File /usr/share/yum-cli/yummain.py, line 288, in user_main - errcode = main(args) - File /usr/share/yum-cli/yummain.py, line 140, in main - result, resultmsgs = base.doCommands() - File /usr/share/yum-cli/cli.py, line 436, in doCommands - self._getTs(needTsRemove) - File /usr/lib/python2.7/dist-packages/yum/depsolve.py, line 101, in _getTs - self._getTsInfo(remove_only) - File /usr/lib/python2.7/dist-packages/yum/depsolve.py, line 112, in _getTsInfo - pkgSack = self.pkgSack - File /usr/lib/python2.7/dist-packages/yum/__init__.py, line 892, in lambda - pkgSack = property(fget=lambda self: self._getSacks(), - File /usr/lib/python2.7/dist-packages/yum/__init__.py, line 673, in _getSacks - self.repos.populateSack(which=repos) - File /usr/lib/python2.7/dist-packages/yum/repos.py, line 294, in populateSack - sack.populate(repo, mdtype, callback, cacheonly) - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 168, in populate - if self._check_db_version(repo, mydbtype): - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 226, in _check_db_version - return repo._check_db_version(mdtype) - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1268, in _check_db_version - repoXML = self.repoXML - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1467, in lambda - repoXML = property(fget=lambda self: self._getRepoXML(), - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1459, in _getRepoXML - self._loadRepoXML(text=self) - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1449, in _loadRepoXML - return self._groupLoadRepoXML(text, self._mdpolicy2mdtypes()) - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1424, in _groupLoadRepoXML - if self._commonLoadRepoXML(text): - File /usr/lib/python2.7/dist-packages/yum/yumRepo.py, line 1242, in _commonLoadRepoXML - result =
[Bug 1428377] Re: [FFE] Sync new package liberasurecode (for vivid) Backport for Ubuntu 14.04 LTS)
Scott thanks so much for the sync. I'm testing now and it appears the backport to trusty will require two more backports of things that don't exist in trusty: gf-complete jerasure I will do additional testing on these later today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428377 Title: [FFE] Sync new package liberasurecode (for vivid) Backport for Ubuntu 14.04 LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1428377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428377] Re: [FFE] Sync new package liberasurecode (for vivid) Backport for Ubuntu 14.04 LTS)
no-change backports of all three packages resulted in successful build and test by me using sbuild and by user on their own trusty system. To reiterate: gf-complete jerasure liberasurecode Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428377 Title: [FFE] Sync new package liberasurecode (for vivid) Backport for Ubuntu 14.04 LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1428377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428377] Re: [FFE] New package liberasurecode (for vivid and Ubuntu 14.04 LTS)
Hi Ubuntu release team. I'm hoping we can have liberasurecode in universe for vivid. Please advise if this is feasible seeing as it has now passed Debian NEW. ** Also affects: trusty-backports Importance: Undecided Status: New ** Summary changed: - [FFE] New package liberasurecode (for vivid and Ubuntu 14.04 LTS) + [FFE] Sync new package liberasurecode (for vivid) Backport for Ubuntu 14.04 LTS) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428377 Title: [FFE] Sync new package liberasurecode (for vivid) Backport for Ubuntu 14.04 LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1428377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428377] Re: [FFE] Please sync liberasurecode from Debian Jessie
FYI, this is not accpted into Debian just yet. The ITP is still pending. Seems unlikely we'd get a special NEW ubuntu version in time for vivid. ** Summary changed: - Please sync liberasurecode from Debian Jessie + [FFE] Please sync liberasurecode from Debian Jessie ** Description changed: + This is a feature freeze exception request. The library is strategically + important for swift, a component of OpenStack. Thank you for considering + this fairly simple library sync for vivid. + liberasurecode is part of Debian Jessie - this package is critical for getting erasure coding functionality into OpenStack Swift (Kilo). http://kilo-jessie.pkgs.mirantis.com/debian/pool/jessie-kilo- backports/main/l/liberasurecode/ For some reason, this package hasn't been sync'ed to Ubuntu since it was created by Debian maintainer (Zigo) last October - please help sync this package to Ubuntu 14.04.2 LTS. ** Summary changed: - [FFE] Please sync liberasurecode from Debian Jessie + [FFE] New package liberasurecode ** Bug watch added: Debian Bug tracker #769516 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769516 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769516 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428377 Title: [FFE] New package liberasurecode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1428377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428377] Re: [FFE] New package liberasurecode
I've unsubscribed ubuntu-release until there is an actual action they can take. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428377 Title: [FFE] New package liberasurecode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1428377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412719] Re: wait-for-state restarts whoopsie every 30sec
Michael, agree that 'started' is the wrong thing to look for and has probably caused a few confusing things through the years since wait-for- state has been in use. I think the patch should be merged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412719 Title: wait-for-state restarts whoopsie every 30sec To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1412719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413279] Re: upstart event static-network-up emited to early
Thanks for the bug report john! This makes perfect sense to me. The original was written assuming eth0 would only have one /e/n/i section, but in the file above, it has two. I think the answer is to include the address family, so eth0.inet and eth0.inet6 should be two different interfaces so the script will continue to wait until both are up. ** Changed in: ifupdown (Ubuntu) Status: New = Triaged ** Changed in: ifupdown (Ubuntu) Importance: Undecided = High ** Tags added: ipv6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413279 Title: upstart event static-network-up emited to early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1413279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311987] Re: deploy-ironic ramdisks do not boot: Failed to execute /init (error -28)
subair, Can you open a new bug with a full description of the problem you are having, including the steps you took to get there so we can reproduce? This one is pretty specific to booting the deploy ramdisk on machines with less than 1GB of RAM. THANKS! ** Changed in: diskimage-builder Assignee: subair (muhsubair74) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311987 Title: deploy-ironic ramdisks do not boot: Failed to execute /init (error -28) To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1311987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382607] Re: [SRU] Backport python3.4 logging module backward incompatibility fix.
API breaks are bad, mmmkay. Setting to Critical. ** Changed in: python3.4 (Ubuntu) Status: New = Triaged ** Changed in: python3.4 (Ubuntu) Importance: Undecided = Critical ** Also affects: python3.4 (Ubuntu Utopic) Importance: Critical Status: Triaged ** Also affects: python3.4 (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: python3.4 (Ubuntu Trusty) Status: New = Triaged ** Changed in: python3.4 (Ubuntu Trusty) Importance: Undecided = High ** Changed in: python3.4 (Ubuntu Utopic) Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382607 Title: [SRU] Backport python3.4 logging module backward incompatibility fix. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1382607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382607] Re: [SRU] Backport python3.4 logging module backward incompatibility fix.
Forgetting myself, dropping to High .. we need this to be fixed really soon, but it doesn't break EVERYBODY -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382607 Title: [SRU] Backport python3.4 logging module backward incompatibility fix. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1382607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382607] Re: [SRU] Backport python3.4 logging module backward incompatibility fix.
This is fixed upstream in 3.4.2, so it only affects Trusty. ** Changed in: python3.4 (Ubuntu Utopic) 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/1382607 Title: [SRU] Backport python3.4 logging module backward incompatibility fix. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1382607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382607] Re: [SRU] Backport python3.4 logging module backward incompatibility fix.
** Changed in: python3.4 (Ubuntu Trusty) Assignee: (unassigned) = Clint Byrum (clint-fewbar) ** Changed in: python3.4 (Ubuntu Trusty) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382607 Title: [SRU] Backport python3.4 logging module backward incompatibility fix. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1382607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382607] Re: [SRU] Backport python3.4 logging module backward incompatibility fix.
Looks like there is a backport of 3.4.2 to trusty in the works tracking at bug #1348954 ** Changed in: python3.4 (Ubuntu Trusty) Assignee: Clint Byrum (clint-fewbar) = (unassigned) ** Changed in: python3.4 (Ubuntu Trusty) Status: In Progress = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382607 Title: [SRU] Backport python3.4 logging module backward incompatibility fix. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1382607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379427] Re: /etc/network/if-up.d/upstart emits static-network-up to early
Nice find, and confirmed on trusty. ** Changed in: ifupdown (Ubuntu) Status: New = Triaged ** Changed in: ifupdown (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379427 Title: /etc/network/if-up.d/upstart emits static-network-up to early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1379427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378001] Re: package mysql-server-5.5 5.5.38-0ubuntu0.14.04.1 failed to install/upgrade: η υποδιεργασία νέο σενάριο pre-installation επέστρεψε κατάσταση λάθους 1
Hi! I can appreciate the difficult position you've found yourself in, and if we could help, I think we would. However, third party MySQL packages aren't exactly supported by Ubuntu. Your error log shows normal operation: 141006 18:35:13 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 141006 18:35:13 [Note] Plugin 'FEDERATED' is disabled. 141006 18:35:13 [Note] Plugin 'InnoDB' is disabled. 141006 18:35:13 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 141006 18:35:13 [Note] - '127.0.0.1' resolves to '127.0.0.1'; 141006 18:35:13 [Note] Server socket created on IP: '127.0.0.1'. 141006 18:35:14 [Note] Event Scheduler: Loaded 0 events 141006 18:35:14 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.38-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Anyway, I'd suggest restoring from backups. This is the result of a third party package, and not a bug in the MySQL packages. So unless you have more information to share, I'm closing this bug as Invalid. ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1378001 Title: package mysql-server-5.5 5.5.38-0ubuntu0.14.04.1 failed to install/upgrade: η υποδιεργασία νέο σενάριο pre-installation επέστρεψε κατάσταση λάθους 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1378001/+subscriptions -- 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 1378001] Re: package mysql-server-5.5 5.5.38-0ubuntu0.14.04.1 failed to install/upgrade: η υποδιεργασία νέο σενάριο pre-installation επέστρεψε κατάσταση λάθους 1
Hi! I can appreciate the difficult position you've found yourself in, and if we could help, I think we would. However, third party MySQL packages aren't exactly supported by Ubuntu. Your error log shows normal operation: 141006 18:35:13 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 141006 18:35:13 [Note] Plugin 'FEDERATED' is disabled. 141006 18:35:13 [Note] Plugin 'InnoDB' is disabled. 141006 18:35:13 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 141006 18:35:13 [Note] - '127.0.0.1' resolves to '127.0.0.1'; 141006 18:35:13 [Note] Server socket created on IP: '127.0.0.1'. 141006 18:35:14 [Note] Event Scheduler: Loaded 0 events 141006 18:35:14 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.38-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Anyway, I'd suggest restoring from backups. This is the result of a third party package, and not a bug in the MySQL packages. So unless you have more information to share, I'm closing this bug as Invalid. ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378001 Title: package mysql-server-5.5 5.5.38-0ubuntu0.14.04.1 failed to install/upgrade: η υποδιεργασία νέο σενάριο pre-installation επέστρεψε κατάσταση λάθους 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1378001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1357713] Re: ifupdown and upstart can be removed
Doesn't ifupdown still bring up lo? Excerpts from Martin Pitt's message of 2014-09-23 06:17:10 UTC: ubuntu-minimal depends on upstart and ifupdown, so supposedly you removed that. This is really not a supported configuration. As for upstart: Debian has a new essential package init which depends on systemd-sysv | upstart | sysvinit. We could decide to adopt that. Moving to init-system-helpers for that. As for ifupdown: ;Most desktops, phones, etc. use dynamic network configuration with NetworkManager, there is no essential need for ifupdown. But still, of course you can shoot yourself into the foot by randomly removing packages. So just don't do that then :-) ** Package changed: upstart (Ubuntu) = init-system-helpers (Ubuntu) ** Changed in: init-system-helpers (Ubuntu) Importance: Undecided = Low ** Changed in: init-system-helpers (Ubuntu) Status: New = Triaged ** Changed in: ifupdown (Ubuntu) Status: New = Invalid ** Summary changed: - ifupdown and upstart can be removed + Use essential init package to ensure that an init system is present -- You received this bug notification because you are subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential init package to ensure that an init system is present Status in “ifupdown” package in Ubuntu: Invalid Status in “init-system-helpers” package in Ubuntu: Triaged Bug description: I'm using Ubuntu 14.10 dev with ifupdown 0.7.48.1ubuntu4 and upstart 1.13.1-0ubuntu3 and currently it is possible to remove ifupdown and upstart as they are not essential packages or any essential/manual package does depend on them. Here is the output: root@ubuntu:/# apt-get remove ifupdown Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: ifupdown upstart 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 895 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. As I know Ubuntu wants to change from upstart to systemd in the future so removing upstart may be fine but I'm wondering why ifupdown can be removed (wouldn't this remove the ability to create a network connection?). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential init package to ensure that an init system is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- 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
Re: [Bug 1357713] Re: ifupdown and upstart can be removed
Doesn't ifupdown still bring up lo? Excerpts from Martin Pitt's message of 2014-09-23 06:17:10 UTC: ubuntu-minimal depends on upstart and ifupdown, so supposedly you removed that. This is really not a supported configuration. As for upstart: Debian has a new essential package init which depends on systemd-sysv | upstart | sysvinit. We could decide to adopt that. Moving to init-system-helpers for that. As for ifupdown: ;Most desktops, phones, etc. use dynamic network configuration with NetworkManager, there is no essential need for ifupdown. But still, of course you can shoot yourself into the foot by randomly removing packages. So just don't do that then :-) ** Package changed: upstart (Ubuntu) = init-system-helpers (Ubuntu) ** Changed in: init-system-helpers (Ubuntu) Importance: Undecided = Low ** Changed in: init-system-helpers (Ubuntu) Status: New = Triaged ** Changed in: ifupdown (Ubuntu) Status: New = Invalid ** Summary changed: - ifupdown and upstart can be removed + Use essential init package to ensure that an init system is present -- You received this bug notification because you are subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential init package to ensure that an init system is present Status in “ifupdown” package in Ubuntu: Invalid Status in “init-system-helpers” package in Ubuntu: Triaged Bug description: I'm using Ubuntu 14.10 dev with ifupdown 0.7.48.1ubuntu4 and upstart 1.13.1-0ubuntu3 and currently it is possible to remove ifupdown and upstart as they are not essential packages or any essential/manual package does depend on them. Here is the output: root@ubuntu:/# apt-get remove ifupdown Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: ifupdown upstart 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 895 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. As I know Ubuntu wants to change from upstart to systemd in the future so removing upstart may be fine but I'm wondering why ifupdown can be removed (wouldn't this remove the ability to create a network connection?). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential init package to ensure that an init system is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332226] [NEW] sensible-browser opens a new chromium even if one is already running
Public bug reported: This fails terribly because the new chromium cannot lock the profile and just generally doesn't work well. sensible-browser should be opening a new window in an existing instance of a browser. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sensible-utils 0.0.9 Uname: Linux 3.13.0-031300rc3-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 19 10:50:21 2014 Dependencies: InstallationDate: Installed on 2013-01-14 (521 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121017.3) PackageArchitecture: all SourcePackage: sensible-utils UpgradeStatus: Upgraded to trusty on 2014-04-18 (62 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332226 Title: sensible-browser opens a new chromium even if one is already running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1332226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332226] Re: sensible-browser opens a new chromium even if one is already running
Which is actually chromium itself. ** Package changed: sensible-utils (Ubuntu) = chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332226 Title: sensible-browser opens a new chromium even if one is already running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1332226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332226] Re: sensible-browser opens a new chromium even if one is already running
FYI this may actually be about gnome-www-browser: + exec /usr/bin/gnome-www-browser -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332226 Title: sensible-browser opens a new chromium even if one is already running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1332226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1021471] Re: clone() hang when creating new network namespace (dmesg show unregister_netdevice: waiting for lo to become free. Usage count = 2)
Raring is EOL since January 27: https://wiki.ubuntu.com/Releases Excerpts from Alessandro Moscatelli's message of 2014-06-12 22:23:52 UTC: It looks I have this problem with Ubuntu Raring kernel version : 3.8.13 I attached a screenshot with dmesg after I tried to start again my containers. Should I open a new bug ? Thank you in advance ** Attachment added: screenshot https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021471/+attachment/4130637/+files/5.png -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1021471 Title: clone() hang when creating new network namespace (dmesg show unregister_netdevice: waiting for lo to become free. Usage count = 2) Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Bug description: SRU Justification: Impact: When creating new network namespace dmesg can show the following unregister_netdevice: waiting for lo to become free. Usage count = 1 Fix: Stefan Bader's SAUCE patch has fixed this for Quantal: UBUNTU: SAUCE: net/ipv4: Always flush route cache on unregister batch call Testcase: The sourcecode found here: https://lists.debian.org/debian-kernel/2012/05/msg00494.html can be compiled and run as follows: sudo ./reproducer #ctrl+c sudo ./reproducer #wait for a while dmesg | grep unregister -- I'm not sure how I triggered this. I've been moving around between networks and suspending/resuming all day. Earlier in this boot I successfully used a container (start, networking and stop). I came to start the same one later and noticed that it didn't come up. Trying to attach to the console with lxc- console informed me that it wasn't running. I then saw suspicious content in dmesg: [25800.412234] INFO: task lxc-start:25817 blocked for more than 120 seconds. [25800.412243] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [25800.412254] lxc-start D 88013fd13980 0 25817 1 0x [25800.412266] 880007b43cc0 0086 88003ba4c500 880007b43fd8 [25800.412275] 880007b43fd8 880007b43fd8 880134c65c00 88003ba4c500 [25800.412284] 80d0 81ca7c00 88003ba4c500 81ca7c04 [25800.412288] Call Trace: [25800.412306] [81673759] schedule+0x29/0x70 [25800.412313] [81673a1e] schedule_preempt_disabled+0xe/0x10 [25800.412323] [81672537] __mutex_lock_slowpath+0xd7/0x150 [25800.412331] [8167200a] mutex_lock+0x2a/0x50 [25800.412340] [8155ede1] copy_net_ns+0x71/0x100 [25800.412350] [8107adfb] create_new_namespaces+0xdb/0x190 [25800.412357] [8107afec] copy_namespaces+0x8c/0xd0 [25800.412367] [81050142] copy_process.part.22+0x902/0x1520 [25800.412375] [81050ee5] do_fork+0x135/0x390 [25800.412385] [8116db40] ? kmem_cache_free+0x20/0x100 [25800.412395] [8118c6b3] ? putname+0x33/0x50 [25800.412402] [811811cc] ? do_sys_open+0x16c/0x200 [25800.412410] [8101c238] sys_clone+0x28/0x30 [25800.412418] [8167cbf3] stub_clone+0x13/0x20 [25800.412424] [8167c8e9] ? system_call_fastpath+0x16/0x1b [25806.312385] unregister_netdevice: waiting for lo to become free. Usage count = 1 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-generic 3.5.0.3.3 ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4 Uname: Linux 3.5.0-2-generic x86_64 NonfreeKernelModules: nvidia wl AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: NVidia [HDA NVidia], device 0: Cirrus Analog [Cirrus Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: laney 2787 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xd348 irq 22' Mixer name: 'Nvidia MCP89 HDMI' Components: 'HDA:10134206,106b0d00,00100301 HDA:10de000c,10de0101,00100200' Controls : 37 Simple ctrls : 13 Date: Thu Jul 5 21:26:08 2012 HibernationDevice: RESUME=UUID=1c5b3f2c-2c89-4fa1-9ed8-0e238de8fe47 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100729) MachineType: Apple Inc. MacBookPro7,1 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-2-generic
Re: [Bug 1309584] Re: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves
FYI, I have experienced this again. It seems to only happen on resume from suspend. Excerpts from Joseph Salisbury's message of 2014-05-13 18:34:24 UTC: ** Changed in: linux (Ubuntu) Status: Triaged = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1309584 Title: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves Status in “linux” package in Ubuntu: Incomplete Bug description: I am running on an HP EliteBook Folio 9470m which has an i915 video chipset. After upgrading to 14.04, the backlight and brightness controls do not work on the laptop screen. $ sudo intel_backlight current backlight value: 4% ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 18 08:02:05 2014 DistUpgraded: 2014-04-18 01:03:05,027 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: openvswitch, 2.0.1+git20140120: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:18df] InstallationDate: Installed on 2013-01-14 (459 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121017.3) MachineType: Hewlett-Packard HP EliteBook Folio 9470m ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu-root ro quiet splash acpi_osi=!Windows 2012 vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago) dmi.bios.date: 09/24/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IBD Ver. F.30 dmi.board.name: 18DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 62.13 dmi.chassis.asset.tag: CNU2439PZT dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IBDVer.F.30:bd09/24/2012:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1103:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.13:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 9470m dmi.product.version: A1029D1103 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Apr 18 01:04:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5239 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309584 Title: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
Excerpts from Jason Gerard DeRose's message of 2014-05-08 16:45:23 UTC: Stéphane, Gotcha, thanks for the feedback! So am I correct in thinking that the --xattrs option is currently broken in tar on 14.04? If so, is there any chance this could be fixed in an SRU? No, --xattrs works fine in 14.04. The problem is that it must be used. Note that you also have to use --xattrs-include=* while creating the tar to make use of it (which is, IMO, a bug, as if I said --xattrs, I meant _USE XATTRS_. ;) Anyway, another problem is that 12.04 tar does not support it, so the tarball images are not consumable from the previous release, which is a problem for a shop trying to upgrade. I think that may be a worthy SRU, as tars with xattrs will start to become more and more commonplace over the next 3 years that 12.04 is still a supported platform. Certainly somebody should get 14.04's tar into precise-backports while this SRU is debated. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+subscriptions -- 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
Re: [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
Excerpts from Jason Gerard DeRose's message of 2014-05-08 16:45:23 UTC: Stéphane, Gotcha, thanks for the feedback! So am I correct in thinking that the --xattrs option is currently broken in tar on 14.04? If so, is there any chance this could be fixed in an SRU? No, --xattrs works fine in 14.04. The problem is that it must be used. Note that you also have to use --xattrs-include=* while creating the tar to make use of it (which is, IMO, a bug, as if I said --xattrs, I meant _USE XATTRS_. ;) Anyway, another problem is that 12.04 tar does not support it, so the tarball images are not consumable from the previous release, which is a problem for a shop trying to upgrade. I think that may be a worthy SRU, as tars with xattrs will start to become more and more commonplace over the next 3 years that 12.04 is still a supported platform. Certainly somebody should get 14.04's tar into precise-backports while this SRU is debated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816758] Re: libedit lacks utf-8 support
Fred, it is fixed in utopic. I have not evaluated the patch that fixes it, but it may be appropriate for SRU: https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/816758 Title: libedit lacks utf-8 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/816758/+subscriptions -- 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 816758] Re: libedit lacks utf-8 support
Fred, it is fixed in utopic. I have not evaluated the patch that fixes it, but it may be appropriate for SRU: https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816758 Title: libedit lacks utf-8 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/816758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313550] [NEW] ping does not work as a normal user on trusty tarball cloud images.
Public bug reported: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. ** Affects: iputils (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/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1313550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312513] Re: MySQL Server 5.5.35 to 5.5.37 upgrade crashing mysql.help_topic
** Changed in: mysql-5.5 (Ubuntu) Importance: Undecided = Critical ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312513 Title: MySQL Server 5.5.35 to 5.5.37 upgrade crashing mysql.help_topic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1312513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309584] Re: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves
Trying 3.12 now. Note that I discovered a new symptom today: when a monitor is plugged into the DisplayPort, the brightness controls in Brightness and Lock work, but the keyboard controls still don't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309584 Title: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309584] Re: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves
Backlight controls work flawlessly with 3.12 final. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309584 Title: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309584] Re: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves
Actually.. this is quite embarrassing, I installed 3.12, but my system didn't show a grub menu and I actually booted 3.13.0-24-generic Not sure how that happened, but it actually appears that the issue has gone away somehow. Could still be a race maybe? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309584 Title: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1309584] Re: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves
Excerpts from Joseph Salisbury's message of 2014-04-23 18:46:43 UTC: Hmm, do you still have acpi_backlight=vendor? If not, I guess it would be good to test the 3.13.0-24-generic kernel for a while to ensure the bug doesn't come back. I do not. I wonder if it is also possible that I booted w/ EFI or something else that caused this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309584 Title: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309584] Re: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves
Tested with 3.15-rc2, backlight control still did not work. ** 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/1309584 Title: [HP EliteBook Folio 9470m Notebook PC] Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309584] [NEW] Backlight does not work on intel driver after upgrade from 13.10 - 14.04
Public bug reported: I am running on an HP EliteBook Folio 9470m which has an i915 video chipset. After upgrading to 14.04, the backlight and brightness controls do not work on the laptop screen. $ sudo intel_backlight current backlight value: 4% ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 18 08:02:05 2014 DistUpgraded: 2014-04-18 01:03:05,027 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: openvswitch, 2.0.1+git20140120: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:18df] InstallationDate: Installed on 2013-01-14 (459 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121017.3) MachineType: Hewlett-Packard HP EliteBook Folio 9470m ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu-root ro quiet splash acpi_osi=!Windows 2012 vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago) dmi.bios.date: 09/24/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IBD Ver. F.30 dmi.board.name: 18DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 62.13 dmi.chassis.asset.tag: CNU2439PZT dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IBDVer.F.30:bd09/24/2012:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1103:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.13:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 9470m dmi.product.version: A1029D1103 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Apr 18 01:04:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5239 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309584 Title: Backlight does not work on intel driver after upgrade from 13.10 - 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309584] Re: Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves
I just booted with acpi_backlight=vendor and that solves the issue. Happy to help debug the issue to help other users of this hardware avoid 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/1309584 Title: Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309584] Re: Backlight does not work on intel driver after upgrade from 13.10 - 14.04
Seems this is a kernel/firmware/acpi issue. ** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu) ** Summary changed: - Backlight does not work on intel driver after upgrade from 13.10 - 14.04 + Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309584 Title: Backlight does not work on intel driver after upgrade from 13.10 - 14.04, acpi_backlight=vendor solves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
