[Bug 1779051] Re: /usr/bin/gnome-control-center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R
** Branch linked: lp:~ubuntu-desktop/gnome-control-center/ubuntu -- 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/1779051 Title: /usr/bin/gnome-control- center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779051] Re: /usr/bin/gnome-control-center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R
** Description changed: - The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.1-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/f7f4e5f488353a7c6ea085de8a987eecf3c1870e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. - If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + [Impact] + The sound panel doesn't deregister a gsettings handle correctly, that may cause crashes: + https://errors.ubuntu.com/problem/f7f4e5f488353a7c6ea085de8a987eecf3c1870e + + [Test Case] + 1. Open gnome-control-center + 2. Select sound settings + 3. Select another panel + 4. Using dconf-editor toggle com.ubuntu.sound allow-amplified-volume + + Expected result: + Nothing happens + + Observed result: + Errors shown on command line each time value is toggled OR gnome-control-center crashes. + + [Regresion Potential] + Low, we are now cleaning up a reference that was missed. ** Changed in: gnome-control-center (Ubuntu Cosmic) Status: Triaged => Fix Committed -- 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/1779051 Title: /usr/bin/gnome-control- center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779051] Re: /usr/bin/gnome-control-center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R
This is a crash in our 70_allow_sound_above_100.patch patch - the gsettings schema is never unreferenced. ** Also affects: gnome-control-center (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Cosmic) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1779051 Title: /usr/bin/gnome-control- center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779051] Re: /usr/bin/gnome-control-center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R
See bug 1706524 for that feature. -- 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/1779051 Title: /usr/bin/gnome-control- center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779050] Re: /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:_gtk_builder_get_widget:screen_sharing_hide_cb:g_closure_invoke
This is fixed in git master: https://gitlab.gnome.org/GNOME/gnome-control-center/commit/eff88ab2f18d6b89395e098dadfdae7705b0fc92 ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium -- 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/1779050 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:_gtk_builder_get_widget:screen_sharing_hide_cb:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779051] [NEW] /usr/bin/gnome-control-center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.1-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/f7f4e5f488353a7c6ea085de8a987eecf3c1870e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Medium Status: Triaged ** Affects: gnome-control-center (Ubuntu Bionic) Importance: Medium Status: Triaged ** Affects: gnome-control-center (Ubuntu Cosmic) Importance: Medium Status: Triaged ** Tags: artful bionic cosmic kylin-18.04 -- 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/1779051 Title: /usr/bin/gnome-control- center:11:gtk_container_remove:update_output_settings:on_amplify_changed:g_closure_invoke:signal_emit_unlocked_R To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779050] Re: /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:_gtk_builder_get_widget:screen_sharing_hide_cb:g_closure_invoke
To reproduce: 1. Open GNOME Software 2. Go to sharing settings 3. Enable sharing 4. Click on "Screen Sharing" 5. From a terminal switch to another panel: $ gnome-control-center network -- 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/1779050 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:_gtk_builder_get_widget:screen_sharing_hide_cb:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779050] [NEW] /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:_gtk_builder_get_widget:screen_sharing_hide_cb:g_closure_invoke
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.1-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/6e8f205b4e6ab5e65fec15669d6f6b2f8f3a8be8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Medium Status: Fix Committed ** Tags: artful bionic cosmic xenial yakkety zesty -- 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/1779050 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:_gtk_builder_get_widget:screen_sharing_hide_cb:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779048] [NEW] /usr/bin/gnome-control-center:11:on_notification_dismissed:on_remove_printer_timeout:g_timeout_dispatch:g_main_dispatch:g_main_context_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.1-0ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/0aded438d4c3bdc3d33475360cc51f2aa67e9201 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic kylin-17.10 -- 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/1779048 Title: /usr/bin/gnome-control- center:11:on_notification_dismissed:on_remove_printer_timeout:g_timeout_dispatch:g_main_dispatch:g_main_context_dispatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1779048/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 685596] Re: users-admin doesn't report error when PolicyKit authentication fails
[Expired for gnome-system-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-system-tools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/685596 Title: users-admin doesn't report error when PolicyKit authentication fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/685596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723249] Re: gnome-control-center crashed with SIGSEGV in maybe_add_app_id()
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1723249 Title: gnome-control-center crashed with SIGSEGV in maybe_add_app_id() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1723249/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1683445] Re: E6430 brightness control not working
need fix in xenial. ** Changed in: oem-priority Status: New => Confirmed -- 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/1683445 Title: E6430 brightness control not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
One thing I’ve noticed is that on budgie, when you restart the window manager, keyboard shortcuts begin working again. I’m curious if that would work for you… On Wed, Jun 27, 2018 at 5:50 PM Mike Edwards <1759...@bugs.launchpad.net> wrote: > Thanks for the question. My desktop is just Ubuntu. I'm not familiar > with Budgie. > > I've found, though, that Ctrl Alt T works WHEN I use the right [CtRL] > key, but not the left one. The left key does not register on the > Keyboard Tester website, although it gives a key code of 37 when > queried. The right key on the keyboard tester website controls both > right and left [Ctrl] keys. This may just be a key mapping issue, > rather than a Ubuntu issue. I can work with using the right control key > in the interim. Of course, as a new Ubuntu user, I'm always glad to hear > advice. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1759462 > > Title: > Keyboard shortcuts not operational on 18.04 > > Status in gnome-settings-daemon package in Ubuntu: > Incomplete > > Bug description: > After installing 18.04, I noticed that certain keyboard shortcuts no > longer function. > > It appears to be related to the shortcuts that gnome-settings-daemon > control as my shortcuts that are provided by my desktop (Budgie) still > function. > > Some examples are: > > * Media keys for volume up/down/mute > * ctrl-alt-t for the terminal. I tried changing the shortcut to test. > Same behaviour. > > I double checked, and it looks like the needed daemon is still > running, > > ``` > dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-keyboard > dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-media-keys > dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-mouse > dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-power > dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-print-notifications > dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-smartcard > dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-sound > dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-sharing > dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy > dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-rfkill > dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-wacom > dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-xsettings > dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-a11y-settings > dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-clipboard > dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-color > dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-datetime > dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-housekeeping > dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-printer > dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep > --color=auto gnome-settings-daemon > ``` > > Reboot does not seem to help. However, occasionally the shortcuts do > seem to work - but only very occasionally. > > Any other info needed? > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gnome-settings-daemon 3.28.0-0ubuntu2 > ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 > Uname: Linux 4.15.0-12-generic x86_64 > ApportVersion: 2.20.9-0ubuntu1 > Architecture: amd64 > CurrentDesktop: Budgie:GNOME > Date: Tue Mar 27 21:12:18 2018 > InstallationDate: Installed on 2018-03-05 (22 days ago) > InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180304) > SourcePackage: gnome-settings-daemon > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-settings-daemon; > component=main; status=Incomplete; importance=Low; assignee=None; > Launchpad-Bug-Tags: amd64 apport-bug bionic > Launchpad-Bug-Information-Type: Public >
[Bug 1779019] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1706097, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1779019/+attachment/5157248/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1779019/+attachment/5157250/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1779019/+attachment/5157253/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1779019/+attachment/5157254/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1779019/+attachment/5157255/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1779019/+attachment/5157256/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1779019/+attachment/5157257/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779019 Title: gvfsd-mtp crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778983] Re: Resume from suspend on Wayland breaks window positioning
Please report this bug to the Gnome developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues And if you can, please try to simplify the test case as much as possible. ** Tags added: resume ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1778983 Title: Resume from suspend on Wayland breaks window positioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1778983/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778983] Re: Resume from suspend on Wayland breaks window positioning
When done, please let us know the ID of the new bug. -- 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/1778983 Title: Resume from suspend on Wayland breaks window positioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1778983/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778962] Re: when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager; " the editers saves the file as a Amiga SoundTracker a
I can confirm the bug on 16.04, but it's only nautilus/GTK reporting the file type is "Amiga SoundTracker audio (audio/x-mod)". In a shell it is correctly identified as text: $ file Untitled\ Document\ 1 Untitled Document 1: ASCII text Furthermore, the bug does not seem to exist any more in Ubuntu 18.10. ** Package changed: gedit (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released -- 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/1778962 Title: when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager;" the editers saves the file as a Amiga SoundTracker audio (audio/x-mod) file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1778962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717297] Re: gedit sometimes hangs when saving new file
Eduard, Please run: apport-collect 1717297 on the machine to help us get more information. I can't seem to be able to reproduce the problem. So two additional questions: 1. Do you have any network mounts? 2. Does the kernel show any errors during/after the hang? (run: dmesg) ** Changed in: gedit (Ubuntu) Status: New => Incomplete -- 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/1717297 Title: gedit sometimes hangs when saving new file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1717297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create()
** No longer affects: systemd -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
Thanks for the question. My desktop is just Ubuntu. I'm not familiar with Budgie. I've found, though, that Ctrl Alt T works WHEN I use the right [CtRL] key, but not the left one. The left key does not register on the Keyboard Tester website, although it gives a key code of 37 when queried. The right key on the keyboard tester website controls both right and left [Ctrl] keys. This may just be a key mapping issue, rather than a Ubuntu issue. I can work with using the right control key in the interim. Of course, as a new Ubuntu user, I'm always glad to hear advice. -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
I have seen some people who have made these types of comments with desktops other than Budgie, Can you confirm which one you are on? On Wed, Jun 27, 2018 at 2:31 PM Mike Edwards <1759...@bugs.launchpad.net> wrote: > I have a fresh install of 18.04 on an LG Gram. The [control] [alt] T > keys do not open the terminal. Within the terminal, the control keys > don't work either. This is frustrating. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1759462 > > Title: > Keyboard shortcuts not operational on 18.04 > > Status in gnome-settings-daemon package in Ubuntu: > Incomplete > > Bug description: > After installing 18.04, I noticed that certain keyboard shortcuts no > longer function. > > It appears to be related to the shortcuts that gnome-settings-daemon > control as my shortcuts that are provided by my desktop (Budgie) still > function. > > Some examples are: > > * Media keys for volume up/down/mute > * ctrl-alt-t for the terminal. I tried changing the shortcut to test. > Same behaviour. > > I double checked, and it looks like the needed daemon is still > running, > > ``` > dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-keyboard > dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-media-keys > dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-mouse > dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-power > dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-print-notifications > dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-smartcard > dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-sound > dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-sharing > dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy > dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-rfkill > dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-wacom > dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-xsettings > dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-a11y-settings > dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-clipboard > dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-color > dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-datetime > dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-housekeeping > dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 > /usr/lib/gnome-settings-daemon/gsd-printer > dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep > --color=auto gnome-settings-daemon > ``` > > Reboot does not seem to help. However, occasionally the shortcuts do > seem to work - but only very occasionally. > > Any other info needed? > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gnome-settings-daemon 3.28.0-0ubuntu2 > ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 > Uname: Linux 4.15.0-12-generic x86_64 > ApportVersion: 2.20.9-0ubuntu1 > Architecture: amd64 > CurrentDesktop: Budgie:GNOME > Date: Tue Mar 27 21:12:18 2018 > InstallationDate: Installed on 2018-03-05 (22 days ago) > InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180304) > SourcePackage: gnome-settings-daemon > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-settings-daemon; > component=main; status=Incomplete; importance=Low; assignee=None; > Launchpad-Bug-Tags: amd64 apport-bug bionic > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: arauzo arter97 bashfulrobot jfbourdeau louisgag > m1nermike nmnguyen ricklee518 seb128 tdelacro thundermind > Launchpad-Bug-Reporter: Dustin Krysak (bashfulrobot) > Launchpad-Bug-Modifier: Mike Edwards (m1nermike) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bashfulrobot > -- Dustin Krysak -- You received this bug
[Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
I have a fresh install of 18.04 on an LG Gram. The [control] [alt] T keys do not open the terminal. Within the terminal, the control keys don't work either. This is frustrating. -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1680438] Re: gnome-calculator comes up with totally wrong answer
gnome has moved to gitlab. Corresponding bug is now https://gitlab.gnome.org/GNOME/gnome-calculator/issues/59 -- 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/1680438 Title: gnome-calculator comes up with totally wrong answer To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1680438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775634] Re: Occasional notifications about an application having prevented screen lock
This bug only seems to happen in the Xorg session and not the Wayland one. -- 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/1775634 Title: Occasional notifications about an application having prevented screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1775634/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778983] [NEW] Resume from suspend on Wayland breaks window positioning
Public bug reported: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1778983 Title: Resume from suspend on Wayland breaks window positioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1778983/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753719] Re: gnome-calculator won't launch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-calculator (Ubuntu) Status: New => Confirmed -- 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/1753719 Title: gnome-calculator won't launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1753719/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765139] Re: gnome-shell crashed with SIGABRT in __GI_raise()
*** This bug is a duplicate of bug 1422253 *** https://bugs.launchpad.net/bugs/1422253 Added crash report ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+attachment/5157162/+files/_usr_bin_gnome-shell.1000.crash -- 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/1765139 Title: gnome-shell crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765139] Re: gnome-shell crashed with SIGABRT in __GI_raise()
*** This bug is a duplicate of bug 1422253 *** https://bugs.launchpad.net/bugs/1422253 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1765139 Title: gnome-shell crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778607] Re: Incorrect licenses listed in the GNOME Software for Snap Apps.
I doesn't work because those are not officially supported ubuntu debs. I am going to send you a message on launchpad so that we don't crowd this comment section with unrelated comments, and maybe you can help a bit :) - thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1778607 Title: Incorrect licenses listed in the GNOME Software for Snap Apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778962] [NEW] when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager; " the editers saves the file as a Amiga SoundTracker
Public bug reported: when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager;" the editers saves the file as a Amiga SoundTracker audio (audio/x-mod) file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 27 13:32:25 2018 InstallationDate: Installed on 2018-02-20 (126 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1778962 Title: when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager;" the editers saves the file as a Amiga SoundTracker audio (audio/x-mod) file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1778962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196785]
http://trust.acidbelly.org Terry Galati -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/196785 Title: 'sh' syntax highlighting actually for bash, and uses syntax invalid for Bourne shell To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/196785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770502] Re: Brasero hangs when burning cds
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: brasero (Ubuntu) Status: New => Confirmed -- 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/1770502 Title: Brasero hangs when burning cds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+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
For cross-referencing purposes, the Ask Ubuntu thread is https://askubuntu.com/questions/968641/how-does-one-get-system-load- indicator-or-something-similar-working-in-17-10. -- 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 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Patch added: "systemd_237-3ubuntu10.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+attachment/5157097/+files/systemd_237-3ubuntu10.2.debdiff ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778936] [NEW] please re-add Support-system-image-read-only-etc.patch
Public bug reported: The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767817] Re: Full text search does not work
Same here with a fresh installed Ubuntu 18.04... -- 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/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717297] Re: gedit sometimes hangs when saving new file
** Package changed: firefox (Ubuntu) => gedit (Ubuntu) -- 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/1717297 Title: gedit sometimes hangs when saving new file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1717297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717297] [NEW] gedit sometimes hangs when saving new file
You have been subscribed to a public bug: - start gedit - type text - choose save or save as - don't type a name, but click the triangle left of the name of your home folder (see attachment) - sometimes gedit hangs now => text lost - same happens sometimes when just waiting a bit after choosing save / save as ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: as gedit hangs save -- gedit sometimes hangs when saving new file https://bugs.launchpad.net/bugs/1717297 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738085] Re: Bridge gets created while the network interfaces are still being renamed
Hi, first of all I beg your pardon - while I'm just the one cleaning old bugs - it is bad that you had to wait so long. Now lets get to your case... This is a mix of systemd and ifup based network ocnfiguration, and in Artful a lot of this was still in flight. In Bionic there is a simplified frontend to networkd (or networkmanager) [1] netplan. I wanted to check your case with this new way to do it. I have 4 devices, using one as "wan" and 3 for the bridge in netplan looks like: network: version: 2 ethernets: wan: dhcp4: true match: macaddress: 52:54:00:75:f5:3e set-name: wan lan1: match: macaddress: 52:54:00:84:a1:87 set-name: lan1 lan2: match: macaddress: 52:54:00:f3:4f:cc set-name: lan2 lan3: match: macaddress: 52:54:00:ff:11:1a set-name: lan3 bridges: br0: addresses: [ 10.0.0.1/24 ] interfaces: - lan1 - lan2 - lan3 That will create link files like yours for renaming: $ cat /run/systemd/network/10-netplan-wan.link [Match] MACAddress=52:54:00:75:f5:3e [Link] Name=wan WakeOnLan=off But also for network configuration: $ cat /run/systemd/network/10-netplan-wan.network [Match] MACAddress=52:54:00:75:f5:3e Name=wan [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 Especially also the bridge: $ cat /run/systemd/network/10-netplan-br0.network [Match] Name=br0 [Network] Address=10.0.0.1/24 $ cat /run/systemd/network/10-netplan-br0.netdev [NetDev] Name=br0 Kind=bridge And the device association to the bridge: $ cat /run/systemd/network/10-netplan-lan2.network [Match] MACAddress=52:54:00:f3:4f:cc Name=lan2 [Network] Bridge=br0 LinkLocalAddressing=no That looks good to me now: $ networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 6 br0 ether routableconfigured 7 lan3 ether carrier configured 8 lan1 ether carrier configured 9 wan ether routableconfigured 10 lan2 ether carrier configured $ networkctl status ●State: routable Address: 10.0.0.1 on br0 192.168.122.229 on wan fe80::e831:94ff:fe76:95f9 on br0 fe80::5054:ff:fe75:f53e on wan Gateway: 192.168.122.1 on wan DNS: 192.168.122.1 $ brctl show bridge name bridge id STP enabled interfaces br0 8000.ea31947695f9 no lan1 lan2 lan3 Please see [1] and man netplan for more, or feel free to write the same in networkd rules as you already started on your own. But mixing the systems to control devices is not really recommended as you'd run in issues just as the one you have reported. Therefore I'd consider this a broken config more than a bug in Ubuntu and would mark the bug incomplete for now until further discussion/info was provided. [1]: https://netplan.io/ ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete ** Changed in: bridge-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1738085 Title: Bridge gets created while the network interfaces are still being renamed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1738085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778824] Re: Terminal starts maximized when using custom font
170x43 terminal with same font starts in normal window. Terminal of size 170x44 is maximized. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1778824 Title: Terminal starts maximized when using custom font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1778824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778824] Re: Terminal starts maximized when using custom font
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1778824 Title: Terminal starts maximized when using custom font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1778824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778824] Re: Terminal starts maximized when using custom font
I can reproduce this in a GNOME session, but not in Unity. Sounds like a bug with the window manager (gnome-shell or mutter). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1778824 Title: Terminal starts maximized when using custom font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1778824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770617] Re: Dia-normal, GIMP crash when attempting to print using network printer
** Also affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770617 Title: Dia-normal, GIMP crash when attempting to print using network printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dia/+bug/1770617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS
** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- 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/1763892 Title: 144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754702] Re: Delay before you can type after switching input source
Same issue. Very annoying bug. -- 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/1754702 Title: Delay before you can type after switching input source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1754702/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758528] Re: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from gbm_get_next_fb_id()
** Description changed: https://gitlab.gnome.org/GNOME/mutter/issues/21 https://errors.ubuntu.com/problem/a3d143e94242ebfe1c753ef1e2809b7128702abc + + -- + + The fix for this bug is included in mutter 3.28.2 upstream release, and + as per that doesn't need specific SRU verification. + + See bug 1778703 --- Randomly crashes in minutes following a reboot. - ProblemType: Crash - DistroRelease: Ubuntu 18.04 + ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Mar 22 21:39:40 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fce03ec7c90 : mov (%rdi),%rax PC (0x7fce03ec7c90) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA - Signal: 11 - SourcePackage: gnome-shell + Signal: 11SourcePackage: gnome-shell StacktraceTop: gbm_bo_get_plane_count () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- 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/1758528 Title: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from gbm_get_next_fb_id() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1758528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
I have a fresh Ubuntu 18.04 install and experience the same problems: some keyboard shortcut do not work all of a sudden (they worked before, on the same installation) Examples: super-L to lock screen, alt-printScreen, ... -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+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 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)
I will report it there. But are you sure that is not a Wayland issue? That something on the graphics loop can block the whole execution of the program and be woken up by mouse movement sounds like a deep architectural problem to me. The graphics card is rare, it is integrated in a HP ProLiant DL380 G6, a server system with dual Xeon processors. -- 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/1778566 Title: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1778566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
