| bp0 | Is it possible to report bugs via launchpad anymore? When I try I get "Timeout Error" | 03:21 |
|---|---|---|
| phoenix_firebrd | https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1756380 | 04:24 |
| ubottu | Launchpad bug 1756380 in intel-vaapi-driver (Ubuntu) "vaapi VP9 hardware decoding not working anymore in bionic" [Undecided,Confirmed] | 04:24 |
| phoenix_firebrd | Where can I see the progress on the above bug? | 04:25 |
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| Auctus | if i plug headphones in on the lock screen, the headphone dialog thing shows up, shouldnt nothing show up from the lock screen? | 08:12 |
| lotuspsychje | Auctus: i think its normal behaviour, if the screen is locked, nothing shows | 08:13 |
| Auctus | yeah nothing *should* show, because its locked, but it *does* show | 08:14 |
| Auctus | well, at least if i click "sound settings" from that dialogue, the sound settings option doesnt show. That'd be bad. | 08:15 |
| Auctus | but the "what did you just plug in" dialog does show. Maybe there are security implications? idk. | 08:15 |
| Auctus | also i am glad "Night Light" is now built in to the OS | 08:16 |
| lotuspsychje | Auctus: think i saw a user passby, that could not play music during locked screen | 08:24 |
| Auctus | in a recent version of ubuntu, 16.04 or 16.10, my laptop (hp 6910p) would show me whatever was on the screen for a solid 30 seconds, couldnt interact with anything, before finally the lock screen would show up | 08:25 |
| Auctus | lot of problems beginning to show up on core2duo era laptops i guess, not many users left on old hardware to report bugs | 08:25 |
| lotuspsychje | i guess lubuntu & xubuntu will cover that :p | 08:27 |
| Volkodav | Auctus: U have a box on a core2duo | 08:56 |
| Volkodav | what bugs are you talking about? | 08:56 |
| Volkodav | I have a box* | 08:56 |
| Auctus | Volkodav: the above mentioned lock screen issue, recently a graphical screwup where the desktop would get into a restarting loop (unity?) and the machine was unusable, youd have to install lxde or something from the cli to get working again, it was resolved after a few days | 08:59 |
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| Auctus | whatever makes the window animations look cool in 18.04 is good | 10:26 |
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| === JanC_ is now known as JanC | ||
| eoli3n | Hi | 12:26 |
| eoli3n | i can't find in which package /etc/default/rcS file is in bionic | 12:26 |
| eoli3n | apt-file seems have empty cache | 12:27 |
| === phoenix_firebrd is now known as n | ||
| === n is now known as phoenix_firebrd | ||
| eoli3n | hm https://packages.ubuntu.com/search?suite=bionic&arch=any&mode=exactfilename&searchon=contents&keywords=rcS | 12:28 |
| eoli3n | is gdm the new default display manager ? | 12:48 |
| eoli3n | will unity-greeter disapear ? | 12:49 |
| eoli3n | ok, i switch to slick-greeter which is easier to configure | 13:11 |
| manuelschneid3r | is this the correct channel for 1804 dicussions? | 13:41 |
| Faux | Yes! | 13:44 |
| manuelschneid3r | hi guys i got a symbol lookup error in 18 04. in my qt application I make use of libXext. which has always been pulled automatically by some package. | 13:47 |
| manuelschneid3r | now I get a symbol lookup error. (XShapeQueryExtension) which is usually in libXext | 13:48 |
| manuelschneid3r | ldd does not show up libXext anymore | 13:48 |
| manuelschneid3r | the funny thing is the build for i386 is fine | 13:48 |
| manuelschneid3r | sidenote: I let openSuse Build system handle the build | 13:48 |
| manuelschneid3r | 1 mom plz. ill check which of the packages pulls libXext in the i386 build | 13:49 |
| manuelschneid3r | okay no even more interesting is that libXext is not output by ldd | 13:51 |
| manuelschneid3r | ¯\_(ツ)_/¯ | 13:52 |
| swein | Anyone update to latest develop and not able to get spotify to run | 13:55 |
| swein | I'm trying to reinstall and it's hanging in it's own installer | 13:55 |
| swein | gooing apt route. there's broken packages and fail depends. meh | 13:58 |
| swein | had to manually install libcurl3 for those that care. the snap is broke. the .deb binary works | 14:08 |
| eoli3n | i have a strange behaviour with lightdm | 14:09 |
| eoli3n | i can launch it without error with lightdm –-test-mode --debug | 14:10 |
| eoli3n | but i can't start systemd unit | 14:10 |
| eoli3n | https://ptpb.pw/0Et0 | 14:10 |
| eoli3n | lightdm.service: Start request repeated too quickly | 14:11 |
| eoli3n | here logs with debug active : https://ptpb.pw/CW-x | 14:11 |
| Faux | Today's Buyer Beware seems to be snapd: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1756793 | 14:16 |
| ubottu | Launchpad bug 1756793 in snapd (Ubuntu) "Can't run snaps on Ubuntu 18.04" [Undecided,Confirmed] | 14:16 |
| swein | there we go | 14:20 |
| Faux | Oh, heh, swein was complaining about it. I scannde the scrollback, obviously not well. | 14:23 |
| manuelschneid3r | any devs here | 14:24 |
| manuelschneid3r | none of the qt libs links to libXext | 14:24 |
| manuelschneid3r | I am not sure but I guess thats an issue | 14:24 |
| Faux | Sounds like a bug in your application? | 14:24 |
| manuelschneid3r | nope | 14:25 |
| manuelschneid3r | well maybe | 14:25 |
| manuelschneid3r | I couls link explicitely to libXext | 14:25 |
| Faux | Just 'cos something happened to work before doesn't mean it was right. That's 99% of the problem with writing crap in C. | 14:25 |
| manuelschneid3r | but other channels tell me that I can assume libXext to be present when I linked libX11 | 14:26 |
| Faux | If you think it's a bug in Qt, raise it with Qt. If you think it's a bug in libX11, raise it against libX11. If you think it's a bug in Ubuntu's build of libX11 violating something libX11 is documented to do, or it breaks any software that's shipped with Ubuntu, raise it against Ubuntu? | 14:27 |
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| Odd_Bloke | I was able to workaround that snap issue by refreshing to the beta core snap. | 14:40 |
| Odd_Bloke | (i.e. `snap refresh --beta core`) | 14:41 |
| Odd_Bloke | Faux: ^ | 14:41 |
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| Faux | Yup, that fixes it for me; cheers. | 14:42 |
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| === phoenix_firebrd is now known as phoenix_firebrd_ | ||
| === phoenix_firebrd_ is now known as phoenix_firebrd | ||
| === shadeslayer_ is now known as shadeslayer | ||
| BLZbubba | is anyone else seeing marco GPU compositor lockups? it has been happening a lot this week | 15:33 |
| BLZbubba | switching to the non gpu version seems more stable (so far) | 15:34 |
| dupondje | Huy! | 15:46 |
| dupondje | just upgraded to 18.04, but 2 issues :( | 15:46 |
| dupondje | gdm greeter is broken? | 15:46 |
| dupondje | and fractional scaling is not working :( | 15:46 |
| bp0 | I've been trying to report a bug in launchpad for a couple days, and I always get "Timeout Error", is it down? | 16:16 |
| bp0 | https://bugs.launchpad.net/ubuntu/+filebug | 16:16 |
| bp0 | Doesn't work. | 16:16 |
| nacc | bp0: there is #launchpad, and there was a bit of db maintenance a day ago or so | 16:16 |
| nacc | bp0: try now? | 16:16 |
| bp0 | I just tried it and got the timeout error | 16:16 |
| nacc | bp0: does it give you an OOPS id? | 16:17 |
| bp0 | (Error ID: OOPS-ad34bc67402921e640c37c5909ecd6a7) | 16:17 |
| nacc | bp0: right, post in #launchpad and mention that | 16:17 |
| bp0 | Alright, done. Thanks | 16:18 |
| bp0 | https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1757202 | 16:34 |
| ubottu | Launchpad bug 1757202 in nvidia-graphics-drivers-390 (Ubuntu) "xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time" [Undecided,New] | 16:34 |
| bp0 | bug posted, thanks nacc | 16:34 |
| nacc | bp0: yw | 16:36 |
| Ian_Corne | I'm getting "corrupted" screen when I log in, but it goes away after 1 seconds, anyone else? | 16:43 |
| FurretUber | Hi, I turned on my notebook and the wireless is not working but I'm connected using a Ethernet network. It has a QCA9377 card (which is not being shown on lspci). | 16:50 |
| nacc | FurretUber: any indications/errors about the card in dmesg? | 16:53 |
| FurretUber | There is this: https://paste.ubuntu.com/p/rQRRFpFDKp/ | 16:53 |
| nacc | FurretUber: is it a usb wireles device? | 16:55 |
| FurretUber | No, it's a PCI device, but it shows these USB errors | 16:59 |
| nacc | FurretUber: hrm | 17:00 |
| nacc | FurretUber: have you tried with any prior Ubuntu versions/ | 17:00 |
| nacc | FurretUber: oh it's an atheros device? | 17:00 |
| FurretUber | Yes. With prior versions the system would freeze on boot. And yes, it's a Atheros device | 17:00 |
| nacc | https://askubuntu.com/questions/772348/ubuntu-16-04-installing-atheros-qca9377-wireless-driver-makes-booting-problems ? | 17:01 |
| nacc | maybe related, maybe no driver? | 17:01 |
| FurretUber | I have the files there: https://paste.ubuntu.com/p/jbtVZNvtXv/ | 17:04 |
| nacc | hrm ok | 17:04 |
| nacc | FurretUber: do you see the driver load? dmesg | grep ath10k | 17:04 |
| FurretUber | Nothing | 17:04 |
| nacc | FurretUber: then that firmware seems irrelevant :) | 17:05 |
| nacc | FurretUber: can you pastebin full dmesg? | 17:05 |
| FurretUber | At 841, I tried to load the ath module: https://paste.ubuntu.com/p/BCsrp2RXgx/ | 17:07 |
| FurretUber | Other than that, it's normal boot | 17:07 |
| nacc | ll 585-586 are a bit odd (i'm assuming if the device isn't visible to the os it's actually in firmware / ACPI ) | 17:08 |
| FurretUber | This is a error, it always happens | 17:09 |
| nacc | FurretUber: ok | 17:09 |
| FurretUber | I don't know how to solve, but appears to cause no issues other than: | 17:10 |
| FurretUber | [ 1.247761] ima: No TPM chip found, activating TPM-bypass! (rc=-19) | 17:10 |
| nacc | FurretUber: lsmod | grep ath? | 17:11 |
| FurretUber | Nothing | 17:12 |
| nacc | FurretUber: can you pastebin lspci? | 17:12 |
| FurretUber | https://paste.ubuntu.com/p/stGK58qxQN/ When it decides to work it shows as 02:00.0 | 17:13 |
| nacc | FurretUber: you mean on older releases? | 17:14 |
| nacc | FurretUber: or when does it "decide to work"? | 17:14 |
| FurretUber | If I turn off the notebook and turn it on, it may work | 17:14 |
| nacc | FurretUber: ah, this definitely seems like buggy hardware/bios/ACPI | 17:14 |
| FurretUber | It's something like work -> don't work -> work -> don't work | 17:14 |
| nacc | FurretUber: TJ- has some stuff to help workaroudn this (it usually is because the hardware/firmware only works in windows) | 17:14 |
| nacc | FurretUber: but they are not online right now | 17:15 |
| nacc | let me see if ic an find it | 17:15 |
| FurretUber | When working, it shows a message when turning off like: failed to remove key (router's mac addres) vkey 0, something like that | 17:15 |
| nacc | FurretUber: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html | 17:16 |
| FurretUber | I will reboot and test, give me a moment | 17:23 |
| FurretUber | nacc: adding that option caused a kernel panic like the one in https://askubuntu.com/questions/772348/ubuntu-16-04-installing-atheros-qca9377-wireless-driver-makes-booting-problems on boot | 17:32 |
| nacc | hrm | 17:32 |
| nacc | FurretUber: well, that's techincally better in that it means the device was found then? | 17:33 |
| FurretUber | It still shown the USB errors, but then instead of the login screen I got a kernel panic | 17:33 |
| nacc | FurretUber: have you checked if your file contents are the same as the ones inthe github repo? | 17:33 |
| FurretUber | No, I will check | 17:34 |
| nacc | FurretUber: honestly, in my experience atheros devices are a pain, not performant in linux and not worth the hassle :/ | 17:34 |
| nacc | FurretUber: but i would first check if there is newer firmware available from that repo, see if it makes a difference | 17:34 |
| nacc | FurretUber: if it continues to happen, i guess i would file a bug agianst the kernel | 17:35 |
| nacc | https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683577 | 17:35 |
| ubottu | Launchpad bug 1683577 in linux (Ubuntu) "QCA9377 WIFI does not work" [Medium,Incomplete] | 17:35 |
| FurretUber | Is using sha256sum reliable to say the file is the same? | 17:36 |
| nacc | https://bugs.launchpad.net/ubuntu/+bug/1463051 | 17:36 |
| ubottu | Launchpad bug 1463051 in Ubuntu "Qualcomm Atheros QCA9377 Ubuntu 14.04LTS UNCLAIMED" [Undecided,Confirmed] | 17:36 |
| nacc | FurretUber: yeah, probably | 17:36 |
| nacc | FurretUber: you can also just `diff` them | 17:37 |
| nacc | (even binaries) | 17:37 |
| FurretUber | I didn't know the diff command, very useful. The board.bin and board-2.bin are the same and the firmware-5.bin is the same as the one firmware-5.bin from the WLAN.TF.1.0 directory | 17:40 |
| nacc | FurretUber: ok | 17:40 |
| FurretUber | There is another firmware-5.bin on CNSS.TF.1.0 but this one is different and there is a firmare-6.bin at WLAN.TF.2.1 | 17:41 |
| FurretUber | Also, there is a untested firmware-sdio-5 | 17:42 |
| nacc | FurretUber: i really dont' know too mcuh more about the device and don't want to fully break your system | 17:42 |
| nacc | FurretUber: i'd start with filing a bug, i think, against linux | 17:43 |
| FurretUber | This is the notebook's support page: https://pcsupport.lenovo.com/br/pt/products/laptops-and-netbooks/300-series/310-14isk/80ug | 17:44 |
| lotuspsychje | FurretUber: you have linux-firmware installed? | 17:45 |
| FurretUber | Yes | 17:45 |
| lotuspsychje | i recently got 2 boxes that doesnt recognize ethernetcard that worked on early stages of 18.04 3com & ralink | 17:46 |
| lotuspsychje | drivers are loaded, so perhaps flaw in network-manager..not sure yet either | 17:47 |
| FurretUber | This is the bug report I wrote: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218 | 18:16 |
| ubottu | Launchpad bug 1757218 in linux (Ubuntu) "QCA9377 isn't being recognized sometimes" [Undecided,New] | 18:16 |
| lotuspsychje | lets c | 18:16 |
| lotuspsychje | FurretUber: have you tested this in other ubuntu versions? | 18:17 |
| FurretUber | It would suffer a kernel panic when these USB error messages appeared | 18:18 |
| FurretUber | With Bionic only the network card don't work | 18:18 |
| lotuspsychje | FurretUber: try a few tests and reply to your own bug with what you tested | 18:20 |
| lotuspsychje | FurretUber: also finding other users with same issue can help in solving | 18:21 |
| lotuspsychje | !atheros | FurretUber test also perhaps? | 18:22 |
| ubottu | FurretUber test also perhaps?: Wireless documentation, including how-to guides and troubleshooting information, can be found at https://help.ubuntu.com/community/WifiDocs | 18:22 |
| fetido | ¿how do i upgrade from 14.04 to 18.04? | 18:35 |
| FurretUber | The output from the command at https://help.ubuntu.com/community/WirelessTroubleshootingProcedure is gigantic, should I post it on the launchpad bug report? | 18:44 |
| fetido | FurretUber: pastebin it | 19:03 |
| croberts | is 18.04 beta pretty ok to use right now as a dev workstation | 19:21 |
| croberts | or is there still major issues | 19:21 |
| croberts | was curious if anyone had any big things to watch out for | 19:27 |
| Odd_Bloke | croberts: It's working for me, certainly. | 19:35 |
| croberts | nice | 19:35 |
| swein | croberts: good to go. | 19:45 |
| croberts | nice, ty guys | 19:45 |
| fetido | pfefia2ew9 | 20:10 |
| fetido | ¿?¿?¿?¿?¿? | 20:11 |
| === fetido is now known as akko | ||
| tomreyn | akko: you don't upgrade to 18.04, yet, since it's not released. and even then, upgrades won't be available until ~ july (18.04.1 release). then you should be able to upgrade from 14.04 to 16.04 and then from 16.04 to 18.04(.1). | 20:25 |
| tomreyn | akko: there will be a lot of changes on this route, though, so migrating configurations will involve a lot of work, and you might as well consider a fresh installation of 18.04 and a manual migration. | 20:26 |
| croberts | if i use the 18.04 beta can i just upgrade as normal once 18.04 goes to release? | 21:18 |
| croberts | or is it a fresh install | 21:18 |
| Faux | You can upgrade, but it might not be quite the same as as a fresh install. | 21:19 |
| nacc | croberts: yes, you upgrade as normal | 21:19 |
| nacc | *can upgrade | 21:20 |
| croberts | cool | 21:20 |
| nacc | croberts: 'beta' is just a point in time | 21:20 |
| nacc | croberts: you should always update it immediately anyways | 21:20 |
| croberts | that makes more sense, thank you | 21:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!