[Touch-packages] [Bug 1885410] Re: apt 2.0.2 lacks * wildcard support
** Changed in: apt (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/apt/+question/691567 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1885410 Title: apt 2.0.2 lacks * wildcard support Status in apt package in Ubuntu: Invalid Bug description: Upstream removed support for * as a wildcard in apt 2.0.0 They subsequently reinstated it in apt 2.1.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953531 https://lists.debian.org/deity/2020/03/msg00055.html https://metadata.ftp-master.debian.org/changelogs//main/a/apt/apt_2.1.6_changelog Will focal look to update apt to 2.1.x or backport this fix? The lack of this simple syntax for using apt with wildcards really destroys the utility of apt on the command line. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885410] [NEW] apt 2.0.2 lacks * wildcard support
Public bug reported: Upstream removed support for * as a wildcard in apt 2.0.0 They subsequently reinstated it in apt 2.1.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953531 https://lists.debian.org/deity/2020/03/msg00055.html https://metadata.ftp-master.debian.org/changelogs//main/a/apt/apt_2.1.6_changelog Will focal look to update apt to 2.1.x or backport this fix? The lack of this simple syntax for using apt with wildcards really destroys the utility of apt on the command line. Thanks ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1885410 Title: apt 2.0.2 lacks * wildcard support Status in apt package in Ubuntu: New Bug description: Upstream removed support for * as a wildcard in apt 2.0.0 They subsequently reinstated it in apt 2.1.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953531 https://lists.debian.org/deity/2020/03/msg00055.html https://metadata.ftp-master.debian.org/changelogs//main/a/apt/apt_2.1.6_changelog Will focal look to update apt to 2.1.x or backport this fix? The lack of this simple syntax for using apt with wildcards really destroys the utility of apt on the command line. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875533] Re: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1875533 Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: This problem happens on YouTube videos. It's almost like the sound is muted where you can hear something but not make it out. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernest 1080 F pulseaudio /dev/snd/controlC0: ernest 1080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 11:21:04 2020 InstallationDate: Installed on 2020-04-25 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernest 1080 F pulseaudio /dev/snd/controlC0: ernest 1080 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M PRO-VDH MAX (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 8.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 8.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB.10:bd08/28/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 8.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875044] Re: Host name not resolved
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1875044 Title: Host name not resolved Status in systemd package in Ubuntu: Expired Bug description: Systemd-resolved fails to resolve a host which has a private IP address, even though its DNS entry is public. This happens even when I am connected to a VPN where the host resides. Interestingly, if I manually issue a `host -a` request, the host gets resolved, and further resolution works until its cached entry times out. Here's some hopefully helpful output of me running `nslookup` and `host`: # nslookup > presto.lmta.lt Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: *** Can't find presto.lmta.lt: No answer > server 8.8.8.8 Default server: 8.8.8.8 Address: 8.8.8.8#53 > presto.lmta.lt Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: presto.lmta.lt Address: 10.41.0.118 > server 127.0.0.53 Default server: 127.0.0.53 Address: 127.0.0.53#53 > presto.lmta.lt Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: *** Can't find presto.lmta.lt: No answer [^D pressed] # host presto.lmta.lt [no output at all. I immediately run the next command] # host -a presto.lmta.lt Trying "presto.lmta.lt" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20532 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;presto.lmta.lt. IN ANY ;; ANSWER SECTION: presto.lmta.lt. 3599IN A 10.41.0.118 Received 48 bytes from 127.0.0.53#53 in 57 ms [then immediately afterwards:] # host presto.lmta.lt presto.lmta.lt has address 10.41.0.118 # nslookup > presto.lmta.lt Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: presto.lmta.lt Address: 10.41.0.118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885409] [NEW] Shut down or restart xorg error
Public bug reported: xorg always appears in shut down or restart as an error. Computer does not shut down & restart does not restart. No further details as the shut down or restart process is to fast for me to read fully? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Jun 28 13:15:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93] InstallationDate: Installed on 2020-06-03 (25 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 046d:0824 Logitech, Inc. Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B360 AORUS GAMING 3 WIFI ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_t08klu@/vmlinuz-5.4.0-39-generic root=ZFS=rpool/ROOT/ubuntu_t08klu ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360 AORUS GAMING 3 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360AORUSGAMING3WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360AORUSGAMING3WIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360 AORUS GAMING 3 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Jun 28 11:06:58 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885409 Title: Shut down or restart xorg error Status in xorg package in Ubuntu: New Bug description: xorg always appears in shut down or restart as an error. Computer does not shut down & restart does not restart. No further details as the shut down or restart process is to fast for me to read fully? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry:
[Touch-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend
Also seeing the same behavior on 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1530904] Re: ufw logrotate broken
This is still an issue in Focal (20.04).
I think it is because the "postrotate" line of the default
/etc/logrotate.d/ufw file reads:
```
invoke-rc.d rsyslog rotate >/dev/null 2>&1 || true
```
Which will not function on a systemd system.
Using the example from /etc/logrotate.d/rsyslog would work far better.
It simply reads:
```
/usr/lib/rsyslog/rsyslog-rotate
```
This runs a shell script shipped with rsyslog which will use systemctl
to issue a HUP when rotating on a systemd system, and the old invoke-
rc.d method on a system without systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1530904
Title:
ufw logrotate broken
Status in logrotate package in Ubuntu:
Confirmed
Bug description:
ubuntu 14.04.3 with all updates done.
This morning I enabled ufw full login for a while to track network problem.
Later I got warned /var is nearly full. I disabled login then found 3 huge
ufw.log kern.log & syslog files 1.2GB each. Wanting to logrotate to make room
nothing happens with sudo logrotate /etc/logrotate.conf nor sudo
/etc/cron.daily/logrotate although I can see some logs were rotated during past
night.
I have seen messages about permissions I can't remember where.
ls -ld /var/log
drwxrwxr-x 14 root syslog 4096 janv. 4 07:44 /var/log
ls -l /var/log/kern*
-rw-r- 1 syslog adm 1229901824 janv. 4 13:36 /var/log/kern.log
-rw-r- 1 syslog adm 13373 janv. 4 07:44 /var/log/kern.log.1
-rw-r- 1 syslog adm509 déc 27 08:04 /var/log/kern.log.2.gz
-rw-r- 1 syslog adm 152524 déc 21 07:41 /var/log/kern.log.3.gz
-rw-r- 1 syslog adm521 déc 13 07:54 /var/log/kern.log.4.gz
ls -l /var/log/sysl*
-rw-r- 1 syslog adm 1229910016 janv. 4 16:30 /var/log/syslog
-rw-r- 1 syslog adm 11305 janv. 4 07:44 /var/log/syslog.1
-rw-r- 1 syslog adm748 janv. 3 07:42 /var/log/syslog.2.gz
-rw-r- 1 syslog adm692 janv. 2 07:37 /var/log/syslog.3.gz
-rw-r- 1 syslog adm719 janv. 1 07:58 /var/log/syslog.4.gz
-rw-r- 1 syslog adm691 déc 31 07:50 /var/log/syslog.5.gz
-rw-r- 1 syslog adm 1504 déc 30 07:38 /var/log/syslog.6.gz
-rw-r- 1 syslog adm697 déc 29 08:05 /var/log/syslog.7.gz
ls -l /var/log/ufw*
-rw-r- 1 syslog adm 1229922304 janv. 4 11:38 /var/log/ufw.log
-rw-r- 1 syslog adm 5447 janv. 4 00:17 /var/log/ufw.log.1
-rw-r- 1 syslog adm380 août 15:29 /var/log/ufw.log.2.gz
cat /etc/logrotate.conf
# see "man logrotate" for details
# rotate log files weekly
weekly
# use the syslog group by default, since this is the owning group
# of /var/log/syslog.
su root syslog
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# uncomment this if you want your log files compressed
#compress
# packages drop log rotation information into this directory
include /etc/logrotate.d
# no packages own wtmp, or btmp -- we'll rotate them here
/var/log/wtmp {
missingok
monthly
create 0664 root utmp
rotate 1
}
/var/log/btmp {
missingok
monthly
create 0660 root utmp
rotate 1
}
# system-specific logs may be configured here
cat /etc/logrotate.d/ufw
/var/log/ufw.log
{
rotate 4
weekly
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
invoke-rc.d rsyslog reload >/dev/null 2>&1 || true
endscript
}
cat /etc/cron.daily/logrotate
#!/bin/sh
# Clean non existent log file entries from status file
cd /var/lib/logrotate
test -e status || touch status
head -1 status > status.clean
sed 's/"//g' status | while read logfile date
do
[ -e "$logfile" ] && echo "\"$logfile\" $date"
done >> status.clean
mv status.clean status
test -x /usr/sbin/logrotate || exit 0
/usr/sbin/logrotate /etc/logrotate.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1530904/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
Observing on Focal 20.04 on ROG STRIX X470-I, same ALC1220 audio device. Its intermittent, sometimes audacity will record properly. Sometimes it will record slow and playback fast. its not just audacity, e.g. chrome observes same affect (https://mictests.com/) bumped kernel to 5.7.6-050706-generic from mainline, same affect alsa-base 1.0.25+dfsg-0ubuntu5, pulseaudio 1:13.99.1-1ubuntu3.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1764965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1530904] Re: ufw logrotate broken
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: logrotate (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1530904
Title:
ufw logrotate broken
Status in logrotate package in Ubuntu:
Confirmed
Bug description:
ubuntu 14.04.3 with all updates done.
This morning I enabled ufw full login for a while to track network problem.
Later I got warned /var is nearly full. I disabled login then found 3 huge
ufw.log kern.log & syslog files 1.2GB each. Wanting to logrotate to make room
nothing happens with sudo logrotate /etc/logrotate.conf nor sudo
/etc/cron.daily/logrotate although I can see some logs were rotated during past
night.
I have seen messages about permissions I can't remember where.
ls -ld /var/log
drwxrwxr-x 14 root syslog 4096 janv. 4 07:44 /var/log
ls -l /var/log/kern*
-rw-r- 1 syslog adm 1229901824 janv. 4 13:36 /var/log/kern.log
-rw-r- 1 syslog adm 13373 janv. 4 07:44 /var/log/kern.log.1
-rw-r- 1 syslog adm509 déc 27 08:04 /var/log/kern.log.2.gz
-rw-r- 1 syslog adm 152524 déc 21 07:41 /var/log/kern.log.3.gz
-rw-r- 1 syslog adm521 déc 13 07:54 /var/log/kern.log.4.gz
ls -l /var/log/sysl*
-rw-r- 1 syslog adm 1229910016 janv. 4 16:30 /var/log/syslog
-rw-r- 1 syslog adm 11305 janv. 4 07:44 /var/log/syslog.1
-rw-r- 1 syslog adm748 janv. 3 07:42 /var/log/syslog.2.gz
-rw-r- 1 syslog adm692 janv. 2 07:37 /var/log/syslog.3.gz
-rw-r- 1 syslog adm719 janv. 1 07:58 /var/log/syslog.4.gz
-rw-r- 1 syslog adm691 déc 31 07:50 /var/log/syslog.5.gz
-rw-r- 1 syslog adm 1504 déc 30 07:38 /var/log/syslog.6.gz
-rw-r- 1 syslog adm697 déc 29 08:05 /var/log/syslog.7.gz
ls -l /var/log/ufw*
-rw-r- 1 syslog adm 1229922304 janv. 4 11:38 /var/log/ufw.log
-rw-r- 1 syslog adm 5447 janv. 4 00:17 /var/log/ufw.log.1
-rw-r- 1 syslog adm380 août 15:29 /var/log/ufw.log.2.gz
cat /etc/logrotate.conf
# see "man logrotate" for details
# rotate log files weekly
weekly
# use the syslog group by default, since this is the owning group
# of /var/log/syslog.
su root syslog
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# uncomment this if you want your log files compressed
#compress
# packages drop log rotation information into this directory
include /etc/logrotate.d
# no packages own wtmp, or btmp -- we'll rotate them here
/var/log/wtmp {
missingok
monthly
create 0664 root utmp
rotate 1
}
/var/log/btmp {
missingok
monthly
create 0660 root utmp
rotate 1
}
# system-specific logs may be configured here
cat /etc/logrotate.d/ufw
/var/log/ufw.log
{
rotate 4
weekly
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
invoke-rc.d rsyslog reload >/dev/null 2>&1 || true
endscript
}
cat /etc/cron.daily/logrotate
#!/bin/sh
# Clean non existent log file entries from status file
cd /var/lib/logrotate
test -e status || touch status
head -1 status > status.clean
sed 's/"//g' status | while read logfile date
do
[ -e "$logfile" ] && echo "\"$logfile\" $date"
done >> status.clean
mv status.clean status
test -x /usr/sbin/logrotate || exit 0
/usr/sbin/logrotate /etc/logrotate.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1530904/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885380] Re: ejecting mp3-CD doesn't leave tray open
btw, Audio CDs and DVDs work fine, the problem is limited to mp3-CDs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/1885380 Title: ejecting mp3-CD doesn't leave tray open Status in eject package in Ubuntu: New Bug description: When I load an mp3-CD in either of my DVD drives (DVDrom and BlueRay Burner from LG), when I try to eject the CD, the tray doesn't stay open long enough to retrieve it, but closes again right away. This happens, no matter if I eject from KDE apps or from the terminal. Same problem on a second computer installed and configured the same way. OS is Kubuntu 20.04 LTS Linux ... 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux on both machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1885380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885380] Re: ejecting mp3-CD doesn't leave tray open
/bin/eject ** Package changed: ubuntu => eject (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/1885380 Title: ejecting mp3-CD doesn't leave tray open Status in eject package in Ubuntu: New Bug description: When I load an mp3-CD in either of my DVD drives (DVDrom and BlueRay Burner from LG), when I try to eject the CD, the tray doesn't stay open long enough to retrieve it, but closes again right away. This happens, no matter if I eject from KDE apps or from the terminal. Same problem on a second computer installed and configured the same way. OS is Kubuntu 20.04 LTS Linux ... 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux on both machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1885380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885380] [NEW] ejecting mp3-CD doesn't leave tray open
You have been subscribed to a public bug: When I load an mp3-CD in either of my DVD drives (DVDrom and BlueRay Burner from LG), when I try to eject the CD, the tray doesn't stay open long enough to retrieve it, but closes again right away. This happens, no matter if I eject from KDE apps or from the terminal. Same problem on a second computer installed and configured the same way. OS is Kubuntu 20.04 LTS Linux ... 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux on both machines. ** Affects: eject (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ejecting mp3-CD doesn't leave tray open https://bugs.launchpad.net/bugs/1885380 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eject in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Description changed: + [impact] + + rpcbind binds to a 'random' reserved port at startup, which can conflict + with the reserved port number for other applications that actually 'own' + the reserved port number. One example is cups, which uses the reserved + port 631. + + This prevents the actual 'owner' of the reserved port from starting, + since it can't bind to its reserved port. + + Additionally, this can raise alarms from security monitoring software + that does not expect programs to be listening on random reserved ports. + + [test case] + + start rpcbind and check which ports it is listening on, e.g.: + + $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc + udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind + + each time rpcbind is restarted, it will be listening to a different + 'random' port. + + [regression potential] + + this adds a method to disable rpcbind from listening to the 'random' + port. any regression would likely prevent rpcbind from starting, or may + cause problems with the interaction between rpcinfo and rpcbind, as + rpcinfo may use the random reserved port in some cases, as detailed in + the Debian bug. + + [scope] + + This is needed only for Bionic and earlier. + + In Focal and later, and in Debian, rpcbind defaults to not opening the + random reserved port. The admin can use the -r parameter to cause + rpcbind to restore the old behavior of opening the random reserved port. + + [other info] + + Note that the -r parameter is a Debian addition, and the upstream + rpcbind has disabled the random port functionality at build time; there + is no runtime parameter to allow the admin to choose the behavior. + + Also, as discussed in the Debian bug, disabling this rpcbind 'feature' + is known to cause problems for the rpcinfo program, which is why Debian + introduced the -r parameter. So, when this -r parameter is backported to + Bionic and earlier, we must retain the default behavior for those + releases, which is for rpcbind to open the random reserved port. + + TBD: specific method to disable rmtcalls in backport + + + [original description] + + As this backports that functionality, it + Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. ** Changed in: rpcbind (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: rpcbind (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: rpcbind (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: rpcbind (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: rpcbind (Ubuntu Bionic) Status: New => In Progress ** Changed in: rpcbind (Ubuntu Xenial) Status: New => In Progress ** Changed in: rpcbind (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: In Progress Status in rpcbind source package in Bionic: In Progress Status in rpcbind package in Debian: Unknown Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a method to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore
[Touch-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Also affects: cups (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: rpcbind (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: rpcbind (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Status: Confirmed => Invalid ** No longer affects: cups (Ubuntu Xenial) ** No longer affects: cups (Ubuntu Bionic) ** Bug watch added: Debian Bug tracker #939890 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939890 ** Also affects: rpcbind (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939890 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: New Status in rpcbind source package in Xenial: New Status in rpcbind source package in Bionic: New Status in rpcbind package in Debian: Unknown Status in Fedora: Confirmed Bug description: Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885388] [NEW] E: Failed to fetch store Hash Sum mismatch
Public bug reported: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: New Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885388] Re: E: Failed to fetch store Hash Sum mismatch
$ uname -a; cat /etc/issue.net Linux XPS 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Groovy Gorilla (development branch) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: New Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885388] Re: E: Failed to fetch store Hash Sum mismatch
tried to remove /var/lib/apt/lists/* and redo the apt update ... but still getting the same Hash Sum mismatch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: New Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885388] Re: E: Failed to fetch store Hash Sum mismatch
$ apt policy apt apt: Installed: 2.1.1 Candidate: 2.1.1 Version table: *** 2.1.1 100 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: New Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881659] Re: Dell Inspirion 5391: headphones work only if I manually switch source port every time and no different volume levels for speaker and headphones
** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881659 Title: Dell Inspirion 5391: headphones work only if I manually switch source port every time and no different volume levels for speaker and headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a laptop Dell Inspirion 5391 that was shipped with Ubuntu 18.04, and it doesn't have such problems. But I have manually installed Xubuntu 20.04 LTS (firstly because I need full disk encryption with LUKS). And I have two problems the with sound system: 1) If I plug headphones, there is no sound. Sound becomes only if I manually switch source port to "Headset Mono microphone" from "Headphones stereo microphone" in pavucontrol or with the command: pacmd set-source-port 4 "[In] Headset" or with ALSA: amixer set 'Input Source' 'Headset Mic' I have a workaround with /etc/acpi/events, but it is not seamless (I have an one second delay when I plug the headphones). 2) There is no separate volume levels for speaker and headphone in pulseaudio. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tenikeev 3385 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jun 1 23:13:38 2020 InstallationDate: Installed on 2020-05-28 (4 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07DM2C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5391 dmi.product.sku: 096E dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-31T22:56:28.472784 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881659] Re: Dell Inspirion 5391: headphones work only if I manually switch source port every time and no different volume levels for speaker and headphones
Simple mixer control 'Input Source',0 Capabilities: cenum Items: 'Headphone Mic' 'Headset Mic' Item0: 'Headset Mic' Simple mixer control 'Input Source',1 Capabilities: cenum Items: 'Headphone Mic' 'Headset Mic' Item0: 'Headset Mic' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881659 Title: Dell Inspirion 5391: headphones work only if I manually switch source port every time and no different volume levels for speaker and headphones Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a laptop Dell Inspirion 5391 that was shipped with Ubuntu 18.04, and it doesn't have such problems. But I have manually installed Xubuntu 20.04 LTS (firstly because I need full disk encryption with LUKS). And I have two problems the with sound system: 1) If I plug headphones, there is no sound. Sound becomes only if I manually switch source port to "Headset Mono microphone" from "Headphones stereo microphone" in pavucontrol or with the command: pacmd set-source-port 4 "[In] Headset" or with ALSA: amixer set 'Input Source' 'Headset Mic' I have a workaround with /etc/acpi/events, but it is not seamless (I have an one second delay when I plug the headphones). 2) There is no separate volume levels for speaker and headphone in pulseaudio. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tenikeev 3385 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jun 1 23:13:38 2020 InstallationDate: Installed on 2020-05-28 (4 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07DM2C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5391 dmi.product.sku: 096E dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-31T22:56:28.472784 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()
** Changed in: accountsservice (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1843982 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Fix Released Status in accountsservice package in Debian: Fix Released Bug description: [ Description ] When accountsservice's daemon is restarted - particularly when there is a user configured for auto login - it can cause code using its library to crash. This is bad because gnome-shell is one of those users which crashes. [ QA ] Configure a user for automatic login in gnome-shell. Update to this SRU, and then *restart your system*. The crash is in the library part, and so you will still see it if programs loaded the buggy version. Restarting is the easiest way to make sure you're not on it. Restart accounts-daemon.service (sudo systemctl restart accounts- daemon.service) a few times, leaving several seconds between each attempt. See that it crashes if you don't have this SRU, and doesn't if you do have it. --- Test that fast user switching still works properly. --- Take a look at the error reports listed below and hopefully see them not occurring (barring the usual noise) with the SRU. [ Regression potential ] We think this is safe - it tells clients that the daemon is away when it quits, and is back when it comes back. They should get appropriate signals to indicate this. Nevertheless, these signals are sent when they weren't before now, so that could cause problems. Watch out for errors creeping up with this SRU. We wondered upstream whether some more protections might be needed. I'm thinking that those should be *additional* safety rails around this fix, but it could actually be that more is needed and this fix isn't complete. [ Original report ] https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 14 10:29:16 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-05-24 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885334] Re: Crashes when running World of Warcrat with wine/vulkan
I found the older version at http://ppa.launchpad.net/oem-solutions- group/nvidia-driver-staging/ubuntu. It turned out that it's most likely that the hardware is broken, so it was just a coincidence that the hardware failed after the driver update. Sorry for the noise. Best regards, Matthias ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885334 Title: Crashes when running World of Warcrat with wine/vulkan Status in xorg package in Ubuntu: Invalid Bug description: Hi, while version 440.82-0ubuntu0~0.18.04.2 ran with out any problems 440.100-0ubuntu0.18.04.1 crashes after a while with the following errors: Jun 26 22:41:31 imobil2 kernel: [ 1548.518774] NVRM: GPU at PCI::01:00: GPU-059d1eda-0ee6-ba17-38a2-5e6330b325f1 Jun 26 22:41:31 imobil2 kernel: [ 1548.518779] NVRM: Xid (PCI::01:00): 31, pid=1108, Ch 0012, intr 1000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_PROP_0 faulted @ 0x1_12844000. Fault is of type FAULT_INFO_TYPE_UNSUPPORTED_KIND ACCESS_TYPE_WRITE Jun 26 22:47:32 imobil2 kernel: [ 1909.747689] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 1 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747698] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 2 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747704] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 3 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747708] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 5 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747713] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 9 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747718] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 10 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747723] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 18 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747728] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 19 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747735] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: ESR 0x405840=0x8e0c062e Jun 26 22:47:32 imobil2 kernel: [ 1909.748005] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: ChID 0008, Class a097, Offset 1614, Data Jun 26 22:47:33 imobil2 kernel: [ 1910.876226] NVRM: Xid (PCI::01:00): 62, pid=1265, 0110(25dc) 840008ce c415c455 This happend multiple times. Unfortunately the old driver version is not available anymore and I can't check if this is really caused by the driver update. Best regards, Matthias ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3 Date: Fri Jun 26 22:59:14 2020 DistUpgraded: 2020-04-09 19:50:27,912 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 4.15.0-106-generic, x86_64: installed nvidia, 440.100, 4.15.0-108-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK104 [GeForce GTX 770] [1462:2825] InstallationDate: Installed on 2013-12-15 (2384 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: MSI MS-7821 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=UUID=10f3ba43-ad16-4df4-b3b4-e86b64e9f96e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-09 (78 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G45 GAMI
[Touch-packages] [Bug 1885363] Re: Screen flickers after waking up from suspend
Did some more testing: * If I logout when the screen flickers, it also flickers in the login screen after logging out and also after logging back in. * After a reboot (without logging in), the flickering disappears. After suspending from there and waking up, the flickering appears on the login screen. * After another reboot (this time logging in), there is also no flickering. * Booting from a live Fedora 32 USB, the flickering after suspend does *not* occur, even after multiple suspends. * Booting from a live Ubuntu 20.04 USB, the flickering *does* occur after suspend. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885363 Title: Screen flickers after waking up from suspend Status in xorg package in Ubuntu: New Bug description: I upgraded my Ubuntu 20.04 system with a new graphics card a few days ago. Everything seems fine when running the system normally, however whenever I suspend the machine and then wake it back up, severe problems occur. The first time, the machine froze completely. Switching to a different TTY didn't work anymore and the keyboard LEDs didn't respond to caps and num lock anymore, so I had to force shutdown. The second time, it came back OK but the screen has been flickering heavily since. Restarting Gnome and unplugging and plugging monitors back in hasn't helped. Relevant specs: CPU: AMD® Ryzen 9 3900x 12-core processor × 24 GPU: AMD® Radeon rx 5600 xt (MSI RADEON RX 5600 XT MECH OC) Monitors: 1x Acer running at 3840x2160 60Hz, 2x Medion (showing up as "Messeltronik Dresden GmbH") both running at 1920x1080 60Hz. Gnome: 3.36.2 X11 Apt doesn't report any updates. The flickering is most pronounced on the Acer. On the Medions, it seems to only happen when something changes on the screen. I have tried to capture this on video: https://youtu.be/HWT1J76-x94 This bug seem quite similar to this one (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588). I can also stop the flickering by switching the Acer to 1080p but when switching back to 4k, the problem reappears. I hope that ubuntu-bug has included all the necessary details. Let me know if you need anything else. Thank you very much for your help! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Jun 27 10:44:32 2020 DistUpgraded: 2020-04-30 20:17:33,403 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:381e] InstallationDate: Installed on 2019-03-26 (458 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-30 (57 days ago) dmi.bios.date: 04/08/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: X570 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd04/08/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Touch-packages] [Bug 1864280] Re: software-properties-gtk removes [arch=amd64]
Can someone please reopen this? I provided the necessary details for producibility... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1864280 Title: software-properties-gtk removes [arch=amd64] Status in software-properties package in Ubuntu: Expired Bug description: When editing apt sources via software-properties-gtk, additional options like [arch=amd64] are removed. With more and more repositories deprecating i386, this problem becomes more and more important. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1864280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838436] Re: popt download location broken
** Changed in: popt (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to popt in Ubuntu. https://bugs.launchpad.net/bugs/1838436 Title: popt download location broken Status in popt package in Ubuntu: Triaged Status in popt package in Debian: Fix Released Bug description: rpm5.org disappeared, with download area, home page and CVS repo. See also https://bugs.archlinux.org/task/62888?project=1&string=popt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popt/+bug/1838436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885363] [NEW] Screen flickers after waking up from suspend
Public bug reported: I upgraded my Ubuntu 20.04 system with a new graphics card a few days ago. Everything seems fine when running the system normally, however whenever I suspend the machine and then wake it back up, severe problems occur. The first time, the machine froze completely. Switching to a different TTY didn't work anymore and the keyboard LEDs didn't respond to caps and num lock anymore, so I had to force shutdown. The second time, it came back OK but the screen has been flickering heavily since. Restarting Gnome and unplugging and plugging monitors back in hasn't helped. Relevant specs: CPU: AMD® Ryzen 9 3900x 12-core processor × 24 GPU: AMD® Radeon rx 5600 xt (MSI RADEON RX 5600 XT MECH OC) Monitors: 1x Acer running at 3840x2160 60Hz, 2x Medion (showing up as "Messeltronik Dresden GmbH") both running at 1920x1080 60Hz. Gnome: 3.36.2 X11 Apt doesn't report any updates. The flickering is most pronounced on the Acer. On the Medions, it seems to only happen when something changes on the screen. I have tried to capture this on video: https://youtu.be/HWT1J76-x94 This bug seem quite similar to this one (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588). I can also stop the flickering by switching the Acer to 1080p but when switching back to 4k, the problem reappears. I hope that ubuntu-bug has included all the necessary details. Let me know if you need anything else. Thank you very much for your help! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Jun 27 10:44:32 2020 DistUpgraded: 2020-04-30 20:17:33,403 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:381e] InstallationDate: Installed on 2019-03-26 (458 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-30 (57 days ago) dmi.bios.date: 04/08/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: X570 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd04/08/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "Video of the flickering" https://bugs.launchpad.net/bugs/1885363/+attachment/5387645/+files/VID_20200627_104547.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885363 Title: Screen flickers after waking up from suspend Status in xorg package in Ubuntu: New Bug description: I upgraded my Ubuntu 20.04 system with a new graphics card a few days ago. Everything seems fine when running the system normally, however whenever I suspend the machine and then wake it back up, severe problems occur. The first time, the machine froz
[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
This only started for me yesterday. I'm on 20.04 and don't remember running any updates. Tried most of the above and nothing works for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
