[Bug 2038653] Re: Foliate hangs at startup with spinning gear
I have reported the bug at https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2062995 In Ubuntu 24.04, I need both GSK_RENDERER=cairo and WEBKIT_DISABLE_DMABUF_RENDERER=1 to work around this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038653 Title: Foliate hangs at startup with spinning gear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foliate/+bug/2038653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062996] [NEW] Fails to start, "Argument display may not be null". fixed in 3.1.1.
Public bug reported: After upgrading to Ubuntu 24.04, Foliate won't start. I get this output: (com.github.johnfactotum.Foliate:14787): Gjs-CRITICAL **: 19:08:02.419: JS ERROR: Error: Argument display may not be null @resource:///com/github/johnfactotum/Foliate/themes.js:110:18 (com.github.johnfactotum.Foliate:14787): Gjs-CRITICAL **: 19:08:02.419: Module file:///usr/bin/foliate threw an exception This corresponds to Foliate issue https://github.com/johnfactotum/foliate/issues/1267 The fix is at https://github.com/johnfactotum/foliate/commit/2f2d05b221a310b92fbd01cef4aca0c7fc401ca5 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: foliate 4.~really3.1.0-0.1 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 20 19:06:45 2024 PackageArchitecture: all SourcePackage: foliate UpgradeStatus: Upgraded to noble on 2024-04-17 (3 days ago) ** Affects: foliate (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062996 Title: Fails to start, "Argument display may not be null". fixed in 3.1.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foliate/+bug/2062996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062995] [NEW] With nvidia-dkms-470 need GSK_RENDERER=cairo WEBKIT_DISABLE_DMABUF_RENDERER=1
Public bug reported: I have an Nvidia GeForce GT 710, which requires the legacy 470 proprietary driver. Both foliate and epiphany-browser display improperly by default. Some user interface elements are missing, and e-book and web pages are totally blank. To fix this, I added the following lines to /etc/environment : GSK_RENDERER=cairo WEBKIT_DISABLE_DMABUF_RENDERER=1 In the past WEBKIT_DISABLE_DMABUF_RENDERER=1 was enough, but in Ubuntu 24.04 I also require GSK_RENDERER=cairo. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkitgtk-6.0-4 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 20 18:57:04 2024 SourcePackage: webkit2gtk UpgradeStatus: Upgraded to noble on 2024-04-17 (3 days ago) ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062995 Title: With nvidia-dkms-470 need GSK_RENDERER=cairo WEBKIT_DISABLE_DMABUF_RENDERER=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2062995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968827] [NEW] Pulseaudio disables auto mute, so speaker sound continues when headphones plugged in
Public bug reported: My Dell Inspiron 6400 laptop has HDA Intel audio with a STAC9200 codec. It has speakers and a headphone jack. Previously when the headphone jack was unplugged sound came from the speakers, and when headphones were plugged in, sound came only from the headphones. In Ubuntu 22.04, when I plug in the headphones, sound comes from both the speakers and headphones. ALSA has the "Auto-Mute" feature, which mutes the speakers when headphones are plugged in. The problem is that Pulseaudio disables this feature. Every time I plug in headphones, I need to again re-enable that feature using alsamixer to stop sound from speakers. The problem seems to be this unfixed bug in Pulseaudio: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1297 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 15920 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 13 00:57:54 2022 SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-04-04 (8 days ago) dmi.bios.date: 06/13/2007 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968827 Title: Pulseaudio disables auto mute, so speaker sound continues when headphones plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1968827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958180] Re: "not in multiple of 0x10000" chkdsk errors for sparse files
I managed to install and use ntfs-3g 1:2021.8.22-3ubuntu1 from Ubuntu 22.04 into Ubuntu 21.10. (It was usable despite failing to satisfy dependencies, but this is not recommended and I was only doing it as a test.) Even with that newer version, the same bug still exists. I've reported the bug at https://github.com/tuxera/ntfs-3g/issues/25 ** Bug watch added: github.com/tuxera/ntfs-3g/issues #25 https://github.com/tuxera/ntfs-3g/issues/25 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958180 Title: "not in multiple of 0x1" chkdsk errors for sparse files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1958180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958180] [NEW] "not in multiple of 0x10000" chkdsk errors for sparse files
Public bug reported: In Ubuntu 21.10 using ntfs-3g 1:2017.3.23AR.3-3ubuntu5 I can create sparse files which result in the following messages from Windows 10 21H2 disk scanning: Stage 1: Examining basic file system structure ... The allocated length 0x41000 is not in multiple of 0x1 for attribute of type 0x80 and instance tag 0x1. The Windows GUI will say that the drive was scanned successfully with no errors, and I will need to look in Event Viewer to see this in scanning output. Repeated scans will not do anything about this issue. To fix the issue, make a copy of the affected file in Windows and delete the original. Attribute of type 0x80 is the data attribute, which tells where the file's data is stored. Apparently Windows allocates space for sparse files in multiples of 64 KB (0x1), and ntfs-3g does not. The message from disk scanning in Windows fails to tell you what file is involved. I only found the affected file after seeing that sparse files use 64 KB chunks, and then searching the file system for sparse files. I'm attaching a tar file created with the --sparse option. Extracting it onto NTFS should create a sparse file which triggers this issue. I'm testing with a partition with 4 KB clusters. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ntfs-3g 1:2017.3.23AR.3-3ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Jan 17 17:22:47 2022 SourcePackage: ntfs-3g UpgradeStatus: Upgraded to impish on 2021-10-02 (107 days ago) ** Affects: ntfs-3g (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "tar contains sparse file which triggers bug" https://bugs.launchpad.net/bugs/1958180/+attachment/5554993/+files/1229312_sparse_266240.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958180 Title: "not in multiple of 0x1" chkdsk errors for sparse files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1958180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958086] [NEW] "Load random example" fails because examples are in subdirectories
Public bug reported:
In the File menu, "Load random example" fails, saying "Error: Could not
open examples". This is because examples are in subdirectories of
/usr/share/XaoS/examples, and XaoS is not capable of finding examples in
subdirectories. XaoS looks in /usr/share/XaoS/examples and in a few
other non-existent places for examples, but never in subdirectories
where the examples actually are.
To fix this you can move or link examples to /usr/share/XaoS/examples.
For example you can: cd /usr/share/XaoS/examples && sudo find . -name
\*.xpf -exec ln -s "{}" . \;
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xaos 4.2.1-2
ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
Uname: Linux 5.13.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sun Jan 16 14:26:05 2022
SourcePackage: xaos
UpgradeStatus: Upgraded to impish on 2021-10-02 (106 days ago)
** Affects: xaos (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958086
Title:
"Load random example" fails because examples are in subdirectories
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xaos/+bug/1958086/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953239] [NEW] Files with multiple consecutive spaces cause errors
Public bug reported: I was trying to use checkinstall to create a package for projectM music visualizer which I compiled. I already made a tar.xz and was doing "sudo checkinstall tar -C / -xJf /d/projectm-linux-x86_64-20211102.tar.xz" and that was failing with a bunch of errors after "Installation successful": Installation successful == Copying files to the temporary directory...tar: ./usr/local/share/projectM/presets/presets_eyetune/New Creation Sensation - AdamFx,Flexi,Amandio c n Martin - Star to Another World ft Hexocollie n Shadow Harlequin n Geiss B.milk: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors tar: ./usr/local/share/projectM/presets/presets_milkdrop/Rovastar - Kalideostars (Round Round Mix).milk: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors tar: ./usr/local/share/projectM/presets/presets_mischa_collection/A New Definition for Milk - AdamFX - Laser Show in a Crystalstorm ft Orb n Martin Inside the Forge of Isengard.milk: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors tar: ./usr/local/share/projectM/presets/presets_mischa_collection/Stahlregen & AdamFX closer to god through bacon.milk: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors There is a lot more of this. These files indeed do not exist in the .tar.xz or on disk once it is extracted. I tracked down a bunch of the files, and all the corresponding files which do exist have two consecutive spaces in the file name. Apparently checkinstall turns two consecutive spaces into a single space, and then fails to find the file. As a simple test, I created a .tar.gz with "/usr/local/Hello World" (with two spaces between Hello and World) and "/usr/local/Hello World" (with a single space). Creating a package via "sudo checkinstall tar -C / -xzf /d/break_checkinstall_spaces.tar.gz", only the file with a single space gets included, though I don't see the "Cannot stat: No such file or directory" error. Using --fstrans=0 or --fstrans=no doesn't help. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: checkinstall 1.6.2+git20170426.d24a630-2ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Dec 4 23:43:35 2021 SourcePackage: checkinstall UpgradeStatus: Upgraded to impish on 2021-10-02 (63 days ago) ** Affects: checkinstall (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "Shows how file with two consecutive spaces isn't included" https://bugs.launchpad.net/bugs/1953239/+attachment/5545410/+files/break_checkinstall_spaces.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953239 Title: Files with multiple consecutive spaces cause errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/1953239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
No, "pcie_aspm=off" does not help. I also tried uninstalling broadcom-sta-dkms. It blacklists the b44 module via /etc/modprobe.d/broadcom-sta-dkms.conf and also https://wiki.debian.org/wl says that b44 is incompatible with wl. This did not help either. My laptop seems fine with just having the b44 module loaded. Lockups only happen when I plug in the Ethernet cable and start using it. The lockup seems total, with even Magic SysRq from the laptop's own keyboard doing absolutely nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
I got upgraded back to 470 because new 460 transitional dummy packages were released, which caused the upgrade. I could have prevented that via apt-mark hold. When I was getting these problems with 470 I had nvidia.NVreg_PreserveVideoMemoryAllocations=1 in my kernel command line, via /etc/default/grub. After being upgraded to 470 again, I changed that to nvidia.NVreg_PreserveVideoMemoryAllocations=0. So far, waking from sleep has been reliable. (Also, neither Firefox nor KDE Plasma have problems after sleep with this. I had set that option to 1 in the past because it seemed to help with earlier versions of Firefox and Plasma.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946303] [NEW] No video after wake from S3 due to Nvidia driver crash
Public bug reported: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "crashes seen via journalctl" https://bugs.launchpad.net/bugs/1946303/+attachment/5531172/+files/nvidia_resume_crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
In Ubuntu 21.10 with 5.13.0-16-generic kernel, I don't get any dmesg errors after I "modprobe b44" and Ethernet works initially at reasonable speed, but the whole system freezes totally after a few minutes. I suppose this means the b44 driver still doesn't work properly, because I don't get such freezes when using WiFi. Though I don't know for sure, because I don't have any error messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945909] [NEW] Giara requires gir1.2-handy-1
Public bug reported:
After installing Giara, when trying to start it I got:
Traceback (most recent call last):
File "/usr/bin/giara", line 69, in
gi.require_version('Handy', '1')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Handy not available
Installing gir1.2-handy-1 fixed it. This requirement seems to include
the Python interface to Libhandy. Previously libhandy-1-0 was installed,
but that was not enough.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: giara 0.3-2
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Oct 3 14:07:12 2021
InstallationDate: Installed on 2012-01-19 (3545 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: giara
UpgradeStatus: Upgraded to impish on 2021-10-02 (1 days ago)
** Affects: giara (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945909
Title:
Giara requires gir1.2-handy-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/giara/+bug/1945909/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945908] [NEW] Giara fails to log in due to extra characters at end of URL
Public bug reported: When I ran Giara for the first time, it gave a button for logging in, which opened a Reddit login confirmation for Giara in my default browser, Firefox. After confirming that, Firefox asked me to open a link in Giara. That failed, with Giara printing: Error authorizing Reddit client, retrying… Error authorizing Reddit client after retry, quitting… Before that, Giara displayed link starting with orggabmusgiaradesktop:// and ending with #_ on the terminal from where I started it. That # and all characters after it need to be removed for a successful login. Simply run Giara from the command line with that link as the only argument, with those characters at the end removed. This seems to be the corresponding bug: https://gitlab.gnome.org/World/giara/-/issues/97 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: giara 0.3-2 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 3 13:58:29 2021 InstallationDate: Installed on 2012-01-19 (3545 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: giara UpgradeStatus: Upgraded to impish on 2021-10-02 (1 days ago) ** Affects: giara (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945908 Title: Giara fails to log in due to extra characters at end of URL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giara/+bug/1945908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922443] Re: Lxdm black screen after Ubuntu 21.04 upgrade
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316 is the bug which is causing this problem. A fix is committed but it hasn't been released yet for 21.04, and apparently has some test failures in the proposed queue. In installed the pre-release files from https://launchpad.net/ubuntu/+source/glib2.0/2.68.1-1~ubuntu21.04.1/+build/21536716 and it fixes the problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922443 Title: Lxdm black screen after Ubuntu 21.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926316] Re: lxappearance crashes on launch
This also fixes the Lxdm greeter crash I reported at https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443. I installed the pre-release builds from https://launchpad.net/ubuntu/+source/glib2.0/2.68.1-1~ubuntu21.04.1/+build/21536716 and confirm that the bug is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926316 Title: lxappearance crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926316] Re: lxappearance crashes on launch
Seems this should also fix LXDM GTK greeter: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926316 Title: lxappearance crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922439] Re: X hangs after wake on Mobility Radeon x1400
Wake worked with kernel 5.11.0-16-generic. So, I guess this is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922439 Title: X hangs after wake on Mobility Radeon x1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922443] Re: Lxdm black screen after Ubuntu 21.04 upgrade
The problem seems to be /usr/lib/lxdm/lxdm-greeter-gtk crashing at g_key_file_load_from_file(). Also, lxappearance crashes similarly. This may be related: https://gitlab.gnome.org/GNOME/glib/-/issues/2361 . But the crash seems to be triggered by plasma.desktop and twm.desktop in /usr/share/xsessions. In both of those, the Name[whatever]= and Comment[whatever]= lines cause the crash. Yet xfce.desktop works with such lines. /usr/lib/lxdm/lxdm-greeter-gdk does work but seems lacking in features. ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2361 https://gitlab.gnome.org/GNOME/glib/-/issues/2361 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922443 Title: Lxdm black screen after Ubuntu 21.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922463] [NEW] Audacious title text not updated in Task Manager
Public bug reported: I'm using Audacious media player in Winamp 2.x skin mode. It consists of two windows: the main window with playback controls, whose title shows the current track, and the playlist editor window, whose title is constant. These windows are grouped into one Plasma Task Manager button on the panel, even when Task Manager has plenty of space. This is good. The problem is that the text displayed in Task Manager for Audacious shows the current track in Audacious when it was started. Playing a different track in Audacious doesn't change the title displayed in Task Manager. In alt-tab, the title does change. If I close the playlist editor, then the title changes in Task Manager as I change tracks in Audacious. So apparently the way Audacious windows get grouped causes the problem. (Separate Firefox windows group differently, only grouping when Task Manager is full, and then using the name of the application, with a + icon.) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: plasma-workspace 4:5.21.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 20:54:31 2021 SourcePackage: plasma-workspace UpgradeStatus: Upgraded to hirsute on 2021-03-28 (6 days ago) ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922463 Title: Audacious title text not updated in Task Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1922463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922443] Re: Lxdm black screen after Ubuntu 21.04 upgrade
The same problem happens on my main PC (with GeForce GT 710 graphics and 460.56-0ubuntu1 driver). I'm now using sddm instead of lxdm on both systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922443 Title: Lxdm black screen after Ubuntu 21.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922443] [NEW] Lxdm black screen after Ubuntu 21.04 upgrade
Public bug reported: In the past I used lxdm on my Dell Inspiron 6400 laptop without problems. After upgrading from Ubuntu 20.10 to 21.04, lxdm shows a fully black screen, without even a mouse cursor. Attempts to interact with it blindly don't work, which suggests it's somehow hanging, and not simply failing to display. Installing lxdm_0.5.3-2.1_amd64.deb from Ubuntu 20.10 does not fix the problem. So maybe something else is at fault, because that lxdm worked in Ubuntu 20.04. The laptop has Mobility Radeon x1400 with the radeon driver. Though using the fbdev driver instead doesn't change this bug. I don't use LXDE and don't have it installed. I'm only using lxdm because it is lightweight and fast, and I prefer other desktop environments. This has never been a problem in the past. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lxdm 0.5.3-4 Uname: Linux 5.12.0-051200rc5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Apr 3 13:58:41 2021 InstallationDate: Installed on 2012-01-19 (3362 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lxdm UpgradeStatus: Upgraded to hirsute on 2021-04-02 (1 days ago) ** Affects: lxdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922443 Title: Lxdm black screen after Ubuntu 21.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922439] Re: X hangs after wake on Mobility Radeon x1400
Wake from sleep works in Xfce and Plasma in Ubuntu 21.04 when using kernel 5.12.0-051200rc5-generic from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.12-rc5/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922439 Title: X hangs after wake on Mobility Radeon x1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922439] [NEW] X hangs after wake on Mobility Radeon x1400
Public bug reported: I have a Dell Inspiron 6400 with Mobility Radeon x1400. In Ubuntu 20.10 and earlier, wake from sleep worked properly. In Ubuntu 21.04, X does not work after wake from sleep. It fails in Plasma, Xfce, Openbox and Twm. With both Plasma and Xfce the screen is totally black. In all cases it is possible to use Control+Alt+F2 to go to a text console and use that. Generally it is possible to kill and restart X to get a usable GUI again. I'm reporting this as a kernel bug because if I boot Ubuntu 21.04 with linux-image-5.8.0-48-generic from Ubuntu 20.10, then X works after wake from sleep. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-13-generic 5.11.0-13.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:20:38 2021 HibernationDevice: RESUME=UUID=2d7284cc-d0df-45d7-b0a1-e5a0a8128eb8 InstallationDate: Installed on 2012-01-19 (3362 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda5 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.196 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-02 (1 days ago) dmi.bios.date: 06/13/2007 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922439 Title: X hangs after wake on Mobility Radeon x1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916074] [NEW] Firefox has border if started with kwin compositing disabled
Public bug reported: If I start Firefox with in KDE Plasma with kwin compositing disabled, and the Firefox title bar is disabled via Customize, the whole window has a border. Otherwise my computer is configured to not have window borders, and other applications don't have such a border. I don't know how to make that border go away, besides enabling compositing. Playing with #main-window in userChrome.css shows that the border and margin I can set there exists inside the border which I'm trying to remove. KWin has a hotkey for toggling compositing, found in Global Shortcuts. Default seems to be Alt+Shift+F12. Toggling compositing doesn't seem to change this immediately. What matters is the state of compositing when Firefox was started. I'm attaching a screenshot showing this border. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 85.0.1+build1-0ubuntu0.20.10.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bgjenero 1908 F pulseaudio /dev/snd/controlC0: bgjenero 1908 F pulseaudio /dev/snd/controlC1: bgjenero 1908 F pulseaudio BuildID: 20210204182252 CasperMD5CheckResult: skip Channel: release CurrentDesktop: KDE Date: Thu Feb 18 15:15:39 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev eth0 proto static 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.44 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-99b8dfa6-8d6d-4541-919c-7d2960210213 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:353 PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js user.js Profiles: Profile0 (Default) - LastVersion=85.0.1/20210204182252 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-99b8dfa6-8d6d-4541-919c-7d2960210213 bp-f8fe1ebe-97ed-4eec-8e60-11f5d0210118 bp-e9cbbf6c-3c3f-430d-83ce-a0fca0210101 bp-f2129335-9559-437d-b537-6f4830210101 bp-70bc911e-707f-4f53-93fe-f2ebf0210101 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to groovy on 2020-10-22 (119 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy release-channel third-party-packages ** Attachment added: "Screenshot showing border." https://bugs.launchpad.net/bugs/1916074/+attachment/5464856/+files/Screenshot_2021-02-18_15-18-16.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916074 Title: Firefox has border if started with kwin compositing disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912907] [NEW] Told to expect login code via SMS but it came via Telegram intead
Public bug reported: I had a Telegram account created via the official client (telegram- desktop package) in Ubuntu, where I logged in using a code sent via SMS. Using telegram-purple for the first time on another PC, I provided the same mobile phone number, and then Pidgin asked me to input a code that I receive via SMS. No code came via SMS. I tried a few times and still got no code. Then I booted up the first PC, ran telegram-desktop, and found the codes had been delivered there. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: telegram-purple 1.4.3-3ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 23 14:01:24 2021 RebootRequiredPkgs: linux-image-5.8.0-40-generic linux-base SourcePackage: telegram-purple UpgradeStatus: Upgraded to groovy on 2020-10-22 (93 days ago) ** Affects: telegram-purple (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912907 Title: Told to expect login code via SMS but it came via Telegram intead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-purple/+bug/1912907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912030] Re: Crash unless ffmpeg direct rendering disabled with ATI X1400
But, not all VLC video outputs are supposed to use OpenGL, so I don't see why Mesa is relevant. One of the crash backtraces doesn't involve Mesa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912030 Title: Crash unless ffmpeg direct rendering disabled with ATI X1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1912030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912030] [NEW] Crash unless ffmpeg direct rendering disabled with ATI X1400
Public bug reported: After upgrading to Ubuntu 20.10, VLC started crashing when I tried to play video. I tried changing to different video output methods, but none of them worked. In the past, I remember several methods working fine. In the ffmpeg advanced preferences page, disabling the direct rendering option made video playback work. I thought the vaapi errors VLC reports had something to do with it, but apparently not, because they still happen with successful playback. This is on a Dell Inspiron 6400 with ATI Mobility Radeon X1400, which doesn't support hardware decoding of the H.264 video I'm trying to play. Here's one backtrace: Thread 26 "vlc" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff880df640 (LWP 11335)] __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 104 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: No such file or directory. (gdb) bt #0 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 #1 0x77d03fc2 in picture_CopyPixels () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #2 0x77d04016 in picture_Copy () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #3 0x77cdf1ea in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #4 0x77ce1438 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #5 0x77f67590 in start_thread (arg=0x7fff880df640) at pthread_create.c:463 #6 0x77e87223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Also another: #0 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 #1 0x7fffc7022bff in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #2 0x7fffc74f1d66 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #3 0x7fffc6b41317 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #4 0x7fffc6cb4b07 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #5 0x7fffc6cb7dcc in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #6 0x7fffc6cbd9d9 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #7 0x7fff885b2eee in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #8 0x7fff885ad2c5 in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #9 0x7fff885b3cee in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #10 0x77cdf4e6 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #11 0x77ce1438 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #12 0x77f67590 in start_thread (arg=0x7fff886bb640) at pthread_create.c:463 #13 0x77e87223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: vlc 3.0.11.1-2 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Jan 15 18:46:42 2021 InstallationDate: Installed on 2012-01-19 (3284 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: vlc UpgradeStatus: Upgraded to groovy on 2020-10-21 (86 days ago) ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912030 Title: Crash unless ffmpeg direct rendering disabled with ATI X1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1912030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907479] [NEW] Mouse movement stops after switching to text VT and back to X
Public bug reported: My Dell Inspiron 6400 laptop has a Synaptics touchpad. If I'm using xserver-xorg-input-synaptics and I use Control-Alt-Fkey or sudo chvt to switch to a text virtual console and then switch back to X, the mouse stops moving via the touchpad. The touchpad seems totally ignored, and I can't tap to click either. However, the two physical mouse buttons located below the touchpad continue to work properly. Also, sudo evtest shows that touchpad events are still delivered by the kernel. If I apt purge xserver-xorg-input-synaptics and use the touchpad like a generic mouse, this does not happen. If I do that and then install xserver-xorg-input-libinput, using the touchpad via libinput, this also does not happen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Dec 9 11:32:34 2020 DistUpgraded: 2020-10-21 19:30:44,581 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu InstallationDate: Installed on 2012-01-19 (3247 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: Dell Inc. MM061 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-31-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda5 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to groovy on 2020-10-21 (48 days ago) dmi.bios.date: 06/13/2007 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907479 Title: Mouse movement stops after switching to text VT and back to X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1907479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903728] [NEW] Number of X colormap entries may be less than 1 << depth
Public bug reported: If I run scrot 1.4-1 to take a screenshot from a MicroVAX with a QDSS display device running ULTRIX 4.5, I get: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 91 (X_QueryColors) Value in failed request: 0xff Serial number of failed request: 23 Current serial number in output stream: 23 The QDSS is an 8 bit PseudoColor device, but it only has 254 available colormap entries, not 256. Here is a fragment from xdpyinfo: visual: visual id:0x23 class:PseudoColor depth:8 planes available colormap entries:254 red, green, blue masks:0x0, 0x0, 0x0 significant bits in color specification:8 bits The problem is that in __imlib_GrabDrawableToRGBA(), imlib2 ignores the number of colormap entries and instead does XQueryColors() for all 256 entries, based on the 8 bit depth. The hardware does actually have 256 entries, but the last two are reserved for the hardware cursor, and so the X server denies this XQueryColors() request. The attached patch instead only queries the number of colormap entries based on the visual, and sets the rest of the entries to zero. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libimlib2 1.6.1-2 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Nov 10 10:04:44 2020 SourcePackage: imlib2 UpgradeStatus: Upgraded to groovy on 2020-10-22 (19 days ago) ** Affects: imlib2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Patch added: "Fix for this issue" https://bugs.launchpad.net/bugs/1903728/+attachment/5433042/+files/map_entries_not_depth.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903728 Title: Number of X colormap entries may be less than 1 << depth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imlib2/+bug/1903728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
I don't see a null pointer message but the b44 driver is still broken in 5.4.0-33-generic on my Dell Inspiron 6400: [ 3148.539194] ssb: Found chip with id 0x4401, rev 0x02 and package 0x00 [ 3148.599317] b44 :03:00.0: Sonics Silicon Backplane found on PCI device :03:00.0 [ 3148.599414] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0 [ 3148.627839] b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:15:c5:b3:8a:ba [ 3148.684246] swiotlb_tbl_map_single: 14 callbacks suppressed [ 3148.684251] b44 :03:00.0: swiotlb buffer is full (sz: 1566 bytes), total 0 (slots), used 0 (slots) [ 3148.684261] [ cut here ] [ 3148.684267] WARNING: CPU: 0 PID: 36638 at kernel/dma/direct.c:35 report_addr+0x37/0x60 [ 3148.684268] Modules linked in: b44 mii iptable_filter bpfilter ccm b43 dell_laptop dell_smm_hwmon snd_hda_codec_hdmi cordic kvm snd_hda_codec_idt snd_hda_codec_generic bcma ledtrig_audio radeon dell_wmi snd_hda_intel snd_intel_dspcfg dell_smbios dcdbas input_leds joydev mac80211 snd_hda_codec r852 sparse_keymap wmi_bmof serio_raw dell_wmi_descriptor ttm sm_common snd_hda_core nand snd_hwdep drm_kms_helper nand_ecc snd_pcm cfg80211 bch i2c_algo_bit snd_timer fb_sys_fops r592 nandcore mtd memstick syscopyarea sysfillrect snd libarc4 sysimgblt soundcore mac_hid sch_fq_codel coretemp parport_pc ppdev lp parport drm ip_tables x_tables autofs4 ssb_hcd gpio_ich pata_acpi i2c_i801 psmouse lpc_ich firewire_ohci sdhci_pci cqhci firewire_core sdhci crc_itu_t ssb wmi video [ 3148.684314] CPU: 0 PID: 36638 Comm: NetworkManager Not tainted 5.4.0-33-generic #37-Ubuntu [ 3148.684315] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 [ 3148.684318] RIP: 0010:report_addr+0x37/0x60 [ 3148.684320] Code: 48 8b 87 28 02 00 00 48 89 75 f8 48 85 c0 74 2a 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 11 80 3d db c3 71 01 00 0f 84 7d 07 00 00 <0f> 0b c9 c3 48 83 bf 38 02 00 00 00 74 f2 eb e3 80 3d bf c3 71 01 [ 3148.684321] RSP: 0018:9ae68055b450 EFLAGS: 00010246 [ 3148.684323] RAX: fffe RBX: RCX: [ 3148.684324] RDX: 061e RSI: 6b440a80 RDI: 8cb34b4db0b0 [ 3148.684325] RBP: 9ae68055b458 R08: 3fff R09: 0004 [ 3148.684327] R10: R11: 0001 R12: 8cb2f8b0c000 [ 3148.684328] R13: 061e R14: 8cb2f45cef00 R15: 8cb2f96ac8c0 [ 3148.684330] FS: 7f02e05ca240() GS:8cb34c60() knlGS: [ 3148.684331] CS: 0010 DS: ES: CR0: 80050033 [ 3148.684333] CR2: 7f5935e43f28 CR3: c6128000 CR4: 06f0 [ 3148.684334] Call Trace: [ 3148.684340] dma_direct_map_page+0xdc/0xf0 [ 3148.684347] b44_alloc_rx_skb+0x1bb/0x4a0 [b44] [ 3148.684348] ? dma_direct_alloc_pages+0x93/0x130 [ 3148.684351] b44_init_rings+0xb8/0x190 [b44] [ 3148.684354] b44_open+0xfc/0x470 [b44] [ 3148.684357] __dev_open+0xd4/0x170 [ 3148.684359] __dev_change_flags+0x191/0x1f0 [ 3148.684361] dev_change_flags+0x26/0x60 [ 3148.684364] do_setlink+0x82e/0x980 [ 3148.684368] ? cpumask_next+0x1b/0x20 [ 3148.684371] ? __snmp6_fill_stats64.isra.0+0xe7/0x110 [ 3148.684375] ? __nla_validate_parse+0x42/0x140 [ 3148.684377] __rtnl_newlink+0x580/0x970 [ 3148.684380] ? __nla_put+0x20/0x30 [ 3148.684383] ? __kmalloc_node_track_caller+0x205/0x320 [ 3148.684385] ? pskb_expand_head+0x75/0x2d0 [ 3148.684387] ? __kmalloc_reserve.isra.0+0x31/0x90 [ 3148.684391] ? security_sock_rcv_skb+0x2f/0x50 [ 3148.684393] ? sk_filter_trim_cap+0x48/0x220 [ 3148.684395] ? skb_queue_tail+0x43/0x50 [ 3148.684397] ? __netlink_sendskb+0x42/0x50 [ 3148.684401] ? security_capable+0x3d/0x60 [ 3148.684404] ? _cond_resched+0x19/0x30 [ 3148.684406] ? kmem_cache_alloc_trace+0x16c/0x240 [ 3148.684408] rtnl_newlink+0x49/0x70 [ 3148.684410] rtnetlink_rcv_msg+0x2c0/0x380 [ 3148.684413] ? vsnprintf+0x35d/0x4e0 [ 3148.684414] ? rtnl_calcit.isra.0+0x100/0x100 [ 3148.684416] netlink_rcv_skb+0x50/0x120 [ 3148.684418] rtnetlink_rcv+0x15/0x20 [ 3148.684420] netlink_unicast+0x187/0x220 [ 3148.684422] netlink_sendmsg+0x222/0x3e0 [ 3148.684425] sock_sendmsg+0x65/0x70 [ 3148.684426] sys_sendmsg+0x212/0x280 [ 3148.684429] ___sys_sendmsg+0x88/0xd0 [ 3148.684431] ? rtnl_unlock+0xe/0x10 [ 3148.684433] ? addrconf_sysctl_forward+0x111/0x280 [ 3148.684436] ? get_max_files+0x20/0x20 [ 3148.684439] ? __fget_light+0x57/0x70 [ 3148.684441] __sys_sendmsg+0x5c/0xa0 [ 3148.68] __x64_sys_sendmsg+0x1f/0x30 [ 3148.684447] do_syscall_64+0x57/0x190 [ 3148.684450] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3148.684452] RIP: 0033:0x7f02e1a3b12d [ 3148.684454] Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 ca ee ff ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 48 89 44 24 08 e8 fe ee ff ff 48 [ 3148.684455] RSP: 002b:7fffaac61a40 EFLAGS:
[Bug 1877873] [NEW] Temperature becomes voltage after restarting panel
Public bug reported: My it8718 chip measures voltages, fan RPM and temperatures. I want to monitor what sensors.conf calls temp1, labelled "NBr Temp". I can set that up via the GUI and it works. But when I log out and back in or restart the Xfce panel, that shows +3.3V instead, which is in2 in sensors.conf. Furthermore, the label for in2 becomes "NBr Temp". Initially, before I tried to monitor "NBr Temp", that label was correctly displayed. This started working properly after I built xfce-sensors-plugin 1.3.92 from https://git.xfce.org/panel-plugins/xfce4-sensors-plugin/ This may be the bug, now fixed over there: https://bugzilla.xfce.org/show_bug.cgi?id=14398 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfce4-sensors-plugin 1.3.0-2build1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun May 10 11:23:05 2020 SourcePackage: xfce4-sensors-plugin UpgradeStatus: Upgraded to focal on 2020-04-06 (34 days ago) ** Affects: xfce4-sensors-plugin (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/1877873 Title: Temperature becomes voltage after restarting panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-sensors-plugin/+bug/1877873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] Re: memtest86+ hang on GA-P35-DS3R with X5470 and 6 GB
Source package differences between memtest86+ 3ubuntu2 (which does a whole pass without errors) and 3.1ubuntu1 (which locks up at 79% in test 1) don't seem to explain this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: memtest86+ hang on GA-P35-DS3R with X5470 and 6 GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] [NEW] memtest86+ hang on GA-P35-DS3R with X5470 and 6 GB
Public bug reported: Yesterday I booted into Ubuntu's memtest86+. I wasn't experiencing or expecting problems, and only wanted to make sure memory is okay after I had to remove modules to take the PSU out and put it back in. I ran it twice, and both times it hung at exactly 79% in the first test. Even fail safe mode hung exactly at that point. Then I booted with the floppy image from memtest86+-4.10.floppy.zip and it worked fine. Today I installed memtest86+_5.01-3ubuntu2_amd64.deb from Ubuntu 19.10 and that worked fine too. The failing version is 5.01-3.1ubuntu1. Memory configuration is 2 * 2 GB (F2-6400CL5-2GBPQ) and 2 * 1 GB (OCZ2G8001G) working in dual channel mode. CPU is Harpertown Xeon X5470 running at stock speed (3.33 GHz). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: memtest86+ 5.01-3.1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 13:51:01 2020 SourcePackage: memtest86+ UpgradeStatus: Upgraded to focal on 2020-04-06 (24 days ago) ** Affects: memtest86+ (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/1876157 Title: memtest86+ hang on GA-P35-DS3R with X5470 and 6 GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200
I did some more investigation and found that without the workaround the analog output only appears while headphones are plugged in. The SPDIF output disappears while headphones are plugged in. The bug has been submitted with this new information at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #852 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872791 Title: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200
It was easy to fix this by adding the following line to /etc/pulse/default.pa load-module module-alsa-sink device=hw:0,0 After doing that and rebooting, I had to set the analog device as the fallback device in pavucontrol. (Before the default.pa change, the SPDIF device had been the only playback device there.) So, sound works now. But, why did I have to do that? Why was the SPDIF device automatically detected but not the audio device? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872791 Title: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872791] [NEW] PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200
Public bug reported: PulseAudio currently doesn't see the analog audio output in my Dell Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the SPDIF output. This is the situation in both "pactl list sinks" and pavucontrol. I hear no sound from applications, probably because it's going to SPDIF. I don't have a way to listen to SPDIF to see if that is indeed the case. ALSA sees the analog output and "speaker-test -D plughw:0" plays sound through the laptop's speakers. This problem never happened in Ubuntu 19.10 and earlier. It might have worked earlier in 20.04 also, but I'm not sure of that. Rebooting didn't help. Purging and reinstalling pulseaudio and its automatically installed dependencies didn't help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic. ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1414 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 22 Simple ctrls : 9 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Apr 14 13:37:43 2020 InstallationDate: Installed on 2012-01-19 (3008 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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/1872791 Title: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
iommu=soft does not help, and I don't understand why it would help theoretically when the Core 2 Duo T7400 CPU doesn't have a hardware IOMMU. The problem seems to be that the 64 MB buffer is allocated beyond 1 GB. One theoretical good workaround would be to boot up with only 1 GB and then enable the rest of memory. But I'm not sure how to do that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
This problem still exists in Ubuntu Focal Fossa (development branch) 20.04 with linux-image-5.4.0-21-generic. It also exists in linux-image- unsigned-5.6.2-050602-generic_5.6.2-050602.202004020822_amd64.deb With linux-image-5.4.0-21-generic I didn't get any error messages after "insmod b44" in recovery mode. Also I normally booted linux- image-5.4.0-21-generic with mem=1G (limiting available memory to 1 GB) twice and also didn't get error messages after "sudo insmod b44". These symptoms are consistent with the hypothesis that swiotlb bounce buffers normally get allocated above 1 GB, causing a problem for b44 because the device can't do DMA above 1 GB and the driver can't handle this situation. That's the same problem discussed in this thread from 2011 https://groups.google.com/forum/#!topic/linux.kernel/GEx80ZCue1o Obviously limiting memory to 1 GB has an unacceptable performance penalty, but it's nice to have at least one way to get working Ethernet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860954] [NEW] b43 WiFi monitor mode doesn't work with BCM4321 card
Public bug reported: My Inspiron 6400 laptop has a Dell Wireless 1500 Draft 802.11n WLAN Mini-Card with BCM4321 chip. I was using airmon-ng from aircrack-ng to enter monitor mode. It claims the chipset is "non-mac80211 device? (report this!)" but I think that's incorrect information and only cosmetic. It does create the monitor device. Then I was using Wireshark to capture packets from that device. I was only getting beacon, probe request and probe response packets, despite knowing that there was data on the network. As a workaround, it is possible to properly monitor by using a different driver, from the broadcom-sta-dkms package. After installing that package and rebooting, I couldn't connect to my wireless network anymore, but I could "echo 1 | sudo tee /proc/brcm_monitor0" to create a prism0 device. Changing channels was a problem, maybe requiring a change on the associated non-monitor device before enabling the monitor. But capture on prism0 worked great. I was getting all kinds of packets and was able to decrypt data in Wireshark after enabling "Assume packets have FCS". Even though I couldn't connect to my network, I could capture and decrypt its traffic. Rebooting seems required for switching from b43 to wl drivers, because otherwise the wl driver doesn't start properly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-26-generic. ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1492 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 22 Simple ctrls : 9 CurrentDesktop: XFCE Date: Mon Jan 27 00:09:29 2020 HibernationDevice: RESUME=UUID=62d89c78-536c-42ab-968d-463122f8c3a2 InstallationDate: Installed on 2012-01-19 (2930 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda6 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (94 days ago) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1860954 Title: b43 WiFi monitor mode doesn't work with BCM4321 card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails
Right now in 19.10, /lib/systemd/system/fstrim.service runs /sbin/fstrim --fstab --verbose --quiet , which doesn't cause the service to report these errors. According to the fstrim man page, for the --fstab option: "Errors from filesystems that do not support the discard operation, read-only devices and read-only filesystems are silently ignored." So, I consider this fixed now. Feel free to close 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/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860938] [NEW] Sound interruptions during high radeon OpenGL load
Public bug reported: On my Dell Inspiron 6400 laptop with Mobility Radeon X1400 and built in Intel HDA audio with STAC9200 codec, audio is normally perfect. Even with 100% load on both CPU cores audio is perfect. However, while playing high resolution video, audio has many tiny regular interruptions which can be like crackles or micro stuttering. This happens when playing 1080p YouTube video in Chrome or 1080p video via VLC using the OpenGL output. Other high GPU load, like scrolling Google Maps around a lot in Chrome, can also cause these interruptions. They don't only affect the application causing graphical load, but also affect other applications playing audio, like mpg123. I've changed bdl_pos_adj, position_fix and enable_msi parameters of the snd_hda_intel module. Maybe bdl_pos_adj=64 and position_fix=1 makes it a bit better, but I'm not certain and it's certainly still not okay. I tried interrupt priorities as described in https://wiki.ubuntu.com/UbuntuStudio/rtirq and that didn't help. Changing latency via setpci seems not applicable because this laptop uses PCI Express. Not running PulseAudio and using ALSA instead doesn't help. Running a bare-bones X configuration with twm doesn't help. Configuring VLC to use XVideo video output makes audio perfect with the same video which was causing these interruptions when using OpenGL video output. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-26-generic. ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1646 F pulseaudio /dev/snd/pcmC0D0p: bgjenero 1646 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 22 Simple ctrls : 9 CurrentDesktop: XFCE Date: Sun Jan 26 16:45:23 2020 HibernationDevice: RESUME=UUID=62d89c78-536c-42ab-968d-463122f8c3a2 InstallationDate: Installed on 2012-01-19 (2929 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda6 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (93 days ago) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (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/1860938 Title: Sound interruptions during high radeon OpenGL load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
I don't normally use Ethernet on my laptop, and for some reason the b44 module for Ethernet doesn't get loaded normally. So I didn't notice this. But I'm getting the same problem reported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/comments/8 in Ubuntu 19.10 with linux-image-5.3.0-24-generic on my Inspiron 6400. This Debian bug report has some ideas about a cause: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939697 ** Bug watch added: Debian Bug tracker #939697 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939697 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855627] Re: projectM 2.1.0+dfsg-4build2 crashes with SIGABRT on first preset change
I'm also getting this crash in eoan. Building with a patch made from the commit linked in the Debian bug report ( https://github.com/projectM- visualizer/projectm/commit/c87f208c47252b47b117db73cc28a053d5133ffd ) makes it work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855627 Title: projectM 2.1.0+dfsg-4build2 crashes with SIGABRT on first preset change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/projectm/+bug/1855627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
linux-image- unsigned-4.20.0-042000-generic_4.20.0-042000.201812232030_amd64.deb is good but linux-image- unsigned-5.0.0-05rc1-generic_5.0.0-05rc1.201901062130_amd64.deb is bad. I'm not sure I'll have time for a git bisect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
Sorry, I mean bug is not present in 4.18.0-16-generic and present in 5.0.0-7-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821564] [NEW] b44 Ethernet driver null pointer during initialization
Public bug reported: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14: 7ffe93a35e7c R15: 6.485518] Modules linked in: arc4 b43 cordic snd_hda_codec_hdmi ttm bcma dell_laptop snd_hda_codec_idt snd_hda_codec_generic dell_smm_hwmon drm_kms_helper dell_wmi ledtrig_audio snd_hda_intel kvm mac80211 dell_smbios dcdbas drm joydev snd_hda_codec r852 irqbypass input_leds sm_common sparse_keymap wmi_bmof dell_wmi_descriptor snd_hda_core i2c_algo_bit snd_hwdep cfg80211 serio_raw snd_pcm nand fb_sys_fops snd_timer r592 syscopyarea nand_ecc snd nand_bch sysfillrect soundcore sysimgblt bch memstick mtd
[Bug 1364578] Re: Geeqie does not render the directory list and file list windows upon opening a directory with a large number of image files in it.
Using Geeqie 1:1.4+git20180820-1 in Ubuntu 18.10, I see that it does render the directory listing window. The problem is that the window takes a long time to render. During that time I still see a photo and can go to the next photo via the space bar, but the image overlay with the histogram and other information is messed up, with the part over the black bar outside the photo not drawn properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364578 Title: Geeqie does not render the directory list and file list windows upon opening a directory with a large number of image files in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geeqie/+bug/1364578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718720] Re: Sensors plugin settings lost and can't be set in 17.10
Maybe I was confused. I was just setting up xfce4-sensors-plugin 1.3.0-2 Ubuntu 18.10 and noticed something. When I double-click on the plugin it opens "Sensors Viewer". If I want to reconfigure the plugin I need to right click on it and select "Properties". This opens "Sensors Plugin". The confusing thing is that "Sensors Viewer" looks a lot like "Sensors Plugin" configuration. It even has "Show" checkboxes for the various temperatures, which makes it seem as if toggling those checkboxes should have some effect on the plugin. If I use the correct dialog for configuring the plugin, then I am able to reconfigure it and the configuration is saved properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718720 Title: Sensors plugin settings lost and can't be set in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-sensors-plugin/+bug/1718720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797717] [NEW] fstrim -av tries to trim read only mounted ntfs-3g and fails
Public bug reported: If I run sudo fstrim -av I see: /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor /: 26.9 GiB (28823887872 bytes) trimmed /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is read-only mounted NTFS, also via ntfs-3g. Lines from fstab: UUID=censored /media/SSD_Data ntfs-3g rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec 0 0 UUID=censored /media/Win7 ntfs-3g ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files 0 0 If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7 then sudo fstrim -av takes longer and succeeds for all filesystems. So, it seems the read only is the problem. This seems cosmetic, but it causes periodic runs of fstrim via systemd to report failures. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: util-linux 2.32-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 13 15:25:41 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu
This never happened in 18.04, and started happening after upgrading to 18.10. The keyring daemon when taking 100% CPU on one core also seems to hang and not respond to applications. I've had Chrome hang on startup, and I've had ssh and scp hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797417] Re: Background of system tray icons not drawn properly
My main computer with GeForce 8600 GT and driver 340.107-0ubuntu2 had Compton compositor running via Application Autostart in Session and Startup. Disabling that, logging out and logging back in brings up some corruption there as well. ** Attachment added: "Tray corruption on main computer" https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1797417/+attachment/5200149/+files/Nvidia%20GeForce%208600%20GT%20driver%20340.107-0ubuntu2%20xfce4-panel%204.13.3-1ubuntu1%20tray%20corruption.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797417 Title: Background of system tray icons not drawn properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1797417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797417] Re: Background of system tray icons not drawn properly
My main computer with GeForce 8600 GT and driver 340.107-0ubuntu2 had Compton compositor running via Application Autostart in Session and Startup. Disabling that, logging out and logging back in brings up some corruption there as well. ** Attachment added: "Tray corruption on main computer" https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1797417/+attachment/5200148/+files/Nvidia%20GeForce%208600%20GT%20driver%20340.107-0ubuntu2%20xfce4-panel%204.13.3-1ubuntu1%20tray%20corruption.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797417 Title: Background of system tray icons not drawn properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1797417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797417] Re: Background of system tray icons not drawn properly
Compositing was disabled. When I enabled it, the problem was fixed instantly. I have not seen any more signs of the problem with compositing enabled. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797417 Title: Background of system tray icons not drawn properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1797417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797417] [NEW] Background of system tray icons not drawn properly
Public bug reported: In Ubuntu 18.04 this problem did not exist. After upgrading to 18.10 the backgrounds of system tray icons in the Xfce panel are not drawn properly on my Inspiron 6400 laptop with ATI/AMD Mobility Radeon X1400 graphics and the open source radeon driver. This problem does not exist in 18.10 on my main PC with Nvidia 8600GT and their proprietary drivers. The background of the system tray icons is not simply black. Look at the network icon. The previous contents of the icon are visible behind the WiFi signal bars. Though, now that I tried installing libxfconf-0-2_4.12.1-1_amd64.deb and xfce4-panel_4.12.2-1ubuntu1_amd64.deb from Ubuntu 18.04 I see some glitches in the system tray, though not as bad. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xfce4-panel 4.13.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 11 12:04:26 2018 InstallationDate: Installed on 2012-01-19 (2457 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: xfce4-panel UpgradeStatus: Upgraded to cosmic on 2018-10-11 (0 days ago) ** Affects: xfce4-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "This shows the problem" https://bugs.launchpad.net/bugs/1797417/+attachment/5200105/+files/xfce4-panel%204.13.3-1ubuntu1%20tray%20icon%20background%20drawing%20bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797417 Title: Background of system tray icons not drawn properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1797417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763967] Re: rmmod b43 hangs
rmmod b43 works in 4.15.0-21-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763967 Title: rmmod b43 hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] [NEW] Battery graph in tray icon is inaccurate
Public bug reported: xfce4-power-manager has a tray icon which shows current status and has a graph when a battery is inserted. The green bar in the icon should be showing current battery level, but it varies weirdly. If I place my mouse cursor over the icon the tooltip which appears shows the actual battery level. Now it is charging, 44%, but the graph is more like 80%. Earlier while discharging at around 28% the green was absent, as if it was 0%. Both times I verified via the tooltip. So, the package has correct info but is graphing it incorrectly. It is not simply old info because it changes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfce4-power-manager 1.6.1-0ubuntu1 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 27 23:05:53 2018 InstallationDate: Installed on 2012-01-19 (2291 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to bionic on 2018-03-11 (48 days ago) ** Affects: xfce4-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767560 Title: Battery graph in tray icon is inaccurate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763967] Re: rmmod b43 hangs
Bug does not exist in 4.16.2-041602-generic. I did rmmod b43 4 times and it always succeeded immediately. It never worked properly in 4.15.0-13-generic so I am confident this isn't just random success, and it means the bug is fixed in upstream. What older version should I try? Currently I don't have any old versions available. ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763967 Title: rmmod b43 hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763967] [NEW] rmmod b43 hangs
Public bug reported: I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43" always hangs. So far I have only tried it while connected to a wireless network. I immediately disconnect from the wireless network, so it seems module removal does begin. But the rmmod process never finishes and is unkillable. The hang seems indefinite, and a normal reboot is not possible, the rapid ctrl-alt-del systemd emergency reboot is impossible, and only a Magic SysRq reboot works. This worked in Ubuntu 17.10, but always fails in Ubuntu 18.04. (I was unloading the module before suspend due to occasional problems after resume. I tracked this down when wondering why suspend was hanging. Even running the "rmmod b43" on its own without suspend happening causes the hang. Right now I disabled that automatic unloading.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-13-generic. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1560 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 22 Simple ctrls : 9 CurrentDesktop: XFCE Date: Sat Apr 14 11:54:36 2018 HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18 InstallationDate: Installed on 2012-01-19 (2277 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-03-11 (34 days ago) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763967 Title: rmmod b43 hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754911] Re: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
In 4.15.0-13-generic, BCM4321 WiFi works via b43 and BCM4401-B0 b44 Ethernet eth0 exists. So, it seems this has been fixed. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754911 Title: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754911] Re: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.9/ I installed: linux-headers-4.15.9-041509_4.15.9-041509.201803111231_all.deb linux-headers-4.15.9-041509-generic_4.15.9-041509.201803111231_amd64.deb linux-image-4.15.9-041509-generic_4.15.9-041509.201803111231_amd64.deb And booted into 4.15.9-041509-generic on my Inspiron 6400. BCM4321 WiFi works via b43 and BCM4401-B0 b44 Ethernet eth0 exists. In other words, this bug does not exist in 4.15.9-041509-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754911 Title: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754911] Re: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
After installing linux-headers-4.16.0-041600rc4_4.16.0-041600rc4.201803041930_all.deb , linux-headers-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb and linux-image-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/ and booting 4.16.0-041600rc4-generic I have eth0. So, apparently this is fixed in later kernel versions. I am still encountering https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752081 "platform regulatory.0: Direct firmware load for regulatory.db failed with error -2" but wireless now works nevertheless. I originally reported this bug for the wired Ethernet interface because I wasn't sure if that other bug was causing wireless to not work. Now I'm thinking this same bug was probably making wireless not work either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754911 Title: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754911] [NEW] b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
Public bug reported: When I boot linux-image-4.13.0-36-generic then I get an eth0 interface and dmesg output includes: ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x42 43) b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0 b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00 When I boot linux-image-4.15.0-10-generic those lines don't appear and I don't get an eth0 interface. Doing modprobe b44 doesn't help. This is on a Dell Inspiron 6400. I wonder if I'm running into this bug: https://patchwork.kernel.org/patch/10185397/ I'm reporting it while running linux-image-4.13.0-36-generic because I also can't get wireless to work in 4.15, so I can't report from there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-36-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1449 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 22 Simple ctrls : 9 CurrentDesktop: XFCE Date: Sat Mar 10 20:55:15 2018 HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18 InstallationDate: Installed on 2012-01-19 (2243 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) JournalErrors: -- Logs begin at Sat 2018-03-10 18:57:57 EST, end at Sat 2018-03-10 20:55:01 EST. -- Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus: Failed to construct signal Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754911 Title: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737522] [NEW] cfq scheduler can write parts of sequential write in reverse order
Public bug reported: I'm opening a raw disk device (like /dev/sdb) with O_DIRECT and then doing write() calls. The device is actually USB mass storage. Looking at the USB packets with Wireshark, I see that the write() calls are being split into multiple SCSI writes. That part is okay I guess. The problem is that these writes can happen in reverse order. Suppose the write() call is writing to sectors 100 to 200. The first SCSI write may write 150 to 200 and the second SCSI write may write 100 to 149. Correctness does appear to be maintained. I only had a problem with correctness because I'm abusing the protocol for writing to a hacked digital photo frame via https://github.com/dreamlayers/st220x/blob/master/libst2205/st2205.c . The photo frame doesn't fully process the protocol and only looks at the data as a series of USB packets. However, this is bad for performance with hard disks. Surely if you have a sequential write, the optimal way to do that write is sequentially from start to finish. Since changing the scheduler for that block device from cfq to noop fixes this problem, I assume it has to do with the elevator algorithm use to optimize hard disk access. But surely such optimization only makes sense between contiguous sequential writes, and not for splitting up one such write. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-19-generic. ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2116 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfa20 irq 30' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100101' Controls : 63 Simple ctrls : 26 CurrentDesktop: XFCE Date: Mon Dec 11 05:23:12 2017 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=52543c1b-1764-4766-a504-f4b94422fa6e ro RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-09-30 (71 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737522 Title: cfq scheduler can write parts of sequential write in reverse order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718720] Re: Sensors plugin settings lost and can't be set in 17.10
I don't know of any way to make this work with the package from 17.10 / Artful, but installing the current 1.2.6-1 xfce4-sensors-plugin from 17.04 / Zesty makes the plugin work. No other changes were needed. With the plugin from Zesty the plugin output on the panel immediately changes when I change settings. I got it from: https://packages.ubuntu.com/zesty/amd64/xfce4-sensors-plugin/download -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718720 Title: Sensors plugin settings lost and can't be set in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-sensors-plugin/+bug/1718720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718720] [NEW] Sensors plugin settings lost and can't be set in 17.10
Public bug reported: In past versions of Ubuntu, the XFCE sensors plugin worked. I just upgraded to Artful 17.10 and it does not work anymore. The problem seems to be that settings were lost and cannot be configured anymore. All I see on the panel is the word "Sensors" in bold. Double clicking that gives me a configuration dialog. My old settings are gone. I can change settings in the dialog, but after I close and re-open the dialog I always see the same settings, as if I made no changes. The weather plugin also lost settings when I upgraded to Artful, but after I configured it, the settings were remembered, even after a reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xfce4-sensors-plugin 1.2.6-1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 21 12:06:33 2017 InstallationDate: Installed on 2012-01-19 (2072 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: xfce4-sensors-plugin UpgradeStatus: Upgraded to artful on 2017-09-21 (0 days ago) ** Affects: xfce4-sensors-plugin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718720 Title: Sensors plugin settings lost and can't be set in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-sensors-plugin/+bug/1718720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678271] Re: Background color erase (bce) is broken
I tried installing some old libraries and binaries from Yakkety but even with that I couldn't reproduce it in Ubuntu 17.04. I don't have any more Yakkety systems to test on. I also can't reproduce it in 16.04.2 LTS in Windows 10. I don't think any DOSBox changes could have changed this either. So I'm a bit mystified here. Sorry about wasting your time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678271 Title: Background color erase (bce) is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1678271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678271] Re: Background color erase (bce) is broken
I'm not able to reproduce this now in Zesty with gnome-terminal 3.20.2-1ubuntu8. Program that was causing problems before is DOSBox SVN with ncursesw output added, https://github.com/dreamlayers/em- dosbox/tree/contxt-only but that works fine now. infocmp $TERM shows I'm using /lib/terminfo/x/xterm-256color and bce is present there, so it seems bce now works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678271 Title: Background color erase (bce) is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1678271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677961] Re: xfce4-terminal crashes if input arrives too soon after resize
I'm not able to reproduce this in Zesty xfce4-terminal 0.8.4-1. So, it seems you're right and this has been fixed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677961 Title: xfce4-terminal crashes if input arrives too soon after resize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/1677961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680642] [NEW] xdg-icon-resource does not set permissions when installing icon
Public bug reported: When installing an icon using a command such as "sudo xdg-icon-resource install --novendor --context apps --size 256 synaesthesia.png synaesthesia", the ownership of the file created at /usr/local/share/icons/hicolor/256x256/apps/synaesthesia.png is set to root:root, but the permissions aren't changed. I ran into this problem when installing a .desktop file and icon and finding that the icon failed to show up. The problem was that the .png file was not world readable, and so after the ownership was changed it was not readable to me anymore. xdg-icon-resource does at least remove the setuid and setgid bits, so although I can make a copy of bash with the .png extension, install that, and run it, I can't use this to make a setuid root bash. "sudo xdg-desktop-menu install" seems to do the same thing with the files it puts in /usr/share/applications ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xdg-utils 1.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 6 20:40:29 2017 PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: Upgraded to yakkety on 2016-10-13 (175 days ago) ** Affects: xdg-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680642 Title: xdg-icon-resource does not set permissions when installing icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1680642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671954] Re: SDL 2 full screen mode changes broken with nvidia-340
https://bugzilla-attachments.libsdl.org/attachment.cgi?id=1715 does not fix the issue I reported. I still can't get full screen mode to work properly. Normally I still get the large scrolling virtual desktop issue, and with SDL_VIDEO_X11_XRANDR=0 set in the environment things are even worse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671954 Title: SDL 2 full screen mode changes broken with nvidia-340 To manage notifications about this bug go to: https://bugs.launchpad.net/libsdl/+bug/1671954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678271] [NEW] Background color erase (bce) is broken
Public bug reported: I'm running my ncursesw application, displaying a black background. When the screen or a region scrolls up by one line, empty areas of the screen in the newly visible line show the default white background of gnome- terminal. If I remove the bce capability from the Terminfo for that terminal type, the problem goes away. This workaround involves: "infocmp xterm-256color > xt.ti" to get the Terminfo data in text format. Editing xt.ti and removing "bce, " on the 3rd line "tic xt.ti" to compile this text to Terminfo again. Without sudo that ends up in ~/.terminfo, overriding the system's entry, and with sudo it would overwrite the system's Terminfo entry for that terminal type. Another workaround would be to use a different terminal type without bce, like TERM=screen, but removing bce is better because that leaves other capabilities intact. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.20.2-1ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 13:49:01 2017 SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-13 (169 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678271 Title: Background color erase (bce) is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1678271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677961] [NEW] xfce4-terminal crashes if input arrives too soon after resize
Public bug reported:
If I start with an 80x24 terminal, resize to 80x25 with printf("\e[8;25;80t")
and then quickly send output via Ncurses, then xfce4-terminal crashes:
Vte-0.0:ERROR:/build/vte-jOPZPt/vte-0.28.2/./src/ring.c:370:_vte_ring_thaw_one_row:
assertion failed: (ring->start < ring->writable)
Aborted (core dumped)
All the xfce4-terminal windows run in the same process. When you run it
a second time from the command line, it just opens a new window in the
old process and quits. So, if you want to view that error output, close
all xfce4-terminal windows and start the program again from another
terminal program, like xterm.
Adding a half second delay after the escape sequence makes the problem
go away.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xfce4-terminal 0.6.3-2ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Mar 30 23:55:41 2017
InstallationDate: Installed on 2012-01-19 (1898 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: xfce4-terminal
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (168 days ago)
** Affects: xfce4-terminal (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677961
Title:
xfce4-terminal crashes if input arrives too soon after resize
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/1677961/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671954] Re: SDL 2 full screen mode changes broken with nvidia-340
SDL 2 is able to go back to the proper desktop resolution when exiting full screen if and only if the top left corner of the current viewport is at the top left of the displayed area. In other words, if I don't scroll the viewport right or down by going to those edges with the mouse, or if I scroll it and then scroll back to the left and top limits, only then do I go back to the proper resolution in desktop mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671954 Title: SDL 2 full screen mode changes broken with nvidia-340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1671954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671954] [NEW] SDL 2 full screen mode changes broken with nvidia-340
Public bug reported: I have a GeForce 8600GT card and am using nvidia-340 drivers, version 340.101-0ubuntu0.16.10.1. Going into full screen mode results in a mode smaller than the displayed area, where the mouse can be used to scroll the screen viewport around. Returning from full screen mode does not reset things back to the desktop mode, and instead leaves it in the same mode. Both of these behaviours seem broken. SDL 1 mode changes work. Also xrandr mode changes work. That's why I'm reporting this as an SDL 2 bug, not an nvidia-340 bug. Earlier I dealt with an nvidia-340 bug https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-340/+bug/1671920 but that is solved and I don't think that's why this is failing. I'm attaching a small program which can be used to examine this behaviour. It can be built for SDL 1 and SDL 2 by supplying appropriate -I directory and -l libary, as in: gcc -I/usr/include/SDL sdl_togglefullscreen.c -lSDL -o sdl_togglefullscreen1 gcc -I/usr/include/SDL2 sdl_togglefullscreen.c -lSDL2 -o sdl_togglefullscreen2 If reproducing this bug make sure xrandr is installed so you can go back to your desired resolution if SDL 2 fails to go back to it. Use something like xrandr --output DVI-I-2 --mode 1600x1200 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libsdl2-2.0-0 2.0.4+dfsg2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 10 17:09:30 2017 SourcePackage: libsdl2 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (148 days ago) ** Affects: libsdl2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "Program for reproducing bug" https://bugs.launchpad.net/bugs/1671954/+attachment/4835568/+files/sdl_togglefullscreen.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671954 Title: SDL 2 full screen mode changes broken with nvidia-340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1671954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671920] [NEW] Mode changes fail unless some xorg.conf screen options are set
Public bug reported: The first mode change always works, but subsequent mode changes keep failing. Running xrandr --output DVI-I-2 --mode 1600x1200 to go back to the native resolution or any other supported resolution fails with: xrandr: Configure crtc 0 failed X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 21 (RRSetCrtcConfig) Value in failed request: 0x0 Serial number of failed request: 38 Current serial number in output stream: 38 Mode changes from SDL 1.2 and 2.0 also fail, and a SDL 1.2 program is killed by the error when returning from full screen. These are changes for modes on my first monitor, which I use all the time. I think the bug is happening because the second monitor provides invalid EDID while turned off via the switch on the back. Everything works if the switch on the back of the second monitor is turned on or if an /etc/X11/xorg.conf file with sufficient options in the screen section is in place. Ubuntu upgrades rename the xorg.conf file and deactivate it, and I was running into the bug because of that. I'm not yet sure which option lines in the screen section are required. I'm attaching my normal xorg.conf file, which makes things work. I'm calling this a bug because the second monitor shouldn't break mode changes on the first monitor. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nvidia-340 340.101-0ubuntu0.16.10.1 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 10 15:12:33 2017 SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (148 days ago) modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "This xorg.conf file makes the problem go away" https://bugs.launchpad.net/bugs/1671920/+attachment/4835491/+files/xorg.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671920 Title: Mode changes fail unless some xorg.conf screen options are set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1671920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665497] [NEW] Icon with x is confusing: volume could be muted or turned down to zero
Public bug reported: If audio is muted, then instead of the volume level arcs in front of the speaker icon, there is an x. Mute button needs to be pressed to get sound. Volume keys still affect the volume setting, but there is no visual indication of that on the icon, or any audio indication because audio is muted. If volume is turned all of the way down, the exact same icon is displayed. The volume needs to be increased to get sound. The mute button does actually work, but nothing seems to happen when you press it, because the same icon with the x is displayed always, and there is never any sound due to volume being turned down. If you think that sound was muted but the volume was only turned all the way down, you press the mute button, but nothing changes. Then if you try to increase the volume again nothing changes, because you just muted sound. This is ridiculously confusing. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-pulseaudio-plugin 0.2.4-1 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 16 19:55:20 2017 SourcePackage: xfce4-pulseaudio-plugin UpgradeStatus: Upgraded to yakkety on 2016-10-13 (126 days ago) ** Affects: xfce4-pulseaudio-plugin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665497 Title: Icon with x is confusing: volume could be muted or turned down to zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-pulseaudio-plugin/+bug/1665497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647709] Re: Can't connect to WiFi if setting MAC address, RTNETLINK answers: Device or resource busy
This seems to be an old bug, which is also mentioned elsewhere: https://unix.stackexchange.com/questions/26126/spoofed-mac-address-ignored-by-wpa-supplicant https://bugs.launchpad.net/neutron/+bug/1193972 Another symptom of this bug is probably inability to connect if you need the changed MAC address to successfully authenticate. As a workaround, use: pre-up ifconfig wlan0 hw ether xx:xx:xx:xx:xx:xx Instead of: hwaddress ether xx:xx:xx:xx:xx:xx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647709 Title: Can't connect to WiFi if setting MAC address, RTNETLINK answers: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1647709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647709] [NEW] Can't connect to WiFi if setting MAC address, RTNETLINK answers: Device or resource busy
Public bug reported: If my /etc/network/interfaces settings for wlan0 include a "hwaddress ether" line, then running ifup for that interface fails at the very end, after successfully authenticating with the access point. Here is what happens: systemd[1]: Started ifup for wlan0. wpa_supplicant[765]: Successfully initialized wpa_supplicant sh[737]: RTNETLINK answers: Device or resource busy sh[737]: Failed to bring up wlan0. systemd[1]: ifup@wlan0.service: Main process exited, code=exited, status=1/FAILURE wpa_supplicant[791]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Furthermore, this kind of failure leaves a mess somehow, and subsequent attempts to connect lead to "RTNETLINK answers: File exists". ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ifupdown 0.8.13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 6 07:48:55 2016 InstallationDate: Installed on 2012-01-19 (1783 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: ifupdown UpgradeStatus: Upgraded to yakkety on 2016-10-13 (53 days ago) ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647709 Title: Can't connect to WiFi if setting MAC address, RTNETLINK answers: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1647709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453404] Re: r8169 occasionally doesn't work after suspend
After upgrading to Ubuntu 16.10 I removed the r8168-dkms package so I could see if this bug still exists in 4.8.0 kernels. I upgraded on October 13th, and everything worked fine until today, October 24th. After waking from sleep eth0 appeared up according to ifconfig, but I had no connectivity and couldn't even ping other devices on the LAN. This fixed itself after ifconfig down followed by ifconfig up. I never had to do such a thing while using r8168-dkms. So, it seems the bug still exists, and I will reinstall r8168-dkms now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453404 Title: r8169 occasionally doesn't work after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1479136] Re: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards
I wonder if this is the same bug which I am seeing on my Dell Inspiron 6400 laptop with Radeon X1400 video. Occasionally I get white lines which are very similar to the https://www.youtube.com/watch?v=nx2-Fvihzxg video posted at the beginning. The only difference is that more lines are present at screen edges and high contrast borders. Line length and the way they flicker is very similar. This problem has been present over multiple Ubuntu versions, and is still present in 64-bit Ubuntu 16.10 with kernel 4.8.0-26-generic. In the past I posted about the problem at: https://ubuntuforums.org/showthread.php?t=2322535 Sometimes I've gotten worse corruption like how Ivan Zakharyaschev (imz) wrote "sometimes the flickering did appear as some regions (with text) displayed at another place on the screen appearing extremely quickly and transparently also at a wrong places at the top." This is more rare than the white lines, and has not happened in Ubuntu 16.10 yet. Changing video modes can start or stop corruption. So, if I have corruption, run a script which uses xrandr to change to a lower resolution and back to the native resolution. This usually works in one try but sometimes takes a few tries. The problem happens rarely enough that it's not a big deal, but a fix would be nice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479136 Title: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629617] [NEW] File corruption with ext4 dump and restore
Public bug reported: I used Ubuntu 16.04.1 LTS dump and restore version 0.4b44-7 to dump and restore a Raspbian Jessie ext4 file system from an SD card. After restoring, the _CACHE_00?_ files from ~/.cache/mozilla/firefox//Cache/ have differing contents. On the original file system they consist of all zero bytes, but on a restored file system they have large sections of non-zero bytes near the end. All other files match by MD5 sum, and the restored dump is usable. There are no error messages during dump or restore. These same files are affected every time. This seems to be a deterministic problem relating to these files, and not an issue with the SD card or reader. The file system passes fsck.ext4 -f without any errors. The bug has already been reported as upstream bug https://sourceforge.net/p/dump/bugs/162/ by someone else. There is no fix yet. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dump 0.4b44-7 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 1 23:17:05 2016 SourcePackage: dump UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dump (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629617 Title: File corruption with ext4 dump and restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dump/+bug/1629617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875991] Re: Not able to start a xsession with a space in the name
This seems to be a bug in gconf-common. LXDM sets the DESKTOP_SESSION environment variable to the Name string from the desktop file, and /etc/X11/Xsession.d/70gconfd_path-on-session cannot handle the space due to lack of quoting. I'm not sure if setting DESKTOP_SESSION to the Name from the .desktop file and having a space in it is wise, but everything seems to work after fixing the quoting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875991 Title: Not able to start a xsession with a space in the name To manage notifications about this bug go to: https://bugs.launchpad.net/lxde/+bug/875991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588395] [NEW] 70gconfd_path-on-session doesn't quote DESKTOP_SESSION and fails if it contains a space
Public bug reported:
In /etc/X11/Xsession.d/70gconfd_path-on-session these lines fail if
there is a space in ${DESKTOP_SESSION}:
export MANDATORY_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.mandatory.path
export DEFAULTS_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.default.path
The error output to ~/.xsession-errors is:
/etc/X11/Xsession: 6: export: Session.mandatory.path: bad variable name
I'm not sure why the error is pointing to the wrong file. Adding quotes around
the variables in those lines makes the error go away. This error totally
prevents logging into X. It happens when using LXDM to start Xfce, because LXDM
sets DESKTOP_SESSION to Name from /usr/share/xsessions/xfce.desktop :
Name=Xfce Session
These LXDM bugs relate to the problem, but I guess the lack of quoting
here is the root cause. I'm not sure if setting DESKTOP_SESSION to the
Name from the .desktop file and having a space in it is wise, but
everything seems to work after fixing the quoting. Proper quoting is
used elsewhere.
https://sourceforge.net/p/lxde/bugs/420/
https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/875991
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gconf2-common 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jun 2 10:16:46 2016
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: gconf
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gconf (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588395
Title:
70gconfd_path-on-session doesn't quote DESKTOP_SESSION and fails if it
contains a space
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1588395/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392204] Re: Huge CPU usage by mount.ntfs process
I'm also having this problem copying to an external USB 3 drive, with Nemo (Cinnamon file manager) copies around 35 MiB/s on my Q6600 CPU. big_writes helped, but although file copying via Nemo sped up to around 60 MiB/s, it was still CPU bound. Copying via pv < source_file > dest_file is faster and not CPU bound, around 130 MiB/s. pv without big writes is CPU bound at 90 MiB/s, so Nemo seems to be the main culprit in my case. This is in Xenial Xerus (development branch) 16.04 64-bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/392204 Title: Huge CPU usage by mount.ntfs process To manage notifications about this bug go to: https://bugs.launchpad.net/ntfs-3g/+bug/392204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539630] Re: Xorg display corruption, Dell Inspiron 6400, Lucid Beta ISO test
I'm getting a similar bug in 16.04 on my Inspiron 6400 with X1300 and a 1680x1050 display. I have disabled graphical overlays during boot because I prefer to see boot text. Corruption starts after the switch from ordinary VGA text mode to a high resolution text mode which I assume is implemented using a graphics mode. In that text mode, corruption is mostly flashing long vertical bright bars rising from the bottom. In X, corruption is mostly short horizontal lines on a dark area to the right of a bright area, and the long vertical bars seen in text mode rarely appear. The corruption never propagates via screen operations like scrolling, so it doesn't seem to be in memory. It's as if there is something wrong with the video mode or LVDS communication with the display. I made the corruption go away in X by first switching to a lower resolution via "xrandr --output LVDS --mode 1400x1050" and then going back to the native resolution via "xrandr --output LVDS --mode 1680x1050". I'm not getting any corruption in Windows 7, so I don't think this is a hardware problem. ** Attachment added: "Vertical bar corruption in text mode" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/539630/+attachment/4599344/+files/P3140013.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/539630 Title: Xorg display corruption, Dell Inspiron 6400, Lucid Beta ISO test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/539630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309617] Re: plymouth-upstart-bridge main process (189) terminated with status 1 at boot
I never experienced any significant problems because of this bug. It only results in those error messages. If your system fails to boot or other things crash, that is probably due to a different unrelated issue. The "sleep" in /etc/init/plymouth-upstart-bridge.conf does make these error messages go away, but it gives an "Unknown stanza" error instead, so it's not really a solution. I'm not even sure if plymouth-upstart- bridge runs when there is an unknown stanza there, so it could make things worse. This problem is not present in recent Ubuntu versions when using systemd instead of upstart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309617 Title: plymouth-upstart-bridge main process (189) terminated with status 1 at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1309617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453404] Re: r8169 occasionally doesn't work after suspend
I refuse to test this with the latest upstream kernel. That is because the bug happens rarely and the upstream kernel breaks other stuff. I would have to use Ubuntu for a prolonged period with the upstream kernel, putting up with that brokenness, or I would have to go into suspend and wake many times quickly, which I believe is not good for my hardware. Feel free to delete this bug because of this refusal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453404 Title: r8169 occasionally doesn't work after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453404] [NEW] r8169 occasionally doesn't work after suspend
Public bug reported: Occasionally the onboard gigabit Ethernet on this Gigabyte GA-P35-DS3R rev 1.0 motherboard doesn't work after suspend. This happens less than one out of ten times. Over the last several Ubuntu releases, sudo ifconfig eth0 down followed by sudo ifconfig eth0 up has always been enough to re-establish connectivity. A long time ago, I sometimes had to unload and reload the r8169 module. This was the first time this bug happened in Ubuntu 15.04. A similar bug already exists at https://bugs.launchpad.net/linux/+bug/771857 . I am reporting this here because the last comment there asks for a report via ubuntu-bug linux. Right now, as a workaround, I'm installing the r8168-dkms package, which includes the proprietary Realtek driver. Here is lspci -v output for this ethernet controller: 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Motherboard Flags: bus master, fast devsel, latency 0, IRQ 29 I/O ports at d000 [size=256] Memory at f900 (64-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at f800 [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c ? Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting ? Kernel driver in use: r8169 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2673 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sat May 9 10:57:05 2015 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 InstallationDate: Installed on 2012-01-19 (1206 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (15 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453404 Title: r8169 occasionally doesn't work after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771857] Re: Realtek 8168B (r8169) interface not working following suspend
This keeps happening to me occasionally, less than one out of ten times. Over the last several Ubuntu releases, sudo ifconfig eth0 down followed by sudo ifconfig eth0 up has always been enough to re- establish connectivity. A long time ago, I sometimes had to unload and reload the r8169 module. This was the first time this bug happened in Ubuntu 15.04. I just filed a new report using ubuntu-bug linux: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453404 As a workaround, I'm installing the r8168-dkms package, which includes the proprietary Realtek driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771857 Title: Realtek 8168B (r8169) interface not working following suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/771857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033676] Re: Dell Inspiron 6400 WiFi light will not stop flashing
This happened to me once when I was trying to connect to WiFi from the command line. It seemed to happen because multiple wpa_supplicant processes were running. You could try ps xa | grep wpa_supplicant to see if you have multiple processes running. Doing sudo killall wpa_supplicant stopped it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033676 Title: Dell Inspiron 6400 WiFi light will not stop flashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-do/+bug/1033676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450088] Re: Wakes from S3 in a few seconds unless WIndows has been run
I solved the problem. This was wake on LAN. When I ran sudo ethtool eth0 the output included: Supports Wake-on: pumbg Wake-on: ug From the ethtool man page: u Wake on unicast messages g Wake on MagicPacket™ This was wake on unicast messages. Wake-on: ug is the default both with the r8169 driver that's included in the kernel and with the r8168-dkms package which presumably contains the driver from Realtek. I guess the BIOS sets it up this way. I see no BIOS options relating to wake on LAN. I disabled wake on LAN via the Advanced settings in Device Manager in Windows, and that was persisting until all power including standby power was cut. I am now disabling WOL with the following line in /etc/rc.local: ethtool -s eth0 wol d I also tried ethtool -s eth0 wol g which only wakes on magic packet and I didn't get an unexpected wakeup. Enabling wake on unicast messages by default is ridiculous. I guess this may be the fault of my BIOS. I'm not sure if there's anything Linux could do about that automatically. I just wish Linux would tell me what's the wake reason! If I saw something telling me this was wake on LAN I would have spent much less time figuring this out! Here's sudo lspci -v info about the ethernet controller, 10ec:8168: 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Motherboard Flags: bus master, fast devsel, latency 0, IRQ 29 I/O ports at d000 [size=256] Memory at f900 (64-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at f800 [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c ? Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting ? Kernel driver in use: r8169 My suspend tests were using this command to initiate suspend, running as a normal user: dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true The attached /proc/acpi/wakeup file is in the state used during my most recent testing. I am disabling everything there via /etc/rc.local, but that didn't solve the problem. I never got any matches in my resume trace, just magic numbers. Anyways, that data should only be relevant if there is a lockup while going to sleep or resuming. ** Attachment added: /proc/acpi/wakeup https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450088/+attachment/4388745/+files/wakeup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450088 Title: Wakes from S3 in a few seconds unless WIndows has been run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405784] Re: /usr/sbin/fancontrol: line 492: [: too many arguments
This also affects me in vivid. The problem is that min_fanval wasn't set. Up
above it is set inside an
if [[ -n ${fan} ]] block, so it's not set if you're not using fan RPM
sensors. This was fixed in r6255: http://lm-sensors.org/changeset/6255
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405784
Title:
/usr/sbin/fancontrol: line 492: [: too many arguments
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lm-sensors-3/+bug/1405784/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450088] Re: Wakes from S3 in a few seconds unless WIndows has been run
I can reproduce this with v4.1-rc1-vivid. I had to uninstall nvidia-340-updates because the DKMS module failed to build and boot hung while it was installed. So, I was using nouveau for my GeForce 8600GT PCI express graphics card. I can't reproduce it if not running X, or running X, twm and xterm or GNOME terminal. However, if I run Google Chrome in addition to that, I can reproduce it. Also, I can always reproduce it when using Openbox or Cinnamon. Successful sleep in Linux (without an unexpected wakeup) does not prevent future wakeups when conditions change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450088 Title: Wakes from S3 in a few seconds unless WIndows has been run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450088] [NEW] Wakes from S3 in a few seconds unless WIndows has been run
Public bug reported: I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0 motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power was fully cut, including standby power, and Windows has not been run since then, Ubuntu will quickly wake from S3 sleep without any apparent reason. Procedure to reproduce: 1. Shut down computer normally from the operating system. 2. When computer appears off, cut power either via the switch on the back or by unplugging it. 3. Wait some time. 10 seconds is probably enough and a minute should be 100% certain. 4. Boot directly into Ubuntu. It's okay to boot into Ubuntu via the Windows 7 boot menu. Do not actually boot into Windows itself though; if you do that you must restart at step 1. 5. Initiate S3 sleep. I have tried both of these with the same results: dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true sudo sh -c echo mem /sys/power/state 6. Wait. The system should wake up within a few seconds, and certainly in less than a minute. The delay varies. The only problem is that the system won't stay sleeping. Everything works fine after the system wakes. Repeated attempts to sleep give the same result. I have disabled everything in /proc/acpi/wakeup using the following in /etc/rc.local: sed -n '/enabled/s,\([^\t]\+\)\s.*$,echo \1 /proc/acpi/wakeup,p' /proc/acpi/wakeup | sh I confirm that it appears disabled before and after sleep. I have also disabled all wakeup files in sys (found via sudo find /sys -iname wakeup -type f), and it didn't help. The logs don't seem to show a wakeup reason. If I boot into Windows 7 and then boot into Linux, this problem stops happening. Shutting down from either operating system or pressing the reset button does not cause the problem to reoccur. It only reoccurs if standby power has been cut. I am assuming that Linux fails to perform some initialization which Windows performs, and that initialization persists as long as standby power is available. I am assuming this is a kernel bug because it occurs even if I use echo mem /sys/power/state to enter sleep. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2280 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Apr 29 10:39:49 2015 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 InstallationDate: Installed on 2012-01-19 (1196 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (5 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450088 Title: Wakes from S3 in a few seconds unless WIndows has been run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261730] Re: /dev/sda1 must be recovered on every boot
In 14.10 amd64, mountall keeps running, causing init to keep /var/log/upstart/mountall.log open for writing, which prevents root from being remounted read-only. These things are easy to examine by adding a /bin/sh line to /etc/init.d/reboot in do_stop() before reboot -d -f -i. Then when you reboot you can switch to virtual console 1 and use lsof and other commands to explore what is going on. For example this is the line in lsof output showing the problem: init 1 root8w REG8,5 613 1062101 /var/log/upstart/mountall.log I added a /usr/bin/killall mountall line to /etc/init.d/umountroot before root is supposed to be remounted read-only. That seems to fix the problem. You need the full path because /usr/bin isn't in PATH, and don't use -9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261730 Title: /dev/sda1 must be recovered on every boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1261730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309617] Re: plymouth-upstart-bridge main process (189) terminated with status 1 at boot
Adding sleep 2 results in a different error: init: /etc/init /plymouth-upstart-bridge.conf:18: Unknown stanza. I wonder if this causes plymouth-upstart-bridge to not run at all? I have not encountered any problems running like that for many months, but I wonder if some situations could lead to problems. Is plymouth-upstart-bridge needed by programs which may require user interaction during boot, such as fsck? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309617 Title: plymouth-upstart-bridge main process (189) terminated with status 1 at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1309617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064185] Re: root partition not unmounting cleanly on reboot
I was getting this problem in 12.10 and I continued to get it after an upgrade to 13.04. Today in 13.04 I edited /etc/rc6.d/S90reboot to run sh and examined the situation. (If I simply ran sh, I got no output, just like other messages in that script aren't displayed. I ended up using sh /dev/console /dev/console 21 and then repeatedly trying to run commands because something was taking some of the input. You may want to just add a lsof command redirecting to a file followed by a sync instead.) I ran lsof and got the attached output. Please ignore references to /o because that is the lsof output file. The output shows one file being written: /var/log/upstart/ureadahead-other.log by init. I don't need that service, so I solved the problem by disabling it: sudo sh -c echo 'manual' /etc/init/ureadahead-other.override I guess the proper solution would be to add a stop condition to /etc/init/ureadahead-other.conf, for example: stop on runlevel [06] ** Attachment added: lsof.reboot.txt https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1064185/+attachment/3665015/+files/lsof.reboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064185 Title: root partition not unmounting cleanly on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1064185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
