OBS studio 需要的Opengl版本,10年前的電腦的內顯版本不滿足。youtube-dl 的問題-youtube背後的機制不斷在調整,youtibe-dl要自行更新到最新版本。
Obs studio 最少需要OpenGL 3.2 ,就算是3.1都不行。
Attempted path: share/obs/obs-studio/locale/en-US.ini
Attempted path: /usr/share/obs/obs-studio/locale/en-US.ini
Attempted path: share/obs/obs-studio/locale.ini
Attempted path: /usr/share/obs/obs-studio/locale.ini
Attempted path: share/obs/obs-studio/locale/zh-CN.ini
Attempted path: /usr/share/obs/obs-studio/locale/zh-CN.ini
info: Using preferred locale 'zh-CN'
Attempted path: share/obs/obs-studio/themes/Dark.qss
Attempted path: /usr/share/obs/obs-studio/themes/Dark.qss
info: CPU Name: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz
info: CPU Speed: 1396.932MHz
info: Physical Cores: 2, Logical Cores: 4
info: Physical Memory: 7762MB Total, 4602MB Free
info: Kernel Version: Linux 5.3.0-62-generic
info: Distribution: "Ubuntu" "18.04"
info: Portable mode: false
QMetaObject::connectSlotsByName: No matching signal for on_advAudioProps_clicked()
QMetaObject::connectSlotsByName: No matching signal for on_advAudioProps_destroyed()
QMetaObject::connectSlotsByName: No matching signal for on_program_customContextMenuRequested(QPoint)
info: OBS 0.0.1 (linux)
info: ---------------------------------
info: ---------------------------------
info: audio settings reset:
samples per sec: 44100
speakers: 2
info: ---------------------------------
info: Initializing OpenGL...
error: X Error: GLXBadFBConfig
error: Failed to create OpenGL context.
error: Failed to create context!
error: device_create (GL) failed
error: Failed to initialize video. Your GPU may not be supported, or your graphics drivers may need to be updated.
info: Freeing OBS context data
info: == Profiler Results =============================
info: run_program_init: 2640.01 ms
info: ┣OBSApp::AppInit: 1.614 ms
info: ┃ ┗OBSApp::InitLocale: 1.38 ms
info: ┗OBSApp::OBSInit: 122.179 ms
info: ┣obs_startup: 21.909 ms
info: ┗OBSBasic::OBSInit: 30.874 ms
info: ┣OBSBasic::InitBasicConfig: 0.089 ms
info: ┣OBSBasic::ResetAudio: 0.209 ms
info: ┗OBSBasic::ResetVideo: 30.503 ms
info: obs_hotkey_thread(25 ms): min=0.103 ms, median=0.423 ms, max=6.22 ms, 99th percentile=6.22 ms, 100% below 25 ms
info: audio_thread(Audio): min=0.02 ms, median=0.028 ms, max=0.11 ms, 99th percentile=0.082 ms
info: =================================================
info: == Profiler Time Between Calls ==================
info: obs_hotkey_thread(25 ms): min=25.187 ms, median=25.529 ms, max=31.353 ms, 46.3158% within ±2% of 25 ms (0% lower, 53.6842% higher)
info: =================================================
info: Number of memory leaks: 172
fattabby@fattabby-desktop:~$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 12)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation H55 Chipset LPC Interface Controller (rev 06)
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)
01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
02:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
02:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
04:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
3f:02.1 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor QPI Physical 0 (rev 02)
3f:02.2 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 02)
3f:02.3 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 02)
我有一台10年前的筆電就是如此。
直播的筆電得用新電腦
你有看過Tabletop Simulator 官網提到的硬體需求嗎?
你可以看到 /var/crash 有無軟體崩潰的訊息
那很有可能就是我現在的情形,當機時有點半殘。按Num Lock時稍微有反應,輕按一下電源按鈕他會類似正常方式的斷電
我覺得不是 Wayland 的問題。Wayland 只負責跟驅動程式溝通。
稍微看了一下,感覺類似X Window的角色。我的推論是,換句話說,如果進不去Wayland的話,系統就會半殘在那裡
只是重開之後似乎每次都能很幸運地重新喚起Waland,但是就不知道哪次會成功哪次會失敗
Wayland 需要opengl es,但是10年前電腦內顯這方面的實作…… 還不如加裝一張顯示卡就快速解決問題。
英文維基百科是這麼寫
Ubuntu ships Wayland as default in Ubuntu 17.10 (Artful Aardvark).[79] Ubuntu reverted to X.Org for Ubuntu 18.04 LTS, as Wayland still has issues with screen sharing and remote desktop applications, and does not recover as well from window manager crashes.[80][81]
如果是這樣,是不是我的問題和Wayland也無直接關係(但是又可以在crash看得到?
18.04
是用X.org 沒錯。可是你是否有作特别設定還是用了wayland?
我是直接從ubuntu網站抓18.04-4的ISO
/var/crash 用 sudo rm 的方式殺掉wayland的回報檔,下次有進桌面失敗的狀況再到/var/crash 看看?
但至少這樣討論下來,似乎有相當把握推論是過舊的內顯惹的禍?
但至少這樣討論下來,似乎有相當把握推論是過舊的內顯惹的禍?
會換這台電腦,主要的原因是我第一次跑Ubuntu的桌機,疑似主機板問題,這幾個月頻頻當機。想說用了8年也夠本了,但又不能影響日常工作,所以就找了倉庫裡10年前的舊電腦來「廢物利用」
雖然老早就預想到,會有機齡過久可能造成驅動不相容的問題,但是沒料想到會變成這樣
當然這純屬推論,畢竟也沒有真的動手編過。也許新一代小孩可能自己做到?
老孩子就自己能辦得到喔,連音樂家 好和弦的官大為都會自己編程式
不過最近要處理的事還是太多(人的注意力還是很有限),這波忙完後或許可以找幾本書試試看
總之感謝大家。我想這個問題頗有意義(特別是遇到舊電腦要跑Ubuntu的時候
只是現在的產業現實,應該還是會以Windows為主(純屬猜測
我們走的比較是公部門管理(相對於企業管理),但是怎麼去整合資訊問題,這還需要很多學習
我的目標還是暫時會聚焦在,怎麼建立有利於開放原始碼的組織環境
那你為什麼要自主為Canonical公司效力?而不幫 Arch、Suse、Redhat 擴大市場呢? XD
嗯,看你的工作職位要運作什麼樣的商業模式,那就要找適合的解決方案、合作廠商囉
這就會是另一個歷練了,那其實某種程度就是MIS的抉擇
我有一台 i7 2代的筆電 也是跑ubuntu 18.04/20.04 OK 的
我两台台式机,两代三代15,跑ubuntu20.04.