Public bug reported:
I recently upgraded from 18.04 to 18.10, and after the upgrade I
immediately started seeing very long delays after login. Not only that,
the xfce4-notifyd aspect would just time out and never complete loading.
The solution was
systemctl disable bluetooth
So, to disable the bluetooth daemon.
Now, my computer doesn't have bluetooth, and I don't plug bluetooth
devices/radios into it really ever.
During the "wait" time, things like "ctrl esc" and other ways to bring
up the application menu simply didn't respond. And I would have to
manually run and fork the xfce4-notifyd proccess.
I suspect bluetooth is timing out looking for devices that don't/never
exist(ed), but I don't know why that behaviour changed drastically in
18.10. This is a very poor user experience, and it took me weeks on and
off to figure out.
* Ubuntu 18.10 + XFCE4
* i7 980x
* 24GB RAM
* Asus Xonar DGX
* GTX 960
* 3x1920x1080 monitors (all in landscape)
Hope this gets solved, because there's seriously no good solutions on
the internet that I could find. This seriously was stabbing in the dark
here.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Nov 11 11:57:12 2018
InstallationDate: Installed on 2015-07-20 (1209 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
InterestingModules: bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic
root=UUID=3557b89b-06a6-4e9f-8538-41be167eede8 ro quiet splash vga=789
nomodeset mode_option=1280x1024-24,mtrr=3,scroll=ywrap
SourcePackage: bluez
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (11 days ago)
dmi.bios.date: 09/19/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1701
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Rampage II GENE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1701:bd09/19/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIGENE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
rfkill:
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1802774
Title:
Bluetooth (bluez) in 18.10 hangs xfce4 for upwards of 30 seconds,
notifyd / stuff crashes
Status in bluez package in Ubuntu:
New
Bug description:
I recently upgraded from 18.04 to 18.10, and after the upgrade I
immediately started seeing very long delays after login. Not only
that, the xfce4-notifyd aspect would just time out and never complete
loading.
The solution was
systemctl disable bluetooth
So, to disable the bluetooth daemon.
Now, my computer doesn't have bluetooth, and I don't plug bluetooth
devices/radios into it really ever.
During the "wait" time, things like "ctrl esc" and other ways to bring
up the application menu simply didn't respond. And I would have to
manually run and fork the xfce4-notifyd proccess.
I suspect bluetooth is timing out looking for devices that don't/never
exist(ed), but I don't know why that behaviour changed drastically in
18.10. This is a very poor user experience, and it took me weeks on
and off to figure out.
* Ubuntu 18.10 + XFCE4
* i7 980x
* 24GB RAM
* Asus Xonar DGX
* GTX 960
* 3x1920x1080 monitors (all in landscape)
Hope this gets solved, because there's seriously no good solutions on
the internet that I could find. This seriously was stabbing in the
dark here.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Nov 11 11:57:12 2018
InstallationDate: Installed on 2015-07-20 (1209 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
InterestingModules: bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic
root=UUID=3557b89b-06a6-4e9f-8538-41be167eede8 ro quiet splash vga=789
nomodeset mode_option=1280x1024-24,mtrr=3,scroll=ywrap
SourcePackage: bluez
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (11 days ago)
dmi.bios.date: 09/19/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1701
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Rampage II GENE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1701:bd09/19/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIGENE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
rfkill:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1802774/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
