[Bug 2090955] Re: Xorg freezes after waking from sleep
*** This bug is a duplicate of bug 2089319 *** https://bugs.launchpad.net/bugs/2089319 ** This bug has been marked a duplicate of bug 2089319 System is unresponsive after wakeup from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2090955 Title: Xorg freezes after waking from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2090955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2089438] [NEW] package xdiagnose 3.8.10 failed to install/upgrade: nie można otworzyć "/usr/lib/systemd/system/failsafe-x.service.dpkg-new": Nie ma takiego pliku ani katalogu
Public bug reported: Automatic updates, error was displayed. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: xdiagnose 3.8.10 ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12 Uname: Linux 6.8.0-48-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Nov 23 12:27:23 2024 ErrorMessage: nie można otworzyć "/usr/lib/systemd/system/failsafe-x.service.dpkg-new": Nie ma takiego pliku ani katalogu InstallationDate: Installed on 2017-08-23 (2649 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: xdiagnose Title: package xdiagnose 3.8.10 failed to install/upgrade: nie można otworzyć "/usr/lib/systemd/system/failsafe-x.service.dpkg-new": Nie ma takiego pliku ani katalogu UpgradeStatus: Upgraded to noble on 2024-10-05 (49 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 ** Affects: xdiagnose (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2089438 Title: package xdiagnose 3.8.10 failed to install/upgrade: nie można otworzyć "/usr/lib/systemd/system/failsafe-x.service.dpkg-new": Nie ma takiego pliku ani katalogu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/2089438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2089319] [NEW] System is unresponsive after wakeup from suspend
Public bug reported: After resuming my PC from suspend it displays either cursor on a black screen or glitched image of my desktop. Mouse is not responding and system needs hardware reboot. The issue is probably connected with NVIDIA drivers, see attached kernel log (nvidiabug) that was obtained after resuming (via terminal tty which actually was kind of responding). ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xorg 1:7.7+23ubuntu3 Uname: Linux 6.11.9-x64v3-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.fabric-imex-mgmt: DeviceFileMinor: 4323 DeviceFileMode: 256 DeviceFileModify: 1 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..27.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 560.35.03 Fri Aug 16 21:39:15 UTC 2024 GCC version: gcc version 14.2.0 (Ubuntu 14.2.0-4ubuntu2) ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 22:44:50 2024 DistUpgraded: 2024-11-19 19:44:01,616 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: oracular DistroVariant: ubuntu DkmsStatus: nvidia/560.35.03, 6.11.0-9-generic, x86_64: installed nvidia/560.35.03, 6.11.9-x64v3-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:85d1] MachineType: Micro-Star International Co., Ltd. MS-7A32 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.9-x64v3-xanmod1 root=UUID=8b32240a-7d4e-4347-b154-2fb8fd11ccd9 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to oracular on 2024-11-19 (2 days ago) dmi.bios.date: 05/19/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.Q1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.Q1:bd05/19/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2023-05-18T19:30:45.788647 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.122-1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.3-1ubuntu1 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 2:21.1.13-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-3ubuntu1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze oracular ubuntu wayland-session ** Attachment added: "nvidiabug" https://bugs.launchpad.net/bugs/2089319/+attachment/5839305/+files/nvidiabug ** Description changed: After resuming my PC from suspend it displays either cursor on a black screen or glitched image of my desktop. Mouse is not responding and system needs hardware reboot. The issue is probably connected with - NVIDIA drivers, see attached kernel log that was obtained after resuming - (via terminal tty which actually was kind of responding). + NVIDIA drivers, see attached kernel log (nvidiabug) that was obtained + after resuming (via terminal tty which actually was kind of responding). ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xorg 1:7.7+23ubuntu3 Uname: Linux 6.11.9-x64v3-xanmod1 x86
[Bug 2086211] Re: High memory, CPU usage, file picker and shortcut problems after selecting multiple files
After further investigation, I believe this is related to https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal- gnome/+bug/2085698 and https://gitlab.gnome.org/GNOME/xdg-desktop- portal-gnome/-/issues/118. The workaround to restart xdg-desktop-portal- gnome works in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086211 Title: High memory, CPU usage, file picker and shortcut problems after selecting multiple files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2086211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086211] Re: High memory, CPU usage, file picker and shortcut problems after selecting multiple files
Tested the same upload under Chromium and got the same symptoms, so this is likely not Firefox-specific. Both Chromium and Firefox are installed as snap packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086211 Title: High memory, CPU usage, file picker and shortcut problems after selecting multiple files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2086211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086211] [NEW] High memory, CPU usage, file picker and shortcut problems after selecting multiple files
Public bug reported: I am currently uploading numerous files via Firefox into an Immich instance using a file-picker. When I select the first batch of a few hundred files, everything works as expected. However, when I attempt to open the file picker again, nothing happens. At the same time, xdg- desktop-portal-gnome start using a lot of CPU (up to 100% on a single core) and memory (1,3GB RSS in my case). When this happens, desktop shortcuts do nothing - I get an animation when I click them, but the relevant process is not started. Same for opening files in Nautilus. After some time (several minutes), CPU utilisation goes down (memory usage remains elevated) and other symptoms stop. When this happens, I get a separate file picker window opened for each time I clicked the upload button and desktop shortcuts start working again - again, I get a process started for each time I clicked the relevant shortcut. Steps to reproduce: 1. Use the file-picker to select multiple (as in hundreds) files in Firefox. Note: this might be a Firefox bug, but I see symptoms outside Firefox, so assigning it here for now. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xdg-desktop-portal-gnome 46.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 31 17:00:51 2024 InstallationDate: Installed on 2024-02-10 (264 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to noble on 2024-05-30 (154 days ago) ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: I am currently uploading numerous files via Firefox into an Immich instance using a file-picker. When I select the first batch of a few hundred files, everything works as expected. However, when I attempt to open the file picker again, nothing happens. At the same time, xdg- desktop-portal-gnome start using a lot of CPU (up to 100% on a single core) and memory (1,3GB RSS in my case). When this happens, desktop shortcuts do nothing - I get an animation when I click them, but the - relevant process is not started. + relevant process is not started. Same for opening files in Nautilus. After some time (several minutes), CPU utilisation goes down (memory usage remains elevated) and other symptoms stop. When this happens, I get a separate file picker window opened for each time I clicked the upload button and desktop shortcuts start working again - again, I get a process started for each time I clicked the relevant shortcut. Steps to reproduce: 1. Use the file-picker to select multiple (as in hundreds) files in Firefox. Note: this might be a Firefox bug, but I see symptoms outside Firefox, so assigning it here for now. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xdg-desktop-portal-gnome 46.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 31 17:00:51 2024 InstallationDate: Installed on 2024-02-10 (264 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to noble on 2024-05-30 (154 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086211 Title: High memory, CPU usage, file picker and shortcut problems after selecting multiple files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2086211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062064] Re: anki crashed with ModuleNotFoundError in Noble
Distutils have been removed from Python 3.12 (https://stackoverflow.com/questions/77233855/why-did-i-get-an-error- modulenotfounderror-no-module-named-distutils). This can be worked around by installing python3-setuptools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062064 Title: anki crashed with ModuleNotFoundError in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anki/+bug/2062064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048704] Re: Crash: Failed to rotate /var/log/journal/*
Now that I know what is imitating a bug I will try to reproduce a bug again, but this time recording kernel logs. So hopefully I will get some more details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048704 Title: Crash: Failed to rotate /var/log/journal/* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2048704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048704] Re: Crash: Failed to rotate /var/log/journal/*
After some experiments I can confirm that it is in some way related to power supply/battery. In my case bug appeared when laptop switched from `charging` to `fully charged`. I can also confirm, that before black screen with "failed to rotate..." message, the filesystem is switched into read-only mode, which then causes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048704 Title: Crash: Failed to rotate /var/log/journal/* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2048704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048704] Re: Crash: Failed to rotate /var/log/journal/*
I had the same situation. Happened few times, now it is stable again. Few Specs: OS: Ubuntu 22.04.4 LTS x86_64 Kernel: 6.5.0-21-generic Shell: bash 5.1.16 Terminal: gnome-terminal CPU: 11th Gen Intel i7-11800H (16) @ GPU: Intel TigerLake-H GT1 [UHD Grap GPU: NVIDIA GeForce RTX 3050 Mobile While looking for a potential solution i found corrupted log file using `journalctl --verify` that failed with message: "Bad message". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048704 Title: Crash: Failed to rotate /var/log/journal/* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2048704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971145] [NEW] Display configuration changes to default when triggering cmd+P
Public bug reported: I'm using two displays with join displays option and configured 'Display 1' to be on the left side. I found out that by triggering display configuration window using key combination cmd+P changes my setting to default - 'Display 1' is moved to the right. This forces me to reapply this setting every time I accidentally trigger this window. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "1.png" https://bugs.launchpad.net/bugs/1971145/+attachment/5585825/+files/1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971145 Title: Display configuration changes to default when triggering cmd+P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1902973] Re: After upgrade to 20.10 with default 5.8 kernel keyboard didn't work. I've downgraded to 5.4 and keyboard was OK. The USB-installer of Ubuntu 20.10 also didn't work with my keyboa
Hello, with kernel 5.8.0-31 it started working well. Thanks a lot. Andrzej Marczak pon., 23 lis 2020 o 23:40 Launchpad Bug Tracker <1902...@bugs.launchpad.net> napisał(a): > > Status changed to 'Confirmed' because the bug affects multiple users. > > ** Changed in: ubuntu-release-upgrader (Ubuntu) >Status: New => Confirmed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1902973 > > Title: > After upgrade to 20.10 with default 5.8 kernel keyboard didn't work. > I've downgraded to 5.4 and keyboard was OK. The USB-installer of > Ubuntu 20.10 also didn't work with my keyboard. My device is ASUS > R541U. > > Status in ubuntu-release-upgrader package in Ubuntu: > Confirmed > > Bug description: > Updating from 5.8.0-25 to 5.8.0-26 didn't solve the problem. I've seen > on web other people with same problem on Asus laptops. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: ubuntu-release-upgrader-core 1:20.10.12 > ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 > Uname: Linux 5.4.0-52-generic x86_64 > ApportVersion: 2.20.11-0ubuntu50 > Architecture: amd64 > CasperMD5CheckResult: skip > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Thu Nov 5 02:54:32 2020 > InstallationDate: Installed on 2020-04-27 (191 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=pl_PL.UTF-8 >SHELL=/bin/bash > SourcePackage: ubuntu-release-upgrader > Symptom: release-upgrade > UpgradeStatus: Upgraded to groovy on 2020-10-27 (9 days ago) > VarLogDistupgradeXorgFixuplog: >INFO:root:/usr/bin/do-release-upgrade running >INFO:root:No xorg.conf, exiting > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1902973/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902973 Title: After upgrade to 20.10 with default 5.8 kernel keyboard didn't work. I've downgraded to 5.4 and keyboard was OK. The USB-installer of Ubuntu 20.10 also didn't work with my keyboard. My device is ASUS R541U. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1902973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875408] Re: Logitech G700s extra G buttons don't work in wireless mode
I got the same issue after updating from 18.04 to 20.10 (I did following update in one go 18.04 > 20.04 > 20.10, kernel x86_64 Linux 5.8.0-28-generic). I had issue with Logitech G604 using dongle. Buttons G4 and G7 (two buttons on the side, closest to the back of the mouse) stopped working plus when dongle was reconnected while system was running, scroll up and down was not working after the re-connection. The workaround for scroll issue was either to reboot whole machine or switch mouse into Bluetooth mode and back to dongle mode. Thankfully workaround by user Lastique works, both issues disappeared. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902973] [NEW] After upgrade to 20.10 with default 5.8 kernel keyboard didn't work. I've downgraded to 5.4 and keyboard was OK. The USB-installer of Ubuntu 20.10 also didn't work with my keyboard
Public bug reported: Updating from 5.8.0-25 to 5.8.0-26 didn't solve the problem. I've seen on web other people with same problem on Asus laptops. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 5 02:54:32 2020 InstallationDate: Installed on 2020-04-27 (191 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-27 (9 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902973 Title: After upgrade to 20.10 with default 5.8 kernel keyboard didn't work. I've downgraded to 5.4 and keyboard was OK. The USB-installer of Ubuntu 20.10 also didn't work with my keyboard. My device is ASUS R541U. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1902973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
** Changed in: apt (Ubuntu) Status: Confirmed => New ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Andrzej Jonczy (andree0) ** Changed in: glibc (Ubuntu Focal) Status: Confirmed => Fix Released ** Changed in: glibc (Ubuntu) Status: Invalid => Fix Released ** Changed in: apt (Ubuntu) Status: New => Fix Released ** Changed in: apt (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: apt (Ubuntu Focal) Status: Confirmed => Fix Released ** Changed in: apt (Ubuntu Bionic) Assignee: (unassigned) => Andrzej Jonczy (andree0) ** Changed in: apt (Ubuntu Focal) Assignee: (unassigned) => Andrzej Jonczy (andree0) ** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Andrzej Jonczy (andree0) ** Changed in: glibc (Ubuntu Bionic) Assignee: (unassigned) => Andrzej Jonczy (andree0) ** Changed in: glibc (Ubuntu Focal) Assignee: (unassigned) => Andrzej Jonczy (andree0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows
Whoa! I have experienced something interesting. The issue disappeared when I tried to debug something with mouse and use `xev`. After starting it (and also after closing it) - focus issue disappeared. It would be awesome if this helped to fix it. Not sure if this is related but I'm temporary happy (will see for how long it is). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362359 Title: Focus gets stuck to a window - impossible to select other windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows
@arnfranke I just experienced it too last week. I'm using Ubuntu since 2015. Current mouse (trackball) I used from the beginning of 2020. It works with no issue with Ubuntu 18.04. Issue occurred just after last Ubuntu update (middle of August). Whats funny when I have my mouse/trackball plugged in I have this issue also with touchpad. When I remove mouse USB - everything works fine again. Another thing is that when I plug in other mouse or trackball - the issue is not present. It is just with single device. I also tried with another laptop with Ubuntu 18.04 (without update) I worked on it 2 hours - there were no issues. Then I just updated Ubuntu and restarted that second laptop and... issue occurred also on the second machine and again just after Ubuntu update. I'm mad, I love to work with my trackball but I cannot now. This behavior is so strange. Also when I unplug my trackball and plug it agan it works fine for 30-60 seconds and then issue occurred again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362359 Title: Focus gets stuck to a window - impossible to select other windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893134] [NEW] USB headset doesnt work after connecting
Public bug reported: After connecting USB headset ubuntu doesnt switch to it but rather audio goes completely nuts. Changing output device in settings doesnt help, audio is gone. After several replugs and system reboot audio is back on usb headset but then after disconnecting it I cant get my rear jack to work without juggling with output device in settings and (again) a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.7.15-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 23:04:38 2020 InstallationDate: Installed on 2019-11-19 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Device successful Symptom_Card: Bloody Gaming Audio Device - Bloody Gaming Audio Device Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andrzej1465 F pulseaudio /dev/snd/controlC1: andrzej1465 F pulseaudio /dev/snd/controlC0: andrzej1465 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - Bloody Gaming Audio Device, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-15 (103 days ago) dmi.bios.date: 10/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.J0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd10/31/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-11-21T21:34:52.015266 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893134 Title: USB headset doesnt work after connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893134] Re: USB headset doesnt work after connecting
Whats even more interesting, Apport was able to play test noise via USB headset right after connecting but Settings nor Firefox cant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893134 Title: USB headset doesnt work after connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893133] [NEW] Status bar showing 200% scale after boot
Public bug reported: After boot status bar looks as 200% scale in Settings -> Displays (although it is set to 100%) Resolution: Change scale to 200%, apply settings and revert back to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.7.15-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..1d.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:1d:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 22:55:26 2020 DistUpgraded: 2020-05-15 12:11:46,013 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-44-generic, x86_64: installed nvidia, 440.100, 5.7.15-xanmod1, x86_64: installed openrazer-driver, 2.8.0, 5.4.0-44-generic, x86_64: installed openrazer-driver, 2.8.0, 5.7.15-xanmod1, x86_64: installed openrazer-driver, 2.8.0, 5.8.3-xanmod2, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2019-11-19 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A32 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.15-xanmod1 root=UUID=5068e932-3f8c-4fd6-8003-574703a9a2f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-15 (103 days ago) dmi.bios.date: 10/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.J0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd10/31/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893133 Title: Status bar showing 200% scale after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885962] [NEW] 'sudo do-release-upgrade -d' crash
Public bug reported: An unresolvable problem occurred while calculating the upgrade. This was caused by: * Upgrading to a pre-release version of Ubuntu This is most likely a transient problem, please try again later. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Jul 2 00:17:54 2020 InstallationDate: Installed on 2018-07-27 (705 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-07-01 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885962 Title: 'sudo do-release-upgrade -d' crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1885962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878418] [NEW] Installing Ubuntu 19.10 with pendrive (iso image) I have signaled error output \ input. Write on the pedrive with Etcher.
Public bug reported: nstalling Ubuntu 19.10 with pendrive (iso image) I have signaled error output \ input. Write on the pedrive with Etcher.The error is to result from a dirty CD playback and writing mechanism that I don't use. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 Date: Wed May 13 14:59:48 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878418 Title: Installing Ubuntu 19.10 with pendrive (iso image) I have signaled error output \ input. Write on the pedrive with Etcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1878418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875673] Re: printer canon ip4600 only generic text mode
I have the same problem with Canon MP560 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875673 Title: printer canon ip4600 only generic text mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
Are there plans to backport the fix to 19.10, seeing as 20.04 has already received the fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851987] Re: Long boot times, ACPI error messages in dmesg
I'm a complete noob so sorry for no logs, but I have the exact same configuration "I have a lenovo legion Y540 15IRH with nvidia 1660 ti" (don't know how to check motherboard) and the exact same message. Tried booting Kali Linux and Ubuntu. Worked for me the week previous, I think but after I updated BIOS drivers booting no longer works. Kai-Heng, you're saying they're harmless but for me booting stops and there is a weird, not moving, glitch on the screen. ** Attachment added: "IMG_0062.JPG" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851987/+attachment/5329862/+files/IMG_0062.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851987 Title: Long boot times, ACPI error messages in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856491] [NEW] after suspend system freezes for a while after mouting new device
Public bug reported: hello after resuming system from sleep two problems appears: (not sure if thats gnome bug) - after plugging in usb device (eg android phone) or mounting local drive ui freezes for a minute, mouse is working but ui doesnt react at all - wallpaper becomes pixel-crazy mess pc has to be suspended for longer time otherwise i couldnt reproduce these problems ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 22:55:27 2019 DisplayManager: lightdm InstallationDate: Installed on 2019-11-19 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856491 Title: after suspend system freezes for a while after mouting new device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856490] [NEW] Night light effect dissapears after screen dim
Public bug reported: hello, after screen goes off due to no user activity it turns back on without night light effect - no reddish color after opening settings and reenabling this feature, it goes back to work ps night light seems to break while dimming animation hits in - before dimming starts screen looses night light effect and immediately starts to dim ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..1d.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:1d:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 22:43:37 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-24-generic, x86_64: installed nvidia, 435.21, 5.3.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2019-11-19 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A32 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-25-generic root=UUID=5068e932-3f8c-4fd6-8003-574703a9a2f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.J0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd10/31/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 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 2:1.20.5+git20191008-0ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856490 Title: Night light effect dissapears after screen dim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] Re: 4.15 and higher kernels do not read the SD card
andrzej@ASUS ~ $ sudo apt build-dep linux Czytanie list pakietów... Gotowe E: Nie udało się odnaleźć źródła dla pakietu linux "andrzej @ ASUS ~ $ sudo apt build-dep linux Reading package lists ... Ready E: The source for the linux package could not be found" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691556] Re: Can't send audio to Amazon Echo via Bluetooth
I had the same issue with Device or resource busy and the same problem when Alexa says that is connected to pc and no sound - but it's because your pc becomes bluetooth speaker for Echo, in that state pacmd list-cards shows: ... a2dp_source: Przechwytywanie o wysokiej dokładności (źródło A2DP) (priority 20, available: yes) a2dp_sink: Odtwarzanie o wysokiej dokładności (odpływ A2DP) (priority 40, available: no) off: Wyłączone (priority 0, available: yes) ... Finally I got connected Echo as bluetooth speaker and it's working now after reboot too. Steps to get Echo working as bluetooth speaker that works for me: 1. Echo doesn't know anything about bluetooth connection - so first forget your device in Alexa App, and other devices. 2. Reinstall your pulseaudio-module-bluetooth: for fedora: sudo dnf reinstall pulseaudio-module-bluetooth 3. Uncomment MultiProfile in /etc/bluetooth/main.conf and set it to multiple. (not sure if it is nesesery) 4. If you made modifications do: sudo systemctl daemon-reload sudo service bluetooth restart 5. Check if A2DPSink and source is registred with sudo service bluetooth status 6. If not do: pacmd load-module module-bluetooth-discover 7. Reset adapter: sudo hciconfig hci0 reset 8.Check if adapter works good: (my class is 0x1c0104) hciconfig -a 9. Now unload pulseaudio modules: pacmd unload-module module-switch-on-connect pacmd unload-module module-switch-on-port-available Now open terminal and run bluetoothctl, and in bluetoothctl type: default-agent remove ECHO_MAC (if you have saved it before) Now tell to Echo "Alexa, bluetooth" and after "Searching" Echo should show in bluetoothctl so connect it: connect ECHO_MAC exit After that bluetoothctl should show that connects to echo and pairs it, then pacmd list-cards will show a2dp_sink available yes. After reboot when you want to connect, don't say anything to echo, just run bluetoothctl and connect echo. If after connect bluetoothctl doesn't show anything about pair and connect, you can try to manualy connect to a2dp_sink with: dbus-send --print-reply --system --dest=org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX org.bluez.Device1.ConnectProfile string:110b--1000-8000-00805f9b34f Replace XX with your echo MAC. Fedora 29, BlueZ 5.50. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691556 Title: Can't send audio to Amazon Echo via Bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] Re: 4.15 and higher kernels do not read the SD card
Good uname -r 4.14.0-041400rc8-generic dmesg | grep mmc [ 3.128542] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 3.150575] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA [ 3.359275] mmc0: new HS200 MMC card at address 0001 [ 3.363889] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB [ 3.364098] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB [ 3.364254] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB [ 3.364471] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB [ 3.367293] mmcblk0: p1 p2 p3 [ 5.912282] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 6.793061] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [ 7.641133] Adding 4085756k swap on /dev/mmcblk0p3. Priority:-2 extents:1 across:4085756k SSFS [ 51.509028] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 [ 51.510484] mmcblk1: mmc1:59b4 0 59.7 GiB [ 51.513027] mmcblk1: p1 [ 51.730325] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. ### Bad uname -r 4.15.0-041500rc1-generic dmesg | grep mmc [ 3.021412] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 3.048044] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA [ 3.294013] mmc0: new HS200 MMC card at address 0001 [ 3.299552] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB [ 3.299725] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB [ 3.299961] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB [ 3.300235] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB, chardev (242:0) [ 3.304538] mmcblk0: p1 p2 p3 [ 5.824844] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 6.601760] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [ 7.415364] Adding 4085756k swap on /dev/mmcblk0p3. Priority:-2 extents:1 across:4085756k SSFS [ 108.739176] mmc1: Tuning timeout, falling back to fixed sampling clock [ 108.739311] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 [ 108.740897] mmcblk1: mmc1:59b4 0 59.7 GiB [ 118.989952] mmc1: Timeout waiting for hardware interrupt. [ 118.989975] mmc1: sdhci: SDHCI REGISTER DUMP === [ 118.989990] mmc1: sdhci: Sys addr: 0x0008 | Version: 0x1002 [ 118.990003] mmc1: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 [ 118.990015] mmc1: sdhci: Argument: 0x | Trn mode: 0x003b [ 118.990028] mmc1: sdhci: Present: 0x01ff0001 | Host ctl: 0x0017 [ 118.990040] mmc1: sdhci: Power: 0x000f | Blk gap: 0x0080 [ 118.990052] mmc1: sdhci: Wake-up: 0x | Clock: 0x0007 [ 118.990064] mmc1: sdhci: Timeout: 0x000a | Int stat: 0x [ 118.990077] mmc1: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b [ 118.990090] mmc1: sdhci: AC12 err: 0x | Slot int: 0x [ 118.990103] mmc1: sdhci: Caps: 0x0568c8b2 | Caps_1: 0x0807 [ 118.990115] mmc1: sdhci: Cmd: 0x123a | Max curr: 0x [ 118.990127] mmc1: sdhci: Resp[0]: 0x | Resp[1]: 0x01dd7d7f [ 118.990139] mmc1: sdhci: Resp[2]: 0x325b5900 | Resp[3]: 0x [ 118.990150] mmc1: sdhci: Host ctl2: 0x800b [ 118.990162] mmc1: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3f801200 [ 118.990170] mmc1: sdhci: [ 118.990790] mmcblk1: error -110 sending status command, retrying [ 118.991102] mmcblk1: error -110 sending status command, retrying [ 118.991405] mmcblk1: error -110 sending status command, aborting [ 119.557815] mmc1: Tuning timeout, falling back to fixed sampling clock [ 129.736008] mmc1: Timeout waiting for hardware interrupt. [ 129.736030] mmc1: sdhci: SDHCI REGISTER DUMP === [ 129.736046] mmc1: sdhci: Sys addr: 0x0008 | Version: 0x1002 [ 129.736059] mmc1: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 [ 129.736071] mmc1: sdhci: Argument: 0x | Trn mode: 0x003b [ 129.736084] mmc1: sdhci: Present: 0x01ff0001 | Host ctl: 0x0017 [ 129.736097] mmc1: sdhci: Power: 0x000f | Blk gap: 0x0080 [ 129.736109] mmc1: sdhci: Wake-up: 0x | Clock: 0x0007 [ 129.736121] mmc1: sdhci: Timeout: 0x000a | Int stat: 0x [ 129.736133] mmc1: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b [ 129.736146] mmc1: sdhci: AC12 err: 0x | Slot int: 0x [ 129.736158] mmc1: sdhci: Caps: 0x0568c8b2 | Caps_1: 0x0807 [ 129.736171] mmc1: sdhci: Cmd: 0x123a | Max curr: 0x [ 129.736183] mmc1: sdhci: Resp[0]: 0x | Resp[1]: 0x3010f32c [ 129.736196] mmc1: sdhci: Resp[2]: 0x30303030 | Resp[3]: 0x [ 129.736206] mmc1: sdhci: Host ctl2: 0x800b [ 129.736218] mmc1: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3f801
[Bug 1808116] Re: 4.15 and higher kernels do not read the SD card
it`s not fixed uname -r 4.20.0-042000rc7-generic grep mmc [3.772064] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [3.793440] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA [4.033750] mmc0: new HS200 MMC card at address 0001 [4.038688] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB [4.038988] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB [4.039248] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB [4.039389] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB, chardev (238:0) [4.041798] mmcblk0: p1 p2 p3 [6.686829] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [7.627411] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [8.585563] Adding 4085756k swap on /dev/mmcblk0p3. Priority:-2 extents:1 across:4085756k SSFS [ 62.592080] mmc1: Tuning timeout, falling back to fixed sampling clock [ 62.592220] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 [ 62.592920] mmcblk1: mmc1:59b4 0 59.7 GiB [ 72.631773] mmc1: Timeout waiting for hardware interrupt. [ 72.631787] mmc1: sdhci: SDHCI REGISTER DUMP === [ 72.631795] mmc1: sdhci: Sys addr: 0x0008 | Version: 0x1002 [ 72.631801] mmc1: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 [ 72.631807] mmc1: sdhci: Argument: 0x | Trn mode: 0x003b [ 72.631813] mmc1: sdhci: Present: 0x01ff0001 | Host ctl: 0x0017 [ 72.631819] mmc1: sdhci: Power: 0x000f | Blk gap: 0x0080 [ 72.631824] mmc1: sdhci: Wake-up: 0x | Clock:0x0007 [ 72.631830] mmc1: sdhci: Timeout: 0x000a | Int stat: 0x [ 72.631836] mmc1: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b [ 72.631842] mmc1: sdhci: AC12 err: 0x | Slot int: 0x [ 72.631848] mmc1: sdhci: Caps: 0x0568c8b2 | Caps_1: 0x0807 [ 72.631854] mmc1: sdhci: Cmd: 0x123a | Max curr: 0x [ 72.631860] mmc1: sdhci: Resp[0]: 0x | Resp[1]: 0x01dd7d7f [ 72.631866] mmc1: sdhci: Resp[2]: 0x325b5900 | Resp[3]: 0x [ 72.631870] mmc1: sdhci: Host ctl2: 0x800b [ 72.631876] mmc1: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3fc01200 [ 72.631879] mmc1: sdhci: [ 72.633930] mmcblk1: error -110 requesting status [ 73.175820] mmc1: Tuning timeout, falling back to fixed sampling clock [ 83.383832] mmc1: Timeout waiting for hardware interrupt. [ 83.383857] mmc1: sdhci: SDHCI REGISTER DUMP === [ 83.383874] mmc1: sdhci: Sys addr: 0x0008 | Version: 0x1002 [ 83.383888] mmc1: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 [ 83.383902] mmc1: sdhci: Argument: 0x | Trn mode: 0x003b [ 83.383915] mmc1: sdhci: Present: 0x01ff0001 | Host ctl: 0x0017 [ 83.383928] mmc1: sdhci: Power: 0x000f | Blk gap: 0x0080 [ 83.383941] mmc1: sdhci: Wake-up: 0x | Clock:0x0007 [ 83.383954] mmc1: sdhci: Timeout: 0x000a | Int stat: 0x [ 83.383968] mmc1: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b [ 83.383981] mmc1: sdhci: AC12 err: 0x | Slot int: 0x [ 83.383995] mmc1: sdhci: Caps: 0x0568c8b2 | Caps_1: 0x0807 [ 83.384008] mmc1: sdhci: Cmd: 0x123a | Max curr: 0x [ 83.384022] mmc1: sdhci: Resp[0]: 0x | Resp[1]: 0x3010f32c [ 83.384035] mmc1: sdhci: Resp[2]: 0x30303030 | Resp[3]: 0x [ 83.384046] mmc1: sdhci: Host ctl2: 0x800b [ 83.384059] mmc1: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3fc01200 [ 83.384069] mmc1: sdhci: [ 83.386517] mmcblk1: error -110 requesting status [ 83.386539] mmcblk1: recovery failed! [ 83.386587] print_req_error: I/O error, dev mmcblk1, sector 0 [ 83.386604] Buffer I/O error on dev mmcblk1, logical block 0, async page read [ 93.623911] mmc1: Timeout waiting for hardware interrupt. [ 93.623934] mmc1: sdhci: SDHCI REGISTER DUMP === [ 93.623952] mmc1: sdhci: Sys addr: 0x0008 | Version: 0x1002 [ 93.623965] mmc1: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 [ 93.623979] mmc1: sdhci: Argument: 0x | Trn mode: 0x003b [ 93.623993] mmc1: sdhci: Present: 0x01ff0001 | Host ctl: 0x0017 [ 93.624006] mmc1: sdhci: Power: 0x000f | Blk gap: 0x0080 [ 93.624019] mmc1: sdhci: Wake-up: 0x | Clock:0x0007 [ 93.624032] mmc1: sdhci: Timeout: 0x000a | Int stat: 0x [ 93.624046] mmc1: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b [ 93.624059] mmc1: sdhci: AC12 err: 0x | Slot int: 0x [ 93.624072] mmc1: sdhci: Caps: 0x0568c8b2 | Caps_1: 0x0807 [ 93.624085] mmc1: sdhci: Cmd: 0x123a | Max curr: 0x [ 93.624099] mmc1: sdhci: Resp[0]: 0x | Resp[1]: 0x3010f32c [ 93.624112] mmc1: sdhci: Resp[2]:
[Bug 1808116] Re: 4.15 and higher kernels do not read the SD card
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+attachment/5223051/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221664/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221667/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221665/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221663/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221662/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221659/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221666/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221661/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221654/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221660/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221657/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221656/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221658/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] Re: 4.15 and higher kernels do not read the SD card
i: Timeout: 0x000a | Int stat: 0x [ 493.275626] mmc1: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b [ 493.275639] mmc1: sdhci: AC12 err: 0x | Slot int: 0x [ 493.275652] mmc1: sdhci: Caps: 0x0568c8b2 | Caps_1: 0x0807 [ 493.275665] mmc1: sdhci: Cmd: 0x123a | Max curr: 0x [ 493.275679] mmc1: sdhci: Resp[0]: 0x | Resp[1]: 0x3010f32c [ 493.275691] mmc1: sdhci: Resp[2]: 0x30303030 | Resp[3]: 0x [ 493.275702] mmc1: sdhci: Host ctl2: 0x800b [ 493.275715] mmc1: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3f801200 [ 493.275724] mmc1: sdhci: [ 493.278649] mmcblk1: error -110 sending status command, retrying [ 493.278811] mmcblk1: error -110 sending status command, retrying [ 493.278970] mmcblk1: error -110 sending status command, aborting [ 493.278997] print_req_error: I/O error, dev mmcblk1, sector 0 [ 493.279013] Buffer I/O error on dev mmcblk1, logical block 0, async page read [ 503.515341] mmc1: Timeout waiting for hardware interrupt. [ 503.515365] mmc1: sdhci: SDHCI REGISTER DUMP === [ 503.515382] mmc1: sdhci: Sys addr: 0x0008 | Version: 0x1002 [ 503.515396] mmc1: sdhci: Blk size: 0x7200 | Blk cnt: 0x0008 [ 503.515409] mmc1: sdhci: Argument: 0x | Trn mode: 0x003b [ 503.515423] mmc1: sdhci: Present: 0x01ff0001 | Host ctl: 0x0017 [ 503.515435] mmc1: sdhci: Power: 0x000f | Blk gap: 0x0080 [ 503.515448] mmc1: sdhci: Wake-up: 0x | Clock: 0x0007 [ 503.515461] mmc1: sdhci: Timeout: 0x000a | Int stat: 0x [ 503.515475] mmc1: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b [ 503.515488] mmc1: sdhci: AC12 err: 0x | Slot int: 0x [ 503.515501] mmc1: sdhci: Caps: 0x0568c8b2 | Caps_1: 0x0807 [ 503.515514] mmc1: sdhci: Cmd: 0x123a | Max curr: 0x [ 503.515528] mmc1: sdhci: Resp[0]: 0x | Resp[1]: 0x3010f32c [ 503.515540] mmc1: sdhci: Resp[2]: 0x30303030 | Resp[3]: 0x [ 503.515551] mmc1: sdhci: Host ctl2: 0x800b [ 503.515564] mmc1: sdhci: ADMA Err: 0x | ADMA Ptr: 0x3f801200 [ 503.515573] mmc1: sdhci: [ 503.516466] mmcblk1: error -110 sending status command, retrying [ 503.516753] mmcblk1: error -110 sending status command, retrying [ 503.516976] mmcblk1: error -110 sending status command, aborting [ 503.517017] print_req_error: I/O error, dev mmcblk1, sector 0 [ 503.517038] Buffer I/O error on dev mmcblk1, logical block 0, async page read + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0p: andrzej2371 F...m pulseaudio + /dev/snd/controlC0: andrzej2371 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Linux 18.3 + HibernationDevice: RESUME=UUID=cd6c775c-e8bc-4b29-92a1-11ee03628598 + InstallationDate: Installed on 2017-09-21 (446 days ago) + InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170629 + Lsusb: + 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 0bda:57ed Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. E200HA + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic root=UUID=3fedc785-7c52-4efd-8235-82e82f93c2e3 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-45-generic N/A + linux-backports-modules-4.13.0-45-generic N/A + linux-firmware 1.157.21 + Tags: sylvia + Uname: Linux 4.13.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo + _MarkForUpload: True + dmi.bios.date: 12/21/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: E200HA.303 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: E200HA + 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.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: E + dmi.product.name: E200HA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscri
[Bug 1808116] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1808116/+attachment/5221655/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808116 Title: 4.15 and higher kernels do not read the SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808116] [NEW] 4.15 and higher kernels do not read the SD card
Public bug reported: 4.15 and higher kernels do not read the SD card. kernel 4.13 reads the SD card. Checked with a 64GB Samsung and 16 GB card from another manufacturer. Also 4.19.8 kernel does not read cards inxi -Fxz System: Host: ASUS Kernel: 4.13.0-45-generic x86_64 (64 bit gcc: 5.4.0) Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) Distro: Linux Mint 18.3 Sylvia Machine: Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: E200HA.303 date: 12/21/2016 CPU: Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 clock speeds: max: 1920 MHz 1: 1920 MHz 2: 1920 MHz 3: 486 MHz 4: 505 MHz Graphics: Card: Intel Device 22b0 bus-ID: 00:02.0 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.06hz GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes Audio: Card Intel HDMI/DP LPE Audio driver: HdmiLpeAudio Sound: ALSA v: k4.13.0-45-generic Network: Card: Qualcomm Atheros Device 0042 driver: ath10k_pci bus-ID: 01:00.0 IF: wlp1s0 state: up speed: N/A duplex: N/A mac: Drives: HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB Partition: ID-1: / size: 25G used: 21G (89%) fs: ext4 dev: /dev/mmcblk0p2 ID-2: swap-1 size: 4.18GB used: 0.00GB (0%) fs: swap dev: /dev/mmcblk0p3 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 40.0C mobo: N/A Fan Speeds (in rpm): cpu: 0 Info: Processes: 225 Uptime: 1 min Memory: 1101.6/3839.9MB Init: systemd runlevel: 5 Gcc sys: 5.4.0 Client: Shell (bash 4.3.481) inxi: 2.2.35 without a SD card inserted dmesg | grep mmc [ 2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA [ 3.323762] mmc0: new HS200 MMC card at address 0001 [ 3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB [ 3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB [ 3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB [ 3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB [ 3.334332] mmcblk0: p1 p2 p3 [ 4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [ 6.827393] Adding 4085756k swap on /dev/mmcblk0p3. Priority:-1 extents:1 across:4085756k SSFS with inserted SD card dmesg | grep mmc [ 2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA [ 3.323762] mmc0: new HS200 MMC card at address 0001 [ 3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB [ 3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB [ 3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB [ 3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB [ 3.334332] mmcblk0: p1 p2 p3 [ 4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [ 6.827393] Adding 4085756k swap on /dev/mmcblk0p3. Priority:-1 extents:1 across:4085756k SSFS [ 216.577900] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 [ 216.578575] mmcblk1: mmc1:59b4 0 59.7 GiB [ 216.580031] mmcblk1: p1 [ 216.857616] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. === inxi -Fxz System: Host: ASUS Kernel: 4.15.0-42-generic x86_64 (64 bit gcc: 5.4.0) Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) Distro: Linux Mint 18.3 Sylvia Machine: Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: E200HA.303 date: 12/21/2016 CPU: Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 clock speeds: max: 1920 MHz 1: 839 MHz 2: 816 MHz 3: 480 MHz 4: 480 MHz Graphics: Card: Intel Device 22b0 bus-ID: 00:02.0 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.06hz GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes Audio: Card Intel HDMI/DP LPE Audio driver: HdmiLpeAudio Sound: ALSA v: k4.15.0-42-generic Network: Card: Qualcomm Atheros Device 0042 driver: ath10k_pci bus-ID: 01:00.0 IF: wlp1s0 state: up speed: N/A duplex: N/A mac: Drives: HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB Partition: ID-1: / size: 25G used: 21G (89%) fs: ext4 dev: /dev/mmcblk0p2 ID-2: swap-1 size: 4.18GB used: 0.0
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
That worked but I had to ask for access to bug tracking since I'm new to this. Just hope there's no confirmation link etc. email from Canonical since I lost access to mail account I used to create U1 acount way back then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
OK, I cleared the /var/crash folder and then replicated the bug. I got the crash file and submitted it however I don't know how to get bug ID to link it. When I click Continue in the crash report window it disappears. The bug title was "gnome-shell crashed with SIGSEGV in meta_window_get_monitor() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
I'm having the same issue on Intel NUC7 (NUC7i3BHN) with Ubuntu 17.10 and Intel i915 proprietary driver. The NUC is set up as a Kodi HTPC and connected to a Samsung TV. When the TV is turned off and then turned on the session gets terminated and all applications are instantly killed. When the TV is just turned off everything works in the background (eg. when I'm streaming music using Kore remote instead of TV) but crashes the moment the TV is turned on. Also random crashes occur with the TV turned off and long music playback. This confirms that this bug is driver unrelated as it occurs on Nvidia, AMD and Intel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733127] Re: Session crashes when monitor is disconnected
*** This bug is a duplicate of bug 1721428 *** https://bugs.launchpad.net/bugs/1721428 I'm having the same issue on Intel NUC7 (NUC7i3BHN) with Ubuntu 17.10 and Intel i915 proprietary driver. The NUC is set up as a Kodi HTPC and connected to a Samsung TV. When the TV is turned off and then turned on the session gets terminated and all applications are instantly killed. When the TV is just turned off everything works in the background (eg. when I'm streaming music using Kore remote instead of TV) but crashes the moment the TV is turned on. Also random crashes occur with the TV turned off and long music playback. This confirms that this bug is driver unrelated as it occurs on Nvidia, AMD and Intel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733127 Title: Session crashes when monitor is disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1733127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730513] Re: korganiser reminders do not trigger with 17.04.3
Artful test build restores Korganiser reminders. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730513 Title: korganiser reminders do not trigger with 17.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1730513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717758] [NEW] package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowa
Public bug reported: Problem detected by system automatic warning. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 06:11:09 2017 ErrorMessage: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania. InstallationDate: Installed on 2016-06-23 (450 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717758 Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1717758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250
*** This bug is a duplicate of bug 1680904 *** https://bugs.launchpad.net/bugs/1680904 I am getting this error randomly every once in a while. It's locking my PC completely but it's not stopping Spotify playing. Machine can not be restarted in any way even trough SSH session (SSH still works). Her is last error Jun 2 09:47:04 pc-name kernel: [109842.746855] BUG: unable to handle kernel NULL pointer dereference at 0018 Jun 2 09:47:04 pc-name kernel: [109842.746917] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Jun 2 09:47:04 pc-name kernel: [109842.746939] PGD 0 Jun 2 09:47:04 pc-name kernel: [109842.746940] Jun 2 09:47:04 pc-name kernel: [109842.746953] Oops: 0002 [#1] SMP Jun 2 09:47:04 pc-name kernel: [109842.746965] Modules linked in: arc4 ppp_mppe ppp_async nf_conntrack_pptp nf_conntrack_proto_gre ipheth bnep ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc aufs binfmt_misc snd_hda_codec_hdmi dell_wmi sparse_keymap dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic dcdbas joydev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel input_leds pcbc snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq Jun 2 09:47:04 pc-name kernel: [109842.747160] snd_seq_device snd_timer snd soundcore mei_me shpchp mei intel_pch_thermal hci_uart btbcm btqca btintel bluetooth intel_lpss_acpi intel_lpss acpi_als kfifo_buf acpi_pad mac_hid industrialio parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi video pinctrl_sunrisepoint pinctrl_intel i2c_hid hid fjes Jun 2 09:47:04 pc-name kernel: [109842.747303] CPU: 1 PID: 4421 Comm: chrome Not tainted 4.10.0-21-generic #23-Ubuntu Jun 2 09:47:04 pc-name kernel: [109842.747324] Hardware name: Dell Inc. OptiPlex 3040/05XGC8, BIOS 1.3.5 01/26/2016 Jun 2 09:47:04 pc-name kernel: [109842.747345] task: a071225d4500 task.stack: abc743844000 Jun 2 09:47:04 pc-name kernel: [109842.747377] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747399] RSP: 0018:abc743847880 EFLAGS: 00010246 Jun 2 09:47:04 pc-name kernel: [109842.747414] RAX: a07036de6840 RBX: 0003 RCX: 0003 Jun 2 09:47:04 pc-name kernel: [109842.747434] RDX: RSI: a070cc571000 RDI: a07204388000 Jun 2 09:47:04 pc-name kernel: [109842.747453] RBP: abc7438478d8 R08: R09: Jun 2 09:47:04 pc-name kernel: [109842.747473] R10: R11: 0001 R12: a07058c28000 Jun 2 09:47:04 pc-name kernel: [109842.747493] R13: a071901bb290 R14: ff79 R15: 8000 Jun 2 09:47:04 pc-name kernel: [109842.747513] FS: 7f64e6a8c480() GS:a07216c8() knlGS: Jun 2 09:47:04 pc-name kernel: [109842.747536] CS: 0010 DS: ES: CR0: 80050033 Jun 2 09:47:04 pc-name kernel: [109842.747553] CR2: 0018 CR3: 0001c4ebd000 CR4: 003406e0 Jun 2 09:47:04 pc-name kernel: [109842.747574] DR0: DR1: DR2: Jun 2 09:47:04 pc-name kernel: [109842.747594] DR3: DR6: fffe0ff0 DR7: 0400 Jun 2 09:47:04 pc-name kernel: [109842.747613] Call Trace: Jun 2 09:47:04 pc-name kernel: [109842.747638] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747656] ? __alloc_pages_nodemask+0x209/0x260 Jun 2 09:47:04 pc-name kernel: [109842.747683] gen8_alloc_va_range+0x23d/0x470 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747712] i915_vma_bind+0x7e/0x170 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747739] __i915_vma_do_pin+0x2a5/0x450 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747782] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747821] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747851] i915_gem_do_execbuffer.isra.38+0x4ca/0x15c0 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747869] ? wake_up_q+0x44/0x80 Jun 2 09:47:04 pc-name kernel: [109842.747891] i915_gem_execbuffer2+0xa1/0x1e0 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747916] drm_ioctl+0x21b/0x4c0 [drm] Jun 2 09:47:04 pc-name kernel: [109842.747940] ? i915_gem_execbuffer+0x310/0x310 [i915] Jun 2 09:47:04 pc-name kernel: [109842.747955] ? __seccomp_filter+0x67/0x250 Jun
Re: [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown"
Yes. I confirm that. After change in bios from raid to ahci computer is rebooting and swithing off normally. Wysłano z mojego smartfona Samsung Galaxy. Oryginalna wiadomość Od: Tobias Alke <1619...@bugs.launchpad.net> Data: 22.04.2017 08:53 (GMT+01:00) Do: blukisandr...@gmail.com Temat: [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" I think i have a specification to this issue. First, my system with the same problem at shutdown/reboot, but only in a very special case: Fresh install of Ubuntu Server 16.04.2 LTS CPU: Intel Xeon E3-1245v6 (Kabylake) Mainboard: MSI C236A Workstation/Server Mainboard (model: 7998-012R; latest BIOS: v2.7) RAM: 4x TRANSCEND 8GB DDR4 2133 ECC-DIMM 2Rx8 1Gx72 288P 512Mx8/CL15 (model: TS1GLH72V1H) SSD: 2x Samsung Basic MZ-7KE256BW 850 Pro interne SSD 256GB HDD: 2x Western Digital Red 4TB NAS (model: WDBMMA0040HNC-ERSN) Description of the special case with the shutdown/reboot issue: The problem only reveals when RAID-Mode auf the MSI Mainboard is enabled. After resetting to AHCI-Mode, the problem is over an the server works fine. It seems, that's a problem with the "Intel® C236 Chipset" or more specific a driver problem with intel based components on the different systems. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1619844 Title: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" Status in systemd package in Ubuntu: Confirmed Bug description: I tried getting more information in the debug-shell but I was unsuccessful in doing so. I was able to switch to the debug shell via ctrl+alt+f9 but I couldn't actually type anything in. I could switch back to the stuck shutdown screen via ctrl+alt+f1, and hitting NumLock would turn the light on my keyboard on and off, but I couldn't do anything else. I captured a journal of the stuck reboot. Interestingly, the journal shows a few more lines after "Reached target Shutdown", which is as far as I get on my screen. This system was installed with Xenial 16.04.1 (never been upgraded) and has had this problem since the very first boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Sep 3 00:33:19 2016 InstallationDate: Installed on 2016-08-17 (16 days ago) InstallationMedia: Ubuntu-Server 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5f709fed-48c9-4830-87be-acd13f263eb1 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/mariadb.service → /etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1619844/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619844 Title: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1619844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638301] Re: systemctl start auto-completion shows error
I am having the same problem on updated Ubunut Mate 16.10 in Guake Terminal and Mate Terminal. The error is showing after hitting tab after typing "sudo systemctl start " so when system is looking for names of systemd processes. The error is showing also when partial name has been put like "sudo systemctl start ngi[TAB][TAB]" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638301 Title: systemctl start auto-completion shows error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605799] Re: package virtualbox-ext-pack 5.0.24-0ubuntu1.16.04.1 failed to install/upgrade: [SRU] sub-processo script post-installation instalado retornou estado de saída de erro 1
** Changed in: virtualbox-ext-pack (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605799 Title: package virtualbox-ext-pack 5.0.24-0ubuntu1.16.04.1 failed to install/upgrade: [SRU] sub-processo script post-installation instalado retornou estado de saída de erro 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1605799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
the same problem for me: When I start fresh system, the suspend to RAM and resume works properly. But after certain amount of time when OS works, suspending and resuming ends with no response (blank screen). Ubuntu 16.04 64bit, Toshiba A200-1N8, 4.4.0-38-generic, Intel(R) Core(TM)2 Duo CPU T7250 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565241] [NEW] package fglrx-updates (not installed) failed to install/upgrade: podproces zainstalowany skrypt post-removal zwrócił kod błędu 1
Public bug reported: Problems with drivers AMD APU graphics, working on two monitors ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Sat Apr 2 11:29:58 2016 DistUpgraded: 2016-03-02 19:56:11,058 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201, 3.13.0-83-generic, x86_64: installed DuplicateSignature: package:fglrx-updates:(not installed):podproces zainstalowany skrypt post-removal zwrócił kod błędu 1 ErrorMessage: podproces zainstalowany skrypt post-removal zwrócił kod błędu 1 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7697] InstallationDate: Installed on 2014-12-11 (477 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: MSI MS-7697 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=20a02b2c-43c9-48c4-a4fc-936943da0fc7 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: fglrx-installer-updates Title: package fglrx-updates (not installed) failed to install/upgrade: podproces zainstalowany skrypt post-removal zwrócił kod błędu 1 UpgradeStatus: Upgraded to trusty on 2016-03-02 (30 days ago) dmi.bios.date: 09/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A75MA-P35 (MS-7697) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.2:bd09/27/2011:svnMSI:pnMS-7697:pvr1.0:rvnMSI:rnA75MA-P35(MS-7697):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7697 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565241 Title: package fglrx-updates (not installed) failed to install/upgrade: podproces zainstalowany skrypt post-removal zwrócił kod błędu 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1565241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42299] Re: No /etc/mkinitramfs/conf.d/resume after ubiquity installation
** Changed in: initramfs-tools (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/42299 Title: No /etc/mkinitramfs/conf.d/resume after ubiquity installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/42299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529624] Re: Lenovo E50-80 inverted microphone not detected properly
linux-image-4.2.0-28-generic in -proposed solves the problem. ** Tags removed: verification-needed-wily ** Tags added: verification-done-wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529624 Title: Lenovo E50-80 inverted microphone not detected properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529624] Re: Lenovo E50-80 inverted microphone not detected properly
FYI, this patch does indeed fix this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529624 Title: Lenovo E50-80 inverted microphone not detected properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529624] Re: Lenovo E50-80 inverted microphone not detected properly
Do you want me to test this patch? I haven't built a kernel in years, but can try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529624 Title: Lenovo E50-80 inverted microphone not detected properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529624] [NEW] Lenovo E50-80 inverted microphone not detected properly
Public bug reported: System: Lenovo E50-80 with Ubuntu 15.10. Tested with both kernel 4.2.0-22-generic from official repos and 4.4.0-040400rc6-generic from Mainline Kernel repo. Alsa information: http://www.alsa- project.org/db/?f=3088f82a0cf977855f92af9db8ad406c04f71efa 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). Adding model=inv-dmic to snd-hda-intel module options does not change a thing. Hope that helps, tell me if you need more info. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529624 Title: Lenovo E50-80 inverted microphone not detected properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1529624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
Bug report for Lenovo E50-80: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1529624 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526794] [NEW] Navigating to a folder in trash and up moves user out of trash:///
Public bug reported: Ubuntu version: Ubuntu 15.10 Nautilus version: 1:3.14.2-0ubuntu13 If a user opens a folder in trash:/// and then navigates up, he ends up in ~/.local/share/Trash/files rather than in trash:///. If he then tries to delete said folder, it simply gets moved to trash again, since Nautilus does not recognize ~/.local/share/Trash/files as a special location. Steps to reproduce: 1) In Nautilus, create a folder names 'foo' 2) Delete 'foo' by moving to trash 3) Open trash 4) Open 'foo' in trash 5) Navigate up 6) Delete 'foo' Expected behaviour: 'foo' is permanently deleted Observed behaviour: 'foo' is moved from trash to trash, i.e. nothing happens ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 16 14:19:05 2015 EcryptfsInUse: Yes GsettingsChanges: InstallationDate: Installed on 2015-09-15 (91 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to wily on 2015-10-19 (57 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526794 Title: Navigating to a folder in trash and up moves user out of trash:/// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1526794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed
*** This bug is a duplicate of bug 1422004 *** https://bugs.launchpad.net/bugs/1422004 I second that. Problem makes scanner non-functional. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430561 Title: hp-plugin crashes with error: Python gobject/dbus may be not installed To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1430561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516217]
This may be coming from xfce4-volumed running in background. If that is indeed the case, you can either switch xfce4-volumed off or disable notifications in the pulseaudio plugin properties dialog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516217 Title: Shows two notifications To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-pulseaudio-plugin/+bug/1516217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516217]
I see. This commit should fix it: 6431653 Do not show notifications at start up (bug #12313) Closing this report. Please reopen it if the fix doesn't work for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516217 Title: Shows two notifications To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-pulseaudio-plugin/+bug/1516217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397095]
Pushed the patch to git master: 8dc83f5 Do not use widget snapshot as tasklist draw icon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397095 Title: dragging applications in the task bar causes repaint errors To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-panel/+bug/1397095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407357]
Closing as fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407357 Title: Directory Menu panel plugin doesn't remember custom base-directory To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-panel/+bug/1407357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407357]
Filipp, thank you for the patch and sorry for the delay. The patch works and looks OK to me. Pushed to master. We should probably change the default assignee of xfce4-panel bugs - Nick is very busy these days. Small request, can you please attach patches with commit information (made with "git format-patch"). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407357 Title: Directory Menu panel plugin doesn't remember custom base-directory To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-panel/+bug/1407357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316645]
Pushed to git. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316645 Title: [Tasklist plugin] Grouped icons sometimes are wrongly rendered as a mini-icon To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-panel/+bug/1316645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316653]
Pushed to git (v2). It fixes the second issue (transparency of minimized new windows) but the first one is still there (grouped icons are are opaque even when all their windows are minimized). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316653 Title: [Tasklist plugin] Grouped icons are not rendered with transparent effect when their child are all minimized. To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-panel/+bug/1316653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387695]
Leave thunar_file_get_size_string unchanged and add another function e.g. thunar_file_get_size_string_with_mode (const ThunarFile *file, gboolean mode). Modify thunar-list-model.c (and any other code using thunar_file_get_size_string) to use the new function. Cache the configured value as a property in the ThunarListModel object. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387695 Title: File size displayed wrong To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1387695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387695]
I've merged your git branch into master. Thank you, that's a good quality code. BTW, the status bar always uses decimal units. Also, the properties dialog could display both units at once - no need to make it configurable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387695 Title: File size displayed wrong To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1387695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
I followed your advice and multiseat setup still works. And still seat-1 resume problem remains. I noticed that if I do (as root) a number of commands like: # DISPLAY=:1 XAUTHORITY=/var/run/lightdm/root/:1 xrandr --output DVI-I-2 --off # DISPLAY=:1 XAUTHORITY=/var/run/lightdm/root/:1 xrandr --output DVI-I-2 --auto Then seat-1 comes back after suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
I GOT ENLIGHTENED. I know what changed since yesterday. I don't have my printer installed in the multisesat ubuntu, so I'm ocassionally booting into my Debian install where I have my multiseat setup based on a Xephyr approach, where both monitors are connected to the two heads of JUST ONE of the graphics cards. So today the monitor of seat-1 was connected to TWO cards. Hence seat0 saw two monitors and extended its desktop to both, and seat-1 also saw one monitor. When I unplugged the reduntant cable, it all behaves like yesterday: seat-1 wouldn't come back after resume. That's good and bad news: the good news it that the world still works as it is supposed, the bad news is that the seat-1 resume problem remains. I need a break... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
More details on todays behaviour: After boot both screens come up, but sometimes seat-1 does appear, sometimes not and instead seat0 display extends to both monitors. Regardless of whether seat-1 appears or not, the initial position of mouse pointer of seat0 is offset BUT related to seat0's monitor. I think it is exactly in the middle of a big screen composed of BOTH monitors. If, after boot, seat-1 does not appear, when I do ctrl-alt-f1 ctrl- alt-f7 at seat0 (which CanTTY=yes) then greeter at seat1 appears. BUT only until a screensaver kicks-in: then when I move a mouse at seat-1 (or even without it), instead of seat-1's greeter (no one is logged in at seat-1) a missing part of seat0's display appears - I have same folders at the desktop and they tend to appear in a part of the screen "covered" by seat-1's greeter. And then if I ctrl-alt-f1 ctrl-alt-f7 again, seat-1's greeter appears again. The difference to yesterday and the day before is that I played with installing/uninstalling some packages. The versions of packages of interest as of now are: lightdm: 1.10.4-0ubuntu2 xserver-xorg-core: 2:1.15.1-0ubuntu2.6 I'm using Unity. I have no light-locker installed. I must say that until yesterday I had rock-solid behaviour and fully functioning system except waking up from suspend. Then I perhaps messed something up with the installed packages. What packages other than lightdm and xserver-xorg-core should I check? Is it possible that lightdm 1.10.__4__ is causing problems? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Regarding the doubt whether not coming back of seat-1 greeter is caused by the screenscaver kicking-in: that is not the case. I checked again and did a quick suspend and then resume and then looked up the x-1-greeter.log and there was no line about the screensaver. It does activate but far later than the failed suspend/resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Before suspend: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD root 1236 1223 12 55708 73248 0 20:56 tty7 00:00:10 /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch root 1238 1223 2 36801 64892 0 20:56 ?00:00:02 /usr/bin/X -core :1 -seat seat-1 -sharevts -auth /var/run/lightdm/root/:1 -nolisten tcp After resume: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD root 1236 1223 10 93676 173432 1 20:56 tty7 00:00:13 /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch root 1238 1223 1 37185 65092 1 20:56 ?00:00:02 /usr/bin/X -core :1 -seat seat-1 -sharevts -auth /var/run/lightdm/root/:1 -nolisten tcp A big difference today is that the monitor assigned to seat-1 comes back alive BUT it extends the display of session at seat0! In other words, today, after resume, both monitors provide a big desktop for session @ seat0. I can't understand how it changed since yesterday. Yesterday the behaviour was as described above: seat-1 card wouldn't come back. I'm also noticing a changed behaviour after boot and when greeters first appear: until yesterday, they appeared almost at the same time, with mouse pointers exactly in the middle of both. Today, they tend to blink a couple of times, and seat0 mouse pointers appears offset to the right. In /etc/lightdm/x-1-greeter.log I can see at the end: [+61,04s] DEBUG: user-list.vala:1030: Adding/updating user hajaszek () [+398,50s] DEBUG: settings-daemon.vala:209: Screensaver activated Please compare the times. The screensaver activates after about 5 minutes after the greeter is first displayed at system start. I can't tell at this moment if this corresponds to the time when I suspended/resumed or to the time where screensaver kicked-in on an otherwise unavailable display. SInce yesterday evening I played with printer drivers from http://www.bchemnet.com/suldr/; I installed/removed some of them back and forth. Then today I did apt-get install apt-show-version, and then did apt-get autoremove as suggested by apt. I would say this situation is even more annoying compared to the one when seat-1 consistently refuses to show up after resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
I have two discrete cards. So the difference is that your integrated card is probably on the "platform bus", while both of my discrete cards are PCI-E devices. I started testing multiseat setup described in this thread only last Saturday and since then have always been using the lightdm version which supports automatic multiseat; in one of my posts above (where I thought that the multiseat setup didn't work) I enclosed my full lightdm.conf; it only consisted of logind-load-seats and logind-check-graphical. # apt-cache policy lightdm lightdm: Zainstalowana: 1.10.4-0ubuntu2 # means: Installed Kandydująca: 1.10.4-0ubuntu2 # means: Candidate Tabela wersji: *** 1.10.4-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main i386 Packages 100 /var/lib/dpkg/status 1.10.3-0ubuntu2 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 1.10.0-0ubuntu3 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages The full lightdm.conf I'm using now: [LightDM] logind-load-seats=true logind-check-graphical=true [SeatDefaults] allow-guest=false [Seat:seat-1] xserver-command=/usr/bin/X -core -dpms -s 0 And with this setup the card assigned to seat0 in xorg.conf wakes up correctly, but the other does not. I'm wandering which step of restarting lightdm does the trick of waking it up fully? Because, as I said before, the seat-1 is not completely lost after wakeup; if I brutally restart lightdm it comes back, of course all graphical sessions terminated and lightdm login screen displayed again at both seats. My random guess is that the problem is in the X server. Perhaps for waking up there is some code path which works in a similar way to what probing used to work, that is, it only searches for platform display devices? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
The xserver-command with dpms does not work. If I swap the cards in xorg.conf I can see symmetric behaviour: the card which is assigned to seat0 wakes up correctly, but the other one does not, it's just this time that the cards are swapped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
It works for me, too. That said, I experience problems with coming back from machine's suspend: the screen at seat-1 in my setup (please see above) remains blank. I don't know if this is related to multiseat setup in any way, but it is really annoying. I'm using a dirty workaround: at waking up I do "service lightdm restart" which is surely an overkill and definitely not a solution. Any better ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Hi Laércio, SHAME ON ME When I started looking for files to paste here, I had a closer look at my xorg.conf: Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 MatchSeat "seat0" EndSection Section "ServerLayout" Identifier "Layout1" Screen 0 "Screen1" 0 0 MatchSeat "seat1" EndSection Section "Files" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor0" VendorName "Unknown" ModelName "Samsung SMEX2220" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 Option "DPMS" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor1" VendorName "Unknown" ModelName "Philips 170B4" HorizSync 30.0 - 82.0 VertRefresh 56.0 - 76.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce 8400 GS" BusID "PCI:1:0:0" MatchSeat "seat0" EndSection Section "Device" Identifier "Device1" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "Quadro NVS 290" BusID "PCI:3:0:0" MatchSeat "seat1" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 Option "Stereo" "0" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection MatchSeat "seat0" EndSection Section "Screen" Identifier "Screen1" Device "Device1" Monitor"Monitor1" DefaultDepth24 Option "Stereo" "0" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection MatchSeat "seat1" EndSection The problem is in naming. I dutifully named seat 0 "seat0", but I also dutifully followed the convention of naming seat 1 "seat-1", with a dash between the "t" and the "1" - _EXCEPT_ in my xorg.conf... When I did s/seat1/seat-1/g in my xorg.conf, the two seats appear correctly. I did not stress test it too much, but will do now. If I have a problem I will let you know immediately. I've been using multiseat setups for over a decade now and it has always been at least a bit "hakish"; each and every dist-upgrade (I've been using Debian testing, where dist-upgrades happen frequently) has been a threat that thigs would stop working. What is proposed here looks like a proper solution to multiseat setups. Thanks for your work! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Does NOT work for me :-(
I'm still getting the "no screens found" error, which, if I understand
correctly, is supposed to be fixed with:
http://bazaar.launchpad.net/~ubuntu-multiseat/xorg-server/trusty-matchseat/revision/287/debian/patches/xfree86_allow_fallback_to_pci_bus_probe_for_non_seat0.patch
$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ trusty-proposed restricted main
multiverse universe
deb http://pl.archive.ubuntu.com/ubuntu trusty-updates restricted universe main
multiverse
deb http://security.ubuntu.com/ubuntu/ trusty-security restricted universe main
multiverse
deb http://pl.archive.ubuntu.com/ubuntu trusty main restricted universe
multiverse
$ dpkg -l xserver-xorg-core
...
ii xserver-xorg-core 2:1.15.1-0ubuntu2.6
$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev.
2] (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS 290] (rev
a1)
$ cat /etc/udev/rules.d/99-multiseat.rules
SUBSYSTEM=="drm", KERNEL=="card[0-9]*", ATTRS{vendor}=="0x10de",
TAG+="master-of-seat"
TAG=="seat", DEVPATH=="/devices/pci:00/:00:01.0/:01:00.0/*",
ENV{ID_SEAT}="seat0", TAG+="seat0"
TAG=="seat", DEVPATH=="/devices/pci:00/:00:1c.2/:03:00.0/*",
ENV{ID_SEAT}="seat-1", TAG+="seat-1"
TAG=="seat", SUBSYSTEM=="usb", ATTR{name}=="DELL Dell USB Entry Keyboard",
ENV{ID_SEAT}="seat0", TAG+="seat0"
TAG=="seat", SUBSYSTEM=="usb", ATTR{name}=="Logitech USB-PS/2 Optical Mouse",
ENV{ID_SEAT}="seat0", TAG+="seat0"
TAG=="seat", SUBSYSTEM=="input", ATTR{name}=="AT Translated Set 2 keyboard",
ENV{ID_SEAT}="seat-1", TAG+="seat-1"
TAG=="seat", SUBSYSTEM=="input", ATTR{name}=="ImPS/2 Generic Wheel Mouse",
ENV{ID_SEAT}="seat-1", TAG+="seat-1"
$ loginctl list-seats
SEAT
seat0
seat-1
2 seats listed.
$ loginctl show-seat seat0
Id=seat0
ActiveSession=c2
CanMultiSession=yes
CanTTY=yes
CanGraphical=yes
Sessions=c2
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
$ loginctl show-seat seat-1
Id=seat-1
CanMultiSession=no
CanTTY=no
CanGraphical=yes
IdleHint=yes
IdleSinceHint=0
IdleSinceHintMonotonic=0
$ loginctl list-sessions
SESSIONUID USER SEAT
c2 1000 andrzejtpseat0
1 sessions listed.
$ loginctl seat-status seat0
seat0
Sessions: *c2
Devices:
/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
input:input1 "Power Button"
/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
input:input0 "Power Button"
/sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0
[MASTER] drm:card0
/sys/devices/pci:00/:00:1a.0/usb3
usb:usb3
/sys/devices/pci:00/:00:1a.1/usb4
usb:usb4
/sys/devices/pci:00/:00:1a.2/usb5
usb:usb5
/sys/devices/pci:00/:00:1a.7/usb1
usb:usb1
/sys/devices/pci:00/:00:1b.0/sound/card0
sound:card0 "Intel"
/sys/devices/pci:00/:00:1b.0/sound/card0/input10
input:input10 "HDA Intel Line Out CLFE"
/sys/devices/pci:00/:00:1b.0/sound/card0/input11
input:input11 "HDA Intel Line Out Side"
/sys/devices/pci:00/:00:1b.0/sound/card0/input12
input:input12 "HDA Intel Front Headphone"
/sys/devices/pci:00/:00:1b.0/sound/card0/input5
input:input5 "HDA Intel Rear Mic"
/sys/devices/pci:00/:00:1b.0/sound/card0/input6
input:input6 "HDA Intel Front Mic"
/sys/devices/pci:00/:00:1b.0/sound/card0/input7
input:input7 "HDA Intel Line"
/sys/devices/pci:00/:00:1b.0/sound/card0/input8
input:input8 "HDA Intel Line Out Front"
/sys/devices/pci:00/:00:1b.0/sound/card0/input9
input:input9 "HDA Intel Line Out Surround"
/sys/devices/pci:00/:00:1c.4/:04:00.0/ata5/host4/target4:0:0/4:0:0:0/block/sr0
block:sr0
/sys/devices/pci:00/:00:1c.4/:04:00.0/ata5/host4/target4:0:0/4:0:0:0/scsi_generic/sg1
scsi_generic:sg1
/sys/devices/pci:00/:00:1c.4/:04:00.0/ata5/host4/target4:0:1/4:0:1:0/block/sr1
block:sr1
/sys/devices/pci:00/:00:1c.4/:04:00.0/ata5/host4/target4:0:1/4:0:1:0/scsi_generic/sg2
scsi_generic:sg2
/sys/devices/pci:00/:00:1d.0/usb6
usb:usb6
/sys/devices/
[Bug 1387695]
André, I am thinking of two solutions:
1. Add a configuration option with a proper GUI and keep the defaults
("k"=10^3). Preferably, call the 2^10 prefix "Ki". If not, switch the
column header name to "Size (binary)". In "Properties" dialogs and in
the status bar use both systems (e.g. "9.7GB / 9.0GiB").
2. Use two column headers: "Size (decimal)", "Size (binary)" (we can
already switch headers on/off). In "Properties" dialogs and in the
status bar use both systems (e.g. "9.7GB / 9.0GiB").
If you implement either of these variants I will be happy to push it to
master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387695
Title:
File size displayed wrong
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/1387695/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1204919]
Fixed in 3848b0c0df4c2d744e4a9db2653c0507f78fbba3 More testing needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1204919 Title: 4.10.1 version affects session autosave so it couldn't be switched off To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-panel/+bug/1204919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377624] Re: udev requires hotplug support, thus upgrades fail
I'm also experiencing this issue on my 14.04 OVH VPS. It's running 2.6.32-042stab093.5 kernel, btw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377624 Title: udev requires hotplug support, thus upgrades fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1377624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301245] Re: System unresponsive under (IO/memory?) load
The problem still persists in 14.04 with updates (haven't checked 14.10). I have managed to solve(?) it by adding a "noautogroup" parameter to the kernel command line. More details: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219548 ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301245 Title: System unresponsive under (IO/memory?) load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257382] Re: Unity3d engine games all suffer from tearing even with vsync
The problem isn't limited to Unity3D. I switched over to GNOME 3 and though it improved the performance of one game (A Wizard's Lizard), 3D games tear on very capable hardware. I'm using Nvidia 331.xx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257382 Title: Unity3d engine games all suffer from tearing even with vsync To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1257382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049450]
Thank you and sorry for the massive delay. I have pushed the patch to master. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049450 Title: Fails trying to hide the xfce4-panel panel 1 To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-panel/+bug/1049450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181134] Re: xfce4-indicator-plugin crashed with SIGSEGV in g_type_check_instance_cast()
Does anyone how to enable the "global menu" indicator? I am trying to reproduce this error and so far I cannot make the global menu appear in the properties dialog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181134 Title: xfce4-indicator-plugin crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator-plugin/+bug/1181134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312452] Re: Firefox 28 often freezes with grey screen under Ubuntu 14.04
Still a problem, at least on other WMs (xfwm4 here). May I have a link to the compiz fix, please. It seems strange that a piece of software (firefox) exposes a bug in multiple other programs, though. Was the issue reported back to firefox upstream? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312452 Title: Firefox 28 often freezes with grey screen under Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1312452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
Same using Wine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313531] Re: Huge Wallch icon in Xubuntu 14.04
For a long time Unity indicators used only fixed-size icons. Not sure if Unity now supports scalable icons but Gtk API seems stuck to 22px. Xfce indicator plugin used to do bitmap scaling on the fly but that produced ugly icons, was CPU intensive for indicators that update icons often and buggy. Newer versions assume that all icon sizes are 22px. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313531 Title: Huge Wallch icon in Xubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallch/+bug/1313531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294762] Re: Blur effect on whole screen
Okay, I figured out the reason. When in the "nvidia-settings" in antialiasing settings, the field "Enable FXAA" is enabled, the problem affects. If I turned it off, everything will be okay. To see every change I need to restart computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294762 Title: Blur effect on whole screen To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294762] Re: Blur effect on whole screen
There is a problem. Before, to repair this, I've created new user. But this morning the problem affected me again. Now, only my desktop and my all windows are blurred. The unity dash seems to be okay. Yesterday everything was okay, so please tell me how I can get useful log information for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294762 Title: Blur effect on whole screen To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
