Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: 18.04 (Bionic Beaver) Known bugs and work-arounds

  1. #1
    Join Date
    Mar 2006
    Location
    Williams Lake
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    18.04 (Bionic Beaver) Known bugs and work-arounds

    Bionic Beaver (18.04) was released Thursday April 26 2018. Please post your tips and work-a-rounds here. Please do not post problems or ask for help in this thread.
    Last edited by Irihapeti; April 29th, 2018 at 10:06 PM.

  2. #2
    Join Date
    Jun 2016
    Beans
    2,831
    Distro
    Xubuntu

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    Thunar incorrectly thinks USB hard disk hasn't finished ejecting.

    Workaround: In the Thunar sidebar, instead of ejecting, right-click the partition > Unmount. Repeat for all mounted partitions. When all partitions are unmounted, use gnome-disks to power off the USB hard disk.
    Xubuntu 22.04, ArchLinux ♦ System76 hardware, virt-manager/KVM, VirtualBox
    When your questions are resolved to your satisfaction, please use Thread Tools > "Mark this thread as solved..."

  3. #3
    Join Date
    Apr 2018
    Beans
    3

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    In Spanish version, if I install a Snap from the software center, the system duplicates the personals folders, Documents, music, pictures, public, videos they should be just spanish folders, its everything ok until install a snap, then it creates a english version of all those folders and resides both of them simultaneously

  4. #4
    Join Date
    Dec 2009
    Beans
    6,776

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    SMB / Samba - Netbios - Network Browsing is Broken.

    I am talking about Nautilus > Other Locations > Windows Network. You will either get a Folder is Empty error message or just an empty page. Oh and 18.04 no longer installs an smb.conf file either which is important because the work around requires one.

    So to restore it to how it was before:
    Code:
    sudo apt install smbclient
    Then edit /etc/samba/smb.conf and right under the workgroup = WORKGROUP line add this one:
    Code:
    client max protocol = NT1
    Important note: This happened because Samba changed the highest smb dialect to SMB3 so that the client can access a server that disabled SMB1.

    ** If you set it back to NT1 you will be able to see all the servers but you will not be able to connect to any that disabled SMB1. You can use a cifs mount which works independent of how the smb client works.

    ** If you leave it with the new default of SMB3 you will not be able to discover the servers. You can still connect to the server by name but you have to know it's name and you must connect to to it explicitly by that name .. as in ... smb://hostname or use Connect to Server in Nautilus.

    There is some good news: None of this affects any Operating System that enables multicast registration ( or "publishing" ) of their Samba / SMB services.

    Ubuntu will be able to see any other macOS or Linux box via Nautilus > Other Locations - Not under Windows Network since this method has nothing to do with Windows - as long as they enabled multicast registration.

    macOS does this by default. Ubuntu 18.04 enables this feature the instant you install the samba ( server ) package. For all those Linux boxes out there that have not implemented it like Ubuntu 16.04 you can always add your own registration:

    Create a file at /etc/avahi/services/samba.service with this content on all your non-18.04 linux boxes:
    Code:
    <?xml version="1.0" standalone='no'?>
    <!DOCTYPE service-group SYSTEM "avahi-service.dtd">
    <service-group>
       <name replace-wildcards="yes">SMB %h</name> ## Display Name
       <service>
           <type>_smb._tcp</type>
           <port>445</port>
       </service>
    </service-group>

    This will "publish" your samba server to the rest of the network - but it's only discoverable to other Linux boxes or MacBooks.
    Last edited by Morbius1; April 30th, 2018 at 06:44 PM.

  5. #5
    Join Date
    Dec 2005
    Beans
    71

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    Fix for Slack & Dropbox AppIndicators not showing up upon upgrade from 17.10:

    Install this gnome extension: https://extensions.gnome.org/extension/495/topicons/

    1. Slack (installed via snap): Installing the above extension should cause the app indicator to show up again

    2. Dropbox (this I already had installed I believe from the download on dropbox.com):

    2.a. Open ~/.config/autostart/dropbox.desktop for editing
    2.a.1. Modify the line Exec=dropbox start -i as follows:
    Code:
    Exec=dbus-launch dropbox start -i
    2.b Open ./applications/dropbox.desktop
    2.b.1 Modify the line Exec=dropbox start -i to
    Code:
    Exec=dbus-launch dropbox start -i
    2.c. Save the files, stop dropbox and try to launch it again.
    Last edited by riverfr0zen; May 2nd, 2018 at 06:36 PM.

  6. #6
    Join Date
    Aug 2009
    Beans
    Hidden!
    Distro
    Xubuntu

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    Install either intel-microcode or amd64-microcode depending on which CPU you have.

    You may have problems with suspend if you don't. I did and just happened to catch a message about it when I went to tty2 and back to tty1 after suspend.

    See this link in the Detailed Description for some info about what microcode is: https://downloadcenter.intel.com/download/14303
    Last edited by Cavsfan; May 4th, 2018 at 08:47 PM. Reason: Added last line

  7. #7
    Join Date
    Aug 2009
    Beans
    Hidden!
    Distro
    Xubuntu

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    If you have USB connected mouse and keyboard and they will not wake the computer from suspend see this post for the fix.

    It helped me. Prior to doing this I ended up having to press reset after suspend.

  8. #8
    Join Date
    May 2018
    Beans
    1

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    Acer aspire One (ZG5) won't boot to login screen after upgrade to 18.04.

    After a couple of tries and different things I was able to boot in recovery-mode/network
    and switched from gdm3 to lightdm as an experiment. That solved the problem as a workaround for me.

    So from recovery mode

    switch from gdm3 to lightdm. (workaround)
    sudo apt-get install lightdm
    sudo dpkg-reconfigure lightdm (select lightdm and reboot)

    Not sure why gdm3 is locking up AAO
    lightdm is my current workaround.

    Hope this post helps some other AAO pcs out there.

  9. #9
    Join Date
    May 2018
    Beans
    40

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    Bug: Totem hesitates and jerks while playing videos not in full screen mode under Gnome and Gnome derivatives (such as Ubuntu desktop).

    Workarounds (your choice):

    1. Use a different video player such as MPV or VLC.
    2. This is a Gnome bug. Use a different desktop environment such as KDE or Cinnamon.
    3. Use Gnome on Wayland. The bug appears only in Gnome on Xorg.

  10. #10
    Join Date
    Oct 2007
    Beans
    1

    Re: 18.04 (Bionic Beaver) Known bugs and work-arounds

    If cannot login to real console mode(ctrl-alt-f1), screen tells "^[a" when press "a", login to x, and try pressing combined keys, go back to console, and it would be fine.

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •