[Desktop-packages] [Bug 1825651] Re: Transmission freezes when adding second magnet in Ubuntu 19.04
I don't use any non default option. I remember this problem suddenly happened to me one day during the time of ubuntu 19.04 beta and it's still there when I freshly installed ubuntu 19.04 stable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1825651 Title: Transmission freezes when adding second magnet in Ubuntu 19.04 Status in transmission package in Ubuntu: New Bug description: Step to reproduce: 1. Open browser 2. Click a magnet link 3. Choose to use transmission 4. Choose folder 5. OK 6. Open another magnet link 7. Choose folder --> It freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1825651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825651] Re: Transmission freezes when adding second magnet in Ubuntu 19.04
This is the output after (gdb) t a a bt: Thread 13 (Thread 0x7fffcdffb700 (LWP 7985)): #0 0x76bc4729 in __GI___poll (fds=0x55f4b270, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x77426cb6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x77426ddc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x77fc5ffd in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4 0x7744f98d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x76ca7182 in start_thread (arg=) at pthread_create.c:486 #6 0x76bd0b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fffceffd700 (LWP 7983)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x77471b9a in g_cond_wait_until () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x773f80c1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x773f8681 in g_async_queue_timeout_pop () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x774503f1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 --Type for more, q to quit, c to continue without paging-- #5 0x7744f98d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x76ca7182 in start_thread (arg=) at pthread_create.c:486 #7 0x76bd0b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fffc700 (LWP 7972)): #0 0x76bc4729 in __GI___poll (fds=0x7fffc8007080, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffe08359f1 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fffe0827260 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fffe08278ae in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fffe0827960 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fffe0835939 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fffe07d5788 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #7 0x76ca7182 in start_thread (arg=) at pthread_create.c:486 #8 0x76bd0b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 --Type for more, q to quit, c to continue without paging-- Thread 6 (Thread 0x7fffe3fff700 (LWP 7969)): #0 0x76cb1440 in __GI___nanosleep (requested_time=0x7fffe3ffe800, remaining=0x0) at ../sysdeps/unix/sysv/linux/nanosleep.c:28 #1 0x555b5c66 in tr_wait_msec () #2 0x555b2772 in ?? () #3 0x5559f63a in ?? () #4 0x76ca7182 in start_thread (arg=) at pthread_create.c:486 #5 0x76bd0b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x70b4f700 (LWP 7968)): #0 0x76bd0e3f in epoll_wait (epfd=12, events=0x7fffdc000e20, maxevents=32, timeout=39) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x771b02c5 in ?? () from /lib/x86_64-linux-gnu/libevent-2.1.so.6 #2 0x771a6114 in event_base_loop () from /lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x555b4b48 in ?? () #4 0x5559f63a in ?? () #5 0x76ca7182 in start_thread (arg=) at pthread_create.c:486 #6 0x76bd0b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:--Type for more, q to quit, c to continue without paging-- 95 Thread 4 (Thread 0x71a3f700 (LWP 7967)): #0 0x76bc4729 in __GI___poll (fds=0x7fffe802bbb0, nfds=8, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x77426cb6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x77427042 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x77662c76 in ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7744f98d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x76ca7182 in start_thread (arg=) at pthread_create.c:486 #6 0x76bd0b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x72a41700 (LWP 7965)): #0 0x76bc4729 in __GI___poll (fds=0x55659cc0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x77426cb6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x77426ddc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x77426e21 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7744f98d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 --Type for more, q to quit, c to continue without paging-- #5 0x76ca7182 in start_thread (arg=) at pthread_create.c:486 #6 0x76bd0b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x73ae7cc0 (LWP 7960)): #0 0x76bc4729 in __GI___poll (fds=0x55c71920, nfds=5, timeout=969) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x77426cb6 in ?? () from
[Desktop-packages] [Bug 1825651] Re: Transmission freezes when adding second magnet in Ubuntu 19.04
This is the video of the whole process in case you need it. ** Attachment added: "bug-2019-05-06_21.33.06.mp4" https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1825651/+attachment/5261896/+files/bug-2019-05-06_21.33.06.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1825651 Title: Transmission freezes when adding second magnet in Ubuntu 19.04 Status in transmission package in Ubuntu: Incomplete Bug description: Step to reproduce: 1. Open browser 2. Click a magnet link 3. Choose to use transmission 4. Choose folder 5. OK 6. Open another magnet link 7. Choose folder --> It freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1825651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825651] Re: Transmission freezes when adding second magnet in Ubuntu 19.04
This is the backtrace of the bug. ** Attachment added: "Backtrace" https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1825651/+attachment/5261895/+files/gdb-transmission.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1825651 Title: Transmission freezes when adding second magnet in Ubuntu 19.04 Status in transmission package in Ubuntu: Incomplete Bug description: Step to reproduce: 1. Open browser 2. Click a magnet link 3. Choose to use transmission 4. Choose folder 5. OK 6. Open another magnet link 7. Choose folder --> It freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1825651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825651] Re: Transmission freezes when adding second magnet in Ubuntu 19.04
The issue seems to only appear when directly clicking link from browser. You can go to https://nyaa.si/ in the "Link" column, there's U-like symbols, those are magnet link. Just click it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1825651 Title: Transmission freezes when adding second magnet in Ubuntu 19.04 Status in transmission package in Ubuntu: New Bug description: Step to reproduce: 1. Open browser 2. Click a magnet link 3. Choose to use transmission 4. Choose folder 5. OK 6. Open another magnet link 7. Choose folder --> It freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1825651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825651] Re: Transmission freezes when adding second magnet in Ubuntu 19.04
Magnet link is a kind of torrent without the need of downloading a torrent file (you just add link and it starts downloading). I tried to use journalctl and this seems to be where the problem is: Thg 4 24 19:13:32 DINGO transmission-gt[3579]: g_object_set_data: assertion 'G_IS_OBJECT (object)' failed Thg 4 24 19:13:32 DINGO transmission-gt[3579]: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Thg 4 24 19:13:32 DINGO transmission-gt[3579]: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed Thg 4 24 19:13:32 DINGO transmission-gt[3579]: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed Thg 4 24 19:13:32 DINGO transmission-gt[3579]: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1825651 Title: Transmission freezes when adding second magnet in Ubuntu 19.04 Status in transmission package in Ubuntu: Incomplete Bug description: Step to reproduce: 1. Open browser 2. Click a magnet link 3. Choose to use transmission 4. Choose folder 5. OK 6. Open another magnet link 7. Choose folder --> It freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1825651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825651] [NEW] Transmission freezes when adding second magnet in Ubuntu 19.04
Public bug reported: Step to reproduce: 1. Open browser 2. Click a magnet link 3. Choose to use transmission 4. Choose folder 5. OK 6. Open another magnet link 7. Choose folder --> It freezes ** Affects: transmission (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1825651 Title: Transmission freezes when adding second magnet in Ubuntu 19.04 Status in transmission package in Ubuntu: New Bug description: Step to reproduce: 1. Open browser 2. Click a magnet link 3. Choose to use transmission 4. Choose folder 5. OK 6. Open another magnet link 7. Choose folder --> It freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1825651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822402] Re: gnome calendar automatically moves event back 1 day
I don't really understand your question so I recorded the steps to reproduce the bug. Please note that no matter the event is 'personal' or sync with gmail, this bug still happens. ** Attachment added: "Steps to reproduce" https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1822402/+attachment/5253050/+files/calendar_bug-2019-04-05_18.34.24.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1822402 Title: gnome calendar automatically moves event back 1 day Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Step to reproduce: 1. Create an all day event 2. Set it to repeat monthly --> Surprise, it goes back one day Additional information: Time belt: GMT+7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1822402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822402] Re: gnome calendar automatically moves event back 1 day
The latest Ubuntu 19.04 beta and Calendar 3.32.0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1822402 Title: gnome calendar automatically moves event back 1 day Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Step to reproduce: 1. Create an all day event 2. Set it to repeat monthly --> Surprise, it goes back one day Additional information: Time belt: GMT+7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1822402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822775] [NEW] Different input sources per window not work
Public bug reported: Ubuntu 19.04 The option to apply different input source for each window doesn't work (it automatically reset itself) However, I manually change org.gnome.desktop.input-sources.per-window and it works. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1822775 Title: Different input sources per window not work Status in ibus package in Ubuntu: New Bug description: Ubuntu 19.04 The option to apply different input source for each window doesn't work (it automatically reset itself) However, I manually change org.gnome.desktop.input-sources.per-window and it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1822775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822402] [NEW] gnome calendar automatically moves event back 1 day
Public bug reported: Step to reproduce: 1. Create an all day event 2. Set it to repeat monthly --> Surprise, it goes back one day Additional information: Time belt: GMT+7 ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1822402 Title: gnome calendar automatically moves event back 1 day Status in gnome-calendar package in Ubuntu: New Bug description: Step to reproduce: 1. Create an all day event 2. Set it to repeat monthly --> Surprise, it goes back one day Additional information: Time belt: GMT+7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1822402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737979] [NEW] Wayland freezes with matplotlib
Public bug reported: Steps to reproduce problem: _ Using python and matplotlib to plot something _ When the plot appears, move the mouse to save icon _ Boom, it's freezed Wait several minutes for it to start moving again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 20:45:02 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:13dd] InstallationDate: Installed on 2017-11-03 (39 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. X451CAP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X451CAP.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X451CAP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX451CAP.203:bd02/18/2014:svnASUSTeKCOMPUTERINC.:pnX451CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX451CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X451CAP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful false-gpu-hang freeze ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1737979 Title: Wayland freezes with matplotlib Status in xorg package in Ubuntu: New Bug description: Steps to reproduce problem: _ Using python and matplotlib to plot something _ When the plot appears, move the mouse to save icon _ Boom, it's freezed Wait several minutes for it to start moving again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 20:45:02 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:13dd] InstallationDate: Installed on 2017-11-03 (39 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. X451CAP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X451CAP.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X451CAP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 1734021] [NEW] No volume icon
Public bug reported: Newly install ubuntu 17.10, everthing is default but there's no volume icon in rhythmbox (with both wayland and xorg). I removed the rhythmbox- plugin-alternative-toolbar and the volume icon returned. It seems like this is a problem with new interface. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 11:01:30 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:13dd] InstallationDate: Installed on 2017-11-03 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. X451CAP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X451CAP.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X451CAP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX451CAP.203:bd02/18/2014:svnASUSTeKCOMPUTERINC.:pnX451CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX451CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X451CAP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1734021 Title: No volume icon Status in xorg package in Ubuntu: New Bug description: Newly install ubuntu 17.10, everthing is default but there's no volume icon in rhythmbox (with both wayland and xorg). I removed the rhythmbox-plugin-alternative-toolbar and the volume icon returned. It seems like this is a problem with new interface. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 11:01:30 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:13dd] InstallationDate: Installed on 2017-11-03 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. X451CAP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X451CAP.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X451CAP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 1581713] Re: Ubuntu Software asks for an Ubuntu Single Sign-On account to install/remove a snap
** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => DO TU TOAN (dotutoan) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1581713 Title: Ubuntu Software asks for an Ubuntu Single Sign-On account to install/remove a snap Status in Ubuntu GNOME: Triaged Status in gnome-software package in Ubuntu: Triaged Status in snapd package in Ubuntu: Confirmed Bug description: If I try to uninstall a snap using Ubuntu Software, it asks for an Ubuntu Single Sign-On account. It seems strange since if I use a terminal and do: $ sudo snap remove john-the-ripper Everything works as expected. BTW: Ubuntu Software takes ages to find out the size of the snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1581713/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1400856] Re: GLib-GObject-CRITICAL
I compile glib library from source and I learn that if optimization (-Os -O1 or -O2) was turned on during compilation, particularly when compiling gobject/gobject.c from glib, can lead to many strange behaviors and errors. If for somehow, you can try to recompile glib without optimation and see if the error goes away. thanks TP -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1400856 Title: GLib-GObject-CRITICAL Status in glib2.0 package in Ubuntu: Invalid Bug description: screen blinks or something like that and i get error (anjuta:30976): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed (anjuta:30976): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libglib2.0-0 2.40.2-0ubuntu1 Uname: Linux 3.18.0-031800-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Dec 9 21:08:48 2014 InstallationDate: Installed on 2014-12-01 (8 days ago) InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1400856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262275] Re: Crash on display change after resuming from suspend
I also have the same symptom when upgraded to this driver. My machine is: Intel I7 920 Asus X58 Motherboard GTX460 nvidia graphic card After a resume, i noticed that everything looks fine. (since i have dual monitor), i could work on the first monitor (monitor to the left), but as soon as i move my mouse cursor the second monitor, Xorg service locked up. I then ssh*ed* into the PC and attached a debugger to the Xorg process, the stack trace showed that it was running code inside the nvidia driver and never returned. CPU consumption at this point was 100% Please let me know if you need me to run any test scenarios; this buy is very easy to replicate on my PC. Just put it to sleep on RAM, and on the next resume, Xorg would lockup when the mouse cursor is moved on the second monitor. thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1262275 Title: Crash on display change after resuming from suspend Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Bug description: Every time I put my laptop on suspend, then resume it, I get an xorg crash every time I try to change the display. It doesn't matteri if I try from a secondary display to the primary or vice versa, or from a dual display to a single display setup. When I ask for a display change, both displays go black, and the hard disk LED shows a lot of activity. This lasts around 20 or 30 seconds, then xorg crashes. I have to shut down and restart the computer before I can successfully switch displays again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu7 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Wed Dec 18 17:27:53 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-12 (523 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: Upgraded to trusty on 2013-12-09 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1262275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
