[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
This does appear to fix the issue for me on 22.4.04 LTS sudo add-apt-repository ppa:vanvugt/mutter sudo apt update Then upgrade mutter-common, libmutter-10-0 and gir1.1-mutter-10 (I'm not certain if all 3 of these are required or not). This will get you version 42.9-0ubuntu7 Reboot !! (required) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: In Progress Status in mutter source package in Noble: Fix Released Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Run: journalctl -b0 | grep MetaSyncRing 4. Verify the above command does NOT show "MetaSyncRing" messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since the code being modified is only used with that driver. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
Can confirm that libmutter-10-0/42.5-0ubuntu1 fixed my issue. Thanks for all your hard work on this! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Fix Released Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Released Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
I pulled gnome-shell, gnome-shell-common, mutter, and mutter-common 42.5-0ubuntu1 on 22.04.1 LTS, rebooted, and was able to immediately reproduce the issue by locking my screen and attempting to unlock it. OOPS ID: fb8c6096-5550-11ed-b3c8-fa163ef35206 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
I came here from 1969351. On a rig with two identical AMD GPUs (First driving one monitor, second driving three), I'll sometimes have the one monitor disconnect, but it won't detect the failure or cause the other three screens to rearrange until I try to apply a change in Display Settings, after which it will show the one monitor as missing. The system will continue operating normally for a minute or two, before crashing back to the login screen Dmesg shows these entries: [127759.552431] gnome-shell[4403]: segfault at 558324328300 ip 558324328300 sp 7ffd66257c98 error 15 [127780.586613] apport-gtk[272085]: segfault at 18 ip 7fa1e6314cf4 sp 7fff77ca9820 error 4 in libgtk-3.so.0.2404.29[7fa1e620c000+383000] [130882.632498] traps: gnome-shell[272824] general protection fault ip:7f3228a412e7 sp:7ffe4c6be868 error:0 in libgbm.so.1.0.0[7f3228a4+8000] [176834.926719] gnome-shell[285277]: segfault at 50100af ip 7f250fbc92e7 sp 7fff283ee988 error 4 in libgbm.so.1.0.0[7f250fbc8000+8000] - Sometimes the system crashes to the login screen during a screen lock without any interaction - Sometimes the system crashes to the login screen when attempting to unlock a locked session - Sometimes after unlock a session shows all the windows rearranged or consolidated into a single workspace as though a monitor was briefly disconnected. Often windows are 'maximized' with a strange offset from a monitor's edge, which is fixed by re-maximizing the window. - Sometimes after unlock everything is fine. I have crash reports for the most recent failure in /var/crash, though I'm not sure how to provide them. _usr_bin_gnome-shell.1000.crash is nearly 70MiB -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1059947] Re: xvfb-run munges stdout and stderr together
This bug is still present in xvfb 2:1.20.13-1ubuntu1~20.04.2. It prevents us from using `xvfb-run` when we need to disambiguate STDOUT and STDERR. I'm not familiar with the problem of autopkgtests, but is this still an issue? Can autopkgtests be fixed? If we're an impasse, does it make sense to turn this into a feature request to add a flag to change the redirection behavior? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1059947 Title: xvfb-run munges stdout and stderr together Status in xorg-server package in Ubuntu: Triaged Bug description: It executes the supplied command thusly: DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE "$@" 2>&1 This should be DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE "$@" Leaving the caller to redirect stderr to stdout, or to supply a single fd at their discretion. The side effect of munging the two fd's together is that programs which provide structured data on stdout have their output streams corrupted if they, or any subprocesses they have, happen to write to stderr at an inopportune time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1059947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
If I take the exfat flashdrive to a 20.04 system that does not have exfat-utils/exfat-fuse on it, it works exactly as I expect and mounts as an exfat filesystem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: Invalid Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
I believe if got the exfat-fuse filesystem when I installed exfat-tools in order to mkexfatfs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: Invalid Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
exfat-utils that is -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: Invalid Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866721] Re: Unable to use microphone in chrome
Not really no. Between this bug and https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853008 I was forced to remove chromium-browser and snapd from my system entirely and switch to the Google chrome binaries. Snap was also causing other issues on my system since for some reason the snap version of docker got installed and started interfering with my docker-ce installation from the docker apt repository. It's clearly not ready for prime-time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1866721 Title: Unable to use microphone in chrome Status in chromium-browser package in Ubuntu: Incomplete Bug description: Running Ubuntu 19.10 and the chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 package I am unable to use my microphone with sites that support it, such as discord. I can hear audio from websites like Youtube, but sites that want to use my microphone fail to do so, even though I give permission. I've tested with Hubs by Mozilla, Discord and https://www.onlinemictest.com/ All three properly prompt for permission, but then act as if I refused to give it when choose "allow". If I start chrome from the command line, when this happens I see this in the output [73233:73233:0309/165624.013771:ERROR:pulse_util.cc(300)] pa_operation is nullptr. The https://www.onlinemictest.com/ reports "Microphone not authorized. Please check your media permissions settings." My microphone works fine in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866721] [NEW] Unable to use microphone in chrome
Public bug reported: Running Ubuntu 19.10 and the chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 package I am unable to use my microphone with sites that support it, such as discord. I can hear audio from websites like Youtube, but sites that want to use my microphone fail to do so, even though I give permission. I've tested with Hubs by Mozilla, Discord and https://www.onlinemictest.com/ All three properly prompt for permission, but then act as if I refused to give it when choose "allow". If I start chrome from the command line, when this happens I see this in the output [73233:73233:0309/165624.013771:ERROR:pulse_util.cc(300)] pa_operation is nullptr. The https://www.onlinemictest.com/ reports "Microphone not authorized. Please check your media permissions settings." My microphone works fine in Firefox. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1866721 Title: Unable to use microphone in chrome Status in chromium-browser package in Ubuntu: New Bug description: Running Ubuntu 19.10 and the chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 package I am unable to use my microphone with sites that support it, such as discord. I can hear audio from websites like Youtube, but sites that want to use my microphone fail to do so, even though I give permission. I've tested with Hubs by Mozilla, Discord and https://www.onlinemictest.com/ All three properly prompt for permission, but then act as if I refused to give it when choose "allow". If I start chrome from the command line, when this happens I see this in the output [73233:73233:0309/165624.013771:ERROR:pulse_util.cc(300)] pa_operation is nullptr. The https://www.onlinemictest.com/ reports "Microphone not authorized. Please check your media permissions settings." My microphone works fine in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866132] [NEW] Overview window placement hides some windows in some multi-monitor configs
Public bug reported: I created an extensive report here: https://gitlab.gnome.org/GNOME/mutter/issues/1087 Basically if you have a portrait mode monitor that has a larger vertical resolution than the primary monitor, the primary monitor appears to place the overview previews as if it had that larger vertical resolution, and therefore some overview previews get pushed off the bottom of the monitor. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1866132 Title: Overview window placement hides some windows in some multi-monitor configs Status in yaru-theme package in Ubuntu: New Bug description: I created an extensive report here: https://gitlab.gnome.org/GNOME/mutter/issues/1087 Basically if you have a portrait mode monitor that has a larger vertical resolution than the primary monitor, the primary monitor appears to place the overview previews as if it had that larger vertical resolution, and therefore some overview previews get pushed off the bottom of the monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1866132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Wow. This is all remarkably chill for a bug that boils down to "Chrome can't launch external apps". I just started a new job and I'm trying to set up ubuntu 19.10 as my primary desktop and I'm being blocked by this. Both slack and zoom fail to launch because of this. It also means that apps that want to use Google to authenticate, and thus launch chrome to run the google login and then get a URL callback don't work (Slack in particular). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in udisks2 package in Ubuntu: New Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839856] Re: Screen resolution on external monitor won't go above 2560 x 1080
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1839856 Title: Screen resolution on external monitor won't go above 2560 x 1080 Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: I have an external monitor capable of 3440 x 1440. I am using a Thinkpad T480s. Up until about 2 weeks ago, I could set the resolution of the monitor to 3440 x 1440 just fine. Now when I try, the screen goes black and I have to revert to a lower resolution. The highest it will go now is 2560 x 1080. Lower resolutions work fine as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 12 08:56:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-25-generic, x86_64: installed acpi-call, 1.1.0, 5.0.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2258] InstallationDate: Installed on 2019-02-19 (173 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20L7S01200 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=471b6634-e334-44c7-b898-080ab93327e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET53W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7S01200 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L7S01200:pvrThinkPadT480s:rvnLENOVO:rn20L7S01200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7S01200 dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770271] Re: VegaM support
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770271 Title: VegaM support Status in amd: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in mesa source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-fbdev in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Fix Released Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Fix Released Status in gdm3 source package in Cosmic: Fix Released Status in kmod source package in Cosmic: Invalid Status in linux source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Invalid Status in xserver-xorg-video-fbdev source package in Cosmic: Fix Released Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty. Switching to another tty then back also starts gdm. It happens on bare metal and VM. Originally, when this issue happened there was a plymouth crash reported in bug 1794292 but this issue is still happening without the plymouth crash. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22. 67 May 22 09:36:29
[Desktop-packages] [Bug 1774443] Re: wireless hardblocked and wireless enable button not functional
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1774443 Title: wireless hardblocked and wireless enable button not functional Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and ubuntu. In Windows, system boots with wireless disabled and then pressing the wireless enable button twice enables WiFi. In ubuntu, system boots with wireless disabled and wireless enable button has no functionality either directly or in combination with the fn-key. Module hp_wmi may be the culprit? But disabling this has no effect on hardblock. reference forum post for more detailed info: https://ubuntuforums.org/showthread.php?t=2392934=13772159#post13772159 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 31 10:32:38 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-19 (11 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 172.16.96.1 dev eno1 proto static metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 172.16.96.0/19 dev eno1 proto kernel scope link src 172.16.119.109 metric 100 192.17.90.180 via 172.16.96.1 dev eno1 proto dhcp metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 0357c159-f43c-38f9-8b6f-91bb641d1712 802-3-ethernet 1527780471 Thu 31 May 2018 10:27:51 AM CDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected/org/freedesktop/NetworkManager/Devices/2 Wired connection 1 0357c159-f43c-38f9-8b6f-91bb641d1712 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp8s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled disabled enabled enabled --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: naww 1928 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=96f5e2e6-1a22-453e-84c5-21cb7094a381 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-19 (32 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.42.129 dev enp0s20u3 proto static metric 100 169.254.0.0/16 dev enp0s20u3 scope link metric 1000 192.168.42.0/24 dev enp0s20u3 proto kernel scope link src 192.168.42.168 metric 100 MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.2.6-0ubuntu0.16.04.2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=753230c7-6c88-415a-93f2-c133b9a161b1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
[Desktop-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported Status in HWE Next: Fix Released Status in HWE Next wily series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in linux source package in Wily: Fix Released Status in linux-firmware source package in Wily: Fix Released Bug description: = CURRENT STATUS: Wily(15.10) could not work with and don't need Adam's dkms package 1.0 or 1.1 Wily(15.10) has already fixed the driver part, and the firmware part is in progress. For now, you guys could use 15.10(purge the ath10k-dkms if you tried installing it), and make a copy of https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/ 15.10 will work in a week by a simple `apt upgrade` Distros before 15.10(lower than 4.2 kernel) please keep using the dkms(which will be relocated soon) = Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. Qualcomm Atheros Device [168c:003e] (rev 20) mainline commit d63955b33b3bee45d784ffdfafeb93076c765660 [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0 [6.417386] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [6.417404] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2 [6.417407] ath10k_pci :02:00.0: failed to load spec board file, falling back to generic: -2 [6.417416] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board.bin failed with error -2 [6.417418] ath10k_pci :02:00.0: failed to fetch generic board data: -2 [6.417420] ath10k_pci :02:00.0: failed to fetch board file: -2 [6.417421] ath10k_pci :02:00.0: could not fetch firmware files (-2) [6.417423] ath10k_pci :02:00.0: could not probe fw (-2) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383184/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1773700] Re: [UX390UAK, Realtek ALC295, Speaker, Internal] very loud and crackling sound no matter what sound I play
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1773700 Title: [UX390UAK, Realtek ALC295, Speaker, Internal] very loud and crackling sound no matter what sound I play Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I just installed ubuntu, and immediately had problems of very loud and crackling sound no matter what sound I played. I tried the three solutions listed here https://wiki.ubuntu.com/Audio/PositionReporting, the three of them resulted in no sound at all, and now even if I revert back everything, I can't get any sound out from the speakers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: remuth 1038 F...m pulseaudio /dev/snd/controlC0: remuth 1038 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 27 22:37:20 2018 InstallationDate: Installed on 2018-05-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: remuth 1038 F...m pulseaudio /dev/snd/controlC0: remuth 1038 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768967] Re: Screen randomly flips 180 degrees
*** This bug is a duplicate of bug 1726160 *** https://bugs.launchpad.net/bugs/1726160 ** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1768967 Title: Screen randomly flips 180 degrees Status in iio-sensor-proxy package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 on an HP 350 G1 laptop. According to jstest- gtk, the laptop has a ST LIS3LV02DL Accelerometer with three axes. Axes 0 and 2 remain at 0 (center) no matter what I do. Axis 1 on the other hand senses how much the base of the laptop (the lower half of the clam shell, the part with the keyboard), is tilted. When the laptop is level, the Axis's value should be 0, but it can be anywhere from -20 to 20 while the laptop is being typed on. When its reading is above 0, the screen flips. These two facts cause the screen to flip seemingly randomly while it's being used. Workarround: Lock the screen orientation in GNOME. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 3 15:53:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:21b7] InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1a8b0eca-695f-444c-9cb1-558fe4916595 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 21B7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 46.0B dmi.chassis.asset.tag: Classis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd10/17/2014:svnHewlett-Packard:pnHPPavilion350G1NotebookPC:pvr05A620300:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=242 dmi.product.name: HP Pavilion 350 G1 Notebook PC dmi.product.version: 05A620300 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1768967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
*** This bug is a duplicate of bug 1711101 *** https://bugs.launchpad.net/bugs/1711101 ** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1802350 Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: On a fresh install of ubutu 18.04 all sound work (youtube and system sounds) I connected external hdmi monitor with speakers. I switched audio output to hdmi in settings Then all audio was channeled to external monitor speakers (youtube and system sounds) Then I disconnected external monitor and did not touch the audio output Now only system sounds are working. Youtube in chrome does not work. Audio settings says internal speakers. Firefox youtube has audio normally After reboot same issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 1412 F pulseaudio /dev/snd/controlC1: ed 1412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:28:37 2018 InstallationDate: Installed on 2018-11-01 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11: dmi.product.family: 00 dmi.product.name: Inspiron 5547 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1771749 Title: Ethernet connection lost after few minutes since starting Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: This is the same bug I notified at Bug #1770848 but with a more precise selection of (what I think it is) the package affected and a better description. I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is most everything Ok, but -I think that- the network-manager has a problem. In the last LTS version, Kubuntu 16.04, nor in any Linux version if I remember well, I never lost connection through Ethernet (the only Internet connection with our desktop PC), but the Bionic Beaver loses the connection every now and then, perhaps within few minutes or hours, but several times per day. When the connection is lost, I note that it disappears any info even mention to any network into the network window and the network manager icon becomes red color. Not matter if I unplug and then plug the ethernet cable again, the ethernet connection is not longer detected and only restarting the PC makes the connection to work again. Incidentally, I also have noticed with this version of Kubuntu 18.04 that in my laptop there is also now a similar problem with the scanner: If I plug it in some USB port of the laptop once Kubuntu 18.04 is already running, it's not detected by Xsane. I have to plug it in before than pressing the power button or at the time of starting the OS, for the scanner to be detected by the scanning program (and then only works with Xsane, not if I use Simple Scan or Skanlite, even when it works under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the scanner cable from the USB port it is not detected anymore when plugging it again, and only restarting the laptop makes it to be detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 17 08:24:23 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-11 (5 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s7 proto static metric 100 169.254.0.0/16 dev enp0s7 scope link metric 1000 192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100 IwConfig: enp0s7no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c ethernet 1526538083 jue 17 may 2018 08:21:23 CEST yes 4294967196 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s7 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s7 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 1cc37db8-0db8-3887-acf2-59fbbcd0cb1c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nosotros 1116 F pulseaudio /dev/snd/controlC1: nosotros 1116 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate:
[Desktop-packages] [Bug 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1626731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758942] Re: [i915_bpo] écran noir au démarrage
** Tags added: ubuntu-certified ** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1758942 Title: [i915_bpo] écran noir au démarrage Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: écran noir, impossible de rentrer mon mot de passe au démarrage, lecteur video ne fonctionne pas, impossible de supprimer des logiciels, plantage en cours de session ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 26 16:53:16 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:078c] InstallationDate: Installed on 2018-03-15 (11 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=fbcd4cac-8cb9-4527-af8f-a07d69322204 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.3 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Mar 26 16:32:28 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5574 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762818] Re: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1762818 Title: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Symptom: booting 18.04 kernel reduces resolution available while 17.10 kernel (on 18.04) does not I have a 3 identical monitor setup - all at 2560x1600 native resolution. If I boot the current 18.04 kernel 4.15.0-13-generic then the third monitor does not have the native resolution available. If I reboot with the last 17.10 kernel 4.13.0-37-generic then all monitors have the native resolution available. On the video card the monitors are connected to HDMI, DisplayPort and DVI. On the monitors themselves the connectors are HDMI, DisplayPort and HDMI. (3rd monitor is using DVI to HDMI cable.) Xorg logs show identical EDID information between the kernels. 18.04's just decides to not make 2560x1600 available, having 2048x1080 or 1920x1200 as the highest. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 10 12:17:31 2018 DistUpgraded: 2018-03-31 12:24:30,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev e5) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 450/455/460/560] [1458:230a] LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1456) killed by TERM signal MachineType: Supermicro C7Z170-SQ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=725712a6-f0e0-4da1-b3d1-746a233eb459 ro rootflags=subvol=@ SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-31 (9 days ago) dmi.bios.date: 12/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: Default string dmi.board.name: C7Z170-SQ dmi.board.vendor: Supermicro dmi.board.version: 1.01A dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/19/2016:svnSupermicro:pnC7Z170-SQ:pvr0123456789:rvnSupermicro:rnC7Z170-SQ:rvr1.01A:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: C7Z170-SQ dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37)
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1764087 Title: Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37) Status in X.Org X server: Won't Fix Status in lightdm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 Lenovo T410 with VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Booting from latest kernel ThinkPad-T410 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi connection insofar as it does not connect to my router. Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the time but occasionally has the same effects. I have had to submit this report after booting from 4.13.0.37 in order to submit bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 15 10:40:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (567 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Apr 15 08:52:27 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-09-24 (757 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: xorg-server PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (66 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1763975 Title: DP1.2 daisy-chain flickering Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2 disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-04-01 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: Intel Corporation NUC7i7BNH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763975/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Released Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789949] Re: WiFi-Stick TP-Link T2UH not working
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1789949 Title: WiFi-Stick TP-Link T2UH not working Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: TP-Link Archer T2UH, AC600, version 1 After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 10 I was immediately able to connect). So searching on the web I found some kind of "solution", which it not really working well. on various Forums I found the links to the following drivers: https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916 https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/ From which the first works well on Debian, but fail to compile on ubuntu. And the second one works on ubuntu, but makes the network manager laggin, and won't let me reconnect after some random disconnects, until I restart the NetworkManager.That happens quite often. Plugging it out and back in, also requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, I had to manually copy-paste the git, cause the readme description seemed to be referring to another package. Also, I don't know how secure these drivers are. There is also a driver from TP-Link, which is too old and doesnt work with newer kernels. Mediatek also has driver, but i didnt know how to build them. Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick (thus showing "no networks") and im connected to the internet through another (built-in) device. For the TP-Link T2UH the lsusb will show: Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. while disconnected the "ip a" will show: 9: ra0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff lsb_release -rd shows: Description: Ubuntu 18.04.1 LTS Release: 18.04 Not sure if this is a bug of the Network Manager, or just a missing feature. Maybe it would be good to have a driver for it from the repository. Or to somehow integrate the chip-support into the system. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 30 17:51:16 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-08-26 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/4 uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7 /org/freedesktop/NetworkManager/ActiveConnection/7 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- ra0 wifi unmanaged/org/freedesktop/NetworkManager/Devices/5 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: a 2175 F pulseaudio /dev/snd/pcmC0D0p: a 2175 F...m pulseaudio /dev/snd/controlC0: a 2175 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-08-26 (16 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute:
[Desktop-packages] [Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1797190 Title: It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive Status in Linux: Confirmed Status in gnome-disk-utility package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: List: linux-usb https://marc.info/?l=linux-usb=153919676204905=2 --- https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104 --- Hello, I am trying to format a pendrive of 2TB(Purchased in China for ebay). What I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be accessed, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1797190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1797432 Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: Headphone jack stopped working. Speakers do work. Nevermind issue was on my end not sure how to close bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 11 13:12:34 2018 InstallationDate: Installed on 2018-01-05 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification appears even when all notifications disabled
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification appears even when all notifications disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798083] Re: Nvidia doesn't work after I upgraded to 4.19rc8
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1798083 Title: Nvidia doesn't work after I upgraded to 4.19rc8 Status in linux package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Bug description: I upgraded my linux to 4.19rc8 When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is undefined` Then I checked,nvidia doesn't work. $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is undefined nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled displays on GPU 0 (Missing Extension). nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected displays on GPU 0 (Missing Extension). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 20:18:27 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-10-generic, x86_64: installed nvidia, 390.87, 4.18.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1b90] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1b90] InstallationDate: Installed on 2018-10-10 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc8-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: New Status in firefox package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: New Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802806] Re: Unable to connect to wifi network after lubuntu install
** Tags added: cscc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1802806
Title:
Unable to connect to wifi network after lubuntu install
Status in linux package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Hi,
I had ubuntu 16 and my home wifi never had issues. Now i installed lubuntu
bionic now i can never connect to my home wifi.
I am getting below message on running command -
nmcli dev wifi connect myssid password mypassword
Error: Connection activation failed: (5) IP configuration could not be
reserved (no available address, timeout, etc.)
I can not use my system any more and any help will be appreciated to
resolve the issue. I posted this issues in askubuntu and no response
so far.
Please help. Please let me know any more information needed.
System details :
Laptop - hp
"Realtek RTL8188EE Wireless Network Adapter (RTL8188EE mini-PCIe card)"
wifi (rtl8188ee), 40:B8:9A:09:D7:9E, hw, mtu 1500
Note - I can connect to hotspot network on my phone with no issues.
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18
Uname: Linux 4.15.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Sun Nov 11 19:59:39 2018
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2018-08-22 (81 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
IpRoute:
default via 172.20.10.1 dev wlo1 proto dhcp metric 600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.20.10.0/28 dev wlo1 proto kernel scope link src 172.20.10.7 metric 600
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
ProcEnviron:
LANGUAGE=en_US
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATEDBUS-PATH
CONNECTION CON-UUID CON-PATH
wlo1 wifi connected/org/freedesktop/NetworkManager/Devices/4
iPhone 1eaf289fc-1e98-4e6b-a075-766c11fc9d49
/org/freedesktop/NetworkManager/ActiveConnection/6
docker0 bridgeconnected/org/freedesktop/NetworkManager/Devices/2
docker0 f03e7a66-563b-4936-ad48-1cc0b87e14f7
/org/freedesktop/NetworkManager/ActiveConnection/1
enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/3
-- ----
lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1
-- ----
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.10.6 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-37-generic.
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: akanse 1892 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9091 irq 93'
Mixer name : 'Realtek ALC3227'
Components : 'HDA:10ec0282,103c21de,0013
HDA:80862882,80860101,0010'
Controls : 29
Simple ctrls : 12
CurrentDesktop: LXDE
DistroRelease: Ubuntu 18.04
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2018-08-22 (81 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
IpRoute:
default via 172.20.10.1 dev wlo1 proto dhcp metric 600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.20.10.0/28 dev wlo1 proto kernel scope link src 172.20.10.7 metric 600
Lsusb:
Bus 002 Device 002: ID 0bda:0401 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd
(Foxlink)
Bus 001 Device 002: ID 0bda:5401 Realtek
[Desktop-packages] [Bug 1805821] Re: [amdgpu] GUI performance is poor
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1805821 Title: [amdgpu] GUI performance is poor Status in linux package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: Response is slow, amdgpu driver gives warning in dmesg which is below [0.00] Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 (Ubuntu 4.15.0-36.39-generic 4.15.18) [0.00] random: get_random_u32 called from bsp_init_amd+0x255/0x2a0 with crng_init=0 [0.966765] amd_uncore: AMD NB counters detected [1.165305] pcie_mp2_amd: AMD(R) PCI-E MP2 Communication Driver Version: 1.0 [1.716922] amdkcl: loading out-of-tree module taints kernel. [1.716947] amdkcl: module verification failed: signature and/or required key missing - tainting kernel [1.827886] [drm] amdgpu kernel modesetting enabled. [1.827887] [drm] amdgpu version: 18.30.2.15 [1.833528] fb: switching to amdgpudrmfb from EFI VGA [1.850977] amdgpu :00:01.0: VRAM: 1024M 0x00F4 - 0x00F43FFF (1024M used) [1.850979] amdgpu :00:01.0: GTT: 1024M 0x - 0x3FFF [1.851137] [drm] amdgpu: 1024M of VRAM memory ready [1.851139] [drm] amdgpu: 14975M of GTT memory ready. [1.851291] [drm] amdgpu: dpm initialized [1.853722] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! type 0 expected 3 [1.853779] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.853825] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.853872] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [2.064038] fbcon: amdgpudrmfb (fb0) is primary device [2.128334] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device [2.145953] [drm] Initialized amdgpu 3.26.0 20150101 for :00:01.0 on minor 0 [5.265031] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [6.277293] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [7.289439] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [8.301565] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [9.313691] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 10.325849] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 11.338007] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 12.350159] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 13.362305] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 14.374463] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 14.394355] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, giving up!!! [ 14.394396] [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR* set_powergating_state of IP block failed -110 [ 15.420234] [drm:amdgpu_vce_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out. [ 15.420321] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 12 (-110). [ 15.420369] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110). [ 23.736730] EDAC amd64: Node 0: DRAM ECC disabled. [ 23.736731] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. [ 1566.370793] audit: type=1400 audit(1543500426.678:40): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/libdrm/amdgpu.ids" pid=7169 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Takes too for software center to install .deb package where as it happens in a few seconds in terminal via dpkg -i. Problems are after installation of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop:
[Desktop-packages] [Bug 1806232] Re: Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1806232 Title: Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: There is screen tearing on the left side of the screen, and it's especially apparent when there's motion on the entire screen. This is happening on Ubuntu 18.10 on an Asus T102HA with an Atom x5 Cherry Trail. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 00:59:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1400] InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. T102HA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=6d4342e4-1f2b-42ea-850e-63e34c955cd3 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T102HA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T102HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT102HA.204:bd07/18/2016:svnASUSTeKCOMPUTERINC.:pnT102HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT102HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T102HA dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 10HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr10HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: RF511/RF411/RF711
[Desktop-packages] [Bug 1810388] Re: syslog filled with drm messages 40 times per second
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1810388 Title: syslog filled with drm messages 40 times per second Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Bug description: Hi all, I don't really know when it exactly began. From /var/log/syslog : Jan 3 09:42:42 localhost kernel: [32659.271016] [drm:drm_mode_addfb2 [drm]] [FB:74] Jan 3 09:42:42 localhost kernel: [32659.300800] [drm:drm_mode_addfb2 [drm]] [FB:89] There are similar bugs that have been already noticed, but none of them helped me. Changing desktop environment to a non-gnome desktop stops messages. My environment (export cmd) : declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/etc/xdg" declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME" declare -x XDG_DATA_DIRS="/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop" declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/userprofile" declare -x XDG_MENU_PREFIX="gnome-" declare -x XDG_RUNTIME_DIR="/run/user/1000" declare -x XDG_SEAT="seat0" declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" declare -x XDG_SESSION_DESKTOP="ubuntu" declare -x XDG_SESSION_ID="c2" declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0" declare -x XDG_SESSION_TYPE="x11" declare -x XDG_VTNR="7" My kernel : 4.15.0-43-generic Ubuntu 18.04.01 LTS Graphic : Intel Haswell Mobile Any help is appreciated Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jan 3 09:38:35 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed virtualbox, 5.2.18, 4.19.0-041900-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a] InstallationDate: Installed on 2016-12-20 (743 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS13 9333 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=19d7298f-74c8-4a78-9f17-88b9f04bbc3a ro net.ifnames=0 biosdevname=0 acpi=force plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/31/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay System dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1159358] Re: 04a9:1736 [HP Pavillion dm3-1109TU] USB Printer needs replug to work after boot
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1159358 Title: 04a9:1736 [HP Pavillion dm3-1109TU] USB Printer needs replug to work after boot Status in cups package in Ubuntu: Expired Status in linux package in Ubuntu: Incomplete Bug description: While working a moment on LibreOffice Calc found that facts: - Print job was pending (printer not printing). Found that the printer was not working. Usually if the problem persists, plug out the USB cable and then plug in again. I don't find any solution other than replugging printer USB cable to wake up the printer. HP Pavillion dm3-1109TU Printer: Canon Pixma MX328 (driver: Canon PIXMA MX300 - CUPS+Gutenprint v5.2.8-pre1) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-39.62-generic-pae 3.2.39 Uname: Linux 3.2.0-39-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CompizPlugins: [core,composite,opengl,imgjpeg,decor,imgpng,snap,obs,gnomecompat,vpswitch,compiztoolbox,resize,regex,dbus,mousepoll,grid,place,animation,move,session,workarounds,switcher,expo,wall,fade,scale] CompositorRunning: compiz Date: Sun Mar 24 15:55:26 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3649] Subsystem: Hewlett-Packard Company Device [103c:3649] InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Hewlett-Packard HP Pavilion dm3 Notebook PC MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-39-generic-pae root=UUID=2E2462FD2462C783 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2010 dmi.bios.vendor: Insyde Corp. dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3649 dmi.board.vendor: Hewlett-Packard dmi.board.version: 41.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrF.19:bd11/16/2010:svnHewlett-Packard:pnHPPaviliondm3NotebookPC:pvr048711241F1011012:rvnHewlett-Packard:rn3649:rvr41.3D:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dm3 Notebook PC dmi.product.version: 048711241F1011012 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1159358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1689408] Re: System hang when utilising OpenGL 4.5 features
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1689408 Title: System hang when utilising OpenGL 4.5 features Status in Mesa: Fix Released Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: New Bug description: I've found this to be easily reproducible via unigine's heaven benchmark, which uses tessellation and other features extensively. Simply creating a OpenGL 4.5 context will not trigger the hang, and you must explicitly request an OGL 4+ context as the default will only be 3.0. On a successful trigger, the screen may flicker on and off a few times and eventually hang completely on a black screen, there's no way to recover the system from this state bar a power cycle (ie hold the power button). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paulh 1405 F pulseaudio /dev/snd/controlC0: paulh 1405 F pulseaudio CurrentDesktop: KDE Date: Tue May 9 09:14:09 2017 InstallationDate: Installed on 2017-01-05 (123 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1C dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8133 dmi.board.vendor: HP dmi.board.version: KBC Version 98.0E dmi.chassis.asset.tag: 5CG6124XBK dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1689408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Won't Fix Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788044] Re: task kworker blocked for more than 120 seconds nouveau
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1788044 Title: task kworker blocked for more than 120 seconds nouveau Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: I was using chromium when the whole system GUI stopped responding at 15:42. This corresponds to the system journal at that point: Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: runlist 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: channel 15: killed Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: fifo: engine 0: scheduled for recovery Aug 20 15:42:56 dh3930 kernel: nouveau :01:00.0: compiz[7682]: channel 15 killed! Aug 20 15:45:50 dh3930 kernel: INFO: task kworker/u24:4:14623 blocked for more than 120 seconds. Aug 20 15:45:50 dh3930 kernel: Not tainted 4.15.0-32-generic #35-Ubuntu Aug 20 15:45:50 dh3930 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 20 15:45:50 dh3930 kernel: kworker/u24:4 D0 14623 2 0x8000 Aug 20 15:45:50 dh3930 kernel: Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Aug 20 15:45:50 dh3930 kernel: Call Trace: Aug 20 15:45:50 dh3930 kernel: __schedule+0x291/0x8a0 Aug 20 15:45:50 dh3930 kernel: schedule+0x2c/0x80 Aug 20 15:45:50 dh3930 kernel: schedule_timeout+0x1cf/0x350 Aug 20 15:45:50 dh3930 kernel: ? nvif_object_ioctl+0x47/0x50 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_bo_rd32+0x2a/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nv84_fence_read+0x2e/0x30 [nouveau] Aug 20 15:45:50 dh3930 kernel: ? nouveau_fence_no_signaling+0x2a/0x80 [nouveau] Aug 20 15:45:50 dh3930 kernel: dma_fence_default_wait+0x1c7/0x260 Aug 20 15:45:50 dh3930 kernel: ? dma_fence_release+0xa0/0xa0 Aug 20 15:45:50 dh3930 kernel: dma_fence_wait_timeout+0x3e/0xf0 Aug 20 15:45:50 dh3930 kernel: drm_atomic_helper_wait_for_fences+0x63/0xc0 [drm_kms_helper] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_tail+0x55/0x3b10 [nouveau] Aug 20 15:45:50 dh3930 kernel: nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Aug 20 15:45:50 dh3930 kernel: process_one_work+0x1de/0x410 Aug 20 15:45:50 dh3930 kernel: worker_thread+0x32/0x410 Aug 20 15:45:50 dh3930 kernel: kthread+0x121/0x140 Aug 20 15:45:50 dh3930 kernel: ? process_one_work+0x410/0x410 Aug 20 15:45:50 dh3930 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Aug 20 15:45:50 dh3930 kernel: ret_from_fork+0x35/0x40 The 'blocked for more than 120 seconds' message and call trace repeated every ~121 seconds until I rebooted. At that point, the following additional line appeared with the 'blocked for more than 120 seconds' message: Aug 20 16:01:51 dh3930 kernel: nouveau :01:00.0: chromium- browse[14187]: failed to idle channel 20 [chromium-browse[14187]] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2460 F pulseaudio /dev/snd/controlC0: david 2460 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 20 16:07:40 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9e4f3d6a-f1b3-40c0-8c97-97d861a7ce11 InstallationDate: Installed on 2016-10-24 (664 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-32-generic root=UUID=311cc681-166d-47bd-847d-f41c81578c1a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-01 (110 days ago) dmi.bios.date: 05/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1778555] Re: My Webcam does not work with Cheese
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1778555 Title: My Webcam does not work with Cheese Status in cheese package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Cheese says that there is no video cam. The same webcam (connected through USB 3) does work in Skype. From dmesg: [1.329876] usb 3-2: New USB device found, idVendor=17a1, idProduct=0128 [1.329877] usb 3-2: New USB device strings: Mfr=32, Product=38, SerialNumber=0 [1.329878] usb 3-2: Product: USB2.0 JPEG WebCam [1.329879] usb 3-2: Manufacturer: TASCORP From dmidecode (about my motherboard): Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: H67A-UD3H Version: Serial Number: UUID: ----1C6F65886700 Wake-up Type: Power Switch SKU Number: Family: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ dpkg -s cheese Package: cheese Status: install ok installed Priority: optional Section: gnome Installed-Size: 437 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.0-1ubuntu1 Depends: libc6 (>= 2.4), libcanberra-gtk3-0 (>= 0.25), libcheese-gtk25 (>= 3.18.0), libcheese8 (>= 3.18.0), libclutter-1.0-0 (>= 1.16), libclutter-gtk-1.0-0 (>= 0.91.8), libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 (>= 2.39.90), libgnome-desktop-3-17 (>= 3.17.92), libgstreamer1.0-0 (>= 1.0.0), libgtk-3-0 (>= 3.13.7), cheese-common (>= 3.28.0-1ubuntu1), gnome-video-effects Recommends: gvfs, yelp Suggests: gnome-video-effects-frei0r Description: tool to take pictures and videos from your webcam A webcam application that supports image and video capture. Makes it easy to take photos and videos of you, your friends, pets or whatever you want. Allows you to apply fancy visual effects, fine-control image settings and has features such as Multi-Burst mode, Countdown timer for photos. Homepage: https://wiki.gnome.org/Apps/Cheese Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 19:11:59 2018 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67A-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67A-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67A-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67A-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: porton 1424 F pulseaudio /dev/snd/controlC0: porton 1424 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601 [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4734.238757] usb 3-4: Product: 802.11 n WLAN [ 4734.238772] usb 3-4: Manufacturer: MediaTek [ 4734.238775] usb 3-4: SerialNumber: 1.0 [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500 [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146 [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110 [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110 [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110 [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110 [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110 [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110 [ 4757.730870] usbcore: registered new interface driver mt7601u // end $> sudo ifconfig -a // do not list any new interface 2) DPO_MT7601U_LinuxSTA_3.0.0.4_20130913.tar.bz2
[Desktop-packages] [Bug 1790249] Re: desktop sharing won't start after upgrading to 18.04
*** This bug is a duplicate of bug 1741027 *** https://bugs.launchpad.net/bugs/1741027 ** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1790249 Title: desktop sharing won't start after upgrading to 18.04 Status in linux package in Ubuntu: Incomplete Status in unity-control-center package in Ubuntu: New Bug description: First time destop sharing was started the system detected a problem which was reported -- so there should be some info for you there already. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:17:29 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in upower source package in Bionic: Fix Released Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mutter source package in Bionic: Fix Released Bug description: [ Description ] GNome shell crashes after Xorg loggin [ Test case ] From GDM login in a GNOME Ubuntu session (so Xorg). It should start with no issues [ Regression potential ] We were deferencing a NULL pointer while outputting an error. This is pretty safe. Although the session might still not run properly as per a driver issue to be addressed in linux package. --- https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: Invalid Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys
** Tags added: cscc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/214786 Title: Apple USB ISO keyboard has incorrectly swapped keys Status in Mactel Support: Confirmed Status in linux package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Since upgrading kernel to version 2.6.24-12.22 two keys are now swapped on my Apple USB aluminium keyboard with danish layout. Now the keys "<" and "½" are swapped and no longer matches the actual print on the keycaps. The error is isolated to the following commit: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748 This commit introduced a key swapping for all "ISO" type Apple keyboards. In my case this swapping is incorrect, and generally it seems like a very bad idea to perform hard coded locale specific key mapping in kernel space as this is also done several places in user space. The included patch reverts the behavior to the default that matches the keycap printing. To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/214786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828134] Re: Wifi not working after suspend/resume cycle
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1828134 Title: Wifi not working after suspend/resume cycle Status in NetworkManager: Unknown Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1828134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830867] Re: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1830867 Title: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a new laptop and I cannot manage to have a clean and stable sound with HDMI. It happens every time I play a track on Spotify (desktop and web), sometimes from a VLC radio or a youtube video, never from a video with VLC yet. I'm attaching a record of what I hear when I play a track from Spotify. I created two reports. One during a Spotify playing, when it is crackling and after the sound started to crackle everywhere: http://alsa-project.org/db/?f=4e7d724718a48179fa2f3740d5f3e634ad75def9 Another after a fresh reboot, where the sound is correct with at least YouTube: http://alsa-project.org/db/?f=2ec68f888bb93a0de648d48fd720f54cee644564 Just after this last report, the sound is still crackling with Spotify and VLC radio. Not with Youtube. A diff on theses files gives some differences I find suspect. Are there expected ? Do you have an idea where the problem comes from ? Thank you for your support ! Edouard --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edouard1677 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-05-28T23:16:01.413832 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in HWE Next: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Triaged Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Triaged Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Triaged Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1837683 Title: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: environment: - XPS-13-938 - connect 5G ac wifi - disabled suspend in power setting - disabled blank screen in power setting steps: - play 4k video by chrome on youtube[1] overnight symptom: - after about 8 hours, the screen is black and keyboard and mouse can not wake up screen. - the audio of 4K video is still playing, I can hear that when screen is black. - magic key still work, so I can reboot system by magic key. - a repeat error message in syslog: " Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): Page flip failed: Invalid argument Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE) modeset(0): present flip failed " [1] https://www.youtube.com/watch?v=pkKBXH2qc_I=11701s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18 Uname: Linux 4.15.0-1047-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 09:47:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed on 2019-07-20 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1047-oem root=UUID=77efb06b-1ce6-4749-a131-67f57aa8b21b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
** Tags added: bjf-tracking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1514249] Re: libreoffice window corruption after resize
This probly should be closed since it isn't an issue in 18.04, maybe not an issue in 16.04 either? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1514249 Title: libreoffice window corruption after resize Status in libreoffice package in Ubuntu: Confirmed Bug description: When resizing a libreoffice calc window it is corrupted. It sounds like it is similar to this: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/889212 from several years ago. The fix is the same, install libreoffice-gtk. The bug is mentioned hear also. https://sites.google.com/site/easylinuxtipsproject/libreoffice ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 8 14:07:43 2015 InstallationDate: Installed on 2015-11-08 (0 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1514249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712663] Re: Visioneer RoadWarrior Scanner [Sane]
Same problem in Ubuntu 18.04 LTS. Works fine in Win10 and is all black in Linux. The difference though: The light isn't enabled in Linux. The white light is on in Windows, but there is only a dim red light only in Linux. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1712663 Title: Visioneer RoadWarrior Scanner [Sane] Status in simple-scan package in Ubuntu: Expired Bug description: I just picked up one of these portable scanners, it works well in Windows. In Linux and either xsane or simple-scan however it always scans a completely black page. Thinking it was a calibration issue I ran:- SANE_DEBUG_GENESYS=255 scanimage -d genesys --calibrate 2>calibrate.log Which at first reported it couldn't find the correct sheet. I made one using: http://www.fixya.com/support/t17003105-calibration_sheet_visioneer_roadwarrior and the errors went away This is resolved. The calibration value "01 e8 00 00 00" is written. There is still an error in the log but it appears to be OK. I'm unsure if it's calibration anyhow as it worked OK-ish in Windows (washed out, but had an image). Scans are still completely black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1712663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly
I see a difference in the ALSA driver version being used now so maybe this problem was recently fixed? # in alsa-info output !!ALSA Version !! # Before k4.14.55-1-MANJARO # Now k4.14.71-1-MANJARO -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1619866 Title: Lenovo G50-45 inverted microphone not detected properly Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: New Bug description: System: Lenovo G50-45 with Lubuntu 16.04 Alsa information: http://www.alsa- project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f Internal microphone does not pick up sound by default. When I mute one channel, it works (this is not a good workaround since some application, such as Facebook Messenger, unmute both channels and set them to the same level automatically). --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: silvana2681 F pulseaudio /dev/snd/controlC1: silvana2681 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f InstallationDate: Installed on 2016-09-02 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 80E3 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN25WW(V1.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3 dmi.product.version: Lenovo G50-45 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly
Any idea the problem with Skype I mentioned above? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1619866 Title: Lenovo G50-45 inverted microphone not detected properly Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: New Bug description: System: Lenovo G50-45 with Lubuntu 16.04 Alsa information: http://www.alsa- project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f Internal microphone does not pick up sound by default. When I mute one channel, it works (this is not a good workaround since some application, such as Facebook Messenger, unmute both channels and set them to the same level automatically). --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: silvana2681 F pulseaudio /dev/snd/controlC1: silvana2681 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f InstallationDate: Installed on 2016-09-02 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 80E3 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN25WW(V1.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3 dmi.product.version: Lenovo G50-45 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly
I cannot reproduce the problem now. Recording via arecord with channels locked in pavucontrol works OK. The problem seems to only still exist using Skype (my version is 8.29.0.50) which strangely is not allowing me to unlock the channels. My Alsa-info: http://www.alsa-project.org/db/?f=9dd883825d6f6c832cfc36c9eb1eaafa347fc4d8 System: Host: G50 Kernel: 4.14.71-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Xfce 4.12.4 Distro: Manjaro Linux Machine: Type: Laptop System: LENOVO product: 80E3 v: Lenovo G50-45 serial: Mobo: LENOVO model: Lancer 5B2 v: 31900058 STD serial: UEFI: LENOVO v: A2CN45WW(V2.13) date: 08/04/2016 Battery: ID-1: BAT1 charge: 23.2 Wh condition: 23.2/31.7 Wh (73%) model: LENOVO PABAS0241231 status: Full CPU: Topology: Quad Core model: AMD A6-6310 APU with AMD Radeon R4 Graphics bits: 64 type: MCP arch: Puma rev: 1 L2 cache: 2048 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 14378 Speed: 1648 MHz min/max: 1000/1800 MHz Core speeds (MHz): 1: 1681 2: 1505 3: 1296 4: 1556 Graphics: Device-1: AMD Mullins [Radeon R4/R5 Graphics] driver: radeon v: kernel bus ID: 00:01.0 Display: x11 server: X.Org 1.20.1 driver: ati,radeon unloaded: modesetting resolution: 1366x768~60Hz, 1920x1080~60Hz OpenGL: renderer: AMD MULLINS (DRM 2.50.0 4.14.71-1-MANJARO LLVM 6.0.1) v: 4.5 Mesa 18.2.1 direct render: Yes Audio: Device-1: AMD Kabini HDMI/DP Audio driver: snd_hda_intel v: kernel bus ID: 00:01.1 Device-2: AMD FCH Azalia driver: snd_hda_intel v: kernel bus ID: 00:14.2 Sound Server: ALSA v: k4.14.71-1-MANJARO Network: Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be v: kernel port: 3000 bus ID: 01:00 IF: wlp1s0 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8168 v: 8.045.08-NAPI port: 2000 bus ID: 02:00 IF: enp2s0 state: down mac: Drives: Local Storage: total: 465.76 GiB used: 103.86 GiB (22.3%) ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB Partition: ID-1: / size: 144.89 GiB used: 103.55 GiB (71.5%) fs: ext4 dev: /dev/sda5 ID-2: swap-1 size: 6.96 GiB used: 260.8 MiB (3.7%) fs: swap dev: /dev/sda6 Sensors: System Temperatures: cpu: 51.2 C mobo: N/A gpu: radeon temp: 50 C Fan Speeds (RPM): N/A Info: Processes: 227 Uptime: 2d 15h 08m Memory: 6.77 GiB used: 4.28 GiB (63.2%) Init: systemd Compilers: gcc: 8.2.1 Shell: bash v: 4.4.23 inxi: 3.0.21 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1619866 Title: Lenovo G50-45 inverted microphone not detected properly Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: New Bug description: System: Lenovo G50-45 with Lubuntu 16.04 Alsa information: http://www.alsa- project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f Internal microphone does not pick up sound by default. When I mute one channel, it works (this is not a good workaround since some application, such as Facebook Messenger, unmute both channels and set them to the same level automatically). --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: silvana2681 F pulseaudio /dev/snd/controlC1: silvana2681 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f InstallationDate: Installed on 2016-09-02 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 80E3 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN25WW(V1.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3
[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788926] [NEW] package nvidia-prime 0.8.2 failed to install/upgrade: there is no script in the new version of the package - giving up
Public bug reported: I am upgrading the environment in which I have NVIDIA processes run, and they need to be able to find the nvidia libraries and everything else needed to work with my (very expensive) NVIDIA card that I require. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.2 ProcVersionSignature: Ubuntu 4.4.0-133.159-lowlatency 4.4.134 Uname: Linux 4.4.0-133-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 24 12:24:18 2018 ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2016-11-21 (641 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.27 SourcePackage: nvidia-prime Title: package nvidia-prime 0.8.2 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to bionic on 2018-08-24 (0 days ago) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages ** Attachment removed: "Df.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180416/+files/Df.txt ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180417/+files/Dmesg.txt ** Attachment removed: "DpkgHistoryLog.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180418/+files/DpkgHistoryLog.txt ** Attachment removed: "AptOrdering.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180414/+files/AptOrdering.txt ** Attachment removed: "NonfreeKernelModules.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180413/+files/NonfreeKernelModules.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+attachment/5180415/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1788926 Title: package nvidia-prime 0.8.2 failed to install/upgrade: there is no script in the new version of the package - giving up Status in nvidia-prime package in Ubuntu: New Bug description: I am upgrading the environment in which I have NVIDIA processes run, and they need to be able to find the nvidia libraries and everything else needed to work with my (very expensive) NVIDIA card that I require. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.2 ProcVersionSignature: Ubuntu 4.4.0-133.159-lowlatency 4.4.134 Uname: Linux 4.4.0-133-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 24 12:24:18 2018 ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2016-11-21 (641 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.27 SourcePackage: nvidia-prime Title: package nvidia-prime 0.8.2 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to bionic on 2018-08-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1788926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed
In bug 994921 it suggests commenting out line 23 of /etc/apport/crashdb.conf. However the crashdb.conf file on my Cosmic system does not have a line containing 'poblem_types'. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1788691 Title: [Cosmic] gnome-shell crashes when windows key pressed Status in gnome-shell package in Ubuntu: New Bug description: This is not reproducible for every press of the windows key but usually happens after an hour of normal desktop use. This nugget was found in /var/log/syslog: Aug 23 12:39:42 fog gnome-shell[6796]: JS ERROR: TypeError: this._init is undefined#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:572:24#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/workspacesView.js:502:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:285:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:556:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:542:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:672:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:200:13 Aug 23 12:39:42 fog gnome-shell[6796]: clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed Aug 23 12:40:00 fog gnome-shell[6796]: message repeated 5 times: [ clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed] Aug 23 12:40:12 fog org.gnome.SettingsDaemon.MediaKeys.desktop[7017]: [7203:7219:0823/124012.608378:ERROR:socket_stream.cc(210)] Closing stream with result -7 Aug 23 12:40:22 fog org.gnome.SettingsDaemon.MediaKeys.desktop[7017]: [7203:7219:0823/124022.848403:ERROR:socket_stream.cc(210)] Closing stream with result -7 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (373 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788691/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed
1. No crash files i /var/crash. 2. Nothing recent at https://errors.ubuntu.com. 3. Will give this a try. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1788691 Title: [Cosmic] gnome-shell crashes when windows key pressed Status in gnome-shell package in Ubuntu: New Bug description: This is not reproducible for every press of the windows key but usually happens after an hour of normal desktop use. This nugget was found in /var/log/syslog: Aug 23 12:39:42 fog gnome-shell[6796]: JS ERROR: TypeError: this._init is undefined#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:572:24#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/workspacesView.js:502:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:285:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:556:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:542:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:672:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:200:13 Aug 23 12:39:42 fog gnome-shell[6796]: clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed Aug 23 12:40:00 fog gnome-shell[6796]: message repeated 5 times: [ clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed] Aug 23 12:40:12 fog org.gnome.SettingsDaemon.MediaKeys.desktop[7017]: [7203:7219:0823/124012.608378:ERROR:socket_stream.cc(210)] Closing stream with result -7 Aug 23 12:40:22 fog org.gnome.SettingsDaemon.MediaKeys.desktop[7017]: [7203:7219:0823/124022.848403:ERROR:socket_stream.cc(210)] Closing stream with result -7 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (373 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788691/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed
** Description changed: + This is not reproducible for every press of the windows key but usually + happens after an hour of normal desktop use. + + This nugget was found in /var/log/syslog: + Aug 23 12:39:42 fog gnome-shell[6796]: JS ERROR: TypeError: this._init is undefined#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:572:24#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/workspacesView.js:502:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:285:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:556:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:542:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:672:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:200:13 Aug 23 12:39:42 fog gnome-shell[6796]: clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed Aug 23 12:40:00 fog gnome-shell[6796]: message repeated 5 times: [ clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed] Aug 23 12:40:12 fog org.gnome.SettingsDaemon.MediaKeys.desktop[7017]: [7203:7219:0823/124012.608378:ERROR:socket_stream.cc(210)] Closing stream with result -7 Aug 23 12:40:22 fog org.gnome.SettingsDaemon.MediaKeys.desktop[7017]: [7203:7219:0823/124022.848403:ERROR:socket_stream.cc(210)] Closing stream with result -7 - --- + --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (373 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: - TERM=tmux-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=tmux-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1788691 Title: [Cosmic] gnome-shell crashes when windows key pressed Status in gnome-shell package in Ubuntu: New Bug description: This is not reproducible for every press of the windows key but usually happens after an hour of normal desktop use. This nugget was found in /var/log/syslog: Aug 23 12:39:42 fog gnome-shell[6796]: JS ERROR: TypeError: this._init is undefined#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:572:24#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/workspacesView.js:502:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/viewSelector.js:285:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_animateVisible@resource:///org/gnome/shell/ui/overview.js:556:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012show@resource:///org/gnome/shell/ui/overview.js:542:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012toggle@resource:///org/gnome/shell/ui/overview.js:672:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_initializeUI/<@resource:///org/gnome/shell/ui/main.js:200:13 Aug 23 12:39:42 fog gnome-shell[6796]: clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed Aug 23 12:40:00 fog gnome-shell[6796]: message repeated 5 times: [ clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed] Aug 23 12:40:12 fog org.gnome.SettingsDaemon.MediaKeys.desktop[7017]: [7203:7219:0823/124012.608378:ERROR:socket_stream.cc(210)] Closing stream with result -7 Aug 23 12:40:22 fog org.gnome.SettingsDaemon.MediaKeys.desktop[7017]: [7203:7219:0823/124022.848403:ERROR:socket_stream.cc(210)] Closing stream with result -7 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop:
[Desktop-packages] [Bug 1786948] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1786948/+attachment/5175214/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786948 Title: Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load Status in gnome-shell package in Ubuntu: Confirmed Bug description: The title says it all at this point. Happy to gather additional logs. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786948] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1786948/+attachment/5175215/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786948 Title: Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load Status in gnome-shell package in Ubuntu: Confirmed Bug description: The title says it all at this point. Happy to gather additional logs. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786948] Re: Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load
apport information ** Tags added: apport-collected cosmic wayland-session ** Description changed: The title says it all at this point. Happy to gather additional logs. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.10 + EcryptfsInUse: Yes + InstallationDate: Installed on 2017-08-14 (364 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) + Package: gnome-shell 3.29.90-1ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=tmux-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 + Tags: wayland-session cosmic + Uname: Linux 4.17.0-7-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1786948/+attachment/5175213/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786948 Title: Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load Status in gnome-shell package in Ubuntu: Confirmed Bug description: The title says it all at this point. Happy to gather additional logs. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) Package: gnome-shell 3.29.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Tags: wayland-session cosmic Uname: Linux 4.17.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786948] [NEW] Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load
Public bug reported: The title says it all at this point. Happy to gather additional logs. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786948 Title: Latest Cosmic dist-upgrade causes shell extensions (dash to dock, hide top bar) to fail to load Status in gnome-shell package in Ubuntu: New Bug description: The title says it all at this point. Happy to gather additional logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly
Here is my alsa-info report: http://www.alsa- project.org/db/?f=be279d4be4647c2e25da163de10f080c327561d0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1619866 Title: Lenovo G50-45 inverted microphone not detected properly Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: New Bug description: System: Lenovo G50-45 with Lubuntu 16.04 Alsa information: http://www.alsa- project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f Internal microphone does not pick up sound by default. When I mute one channel, it works (this is not a good workaround since some application, such as Facebook Messenger, unmute both channels and set them to the same level automatically). --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: silvana2681 F pulseaudio /dev/snd/controlC1: silvana2681 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f InstallationDate: Installed on 2016-09-02 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 80E3 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN25WW(V1.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3 dmi.product.version: Lenovo G50-45 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly
This problem still exists. I think it's due to #1 some notebooks having an inverted mic channel and #2 Pulseaudio auto/dynamic-setting mic levels of both channels equal. So when you turn down one channel to allow it to work (workaround) Pulseaudio sets it back which disables the mic again. I don't know if this problem should be resolved in the Kernel or Pulseaudio. But I have seen an "inverted mic" is a common problem that many people have and struggle with getting their mic to work as a result. I have the Lenovo G50-45 with updated BIOS: A2CN45WW(V2.13) Running the latest Manjaro distro w/kernel 4.14: Linux G50 4.14.55-1-MANJARO 08/04/2016 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1619866 Title: Lenovo G50-45 inverted microphone not detected properly Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: New Bug description: System: Lenovo G50-45 with Lubuntu 16.04 Alsa information: http://www.alsa- project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f Internal microphone does not pick up sound by default. When I mute one channel, it works (this is not a good workaround since some application, such as Facebook Messenger, unmute both channels and set them to the same level automatically). --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: silvana2681 F pulseaudio /dev/snd/controlC1: silvana2681 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f InstallationDate: Installed on 2016-09-02 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 80E3 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN25WW(V1.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3 dmi.product.version: Lenovo G50-45 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1619866 Title: Lenovo G50-45 inverted microphone not detected properly Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: New Bug description: System: Lenovo G50-45 with Lubuntu 16.04 Alsa information: http://www.alsa- project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f Internal microphone does not pick up sound by default. When I mute one channel, it works (this is not a good workaround since some application, such as Facebook Messenger, unmute both channels and set them to the same level automatically). --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: silvana2681 F pulseaudio /dev/snd/controlC1: silvana2681 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f InstallationDate: Installed on 2016-09-02 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 80E3 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN25WW(V1.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3 dmi.product.version: Lenovo G50-45 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723809] Re: NetworkManager-wait-online.service slows down boot
Real hardware running Bionic, MSI b350m prog motherboard with R3 1300x cpu. I must use a usb ethernet due to the onboard ethernet causing PCIe issues. I thought the extended freeze I was experiencing at boot up was caused by hardware driver issues I'm debugging, since I do not even get a log blurb if I hard reset, but I just happened to notice it is this bug by disabling quiet and splash. The wait-online-service check *never* finishes for me when it is triggered. I've left the PC on in this state for over an hour and it never reached the desktop. I don't know what triggers it, but lately it seems I experience it nine times out of ten boots. If I boot without the usb ethernet connected (PCIe ethernet drivers disabled) the boot starts immediately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1723809 Title: NetworkManager-wait-online.service slows down boot Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrade to artful, boot is considerable slower. By using systemd-analyze blame I've managed to narrow it to NetworkManager-wait-online.service. 30.591s NetworkManager-wait-online.service 10.240s nmbd.service 9.273s postfix@-.service 9.110s apt-daily.service 6.485s dev-sdb1.device 5.488s ModemManager.service 5.318s udisks2.service 4.968s accounts-daemon.service 3.807s fwupd.service 3.049s grub-common.service 2.837s apport.service 2.764s NetworkManager.service 2.413s speech-dispatcher.service 2.362s snapd.service 2.160s networking.service 2.083s pppd-dns.service 2.078s lm-sensors.service 2.073s gpu-manager.service 2.066s alsa-restore.service 1.570s smbd.service 1.380s rsyslog.service 1.310s polkit.service 1.117s apparmor.service ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Oct 16 00:18:09 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.3 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/4 Wired connection 1 066da907-ea49-35a2-8b54-b829cc834081 /org/freedesktop/NetworkManager/ActiveConnection/2 enp0s18f2u2ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s18f2u2i2 ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1723809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
I still have this problem and I am running mutter 3.27.92-1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
@glenpike For Xenial you need gcc-5 5.4.0-6ubuntu1~16.04.9. You can find which version you have installed via "dpkg -l | grep gcc-5". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
@cjmather If you are sure that you have the latest gcc and you are still seeing kernel panics with the -116 kernel, please file a new bug and report back here what that bug # is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725955] Re: "Printer added" notification
This notification pops up each time the network is changed (connected, disconnected), printer turned off or on, and during a daily chron job. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1725955 Title: "Printer added" notification Status in GNOME Settings Daemon: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: I've recently installed Ubuntu 17.10 (Gnome shell). After a while I saw an OSD notification with the message "printer added", and thought that must be because of the new driverless printers feature in the kernel. I have a brother printer in the network, and I tested it and it worked. The thing is that the message repeats itself, approximately every two minutes, and it's really distracting. I saw a question about this on AskUbuntu (https://askubuntu.com/questions/918462/ubuntu-17-04 -printer-added-notifications-under-gnome), and a solution, but it seemed like no one had filed a bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1725955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747566] [NEW] org.gnome.Shell.desktop stacktraces; tweener.js
Public bug reported: I'm running Ubuntu Bionic. After latest dist-upgrade today I'm not getting a lot of stacktraces in my syslog: Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:80 (0x7f38c40ddef0 @ 82) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f6ff970 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f6ffa10 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f6ffab0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 b
[Desktop-packages] [Bug 297323] Re: Vino uses a hard coded string when registering with Avahi (Zeroconf)
Still affected, and unable to disable the broadcasting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/297323 Title: Vino uses a hard coded string when registering with Avahi (Zeroconf) Status in vino: New Status in vino package in Ubuntu: Triaged Bug description: Binary package hint: vino Vino self registers as "$User remote desktop on $hostname" I would like to control this string, but I can not find any method to do so. I can work around this by using an option in avahi to not use dbus, however that doesn't work well, because then my chat service doesn't show up from the Linux box. I currently have the rfb service also defined in /etc/avahi/services/rfb.service using the string (common among my rfb and afp services) so that they show up in a very Mac-fashion in Finder. So I think Vino is registering using that string above, but there is no way to either disable that registration or to control the string to use under the vino-preferences (or any other manual way that I can tell) To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/297323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868570] Re: Can't edit or delete bookmarks in Vinagre
2018, still affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/868570 Title: Can't edit or delete bookmarks in Vinagre Status in Vinagre: VNC client for GNOME: Confirmed Status in vinagre package in Ubuntu: Triaged Bug description: The bookmarks sidebar is no longer available. Unable to edit or delete existing bookmarks. Able to add new bookmarks however they can not be edited afterwards. Bookmarks sidebar is missing from enclosed screenshot. No options to restore it in the menus. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: vinagre 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Wed Oct 5 14:36:08 2011 ExecutablePath: /usr/bin/vinagre InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: vinagre UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/vinagre/+bug/868570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1502370] Re: Unity does not send UnmapNotify event when window is iconified
See also: https://bugs.launchpad.net/unity/+bug/998073
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1502370
Title:
Unity does not send UnmapNotify event when window is iconified
Status in Unity:
New
Status in cinnamon package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Status in unity package in Ubuntu:
Confirmed
Bug description:
To reproduce this bug, run "wish" in a terminal window. Here's what I did in
wish:
> wish
% wm tracing 1
% wm iconify .
WaitForMapNotify giving up on .
WaitForMapNotify finished with . (winPtr 0x1af3a50, wmPtr 0x1af3850)
% wm state .
normal
% wm deiconify .
%
Three symptoms can be seen in the wish session:
1. wish should not report "WaitForMapNotify giving up on ."
2. After the "wm iconify ." command, the window disappears; however, the "wm
state ." should report "iconic" instead of "normal".
3. The "wm deiconify ." command should make the window reappear, but it does
not.
I'm struggling with whether this is a Unity bug or a Tk bug. The problem is
exhibited under Unity and Gnome Shell, but does not occur under fvwm2 (I ran
the test under all 3 window managers on the same system). Under fvwm2:
1. wish does not report "WaitForMapNotify giving up on ."
2) The "wm state ." command correctly returns "iconic".
3) The "wm deiconify ." command correctly makes the window reappear.
Under Gnome Shell and fvwm2, I was able to run "xtrace wish", and repeat the
session to watch the X11 events (I got a SEGV when I tried this under Unity and
I filed a bug). Under Gnome Shell, the xtrace info looks like this:
000:<:0092: 24: Request(16): InternAtom only-if-exists=false(0x00)
name='WM_CHANGE_STATE'
000:>:0092:32: Reply to InternAtom: atom=0x1dc("WM_CHANGE_STATE")
000:<:0093: 44: Request(25): SendEvent propagate=false(0x00)
destination=0x009b event-mask=SubstructureNotify,SubstructureRedirect
ClientMessage(33) format=0x20 window=0x0186 type=0x1dc("WM_CHANGE_STATE")
data=0x03,0x00,0x00,0x00,0xf0,0x71,0xd0,0x00,0x28,0x3e,0xc4,0x00,0x00,0x00,0x00,0x00,0x06,0x00,0x80,0x01;
000:>:0093: Event PropertyNotify(28) window=0x0186
atom=0x185(unrecognized atom) time=0x04931165 state=NewValue(0x00)
000:>:0093: Event PropertyNotify(28) window=0x0186
atom=0x15c("_NET_WM_STATE") time=0x04931165 state=NewValue(0x00)
000:<:0094: 24: Request(20): GetProperty delete=false(0x00)
window=0x0186 property=0x15c("_NET_WM_STATE") type=0x4("ATOM")
long-offset=0x long-length=0x0400
000:>:0094:36: Reply to GetProperty: type=0x4("ATOM")
bytes-after=0x data=;
Under fvwm2, the xtrace info looks like this:
000:<:008b: 24: Request(16): InternAtom only-if-exists=false(0x00)
name='WM_CHANGE_STATE'
000:>:008b:32: Reply to InternAtom: atom=0x1b1("WM_CHANGE_STATE")
000:<:008c: 44: Request(25): SendEvent propagate=false(0x00)
destination=0x009b event-mask=SubstructureNotify,SubstructureRedirect
ClientMessage(33) format=0x20 window=0x01c6 type=0x1b1("WM_CHANGE_STATE")
data=0x03,0x00,0x00,0x00,0xa0,0x7c,0x34,0x02,0x28,0xce,0x13,0x02,0x00,0x00,0x00,0x00,0x06,0x00,0xc0,0x01;
000:>:008c: Event UnmapNotify(18) event=0x01c6 window=0x01c6
from-configure=false(0x00)
000:>:008c: Event PropertyNotify(28) window=0x01c6
atom=0x185(unrecognized atom) time=0x04aa349c state=NewValue(0x00)
000:<:008d: 8: Request(10): UnmapWindow window=0x01c5
000:>:008d: Event PropertyNotify(28) window=0x01c6
atom=0x15c("_NET_WM_STATE") time=0x04aa349d state=NewValue(0x00)
000:<:008e: 4: Request(127): NoOperation
000:<:008f: 24: Request(20): GetProperty delete=false(0x00)
window=0x01c6 property=0x15c("_NET_WM_STATE") type=0x4("ATOM")
long-offset=0x long-length=0x0400
000:>:008f:36: Reply to GetProperty: type=0x4("ATOM")
bytes-after=0x data=;
Note that fvwm2 returns the UnmapNotify event to the client (in
response to the ClientMessage event), but Gnome Shell (and presumably
Unity) doesn't. As a result, wish does not send the UnmapWindow
request to the window manager under Gnome Shell.
The ICCCM (section 4.1.4) says "Clients can select for StructureNotify
on their top-level windows to track transitions between Normal and
Iconic states. Receipt of a MapNotify event will indicate a transition
to the Normal state, and receipt of an UnmapNotify event will indicate
a transition to the Iconic state.
The relevant Tk code is in the tk8.6 source package
(http://packages.ubuntu.com/source/trusty/tk8.6). At the bottom of
unix/tkUnixWm.c the TkpWmSetState() function calls XIconifyWindow(),
followed by WaitForMapNotify(). It is WaitForMapNotify() that prints
out the message that it is giving up. There's an interesting comment
[Desktop-packages] [Bug 1502370] Re: Unity does not send UnmapNotify event when window is iconified
** Also affects: cinnamon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1502370
Title:
Unity does not send UnmapNotify event when window is iconified
Status in Unity:
New
Status in cinnamon package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Status in unity package in Ubuntu:
Confirmed
Bug description:
To reproduce this bug, run "wish" in a terminal window. Here's what I did in
wish:
> wish
% wm tracing 1
% wm iconify .
WaitForMapNotify giving up on .
WaitForMapNotify finished with . (winPtr 0x1af3a50, wmPtr 0x1af3850)
% wm state .
normal
% wm deiconify .
%
Three symptoms can be seen in the wish session:
1. wish should not report "WaitForMapNotify giving up on ."
2. After the "wm iconify ." command, the window disappears; however, the "wm
state ." should report "iconic" instead of "normal".
3. The "wm deiconify ." command should make the window reappear, but it does
not.
I'm struggling with whether this is a Unity bug or a Tk bug. The problem is
exhibited under Unity and Gnome Shell, but does not occur under fvwm2 (I ran
the test under all 3 window managers on the same system). Under fvwm2:
1. wish does not report "WaitForMapNotify giving up on ."
2) The "wm state ." command correctly returns "iconic".
3) The "wm deiconify ." command correctly makes the window reappear.
Under Gnome Shell and fvwm2, I was able to run "xtrace wish", and repeat the
session to watch the X11 events (I got a SEGV when I tried this under Unity and
I filed a bug). Under Gnome Shell, the xtrace info looks like this:
000:<:0092: 24: Request(16): InternAtom only-if-exists=false(0x00)
name='WM_CHANGE_STATE'
000:>:0092:32: Reply to InternAtom: atom=0x1dc("WM_CHANGE_STATE")
000:<:0093: 44: Request(25): SendEvent propagate=false(0x00)
destination=0x009b event-mask=SubstructureNotify,SubstructureRedirect
ClientMessage(33) format=0x20 window=0x0186 type=0x1dc("WM_CHANGE_STATE")
data=0x03,0x00,0x00,0x00,0xf0,0x71,0xd0,0x00,0x28,0x3e,0xc4,0x00,0x00,0x00,0x00,0x00,0x06,0x00,0x80,0x01;
000:>:0093: Event PropertyNotify(28) window=0x0186
atom=0x185(unrecognized atom) time=0x04931165 state=NewValue(0x00)
000:>:0093: Event PropertyNotify(28) window=0x0186
atom=0x15c("_NET_WM_STATE") time=0x04931165 state=NewValue(0x00)
000:<:0094: 24: Request(20): GetProperty delete=false(0x00)
window=0x0186 property=0x15c("_NET_WM_STATE") type=0x4("ATOM")
long-offset=0x long-length=0x0400
000:>:0094:36: Reply to GetProperty: type=0x4("ATOM")
bytes-after=0x data=;
Under fvwm2, the xtrace info looks like this:
000:<:008b: 24: Request(16): InternAtom only-if-exists=false(0x00)
name='WM_CHANGE_STATE'
000:>:008b:32: Reply to InternAtom: atom=0x1b1("WM_CHANGE_STATE")
000:<:008c: 44: Request(25): SendEvent propagate=false(0x00)
destination=0x009b event-mask=SubstructureNotify,SubstructureRedirect
ClientMessage(33) format=0x20 window=0x01c6 type=0x1b1("WM_CHANGE_STATE")
data=0x03,0x00,0x00,0x00,0xa0,0x7c,0x34,0x02,0x28,0xce,0x13,0x02,0x00,0x00,0x00,0x00,0x06,0x00,0xc0,0x01;
000:>:008c: Event UnmapNotify(18) event=0x01c6 window=0x01c6
from-configure=false(0x00)
000:>:008c: Event PropertyNotify(28) window=0x01c6
atom=0x185(unrecognized atom) time=0x04aa349c state=NewValue(0x00)
000:<:008d: 8: Request(10): UnmapWindow window=0x01c5
000:>:008d: Event PropertyNotify(28) window=0x01c6
atom=0x15c("_NET_WM_STATE") time=0x04aa349d state=NewValue(0x00)
000:<:008e: 4: Request(127): NoOperation
000:<:008f: 24: Request(20): GetProperty delete=false(0x00)
window=0x01c6 property=0x15c("_NET_WM_STATE") type=0x4("ATOM")
long-offset=0x long-length=0x0400
000:>:008f:36: Reply to GetProperty: type=0x4("ATOM")
bytes-after=0x data=;
Note that fvwm2 returns the UnmapNotify event to the client (in
response to the ClientMessage event), but Gnome Shell (and presumably
Unity) doesn't. As a result, wish does not send the UnmapWindow
request to the window manager under Gnome Shell.
The ICCCM (section 4.1.4) says "Clients can select for StructureNotify
on their top-level windows to track transitions between Normal and
Iconic states. Receipt of a MapNotify event will indicate a transition
to the Normal state, and receipt of an UnmapNotify event will indicate
a transition to the Iconic state.
The relevant Tk code is in the tk8.6 source package
(http://packages.ubuntu.com/source/trusty/tk8.6). At the bottom of
unix/tkUnixWm.c the TkpWmSetState() function calls XIconifyWindow(),
followed by WaitForMapNotify(). It is WaitForMapNotify() that prints
out the message that it is giving up. There's an
[Desktop-packages] [Bug 1502370] Re: Unity does not send UnmapNotify event when window is iconified
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1502370
Title:
Unity does not send UnmapNotify event when window is iconified
Status in Unity:
New
Status in gnome-shell package in Ubuntu:
New
Status in unity package in Ubuntu:
Confirmed
Bug description:
To reproduce this bug, run "wish" in a terminal window. Here's what I did in
wish:
> wish
% wm tracing 1
% wm iconify .
WaitForMapNotify giving up on .
WaitForMapNotify finished with . (winPtr 0x1af3a50, wmPtr 0x1af3850)
% wm state .
normal
% wm deiconify .
%
Three symptoms can be seen in the wish session:
1. wish should not report "WaitForMapNotify giving up on ."
2. After the "wm iconify ." command, the window disappears; however, the "wm
state ." should report "iconic" instead of "normal".
3. The "wm deiconify ." command should make the window reappear, but it does
not.
I'm struggling with whether this is a Unity bug or a Tk bug. The problem is
exhibited under Unity and Gnome Shell, but does not occur under fvwm2 (I ran
the test under all 3 window managers on the same system). Under fvwm2:
1. wish does not report "WaitForMapNotify giving up on ."
2) The "wm state ." command correctly returns "iconic".
3) The "wm deiconify ." command correctly makes the window reappear.
Under Gnome Shell and fvwm2, I was able to run "xtrace wish", and repeat the
session to watch the X11 events (I got a SEGV when I tried this under Unity and
I filed a bug). Under Gnome Shell, the xtrace info looks like this:
000:<:0092: 24: Request(16): InternAtom only-if-exists=false(0x00)
name='WM_CHANGE_STATE'
000:>:0092:32: Reply to InternAtom: atom=0x1dc("WM_CHANGE_STATE")
000:<:0093: 44: Request(25): SendEvent propagate=false(0x00)
destination=0x009b event-mask=SubstructureNotify,SubstructureRedirect
ClientMessage(33) format=0x20 window=0x0186 type=0x1dc("WM_CHANGE_STATE")
data=0x03,0x00,0x00,0x00,0xf0,0x71,0xd0,0x00,0x28,0x3e,0xc4,0x00,0x00,0x00,0x00,0x00,0x06,0x00,0x80,0x01;
000:>:0093: Event PropertyNotify(28) window=0x0186
atom=0x185(unrecognized atom) time=0x04931165 state=NewValue(0x00)
000:>:0093: Event PropertyNotify(28) window=0x0186
atom=0x15c("_NET_WM_STATE") time=0x04931165 state=NewValue(0x00)
000:<:0094: 24: Request(20): GetProperty delete=false(0x00)
window=0x0186 property=0x15c("_NET_WM_STATE") type=0x4("ATOM")
long-offset=0x long-length=0x0400
000:>:0094:36: Reply to GetProperty: type=0x4("ATOM")
bytes-after=0x data=;
Under fvwm2, the xtrace info looks like this:
000:<:008b: 24: Request(16): InternAtom only-if-exists=false(0x00)
name='WM_CHANGE_STATE'
000:>:008b:32: Reply to InternAtom: atom=0x1b1("WM_CHANGE_STATE")
000:<:008c: 44: Request(25): SendEvent propagate=false(0x00)
destination=0x009b event-mask=SubstructureNotify,SubstructureRedirect
ClientMessage(33) format=0x20 window=0x01c6 type=0x1b1("WM_CHANGE_STATE")
data=0x03,0x00,0x00,0x00,0xa0,0x7c,0x34,0x02,0x28,0xce,0x13,0x02,0x00,0x00,0x00,0x00,0x06,0x00,0xc0,0x01;
000:>:008c: Event UnmapNotify(18) event=0x01c6 window=0x01c6
from-configure=false(0x00)
000:>:008c: Event PropertyNotify(28) window=0x01c6
atom=0x185(unrecognized atom) time=0x04aa349c state=NewValue(0x00)
000:<:008d: 8: Request(10): UnmapWindow window=0x01c5
000:>:008d: Event PropertyNotify(28) window=0x01c6
atom=0x15c("_NET_WM_STATE") time=0x04aa349d state=NewValue(0x00)
000:<:008e: 4: Request(127): NoOperation
000:<:008f: 24: Request(20): GetProperty delete=false(0x00)
window=0x01c6 property=0x15c("_NET_WM_STATE") type=0x4("ATOM")
long-offset=0x long-length=0x0400
000:>:008f:36: Reply to GetProperty: type=0x4("ATOM")
bytes-after=0x data=;
Note that fvwm2 returns the UnmapNotify event to the client (in
response to the ClientMessage event), but Gnome Shell (and presumably
Unity) doesn't. As a result, wish does not send the UnmapWindow
request to the window manager under Gnome Shell.
The ICCCM (section 4.1.4) says "Clients can select for StructureNotify
on their top-level windows to track transitions between Normal and
Iconic states. Receipt of a MapNotify event will indicate a transition
to the Normal state, and receipt of an UnmapNotify event will indicate
a transition to the Iconic state.
The relevant Tk code is in the tk8.6 source package
(http://packages.ubuntu.com/source/trusty/tk8.6). At the bottom of
unix/tkUnixWm.c the TkpWmSetState() function calls XIconifyWindow(),
followed by WaitForMapNotify(). It is WaitForMapNotify() that prints
out the message that it is giving up. There's an interesting comment
in WaitForMapNotify()
[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
Environment: Fresh install 16.04 Razer Blade 14 2014 Intel GPU Nvidia 870M 1x HDMI port I originally had no video drivers installed and was using the Intel gpu and this did not work with DisplayLink with 1.4x drivers installed until i added xorg.conf.d/20-intel.conf. After this it worked as a third display but I had disappearing mouse cursor issues constantly and only with the DisplayLink hdmi usb adapter plugged in... there were times when the mouse wouldn't come back for minutes. Most of the time the behavior would be: on the top half of the screen the mouse would only flicker and on the bottom half it would completely disappear. I experimented with all permutations in the directory /usr/share/xorg.conf.d/ between 20-nvidia.conf, 20-intel.conf one being present vs both and all of the params in each scenario: TearingFree false/true, TripleBuffering false/true, PageFlip false/true Solution for me was to use the GNOME desktop, the 20-intel.conf with only: Section "Device" Identifier "Intel Graphics" Driver "Intel" EndSection And using the Nvidia driver 340 proprietary in AdditionalDrivers while setting it to be primary usage in Nvidia application with rendering quality set to performance. No more disappearing mouse, 3 monitors all plugged in at boot and only a 10 second wait for the USB DisplayLink monitor to show up after login. Cheers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Bug description: *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT* If you are having an issue and want it addressed, it is most helpful to file a new report. If you were led here by DisplayLink's website, you were led here in error as no useful debugging information has been provided by the original reporter, which is necessary to root cause, and solve the issue he reported. Posting comments about how you think you have the same problem isn't helpful here. My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729377] Re: AMD r7 250 wrong detection
** Attachment added: "outpout of glxinfo.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+attachment/5006143/+files/outpout%20of%20glxinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1729377 Title: AMD r7 250 wrong detection Status in mesa package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD 8830M. This results in the wrong detection of drivers. The result is a wrongly installed driver and very poor performance. This bug has been affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10. brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller' 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] (rev 87) brad@brad-ubuntu:~$ lsmod | grep -i 'radeon' radeon 1470464 9 i2c_algo_bit 16384 2 amdgpu,radeon ttm94208 2 amdgpu,radeon drm_kms_helper167936 2 amdgpu,radeon drm 356352 9 amdgpu,radeon,ttm,drm_kms_helper brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu' amdgpu 2007040 0 i2c_algo_bit 16384 2 amdgpu,radeon ttm94208 2 amdgpu,radeon drm_kms_helper167936 2 amdgpu,radeon drm 356352 9 amdgpu,radeon,ttm,drm_kms_helper Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper driver is, xserver-xorg-video-radeon. However even after proper installation of the new driver. Ubuntu still reports that I am using a mobile graphics card, instead of a desktop graphics card. Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading DistroCodename: artful DistroRelease: Ubuntu 17.10 DistroVariant: ubuntu InstallationDate: Installed on 2017-08-23 (71 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7721 Package: xorg 1:7.7+19ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful ubuntu Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V8.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A68HM-E33 V2 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 9.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 9.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7721 dmi.product.version: 9.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729377] Re: AMD r7 250 wrong detection
** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+attachment/5006144/+files/Xorg.1.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1729377 Title: AMD r7 250 wrong detection Status in mesa package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD 8830M. This results in the wrong detection of drivers. The result is a wrongly installed driver and very poor performance. This bug has been affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10. brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller' 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] (rev 87) brad@brad-ubuntu:~$ lsmod | grep -i 'radeon' radeon 1470464 9 i2c_algo_bit 16384 2 amdgpu,radeon ttm94208 2 amdgpu,radeon drm_kms_helper167936 2 amdgpu,radeon drm 356352 9 amdgpu,radeon,ttm,drm_kms_helper brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu' amdgpu 2007040 0 i2c_algo_bit 16384 2 amdgpu,radeon ttm94208 2 amdgpu,radeon drm_kms_helper167936 2 amdgpu,radeon drm 356352 9 amdgpu,radeon,ttm,drm_kms_helper Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper driver is, xserver-xorg-video-radeon. However even after proper installation of the new driver. Ubuntu still reports that I am using a mobile graphics card, instead of a desktop graphics card. Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading DistroCodename: artful DistroRelease: Ubuntu 17.10 DistroVariant: ubuntu InstallationDate: Installed on 2017-08-23 (71 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7721 Package: xorg 1:7.7+19ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful ubuntu Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V8.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A68HM-E33 V2 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 9.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 9.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7721 dmi.product.version: 9.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729377] Re: AMD r7 250 wrong detection
Hence my confusion, llvmpipe (LLVM 5.0, 128 bits) with the radeon driver is reported. And CAPE VERDE with the ati driver. Why would the wrong driver show proper input with glxinfo?. Either way still shows wrong graphics card all together. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1729377 Title: AMD r7 250 wrong detection Status in mesa package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD 8830M. This results in the wrong detection of drivers. The result is a wrongly installed driver and very poor performance. This bug has been affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10. brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller' 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] (rev 87) brad@brad-ubuntu:~$ lsmod | grep -i 'radeon' radeon 1470464 9 i2c_algo_bit 16384 2 amdgpu,radeon ttm94208 2 amdgpu,radeon drm_kms_helper167936 2 amdgpu,radeon drm 356352 9 amdgpu,radeon,ttm,drm_kms_helper brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu' amdgpu 2007040 0 i2c_algo_bit 16384 2 amdgpu,radeon ttm94208 2 amdgpu,radeon drm_kms_helper167936 2 amdgpu,radeon drm 356352 9 amdgpu,radeon,ttm,drm_kms_helper Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper driver is, xserver-xorg-video-radeon. However even after proper installation of the new driver. Ubuntu still reports that I am using a mobile graphics card, instead of a desktop graphics card. Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading DistroCodename: artful DistroRelease: Ubuntu 17.10 DistroVariant: ubuntu InstallationDate: Installed on 2017-08-23 (71 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7721 Package: xorg 1:7.7+19ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful ubuntu Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V8.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A68HM-E33 V2 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 9.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 9.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7721 dmi.product.version: 9.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
