[Bug 1938683] Re: dash number-of-windows indicator not cleared for thunderbird
** Attachment added: "Screenshot from 2021-08-02 11-46-16.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938683/+attachment/5515238/+files/Screenshot%20from%202021-08-02%2011-46-16.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1938683 Title: dash number-of-windows indicator not cleared for thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1938683] [NEW] dash number-of-windows indicator not cleared for thunderbird
Public bug reported: The "number of windows" indicator in the Ubuntu Dash (the orange dots to the left of the app icon) is not cleared for Thunderbird, when a new e-mail is written in a new window. Ultimately, the indicators stay visible even after Thunderbird is closed completely, and it's no longer possible to launch thunderbird by left-clicking of the dash icon (middle-click works okay). Steps to reproduce: 1. Launch Thunderbird. There is one orange dot to the left of the thunderbird icon. 2. Write an e-mail and close the e-mail window 3. Observe that there are now two orange dots to the left of the thunderbird icon. Please see the screenshot for more details. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 2 11:41:47 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-03-24 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (101 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1938683 Title: dash number-of-windows indicator not cleared for thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848277] Re: Won't start, get "cannot open display: :0" message
Also does not work for me on Ubuntu 20.10 when running on Xorg. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1848277 Title: Won't start, get "cannot open display: :0" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1848277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Daniel thank you so much for being so supportive, I really appreciate it :) I have ran the command `ubuntu-bug /var/crash/_usr_bin_gnome- shell.1000.crash` which then opens a dialog; however when I press "Send" there's no follow-up - no browser tab opens. The contents of `_usr_bin_gnome-shell.1000.uploaded` says `93823806-9ff7-11ea- 9bb3-fa163e102db1` so maybe it's already there in your servers. From the dialog I see the following title: gnome-shell crashed with SIGABRT in __Gl___poll() (sorry copy-paste from the dialog doesn't work). And there is no rush - the computer crashes once per day or so, so it's definitely not that annoying; if it becomes an annoyance I'll install the proprietary driver as a workaround. Thanks again -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Thank you kindly. I was able to ssh into the machine and prepare a crash report from the gnome-shell process, I will upload that shortly, perhaps as a separate bug report. However, the real culprit might be located in the dmesg: ``` [12870.773176] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] [12870.773196] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery [12870.773220] nouveau :01:00.0: fifo: channel 6: killed [12870.773229] nouveau :01:00.0: fifo: engine 5: scheduled for recovery [12870.773234] nouveau :01:00.0: fifo: engine 0: scheduled for recovery [12870.773896] nouveau :01:00.0: systemd-logind[1312]: channel 6 killed! [12907.524710] GpuWatchdog[5838]: segfault at 0 ip 560accf3e4c9 sp 7f3ce9a516c0 error 6 in chrome[560ac8dd1000+7094000] [12907.524716] Code: 00 79 09 48 8b 7d c0 e8 05 28 2b fc c7 45 c0 aa aa aa aa 0f ae f0 41 8b 84 24 e0 00 00 00 89 45 c0 48 8d 7d c0 e8 e7 44 e9 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e [12922.616876] nouveau :01:00.0: Xwayland[2419]: failed to idle channel 4 [Xwayland[2419]] [12937.616723] nouveau :01:00.0: Xwayland[2419]: failed to idle channel 4 [Xwayland[2419]] [12937.616907] nouveau :01:00.0: fifo: fault 00 [READ] at 00013000 engine 07 [HOST0] client 07 [HUB/HOST_CPU] reason 02 [PTE] on channel 4 [007fa19000 Xwayland[2419]] [12937.616915] nouveau :01:00.0: fifo: channel 4: killed [12937.616917] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery [12937.616923] nouveau :01:00.0: fifo: engine 0: scheduled for recovery [12937.616941] nouveau :01:00.0: fifo: engine 5: scheduled for recovery [12937.616945] nouveau :01:00.0: Xwayland[2419]: channel 4 killed! [12937.735092] [ cut here ] [12937.735142] WARNING: CPU: 3 PID: 26055 at drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6d/0x80 [nouveau] [12937.735142] Modules linked in: rfcomm aufs cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr mei_hdcp snd_hda_codec_hdmi intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm intel_cstate intel_rapl_perf iwlmvm mac80211 libarc4 snd_usb_audio snd_hda_codec_realtek serio_raw intel_wmi_thunderbolt uvcvideo rmi_smbus snd_hda_codec_generic snd_usbmidi_lib rmi_core snd_seq_midi snd_seq_midi_event wmi_bmof videobuf2_vmalloc iwlwifi videobuf2_memops videobuf2_v4l2 snd_rawmidi snd_hda_intel videobuf2_common snd_intel_dspcfg rtsx_pci_ms thinkpad_acpi btusb snd_hda_codec nvram videodev btrtl btbcm snd_hda_core input_leds memstick ledtrig_audio mc snd_seq btintel joydev cfg80211 snd_hwdep bluetooth snd_pcm snd_seq_device mei_me ecdh_generic ecc snd_timer mei intel_pch_thermal snd soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress dm_crypt [12937.735161] raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nouveau rtsx_pci_sdmmc mxm_wmi aesni_intel crypto_simd i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt cryptd fb_sys_fops glue_helper drm e1000e psmouse ahci i2c_i801 rtsx_pci libahci wmi video [12937.735173] CPU: 3 PID: 26055 Comm: chrome Not tainted 5.4.0-31-generic #35-Ubuntu [12937.735174] Hardware name: LENOVO 20EN0005MS/20EN0005MS, BIOS N1EET87W (1.60 ) 12/06/2019 [12937.735194] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau] [12937.735196] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 48 89 45 e8 e8 71 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 ea f6 58 eb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [12937.735196] RSP: 0018:b807c5f5fbc8 EFLAGS: 00010282 [12937.735197] RAX: fffe RBX: b807c5f5fbf8 RCX: [12937.735198] RDX: 0010 RSI: b807c5f5fb38 RDI: b807c5f5fbd8 [12937.735198] RBP: b807c5f5fbe8 R08: R09: [12937.735199] R10: 0030 R11: 9b7ac9c07e40 R12: b807c5f5fc30 [12937.735199] R13: 9b7ca4fff0b0 R14: R15: 9b7ac9c07e38 [12937.735200] FS: 7f3cfaa1db00() GS:9b7cac2c() knlGS: [12937.735201] CS: 0010 DS: ES: CR0: 80050033 [12937.735201] CR2: 560ad25fe010 CR3: 000842f0a004 CR4: 003606e0 [12937.735202] DR0: DR1: DR2: [12937.735202] DR3: DR6: fffe0ff0 DR7: 0400 [12937.735203] Call Trace: [12937.735265] nouveau_vma_del+0x75/0xc0 [nouveau] [12937.735316] nouveau_gem_object_close+0x1f5/0x210 [nouveau] [12937.735330] drm_gem_object_release_handle+0x35/0xa0 [drm] [12937.735337] drm_gem_handle_delete+0x59/0xa0 [drm] [12937.735344] ?
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+attachment/5377303/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
It was a different time, so maybe they're unrelated as you say. Because the sound continues to play, I suspect that it's just the graphics stack that freezes. To verify this assumption I've installed openssh-server on the laptop; if the freeze occurs again, I'll ssh into the machine and I may be able to gather useful debugging info. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Thank you so much. I was not yet able to investigate the crash (it usually happens during a video call and then I quickly need to reboot, to continue chatting with the customer - no time to diagnose :-D ) However, today I found out something in the log that might be connected (even though in this case nothing crashed, the computer seems to be continuing just fine): [ 2090.256068] [ cut here ] [ 2090.256153] WARNING: CPU: 5 PID: 6749 at drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6d/0x80 [nouveau] [ 2090.256154] Modules linked in: ccm rfcomm aufs cmac algif_hash overlay algif_skcipher af_alg bnep binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_hdmi intel_rapl_msr mei_hdcp intel_rapl_common iwlmvm x86_pkg_temp_thermal intel_powerclamp coretemp mac80211 kvm_intel snd_hda_codec_realtek libarc4 snd_hda_codec_generic kvm rmi_smbus snd_usb_audio rmi_core uvcvideo snd_usbmidi_lib intel_cstate intel_rapl_perf videobuf2_vmalloc snd_hda_intel serio_raw btusb iwlwifi videobuf2_memops snd_intel_dspcfg videobuf2_v4l2 btrtl snd_seq_midi snd_hda_codec videobuf2_common snd_seq_midi_event snd_rawmidi btbcm snd_hda_core btintel intel_wmi_thunderbolt videodev input_leds joydev snd_hwdep wmi_bmof snd_seq thinkpad_acpi bluetooth rtsx_pci_ms mc snd_pcm memstick cfg80211 nvram ledtrig_audio mei_me ecdh_generic snd_seq_device ecc intel_pch_thermal mei snd_timer snd soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress [ 2090.256181] hid_generic usbhid hid dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rtsx_pci_sdmmc nouveau aesni_intel crypto_simd mxm_wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect cryptd sysimgblt glue_helper fb_sys_fops psmouse drm e1000e i2c_i801 rtsx_pci ahci libahci wmi video [ 2090.256215] CPU: 5 PID: 6749 Comm: chrome Not tainted 5.4.0-31-generic #35-Ubuntu [ 2090.256215] Hardware name: LENOVO 20EN0005MS/20EN0005MS, BIOS N1EET87W (1.60 ) 12/06/2019 [ 2090.256263] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau] [ 2090.256283] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 48 89 45 e8 e8 71 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 ea 26 7f ed 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [ 2090.256284] RSP: 0018:a8d503f27bc8 EFLAGS: 00010282 [ 2090.256286] RAX: fffe RBX: a8d503f27bf8 RCX: [ 2090.256287] RDX: 0010 RSI: a8d503f27b38 RDI: a8d503f27bd8 [ 2090.256287] RBP: a8d503f27be8 R08: R09: [ 2090.256288] R10: 0030 R11: 927e7fc8f640 R12: a8d503f27c30 [ 2090.256289] R13: 927f64fee0b0 R14: R15: 927e7fc8f638 [ 2090.256290] FS: 7f0fb553bb00() GS:927f6c34() knlGS: [ 2090.256291] CS: 0010 DS: ES: CR0: 80050033 [ 2090.256291] CR2: 55bdb8317000 CR3: 00088824a003 CR4: 003606e0 [ 2090.256292] DR0: DR1: DR2: [ 2090.256306] DR3: DR6: fffe0ff0 DR7: 0400 [ 2090.256306] Call Trace: [ 2090.256362] nouveau_vma_del+0x75/0xc0 [nouveau] [ 2090.256402] nouveau_gem_object_close+0x1f5/0x210 [nouveau] [ 2090.256416] drm_gem_object_release_handle+0x35/0xa0 [drm] [ 2090.256427] drm_gem_handle_delete+0x59/0xa0 [drm] [ 2090.256449] ? drm_gem_handle_create+0x40/0x40 [drm] [ 2090.256478] drm_gem_close_ioctl+0x24/0x30 [drm] [ 2090.256488] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2090.256511] drm_ioctl+0x234/0x3d0 [drm] [ 2090.256522] ? drm_gem_handle_create+0x40/0x40 [drm] [ 2090.256526] ? evict+0x14c/0x1b0 [ 2090.256565] nouveau_drm_ioctl+0x78/0xc0 [nouveau] [ 2090.256567] do_vfs_ioctl+0x407/0x670 [ 2090.256570] ? __secure_computing+0x42/0xe0 [ 2090.256571] ksys_ioctl+0x67/0x90 [ 2090.256573] __x64_sys_ioctl+0x1a/0x20 [ 2090.256575] do_syscall_64+0x57/0x190 [ 2090.256578] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2090.256579] RIP: 0033:0x7f0fae1375d7 [ 2090.256581] Code: b3 66 90 48 8b 05 b1 48 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 81 48 2d 00 f7 d8 64 89 01 48 [ 2090.256595] RSP: 002b:7ffcbdcc1068 EFLAGS: 0246 ORIG_RAX: 0010 [ 2090.256596] RAX: ffda RBX: 55bdb82e3870 RCX: 7f0fae1375d7 [ 2090.256597] RDX: 7ffcbdcc10a0 RSI: 40086409 RDI: 0015 [ 2090.256597] RBP: 7ffcbdcc10a0 R08: R09: 0002 [ 2090.256598] R10: 7f0fa1124070 R11: 0246 R12: 40086409 [ 2090.256599] R13: 0015 R14: 0001 R15: b82c7b00 [ 2090.256600] ---[ end trace 9a9c0a943b125b8f ]--- [
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Thank you, I was exactly hoping for a guidance on how to debug this issue further. The crash happened today 10:55:00; please find the output of journalctl -b-1 attached. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+attachment/5370267/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878166] [NEW] gnome-shell freezes randomly on nouveau and wayland
Public bug reported: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868924] [NEW] a desktop launcher icon can not be activated by focusing and pressing enter
Public bug reported: I have a desktop launcher icon which launches a shell script which auto- starts apps that I use. I tend to click on the launcher icon with my mouse, then press Enter to run the launcher. This worked well on Ubuntu 19.10 but stopped working on Ubuntu 20.04. Double-clicking on the launcher icon correctly launches the launcher, and I'm happy with the workaround. Yet, maybe something to look into. Thank you kindly :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 08:14:30 2020 InstallationDate: Installed on 2016-09-05 (1296 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to focal on 2020-03-20 (4 days ago) ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1868924 Title: a desktop launcher icon can not be activated by focusing and pressing enter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1868924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847184] [NEW] java Keyboard stops working after a dialog is shown
Public bug reported: On Ubuntu 19.10 + Gnome + Wayland, after a dialog (any dialog) is shown, the keyboard stops working in Intellij - the editor stops responding to keystrokes, global shortcuts like Ctrl+N stops working etc, until you alt-tab to another application and back to intellij. The bug has been reported here to Intellij: https://youtrack.jetbrains.com/issue/IDEA-222415 However, the bug was really present in https://gitlab.gnome.org/GNOME/mutter/issues/819 The fix is already in git: https://www.phoronix.com/scan.php?page=news_item=Java-Focus-GNOME- Wayland Could you please upgrade Mutter to include fix for this issue? Thank you :) Have a nice day ;) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 07:52:13 2019 InstallationDate: Installed on 2016-09-05 (1127 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-26 (11 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1847184 Title: java Keyboard stops working after a dialog is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1847184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838179] [NEW] gnome-system-monitor snap segfaults
Public bug reported: I have gnome-system-monitor installed as a snap. It never starts for me - it always segfaults. $ snap info gnome-system-monitor name: gnome-system-monitor summary: System Monitor publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bugs?field.tag=snap license: unset description: | GNOME System Monitor is a GNOME process viewer and system monitor with an attractive, easy-to-use interface, It has features, such as a tree view for process dependencies, icons for processes, the ability to hide processes that you don't want to see, graphical time histories of CPU/memory/swap usage, the ability to kill/renice processes needing root access, as well as the standard features that you might expect from a process viewer. commands: - gnome-system-monitor snap-id: 9BTClmjz31r0UltmbJ5nnGe0Xm1AzfMp tracking: stable/ubuntu-18.10 refresh-date: 18 days ago, at 23:46 EEST channels: stable:3.32.1-3-g0ea89b4922 2019-07-09 (100) 3MB - candidate: 3.32.1-3-g0ea89b4922 2019-07-09 (100) 3MB - beta: ↑ edge: ↑ installed: 3.32.1-3-g0ea89b4922(100) 3MB - $ gnome-system-monitor mkdir: cannot create directory '/home/vyzivus/snap/gnome-system-monitor/100/.config': Permission denied mkdir: cannot create directory '/home/vyzivus/snap/gnome-system-monitor/100/.local': Permission denied /snap/gnome-system-monitor/100/bin/desktop-launch: line 246: /home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.dirs: No such file or directory cp: cannot create regular file '/home/vyzivus/snap/gnome-system-monitor/100/.config': Permission denied /snap/gnome-system-monitor/100/bin/desktop-launch: line 249: /home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.dirs.md5sum: No such file or directory /snap/gnome-system-monitor/100/bin/desktop-launch: line 249: /home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.locale.md5sum: No such file or directory Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Desktop Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Downloads Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Templates Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Public Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Documents Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Music Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Pictures Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Videos realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.config’: Permission denied /snap/gnome-system-monitor/100/bin/desktop-launch: line 381: /home/vyzivus/snap/gnome-system-monitor/100/.config/fontconfig/fonts.conf: No such file or directory ln: failed to create symbolic link '/home/vyzivus/snap/gnome-system-monitor/100/.local/share': No such file or directory ln: failed to create symbolic link '/home/vyzivus/snap/gnome-system-monitor/100/.themes': Permission denied mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied ln: target '/home/vyzivus/snap/gnome-system-monitor/100/.local/share/glib-2.0/schemas' is not a directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.config’: Permission denied ln: failed to create symbolic link '/home/vyzivus/snap/gnome-system-monitor/100/.config/dconf': No such file or directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied ln: target '/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/DMZ-Black' is not a directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied ln: target '/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/DMZ-White' is not a directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied ln: failed to create symbolic link '/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/Papirus-Adapta-Maia': No such file or directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied ln: failed to create symbolic link '/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/Papirus-Adapta-Nokto-Maia': No such file or directory mkdir: cannot create directory
[Bug 1838179] Re: gnome-system-monitor snap segfaults
ubuntu 19.04 x86-64 5.0.0-21-generic #22-Ubuntu SMP Tue Jul 2 13:27:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1838179 Title: gnome-system-monitor snap segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1838179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826830] [NEW] newly launched apps start unfocused
Public bug reported: For example, pressing the ENTER key on a .png image in Krusader will start the Gnome Image Viewer (if Krusader is so configured), however the focus returns back to the Krusader. Pressing DEL would then delete files in the Krusader; pressing any keys controls the Krusader but since it's obscured by the Image Viewer, it's hard to see what's going on. This is highly confusing to me. A better solution would be either to start the Image Viewer focused, or to start the Image Viewer in the background, behind krusader (and perhaps flashing the icon in the Unity dock). I'm not sure whether the bug is in Krusader itself, or in Gnome-Shell (being a window manager), I'm a bit guessing here :) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 08:55:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['system-moni...@paradoxxx.zero.gmail.com', 'desktop-icons@csoriano', 'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-09-05 (965 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-12 (47 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826830 Title: newly launched apps start unfocused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826830] Re: newly launched apps start unfocused
Definitely Gnome Shell, since starting e.g. "Files" (Nautilus) from the dock starts the Nautilus unfocused, sending any keystrokes to whatever app was active before. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826830 Title: newly launched apps start unfocused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806384] [NEW] lock screen shows application list and allows launching apps
Public bug reported: Sometimes the login screen suddenly does not hide the app list. Clicking on individual apps will actually launch that app behind the lock screen. I haven't found a way to reliably reproduce this issue - it happens "randomly", mostly after I dock/undock laptop, or suspend/resume the laptop, or maybe plug/unplug the monitor. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 14:18:08 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['system-moni...@paradoxxx.zero.gmail.com']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2016-09-05 (819 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (66 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1806384 Title: lock screen shows application list and allows launching apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1806384/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806384] Re: lock screen shows application list and allows launching apps
Screenshot ** Attachment added: "IMG_20181203_133936.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1806384/+attachment/5218456/+files/IMG_20181203_133936.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1806384 Title: lock screen shows application list and allows launching apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1806384/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714804] Re: Aardvark Daily: Indicator-Multiload doesn't show full-width
Workaround is simply to use the gnome-shell-extension-system-monitor instead - it's essentially the indicator-multiload but better integrated with gnome-shell. To install it: sudo apt install gnome-shell-extension-system-monitor To enable it, you need to install gnome-tweak tool: sudo apt install gnome-tweak-tool Then launch it in console by running gnome-tweaks ; then head to the Extensions tab and make sure the System-monitor extension is enabled. You can configure it by pressing the cog-wheel button; I tend to set the Graph width to 40px and Refresh time to 500 for all shown graphs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1714804 Title: Aardvark Daily: Indicator-Multiload doesn't show full-width To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/1714804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714804] Re: Aardvark Daily: Indicator-Multiload doesn't show full-width
You can reset the width using dconf reset /de/mh21/indicator-multiload/general/width -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1714804 Title: Aardvark Daily: Indicator-Multiload doesn't show full-width To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/1714804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756265] [NEW] gnome screencast stops after 30 seconds
Public bug reported: When I start screencast by pressing Alt+Ctrl+Shift+R, it auto-stops itself exactly after 30 seconds. That is highly unexpected, there is no explanation as to why the sudden stop. That leaves me confused as an user. Workaround is to increase the screencast max duration: https://coderwall.com/p/aluafg/gnome-record-desktop-30s-limit ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 08:58:15 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['system-moni...@paradoxxx.zero.gmail.com']" b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'chromium-browser.desktop', 'thunderbird.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2016-09-05 (556 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-13 (2 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1756265 Title: gnome screencast stops after 30 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756265/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755588] Re: ubuntu wayland crashes when I attach secondary monitor
Thank you very much for your quick reply! There are in fact two crash report files: $ ubuntu-bug /var/crash/_usr_bin_Xwayland.1000.crash reported that it's already reported as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1731911 $ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash I've reported this one as https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1755671 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1755588 Title: ubuntu wayland crashes when I attach secondary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755588] Re: ubuntu wayland crashes when I attach secondary monitor
lspci: 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1000M] (rev a2) 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) 3e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1755588 Title: ubuntu wayland crashes when I attach secondary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755588] [NEW] ubuntu wayland crashes when I attach secondary monitor
Public bug reported: I have a notebook with dual graphic cards: Intel+Nvidia (handled by nouveau). The miniDP port is apparently connected to nvidia since it stops working when I use nouveau.modeset=0. I am able to start a Wayland session when there's no secondary monitor connected; as soon as I connect it to miniDP the wayland session crashes and falls back to the greeter. The greeter won't even start Wayland session - it immediately crashes back to the greeter. Workaround is to use the Xorg-based session which works properly with secondary monitor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 22:34:37 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['system-moni...@paradoxxx.zero.gmail.com']" b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'chromium-browser.desktop', 'thunderbird.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2016-09-05 (554 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-13 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1755588 Title: ubuntu wayland crashes when I attach secondary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755588] Re: ubuntu wayland crashes when I attach secondary monitor
syslog ** Attachment added: "syslog.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755588/+attachment/5078582/+files/syslog.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1755588 Title: ubuntu wayland crashes when I attach secondary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1600606] Re: Totem is missing the playlist
The playlist is nowhere to be found in Totem. Apparently it was perceived being too complex by the Gnome guys. The problem is that there are previous/next buttons which apparently navigate through some kind of an invisible playlist, so there is a notion of a playlist. That is extremely confusing to the user - apparently there is a playlist, but it can not be opened/shown, which I perceive as a bug in the UI design. True, it's not Ubuntu, it's upstream. To remove confusion, please either reintroduce playlist, or remove the back/forward buttons. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1600606 Title: Totem is missing the playlist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1600606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
It worked! I switched my machine back to hybrid mode (so that both Intel and Nvidia cards are visible in lspci) and added the nouveau.modeset=0 kernel parameters. And now I am able to select the Ubuntu (wayland) option and indeed it works: XDG_SESSION_TYPE=wayland, and the About dialog shows "Intel® HD Graphics 530 (Skylake GT2)" as the Graphics card. Thanks! So the bug is indeed in gnome-shell. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Daniel, thank you so much for your time investigating this, I appreciate it. The /etc/modprobe.d definitely exists: $ ls -la /etc/modprobe.d/ total 76 drwxr-xr-x 2 root root 4096 okt 23 11:51 . drwxr-xr-x 153 root root 12288 okt 23 11:51 .. -rw-r--r-- 1 root root 2507 júl 31 2015 alsa-base.conf -rw-r--r-- 1 root root 325 mar 13 2016 blacklist-ath_pci.conf -rw-r--r-- 1 root root 1603 mar 13 2016 blacklist.conf -rw-r--r-- 1 root root 210 mar 13 2016 blacklist-firewire.conf -rw-r--r-- 1 root root 697 mar 13 2016 blacklist-framebuffer.conf -rw-r--r-- 1 root root 156 júl 31 2015 blacklist-modem.conf lrwxrwxrwx 1 root root41 sep 5 2016 blacklist-oss.conf -> /lib/linux-sound-base/noOSS.modprobe.conf -rw-r--r-- 1 root root 583 mar 13 2016 blacklist-rare-network.conf -rw-r--r-- 1 root root 1077 mar 13 2016 blacklist-watchdog.conf -rw-r--r-- 1 root root 127 feb 7 2017 dkms.conf -rw-r--r-- 1 root root 154 nov 10 2015 intel-microcode-blacklist.conf -rw-r--r-- 1 root root 347 mar 13 2016 iwlwifi.conf -rw-r--r-- 1 root root 379 júl 28 2016 mdadm.conf -rw-r--r-- 1 root root 104 mar 13 2016 mlx4.conf -rw-r--r-- 1 root root68 dec 28 2015 osspd.conf -rw-r--r-- 1 root root30 mar 3 2016 vmwgfx-fbdev.conf I am typing this from my wayland-enabled session, and the journalctl also contains those lines: okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin kernel: new mount options do not match the existing superblock, will be ignored okt 23 08:41:32 mavi-vaadin anacron[1079]: Will run job `cron.daily' in 5 min. okt 23 08:41:32 mavi-vaadin anacron[1079]: Jobs will be executed sequentially okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin avahi-daemon[1078]: Found user 'avahi' (UID 113) and group 'avahi' (GID 122). okt 23 08:41:32 mavi-vaadin avahi-daemon[1078]: Successfully dropped root privileges. okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin avahi-daemon[1078]: avahi-daemon 0.6.32 starting up. okt 23 08:41:32 mavi-vaadin ModemManager[1080]: ModemManager (version 1.6.8) starting in system bus... okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: /etc/modprobe.d is not a file okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: Error: can't open /lib/modules/4.13.0-16-generic/updates/dkms okt 23 08:41:32 mavi-vaadin gpu-manager[1074]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_ I have the root FS encrypted by LLVM/dmcrypt, and it couldn't have been mounted so soon, since it takes cca 2 seconds to enter my password. Could that be the reason of seeing those error messages? Anyways, since those messages are present and I'm able to run wayland, this leads me to believe that those lines are unconnected to this issue. Anyways, googling for the gnome-shell error message did in fact found something very interesting: https://bugzilla.redhat.com/show_bug.cgi?id=1402283 It seems that even on non-hybrid desktop systems with two completely separate graphic cards gnome-shell seemingly can't find drm kms device (even though there are two of those). So the error message may be misleading, since disabling kms on second card in fact works around this issue. I will try the same and disable KMS on nouveau and let you know. Thanks again for looking into this issue! ** Bug watch added: Red Hat Bugzilla #1402283 https://bugzilla.redhat.com/show_bug.cgi?id=1402283 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4978285/+files/huhu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
** Attachment added: "mutter log 3" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975773/+files/mutter-2156-debug-log-D3L47Y-nokeycode -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Attaching mutter log; but removing lines such as these: KEYBINDINGS: Grabbing keybinding keycode 133 mask 0x0 on 0x15a Since it may reveal my password. ** Attachment added: "mutter log 2" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975772/+files/mutter-1742-debug-log-9BRH8Y-nokeycode -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
** Attachment added: "mutter log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975771/+files/mutter-1662-debug-log-H7DC8Y -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Correction: *those two cards are not completely separate but need to cooperate somehow (since Intel's connected to the panel while Nvidia's connected to HDMI, but they need to cooperate, for example when Intel needs to draw over HDMI when an external monitor is connected) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Thank you for your responses, and I apologize if I sounded rude - I didn't meant to. I rebooted in the hybrid mode and added the abovementioned lines into /etc/environment, unfortunately the /tmp/mutterlogs file is not created. There are other files though: $ ls -la /tmp/mutter* -rw--- 1 gdm gdm 468 okt 19 12:12 /tmp/mutter-1444-debug-log-BN1E8Y -rw--- 1 gdm gdm 77041 okt 19 12:12 /tmp/mutter-1521-debug-log-XFRL8Y -rw--- 1 mavi mavi 493891 okt 19 12:15 /tmp/mutter-1931-debug-log-POR97Y I'm not sure if they would be helpful to you. I have verified that the env variables are indeed set: $ echo $WAYLAND_DEBUG 1 I wondered that the file might be deleted by the auto-cleanup of /tmp, so I created world-writable /foo directory and set MUTTER_USE_LOGFILE=/foo/mutterlogs but nothing got created in /foo. Please let me know if you'd need the contents of those files. Yet they contain nothing wayland-specific: $ sudo cat /tmp/mutter* |grep -i wayl VERBOSE: Using _NET_WM_NAME for new title of 0x3a1 (Bug #17245): "Bug #1724583 “gdm3 in Ubuntu 17.10 doesn't list wayland sessions...” : Bugs : gdm3 package : Ubuntu - Chromium" VERBOSE: Ignoring WM_NAME "Bug #1724583 “gdm3 in Ubuntu 17.10 doesn't list wayland sessions...” : Bugs : gdm3 package : Ubuntu - Chromium" as _NET_WM_NAME is set cat of the first file: $ sudo cat /tmp/mutter-1444-debug-log-BN1E8Y VERBOSE: Mutter version 3.26.1 running on 19.10.2017 VERBOSE: Running in locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=sk_SK.UTF-8;LC_TIME=sk_SK.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=sk_SK.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=sk_SK.UTF-8;LC_NAME=sk_SK.UTF-8;LC_ADDRESS=sk_SK.UTF-8;LC_TELEPHONE=sk_SK.UTF-8;LC_MEASUREMENT=sk_SK.UTF-8;LC_IDENTIFICATION=sk_SK.UTF-8" with encoding "UTF-8" VERBOSE: Compiled with randr extension VERBOSE: Compiled with startup notification Perhaps it is as you say - GDM3 sees two graphic cards, assumes hybrid mode and simply disables Wayland right off the bat; perhaps we will need to wait until Mutter 3.27.1 is released. I was probably wrong: those two cards are not completely separate but need to cooperate somehow (since Intel's connected to the panel while Nvidia's connected to HDMI), and perhaps Mutter needs to do some magic to support that? More info at https://bugzilla.gnome.org/show_bug.cgi?id=785381 ** Bug watch added: GNOME Bug Tracker #785381 https://bugzilla.gnome.org/show_bug.cgi?id=785381 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
I believe this is a bug in GDM3 detection algorithm which incorrectly disables Wayland support on a system which runs just fine with Wayland. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Thanks. I know Wayland+KMS doesn't work with NVIDIA proprietary. However, I don't use NVIDIA proprietary drivers and I don't have them installed and I don't want to use Wayland on NVIDIA proprietary. Thus, your conclusion is not right. When I enable "Hybrid" mode in BIOS, I believe that both VGA cards (Intel and Nvidia) are made available to the system (as shown by dmesg); OS is free to use any of those. Typically Linux only uses Intel and ignores Nvidia in this mode - that is completely fine and that's what I want - to run Wayland on top of Intel. The problem is that Wayland doesn't work with the Intel-based graphic card for me, on this very laptop when both video cards are visible. Or perhaps GDM3 detects more than one graphic card and disables Wayland support. Or perhaps GDM3 detects Skylake Intel chipset and disables Wayland support. I don't know - GDM3 logs nothing usable to its log even when in debug mode, so it is unclear what is the reason behind disabling Wayland support. To sum it up: I want to use Wayland on Intel, but GDM3 won't allow me to do so, and it doesn't provide any hints as to why. KDE Plasma on Wayland *RUNS FINE* on this very configuration. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Thanks for the info on Hybrid mode - really nice! However, what I'd like is to run Ubuntu+Wayland on my Intel card only. So, I don't want to run it in hybrid mode, I don't want to run it on NVIDIA proprietary, just on the Intel card. KDE Plasma+Wayland runs fine and uses Intel only; GDM3 forces me to use Xorg for unknown reason. The only workaround is to "set the Discrete mode in BIOS" which only hides Intel card; then GDM3 allows me to run Wayland (on top of Nouveau). Works for me; yet I would still prefer to use just the Intel+Wayland configuration. Please, let me know how I can make myself more clear. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 doesn't list wayland-based sessions
I have switched to the Hybrid mode. Now the only session available is the Xorg-based session; About dialog shows that the Intel® HD Graphics 530 (Skylake GT2) is now being used. Could it be that it is not compatible with Wayland? Anyway, attaching the lspci -k of the Hybrid mode. In the hybrid mode, the Intel graphics is now available: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) Subsystem: Lenovo HD Graphics 530 Kernel driver in use: i915 Kernel modules: i915 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 doesn't list wayland-based sessions on Intel® HD Graphics 530 (Skylake GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 doesn't list wayland-based sessions
** Attachment added: "lspci -k of the Hybrid mode" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975632/+files/lsp_hybrid ** Summary changed: - gdm3 doesn't list wayland-based sessions + gdm3 doesn't list wayland-based sessions on Intel® HD Graphics 530 (Skylake GT2) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 doesn't list wayland-based sessions on Intel® HD Graphics 530 (Skylake GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 doesn't list wayland-based sessions
I actually have a nvidia card, and since I switched to Discrete mode in BIOS, Wayland session works properly; moreover it seems to be working on top of Nouveau (the About dialog says that Graphics is NV117). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 doesn't list wayland-based sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 doesn't list wayland-based sessions
** Attachment added: "lspci -k" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975580/+files/lsp -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 doesn't list wayland-based sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm3 doesn't list wayland-based sessions
*** This bug is a duplicate of bug 1723577 *** https://bugs.launchpad.net/bugs/1723577 Solved! I went to BIOS and switched the Video card setting from Hybrid to Discrete. Now gdm3 offered the wayland option (or, rather, both "Ubuntu" and "Ubuntu on Xorg"). I now run Wayland as confirmed by env|grep wayland: XDG_SESSION_TYPE=wayland I believe that nouveau driver is actually being used, so I need to look into the possibility to force Intel, to achieve better support. Anyways, it seems that Hybrid mode won't pass gdm3 validation routines and it disables Wayland support; switching to Discrete solves the issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 doesn't list wayland-based sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm no wayland
*** This bug is a duplicate of bug 1723577 *** https://bugs.launchpad.net/bugs/1723577 ** Attachment added: "Output of journalctl -u gdm.service" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975011/+files/gdm.log ** Summary changed: - gdm no wayland + gdm3 doesn't list wayland-based sessions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 doesn't list wayland-based sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm no wayland
*** This bug is a duplicate of bug 1723577 *** https://bugs.launchpad.net/bugs/1723577 I disagree about the duplicate status. This bug: gdm3 itself starts in Wayland successfully, but it doesn't list the wayland sessions (it only lists the xorg-based sessions). The bug #1723577 is that gdm3 won't even start and needs to be reconfigured to start in Xorg mode. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm3 doesn't list wayland-based sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm no wayland
*** This bug is a duplicate of bug 1723577 *** https://bugs.launchpad.net/bugs/1723577 Attaching my /etc/gdm3/custom.conf: ** Attachment added: "custom.conf" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4974887/+files/custom.conf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm no wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm no wayland
I enabled the debug logs for gdm3 in /etc/gdm3/custom.conf, but the logs are nowhere to be found: /var/log/gdm3 is empty. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm no wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] [NEW] gdm no wayland
Public bug reported: I've just upgraded to Ubuntu 17.10 and switched the login manager from sddm to gdm3. Unfortunately it doesn't list the -wayland sessions. The /usr/share/xsessions folder indeed only contains the -xorg -related sessions: $ ls -la /usr/share/xsessions total 36 drwxr-xr-x 2 root root 4096 okt 18 16:00 . drwxr-xr-x 427 root root 20480 okt 18 15:56 .. -rw-r--r-- 1 root root 201 okt 13 12:56 gnome-xorg.desktop -rw-r--r-- 1 root root 2354 aug 23 16:39 plasma.desktop -rw-r--r-- 1 root root 262 okt 13 12:56 ubuntu-xorg.desktop How can I enable the ubuntu-wayland session please? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 16:37:47 2017 InstallationDate: Installed on 2016-09-05 (408 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm no wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724583] Re: gdm no wayland
Hm, there actually is /usr/share/wayland-sessions/ubuntu.desktop - could it be that gdm3 for some reason ignores this folder? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1724583 Title: gdm no wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1682435] [NEW] Slovak qwerty keyboard: pressing =a in kwrite should produce á yet it produces a
Public bug reported: Since ibus did not work for me (it ignored any configured layout and always used english) I tried to install fcitx as a workaround. Fcitx works, yet I am not able to type in á by pressing = and a, only by pressing the "8" key. Yet this only apparently applies to KDE applications such as kwrite and konsole - apparently OpenOffice Writer nor Chromium is unaffected by this bug and correctly responds to =a by typing in á. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: fcitx 1:4.2.9.1-6 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 13 16:33:47 2017 InstallationDate: Installed on 2016-09-05 (220 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: fcitx UpgradeStatus: Upgraded to zesty on 2017-03-31 (13 days ago) ** Affects: fcitx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fcitx in Ubuntu. https://bugs.launchpad.net/bugs/1682435 Title: Slovak qwerty keyboard: pressing =a in kwrite should produce á yet it produces a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1682435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636406] [NEW] UnknownMethod DescribeAll
Public bug reported: Running gedit with -s -w fails: $ gedit -s -w bla.txt Failed to register: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "DescribeAll" with signature "" on interface "org.gtk.Actions" doesn't exist Omitting the -w parameter however works correctly and the calling process is blocked, so perhaps the -w parameter is no longer needed? Anyway, just wanted you to know that -w is borked. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gedit 3.22.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 25 11:25:15 2016 InstallationDate: Installed on 2016-09-05 (49 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gedit UpgradeStatus: Upgraded to yakkety on 2016-09-30 (24 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1636406 Title: UnknownMethod DescribeAll To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1636406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1525939] Re: trash bin shown non-empty, yet there are no files in the trash
** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1525939/+attachment/4534531/+files/Screenshot%20from%202015-12-14%2015-39-57.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1525939 Title: trash bin shown non-empty, yet there are no files in the trash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1525939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1525939] [NEW] trash bin shown non-empty, yet there are no files in the trash
Public bug reported: The trash bin icon is shown as containing files, yet the nautilus Trash window shows no files. The "Empty" button is enabled though. When pressed, the confirm dialog is shown - upon confirming, nothing is done though - the nautilus Trash still shows no files, the "Empty" button stays enabled and the Unity trash bin icon stays full. Attaching screenshot of the issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 14 15:38:46 2015 GsettingsChanges: InstallationDate: Installed on 2014-03-07 (646 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) SourcePackage: nautilus UpgradeStatus: Upgraded to wily on 2015-10-08 (67 days ago) usr_lib_nautilus: evince 3.16.1-0ubuntu1 file-roller3.16.4-1ubuntu3 gnome-terminal 3.16.2-1ubuntu4 nautilus-share 0.7.3-1ubuntu5 totem 3.16.4-0ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1525939 Title: trash bin shown non-empty, yet there are no files in the trash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1525939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1509079] Re: logging in to gnome wayland show blank screen and lightdm is restarted
** Attachment added: "lightdm.log" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1509079/+attachment/4502628/+files/lightdm.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1509079 Title: logging in to gnome wayland show blank screen and lightdm is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1509079/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1509079] [NEW] logging in to gnome wayland show blank screen and lightdm is restarted
Public bug reported: I select the Gnome on Wayland login option, then type my password in and press Enter. A blank screen with a blinking cursor appears, and then I am thrown back into the lightdm login screen, without any error message. I am attaching the lightdm.log which has some intriguing error messages. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-session-wayland 3.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 ApportVersion: 2.19.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Thu Oct 22 22:06:22 2015 InstallationDate: Installed on 2013-08-17 (796 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) SourcePackage: gnome-session UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1509079 Title: logging in to gnome wayland show blank screen and lightdm is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1509079/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1479054] Re: Shuffle and repeat buttons pressed state does not visually differ from unpressed state
Even on close zoom, I cannot tell which screenshot shows pressed buttons and which screenshot shows unpressed buttons. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1479054 Title: Shuffle and repeat buttons pressed state does not visually differ from unpressed state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1479054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1479054] Re: Shuffle and repeat buttons pressed state does not visually differ from unpressed state
** Attachment added: Screenshot from 2015-07-28 18:53:59.png https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1479054/+attachment/4435272/+files/Screenshot%20from%202015-07-28%2018%3A53%3A59.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1479054 Title: Shuffle and repeat buttons pressed state does not visually differ from unpressed state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1479054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1479054] [NEW] Shuffle and repeat buttons pressed state does not visually differ from unpressed state
Public bug reported: In the default Ubuntu theme, the pressed/activated and deactivated button states are very similar and hard to differ. It is therefore hard to tell from the first look, if the shuffle is enabled or not. I am attaching the screenshots. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: rhythmbox 3.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2 Uname: Linux 3.19.0-23-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 28 18:47:08 2015 InstallationDate: Installed on 2013-08-17 (710 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) SourcePackage: rhythmbox UpgradeStatus: Upgraded to vivid on 2015-05-02 (87 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid ** Attachment added: Screenshot from 2015-07-28 18:51:06.png https://bugs.launchpad.net/bugs/1479054/+attachment/4435265/+files/Screenshot%20from%202015-07-28%2018%3A51%3A06.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1479054 Title: Shuffle and repeat buttons pressed state does not visually differ from unpressed state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1479054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 979445] Re: Brasero should not be on default ubuntu
I just tried to burn a simple flacs to an audio CD, Brasero managed to screw first disk completely, burn a 25 minutes of silence on another, and then started to produce undecipherable messages like impossible to link to plugin pads or whatever. Afterwards, it only produced messages like Cannot eject disk and Disk already mounted and similar nonsense. Uninstalled brasero, installed k3b and voila, I have my CD Audio on first run. Please replace Brasero with anything. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/979445 Title: Brasero should not be on default ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/979445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1383197] [NEW] eog half of the time freezes when pressing F11
Public bug reported: Since upgrade to Utopic, pressing F11 in eog would cause sometimes eog to freeze (the eog window goes blackwhite, the Program stopped responding dialog pops out) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: eog 3.12.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 20 10:58:56 2014 InstallationDate: Installed on 2014-03-07 (226 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) SourcePackage: eog UpgradeStatus: Upgraded to utopic on 2014-10-16 (3 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1383197 Title: eog half of the time freezes when pressing F11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1383197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1234665] [NEW] hide all normal windows custom key binding is ignored
Public bug reported: Good day, I tried to set Ctrl+Alt+D as my custom key binding to the All Settings / Keyboard / Shortcuts / Navigation / Hide all normal windows setting. The setting is accepted, however the setting is ignored and nothing happens when I press Ctrl+Alt+D - Ctrl+Win+D continues to work. I am attaching a screenshot of the setting. Thank you. This is kind of weird because my other custom key bindings (prev/next song, launch terminal with Shift+F2 etc) are working correctly. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu41 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Thu Oct 3 13:27:56 2013 InstallationDate: Installed on 2013-08-03 (60 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release i386 (20130423.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-02 (0 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130930-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy ** Attachment added: keyboard settings screenshot https://bugs.launchpad.net/bugs/1234665/+attachment/3857268/+files/Screenshot%20from%202013-10-03%2013%3A33%3A59.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1234665 Title: hide all normal windows custom key binding is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1234665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1234665] Re: hide all normal windows custom key binding is ignored
What is worse, the keyboard layout switch button does not work: the default value is Win+Space which does not work. I tried to set it to Alt+LShift but it does not work either. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1234665 Title: hide all normal windows custom key binding is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1234665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1220550] [NEW] gnome-keyring resets password
Public bug reported: Good day :) I have Ubuntu installed on an encrypted LVM partition, with user auto-login and an empty gnome-keyring password (I believe that an empty gnome-keyring password on an encrypted LVM is safe... is it? :). Every 5th or 6th boot (I don't know exact number) the gnome-keyring dialog pops out and asks me for a password. It no longer accepts empty password. I tried to set the password to some non-empty string (a or something like that), it again worked for several boots, then again started to ask for the password. I have to enter the user's password for the dialog to disappear. So it seems to me that something is (randomly?) resetting the gnome-keyring password to match the login password. Thanks and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-keyring 3.6.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Wed Sep 4 09:02:11 2013 InstallationDate: Installed on 2013-08-03 (31 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release i386 (20130423.1) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1220550 Title: gnome-keyring resets password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1220550/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168371] Re: incoming messages not opened in a window
After a reboot, the conversation windows start to pop up correctly. Weird. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1168371 Title: incoming messages not opened in a window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168371] [NEW] incoming messages not opened in a window
Public bug reported: Today I upgraded to Ubuntu 13.04. Since the upgrade, Empathy stopped to open conversations in a window - the incoming message is shown as a notification, but the envelope applet icon stays white (does not turn to blue) and no conversation window is popped up. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic i686 ApportVersion: 2.9.2-0ubuntu7 Architecture: i386 Date: Fri Apr 12 13:25:35 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-05-17 (1061 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to raring on 2013-04-12 (0 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1168371 Title: incoming messages not opened in a window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1053658] Re: Automatic Contacts feature went missing (via bbdb e-plugin)
After Google changed the paradigm of mail address auto-completion by auto-completing mail addresses from all your mails, the concept of an address book became obsolete. It is a pity that Evolution still clings to this deprecated concept. The Automatic Contacts feature is at most a half-step towards Google-style auto-completion, however it's better than nothing. It is strange that this basic functionality is not embedded in the core of Evolution, but it is rather a plugin. When this plugin went missing, Evolution mail address auto-completion became useless. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1053658 Title: Automatic Contacts feature went missing (via bbdb e-plugin) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1053658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069531] Re: Cannot login to Empathy after setting up Google online account
Each time I boot up my computer, Empathy shows that Google account requires registration. However, the Online Accounts System Setting window does not show registration being required. when I select the Available option from the drop down list a few times, Empathy eventually is able to connect to Google. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1069531 Title: Cannot login to Empathy after setting up Google online account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1069531/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)
It somehow seems that Unity 2D does not trigger this bug. However, I have recently switched to Unity 3D with Compiz and the problem manifested again. Ubuntu 12.04 x86-32, fully updated -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
This should probably be closed: I reinstalled from the Maverick Desktop install CD and everything works okay. Also, I upgraded to Maverick on three other computers and all are working correctly. Perhaps some weird setting on my side. Thanks anyways, and keep up a good work! -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] [NEW] gnome does not start and restarts gdm back to login screen
Public bug reported: Binary package hint: gdm Hello, can you please help me? After upgrading to Maverick on Linux yuzuki 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linux from a fully updated Lucid, the Gnome session no longer starts. I click on the user name, enter my password, then the GDM restarts back to the login screen, while briefly showing TTY1. There is no error in Xorg.0.log, although there are some suspicious entries in Xorg.1.log.old, attaching. I also tried to obtain crash report with apport, however apport states that there is no crash report available. I am also attaching gdm logs, just in case. I am now running X with sudo startx. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
Xorg.1.log.old ** Attachment added: Xorg.1.log.old https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/656017/+attachment/1676008/+files/Xorg.1.log.old -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
** Attachment added: :0.log https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/656017/+attachment/1676009/+files/%3A0.log -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
** Attachment added: :0.log.1 https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/656017/+attachment/1676010/+files/%3A0.log.1 -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
** Attachment added: :0.log.2 https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/656017/+attachment/1676011/+files/%3A0.log.2 -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
** Attachment added: :0.log.4 https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/656017/+attachment/1676012/+files/%3A0.log.4 -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
** Attachment added: :0.log.3 https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/656017/+attachment/1676013/+files/%3A0.log.3 -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
# cat \:0-slave.log* gdm-session-worker[7754]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed gdm-session-worker[7754]: pam_succeed_if(gdm:auth): requirement user ingroup nopasswdlogin not met by user vyzivus gdm-session-worker[7754]: pam_sm_authenticate: Called gdm-session-worker[7754]: pam_sm_authenticate: username = [vyzivus] gdm-session-worker[7754]: pam_sm_authenticate: /home/vyzivus is already mounted gdm-session-worker[7754]: pam_unix(gdm:session): session opened for user vyzivus by (uid=0) gdm-session-worker[7754]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0 gdm-session-worker[7754]: pam_unix(gdm:session): session closed for user vyzivus Sessions still open, not unmounting gdm-session-worker[6883]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed gdm-session-worker[6883]: pam_succeed_if(gdm:auth): requirement user ingroup nopasswdlogin not met by user vyzivus gdm-session-worker[6883]: pam_sm_authenticate: Called gdm-session-worker[6883]: pam_sm_authenticate: username = [vyzivus] gdm-session-worker[6883]: pam_sm_authenticate: /home/vyzivus is already mounted gdm-session-worker[6883]: pam_unix(gdm:session): session opened for user vyzivus by (uid=0) gdm-session-worker[6883]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0 gdm-session-worker[6883]: pam_unix(gdm:session): session closed for user vyzivus Sessions still open, not unmounting -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
** Attachment added: :0-greeter.log https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/656017/+attachment/1676024/+files/%3A0-greeter.log -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
# cat \:0-greeter.log* ** (process:7876): DEBUG: Greeter session pid=7876 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-b6BFi0/database gdm-simple-greeter[7876]: Gtk-WARNING: /build/buildd/gtk+2.0-2.22.0/gtk/gtkwidget.c:5684: widget not within a GtkWindow Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. gdm-simple-greeter[7876]: WARNING: Unable to parse history: (null) 13 Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. ** (process:7752): DEBUG: Greeter session pid=7752 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-Sp5akw/database gdm-simple-greeter[7752]: Gtk-WARNING: /build/buildd/gtk+2.0-2.22.0/gtk/gtkwidget.c:5684: widget not within a GtkWindow Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. gdm-simple-greeter[7752]: WARNING: Unable to parse history: (null) 13 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. ** (process:7005): DEBUG: Greeter session pid=7005 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-MAYaMT/database gdm-simple-greeter[7005]: Gtk-WARNING: /build/buildd/gtk+2.0-2.22.0/gtk/gtkwidget.c:5684: widget not within a GtkWindow Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. gdm-simple-greeter[7005]: WARNING: Unable to parse history: (null) 13 gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'. gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. gnome-power-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. ** (process:7028): DEBUG: Greeter session pid=7028 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-MAYaMT/database gdm-simple-greeter[7028]: Gtk-WARNING: cannot open display: :0.0 ** (process:6881): DEBUG: Greeter session pid=6881 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-NlBU8l/database gdm-simple-greeter[6881]: Gtk-WARNING: /build/buildd/gtk+2.0-2.22.0/gtk/gtkwidget.c:5684: widget not within a GtkWindow Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. gdm-simple-greeter[6881]: WARNING: Unable to parse history: (null) 13 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1200034 (Login Wind) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
[Bug 656017] Re: gnome does not start and restarts gdm back to login screen
** Attachment added: :0-greeter.log.1 https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/656017/+attachment/1676025/+files/%3A0-greeter.log.1 -- gnome does not start and restarts gdm back to login screen https://bugs.launchpad.net/bugs/656017 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 560964] [NEW] evolution crashed with SIGSEGV in indicate_indicator_get_property()
Public bug reported: Binary package hint: evolution Dear Ubuntu maintainers, I'm using a fully updated Lucid Lynx, having evolution 2.28.3-0ubuntu8. The bug occurs randomly, so I cannot reproduce it easily. The bug occurs very infrequently. Thanks! ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: evolution 2.28.3-0ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 Architecture: i386 Date: Sun Apr 11 22:17:54 2010 Disassembly: = 0xc:Cannot access memory at address 0xc EcryptfsInUse: Yes ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318) ProcCmdline: evolution ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xc: Cannot access memory at address 0xc PC (0x000c) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () indicate_indicator_get_property () org_gnome_mail_read_notify () ?? () from /usr/lib/evolution/2.28/libeutil.so.0 e_plugin_invoke () Title: evolution crashed with SIGSEGV in indicate_indicator_get_property() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (polkit-gnome-authentication-agent-1:1242): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-panel:1244): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x9d1eb68 (gnome-panel:1244): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x9d1eb68 (gnome-terminal:1452): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL entry-lock_count 0' failed (gnome-terminal:1749): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL entry-lock_count 0' failed ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 lucid -- evolution crashed with SIGSEGV in indicate_indicator_get_property() https://bugs.launchpad.net/bugs/560964 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 560964] Re: evolution crashed with SIGSEGV in indicate_indicator_get_property()
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43853875/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/43853876/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/43853877/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/43853878/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/43853879/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/43853880/ThreadStacktrace.txt -- evolution crashed with SIGSEGV in indicate_indicator_get_property() https://bugs.launchpad.net/bugs/560964 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544299] Re: the view previous conversations menu item cannot be assigned a keyboard shortcut
Thanks for your response. Created the GNOME bug report: https://bugzilla.gnome.org/show_bug.cgi?id=613665 ** Bug watch added: GNOME Bug Tracker #613665 https://bugzilla.gnome.org/show_bug.cgi?id=613665 -- the view previous conversations menu item cannot be assigned a keyboard shortcut https://bugs.launchpad.net/bugs/544299 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544299] [NEW] the view previous conversations menu item cannot be assigned a keyboard shortcut
Public bug reported: Binary package hint: empathy With Pidgin I was used to open the conversation history with CTRL+L. This shortcut is assigned to the Clear action in Empathy. I tried to reassign the shortcut: I was able to remove the shortcut from the Clear menu item, but I cannot set any shortcut to the Contact View Previous Conversations. The GNOME Editable menu shortcut keys option is enabled. I'm on fully updated Ubuntu 9.10, empathy is 2.28.1.1-0ubuntu1. Thanks! ProblemType: Bug Architecture: amd64 Date: Mon Mar 22 17:27:47 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/empathy Package: empathy 2.28.1.1-0ubuntu1 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-20.58-generic SourcePackage: empathy Uname: Linux 2.6.31-20-generic x86_64 ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- the view previous conversations menu item cannot be assigned a keyboard shortcut https://bugs.launchpad.net/bugs/544299 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 544299] Re: the view previous conversations menu item cannot be assigned a keyboard shortcut
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/41624017/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/41624018/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/41624019/ProcStatus.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/41624020/XsessionErrors.txt -- the view previous conversations menu item cannot be assigned a keyboard shortcut https://bugs.launchpad.net/bugs/544299 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 426421] Re: Can't play text file without video on opening mkv file
This bug is present in final Karmic as well. -- Can't play text file without video on opening mkv file https://bugs.launchpad.net/bugs/426421 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 178698] Re: IMAP and weird characters in name field
Thank you for the tip! I switched to Jaunty and I no longer see the messed names in the name field. I also remember that the bug disappeared from Intrepid's Evolution (I don't know when though). -- IMAP and weird characters in name field https://bugs.launchpad.net/bugs/178698 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 147148] Feature request: Add sessionsaver extension
Public bug reported: Quite an essential extension (at least for me), unfortunately an unofficial one. There is howto at http://blog.cybernotic.org/?p=20 - is there a chance of this extension added to gutsy or should I compile it myself? ** Affects: epiphany-extensions (Ubuntu) Importance: Undecided Status: New -- Feature request: Add sessionsaver extension https://bugs.launchpad.net/bugs/147148 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for epiphany-extensions in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
