[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
thanks Allan! For me a simple : rm /lib/firmware/ath11k/WCN6855/hw2.1 is all that was needed before restarting the update process. The result is that before the failed upgrade it looked like this : lrwxrwxrwx 1 root root 5 Feb 17 08:51 hw2.1 -> hw2.0 and after the successful upgrade it now looks like this : drwxr-xr-x 2 root root 6 Mär 15 15:34 . lrwxrwxrwx 1 root root 17 Mär 14 11:40 amss.bin -> ../hw2.0/amss.bin lrwxrwxrwx 1 root root 20 Mär 14 11:40 board-2.bin -> ../hw2.0/board-2.bin lrwxrwxrwx 1 root root 15 Mär 14 11:40 m3.bin -> ../hw2.0/m3.bin lrwxrwxrwx 1 root root 18 Mär 14 11:40 regdb.bin -> ../hw2.0/regdb.bin which at first glance is the same -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208905] Re: Occasionally offlineimap gets stuck and eats up all of my RAM
Oops, my version is: cedar% offlineimap --version 7.2.3 cedar% lsb_release -irc Distributor ID: Ubuntu Release:20.04 Codename: focal cedar% -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208905 Title: Occasionally offlineimap gets stuck and eats up all of my RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/offlineimap/+bug/1208905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208905] Re: Occasionally offlineimap gets stuck and eats up all of my RAM
I have not yet seen offlineimap take oodles of RAM, but I do see it download ~1 message per second with *lots* of selects and futex waits. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208905 Title: Occasionally offlineimap gets stuck and eats up all of my RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/offlineimap/+bug/1208905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station
I have the same issue with my Cable Matters USB-C dual 4k DisplayPort docking station and HP Elitebook laptop. In my experience, it does not occur on every disconnect, however each time it does occur, it appears to be preceded by a kernel oops: [114032.828215] usb 2-1: USB disconnect, device number 50 [114032.828220] usb 2-1.3: USB disconnect, device number 51 [114032.828222] usb 2-1.3.2: USB disconnect, device number 58 [114032.828225] usb 2-1.3.2.1: USB disconnect, device number 59 [114032.829619] [drm] DM_MST: stopping TM on aconnector: 660e4f23 [id: 77] [114032.829741] [drm] DM_MST: Disabling connector: 5955f6aa [id: 95] [master: 660e4f23] [114032.829901] [ cut here ] [114032.829902] sysfs group 'power' not found for kobject 'i2c-11' [114032.829920] WARNING: CPU: 3 PID: 42300 at fs/sysfs/group.c:279 sysfs_remove_group+0x7c/0x80 [114032.829921] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm binfmt_misc rfcomm cmac algif_hash algif_skcipher af_alg cdc_ether usbnet snd_usb_audio snd_usbmidi_lib usbhid r8152 mii bnep btusb btrtl btbcm btintel bluetooth ecdh_generic ecc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common bonding aufs evdi(OE) snd_hda_codec_conexant snd_hda_codec_generic overlay ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd iwlmvm nls_iso8859_1 soundcore mac80211 libarc4 edac_mce_amd iwlwifi kvm_amd ccp kvm hp_wmi joydev input_leds sparse_keymap serio_raw wmi_bmof hid_multitouch cfg80211 ucsi_acpi typec_ucsi ipmi_devintf k10temp ipmi_msghandler typec mac_hid hp_wireless sch_fq_codel v4l2loopback(OE) videodev mc parport_pc ppdev lp parport ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq [114032.829978] async_xor async_tx xor uas usb_storage raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic amdgpu crct10dif_pclmul crc32_pclmul amd_iommu_v2 ghash_clmulni_intel gpu_sched i2c_algo_bit ttm aesni_intel drm_kms_helper i2c_hid crypto_simd hid cryptd syscopyarea sysfillrect glue_helper psmouse sysimgblt nvme fb_sys_fops ahci i2c_piix4 drm libahci nvme_core r8169 realtek wmi video i2c_amd_mp2_plat i2c_amd_mp2_pci [114032.830005] CPU: 3 PID: 42300 Comm: kworker/3:0 Tainted: G OE 5.4.0-42-generic #46-Ubuntu [114032.830007] Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.10.00 01/03/2020 [114032.830019] Workqueue: events drm_dp_destroy_connector_work [drm_kms_helper] [114032.830023] RIP: 0010:sysfs_remove_group+0x7c/0x80 [114032.830026] Code: e7 e8 98 b9 ff ff 5b 41 5c 41 5d 5d c3 4c 89 e7 e8 e9 b4 ff ff eb c9 49 8b 55 00 48 8b 33 48 c7 c7 10 de b8 97 e8 6f 9f d1 ff <0f> 0b eb d8 0f 1f 44 00 00 48 85 f6 74 37 55 48 89 e5 41 55 41 54 [114032.830027] RSP: 0018:abccc0363c18 EFLAGS: 00010286 [114032.830029] RAX: RBX: 978f3c60 RCX: 0006 [114032.830030] RDX: 0007 RSI: 0086 RDI: 9a4d5fcd78c0 [114032.830032] RBP: abccc0363c30 R08: 0c98 R09: 0004 [114032.830032] R10: R11: 0001 R12: [114032.830034] R13: 9a4d135f9418 R14: c0369140 R15: c0369140 [114032.830036] FS: () GS:9a4d5fcc() knlGS: [114032.830037] CS: 0010 DS: ES: CR0: 80050033 [114032.830038] CR2: 55e429698c40 CR3: 00040af48000 CR4: 003406a0 [114032.830039] Call Trace: [114032.830047] dpm_sysfs_remove+0x59/0x60 [114032.830050] device_del+0x85/0x370 [114032.830055] cdev_device_del+0x1a/0x40 [114032.830058] i2cdev_detach_adapter+0x87/0xc0 [114032.830060] i2cdev_notifier_call+0x21/0x40 [114032.830064] notifier_call_chain+0x55/0x80 [114032.830067] blocking_notifier_call_chain+0x50/0x70 [114032.830070] device_del+0x7d/0x370 [114032.830072] device_unregister+0x1b/0x60 [114032.830075] i2c_del_adapter+0x238/0x300 [114032.830085] drm_dp_port_teardown_pdt+0x1f/0x40 [drm_kms_helper] [114032.830096] drm_dp_destroy_connector_work+0xa3/0x110 [drm_kms_helper] [114032.830100] process_one_work+0x1eb/0x3b0 [114032.830104] worker_thread+0x4d/0x400 [114032.830108] kthread+0x104/0x140 [114032.830111] ? process_one_work+0x3b0/0x3b0 [114032.830114] ? kthread_park+0x90/0x90 [114032.830118] ret_from_fork+0x22/0x40 [114032.830124] ---[ end trace 5a351113a270c4cc ]--- [114032.830211] [ cut here ] [114032.830213] sysfs group 'power' not found for kobject 'i2c-11' [114032.830228] WARNING: CPU: 3 PID: 42300 at fs/sysfs/group.c:279 sysfs_remove_group+0x7c/0x80 [114032.830229] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm binfmt_misc rfcomm cmac algif_hash algif_skcipher af_alg cdc_ether usbnet snd_usb_audio snd_usbmidi_lib usbhid r8152 mii bnep btusb
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
It had actually been working fine in 20.04 until a recent kernel update to 5.4.0-33.37. Since the update, it always fails with this stack trace: [140594.217061] [ cut here ] [140594.217062] sysfs group 'power' not found for kobject 'i2c-11' [140594.217079] WARNING: CPU: 5 PID: 64631 at fs/sysfs/group.c:279 sysfs_remove_group+0x7c/0x80 [140594.217080] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc ccm rfcomm cmac algif_hash algif_skcipher af_alg cdc_ether usbnet r8152 mii snd_usb_audio snd_usbmidi_lib bnep bonding btusb btrtl btbcm btintel bluetooth ecdh_generic ecc evdi(OE) aufs uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common overlay nls_iso8859_1 snd_hda_codec_conexant snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd iwlmvm edac_mce_amd mac80211 kvm_amd ccp soundcore libarc4 kvm iwlwifi input_leds joydev serio_raw hp_wmi sparse_keymap ipmi_devintf wmi_bmof hid_multitouch k10temp cfg80211 ipmi_msghandler ucsi_acpi typec_ucsi typec hp_wireless mac_hid sch_fq_codel v4l2loopback(OE) videodev mc parport_pc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage raid10 raid456 async_raid6_recov async_memcpy [140594.217138] async_pq async_xor async_tx xor usbhid raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul hid_generic ghash_clmulni_intel amdgpu amd_iommu_v2 gpu_sched i2c_algo_bit ttm nvme aesni_intel drm_kms_helper syscopyarea sysfillrect crypto_simd sysimgblt i2c_hid fb_sys_fops hid ahci psmouse drm cryptd libahci i2c_piix4 glue_helper nvme_core r8169 realtek wmi video i2c_amd_mp2_plat i2c_amd_mp2_pci [140594.217167] CPU: 5 PID: 64631 Comm: kworker/5:0 Tainted: G OE 5.4.0-33-generic #37-Ubuntu [140594.217169] Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.10.00 01/03/2020 [140594.217183] Workqueue: events drm_dp_destroy_connector_work [drm_kms_helper] [140594.217187] RIP: 0010:sysfs_remove_group+0x7c/0x80 [140594.217191] Code: e7 e8 98 b9 ff ff 5b 41 5c 41 5d 5d c3 4c 89 e7 e8 e9 b4 ff ff eb c9 49 8b 55 00 48 8b 33 48 c7 c7 40 d4 58 a5 e8 4f 90 d1 ff <0f> 0b eb d8 0f 1f 44 00 00 48 85 f6 74 37 55 48 89 e5 41 55 41 54 [140594.217192] RSP: 0018:b1ea82f3fc00 EFLAGS: 00010286 [140594.217194] RAX: RBX: a52f3b60 RCX: 0006 [140594.217196] RDX: 0007 RSI: 0096 RDI: 9085dfd578c0 [140594.217197] RBP: b1ea82f3fc18 R08: 0851 R09: 0004 [140594.217198] R10: R11: 0001 R12: [140594.217199] R13: 9082e1c93800 R14: c0327140 R15: c0327140 [140594.217201] FS: () GS:9085dfd4() knlGS: [140594.217202] CS: 0010 DS: ES: CR0: 80050033 [140594.217204] CR2: 7f81ed808000 CR3: 00041687e000 CR4: 003406a0 [140594.217205] Call Trace: [140594.217213] dpm_sysfs_remove+0x59/0x60 [140594.217217] device_del+0x85/0x370 [140594.217220] ? class_find_device+0x97/0xf0 [140594.217223] device_unregister+0x1b/0x60 [140594.217226] device_destroy+0x4b/0x70 [140594.217229] i2cdev_detach_adapter+0x58/0x90 [140594.217231] i2cdev_notifier_call+0x21/0x40 [140594.217235] notifier_call_chain+0x55/0x80 [140594.217238] blocking_notifier_call_chain+0x50/0x70 [140594.217241] device_del+0x7d/0x370 [140594.217244] device_unregister+0x1b/0x60 [140594.217247] i2c_del_adapter+0x238/0x300 [140594.217257] drm_dp_port_teardown_pdt+0x1f/0x40 [drm_kms_helper] [140594.217267] drm_dp_destroy_connector_work+0xa3/0x110 [drm_kms_helper] [140594.217271] process_one_work+0x1eb/0x3b0 [140594.217274] worker_thread+0x4d/0x400 [140594.217277] kthread+0x104/0x140 [140594.217279] ? process_one_work+0x3b0/0x3b0 [140594.217281] ? kthread_park+0x90/0x90 [140594.217285] ret_from_fork+0x22/0x40 [140594.217288] ---[ end trace 854f992547f30c28 ]--- [140594.217339] [ cut here ] [140594.217340] sysfs group 'power' not found for kobject 'i2c-11' [140594.217352] WARNING: CPU: 5 PID: 64631 at fs/sysfs/group.c:279 sysfs_remove_group+0x7c/0x80 [140594.217352] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc ccm rfcomm cmac algif_hash algif_skcipher af_alg cdc_ether usbnet r8152 mii snd_usb_audio snd_usbmidi_lib bnep bonding btusb btrtl btbcm btintel bluetooth ecdh_generic ecc evdi(OE) aufs uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common overlay nls_iso8859_1 snd_hda_codec_conexant snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd iwlmvm edac_mce_amd mac80211 kvm_amd ccp
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
Issue still remains with the mainline kernel. The contents of the kernel Oops message differs slightly, but still very similar: [ 27.532858] BUG: unable to handle kernel NULL pointer dereference at 03e8 [ 27.532862] #PF error: [WRITE] [ 27.532865] PGD 0 P4D 0 [ 27.532869] Oops: 0002 [#1] SMP NOPTI [ 27.532873] CPU: 3 PID: 82 Comm: kworker/3:1 Not tainted 5.1.0-050100rc3-generic #201904010618 [ 27.532875] Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 [ 27.532982] Workqueue: events dm_irq_work_func [amdgpu] [ 27.532989] RIP: 0010:queue_work_on+0x1b/0x40 [ 27.532992] Code: 75 01 01 e8 f9 13 fe ff 0f 0b e9 b5 fc ff ff 0f 1f 44 00 00 55 48 89 e5 53 9c 58 0f 1f 44 00 00 48 89 c3 fa 66 0f 1f 44 00 00 48 0f ba 2a 00 73 11 31 c9 48 89 df 57 9d 0f 1f 44 00 00 89 c8 [ 27.532994] RSP: 0018:c16bc1eebc88 EFLAGS: 00010002 [ 27.532996] RAX: 0202 RBX: 0202 RCX: 0001 [ 27.532998] RDX: 03e8 RSI: 9dde1e80d200 RDI: 2000 [ 27.533000] RBP: c16bc1eebc90 R08: 00027080 R09: b8210b0b [ 27.533002] R10: fc35106d5500 R11: 9dde1e86ca90 R12: 9dde0f2db646 [ 27.533003] R13: 9dde1b4b9a80 R14: 9dde195eb000 R15: [ 27.533006] FS: () GS:9dde1ecc() knlGS: [ 27.533008] CS: 0010 DS: ES: CR0: 80050033 [ 27.533010] CR2: 03e8 CR3: 000411ca6000 CR4: 003406a0 [ 27.533011] Call Trace: [ 27.533026] drm_dp_mst_handle_up_req+0x503/0x550 [drm_kms_helper] [ 27.533037] drm_dp_mst_hpd_irq+0xbe/0xaa0 [drm_kms_helper] [ 27.533045] ? drm_dp_mst_hpd_irq+0xbe/0xaa0 [drm_kms_helper] [ 27.533133] handle_hpd_rx_irq+0x22c/0x2e0 [amdgpu] [ 27.533219] ? handle_hpd_rx_irq+0x22c/0x2e0 [amdgpu] [ 27.533306] dm_irq_work_func+0x53/0x70 [amdgpu] [ 27.533309] process_one_work+0x20f/0x410 [ 27.533312] worker_thread+0x34/0x400 [ 27.533315] kthread+0x120/0x140 [ 27.533318] ? process_one_work+0x410/0x410 [ 27.533320] ? __kthread_parkme+0x70/0x70 [ 27.533325] ret_from_fork+0x22/0x40 [ 27.533327] Modules linked in: cmac bnep btusb btrtl btbcm btintel bluetooth ecdh_generic bonding uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media nfc edac_mce_amd kvm_amd ccp kvm arc4 irqbypass nls_iso8859_1 crct10dif_pclmul crc32_pclmul snd_hda_codec_conexant ghash_clmulni_intel snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_intel iwlmvm snd_seq_midi snd_seq_midi_event aes_x86_64 crypto_simd mac80211 cryptd snd_rawmidi glue_helper snd_seq iwlwifi snd_seq_device joydev snd_timer input_leds hp_wmi serio_raw sparse_keymap wmi_bmof snd k10temp cfg80211 soundcore ipmi_devintf ipmi_msghandler ucsi_acpi typec_ucsi typec hp_wireless mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 amdgpu chash gpu_sched amd_iommu_v2 i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme psmouse ahci drm libahci i2c_piix4 r8169 nvme_core realtek [ 27.533372] wmi i2c_hid hid video [ 27.533378] CR2: 03e8 [ 27.533380] ---[ end trace af80d2e3030b9f18 ]--- ** 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/1819924 Title: System hangs when hot-plugging dual monitor dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
I don't think this issue is related to LP #1820811. In #1820811, the hang always occurs when hot-plugging. With this issue, if the device is cold plugged (plugged in at boot), it can be disconencted and re-connected without issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820811] Re: Thunderbolt3 dock freezes X on hotplug when used with external displays
Sorry for the delayed followup, but if your machine is booted with it plugged in, are you then able to unplug and re-plug the device without issue? Or does the hang re-occur regardless of whether the device was plugged in at boot or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820811 Title: Thunderbolt3 dock freezes X on hotplug when used with external displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820811] Re: Thunderbolt3 dock freezes X on hotplug when used with external displays
We are trying to determine if this bug is related to bug #1819924. With the affected kernel versions, does the hang still occur if the dock is connected before booting? That is, with your computer shut off, plug in the dock and then boot up. Does the computer hang after booting? If not, are you then able to hot-plug (disconnect and re-connect) without issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820811 Title: Thunderbolt3 dock freezes X on hotplug when used with external displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
It's possible, though it's hard to confirm as I cannot find a kernel OOPS message in that ticket. If they can avoid hanging if the dock is plugged in when first booting, then I think they are very likely related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
I have verified this issue still exists in kernel version 4.18.0-10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819924] [NEW] System hangs when hot-plugging dual monitor dock
Public bug reported: When plugging in my Cable Matters USB-C Dual 4K DisplayPort Docking Station into my system, after it has already booted, the system hangs with a kernel OOPS. This is always repeatable. Steps to reproduce: 1. Ensure docking station is unplugged or shut-off. 2. Boot up computer. 3. Turn-on docking station and plug into to system. If the docking station is plugged in before the system boots, it works fine. It can even be unpluged and hot-plugged without issue at that point. This kernel Oops occurs when the system hangs: BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 SMP NOPTI CPU: 3 PID: 84 Comm: kworker/3:1 Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 Workqueue: events_long drm_dp_mst_link_probe_work [drm_kms_helper] RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 8e df ff ff 31 c0 65 48 8b 14 25 00 5c 01 00 48 0f b1 13 74 08 48 89 df e8 b4 ff ff ff 5b 5d c3 90 0f 1f 44 RSP: 0018:b6c0c1efbd78 EFLAGS: 00010246 RAX: RBX: 0320 RCX: 8ed7cfb5c800 RDX: 8ed7d383 RSI: 0202 RDI: 0320 RBP: b6c0c1efbd80 R08: 0201 R09: R10: R11: 8ed7df6e1ac8 R12: R13: 8ed7cfb5c468 R14: 8ed7d3b33f60 R15: FS: () GS:8ed7df6c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0320 CR3: 0003b5d6e000 CR4: 003406a0 Call Trace: drm_dp_mst_wait_tx_reply+0x155/0x1f0 [drm_kms_helper] ? wait_woken+0x80/0x80 drm_dp_send_enum_path_resources.isra.24+0x69/0xf0 [drm_kms_helper] drm_dp_check_and_send_link_address+0xa1/0xd0 [drm_kms_helper] drm_dp_mst_link_probe_work+0x4f/0x80 [drm_kms_helper] process_one_work+0x20f/0x410 worker_thread+0x34/0x400 kthread+0x120/0x140 ? pwq_unbound_release_workfn+0xd0/0xd0 ? kthread_bind+0x40/0x40 ret_from_fork+0x22/0x40 Modules linked in: snd_usb_audio snd_usbmidi_lib usbhid cdc_ether uas usbnet usb_storage r8152 rfcomm binfmt_misc ccm cmac bnep btusb btrtl btbcm btintel bluetooth ecdh_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media evdi(OE) nfc arc4 joydev nls_iso8859_1 snd_hda_codec_conexant snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep kvm_amd ccp kvm irqbypass snd_pcm crct10dif_pclmul iwlmvm crc32_pclmul ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event mac80211 snd_rawmidi snd_seq snd_seq_device snd_timer iwlwifi aesni_intel snd hp_wmi aes_x86_64 crypto_simd cryptd input_leds glue_helper wmi_bmof serio_raw sparse_keymap hid_multitouch k10temp soundcore cfg80211 ipmi_devintf ipmi_msghandler ucsi_acpi typec_ucsi typec mac_hid hp_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic amdkfd amd_iommu_v2 amdgpu chash gpu_sched i2c_algo_bit ttm nvme drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci libahci r8169 nvme_core i2c_piix4 mii i2c_hid wmi hid video CR2: 0320 ---[ end trace 3aa69f7fb354f0c1 ]--- BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 RIP: 0010:queue_work_on+0x1b/0x40 Code: SMP NOPTI CPU: 0 PID: 974 Comm: Xorg Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 58 66 66 2e 0f 01 01 e8 69 1f 84 00 27 fe ff 00 0f 0b e9 00 b5 fc ff 00 ff 0f 1f 00 44 00 00 0f 55 48 89 e5 1f 44 00 53 00 55 48 9c 89 e5 53 58 0f 1f 48 44 00 00 48 89 fb e8 89 c3 fa 8e 66 0f 1f df 44 00 00 ff 48 0f ba 2a ff 31 c0 00 65 48 8b 73 11 31 c9 14 25 00 48 89 df 57 5c 01 00 9d 0f 1f 44 00 00 89 48 0f b1 c8 RSP: 0018:b6c0c2063c98 EFLAGS: 00010002 13 RAX: 0202 RBX: 0202 RCX: 74 08 48 89 RDX: 03a8 RSI: 8ed7df019000 RDI: 2000 df e8 b4 RBP: b6c0c2063ca0 R08: 00027080 R09: a25d9e13 R10: fa628ed74840 R11: 0036 R12: 8ed7cfb5c5e6 R13: 8ed7801fa800 R14: 0001 R15: 8ed7d3b33f60 FS: () GS:8ed7df6c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0320 CR3: 0003b5d6e000 CR4: 003406a0 ff ff ff 5b 5d c3 90 0f 1f 44 RSP: 0018:b6c0c2b3b858 EFLAGS: 00010246 RAX: RBX: 0320 RCX: 8ed7cfb5c800 RDX: 8ed7da888000 RSI: 0206 RDI: 0320 RBP: b6c0c2b3b860 R08: 0206 R09: R10: R11: 8ed7df621ac8 R12: R13: 8ed7cfb5c468 R14: 8ed7d3b33f60 R15:
[Bug 1769266] [NEW] Unable to complete setup-ds-admin when running in Bionic LXC container
Public bug reported: Using a brand new Bionic 18.04LTS LXC container on a Bionic host, I am unable to complete running setup-ds-admin. When performing the exact same sequence on the physical host it completes as expected. When run as "setup-ds-admin -k -d" on the container, the run ends with this: --- Your new DS instance 'ds3891' was successfully created. Creating the configuration directory server . . . +Processing /usr/share/dirsrv/data/01nsroot.ldif.tmpl ... +Processing /usr/share/dirsrv/data/02globalpreferences.ldif.tmpl ... +Processing /usr/share/dirsrv/data/12dsconfig.mod.tmpl ... +Processing /usr/share/dirsrv/data/13dsschema.mod.tmpl ... +Processing /usr/share/dirsrv/data/14dsmonitor.mod.tmpl ... +Processing /usr/share/dirsrv/data/16dssuffixadmin.mod.tmpl ... Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.example.com:389/o=NetscapeRoot'. Error: Invalid credentials Could not register the directory server with the configuration directory server. Exiting . . . --- and the UserPassword entry for that user is a bogus string, unrelated to the password entered. By that I mean that I can run the same sequence four times with different passwords (cleaning up the /etc/dirsrv/slapd-* directories in between), and the same exact string will end up stored in the UserPassword entry for that user. The password for "cn=Directory Manager" is fine, however. The value of admin's UserPassword will always end up being this: userPassword:: e1NTSEE1MTJ9Y21SMUR1MER0Tk9FNWNZc1VlSTVXRHA1TlBSK2NQeGY1MlJPVTN GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz As noted, the same exact sequence run on the bare host (not in an LXC container) yields expected results. ** Affects: 389-admin (Ubuntu) Importance: Undecided Status: New ** Tags: bionic lxc ** Description changed: Using a brand new Bionic 18.04LTS LXC container on a Bionic host, I am unable to complete running setup-ds-admin. When performing the exact same sequence on the physical host it completes as expected. When run as "setup-ds-admin -k -d" on the container, the run ends with this: --- Your new DS instance 'ds3891' was successfully created. Creating the configuration directory server . . . +Processing /usr/share/dirsrv/data/01nsroot.ldif.tmpl ... +Processing /usr/share/dirsrv/data/02globalpreferences.ldif.tmpl ... +Processing /usr/share/dirsrv/data/12dsconfig.mod.tmpl ... +Processing /usr/share/dirsrv/data/13dsschema.mod.tmpl ... +Processing /usr/share/dirsrv/data/14dsmonitor.mod.tmpl ... +Processing /usr/share/dirsrv/data/16dssuffixadmin.mod.tmpl ... - Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.occinc.com:389/o=NetscapeRoot'. Error: Invalid credentials + Could not authenticate as user 'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot' to server 'ldap://ds3891.example.com:389/o=NetscapeRoot'. Error: Invalid credentials Could not register the directory server with the configuration directory server. Exiting . . . --- and the UserPassword entry for that user is a bogus string, unrelated to the password entered. By that I mean that I can run the same sequence four times with different passwords (cleaning up the /etc/dirsrv/slapd-* directories in between), and the same exact string will end up stored in the UserPassword entry for that user. The password for "cn=Directory Manager" is fine, however. The value of admin's UserPassword will always end up being this: userPassword:: e1NTSEE1MTJ9Y21SMUR1MER0Tk9FNWNZc1VlSTVXRHA1TlBSK2NQeGY1MlJPVTN - GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz + GZzFLQW1zTnlQZDRQOXdNNm1YTFJSZ1V0THp0d1ZnQWFyeFc1a2s2UVRMU2s0TDZTcm1xTXkrTmEz As noted, the same exact sequence run on the bare host (not in an LXC container) yields expected results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769266 Title: Unable to complete setup-ds-admin when running in Bionic LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-admin/+bug/1769266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340179] Re: Calibre E-book Viewer has no icon
@rolf: > Yes, it is indeed naive to think that explicitly opening new tickets in LP > for non-Ubuntu software is helpful. When and where did I do that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340179 Title: Calibre E-book Viewer has no icon To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1340179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340179] Re: Calibre E-book Viewer has no icon
@sup: > Michael - if you installed from the Calibre site, that is not a ubuntu bug, > sorry Yes, I know that, which is why I filed a bug upstream in the first place, and only linked to it from here. @r0lf: > Yeah, you really have to wonder sometimes what people are thinking (if they > are). "People" are probably thinking that a short comment noting that: a) the issue also exists when the upstream code is installed (therefore, whatever else is going on, it probably isn't a packaging issue per-se) b) that the issue also exists for other versions of the application and other versions of the OS (therefore, it probably isn't a regression per-se in either) c) and pointing to a detailed bug report (which may help with reproducing the issue) … would be seen as *helpful*, and that such comments wouldn't be immediately dismissed with a knee-jerk reaction as uninformed by someone who has obvious issues with reading comprehension, situational awareness, socialization. Upon reflection, I suppose it *is* rather foolish and naive of "people" to think any of that. Good day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340179 Title: Calibre E-book Viewer has no icon To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1340179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340179] Re: Calibre E-book Viewer has no icon
@jason-force, I am seeing the same issue in Ubuntu 15.04. As my Calibre is a binary install from the site rather than the distribution package, I've filed a bug here: https://bugs.launchpad.net/calibre/+bug/1660299 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340179 Title: Calibre E-book Viewer has no icon To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1340179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340179] Re: Calibre E-book Viewer has no icon
I currently have similar behavior to that described by @jason-force. I am currently on Ubuntu 15.04. As my Calibre is installed from the Calibre site rather than a package from the repository, I have filed a more complete bug report here: https://bugs.launchpad.net/calibre/+bug/1660299 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340179 Title: Calibre E-book Viewer has no icon To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1340179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632940] [NEW] sddm-greeter crashes on monitor disconnect
Public bug reported: When sddm is currently active (no users logged in on the desktop) and a monitor is disconnected, the screen of the remaining monitors suddenly go blank and the display manager is unusable until it is restarted. The only way to rectify this issue is to switch to a text console and manually restart the service through systemctl. Note that this appears to only affect sddm when it is started via systemd. When sddm is executed manually as root (via the command 'sudo sddm'), this issue cannot be repeated. Attached is the sddm logs. ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sddm log of when the issue occurs" https://bugs.launchpad.net/bugs/1632940/+attachment/4760140/+files/sddm.log ** Description changed: When sddm is currently active (no users logged in on the desktop) and a monitor is disconnected, the screen of the remaining monitors suddenly go blank and the display manager is unusable until it is restarted. The only way to rectify this issue is to switch to a text console and manually restart the service through systemctl. Note that this appears to only affect sddm when it is started via systemd. When sddm is executed manually as root (via the command 'sudo - sddm', this issue cannot be repeated. + sddm'), this issue cannot be repeated. Attached is the sddm logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632940 Title: sddm-greeter crashes on monitor disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1632940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
I'm getting the same issue with my logitech H800 headset. Here's a more verbose pulseaudio log of the device connecting and attempting to switch profiles: I: [pulseaudio] module-card-restore.c: Restored profile 'a2dp_sink' for card bluez_card.88_C6_26_31_DF_F0. I: [pulseaudio] module-card-restore.c: Restoring port latency offsets for card bluez_card.88_C6_26_31_DF_F0. I: [pulseaudio] card.c: Created 3 "bluez_card.88_C6_26_31_DF_F0" I: [pulseaudio] module-bluez5-device.c: Transport /org/bluez/hci0/dev_88_C6_26_31_DF_F0/fd2 acquired: fd 28 I: [pulseaudio] module-bluez5-device.c: SBC parameters: allocation=0, subbands=1, blocks=3, bitpool=53 I: [pulseaudio] sink.c: Created sink 1 "bluez_sink.88_C6_26_31_DF_F0" with sample spec s16le 2ch 44100Hz and channel map front-left,front-right I: [pulseaudio] sink.c: bluetooth.protocol = "a2dp_sink" I: [pulseaudio] sink.c: device.description = "H800 Logitech Headset" I: [pulseaudio] sink.c: device.string = "88:C6:26:31:DF:F0" I: [pulseaudio] sink.c: device.api = "bluez" I: [pulseaudio] sink.c: device.class = "sound" I: [pulseaudio] sink.c: device.bus = "bluetooth" I: [pulseaudio] sink.c: device.form_factor = "headset" I: [pulseaudio] sink.c: bluez.path = "/org/bluez/hci0/dev_88_C6_26_31_DF_F0" I: [pulseaudio] sink.c: bluez.class = "0x240404" I: [pulseaudio] sink.c: bluez.alias = "H800 Logitech Headset" I: [pulseaudio] sink.c: device.icon_name = "audio-headset-bluetooth" I: [pulseaudio] sink.c: device.intended_roles = "phone" I: [pulseaudio] source.c: Created source 2 "bluez_sink.88_C6_26_31_DF_F0.monitor" with sample spec s16le 2ch 44100Hz and channel map front-left,front-right I: [pulseaudio] source.c: device.description = "Monitor of H800 Logitech Headset" I: [pulseaudio] source.c: device.class = "monitor" I: [pulseaudio] source.c: device.string = "88:C6:26:31:DF:F0" I: [pulseaudio] source.c: device.api = "bluez" I: [pulseaudio] source.c: device.bus = "bluetooth" I: [pulseaudio] source.c: device.form_factor = "headset" I: [pulseaudio] source.c: bluez.path = "/org/bluez/hci0/dev_88_C6_26_31_DF_F0" I: [pulseaudio] source.c: bluez.class = "0x240404" I: [pulseaudio] source.c: bluez.alias = "H800 Logitech Headset" I: [pulseaudio] source.c: device.icon_name = "audio-headset-bluetooth" I: [pulseaudio] source.c: device.intended_roles = "phone" I: [bluetooth] core-util.c: Successfully enabled SCHED_RR scheduling for thread, with priority 5. I: [bluetooth] module-bluez5-device.c: Transport /org/bluez/hci0/dev_88_C6_26_31_DF_F0/fd2 resuming I: [pulseaudio] module.c: Loaded "module-bluez5-device" (index: #22; argument: "path=/org/bluez/hci0/dev_88_C6_26_31_DF_F0"). I: [pulseaudio] module-card-restore.c: Card bluez_card.88_C6_26_31_DF_F0 profile a2dp_sink became available, activating. I: [pulseaudio] module-suspend-on-idle.c: Sink bluez_sink.88_C6_26_31_DF_F0 idle for too long, suspending ... I: [bluetooth] bluez5-util.c: Transport /org/bluez/hci0/dev_88_C6_26_31_DF_F0/fd2 released I: [pulseaudio] module-card-restore.c: Card bluez_card.88_C6_26_31_DF_F0 profile a2dp_sink became available, activating. W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial
I'm seeing this same issue with Xenial and my logitech H800 headset. The profile A2DP is automatically selected and I am unable to specify HSP/HFP. As a result, I am unable to get the microphone through bluetooth. I have bluez 5.37-0ubuntu5 currently installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549163 Title: Bluetooth headset HSP/HFP mode not working in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425692] [NEW] unable to adjust kde panel after screen rotate
Public bug reported: After rotating a screen from the Display configuration control module, any KDE panels present on the rotated screen can no longer be adjusted or moved. After the screen is rotated, any attempts to open up the panel tool box fails. The panel tool box appears to flicker for an instant, but is immediately closed. It is impossible to adjust any settings from the panel tool box, including the panel height or screen edge. This issue appears to occur only to panels already existing on the rotated screen and limited only to the screen that undergone rotation. Any panel present on a screen that did not undergo rotation appears to be unaffected. Also, any panel created after the screen was rotated appears to be unaffected by this issue. Steps to reproduce: 1. Create a kde panel on the screen to be rotated (if one does not already exist). 2. Rotate screen via the Display Configuration control module. 3. Unlock widgets. 4. Attempt to open panel tool box on panel in rotated screen. I have tested this with both Kubuntu 14.04 and Kubuntu 14.10 (Plasma 4 version). Both releases appear to be affected by this. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425692 Title: unable to adjust kde panel after screen rotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1425692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418175] [NEW] nut-server packaging incorrectly assumes host will be client, too
Public bug reported: The packaging for nut-server assumes that host will also be a client, which is an invalid assumption. As is stated a href=http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#DataRoom;on the nut website/a: quoteFinally, there’s a special case. Type A systems are connected to a UPS’s serial port, but don’t depend on it for power. This usually happens when a UPS is physically close to a box and can reach the serial port, but the wiring is such that it doesn’t actually feed it./quote There is no good reason for nut=server to depend upon nut-client. Furthermore, /etc/init.d/nut, in the start-stop-client() function should not include netserver in the case $MODE... statement, or else a different mode should be introduced which starts only the driver and upsd components, as is described in the documentation. It is a potentially dangerous and critical assumption that a nut host will always be powered by, or only be powered by, a ups which it is also monitoring. The software supports much greater freedom than this, and the packaging should reflect this. This is specifically in reference to the Precise (12.04.2 LTS) packaging of nut-2.6.3-1ubuntu1.1, but the same dependency is observed to exist in nut-2.7.1-1ubuntu1 for Trusty (14.04.1 LTS). ** Affects: nut (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/1418175 Title: nut-server packaging incorrectly assumes host will be client, too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1418175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418175] [NEW] nut-server packaging incorrectly assumes host will be client, too
Public bug reported: The packaging for nut-server assumes that host will also be a client, which is an invalid assumption. As is stated a href=http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#DataRoom;on the nut website/a: quoteFinally, there’s a special case. Type A systems are connected to a UPS’s serial port, but don’t depend on it for power. This usually happens when a UPS is physically close to a box and can reach the serial port, but the wiring is such that it doesn’t actually feed it./quote There is no good reason for nut=server to depend upon nut-client. Furthermore, /etc/init.d/nut, in the start-stop-client() function should not include netserver in the case $MODE... statement, or else a different mode should be introduced which starts only the driver and upsd components, as is described in the documentation. It is a potentially dangerous and critical assumption that a nut host will always be powered by, or only be powered by, a ups which it is also monitoring. The software supports much greater freedom than this, and the packaging should reflect this. This is specifically in reference to the Precise (12.04.2 LTS) packaging of nut-2.6.3-1ubuntu1.1, but the same dependency is observed to exist in nut-2.7.1-1ubuntu1 for Trusty (14.04.1 LTS). ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1418175 Title: nut-server packaging incorrectly assumes host will be client, too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1418175/+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 1318828] [NEW] Crash during installation of mythbuntu 14.04
Public bug reported: Crash during installation ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 Date: Mon May 12 16:48:11 2014 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/mythbuntu.seed boot=casper only-ubiquity quiet splash -- LiveMediaBuild: Mythbuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mythbuntu trusty ubiquity-2.18.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318828 Title: Crash during installation of mythbuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1318828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318828] Re: Crash during installation of mythbuntu 14.04
*** This bug is a duplicate of bug 1309553 *** https://bugs.launchpad.net/bugs/1309553 Removed duplicate of bug 1309533 as that has to do with Can't edit factoids that are aliases to nonexisting factoids in IRC, which has nothing to with installing MythBuntu. ** This bug is no longer a duplicate of bug 1309553 Mythbuntu Installer Crash enabling VNC ** This bug has been marked a duplicate of bug 1318817 Error preventing new install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318828 Title: Crash during installation of mythbuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1318828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318817] Re: Error preventing new install
*** This bug is a duplicate of bug 1309553 *** https://bugs.launchpad.net/bugs/1309553 Removed duplicate of bug 1309533 as that has to do with Can't edit factoids that are aliases to nonexisting factoids in IRC, which has nothing to with installing MythBuntu. ** This bug is no longer a duplicate of bug 1309533 Can't edit factoids that are aliases to nonexisting factoids -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318817 Title: Error preventing new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1318817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219512] [NEW] Setting ListenAddress to dynamic (e.g. dhclient determined) ip deadlocks boot
Public bug reported: 1. Install Ubuntu Server 2. Install openssh-server 3. Set your router (or OTHER dhcp-server) to assign a fixed ip to your server installation 4. Change ListenAddress to that fixed ip 5. Server never finishes booting. no remote (ssh) login possible. sometimes not even pingable. --- sshd trying to bind to an ip even when no network link is availble is one thing, but it certainly should not end in a deadlock during boot... auth.log Sep 1 04:05:34 server sshd[1072]: error: Bind to port 28282 on 192.168.1.2 failed: Cannot assign requested address. Sep 1 04:05:34 server sshd[1072]: fatal: Cannot bind any address. kern.log Sep 1 04:05:37 server kernel: [ 28.662038] r8169 :04:00.0 p2p1: link up Sep 1 04:05:37 server kernel: [ 28.662048] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1: link becomes ready sshd_config: -- Port 12345 ListenAddress 192.168.1.2 AllowUsers bernstein PrintMotd no AcceptEnv LANG LC_* Subsystem sftp /usr/lib/openssh/sftp-server UsePAM yes LogLevel VERBOSE PermitRootLogin no UsePrivilegeSeparation sandbox PasswordAuthentication no ChallengeResponseAuthentication no ClientAliveInterval 240 LoginGraceTime 20 MaxStartups 1:100:1 Banner /etc/issue.net System information --- ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openssh-server 1:6.1p1-4 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 19:46:10 2013 MarkForUpload: True SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Description changed: 1. Install Ubuntu Server 2. Install openssh-server 3. Set your router (or OTHER dhcp-server) to assign a fixed ip to your server installation 4. Change ListenAddress to that fixed ip 5. Server never finishes booting. no remote (ssh) login possible. sometimes not even pingable. - --- sshd trying to bind to an ip even when the network no network link - is availble is one thing... but it certainly should not end in a - deadlock during boot... + --- sshd trying to bind to an ip even when no network link is availble + is one thing, but it certainly should not end in a deadlock during + boot... auth.log Sep 1 04:05:34 server sshd[1072]: error: Bind to port 28282 on 192.168.1.2 failed: Cannot assign requested address. Sep 1 04:05:34 server sshd[1072]: fatal: Cannot bind any address. kern.log Sep 1 04:05:37 server kernel: [ 28.662038] r8169 :04:00.0 p2p1: link up Sep 1 04:05:37 server kernel: [ 28.662048] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1: link becomes ready sshd_config: -- Port 12345 ListenAddress 192.168.1.2 AllowUsers bernstein PrintMotd no AcceptEnv LANG LC_* Subsystem sftp /usr/lib/openssh/sftp-server UsePAM yes LogLevel VERBOSE PermitRootLogin no UsePrivilegeSeparation sandbox PasswordAuthentication no ChallengeResponseAuthentication no ClientAliveInterval 240 LoginGraceTime 20 MaxStartups 1:100:1 Banner /etc/issue.net + System information + --- ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openssh-server 1:6.1p1-4 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 19:46:10 2013 MarkForUpload: True SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1219512 Title: Setting ListenAddress to dynamic (e.g. dhclient determined) ip deadlocks boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1219512/+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 1219512] Re: Setting ListenAddress to dhcp-client determined ip deadlocks boot
** Summary changed: - Setting ListenAddress to dynamic (e.g. dhclient determined) ip deadlocks boot + Setting ListenAddress to dhcp-client determined ip deadlocks boot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1219512 Title: Setting ListenAddress to dhcp-client determined ip deadlocks boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1219512/+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 1219512] [NEW] Setting ListenAddress to dynamic (e.g. dhclient determined) ip deadlocks boot
Public bug reported: 1. Install Ubuntu Server 2. Install openssh-server 3. Set your router (or OTHER dhcp-server) to assign a fixed ip to your server installation 4. Change ListenAddress to that fixed ip 5. Server never finishes booting. no remote (ssh) login possible. sometimes not even pingable. --- sshd trying to bind to an ip even when no network link is availble is one thing, but it certainly should not end in a deadlock during boot... auth.log Sep 1 04:05:34 server sshd[1072]: error: Bind to port 28282 on 192.168.1.2 failed: Cannot assign requested address. Sep 1 04:05:34 server sshd[1072]: fatal: Cannot bind any address. kern.log Sep 1 04:05:37 server kernel: [ 28.662038] r8169 :04:00.0 p2p1: link up Sep 1 04:05:37 server kernel: [ 28.662048] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1: link becomes ready sshd_config: -- Port 12345 ListenAddress 192.168.1.2 AllowUsers bernstein PrintMotd no AcceptEnv LANG LC_* Subsystem sftp /usr/lib/openssh/sftp-server UsePAM yes LogLevel VERBOSE PermitRootLogin no UsePrivilegeSeparation sandbox PasswordAuthentication no ChallengeResponseAuthentication no ClientAliveInterval 240 LoginGraceTime 20 MaxStartups 1:100:1 Banner /etc/issue.net System information --- ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openssh-server 1:6.1p1-4 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 19:46:10 2013 MarkForUpload: True SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Description changed: 1. Install Ubuntu Server 2. Install openssh-server 3. Set your router (or OTHER dhcp-server) to assign a fixed ip to your server installation 4. Change ListenAddress to that fixed ip 5. Server never finishes booting. no remote (ssh) login possible. sometimes not even pingable. - --- sshd trying to bind to an ip even when the network no network link - is availble is one thing... but it certainly should not end in a - deadlock during boot... + --- sshd trying to bind to an ip even when no network link is availble + is one thing, but it certainly should not end in a deadlock during + boot... auth.log Sep 1 04:05:34 server sshd[1072]: error: Bind to port 28282 on 192.168.1.2 failed: Cannot assign requested address. Sep 1 04:05:34 server sshd[1072]: fatal: Cannot bind any address. kern.log Sep 1 04:05:37 server kernel: [ 28.662038] r8169 :04:00.0 p2p1: link up Sep 1 04:05:37 server kernel: [ 28.662048] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1: link becomes ready sshd_config: -- Port 12345 ListenAddress 192.168.1.2 AllowUsers bernstein PrintMotd no AcceptEnv LANG LC_* Subsystem sftp /usr/lib/openssh/sftp-server UsePAM yes LogLevel VERBOSE PermitRootLogin no UsePrivilegeSeparation sandbox PasswordAuthentication no ChallengeResponseAuthentication no ClientAliveInterval 240 LoginGraceTime 20 MaxStartups 1:100:1 Banner /etc/issue.net + System information + --- ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openssh-server 1:6.1p1-4 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 19:46:10 2013 MarkForUpload: True SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: upstart (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/1219512 Title: Setting ListenAddress to dynamic (e.g. dhclient determined) ip deadlocks boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1219512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219512] Re: Setting ListenAddress to dhcp-client determined ip deadlocks boot
** Summary changed: - Setting ListenAddress to dynamic (e.g. dhclient determined) ip deadlocks boot + Setting ListenAddress to dhcp-client determined ip deadlocks boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219512 Title: Setting ListenAddress to dhcp-client determined ip deadlocks boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1219512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951000] Re: disable guest session screen lock using gsettings
This bug still affects me with Ubuntu 13.04 and lightdm version 1.6.0-0ubuntu3 with KDE as the desktop environment. Is this fix gnome specific? Is it possible to fix this issue for both desktop environments? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192319] [NEW] snmpd init script uses start-stop-daemon without pidfile argument
Public bug reported:
The snmpd.init file in Precise, Quantal, Raring and Saucy invokes start-
stop-daemon without the --pidfile argument. This causes all instances
of snmpd to die when used on an LXC parent host, for example.
From the man page for start-stop-daemon:
Note: unless --pidfile is specified, start-stop-daemon behaves similar
to killall(1). start-stop-daemon will scan the process table looking
for any processes which match the process name, uid, and/or gid (if
specified). Any matching process will prevent --start from starting the
daemon. All matching processes will be sent the TERM signal (or the one
specified via --signal or --retry) if --stop is specified. For daemons
which have long-lived children which need to live through a --stop, you
must specify a pidfile.
In an LXC environment, all the container processes appear in the parent
host's process table, thus service snmpd {restart|stop} will kill all
running snmpd instances, even those in child containers.
In Precise, Quantal and Raring (5.4.3~dfsg-...), this is typical of how the
process is stopped:
start-stop-daemon --quiet --stop --oknodo --exec /usr/sbin/snmpd
In saucy (5.7.2~dfsg-4ubuntu1) this is typical of how the process is stopped:
start-stop-daemon --quiet --stop --oknodo --exec /usr/sbin/snmpd [ ! -f
$SNMP_PID ] || rm $SNMP_PID
In all cases, --pidfile should be used to constrain the action of start-
stop-daemon.
Observed empirically in snmpd-5.4.3~dfsg-2.4ubuntu1.1, observed in
source packages for 5.4.3~dfsg-2.7ubuntu and 5.7.2~dfsg-4ubuntu1 on
launchpad.
** Affects: net-snmp (Ubuntu)
Importance: Undecided
Status: New
** Tags: init.d snmpd start-stop-daemon
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1192319
Title:
snmpd init script uses start-stop-daemon without pidfile argument
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1192319/+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 1192319] [NEW] snmpd init script uses start-stop-daemon without pidfile argument
Public bug reported:
The snmpd.init file in Precise, Quantal, Raring and Saucy invokes start-
stop-daemon without the --pidfile argument. This causes all instances
of snmpd to die when used on an LXC parent host, for example.
From the man page for start-stop-daemon:
Note: unless --pidfile is specified, start-stop-daemon behaves similar
to killall(1). start-stop-daemon will scan the process table looking
for any processes which match the process name, uid, and/or gid (if
specified). Any matching process will prevent --start from starting the
daemon. All matching processes will be sent the TERM signal (or the one
specified via --signal or --retry) if --stop is specified. For daemons
which have long-lived children which need to live through a --stop, you
must specify a pidfile.
In an LXC environment, all the container processes appear in the parent
host's process table, thus service snmpd {restart|stop} will kill all
running snmpd instances, even those in child containers.
In Precise, Quantal and Raring (5.4.3~dfsg-...), this is typical of how the
process is stopped:
start-stop-daemon --quiet --stop --oknodo --exec /usr/sbin/snmpd
In saucy (5.7.2~dfsg-4ubuntu1) this is typical of how the process is stopped:
start-stop-daemon --quiet --stop --oknodo --exec /usr/sbin/snmpd [ ! -f
$SNMP_PID ] || rm $SNMP_PID
In all cases, --pidfile should be used to constrain the action of start-
stop-daemon.
Observed empirically in snmpd-5.4.3~dfsg-2.4ubuntu1.1, observed in
source packages for 5.4.3~dfsg-2.7ubuntu and 5.7.2~dfsg-4ubuntu1 on
launchpad.
** Affects: net-snmp (Ubuntu)
Importance: Undecided
Status: New
** Tags: init.d snmpd start-stop-daemon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192319
Title:
snmpd init script uses start-stop-daemon without pidfile argument
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1192319/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965895] Re: After boot, NetworkManager indicator menu only shows four entries
Just experienced this issue for the first time on an up to date 12.04 (32-bit OS, AMD Phenom(tm) II X4 955 Processor × 4, Realtek RTL8111/8168B PCI Express Gigabit Ethernet Controller), so it looks like the latest update is actually *causing* the issue for me. Killing/restarting the nm-applet works around the issue, but it returns after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965895 Title: After boot, NetworkManager indicator menu only shows four entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/965895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011005] Re: MMC/SD memory card reader stops working after hibernate and resume
Just tested with version 3.5-rc4 found in the kernel mainline ppa. Now the MMC card reader fails to work at all. The stack trace occurs when a memory card is inserted after a fresh boot into the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011005 Title: MMC/SD memory card reader stops working after hibernate and resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011005] Re: MMC/SD memory card reader stops working after hibernate and resume
I tried installing that linux kernel and I came across some odd dependency issues. It appears that linux-headers-generic_3.4.0.5.6 depends on linux-headers-3.4.0-5-generic and linux-image- generic_3.4.0.5.6 depends on linux-image-3.4.0-5-generic. Is this expected? I never before installed kernel packages that depended on a different version. The same thing appears to occur for the 3.4.0.5.7 versions. I did happen to find kernel version 3.4.0 on the kernel ppa that I was able to install. I'll test with that shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011005 Title: MMC/SD memory card reader stops working after hibernate and resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011005] Re: MMC/SD memory card reader stops working after hibernate and resume
This issue still occurs on version 3.4.0 found in the kernel ppa (3.4-precise). ** Tags added: apport-collected precise ** Description changed: On a fresh boot, the MMC/SD memory card reader on my laptop works fine. However, if I hibernate and resume my laptop and attempt to use the MMC/SD memory again, the laptop fails to read the memory card and I receive a kernel trace from the driver. The kernel trace is as follows: [208991.375755] irq 21: nobody cared (try booting with the irqpoll option) [208991.375761] Pid: 0, comm: swapper/1 Tainted: GW 3.3.4-030304-generic #201205011755 [208991.375764] Call Trace: [208991.375774] [c10b38a9] __report_bad_irq+0x29/0xd0 [208991.375780] [c1572bff] ? _raw_spin_lock_irqsave+0x2f/0x50 [208991.375784] [c10b3a63] note_interrupt+0x113/0x1c0 [208991.375788] [c10b17f9] handle_irq_event_percpu+0xa9/0x1e0 [208991.375793] [c10279b8] ? default_spin_lock_flags+0x8/0x10 [208991.375797] [c10b196b] handle_irq_event+0x3b/0x60 [208991.375800] [c10b4010] ? handle_percpu_irq+0x50/0x50 [208991.375804] [c10b405e] handle_fasteoi_irq+0x4e/0xe0 [208991.375806] IRQ [c157a272] ? do_IRQ+0x42/0xc0 [208991.375815] [c1065ad2] ? sched_clock_local+0xb2/0x190 [208991.375819] [c157a1b0] ? common_interrupt+0x30/0x38 [208991.375823] [c106007b] ? find_process_by_pid+0x2b/0x30 [208991.375828] [c131e643] ? acpi_idle_enter_simple+0xef/0x12a [208991.375834] [c1458d2b] ? cpuidle_idle_call+0xab/0x1d0 [208991.375838] [c10020b4] ? cpu_idle+0xa4/0xf0 [208991.375841] [c156c271] ? start_secondary+0xf1/0xf7 [208991.375844] handlers: [208991.375848] [c13eaba0] usb_hcd_irq [208991.375866] [f83b9710] sdhci_irq [208991.375871] [f8881780] r592_irq [208991.375875] [f8a5c6b0] r852_irq [208991.375877] Disabling IRQ #21 [208998.208046] mmc0: Timeout waiting for hardware interrupt. [209008.224025] mmc0: Timeout waiting for hardware interrupt. + --- + ApportVersion: 2.0.1-0ubuntu7 + Architecture: i386 + Dependencies: + linux-firmware 1.79 + linux-generic 3.4.0.5.6 + linux-headers-generic 3.4.0.5.7 + linux-image-generic 3.4.0.5.7 + DistroRelease: Ubuntu 12.04 + InstallationMedia: Kubuntu 10.10 Maverick Meerkat - Release i386 (20101007) + Package: linux 3.4.0.5.6 + PackageArchitecture: i386 + ProcEnviron: + LANGUAGE= + TERM=xterm + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: precise + Uname: Linux 3.4.0-030400-generic i686 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: Upgraded to precise on 2012-04-29 (48 days ago) + UserGroups: admin cdrom dialout lpadmin netdev plugdev sambashare -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011005 Title: MMC/SD memory card reader stops working after hibernate and resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011005] [NEW] MMC/SD memory card reader stops working after hibernate and resume
Public bug reported: On a fresh boot, the MMC/SD memory card reader on my laptop works fine. However, if I hibernate and resume my laptop and attempt to use the MMC/SD memory again, the laptop fails to read the memory card and I receive a kernel trace from the driver. The kernel trace is as follows: [208991.375755] irq 21: nobody cared (try booting with the irqpoll option) [208991.375761] Pid: 0, comm: swapper/1 Tainted: GW 3.3.4-030304-generic #201205011755 [208991.375764] Call Trace: [208991.375774] [c10b38a9] __report_bad_irq+0x29/0xd0 [208991.375780] [c1572bff] ? _raw_spin_lock_irqsave+0x2f/0x50 [208991.375784] [c10b3a63] note_interrupt+0x113/0x1c0 [208991.375788] [c10b17f9] handle_irq_event_percpu+0xa9/0x1e0 [208991.375793] [c10279b8] ? default_spin_lock_flags+0x8/0x10 [208991.375797] [c10b196b] handle_irq_event+0x3b/0x60 [208991.375800] [c10b4010] ? handle_percpu_irq+0x50/0x50 [208991.375804] [c10b405e] handle_fasteoi_irq+0x4e/0xe0 [208991.375806] IRQ [c157a272] ? do_IRQ+0x42/0xc0 [208991.375815] [c1065ad2] ? sched_clock_local+0xb2/0x190 [208991.375819] [c157a1b0] ? common_interrupt+0x30/0x38 [208991.375823] [c106007b] ? find_process_by_pid+0x2b/0x30 [208991.375828] [c131e643] ? acpi_idle_enter_simple+0xef/0x12a [208991.375834] [c1458d2b] ? cpuidle_idle_call+0xab/0x1d0 [208991.375838] [c10020b4] ? cpu_idle+0xa4/0xf0 [208991.375841] [c156c271] ? start_secondary+0xf1/0xf7 [208991.375844] handlers: [208991.375848] [c13eaba0] usb_hcd_irq [208991.375866] [f83b9710] sdhci_irq [208991.375871] [f8881780] r592_irq [208991.375875] [f8a5c6b0] r852_irq [208991.375877] Disabling IRQ #21 [208998.208046] mmc0: Timeout waiting for hardware interrupt. [209008.224025] mmc0: Timeout waiting for hardware interrupt. ** Affects: linux-meta (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/1011005 Title: MMC/SD memory card reader stops working after hibernate and resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1011005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011005] Re: MMC/SD memory card reader stops working after hibernate and resume
After attempting to collect info with apport-collect, I realized that I had upgraded the kernel to 3.3.4 to solve an unrelated issue. I have just tested the default kernel included with the 12.04 release (3.2.0-24) and this issue does not affect the kernel installed by default. As per the suggestion provided by apport-collect, I have submitted this issue upstream to bugzilla.kernel.org. The upstream issue is bug #43361. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011005 Title: MMC/SD memory card reader stops working after hibernate and resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987965] Re: notifier 'Failure to download extra data' every kubuntu 12.04 restart
I tried the suggested fix above, installing libgtk2-perl and then reinstalling flashplugin-installer. However, I still receive this error message on occasion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987965 Title: notifier 'Failure to download extra data' every kubuntu 12.04 restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/987965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989150] [NEW] kmix crashes whenever usb sound device is inserted/removed
Public bug reported: Kmix crashes every time I insert or remove a usb sound device (usb headset). Kmix version: 4:4.8.2-0ubuntu1 on Kubuntu 12.04 Here is the following stack trace from the crash report: Application: KMix (kmix), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fb1857c0780 (LWP 7635))] Thread 3 (Thread 0x7fb16642f700 (LWP 7636)): #0 0x7fb185084b03 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fb17ae90ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb17ae91124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb181e0b426 in QEventDispatcherGlib::processEvents (this=0x7fb168c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fb181ddac82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fb181ddaed7 in QEventLoop::exec (this=0x7fb16642edd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fb181cd9fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fb181dba9ff in QInotifyFileSystemWatcherEngine::run (this=0x1fe8910) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fb181cdcfcb in QThreadPrivate::start (arg=0x1fe8910) at thread/qthread_unix.cpp:298 #9 0x7fb17b9f7e9a in start_thread (arg=0x7fb16642f700) at pthread_create.c:308 #10 0x7fb1850904bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7fb165a22700 (LWP 7637)): #0 0x7fb1850830bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fb17aecb88f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb17ae90abd in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb17ae90f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb17ae91124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb181e0b426 in QEventDispatcherGlib::processEvents (this=0x7fb1540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7fb181ddac82 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fb181ddaed7 in QEventLoop::exec (this=0x7fb165a21dd0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fb181cd9fa7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7fb181dba9ff in QInotifyFileSystemWatcherEngine::run (this=0x20b01d0) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7fb181cdcfcb in QThreadPrivate::start (arg=0x20b01d0) at thread/qthread_unix.cpp:298 #11 0x7fb17b9f7e9a in start_thread (arg=0x7fb165a22700) at pthread_create.c:308 #12 0x7fb1850904bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 1 (Thread 0x7fb1857c0780 (LWP 7635)): [KCrash Handler] #6 0x02066db0 in ?? () #7 0x7fb1853b0e26 in MDWSlider::update (this=0x2099e20) at ../../kmix/gui/mdwslider.cpp:1001 #8 0x7fb1853ac64b in ViewDockAreaPopup::refreshVolumeLevels (this=optimized out) at ../../kmix/gui/viewdockareapopup.cpp:168 #9 0x7fb181df0281 in QMetaObject::activate (sender=0x2018110, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #10 0x7fb181df0281 in QMetaObject::activate (sender=0x2023430, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #11 0x7fb185385b0c in Mixer_Backend::readSetFromHW (this=0x2023430) at ../../kmix/backends/mixer_backend.cpp:155 #12 0x7fb185395df5 in sink_cb (c=optimized out, i=optimized out, eol=optimized out) at ../../kmix/backends/mixer_pulse.cpp:191 #13 0x7fb18376d944 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #14 0x7fb17b3af693 in ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so #15 0x7fb17b3afa03 in pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so #16 0x7fb183763bdd in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #17 0x7fb17b3b42a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so #18 0x7fb183551ab3 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0 #19 0x7fb17ae90c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fb17ae91060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fb17ae91124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fb181e0b3bf in QEventDispatcherGlib::processEvents (this=0x1c51ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #23 0x7fb182af5d6e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #24 0x7fb181ddac82 in QEventLoop::processEvents (this=optimized out, flags=...) at
[Bug 883222] Re: soprano-virtuoso.log eats up hard disk space
I am having particular trouble with this bug for a number of reasons: 1-- I have attempted to disable this service in 3 different ways, and yet this bug still keeps popping up on me-- I've tried disabling the nepomuk search module from the kde services config module, then tried disabling indexing from the nepomuk file indexing controller, and finally disabling from the desktop search config module. Despite all this, nepomuk still starts up and kills all of my hard disk space. 2-- I have encrypted home directories enabled on my system, and after this issue occurs, my system becomes completely unusable. Not only can I not login from the X console, but my text console gets completely swamped with ecryptfs kernel messages, making them unusable. This has become far more than just a mere annoyance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883222 Title: soprano-virtuoso.log eats up hard disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtuoso-opensource/+bug/883222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883222] [NEW] soprano-virtuoso.log eats up hard disk space
Public bug reported: After noticing my home directory partition had suddenly filled up, I eventually discovered the culprit: ~/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.log had grown to a rather large 125GB. The contents of this file consisted essentially of 1 line repeated over and over (and over. . .): 14:01:16 Reference to page with free remap dp = 1490, remap = 1490 I had to remove the log file and kill the virtuoso-t process that was writing it. ** Affects: virtuoso-opensource (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/883222 Title: soprano-virtuoso.log eats up hard disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtuoso-opensource/+bug/883222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720982] [NEW] kopete skype plugin crashes on chat window close
Public bug reported: Binary package hint: kopete If a skype chat window within kopete is closed while the kopete main window is hidden (i.e. minimized to tray icon), either the skype plugin or the skype application crashes. This leaves kopete in a weird state where it can no longer be restored by the tray icon. This can only be rectified by clicking on the kopete shortcut from the applications menu, clicking on file/quit, and then restarting the kopete application. This does not appear to happen when the main kopete window is on the desktop, it only appears to happen when the main kopete window is closed but still accessible by the tray icon. Steps to reproduce: 1. start kopete with a skype account 2. select a skype user to bring up a chat window 3. close main skype window (leave running in background) 4. close chat window 5. notice that the skype application is gone and the main skype window can not be restored by the tray icon ** Affects: kopete (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kopete in ubuntu. https://bugs.launchpad.net/bugs/720982 Title: kopete skype plugin crashes on chat window close -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 682839] [NEW] OpenOffice Writer crashes when attempting to save document with table of contents as a doc file
Public bug reported: Binary package hint: openoffice.org When attempting to save a document with a particular table of contents as a Word .doc file, the application immediately crashes and prompts to recover upon restarting the application. It should be noted that the file was originally a Word .doc file which was imported to .odt format upon opening. The crash did not occur until saving back out to a .doc format file. It is believed that the issue is caused by the table of contents in the file. In the original file, when the table of contents was removed, the crash did not occur. The provided file is an empty table of contents (all other elements from the original file were removed) in which the crash still occurs. This is happening in OpenOffice 3.2 ooo-build 3.2.0.10, Debian 1:3.2.0-7ubuntu4.1 ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New -- OpenOffice Writer crashes when attempting to save document with table of contents as a doc file https://bugs.launchpad.net/bugs/682839 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682839] Re: OpenOffice Writer crashes when attempting to save document with table of contents as a doc file
** Attachment added: badtoc.odt https://bugs.launchpad.net/bugs/682839/+attachment/1749119/+files/badtoc.odt -- OpenOffice Writer crashes when attempting to save document with table of contents as a doc file https://bugs.launchpad.net/bugs/682839 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440179] Re: service fails to start/stop/restart networking daemon
Seeing the same as Simone F. in #5 (note: /etc/init.d/networking start does work) Seeing output of initctl list | grep network as Jon Watte (#9) ... but not the other things (e.g. ifup workin as expected. nothing in /var/log/boot) meanwhile starting/stopping each interface manually as follows works too : sudo service network-interface stop INTERFACE=lo so i guess using the service command invokes another (broken) script than /etc/init.d/networking which works fine. this really shouldn't happen on a lts release -- service fails to start/stop/restart networking daemon https://bugs.launchpad.net/bugs/440179 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580043] [NEW] Failure to save links in Office Open XML format
Public bug reported: Binary package hint: openoffice.org When adding a linked graphic to a document and saving the document as an Office Open XML file format (MS Office 2007 or later), the link reference is not added to the document. When reopening the document in the same OpenOffice instance, the document opens fine, however when opening the document on another computer or in a new instance of OpenOffice, the graphic is broken as it is missing the link. Steps to reproduce: 1. Create new document (tested with both writer and calc documents) 2. Insert Picture From File 3. Choose a picture, check the link check box, and select open 4. Confirm graphic link was inserted by viewing Edit Links 5. Save Document as Microsoft Word/Excel 2007 XML 6. Close OpenOffice 7. Open the Word/Excel 2007 XML file 8. Notice that the graphic now says Read Error-- Edit Links is now ghosted ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New -- Failure to save links in Office Open XML format https://bugs.launchpad.net/bugs/580043 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347838] Re: [LENOVO INVALID] suspend/resume failure
This issue is still occurring for me with the latest ubuntu release, 10.04. -- [LENOVO INVALID] suspend/resume failure https://bugs.launchpad.net/bugs/347838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423725] Re: migrate crashed with ImportError in get_provider()
This bug was already fixed by Debian (bug 549488) in version 0.5.4-2 and above. 0.5.4-3 is already slated to be included into Lucid. Can we get 0.5.4-3 included as an update to Karmic as well? ** Bug watch added: Debian Bug tracker #549488 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549488 -- migrate crashed with ImportError in get_provider() https://bugs.launchpad.net/bugs/423725 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423725] Re: migrate crashed with ImportError in get_provider()
Oops, that bug was for debian's bug tracker, full url: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549488 -- migrate crashed with ImportError in get_provider() https://bugs.launchpad.net/bugs/423725 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556851] [NEW] okular mucks up forms on pdf's in landscape orientation
Public bug reported: Binary package hint: okular When filling in a pdf form into a pdf which is oriented in landscape mode, okular fails to properly display the data of that form. All form data entered into the pdf form is rotated 90 degrees as okular apparently fails to take the orientation of the document into account. When saving with this form data, the pdf file additionally gets corrupted as attempting to open the same file in acrobat reader either results in an error message or the document with the form data absent. ** Affects: okular (Ubuntu) Importance: Undecided Status: New -- okular mucks up forms on pdf's in landscape orientation https://bugs.launchpad.net/bugs/556851 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556851] Re: okular mucks up forms on pdf's in landscape orientation
** Attachment added: Sample of document in landscape oriantation with form http://launchpadlibrarian.net/43297718/landscapetest.pdf -- okular mucks up forms on pdf's in landscape orientation https://bugs.launchpad.net/bugs/556851 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347838] Re: [LENOVO INVALID] suspend/resume failure
This is still happening for me on my laptop with 9.10. I have not yet tested with the oncoming 10.04 though. ** Changed in: linux (Ubuntu) Status: Incomplete = New -- [LENOVO INVALID] suspend/resume failure https://bugs.launchpad.net/bugs/347838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 202039] Re: Booting from USB fails on MacBook Pro 3,1
Although the instructions above do make ubuntu bootable, they don't work with gpu acceleration (e.g. any driver except fbdev)... So the issue still persists on my MacBookPro 3,1 -- Booting from USB fails on MacBook Pro 3,1 https://bugs.launchpad.net/bugs/202039 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 512240] Re: OpenOffice Base (3.1.1 Ubuntu 9.10) hangs while connecting to MySQL tables (ODBC)
I see the same problem connecting to a MS SQL ODBC connection. Can't even do a simple 'SELECT * FROM TABLENAME' without Base hanging indefinitely. I double checked that the same query (and the same ODBC conection) works fine from sqsh and isql. -- OpenOffice Base (3.1.1 Ubuntu 9.10) hangs while connecting to MySQL tables (ODBC) https://bugs.launchpad.net/bugs/512240 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184440] Re: [nvidia] Blue hue in all videos
*** This bug is a duplicate of bug 395476 *** https://bugs.launchpad.net/bugs/395476 i am having a similar problem as everyone else except the blue hue is on my back round and all videos like youtube and such.. her is a video overlay hope you can tell whats wrong by looking at it...im new to ubuntu so any instructions you give make sure they are detailed thannnkkksss... SIS 300/315/330 series Video Overlay Port: 56 Name: XV_COLORKEY Flags: XvGettable XvSettable Min value: 0 Max value: 16777215 Current value: 526352 Name: XV_BRIGHTNESS Flags: XvGettable XvSettable Min value: -128 Max value: 127 Current value: 10 Name: XV_CONTRAST Flags: XvGettable XvSettable Min value: 0 Max value: 7 Current value: 2 Name: XV_SATURATION Flags: XvGettable XvSettable Min value: -7 Max value: 7 Current value: 0 Name: XV_HUE Flags: XvGettable XvSettable Min value: -8 Max value: 7 Current value: 0 Name: XV_AUTOPAINT_COLORKEY Flags: XvGettable XvSettable Min value: 0 Max value: 1 Current value: 1 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Name: XV_TVXPOSITION Flags: XvGettable XvSettable Min value: -32 Max value: 32 Current value: 0 Name: XV_TVYPOSITION Flags: XvGettable XvSettable Min value: -32 Max value: 32 Current value: 0 Name: XV_GAMMA_RED Flags: XvGettable XvSettable Min value: 100 Max value: 1 Current value: 1000 Name: XV_GAMMA_GREEN Flags: XvGettable XvSettable Min value: 100 Max value: 1 Current value: 1000 Name: XV_GAMMA_BLUE Flags: XvGettable XvSettable Min value: 100 Max value: 1 Current value: 1000 Name: XV_DISABLE_GRAPHICS Flags: XvGettable XvSettable Min value: 0 Max value: 1 Current value: 0 Name: XV_DISABLE_GRAPHICS_LR Flags: XvGettable XvSettable Min value: 0 Max value: 1 Current value: 0 Name: XV_DISABLE_COLORKEY Flags: XvGettable XvSettable Min value: 0 Max value: 1 Current value: 0 Name: XV_USE_CHROMAKEY Flags: XvGettable XvSettable Min value: 0 Max value: 1 Current value: 0 Name: XV_INSIDE_CHROMAKEY Flags: XvGettable XvSettable Min value: 0 Max value: 1 Current value: 0 Name: XV_CHROMAMIN Flags: XvGettable XvSettable Min value: 0 Max value: 16777215 Current value: 66046 Name: XV_CHROMAMAX Flags: XvGettable XvSettable Min value: 0 Max value: 16777215 Current value: 66047 Name: XV_SWITCHCRT Flags: XvGettable XvSettable Min value: 0 Max value: 1 Current value: 1 Adaptor: 1 Name: SIS 315/330 series Video Blitter Port: 57 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 58 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 59 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 60 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 61 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 62 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 63 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 64 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 65 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 66 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 67 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 68 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 69 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 70 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 71 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Port: 72 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 e...@eli-bernstein:~$ -- [nvidia] Blue hue in all videos https://bugs.launchpad.net/bugs/184440 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324894] Re: Corrupted low memory at kernel warning on resume
I've never tried the 2.6.32 kernel with Jaunty. I never had any issues with the stock kernel included with Jaunty, so I never upgraded it. The kernel itself appears fine with my hardware. I don't think there would be issues with the newer kernel running on the Jaunty release, but I can't say with certainty as I never tried it. -- Corrupted low memory at kernel warning on resume https://bugs.launchpad.net/bugs/324894 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324894] Re: Corrupted low memory at kernel warning on resume
I have since been able to work around this issue without having to move to the development lucid lynx distro. Instead, I found a 2.6.32 kernel build in this ppa repository for karmic: https://launchpad.net/~apw/+archive/green I added this ppa to my sources list and apt-get installed linux-image. Since upgrading the kernel, I no longer get this corrupted low memory error and my laptop appears to be stable again. -- Corrupted low memory at kernel warning on resume https://bugs.launchpad.net/bugs/324894 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 465617] Re: WARNING: at /build/buildd/linux-2.6.31/arch/x86/kernel/check.c:134 check_for_bios_corruption+0xe5/0x100()
I am also experiencing this issue on my IdeaPad Y30. In addition to the frequent panics and freezes, I also experience sudden reboots. I've also experienced data corruption when accessing a file from the hard disk. When attempting to extract a file from a bzipped tar archive, I got a premature end of file. However, I was able to successfully extract from the archive after rebooting into a Jaunty boot cd. This archive was on an ext3 partition. -- WARNING: at /build/buildd/linux-2.6.31/arch/x86/kernel/check.c:134 check_for_bios_corruption+0xe5/0x100() https://bugs.launchpad.net/bugs/465617 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452814] Re: WARNING: at /build/buildd/linux-2.6.31/net/ipv4/tcp.c:1408 tcp_recvmsg+0xa49/0xb20()
I get this same error either in idle (just having booted, window manager is up, user is logged in) or during apport uploading details of an application error (sequence is not clear). -- WARNING: at /build/buildd/linux-2.6.31/net/ipv4/tcp.c:1408 tcp_recvmsg+0xa49/0xb20() https://bugs.launchpad.net/bugs/452814 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 424606] Re: knetworkmanager crashed with SIGSEGV in __dynamic_cast()
Any plans on releasing this fix into the jaunty backports ppa (found at http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu)? If it had been released, I am still experiencing the same issues and am currently up to date on updates. -- knetworkmanager crashed with SIGSEGV in __dynamic_cast() https://bugs.launchpad.net/bugs/424606 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-networkmanagement in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 347838] Re: [LENOVO INVALID] suspend/resume failure
This issue is still not resolved in the latest karmic build. I tried suspending while booted into the livecd in the karmic alpha 3 build. When trying to suspend, the keyboard led's (caps lock, scroll lock and num lock) all blink once in unison and then the laptop immediately locks up. The machine becomes completely unresponsive and has to be powered down and brought back up again. This time however, the screen does not blank as before-- when suspending from the gui, the desktop remains on the screen completely frozen. Attempting to suspend from the command line was also attempted with the command echo mem /sys/power/state being run as root. The same results occured-- the computer became completely unresponsive. No screen blanking occurs-- the screen remains frozen, including the cursor, which no longer blinks. -- [LENOVO INVALID] suspend/resume failure https://bugs.launchpad.net/bugs/347838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350976] Re: knetwork manager does not recall stored passwords
I have in fact experienced similar symptoms too, where on occasion it would prompt for a password by then connect just fine after canceling the prompt. However, I do not believe it happens for me on the first attempt after login. Usually this happens after waking up from hibernate, though not consistently. -- knetwork manager does not recall stored passwords https://bugs.launchpad.net/bugs/350976 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to knetworkmanager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 350976] Re: knetwork manager does not recall stored passwords
Also note that for me at least, this bug did not occur if the option was set to connect automatically, only when trying to select a network manually which had been previously configured and stored did this issue occur. -- knetwork manager does not recall stored passwords https://bugs.launchpad.net/bugs/350976 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to knetworkmanager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 360029] Re: kde powermanagement does not overide power button press action properly
This would be on the Jaunty release with kde 4.2, so I believe this is the widget. The release was installed when it was in alpha 5, but had been kept up to date as of the reporting of this issue. -- kde powermanagement does not overide power button press action properly https://bugs.launchpad.net/bugs/360029 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360029] [NEW] kde powermanagement does not overide power button press action properly
Public bug reported: Binary package hint: kde-guidance-powermanager When configuring the power profiles in the powermanagement widget, the power button press action does not override the system default when set. In one particular instance, a profile is set to log out on power button press, however, when that profile is currently set, pressing the power button still results in a system shutdown, not a logout as expected. It is believed that the shutdown action is the default action taken by ubuntu when no user provided power management is running (e.g. no user logged on). Other actions, such as the lid closed, functions as expected, behaving as configured in the profile. When the current profile has the power button action configured to behave differently than shutdown, it is expected that that overridden behavior works rather than the system default. ** Affects: guidance-power-manager (Ubuntu) Importance: Undecided Status: New -- kde powermanagement does not overide power button press action properly https://bugs.launchpad.net/bugs/360029 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348275] Re: [iwlagn] networkmanager applet cannot connect to WPA2 home network (intel 4965)
I would like to confirm that I've been experiencing this same bug on my laptop with an Intel PRO/Wireless 5100 AGN controller. After resuming from suspend, I would not be able to connect to a WPA2 network (WPA2-PSK). When I unloaded and reloaded the wifi module, iwlagn, I was then able to connect to the wpa2 network. This was the messages found in dmesg when failing to connect: wlan0: authenticate with AP XX:XX:XX:XX:XX:XX wlan0: authenticated wlan0: associate with AP XX:XX:XX:XX:XX:XX wlan0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x1 status=10 aid=0) wlan0: AP denied association (code=10) -- [iwlagn] networkmanager applet cannot connect to WPA2 home network (intel 4965) https://bugs.launchpad.net/bugs/348275 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 324894] Re: Corrupted low memory at kernel warning on resume
I am also receiving a similar error message on my laptop-- a lenovo Y530 405166U. The error messages occurs every single time immediately after booting: [ 59.816119] Corrupted low memory at 8800fcf0 (fcf0 phys) = 8384 [ 59.816125] Corrupted low memory at 8800fcf8 (fcf8 phys) = 001a [ 59.816134] [ cut here ] [ 59.816138] WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0() [ 59.816141] Memory corruption detected in low memory [ 59.816143] Modules linked in: ppdev bridge stp bnep input_polldev joydev lp parport snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss arc4 ecb snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer iwlagn iwlcore snd_seq_device uvcvideo compat_ioctl32 snd mac80211 asus_laptop psmouse videodev soundcore video ricoh_mmc sdhci_pci sdhci v4l1_compat serio_raw pcspkr iTCO_wdt iTCO_vendor_support snd_page_alloc intel_agp cfg80211 output led_class nvidia(P) ohci1394 ieee1394 ehci_hcd tg3 uhci_hcd fbcon tileblit font bitblit softcursor [ 59.816206] Pid: 0, comm: swapper Tainted: P 2.6.28-9-generic #29-Ubuntu [ 59.816209] Call Trace: [ 59.816212] IRQ [802508d7] warn_slowpath+0xb7/0xf0 [ 59.816223] [8026e6ac] ? sched_clock_cpu+0xcc/0x160 [ 59.816228] [80270959] ? getnstimeofday+0x59/0xe0 [ 59.816233] [8026e6ac] ? sched_clock_cpu+0xcc/0x160 [ 59.816238] [8068c580] ? printk+0x67/0x6f [ 59.816242] [80274cd5] ? tick_program_event+0x25/0x30 [ 59.816247] [8026c7f6] ? hrtimer_interrupt+0x166/0x1c0 [ 59.816252] [802168dd] check_for_bios_corruption+0xdd/0xe0 [ 59.816256] [802168e0] ? periodic_check_for_corruption+0x0/0x40 [ 59.816261] [802168e9] periodic_check_for_corruption+0x9/0x40 [ 59.816267] [8025be39] run_timer_softirq+0x179/0x260 [ 59.816271] [80256a7c] __do_softirq+0x9c/0x170 [ 59.816276] [80213d8c] call_softirq+0x1c/0x30 [ 59.816280] [80214ffd] do_softirq+0x5d/0xa0 [ 59.816283] [802567fd] irq_exit+0x8d/0xa0 [ 59.816287] [802152c5] do_IRQ+0xc5/0x110 [ 59.816291] [80212bf3] ret_from_intr+0x0/0x29 [ 59.816294] EOI [80474d08] ? acpi_idle_enter_bm+0x28a/0x2da [ 59.816302] [80474d00] ? acpi_idle_enter_bm+0x282/0x2da [ 59.816308] [8057e005] ? cpuidle_idle_call+0xa5/0x100 [ 59.816314] [80210e85] ? cpu_idle+0x65/0xc0 [ 59.816319] [8067abac] ? rest_init+0x5c/0x70 [ 59.816323] ---[ end trace 2a61c7d9d1e9b905 ]--- -- Corrupted low memory at kernel warning on resume https://bugs.launchpad.net/bugs/324894 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350976] [NEW] knetwork manager does not recall stored passwords
Public bug reported: Binary package hint: knetworkmanager When prompting for credentials to connect to a new network, Knetwork Manager will store all corresponding data into the KWallet, however it fails to recall this data again on successive sessions, resulting in the user having to reinput all necessary information. This same data is then stored again in the KWallet, under a different key. When I choose a network from the network manager list, I expect it to recall all necessary data to connect to it if it had been connected to previously (e.g. has same essid, AP-mac address, etc). Instead, it just prompts as if it was a new network and stores the duplicated data elsewhere. ** Affects: knetworkmanager (Ubuntu) Importance: Undecided Status: New -- knetwork manager does not recall stored passwords https://bugs.launchpad.net/bugs/350976 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347838] Re: [LENOVO INVALID] suspend/resume failure
Let me provide answers as I can observe from my laptop-- Lenovo Y530 laptop, model 405166U: Did the machine break while going to sleep or waking up? It appears to be breaking while going into sleep. The screen blanks out and the CAPS/NUM/SCROLL lock leds all blink once. After the LED's blink, nothing else happens. No other leds change to indicate a low power state and there is no response from CAPS lock or the wifi kill switch. Despite the screen blanking, the laptop is clearly not in a sleep state-- the cpu fan remains on and heat is still dissipating from the laptop. Is it reproducible? With exception of two attempts, this behavior always occurs. With the first of the other two exceptions, the laptop woke up immediately during the suspend process. In the second exception, the laptop went into the usual state, however, still responded to CAPS lock with the led, and woke up shortly thereafter. I managed to capture the dmesg portion of the suspend process during this second exception and will post it as an attachment. Did it work before? This is a new laptop for me and has never worked before. I have only tried Ubuntu version 8.10 and the latest alpha of 9.04. I have not tried any other versions. Do you end up with flashing caps-lock or similar? Other than the single flash of the LEDs, indicative of a power state change, no consistent blinking of any led's had occurred, leading to believe that this was not a kernel panic. ** Attachment added: Output of dmesg shortly after the attempted suspend and successful recovery. http://launchpadlibrarian.net/24415772/dmesg-suspend.txt -- [LENOVO INVALID] suspend/resume failure https://bugs.launchpad.net/bugs/347838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347838] Re: [LENOVO INVALID] suspend/resume failure
I had mentioned earlier that the screen blanks when going into sleep-- this is not actually the case. Usually, The screen simply goes black with a blinking cursor at the top left of the screen. Occasionally, however, the laptop will attempt to suspend but immediately wakeup instead. -- [LENOVO INVALID] suspend/resume failure https://bugs.launchpad.net/bugs/347838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270748] Re: ath9k wireless not working with AR9280
I have a very simililar problem... although my connection drops each 10-30 seconds. no big deal while browsing but this renders wireless completely unusable for any other task (streaming, copying files bigger than 5MB) while active i get about 3MB/s throughput. network manager does automatically reconnect each time, but this takes just to long for any copy/streaming operation to not abort. I use a macbookpro santarosa in conjunction with a timecapsule router from apple. on OSX windows everything works fine. The router is in g/n mode on the 2.5Ghz band using WPA2-Personal encryption. -- ath9k wireless not working with AR9280 https://bugs.launchpad.net/bugs/270748 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280555] Re: Evolution Monthly Calendar Print Mislabels Days
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/18359215/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/18359216/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/18359217/ProcStatus.txt -- Evolution Monthly Calendar Print Mislabels Days https://bugs.launchpad.net/bugs/280555 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280555] [NEW] Evolution Monthly Calendar Print Mislabels Days
Public bug reported: Binary package hint: evolution When I print a monthly view of an evolution calendar, the first column is correctly labeled Sat/Sun. The second column is incorrectly labeled Sunday (should be Monday). The third column is incorrectly labeled Monday (should be Tuesday), The fourth column is incorrectly labeled Tuesday (should be Wednesday). The fifth column is incorrectly labeled Wednesday (should be Thursday). The sixth column is incorrectly labeled Thursday (should be Friday). I attempted to attach a pdf file showing the column mislabeling, but Launchpad failed to pick up the file :^). ProblemType: Bug Architecture: i386 Date: Wed Oct 8 21:27:48 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evolution NonfreeKernelModules: nvidia Package: evolution 2.22.3.1-0ubuntu1 PackageArchitecture: i386 ProcEnviron: LANG=en_US.UTF-8 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games SHELL=/bin/bash SourcePackage: evolution Uname: Linux 2.6.24-16-generic i686 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- Evolution Monthly Calendar Print Mislabels Days https://bugs.launchpad.net/bugs/280555 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48263] Re: [regression] Wired ethernet (VIA VT6102 Rhine II) and Wireless (RaLink 2500) no longer work under 6.06 (needs acpi=noirq blacklisting)
Bill, try installing with the *alternate* desktop CD. -- [regression] Wired ethernet (VIA VT6102 Rhine II) and Wireless (RaLink 2500) no longer work under 6.06 (needs acpi=noirq blacklisting) https://bugs.launchpad.net/bugs/48263 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48263] Re: [regression] Wired ethernet (VIA VT6102 Rhine II) and Wireless (RaLink 2500) no longer work under 6.06 (needs acpi=noirq blacklisting)
Leann, that laptop is currently my SO's primary machine, so I can't 'experiment' on it much (and I couldn't get the beta desktop LiveCD to finish booting in one recent window of opportunity). I'll be upgrading most of our machines to Hardy soon, and I'll check it out then. I *suspect* it is still a problem, as it certainly was for Gutsy (as Scottopoly reported in November), and the same 'acpi=noirq' solution worked then, but I will (eventually) actually test against Hardy and make sure. -- [regression] Wired ethernet (VIA VT6102 Rhine II) and Wireless (RaLink 2500) no longer work under 6.06 (needs acpi=noirq blacklisting) https://bugs.launchpad.net/bugs/48263 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145112] Re: Random NVidia Proprietary Driver Lock-Ups with dual core + 7300
Please test Hardy alpha4 which is released today(ish). There will be no updates to the gutsy driver. Two words: Gutsy Backports. -- Random NVidia Proprietary Driver Lock-Ups with dual core + 7300 https://bugs.launchpad.net/bugs/145112 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145112] Re: Random NVidia Proprietary Driver Lock-Ups with dual core + 7300
OK, I made the backport request as Bug #189787 . -- Random NVidia Proprietary Driver Lock-Ups with dual core + 7300 https://bugs.launchpad.net/bugs/145112 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188888] [NEW] firefox xforms plugin does not work
Public bug reported: Binary package hint: firefox the xforms plugin 0.8.0.3 (found at https://addons.mozilla.org/de/firefox/addon/824) does not work with the ubuntu version of firefox. it does install without errors, however it fails to work. test cases (after installation of the plugin) can be found at http://www.mozilla.org/projects/xforms/samples.html this is likely a compilation / configration error in the ubuntu version of firefox since downloading the corresponding official firefox version (2.0.0.11) (from http://www.mozilla-europe.org/de/products/firefox/) and running it with a new profile (./firefox -ProfileManager), installing the xforms plugin (including firefox restart) then quitting the official firefox, starting ubuntu's firefox with the newly created profile et violà the test cases work. [EMAIL PROTECTED]:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION=Ubuntu 7.10 [EMAIL PROTECTED]:~$ dpkg -l firefox | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Beschreibung +++-==-=- ii firefox2.0.0.11+2nobinonly-0ubuntu0.7.10 lightweight web browser based on Mozilla ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- firefox xforms plugin does not work https://bugs.launchpad.net/bugs/18 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145112] Re: Random NVidia Proprietary Driver Lock-Ups with dual core + 7300
Looks like a couple of days ago NVidia released an updated driver (169.09) with some extra bugfixes: http://www.nvnews.net/vbulletin/showthread.php?t=106661 -- Random NVidia Proprietary Driver Lock-Ups with dual core + 7300 https://bugs.launchpad.net/bugs/145112 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184087] Re: xserver-xorg
** Changed in: ubuntu Assignee: (unassigned) = canonical-xorg (canonical-xorg) -- xserver-xorg https://bugs.launchpad.net/bugs/184087 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145112] Re: Random NVidia Proprietary Driver Lock-Ups with dual core + 7300
Probably the right thing to do here is to get the new driver into the Hardy restricted repos, and then make a Gutsy restricted backport available. Yoo hoo... Maintainers... Can you give us a hand here? -- Random NVidia Proprietary Driver Lock-Ups with dual core + 7300 https://bugs.launchpad.net/bugs/145112 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145112] Re: Random NVidia Proprietary Driver Lock-Ups with dual core + 7300
OK, so when can we expect nvidia-glx-new to be updated (for Hardy or Gutsy)? -- Random NVidia Proprietary Driver Lock-Ups with dual core + 7300 https://bugs.launchpad.net/bugs/145112 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145112] Re: Random NVidia Proprietary Driver Lock-Ups with dual core + 7300
Perusing synaptic (on Gutsy) only shows two different versions of 100.14.19: 100.14.19+2.6.22.4-14.9 from gutsy and 100.14.19+2.6.22.4-14.10 from gutsy-updates. So how would we downgrade to 100.14.09? -- Random NVidia Proprietary Driver Lock-Ups with dual core + 7300 https://bugs.launchpad.net/bugs/145112 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145112] Re: Random NVidia Proprietary Driver Lock-Ups with dual core + 7300
Looks like nvidia may have fixed the problem in the recent beta driver: http://www.nvnews.net/vbulletin/showthread.php?t=102509 -- Random NVidia Proprietary Driver Lock-Ups with dual core + 7300 https://bugs.launchpad.net/bugs/145112 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113491] Re: Proposal: New startup and shutdown sounds for gusty gibbon
'Fisty'? Ew. -- Proposal: New startup and shutdown sounds for gusty gibbon https://bugs.launchpad.net/bugs/113491 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102507] Re: Dependencies of ubuntu-desktop
view here http://ubuntuforums.org/showpost.php?p=2575753postcount=24 -- Dependencies of ubuntu-desktop https://bugs.launchpad.net/bugs/102507 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107940] Re: Ubuntu should include bluez-gnome by default
yes this should definitively be in recommends of ubuntu-desktop -- Ubuntu should include bluez-gnome by default https://bugs.launchpad.net/bugs/107940 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102507] Re: Dependencies of ubuntu-desktop
this has been done in feisty !!! these fonts are listed as recommends ! to sojourner : synaptic and apt do not allow you to remove recommended packages, it treats them as dependecies, however they can be removed (or never installed) with aptitude ! Or like avb hinted at, you can make apt (and synaptic?) treat recommends as recommends by editing configuration files. ** Changed in: ubuntu-meta (Ubuntu) Status: Unconfirmed = Fix Committed -- Dependencies of ubuntu-desktop https://bugs.launchpad.net/bugs/102507 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49524] Re: Removal of ubuntu-desktop needs a stronger warning
this change should really be made !! i never really knew what the ominous recommend you keep it means it's just useless info, as all but advanced users should not remove standart packages. however an advanced user (like me) might think, a its recommended but why exactly? ...ok what the hell i'll remove it as i want package xy no longer. this just leads to frustrated users and useless bug reports, because advanced users will remove this package without knowing what get's broken... i for instance just removed most recommended packages by ubuntu-desktop, will this break an upgrade? i've no clue but i after reading this bug description i certainly know exactly where to look if something stops working -- Removal of ubuntu-desktop needs a stronger warning https://bugs.launchpad.net/bugs/49524 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90803] Re: evolution cannot be uninstalled
having the same problem with removing gaim ! nautilus-sendto should be a recommends and not a depends ! -- evolution cannot be uninstalled https://bugs.launchpad.net/bugs/90803 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96670] Re: change gthumb dependency to recommends
i think exactly the same ! f-spot / eog make gthumb obsolet, but gthumb is in depends while f-spot is in recommends. huh? move gthumb to recommends! -- change gthumb dependency to recommends https://bugs.launchpad.net/bugs/96670 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99718] Re: ubuntu-desktop should not depend on nautilus-sendto
*** This bug is a duplicate of bug 90803 *** https://bugs.launchpad.net/bugs/90803 having the same problem with removing gaim ! nautilus-sendto should be a recommends and not a depends ! -- ubuntu-desktop should not depend on nautilus-sendto https://bugs.launchpad.net/bugs/99718 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111267] Installed version is 2.4.4c1
Public bug reported: Binary package hint: python2.4 The Python installed is 2.4.4c1, a release candidate, not the production version of 2.4.4. This causes problems with build/install systems that detect available versions of Python, such as Zope3's. This currently affects Edgy. ** Affects: python2.4 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Installed version is 2.4.4c1 https://bugs.launchpad.net/bugs/111267 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111267] Re: Installed version is 2.4.4c1
That's ridiculous. Feisty has a production 2.4.4 available, and so should Edgy. Having a release candidate version of Python be the default python on a system is a very bad idea in general, even aside the problems it is causing me with Zope in particular. There is no way you can legitimately characterize this as a bug in Zope3 or anything else that specifies a list of acceptable versions. -- Installed version is 2.4.4c1 https://bugs.launchpad.net/bugs/111267 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111267] Re: Installed version is 2.4.4c1
OK, I've filed a backport request: https://bugs.launchpad.net/edgy- backports/+bug/111341 -- Installed version is 2.4.4c1 https://bugs.launchpad.net/bugs/111267 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59549] Re: WEP is listed on WPA configure AP.
I had experienced the same issue with both Feisty Fawn and Sabayon Linux on my thinkpad t30. It has an intersil prism2.5 pci card, using the hostap driver. It appears that NetworkManager misinterprets or otherwise fails to scan for networks properly. However, I did discover a workaround: 1: stop NetworkManager 2: start wpa_supplicant with control interface 3: initiate a scan with wpa_cli 4: kill wpa_supplicant 5: start NetworkManager After doing this, I find that the list of networks now show WPA flags on the details that pop up, and when selecting one, it now prompts for the appropriate wpa password instead of having wep as the only option. I am not sure if this fixes NetworkManager with successive scans, I get the sense that it will not. Until a real fix is created, I'm simply adding the steps above in the NetworkManager init scripts for now. -- WEP is listed on WPA configure AP. https://bugs.launchpad.net/bugs/59549 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69297] Re: Gaim crashed on startup
GAIM crashes whenever I try to start it. I have accounts on all major IM services, and GAIM autologons to them all, so I have no idea if the crash is specific to one of them. Because of the crash on startup, I cannot get to the accounts dialog to try turning some of them off. In any case, I've included my crash report. ** Attachment added: _usr_bin_gaim.1000.crash http://librarian.launchpad.net/7393472/_usr_bin_gaim.1000.crash -- Gaim crashed on startup https://bugs.launchpad.net/bugs/69297 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69985] Re: Gaim randomly crashed
Another 'random' crash on edgy I actually wasn't doing anything when it happened, however 5 minutes previously I had twice tried to transfer a file (to an iChat user) that failed. ** Attachment added: crash report http://librarian.launchpad.net/6132956/_usr_bin_gaim.1000.crash -- Gaim randomly crashed https://launchpad.net/bugs/69985 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
